Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Hey guys. The problem is myself, of course. I'm trying to communicate bi-directionally through ttyS0. I have tried agetty, but I get messages like 'pam: Invalid user"<server output>"'
I can see all the server output, up until it waits for input from me. This is where the rut lies, using this method is one-way communication. By using agetty or mgetty, it seems like the programs are creating a login prompt with the serial port. Upon receiving data from the server, these programs quit.
The goal here is to have two-way communication without any login, somewhat a simple direct terminal to the serial port.
you should add the agetty commands to /etc/inittab to make it respawn, i set this up recently and didn't get anything actually functional till i had it in there: "s0:2345:respawn:/sbin/agetty -L 115200 ttyS0 vt100"