mkinitrd. (was Re: [RFC] [PATCH] Allow overriding module parameters from kernel command_line)

On Thu, Apr 19, 2007 at 08:47:13AM +1000, Neil Brown wrote: > > Fixed by changing /etc/fstab and rebuilding initrd, but IMO rootfstype= > > should have worked. > > I think these are both issues that should be solved by smarts in the > initrd. This is getting away from the intent of Kyle's

Re: [RFC] [PATCH] Allow overriding module parameters from kernel command_line

On Wednesday April 18, [EMAIL PROTECTED] wrote: > > On Wed, 18 Apr 2007 11:55:52 -0400 Kyle McMartin <[EMAIL PROTECTED]> wrote: > > With the move to initramfs and heavily modular configs, which include > > loading storage drivers from early userspace, it's becoming harder > > to provide users with

Re: [RFC] [PATCH] Allow overriding module parameters from kernel command_line

> On Wed, 18 Apr 2007 11:55:52 -0400 Kyle McMartin <[EMAIL PROTECTED]> wrote: > With the move to initramfs and heavily modular configs, which include > loading storage drivers from early userspace, it's becoming harder > to provide users with a way of overriding module parameters at boot. > > Curr

Re: [RFC] [PATCH] Allow overriding module parameters from kernel command_line

On Wed, 2007-04-18 at 11:55 -0400, Kyle McMartin wrote: > With the move to initramfs and heavily modular configs, which include > loading storage drivers from early userspace, it's becoming harder > to provide users with a way of overriding module parameters at boot. > > Currently, users would hav

[RFC] [PATCH] Allow overriding module parameters from kernel command_line

With the move to initramfs and heavily modular configs, which include loading storage drivers from early userspace, it's becoming harder to provide users with a way of overriding module parameters at boot. Currently, users would have to break into the initramfs, edit the modprobe options, and then