Does rescue mode with an initrd work for you in Slackware64-15.0?
by Richard Cranium from LinuxQuestions.org on (#6ET2D)
Needless to say, I did something very stupid with my root filesystem's /etc/fstab entry; the end result is that filesystem is now read-only on full boot and any attempts to modify that state require writing something into the root filesystem.
OK, no problem; I should be able to modify (I'm using grub.) the command line passed on as boot by adding rescue. That should give me a command-line to mount directories and fix stuff as part of the initrd portion of the boot.
The problem is that I don't really get an interactive shell. I get the message...
Code:/bin/sh: can't access tty; job control turned off...followed by a Code:/ # prompt that accepts no input from the device that I used to interactively modify the grub boot entry to add rescue to the kernel command line.
I fully realize that if there is an underlying problem here that would require some initrd changes to get this to work for later initrd images that it won't help with the problem that I have at the moment. (Yes, I know that I can get a live slack image and use that to fix my problem but where I live now uses ViaSat and going over your data limit puts you back into the 56k modem days.)
EDIT: OTOH, my /boot partition is on a different filesystem than /, so maybe I can fix it if it's a simple case of changing something in the initrd init script.
OK, no problem; I should be able to modify (I'm using grub.) the command line passed on as boot by adding rescue. That should give me a command-line to mount directories and fix stuff as part of the initrd portion of the boot.
The problem is that I don't really get an interactive shell. I get the message...
Code:/bin/sh: can't access tty; job control turned off...followed by a Code:/ # prompt that accepts no input from the device that I used to interactively modify the grub boot entry to add rescue to the kernel command line.
I fully realize that if there is an underlying problem here that would require some initrd changes to get this to work for later initrd images that it won't help with the problem that I have at the moment. (Yes, I know that I can get a live slack image and use that to fix my problem but where I live now uses ViaSat and going over your data limit puts you back into the 56k modem days.)
EDIT: OTOH, my /boot partition is on a different filesystem than /, so maybe I can fix it if it's a simple case of changing something in the initrd init script.