You are not logged in.
Pages: 1
Hi all,
I've been using ArchLinux for a few years and I had my first experience today of accidentally nuking a system file. The recovery option was to download an iso from another machine, and then use it to mount my / and change the file I wasted. (pro tip: unlimited is not a valid entry in /etc/security/ulimit.conf!)
This got me thinking that I would feel more comfortable with a Debian-style "rescue" boot menu entry for these sorts of situations. Ideally with a password lock on it. But finding information on this is pretty difficult, does anybody have a link to the relevant docs?
In addition, it would be pretty useful to keep the "last working kernel" lying around as a boot option... just incase. Is that something that can be set up? Again, this is the Debian way and I used it once every few years.
Best regards,
Sam
Offline
You can always install more than one kernel. I would suggest keeping the latest kernel, plus the -lts kernel as a backup. That way, if the new kernel breaks something, you can boot into the other one and fix it. However, in your case this time, having multiple kernels really won't help since you deleted a file. But just in general, I always recommend two kernels installed in case something does break.
Offline
Not an Installation issue, moving to NC...
Offline
You may wish to create a separate entry in your boot menu with "systemd.unit=rescue.target" appended to the kernel command line. You may also find this article of interest to you:
https://freedesktop.org/wiki/Software/s … Debugging/
Regards,
Offline
thanks... I expected that I'd need another entry but the problem I have is that I don't know *where* the boot menu lives. I used to use LILO and GRUB and I don't even know the name of the bootloader that ArchLinux is using, or where to look to find out.
Offline
thanks... I expected that I'd need another entry but the problem I have is that I don't know *where* the boot menu lives. I used to use LILO and GRUB and I don't even know the name of the bootloader that ArchLinux is using, or where to look to find out.
What bootloader did you install when you installed Arch?
Offline
fommil wrote:thanks... I expected that I'd need another entry but the problem I have is that I don't know *where* the boot menu lives. I used to use LILO and GRUB and I don't even know the name of the bootloader that ArchLinux is using, or where to look to find out.
What bootloader did you install when you installed Arch?
If I knew that I'd be able to google it :-D
I'm using UEFI and adding files into /boot/loader/entries doesn't do anything, and there is no prompt on startup... not even to select the LTS linux.
Offline
How did you install Arch?
Offline
How did you install Arch?
I followed the standard installation document. But it was several years ago so I cannot remember any of the detailed choices.
Offline
I suspect you are using systemd-boot and that your /boot/loader/loader.conf has a timeout set to zero.
Additional information is available here:
https://wiki.archlinux.org/index.php/Systemd-boot
Regards,
Offline
Please post the output of these two commands to show your boot config. It sounds likely you are using either the direct boot by UEFI of the kernel or systemd's bootctl. These commands will show the UEFI boot configuration and if bootctl is used the specifics of the boot options will show.
# efibootmgr -v
# bootctl statusSimple and Open
Offline
Pages: 1