From: Oleg Verych <olecom@flower.upol.cz>
To: linux-kernel@vger.kernel.org
Subject: Re: [KBUILD] I don't want initramfs in 2.6.19.1 but usr/ is still processed
Date: Wed, 24 Jan 2007 01:07:21 +0000 (UTC) [thread overview]
Message-ID: <slrnerdcqe.e7s.olecom@flower.upol.cz> (raw)
In-Reply-To: 20070103111936.GB18441@DervishD
On 2007-01-03, DervishD wrote:
>
> Hi all :)
Hallo!
> I've noticed that, even if I say NO to initramfs (and even ramdisk
> support), the make process wants to GEN usr/initramfs_data.cpio.gz by
> running the scripts/gen_initramfs_list.sh script.
>
> Why is that script run no matter the initramfs support? Looks like
> it only depends on the contents of CONFIG_INITRAMFS_SOURCE :?
I think reading Documentation/filesystems/ramfs-rootfs-initramfs.txt
will answer your question.
> Thanks in advance :)
>
> RaЗl NЗЯez de Arenas Coronado
>
> --
> Linux Registered User 88736 | http://www.dervishd.net
> It's my PC and I'll cry if I want to... RAmen!
____
prev parent reply other threads:[~2007-01-24 1:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-03 11:19 [KBUILD] I don't want initramfs in 2.6.19.1 but usr/ is still processed DervishD
2007-01-24 1:07 ` Oleg Verych [this message]
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=slrnerdcqe.e7s.olecom@flower.upol.cz \
--to=olecom@flower.upol.cz \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox