Re: [arch-general] syslinux.cfg

2017-02-16 Thread Leonid Isaev
On Thu, Feb 16, 2017 at 11:20:58AM +0100, Ralf Mardorf wrote: > If I want to maintain the other Linux in a systemd-nspawn container, I > won't be able to upgrade the kernel anymore [1]. Is there a workaround > for this, too? Perhaps I'm just using systemd-nspawn incorrect :D. I > should read more

Re: [arch-general] syslinux.cfg

2017-02-16 Thread Ralf Mardorf
On Wed, 15 Feb 2017 20:38:05 -0700, Leonid Isaev wrote: >Let's assume that you have the following: >* /dev/sda1 -- mounted at /boot when you boot your ArchLinux system >* /dev/sdb1 -- the same for Foo >* syslinux is installed on /dev/sda1 (it is bootable). > >What I usually do, is mkdir

Re: [arch-general] syslinux.cfg

2017-02-15 Thread Leonid Isaev
On Thu, Feb 16, 2017 at 03:09:23AM +0100, Ralf Mardorf wrote: > Hi, > > is the no way to get a menu > > > Arch kernel 1 > Arch Kernel 2 > Foo Kernel 1 > Foo Kernel 2 > > > when using syslinux? > > Or even while booting another Linux requires chainloading, there's a > feature to chose

Re: [arch-general] syslinux.cfg

2017-02-15 Thread David Rosenstrauch
On 02/15/2017 09:09 PM, Ralf Mardorf wrote: Hi, is the no way to get a menu Arch kernel 1 Arch Kernel 2 Foo Kernel 1 Foo Kernel 2 when using syslinux? Or even while booting another Linux requires chainloading, there's a feature to chose between all available kernels of another Linux by