From: "James Hayhurst" <herrdoktor@email.com>
To: linux-kernel@vger.kernel.org
Subject: Cannot unmount initrd
Date: Wed, 21 Aug 2002 19:57:30 -0500 [thread overview]
Message-ID: <20020822005730.9319.qmail@email.com> (raw)
I'm making a boot CD and having problems unmounting and freeing the initrd after pivoting to a different root. First off, for some reaosn it seems that /linuxrc is not being executed. Just to test this, I have it as a simple script (with execute permissions) printing something to the screen and it never printed....at boot it just seems to go to /sbin/init on the initrd image. After pivoting to a cramfs root, I cannot unmount /initrd as it says that the device or resource is busy. Checking out /proc, it looks like [keventd], [ksoftirqd_CPU0], [kswapd] and [kupdated] are holding onto open fd from /initrd, namely /initrd/dev/console. Strangely though, some of the fd's they're holding are the "normal" /dev/console.
My /sbin/init on the initrd script looks something like:
#I have the new root mount on /new_root/root.cfs and all directories are set up to pivot
cd /new_root
pivot_root . initrd
export PATH=/bin:/usr/bin:/sbin
echo Done pivoting
umount /initrd/proc
umount /initrd/devfs
umount /initrd
exec chroot . sbin/startup < dev/console > dev/console 2> dev/console
Should i unmount /proc and /devfs before I pivot? Any suggestions would be wonderful!
Cheers,
James
Please CC to me directly if you can, i'm not suscribed to the mailing list, bad me!
--
__________________________________________________________
Sign-up for your own FREE Personalized E-mail at Mail.com
http://www.mail.com/?sr=signup
next reply other threads:[~2002-08-22 0:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-22 0:57 James Hayhurst [this message]
2002-08-22 8:59 ` Cannot unmount initrd Richard Zidlicky
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=20020822005730.9319.qmail@email.com \
--to=herrdoktor@email.com \
--cc=linux-kernel@vger.kernel.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.