Date: Wed, 30 Jan 2013 09:32:25 +0000 From: "Eggert, Lars" <lars@netapp.com> To: Craig Rodrigues <rodrigc@crodrigues.org> Cc: "freebsd-current@freebsd.org" <freebsd-current@freebsd.org> Subject: Re: mounting root from NFS via ROOTDEVNAME Message-ID: <D4D47BCFFE5A004F95D707546AC0D7E91F69BF73@SACEXCMBX01-PRD.hq.netapp.com> In-Reply-To: <CAG=rPVezTjcTp_AXsOMWYCSM1_xFJDvmUwdguHdZBABanGGrxw@mail.gmail.com> References: <D4D47BCFFE5A004F95D707546AC0D7E91F671642@SACEXCMBX01-PRD.hq.netapp.com> <CAG=rPVergKVKUO=VySvM65WPJO_Od1tkWvx45tM_sEyO65mwUg@mail.gmail.com> <19F92E0C-F004-4F16-A5FC-A10DF84BDCCF@netapp.com> <D4D47BCFFE5A004F95D707546AC0D7E91F674CDE@SACEXCMBX01-PRD.hq.netapp.com> <CAG=rPVezTjcTp_AXsOMWYCSM1_xFJDvmUwdguHdZBABanGGrxw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, On Jan 29, 2013, at 20:22, Craig Rodrigues <rodrigc@crodrigues.org> 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 booted by our custom loader (over HTT= P) and the root FS is supposed to be mounted over NFS. > What does your dhcpd configuration file look like? Completely standard, with the addition of a "root-path" option. (Which I wo= uld like to get rid of by setting ROOTDEVNAME in the kernel.) > Also, are you using the FreeBSD loader, or something else? What kinds of > customizations have you done on the loader? Custom loader.=20 > If through your setup you have already managed to load the kernel over > the network, then a lot of the hard work has been done. Telling the kern= el > where the root file system is located becomes the next tricky part. Right, that's the step I am struggeling with.=20 > 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 root file > system > is by parsing /etc/fstab, and looking for the "/" mount. >=20 > So, if your kernel is located in: >=20 > /usr/home/elars/dst/boot/kernel/kernel >=20 > Then create a file /usr/home/elars/dst/etc/fstab file with something like= : >=20 > # Device Mountpoint FSType > Options Dump Pass > 10.11.12.13:/usr/home/elars/dst/ / nfs ro 0 = 0 Thanks, will try that! > Alternatively, if you don't want to create an /etc/fstab file, then > you could put something like this in your loader.conf file: >=20 > vfs.root.mountfrom=3Dnfs:10.11.12.13:/usr/home/elars/dst Will try that too, but not sure if this works with our custom loader. Lars >=20 > If you can get this to work without introducing new kernel options, > that would be ideal, because the kernel options you are > enabling are triggering behaviors. >=20 > -- > Craig Rodrigues > rodrigc@crodrigues.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?D4D47BCFFE5A004F95D707546AC0D7E91F69BF73>