On Thu, Jun 6, 2013 at 9:54 AM, Ian Lepore wrote:
> Well, I started out just testing Lars' patch (it works) but that
> inspired me to pick up the work I toyed with months ago in this area, to
> try to get BOOTP_NFSROOT to respect other root-path options such as
> setting vfs.root.mountfrom in the
On Sun, 2013-06-02 at 19:57 -0400, Rick Macklem wrote:
> Ian Lepore wrote:
> > On Sat, 2013-06-01 at 20:28 -0400, Rick Macklem wrote:
> > > Lars Eggert wrote:
> > > > Hi,
> > > >
> > > > to conclude this thread, the patch below allows one to specify an
> > > > nfs
> > > > rootfs via the ROOTDEVNAME
On Mon, 2013-06-03 at 00:06 -0700, Craig Rodrigues wrote:
> On Tue, May 28, 2013 at 8:13 AM, Eggert, Lars wrote:
>
> > Hi,
> >
> > to conclude this thread, the patch below allows one to specify an nfs
> > rootfs via the ROOTDEVNAME kernel option, which will be mounted when BOOTP
> > does not retu
On Mon, 3 Jun 2013 00:06:44 -0700
Craig Rodrigues wrote:
> On Tue, May 28, 2013 at 8:13 AM, Eggert, Lars wrote:
>
> > Hi,
> >
> > to conclude this thread, the patch below allows one to specify an nfs
> > rootfs via the ROOTDEVNAME kernel option, which will be mounted when BOOTP
> > does not ret
On Tue, May 28, 2013 at 8:13 AM, Eggert, Lars wrote:
> Hi,
>
> to conclude this thread, the patch below allows one to specify an nfs
> rootfs via the ROOTDEVNAME kernel option, which will be mounted when BOOTP
> does not return a root-path option.
>
> Lars
>
>
> diff --git a/sys/nfs/bootp_subr.c
Hi,
On Jun 3, 2013, at 1:57, Rick Macklem wrote:
> Cool. Thanks. Would you like to review and/or test the above?
it'd be great if folks would test this a bit. It certainly works for me, but I
can't say that I have done a very thorough testing.
> I'll be happy to commit it if Lars doesn't have
Ian Lepore wrote:
> On Sat, 2013-06-01 at 20:28 -0400, Rick Macklem wrote:
> > Lars Eggert wrote:
> > > Hi,
> > >
> > > to conclude this thread, the patch below allows one to specify an
> > > nfs
> > > rootfs via the ROOTDEVNAME kernel option, which will be mounted
> > > when
> > > BOOTP does not r
On Sat, 2013-06-01 at 20:28 -0400, Rick Macklem wrote:
> Lars Eggert wrote:
> > Hi,
> >
> > to conclude this thread, the patch below allows one to specify an nfs
> > rootfs via the ROOTDEVNAME kernel option, which will be mounted when
> > BOOTP does not return a root-path option.
> >
> > Lars
> >
Lars Eggert wrote:
> Hi,
>
> to conclude this thread, the patch below allows one to specify an nfs
> rootfs via the ROOTDEVNAME kernel option, which will be mounted when
> BOOTP does not return a root-path option.
>
> Lars
>
My only concern with this (mainly because I don't understand the rules
Hi,
to conclude this thread, the patch below allows one to specify an nfs rootfs
via the ROOTDEVNAME kernel option, which will be mounted when BOOTP does not
return a root-path option.
Lars
diff --git a/sys/nfs/bootp_subr.c b/sys/nfs/bootp_subr.c
index 2c57a91..972fb12 100644
--- a/sys/nfs/bo
Lars Eggert wrote:
> Hi,
>
> On Jan 30, 2013, at 22:43, Craig Rodrigues
> wrote:
> > What you need to do is, before the FreeBSD kernel boots, your
> > loader needs to export some environment variables. This will trigger
> > the various behaviors in the FreeBSD mount code.
>
> the loader can expo
On Jan 31, 2013, at 15:54, Daniel Braniss wrote:
> a shot in the dark, but is /usr/home/elars/dst properly exported?
Yep, the NFS mount works fine when I use BOOTP with a root-path option
Lars
___
freebsd-current@freebsd.org mailing list
http://lists.f
> On Jan 31, 2013, at 12:53, Andre Oppermann
> wrote:
> > The interface doesn't have a name during loader stage. The kernel
> > finds the interface to use based on the MAC address. You should
> > set boot.netif.hwaddr as well in the kernel environment.
>
> Done, no change. Here is what's in my
On Jan 31, 2013, at 12:53, Andre Oppermann
wrote:
> The interface doesn't have a name during loader stage. The kernel
> finds the interface to use based on the MAC address. You should
> set boot.netif.hwaddr as well in the kernel environment.
Done, no change. Here is what's in my loader enviro
On Jan 31, 2013, at 12:45, Andreas Nilsson
wrote:
> Just a shot in the dark, did you actually tell it to do the root mount ro,
> or try with the nfs share as rw?
ro
Lars
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/lis
On 31.01.2013 12:27, Eggert, Lars wrote:
Hi,
On Jan 30, 2013, at 22:43, Craig Rodrigues wrote:
What you need to do is, before the FreeBSD kernel boots, your
loader needs to export some environment variables. This will trigger
the various behaviors in the FreeBSD mount code.
the loader can e
Done. I also ripped out all the BOOTP* options from the kernel.
>
> However, this still fails:
>
> Trying to mount root from nfs:10.11.12.13:/usr/home/elars/dst []...
> mountroot: waiting for device 10.11.12.13:/usr/home/elars/dst ...
> Mounting from nfs:10.11.12.13:/usr/home/elars/dst failed with
Hi,
On Jan 30, 2013, at 22:43, Craig Rodrigues wrote:
> What you need to do is, before the FreeBSD kernel boots, your
> loader needs to export some environment variables. This will trigger
> the various behaviors in the FreeBSD mount code.
the loader can export some environment variables (this
On 1/30/13 1:32 AM, Eggert, Lars wrote:
Hi,
On Jan 29, 2013, at 20:22, Craig Rodrigues wrote:
Alternatively, if you don't want to create an /etc/fstab file, then
you could put something like this in your loader.conf file:
vfs.root.mountfrom=nfs:10.11.12.13:/usr/home/elars/dst
Will try that
On Wed, Jan 30, 2013 at 1:32 AM, Eggert, Lars wrote:
> Hi,
>
> On Jan 29, 2013, at 20:22, Craig Rodrigues wrote:
>
>
> TFTP is not involved. The kernel gets booted by our custom loader (over
> HTTP) and the root FS is supposed to be mounted over NFS.
> > If through your setup you have already ma
Lars Eggert wrote:
> Hi,
>
> On Jan 29, 2013, at 20:22, Craig Rodrigues
> wrote:
> > What kind of architecture are you trying to do this on? Is this
> > i386/amd64 or something else?
>
> amd64
>
> > I am not familiar with netboot compared to
> > PXE. Is TFTP involved at all with netboot?
>
>
On Wed, 2013-01-30 at 09:32 +, Eggert, Lars wrote:
> Hi,
>
> On Jan 29, 2013, at 20:22, Craig Rodrigues wrote:
> > What kind of architecture are you trying to do this on? Is this
> > i386/amd64 or something else?
>
> amd64
>
> > I am not familiar with netboot compared to
> > PXE. Is TFTP
Hi,
On Jan 30, 2013, at 10:32, "Eggert, Lars" wrote:
> On Jan 29, 2013, at 20:22, Craig Rodrigues wrote:
>> In src/sys/boot/common/boot.c which is part of the loader (not the kernel),
>> if you look in the getrootmount() function,
>> you will see that the loader will try to figure out where the
Hi,
On Jan 29, 2013, at 20:22, Craig Rodrigues wrote:
> What kind of architecture are you trying to do this on? Is this
> i386/amd64 or something else?
amd64
> I am not familiar with netboot compared to
> PXE. Is TFTP involved at all with netboot?
TFTP is not involved. The kernel gets boote
On Tue, Jan 29, 2013 at 1:17 AM, Eggert, Lars wrote:
>
> On Jan 29, 2013, at 10:13, Lars Eggert
> wrote:
> > On Jan 29, 2013, at 9:34, Craig Rodrigues
wrote:
> > I had read both before, and they're very useful documents.
Unfortunately, they don't fully apply to my case, since I'm not PXE-bootin
On Tue, 2013-01-29 at 09:17 +, Eggert, Lars wrote:
> On Jan 29, 2013, at 10:13, Lars Eggert
> wrote:
> > On Jan 29, 2013, at 9:34, Craig Rodrigues wrote:
> >> I recommend that you do not use ROOTDEVNAME, and instead
> >> you should follow the instructions which I wrote and contributed to the
On Jan 29, 2013, at 10:13, Lars Eggert
wrote:
> On Jan 29, 2013, at 9:34, Craig Rodrigues wrote:
>> I recommend that you do not use ROOTDEVNAME, and instead
>> you should follow the instructions which I wrote and contributed to the
>> FreeBSD handbook:
>>
>> "PXE Booting with an NFS Root File S
Hi,
On Jan 29, 2013, at 9:34, Craig Rodrigues wrote:
> I recommend that you do not use ROOTDEVNAME, and instead
> you should follow the instructions which I wrote and contributed to the
> FreeBSD handbook:
>
> "PXE Booting with an NFS Root File System"
>
> http://www.freebsd.org/doc/en_US.ISO88
On Mon, Jan 28, 2013 at 7:13 AM, Eggert, Lars wrote:
> Hi,
>
> I'm trying to netboot a system where the root device is specified in the
> kernel via ROOTDEVNAME:
>
>
Lars,
I recommend that you do not use ROOTDEVNAME, and instead
you should follow the instructions which I wrote and contributed to
Lars Eggert wrote:
> Hi,
>
> I'm trying to netboot a system where the root device is specified in
> the kernel via ROOTDEVNAME:
>
> options BOOTP
> options BOOTP_NFSROOT
> options BOOTP_NFSV3
> options BOOTP_COMPAT
> options BOOTP_WIRED_TO=em4
> options ROOTDEVNAME=\"nfs:10.11.12.13:/usr/home/ela
Hi,
On Jan 28, 2013, at 16:23, Ian Lepore wrote:
> Remove the BOOTP_NFSROOT option, it tells the bootp/dhcp code to keep
> querying the server until a root path is delivered. Without it, the
> ROOTDEVNAME option should get used (and I think even override a path
> from the server, if it delivers
On Mon, 2013-01-28 at 15:13 +, Eggert, Lars wrote:
> Hi,
>
> I'm trying to netboot a system where the root device is specified in the
> kernel via ROOTDEVNAME:
>
> options BOOTP
> options BOOTP_NFSROOT
> options BOOTP_NFSV3
> options BOOTP_COMPAT
> options
32 matches
Mail list logo
