All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vladislav Bogdanov <bubble-Awb4OmSD/41iLUuM0BA3LQ@public.gmane.org>
To: Harald Hoyer <harald-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] add fake root support
Date: Wed, 10 Nov 2010 16:54:41 +0200	[thread overview]
Message-ID: <4CDAB231.80903@hoster-ok.com> (raw)
In-Reply-To: <4CDAAA70.1070302-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>

10.11.2010 16:21, Harald Hoyer wrote:
> On 11/01/2010 03:16 PM, Vladislav Bogdanov wrote:
>> 19.10.2010 17:49, Vladislav Bogdanov wrote:
>>> Attached is a patch for "fake" root functionality,
>>> I'm (mostly) duplicating issue's description from my previous e-mail
>>> (for commit message if this is to be pushed):
>>>
>>
>> Sorry for being annoying, but... Any comments?
>>
>> Best,
>> Vladislav
>>
> 
> I like it, but I don't like the parameters...
> 
> Maybe we can express it like this:
> 
> netroot=fake:xxx.yyy.zzz.www:/mnt root=live:blablabla

This can be used not only with nfs I think...
nfs is just one use case which I needed for my project.

And information after fake: should be some-how handled in dracut, but I
currently do not see any use-cases for that. Do you see them? iSCSI? Is
it really needed so early if it is not for root?

And, I'd not mount not-root nfs from within dracut, we need to know
mount point on a real system for that. Additionally, I've already had
much fun with nfs4 and root user access to files. This requires
rpcidmapd, and it has too many dependencies (and properly configured
resolver).

I'd keep it generic, thus making it possible to start network-enabled
node solely from PXE. It is much easier to exploit generic solutions
(IMHO) for own needs.

> 
> and find another name for "fake".. maybe "container"?
Hmmm....
The main idea was to have networking configured without real networked root.
Current dracut policy is to skip networking if no networked root is
configured. That's why I called it 'fake' - I'm cheating with this policy.
I agree that 'fake' is not a best name.
Container... then there should be some contents, but I do not see it...

netroot=force?
networking=force?
Later would require additional efforts, but sounds quite nice for me.

> 
> netroot=container:nfs:xxx.yyy.zzz.www:/mnt root=live:blablabla
> 
> Which reminds me, that we should probably have the possibility to
> concatenate several stages.
> 
> root=nfs:xxx.yyy.zzz.www:/mnt|loop:test.img|live:blablabla

This is quite interesting. But this is from another story.

> 
> comments?

  parent reply	other threads:[~2010-11-10 14:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-19 14:49 [PATCH] add fake root support Vladislav Bogdanov
     [not found] ` <4CBDB007.4090802-Awb4OmSD/41iLUuM0BA3LQ@public.gmane.org>
2010-11-01 14:16   ` Vladislav Bogdanov
     [not found]     ` <4CCECBB0.3030609-Awb4OmSD/41iLUuM0BA3LQ@public.gmane.org>
2010-11-10 14:21       ` Harald Hoyer
     [not found]         ` <4CDAAA70.1070302-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2010-11-10 14:54           ` Vladislav Bogdanov [this message]
2010-11-10 16:09           ` Jon Ander Hernandez
     [not found]             ` <AANLkTim9GEHy0EDBNMS1+fDiZ_UGw6fA3kSMq21qR-Jx-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-11-12  7:54               ` Vladislav Bogdanov

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=4CDAB231.80903@hoster-ok.com \
    --to=bubble-awb4omsd/41iluum0ba3lq@public.gmane.org \
    --cc=harald-H+wXaHxf7aLQT0dZR+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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.