mkinitrd unification across distributions
 help / color / mirror / Atom feed
From: Harald Hoyer <harald-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Peter Jones <pjones-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: Karel Zak <kzak-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
	Daniel Drake <dsd-2X9k7bc8m7Mdnm+yROfE0A@public.gmane.org>,
	util-linux-ng-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] switch_root: a better approach to subroots
Date: Thu, 19 Nov 2009 09:19:05 +0100	[thread overview]
Message-ID: <4B04FF79.90406@redhat.com> (raw)
In-Reply-To: <4B045586.1090906-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>

On 11/18/2009 09:13 PM, Peter Jones wrote:
> On 11/18/2009 01:47 PM, Karel Zak wrote:
>>
>>   I think dracut guys should be in CC. Any objection against this change?
>>
>> On Wed, Nov 18, 2009 at 03:33:12PM +0000, Daniel Drake wrote:
>>> This reverts commit a692a8745941a192528c5e2a05de97155ba586f9.
>>> Booting into a system this way just leads to problems because
>>> you cannot remount the root read-only at shutdown (leading to unclean
>>> shutdowns).
>>>
>>> Miklos Szeredi pointed out a trick to turn any directory into a
>>> mount point which avoids this problem. Therefore we can simplify
>>> switch_root again and simply document that its users should set
>>> up the root as a mount point beforehand.
>>> ---
>>>   sys-utils/switch_root.8 |   13 +++++++
>>>   sys-utils/switch_root.c |   81 +++--------------------------------------------
>>>   2 files changed, 18 insertions(+), 76 deletions(-)
>>>
>>> diff --git a/sys-utils/switch_root.8 b/sys-utils/switch_root.8
>>> index 4fdc8e9..b6712ec 100644
>>> --- a/sys-utils/switch_root.8
>>> +++ b/sys-utils/switch_root.8
>>> @@ -32,6 +32,19 @@ show version number and exit
>>>   .B switch_root
>>>   returns 0 on success and 1 on failure.
>>>
>>> +.SH NOTES
>>> +switch_root will fail to function if
>>> +.B newroot
>>> +is not the root of a mount. If you want to switch root into a directory that
>>> +does not meet this requirement then you can first use a bind-mounting trick to
>>> +turn any directory into a mount point:
>>> +.sp
>>> +.nf
>>> +.RS
>>> +mount --bind $DIR $DIR
>>
>>   Cannot we add this functionality directly to the switch_root command?
>>   I mean call:
>>
>>      mount --bind /newroot/subroot /newroot/subroot
>>      mount --move /newroot/subroot /
>>
>>   Now we have:
>>
>>      mount --move newroot /
>>      chroot /newroot/subroot
>
> That certainly seems preferable to reverting the patch, especially if, as
> the original commit log says, some distro (OLPC in this case) is actually
> using this functionality.
>

no objections
--
To unsubscribe from this list: send the line "unsubscribe util-linux-ng" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2009-11-19  8:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20091118153312.16E989D404F@zog.reactivated.net>
     [not found] ` <20091118153312.16E989D404F-k/4jFdqg8LLlyo9zxV8I99HuzzzSOjJt@public.gmane.org>
2009-11-18 18:47   ` [PATCH] switch_root: a better approach to subroots Karel Zak
     [not found]     ` <20091118184706.GB23977-sHeGUpI7y9L/9pzu0YdTqQ@public.gmane.org>
2009-11-18 20:13       ` Peter Jones
     [not found]         ` <4B045586.1090906-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2009-11-19  8:19           ` Harald Hoyer [this message]
2009-11-20 14:05       ` Victor Lowther
2009-11-20 14:30   ` Karel Zak

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=4B04FF79.90406@redhat.com \
    --to=harald-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
    --cc=dsd-2X9k7bc8m7Mdnm+yROfE0A@public.gmane.org \
    --cc=initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=kzak-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=pjones-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=util-linux-ng-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