[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [cobalt-users] Single User Mode (RAQ2 )



> Hey all,
>
> Well, I've done something really awful to the group file on our staging
> (thank god) Raq2 and now I can no longer su to root. I've tried the old
> paper clip method and I'm successful in resetting the admin password but
not
> the root password.
>
> I've done some searching through the archives and have found some great
> instructions for bringing the machine into single user mode posted by
Graeme
> Fowler.
>
> http://list.cobalt.com/pipermail/cobalt-users/2000-July/015901.html
>
> <snip>
> 1. Find another machine (laptop perhaps) with serial port free.
> 2. Find a null-modem serial cable
> 3. Connect the two together via their serial ports (use port 1 on the
> RaQ)
> 4. Run a terminal emulator on the other machine (whatever takes your
> fancy)
> 5. Reboot the RaQ. At the start of the boot sequence press 'space' when
> it says to and you will enter ROM mode - similar to the BIOS on a PC.
> 6. type (not the enclosing quotes) 'boot' <return>
> 7. type (not the enclosing quotes) 'set_params "single"' <return>
> 8. type (not the enclosing quotes) 'bfd' <return>
> 9. wait for the prompt. You are now in single user mode .
> </snip>
>
> The problem I'm having is at step 5. I don't get anything saying 'hit the
> space key'? Is this because the RAQ2 is a Mips processor and these
> instructions are for the later X86 architecture common in the Raq3's and
up?
> Is there a way to get into single user mode on a Raq2 or is it a matter of
> getting out the old restore CD?
>
> Thanks for any advice you can give (kicking myself in the @ss).
>
> cya,
> Jay

Hi,

It sounds like you removed the admin user from the "wheel" group - only
members of wheel are allowed to su.  I had to correct this for a client a
few weeks ago, and found that the best way, rather than to take the box down
to single user, was to cheat :-)  :

telnet/ssh as admin, copy the /etc/group file to admin's home directory, and
then correct all the cock-ups on this copy.  Then, create a "mock" PKG.  Sea
rch in the knowledge base for "creating PKGs".  You don't need to go the
whole-hog - just create create a "packing_list", a null RPM (to fool the GUI
into thinking that you are installing something) and an upgrade_me script.
In the upgrade_me script just write a very basic bash shell script, which
would rename your current /etc/group file to /etc/group.old and then rename
your corrected version in admin's home directory to /etc/group.  Just make
double sure before you install it that the paths are all correct :-).  Then,
throw it at the GUI, and you should be sorted.

Cheers,
               Dave Rowlands

Verio UK