WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: NFS Oddity  (Read 1736 times)

Offline CentralWare

  • Retired Admins
  • Hero Member
  • *****
  • Posts: 765
NFS Oddity
« on: November 05, 2015, 02:03:10 PM »
I'm PXE booting TCL 6.1 (x86) and using NFS (unfs3)
Manually mounting the nfs share works without a hitch (save for adding -o nolock of course) and I have r/w access.

Code: [Select]
append initrd=files/tc/6/boot/core.gz nfsmount=192.168.11.1:/nfs/_default_ tce=nfs/tce home=nfs/home opt=nfs/opt

The TCE directory is automatically created and populated as expected.
The OPT and HOME directories error out during boot (invalid) and are ignored.
I've tried /mnt/nfs/opt and nfs/opt to no avail.  Any ideas (this used to work in TCL4, so I have to assume I'm not remembering something or something has since changed.)

Thanks!

~TJ~

Offline gerald_clark

  • TinyCore Moderator
  • Hero Member
  • *****
  • Posts: 4254
Re: NFS Oddity
« Reply #1 on: November 05, 2015, 02:19:18 PM »
home=nfs opt=nfs
The home and opt bootcodes cannot include a directory.

Offline CentralWare

  • Retired Admins
  • Hero Member
  • *****
  • Posts: 765
Re: NFS Oddity
« Reply #2 on: November 05, 2015, 02:25:25 PM »
I suppose it HAS been a while! :)
(All of my prior TFTP settings/files are archived from my last run with this.)
Thanks for the update; I suppose what threw me is that tce=nfs/path/to/tce worked without a hitch and thus the same was assumed for the others.

Cheers!

Offline gerald_clark

  • TinyCore Moderator
  • Hero Member
  • *****
  • Posts: 4254
Re: NFS Oddity
« Reply #3 on: November 05, 2015, 02:33:35 PM »
It has nothing to do with nfs.  Home and opt just cannot specify a directory.

Offline CentralWare

  • Retired Admins
  • Hero Member
  • *****
  • Posts: 765
Re: NFS Oddity
« Reply #4 on: November 05, 2015, 02:53:19 PM »
Quote
It has nothing to do with nfs.  Home and opt just cannot specify a directory.
We'll see about that! ;)

Thanks again and take care!