You are not logged in.
So, when I installed Arch, it put the vmlinuz-linux and initramfs-linux.img in to /boot. I'm afraid that when I install another distro, it will overwrite these. I'm afraid that if I make /boot/arch/ and put them in there, and change the arch.conf that systemd-boot uses to boot arch, that when pacman needs to rebuild the image it will just put it back in to /boot since pacman doesn't know I moved it. How do I go about moving these 2 files in to /boot/arch and setting up my mkinitcpio and pacman to know I moved them so when they have to update them, they know where to go? This is not an XY problem, I want to have a debian based distro on my laptop as well, and I want to make another Arch install to use with xen as my dom0.
Offline
I see I can do mkinitcpio -p linux -g /boot/*customLinuxName*.img, so that's fine. I need to figure out how to deal with the vmlinuz-linux file now.
Offline
/etc/mkinitcpio.d
Offline
Before you go crazy, see what the debian kernel is named. I don't recall ever encountering another distro that named its kernel 'vmlinuz-linux'. A cursory investigation indicates that debian uses the scheme 'linux-<version>-<architecture>' for example.
But whether the Constitution really be one thing, or another, this much is certain - that it has either authorized such a government as we have had, or has been powerless to prevent it. In either case, it is unfit to exist.
-Lysander Spooner
Offline
I configure my boot{loader,manager}s to boot /vmlinuz & /initrd.img in my Debian system (this is a symlink to the current kernel image and thus never need to be changed, just like the Arch kernal image nomenclature).
Jin, Jîyan, Azadî
Offline