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
On Wed, 15 Feb 2017 20:38:05 -0700, Leonid Isaev wrote:
>What I usually do, is mkdir /dev/sda1/{arch,foo} and rsync
>kernels/initrds from /dev/sda1 to arch/ and from /dev/sdb1 to foo/.
Hi,
I kept Arch's /boot and will move other Linux /boot to an Arch
directory named /.boot.
A test done with
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
3 matches
Mail list logo