-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Thx for the reply. I fixed the problem by editing /etc/securetty/inittab. On Tue, Apr 27, 2004 at 10:56:37PM -0600, Joseph C. Lininger wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Try these solutions. First, check permitions on /dev/tty<n> where <n> is > the number of the tty. Second, ensure teh lines in inittab read correctly. > > c1:1235:respawn:/sbin/agetty 38400 tty1 linux > > Increment the number for each console. There are two problems I see with > your example. First, list the terminal type (linux). Second, use agetty not > getty. Finally, root logins won't work unless all of the tty's you want to > login in as root from are listed in /etc/securetty > - --- > Joseph C. Lininger > jbahm at pcdesk.net > note, the following is used for automated processing. Please leave in tact > if quoting me in a reply. > Verification: 5eab38a77ac40416e075be8f50607ff7 > - ----- Original Message ----- > From: "Igor Gueths" <igueths at lava-net.com> > To: <speakup at braille.uwo.ca> > Sent: Tuesday, April 27, 2004 8:34 PM > Subject: init/login problems > > > >-----BEGIN PGP SIGNED MESSAGE----- > >Hash: SHA1 > > > >Hi all. i just installed Slackware-9.1. After finding out that dhclient > >was broken, I used dhcpcd and got an IP from the router over here. > >However, I noticed that only 5 ttys were enabled, so I edited inittab > >just like I did on my previous Debian system to add 6 more consoles. The > >syntax in inittab is: console:1235:respawn:/sbin/getty 38400 <tty>. > >Example: c6:1235:respawn:/sbin/getty 38400 tty6 > > > >And I did this for all 12 ttys. Granted, I got the 12 > >consoles...However, I can't login as root in consoles 6-12, nor can I > >login as user (the account being igueths). All the other accounts I > >created could login just fine. Could my problem be something with the > >UID's not being set propperly? Also, init is periodically respawning > >process when it shouldn't be i.e., I get messages about certain consoles > >respawning too fast. Anyone have any ideas on how I can fix this? Quite > >honestly, I've never seen this type of behavior before on a pretty much > >newly installed system. Thanks! > >spawning too fa > >- -- > >Failure is not an option, it comes bundled with your Microsoft product. > >-----BEGIN PGP SIGNATURE----- > >Version: GnuPG v1.2.3 (GNU/Linux) > > > >iD8DBQFAjxhRNohoaf1zXJMRAtf8AJwOsYSD8skzu/pMtz+hg+Dsi3vqxQCeIoML > >KNcaJTmgnC4Z+zFn7pBZsAI= > >=b5p0 > >-----END PGP SIGNATURE----- > > > >_______________________________________________ > >Speakup mailing list > >Speakup at braille.uwo.ca > >http://speech.braille.uwo.ca/mailman/listinfo/speakup > > > -----BEGIN PGP SIGNATURE----- > Version: PGP 8.0.3 > > iQA/AwUBQI85gyenap9Jqj2wEQIDZgCgt7Hlng4kzZT6YADPv07Wu4/7I8sAniyc > Ctvb2VIxpWOnOSZYTEo5z8X1 > =ZnaV > -----END PGP SIGNATURE----- > > > _______________________________________________ > Speakup mailing list > Speakup at braille.uwo.ca > http://speech.braille.uwo.ca/mailman/listinfo/speakup - -- Failure is not an option, it comes bundled with your Microsoft product. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQFAjzrdNohoaf1zXJMRAmszAJ4rVLoS45VK/J9/3rvxGWhlqpYxGgCffZS3 rYRjl68uo2Ob+yBV6zb4Zi8= =wuDx -----END PGP SIGNATURE-----