Hi, On Jan 30, 2013, at 10:32, "Eggert, Lars" <lars_at_netapp.com> wrote: > On Jan 29, 2013, at 20:22, Craig Rodrigues <rodrigc_at_crodrigues.org> 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 root file >> system >> is by parsing /etc/fstab, and looking for the "/" mount. >> >> So, if your kernel is located in: >> >> /usr/home/elars/dst/boot/kernel/kernel >> >> Then create a file /usr/home/elars/dst/etc/fstab file with something like: >> >> # Device Mountpoint FSType >> Options Dump Pass >> 10.11.12.13:/usr/home/elars/dst/ / nfs ro 0 0 > > Thanks, will try that! doesn't work. The kernel never leaves the "DHCP/BOOTP timeout for server"-loop unless I hand out a root-path option via DHCP. I tried your tip above, I tried setting ROOTDEVNAME in the kernel, I created a /boot.config with "-r" in it on the NFS root - all to no avail. >> 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 too, but not sure if this works with our custom loader. Doesn't seem to work either. LarsReceived on Wed Jan 30 2013 - 10:18:21 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:34 UTC