From: Arkadiusz Miskiewicz <arekm@pld-linux.org>
To: viro@parcelfarce.linux.theplanet.co.uk
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] initrd with devfs enabled (Re: initrd and 2.6.0-test8)
Date: Sat, 18 Oct 2003 23:56:04 +0200 [thread overview]
Message-ID: <200310182356.04346.arekm@pld-linux.org> (raw)
In-Reply-To: <20031018194148.GE7665@parcelfarce.linux.theplanet.co.uk>
On Saturday 18 of October 2003 21:41, viro@parcelfarce.linux.theplanet.co.uk
wrote:
> OK, that should do it - the problems happened if you had devfs
> enabled; in that case late-boot code does temporary mount of devfs over
> rootfs /dev, which made /dev/initrd inaccessible. For setups without
> devfs that didn't happen.
>
> Fix is trivial - put the file in question outside of /dev; IOW,
> we simply replace "/dev/initrd" with "/initrd.image" in init/*. It works
> here; please check if it fixes all initrd problems on your boxen.
Works fine for me.
btw. is it possible to do not use initrd with some fs and instead use external
initramfs image?
I've tried to create initramfs image with unpacking initrd image, mounting it
over loop and creating cpio archive from that (find . | cpio -o -c >
../x.cpio), gzipping that cpio and placeing it instead of old initrd at
/boot/initrd + lilo reload.
It doesn't work that way unfortunately (test8 with your patch).
--
Arkadiusz Miśkiewicz CS at FoE, Wroclaw University of Technology
arekm.pld-linux.org AM2-6BONE, 1024/3DB19BBD, arekm(at)ircnet, PLD/Linux
next prev parent reply other threads:[~2003-10-18 22:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-18 16:27 initrd and 2.6.0-test8 Walt H
2003-10-18 17:52 ` viro
2003-10-18 18:22 ` viro
2003-10-18 18:33 ` Christophe Saout
2003-10-18 19:41 ` [PATCH] initrd with devfs enabled (Re: initrd and 2.6.0-test8) viro
2003-10-18 21:56 ` Arkadiusz Miskiewicz [this message]
2003-10-18 22:11 ` viro
2003-10-18 22:46 ` Arkadiusz Miskiewicz
2003-10-18 23:07 ` Valdis.Kletnieks
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=200310182356.04346.arekm@pld-linux.org \
--to=arekm@pld-linux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@parcelfarce.linux.theplanet.co.uk \
/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