mkinitrd unification across distributions
 help / color / mirror / Atom feed
From: daniel-2N1FInP7wozQT0dZR+AlfA@public.gmane.org
To: "initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: Dracut NFS root rw before pivot but ro after pivot
Date: Thu, 07 Oct 2010 12:29:35 +1100	[thread overview]
Message-ID: <20101007122935.19334qntub6vdeo0@webmail.zoltak.com> (raw)
In-Reply-To: <20101005174817.98833aq1pzqn2cds-2RFepEojUI3Y3UUic/vCjNBPR1lH4CV8@public.gmane.org>

Hi Guys,

After reviewing this I found my observations were incorrect.

I have since tried NFSv4 with the same result. I'm now back using NFSv3.

I am booting to pre-pivot rdbreak=pre-pivot.

If I cd /sysroot/tmp (as I did previously) and ../bin/touch test the  
test file is created however the permissions are nobody:nobody:

-rw---- 1 nobody nobody 0 Oct    7 11:47 test

If I try the same in /sysroot i.e. ./bin/touch test I then get:  
Permission denied

For some reason the NFS is seeing the root UID.

The mount options are  
10.197.170.5:/vol/filerboot/linux/images/live-mon-test /sysroot -o  
rw,fg,timeo=6000,retrans=2,rsize=32768,wsize=32768,hard,nointr,noacl,tcp,nfsver=3,nolock,sec=sys

If I chroot into /sysroot and do id it returns with:
uid=0(root) gid=0(root) groups=0(root)

however files get created with the nobody attribute in /tmp?

rpcbind appears to be running as the root user.

When I try to start services such as rpc.statd within the chroot I  
get: superuser access required.

Any ideas?




  parent reply	other threads:[~2010-10-07  1:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-05  1:42 Dracut NFS root rw before pivot but ro after pivot daniel-2N1FInP7wozQT0dZR+AlfA
     [not found] ` <20101005124250.12811x7b1hr8g23k-2RFepEojUI3Y3UUic/vCjNBPR1lH4CV8@public.gmane.org>
2010-10-05  5:52   ` daniel-2N1FInP7wozQT0dZR+AlfA
     [not found]     ` <20101005165245.12962kslvxq6cmyo-2RFepEojUI3Y3UUic/vCjNBPR1lH4CV8@public.gmane.org>
2010-10-05  6:48       ` daniel-2N1FInP7wozQT0dZR+AlfA
     [not found]         ` <20101005174817.98833aq1pzqn2cds-2RFepEojUI3Y3UUic/vCjNBPR1lH4CV8@public.gmane.org>
2010-10-07  1:29           ` daniel-2N1FInP7wozQT0dZR+AlfA [this message]
     [not found]             ` <20101007122935.19334qntub6vdeo0-2RFepEojUI3Y3UUic/vCjNBPR1lH4CV8@public.gmane.org>
2010-10-07  7:24               ` Luca Berra
     [not found]                 ` <20101007072427.GA30734-hdG+WfPrfN2JmafXlB/IVQ@public.gmane.org>
2010-10-07 23:07                   ` daniel-2N1FInP7wozQT0dZR+AlfA

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=20101007122935.19334qntub6vdeo0@webmail.zoltak.com \
    --to=daniel-2n1finp7wozqt0dzr+alfa@public.gmane.org \
    --cc=initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    /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