From: Paul Sokolovsky <pmiscml@gmail.com>
To: openembedded-devel <openembedded-devel@lists.openembedded.org>
Cc: angstrom-distro-devel@linuxtogo.org
Subject: Re: [Angstrom-devel] [RFC] Get rid of adhoc machine-specific messing with kernel packages
Date: Fri, 29 Dec 2006 03:30:51 +0200 [thread overview]
Message-ID: <1525806921.20061229033051@gmail.com> (raw)
In-Reply-To: <459403F2.4080102@dominion.kabel.utwente.nl>
Hello Koen,
Thursday, December 28, 2006, 7:50:42 PM, you wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> CC: to the OE list
> Paul Sokolovsky schreef:
>> Hello angstrom-distro-devel,
>>
>> Thanks for providing pre-holiday 20061219 snapshots for testing.
>> They don't provide separate zImages, but well, that's ok - they are in
>> the images, after all.
>>
>> Well, not for hx4700, for example. Because:
>>
>> ======== linux-handhelds-2.6.inc =====
>> FILES_kernel-image_hx4700 = ""
>> ALLOW_EMPTY_hx4700 = "1"
>> FILES_kernel-image_htcuniversal = ""
>> ALLOW_EMPTY_htcuniversal = "1"
>> ======================================
>>
>> Oops. Sources of such a special treatment of hx4700 and htcuniversal
>> would be unclear to outsider, but people who deal with (mis)features
>> of "ipaqs" know, that hx4700 has one (sic!, even if the most popular)
>> bootloader which doesn't use zImage in the image, but instead requires
>> adhoc means to install kernel, ditto for Universal, though bootloader
>> is another.
>>
>> So, what is tried here is to "save space". But there're few issues:
> Those lines should go, but not before we have a way to exclude 'kernel-image' from the
> rootfs *and* kernel-module-foo doesn't depend kernel-image anymore.
Well, so am I right with assumption above that the only reason for
that is to "save space"? If yes, then we should fix it the right
place. So, if we want to be able to remove zImage file (not
kernel-image package, actually, as indeed modules depend on it, and do
that rightfully) from rootfs, we should do just that. We already
[have ability to] postprocess rootfs in a number of ways, like: remove
root password, make sure that /sbin/init is a real file, not a link,
make sure a /boot/zImage is a relative symlink. So, in that vein, I've
made a patch, submitted as http://bugs.openembedded.org/show_bug.cgi?id=1719
. Tested. Please review.
> regards,
> Koen
[]
--
Best regards,
Paul mailto:pmiscml@gmail.com
prev parent reply other threads:[~2006-12-29 1:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <53610736.20061228191750@gmail.com>
2006-12-28 17:50 ` [Angstrom-devel] [RFC] Get rid of adhoc machine-specific messing with kernel packages Koen Kooi
2006-12-28 20:32 ` Richard Purdie
2006-12-29 2:05 ` Paul Sokolovsky
2006-12-29 11:34 ` Richard Purdie
2007-01-04 19:03 ` [Angstrom-devel] [RFC] Get rid of adhoc machine-specific messing with [linux-handhelds-2.6] " Paul Sokolovsky
2007-01-04 20:55 ` Richard Purdie
2007-01-04 21:22 ` Koen Kooi
2007-01-04 21:33 ` Richard Purdie
2007-01-04 21:38 ` Paul Sokolovsky
2007-01-05 8:41 ` Marcin Juszkiewicz
2007-01-05 9:15 ` Koen Kooi
2007-01-05 10:15 ` pHilipp Zabel
2007-01-06 10:26 ` Paul Sokolovsky
2006-12-29 1:30 ` Paul Sokolovsky [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=1525806921.20061229033051@gmail.com \
--to=pmiscml@gmail.com \
--cc=angstrom-distro-devel@linuxtogo.org \
--cc=openembedded-devel@lists.openembedded.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.