On 24/11/05, Vijairaj <[EMAIL PROTECTED]> wrote:
> If you append "init=/bin/bash" to the kernel command line, you will
> land up in a bash shell, from where the root password can be reset.

This leads to an open question.

You have lost the root password of a given server. Unfortunately:

1. You have a password (the same password that you lost) set in your
lilo.conf, and the "restrict" keyword too.
2. You have set the BIOS to boot from HDD first and set a password
there (again, the one that you lost).
3. Access to the box is difficult or impossible; say it is in a
colocation center on the other side of the globe. The best you can
have is the colo support staff rebooting the box.
4. Reinstalling is not an option - you have several man-years worth of
data on the box, which you have to preserve. Your business cannot
survive a downtime of more than 15 minutes, say. At the moment, the
box is running - thank god for that! :)

On the plus side, you have a serial console and the BIOS also
understands that (ie, you can access the BIOS in the serial console).

What do you do?? And further, what steps would you have taken
beforehand to prevent such a situation from happening? Assume all the
above measures were required for some kind of compliance.

Binand

PS: If I were running the said business, I'd never allow such a big
single point of failure - but that's neither here nor there :)


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id865&op=click
_______________________________________________
linux-india-help mailing list
linux-india-help@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-india-help

Reply via email to