From: Paul Sokolovsky <pmiscml@gmail.com>
To: Rod Whitby <rod@whitby.id.au>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: pfalcon: revert r5dc6982e... vfat nls modules are not for task-base-kernel26
Date: Tue, 18 Dec 2007 02:50:52 +0200 [thread overview]
Message-ID: <1672988162.20071218025052@gmail.com> (raw)
In-Reply-To: <47671326.3090300@whitby.id.au>
Hello Rod,
Tuesday, December 18, 2007, 2:24:06 AM, you wrote:
> <CIA-34> pfalcon org.oe.dev * r5dc6982e... / (1
> packages/tasks/task-base.bb):
> <CIA-34> task-base: Add NLS modules for VFAT support.
> <CIA-34> * Add to task-base-kernel26, as vfat is pretty basic feature.
> <CIA-34> Worth refactoring to vfat feature still, I guess.
> You guessed right.
> kernel26 is not a kitchen sink where you can just add vfat-related nls
> modules that are not strictly required for booting a 2.6 kernel.
As you perfectly know, defining what is strictly required is yet
long task to do for OE and specific machine in it. Whereas Angstrom
RCs are something to do right now.
> Your addition has just *bloated* the rootfs for *every* 2.6 machine,
No, it did not. It just added 10k of uncompressed modules.
> including those that have no possible way of ever mounting an external
> memory stick at all, let alone a vfat-formatted one.
> vfat is *not* a basic feature that should be enabled for all 2.6 kernel
> machines. If you want vfat nls modules, then create a vfat feature
> (just like there is an ext2 feature). Do not pollute the basic kernel26
> feature with this stuff.
Yeah, I have hundreds of other items on my list too ;-).
> And the comment about "# If you don't need VFAT support - don't enable
> them in defconfig." is not applicable, because there are machines that
> want vfat-related nls modules available in the feed as a downloadable
> package, but not in the initial rootfs. Therefore they need to be in
> the defconfig, but certainly should not be in task-base-kernel26.
Again, lots of things need to be, etc. But for now (as is), my doing it
right won't help any machine except some small nslu2. Because vfat of
course will be a distro feature, and so far 1) only nslu overrides
angstrom's DISTRO_FEATURES. Also, there're following things to
consider:
2) It's unclear if vfat feature should ship only 40-50K of kernel
modules, or truly bloat it with dosfsutils. Maybe fdisk?
3) There's also need to clear off machine configs from this stuff,
including proverbial fic-gta*.conf.
So, I'm actually glad that you care about such stuff. So, while I
planned to do all stuff above via RFCs over following Angstrom RCs,
I'd be glad to just do another quick fix now as you request and
offload tasks 1-3 above to you. How that sounds?
> I expect you to revert this change and do it properly, or not do it at all.
> -- Rod
--
Best regards,
Paul mailto:pmiscml@gmail.com
next prev parent reply other threads:[~2007-12-18 0:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-18 0:24 pfalcon: revert r5dc6982e... vfat nls modules are not for task-base-kernel26 Rod Whitby
2007-12-18 0:34 ` Rod Whitby
2007-12-18 0:50 ` Paul Sokolovsky [this message]
2007-12-18 0:56 ` Paul Sokolovsky
2007-12-18 1:08 ` Rod Whitby
2007-12-18 1:46 ` Paul Sokolovsky
2007-12-18 2:08 ` Rod Whitby
2007-12-18 2:42 ` Paul Sokolovsky
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=1672988162.20071218025052@gmail.com \
--to=pmiscml@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=rod@whitby.id.au \
/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.