Linux NFS development
 help / color / mirror / Atom feed
From: "Nicholas Lafferty" <nlafferty@pennswoods.net>
To: "Neil Brown" <neilb@cse.unsw.edu.au>
Cc: "nfs" <nfs@lists.sourceforge.net>
Subject: Re: fh_verify
Date: Tue, 3 Sep 2002 13:47:04 -0400	[thread overview]
Message-ID: <006a01c25371$ea977700$9300a8c0@gridlock> (raw)
In-Reply-To: 15732.7439.949607.498380@notabene.cse.unsw.edu.au

I'm trying to track down all of the things that I think could be the
problem. For one, I know that things are not getting mounted right.

the init script passed to the kernel has the following lines of importance:

mount-t nfs -o nolock,ro,vers=2 $SERVER:/      /ro
mount-t nfs -o nolock,ro,vers=2 $SERVER:/home/guest/share      /ro2
mount-t nfs -o nolock,rw,vers=2 $SERVER:/home/guest/$ID      /rw

#then the /dev on the ramdisk is renamed out of the way and a server version
of dev is mounted EXCLUDED

exec /sbin/init '#'

this should allow me to write to my home dir but it says I have a read only
file system. Perhaps a remount option in my fstab to change.



----- Original Message -----
From: "Neil Brown" <neilb@cse.unsw.edu.au>
To: "Nicholas Lafferty" <nlafferty@pennswoods.net>
Cc: "nfs" <nfs@lists.sourceforge.net>
Sent: Monday, September 02, 2002 10:23 PM
Subject: Re: [NFS] fh_verify


> On Monday September 2, nlafferty@pennswoods.net wrote:
> > I have recently set up a lan with three New Internet Computers booting
off
> > the network as outlined in the article (
> > http://www.dnalounge.com/backstage/src/kiosk ) . After many atempts I
have
> > finally gotten ALMOST a booting client.
> > I have been alternating testing with SysVinit and Busybox's init. If I
use
> > the normal init I get errors on the NFS server about fh_verify:
/etc/shadow
> > permission failure. As soon as inittab is read. I get the same errors
when I
> > run sulogin. If I rename the inittab out of the way I can only boot in
> > single mode.
> >
> > If I use busybox it will boot. But I can not start X and I get the same
> > errors.
> >
> > Any clue? Any help would be great.
>
> Sounds like you need the
>    no_root_squash
> in you /etc/exports.  You definately need this for exporting a root
> filesystem.
>
> NeilBrown
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by: OSDN - Tired of that same old
> cell phone?  Get a new here for FREE!
> https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
> _______________________________________________
> NFS maillist  -  NFS@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nfs



-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone?  Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

  reply	other threads:[~2002-09-03 17:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-02 23:38 fh_verify Nicholas Lafferty
2002-09-03  2:23 ` fh_verify Neil Brown
2002-09-03 17:47   ` Nicholas Lafferty [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-09-02 23:25 fh_verify Nicholas Lafferty

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='006a01c25371$ea977700$9300a8c0@gridlock' \
    --to=nlafferty@pennswoods.net \
    --cc=neilb@cse.unsw.edu.au \
    --cc=nfs@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox