This is a discussion on slackware 10 login problems within the Slackware Linux Support forums, part of the Unix Operating Systems category; --> On Thu, 26 Aug 2004 15:09:55 +0100, nick@linicks.net wrote: [...] > But moaning at me doesn't help the guy ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| On Thu, 26 Aug 2004 15:09:55 +0100, nick@linicks.net wrote: [...] > But moaning at me doesn't help the guy out. He helped you. Best regards, -- DIG (Dmitri I GOULIAEV) Aahz's law: The best way to get information on usenet is not to ask a question, but to post the wrong information. |
| |||
| NOTE: This message was sent thru a mail2news gateway. No effort was made to verify the identity of the sender. -------------------------------------------------------- pgp trash troll delete Hicks, Alan 188 Shady Dale Dr Lizella, GA 31052 478-935-8132 +Alan Hicks+ <alan@lizella.network> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > In alt.os.linux.slackware, Nick dared to utter, > > Well yes, but then why not just suggest the solution to the guy? > 1) Some one else had already offered a valid suggestion. > 2) I was steering him away from your incorrect advice. > 3) To teach you to check something before assuming it to be true across > distributions. > - -- > It is better to hear the rebuke of the wise, > Than for a man to hear the song of fools. > Ecclesiastes 7:5 > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.2.1 (GNU/Linux) > iD8DBQFBLj5glKR45I6cfKARAqnTAKCAyEqocvDUTv4/M4akqAQq3xZlyQCfewp/ > OmcFfSV2CzFHKzUfCsb1Bj4= > =Z6TH > -----END PGP SIGNATURE----- |
| |||
| NOTE: This message was sent thru a mail2news gateway. No effort was made to verify the identity of the sender. -------------------------------------------------------- pgp trash troll delete Hicks, Alan 188 Shady Dale Dr Lizella, GA 31052 478-935-8132 +Alan Hicks+ <alan@lizella.network> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > In alt.os.linux.slackware, Nick dared to utter, > > You don't need to boot off CD. Just reboot and at the lilo prompt, type > > 'linux single'. It will boot minimum and you will be root! > Check your facts. This ain't Red Hat. When you boot to single user mode > in Slackware, you still have to enter that root password to log in. > - -- > It is better to hear the rebuke of the wise, > Than for a man to hear the song of fools. > Ecclesiastes 7:5 > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.2.1 (GNU/Linux) > iD8DBQFBLeHglKR45I6cfKARAp0wAJ4ouyTjS/i+HcKIc00h+3mSwnm82gCgsaC/ > lPuKuB4f4+tJYMXakqrb5Ts= > =0pwF > -----END PGP SIGNATURE----- |
| |||
| PAUL SUTTON wrote: > Nick wrote: >> Dominik L.. Borkowski wrote: >> > > Thanks I'll try that, what file system do you recommend, i am using > reiser, but perhaps I should use ext2 or ext3. > > paul > >> >>>Nick wrote: >>> >>> >>>>So what point is that then? If anybody has access to console, they can >>>>boot up knoppix or whatever and get in anyway? >>> >>>his point was that your advice was invalid. a working solution would be >>>to use 'Linux init=/bin/bash' for example. >> >> >> Well yes, but then why not just suggest the solution to the guy? >> >> I *didn't* check (the thought never crossed my mind) 'linux single' on >> Slackware 10 still prompts for root password - so my bad. But moaning at >> me doesn't help the guy out. >> >> Nick Um, mount it as whatever it was formatted as? |
| ||||
| On 2004-08-26, HJohnson <HuMJohn@AeroSurf.Net> wrote: > OK, after looking at the discussions on this topic, it seems no one gave > you decent advice on how to get into your system. I have been there and > done that a few times (mostly other people's systems.) Here is a simple > means of fixing your login problem. > > 1. Boot off of the Slackare install CD > 2. Mount your Linux HD partition that has the /etc. > 3. cd to <mount point>/etc directory > 4. using the vi command (stripped down version of elvis), edit the > passwd file. Usually you'd want vipw [-s] and vigr [-s] for this, if you want to edit directly. I don't think there's much chance for file corruption in single-user mode, but in multi-user it could happen or be more likely to. -- --- SIGSEGV (Segmentation fault) @ 0 (0) --- +++ killed by SIGSEGV +++ |