On 08/15/2012 09:30 AM, Christoph Vigano wrote:
I could not fix the systems as I could not get
a "recovery" bash prompt. I had to use a boot live CD to edit the fstab
and then all was well. On all my sysvinit systems a bad mount point
would just give me an error and continue booting.
Wouldn't it have been easier to just start with init=/bin/bash ?
Just asking, as this would have been my first attempt at solving the
problem.
Greetings,
Christoph
maybe, I usually just boot to a rescue cd or usb mount the root
partition and go to work at it.
When I break things or have boot failures I don't know what is wrong
until I look. Some times if you are using jfs on root all that is
needed is an fsck but it won't boot because something is buggered so
init=/bin/bash doesn't work, so I just get the usb drive and plug and play.
I do this so I can invoke the maximum damage to the system under abuse :)
