public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rafael Ávila de Espíndola" <rafael.espindola@gmail.com>
To: Denis Vlasenko <vda@ilport.com.ua>
Cc: gentoo-dev@gentoo.org, gentoo-catalyst@gentoo.org,
	linux-kernel@vger.kernel.org
Subject: Re: unmounting a filesystem mounted by /init (initramfs)
Date: Fri, 29 Jul 2005 10:37:09 -0300	[thread overview]
Message-ID: <200507291037.39453.rafael.espindola@gmail.com> (raw)
In-Reply-To: <200507290834.35504.vda@ilport.com.ua>

[-- Attachment #1: Type: text/plain, Size: 867 bytes --]

On Friday 29 July 2005 02:34, Denis Vlasenko wrote:
> "A chroot"? Better provide exact sequence of mounts, chroots which you
> execute. Otherwise people need to guess.
The relevant commands are:

mount -t ext2 /dev/hda1 /memory
mount -t unionfs -o dirs=/memory /union
mount -t squashfs /dev/hda2 /newroot
unionctl /union --add --after 0 --mode ro /newroot
chroot /union /sbin/init

The most promissing Idea I had till now is to move the ext2 mount and the 
unionctl past the point were /sbin/rc runs udevstart. I will try it as soon 
as possible.

> Use lazy umount (umount -l) while fs is still visible
The busybox umount doesn't support lazy unmount :(
Anyway, I don't think that this would work since the unionfs will be using the 
ext2 partition to the very end and there won't be a chance to unmount it.

> vda
Thank you very much,
Rafael

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2005-07-29 13:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-28 22:49 unmounting a filesystem mounted by /init (initramfs) Rafael Espíndola
2005-07-29  5:34 ` Denis Vlasenko
2005-07-29 13:37   ` Rafael Ávila de Espíndola [this message]
2005-07-29 20:24   ` Rafael Ávila de Espíndola

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=200507291037.39453.rafael.espindola@gmail.com \
    --to=rafael.espindola@gmail.com \
    --cc=gentoo-catalyst@gentoo.org \
    --cc=gentoo-dev@gentoo.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vda@ilport.com.ua \
    /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