From: Harald Hoyer <harald-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Wim Muskee <wimmuskee-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: NFS mount problem since 017
Date: Fri, 30 Mar 2012 11:01:03 +0200 [thread overview]
Message-ID: <4F75764F.8040407@redhat.com> (raw)
In-Reply-To: <CAKzfqkeDMpAKarVENVFHddERc0ySn1acnQR=K1wKCDC=N5dGTg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Am 29.03.2012 20:53, schrieb Wim Muskee:
> On Thu, Mar 29, 2012 at 12:39 PM, Harald Hoyer <harald-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> wrote:
>> Am 27.03.2012 20:13, schrieb Wim Muskee:
>>
>> Ah, we now kill rpc.idmapd. So before you do any action, you have to restart
>> rpc.idmapd in the real root.
>
> Any reason the rpc.idmapd is killed now?
> --
> To unsubscribe from this list: send the line "unsubscribe initramfs" in
> the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
ok, just investigated: we kill rcp.idmapd since dracut 0.3.
must be another problem
prev parent reply other threads:[~2012-03-30 9:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-18 9:25 NFS mount problem since 017 Wim Muskee
[not found] ` <CAKzfqkd3hGyqhVvfdSFg7=R595cEjy0gNpnwmBcHQnUXOxbkOA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-03-19 8:23 ` Karel Zak
[not found] ` <20120319082324.GA29521-s5vVilr7EKH/9pzu0YdTqQ@public.gmane.org>
2012-03-27 17:43 ` Wim Muskee
2012-03-27 18:13 ` Wim Muskee
[not found] ` <CAKzfqkcWuySSQRSOdk=Z-UbVieHUEb4aHVs9qro3uw7Q6s-7jg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-03-29 10:39 ` Harald Hoyer
[not found] ` <4F743BF8.9000608-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2012-03-29 18:53 ` Wim Muskee
[not found] ` <CAKzfqkeDMpAKarVENVFHddERc0ySn1acnQR=K1wKCDC=N5dGTg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-03-30 9:01 ` Harald Hoyer [this message]
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=4F75764F.8040407@redhat.com \
--to=harald-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=wimmuskee-Re5JQEeQqe8AvxtiuMwx3w@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