need some help here
I''ve just installed an LFS system, but, when i get to the "login:" part, and i type a user name, it won''t proceed to the "password:" part. all it would do is wait a long time (5-7 seconds) and "login:" again.
have any of you ever run into this problem and knows the solution?
Have you set up the user? Can you login as root? Maybe your login scripts/procedure are/is fscked?
maybe, but either way, it should ask me for the password even if i enter a wrong user name.
The only idea I have is some runlevel problem, perhaps. You''re positive you''re booting into multiuser runlevel, right?
Otherwise, yeah, it''s probably a flawed login script.
rm -rf /bin/laden
Otherwise, yeah, it''s probably a flawed login script.
rm -rf /bin/laden
quote: Original post by danz
I've just installed an LFS system, but, when i get to the "login:" part, and i type a user name, it won't proceed to the "password:" part. all it would do is wait a long time (5-7 seconds) and "login:" again.
have any of you ever run into this problem and knows the solution?
Go into runlevel 1( if I remember correctly ) and type in root at the logon, that should allow you to log into the system and recheck your configs. They might be flawed. LFS can sometimes be a hassle to intall and set up properly. If you want something similar that is a bit less complicated to install, get Gentoo.... Much easier to use and the new version is pretty good and up to date. On my p3 500 w/512Mb RAM at school it installed in about 30 minutes including kernel compile and emerging the basic system tools, the XFS tools and some other small apps.
"DaHjajmajQa'jajHeghmeH!"
Cyberdrek
danielc@iquebec.com
Founder
Laval Linux
/(bb|[^b]{2})/ that is the Question -- ThinkGeek.com
Hash Bang Slash bin Slash Bash -- #!/bin/bash
[edited by - cyberdrek on June 20, 2002 11:15:16 PM]
[Cyberdrek | ]
this is what i get when i get into runlevel 1:
init timeout opening/writing control channel /dev/initctl
does it have anything to do with the fact i init from a chrooted enviroment?
init timeout opening/writing control channel /dev/initctl
does it have anything to do with the fact i init from a chrooted enviroment?
quote: Original post by danz
this is what i get when i get into runlevel 1:
init timeout opening/writing control channel /dev/initctl
does it have anything to do with the fact i init from a chrooted enviroment?
This error looks to me like a bootstrapping error. Hmmm... Maybe you should restart the installation making sure to double check the docs as you''re installing. I''ve never had this problem before. Then again, I only installed LFS once. Oh and it is possible that it is related to your system being chrooted but why would you still be chrooted??? After bootstrapping, installing the system utils( /bin, /sbin, /etc, ... ) and Lilo or Grub, you should be able to reboot directly into your system without a chroot call... Can you elaborate on why your still chrooted, that would help us to figure out your problem.
"DaHjajmajQa''jajHeghmeH!"
Cyberdrek
danielc@iquebec.com
Founder
Laval Linux
/(bb|[^b]{2})/ that is the Question -- ThinkGeek.com
Hash Bang Slash bin Slash Bash -- #!/bin/bash
[Cyberdrek | ]
the problem i mentioned at the top of the page.
whenever i get to the login/password part of the boot, i type in the user name, and then it just waits (as if i have typed a wrong password) and askes for a user name again. it just skippes the entire password part.
whenever i get to the login/password part of the boot, i type in the user name, and then it just waits (as if i have typed a wrong password) and askes for a user name again. it just skippes the entire password part.
Does /dev/initctl exist (in the LFS tree)? IIRC it should be a FIFO, so if it doesn''t exist, try running (as root):
mknod /dev/initctl p
chmod 600 /dev/initctl
in the chrooted environment, and then rebooting into LFS. I have no idea if this will help with your login problem, but I think init likes to have that FIFO
If it doesn''t help (or you already had /dev/initctl), try booting into LFS with the init=/bin/bash kernel option. This should take you directly into a bash shell without requiring you to login.
mknod /dev/initctl p
chmod 600 /dev/initctl
in the chrooted environment, and then rebooting into LFS. I have no idea if this will help with your login problem, but I think init likes to have that FIFO
If it doesn''t help (or you already had /dev/initctl), try booting into LFS with the init=/bin/bash kernel option. This should take you directly into a bash shell without requiring you to login.
This topic is closed to new replies.
Advertisement
Popular Topics
Advertisement
Recommended Tutorials
Advertisement