Re: [PATCH][retry-2] init: Introduce rootdir bootparm to select which dir to sys_chroot

Arjan van de Ven wrote: > to be honest, this is something that really should be done in the > initramfs image; we should strive to keep the more complex bootup > scenarios there and not inside the kernel bootup code... Agreed, but this is neither complex nor is it a scenario. This is a shortcut.

Re: [PATCH][retry-2] init: Introduce rootdir bootparm to select which dir to sys_chroot

H. Peter Anvin wrote: > a. For as long as we keep throwing more crap into the kernel, kinit will > not get merged, because it "provides no new functionality." I'm not really familiar with kinit, but it sounds unfair to hinder new features because it would reduce the usefulness of another

Re: [PATCH][retry-2] init: Introduce rootdir bootparm to select which dir to sys_chroot

On Sun, 18 Nov 2007 20:09:19 +0300 Al Boldi <[EMAIL PROTECTED]> wrote: > > Second try; this time with a doc-update, and the ability to remount > normally. Hi, to be honest, this is something that really should be done in the initramfs image; we should strive to keep the more complex bootup

Re: [PATCH][retry-2] init: Introduce rootdir bootparm to select which dir to sys_chroot

Bodo Eggert wrote: On Sun, 18 Nov 2007, H. Peter Anvin wrote: Bodo Eggert wrote: 1) This is useful for booting a rescue or test system, too. In those cases, you might want to have the old root moved somewhere. (Always "$rootdir/oldroot"? Additional parameter? I'm not sure ...) Again,

Re: [PATCH][retry-2] init: Introduce rootdir bootparm to select which dir to sys_chroot

On Sun, 18 Nov 2007, H. Peter Anvin wrote: > Bodo Eggert wrote: >> 1) This is useful for booting a rescue or test system, too. In those cases, >>you might want to have the old root moved somewhere. >>(Always "$rootdir/oldroot"? Additional parameter? I'm not sure ...) >> > > Again, this

Re: [PATCH][retry-2] init: Introduce rootdir bootparm to select which dir to sys_chroot

Bodo Eggert wrote: 1) This is useful for booting a rescue or test system, too. In those cases, you might want to have the old root moved somewhere. (Always "$rootdir/oldroot"? Additional parameter? I'm not sure ...) Again, this is a good example of why this really shouldn't be

Re: [PATCH][retry-2] init: Introduce rootdir bootparm to select which dir to sys_chroot

Al Boldi <[EMAIL PROTECTED]> wrote: > Second try; this time with a doc-update, and the ability to remount normally. > > Tested against 2.6.23. > > --- > > This patch introduces a rootdir kernel boot parameter, which specifies the > path to the kernel sys_chroot boot dir. > > This is useful

[PATCH][retry-2] init: Introduce rootdir bootparm to select which dir to sys_chroot

Second try; this time with a doc-update, and the ability to remount normally. Tested against 2.6.23. --- This patch introduces a rootdir kernel boot parameter, which specifies the path to the kernel sys_chroot boot dir. This is useful for systems that have more than one distribution

[PATCH][retry-2] init: Introduce rootdir bootparm to select which dir to sys_chroot

Second try; this time with a doc-update, and the ability to remount normally. Tested against 2.6.23. --- This patch introduces a rootdir kernel boot parameter, which specifies the path to the kernel sys_chroot boot dir. This is useful for systems that have more than one distribution

Re: [PATCH][retry-2] init: Introduce rootdir bootparm to select which dir to sys_chroot

Al Boldi [EMAIL PROTECTED] wrote: Second try; this time with a doc-update, and the ability to remount normally. Tested against 2.6.23. --- This patch introduces a rootdir kernel boot parameter, which specifies the path to the kernel sys_chroot boot dir. This is useful for systems

Re: [PATCH][retry-2] init: Introduce rootdir bootparm to select which dir to sys_chroot

Bodo Eggert wrote: 1) This is useful for booting a rescue or test system, too. In those cases, you might want to have the old root moved somewhere. (Always $rootdir/oldroot? Additional parameter? I'm not sure ...) Again, this is a good example of why this really shouldn't be additional

Re: [PATCH][retry-2] init: Introduce rootdir bootparm to select which dir to sys_chroot

On Sun, 18 Nov 2007, H. Peter Anvin wrote: Bodo Eggert wrote: 1) This is useful for booting a rescue or test system, too. In those cases, you might want to have the old root moved somewhere. (Always $rootdir/oldroot? Additional parameter? I'm not sure ...) Again, this is a good

Re: [PATCH][retry-2] init: Introduce rootdir bootparm to select which dir to sys_chroot

Bodo Eggert wrote: On Sun, 18 Nov 2007, H. Peter Anvin wrote: Bodo Eggert wrote: 1) This is useful for booting a rescue or test system, too. In those cases, you might want to have the old root moved somewhere. (Always $rootdir/oldroot? Additional parameter? I'm not sure ...) Again,

Re: [PATCH][retry-2] init: Introduce rootdir bootparm to select which dir to sys_chroot

On Sun, 18 Nov 2007 20:09:19 +0300 Al Boldi [EMAIL PROTECTED] wrote: Second try; this time with a doc-update, and the ability to remount normally. Hi, to be honest, this is something that really should be done in the initramfs image; we should strive to keep the more complex bootup

Re: [PATCH][retry-2] init: Introduce rootdir bootparm to select which dir to sys_chroot

H. Peter Anvin wrote: a. For as long as we keep throwing more crap into the kernel, kinit will not get merged, because it provides no new functionality. I'm not really familiar with kinit, but it sounds unfair to hinder new features because it would reduce the usefulness of another project.

Re: [PATCH][retry-2] init: Introduce rootdir bootparm to select which dir to sys_chroot

Arjan van de Ven wrote: to be honest, this is something that really should be done in the initramfs image; we should strive to keep the more complex bootup scenarios there and not inside the kernel bootup code... Agreed, but this is neither complex nor is it a scenario. This is a shortcut.