Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU |
On Fri, Jul 16, 2004 at 09:45:40AM -0700, Antoinette wrote: > Hey All, > > I've been working on this issue for awhile, without any success. > Here goes: > > I have a linux box running Red Hat Linux release 8.0. And, I'm > attempting to connect remotely via a remote console tool, > ConsoleWorks v1.5 and v2.0. On the linux box, I setserial to > 9600 baud, on the ConsoleWorks side, everything is configured > correctly for access. I have used Linux for about 8 years, configured console access to many a system, but honestly I've never ever had a need to use the setserial program. If you configure your system properly, you shouldn't need to do it. So, first, are you sure that your system is properly configured to allow console access? 1. Are you passing options to the kernel to tell it to use the serial port as a console? If so, how, and which options? 2. Are you running some sort of getty process on the tty? If so, which getty, and how is it started? What are the command-line options you're using? Let's start there, and see where it gets us. :) -- Derek D. Martin http://www.pizzashack.org/ GPG Key ID: 0xDFBEAD02 -=-=-=-=- This message is posted from an invalid address. Replying to it will result in undeliverable mail. Sorry for the inconvenience. Thank the spammers. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: <http://lists.blu.org/pipermail/discuss/attachments/20040716/a7013994/attachment.sig>
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |