On Fri, May 11, 2001 at 07:38:33PM +0100, Russell King wrote:
>
> As long as you can get the root server IP and path from the DHCP client,
I can do that. :-)
> then you mount it in a directory, and use pivot_root() to change to
> that directory.
Cool.
> See the "Changing the root device" of
On Fri, May 11, 2001 at 11:13:00AM -0700, Brian J. Murrell wrote:
> I should have given more information though. My goal is actually to
> NFSRoot the machine being booted. I could not determine a way to get
> the "root path" attribute given by the dhcp/bootp server from
> userspace back to the k
On Fri, 11 May 2001, Brian J. Murrell wrote:
> If there were a way to tell the kernel, from userspace, for
> change_root()/mount_root() where the nfsroot path was, yes. I have
> been hunting through all of the (nfs) root mount code and I don't see
> it. It looks like it can be set either on the
On Thu, May 10, 2001 at 06:00:39PM +0100, Russell King wrote:
>
> Hmm, if you've got userspace up and running, and loaded kernel
> modules using insmod, then what's wrong about running a dhcp,
> bootp or rarp client from userspace?
In theory, and for just ip configuration, nothing.
I should hav
On Thu, May 10, 2001 at 09:49:53AM -0700, Brian J. Murrell wrote:
> Of course, this elminates the need to build kernels with lots of
> statically linked ethernet drivers or building lots of kernels with
> specific drivers statically linked in.
>
> My hope is that this is seen as a good idea (and
Please CC me on any responses as I don't read the kernel-list in my
inbox. Thanx.
I am looking for comments on the attached patch. It's purpose is to
allow IP AutoConfig to happen additionally after the loading of an
initial ramdisk.
This allows one to use a "generic all-purpose" built kernel
6 matches
Mail list logo
