From: Paul Sokolovsky <pmiscml@gmail.com>
To: Rod Whitby <rod@whitby.id.au>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: RFC: Inclusion of bootloader utilities in task-base
Date: Mon, 3 Dec 2007 16:19:51 +0200 [thread overview]
Message-ID: <783254142.20071203161951@gmail.com> (raw)
In-Reply-To: <475322B8.8000501@whitby.id.au>
Hello Rod,
Sunday, December 2, 2007, 11:25:12 PM, you wrote:
> Paul Sokolovsky wrote:
>> This raises the question if user should be allowed (far less
>> required) to change bootloader's standard cmdline as *the normal
>> course of using distro* (== task-base). So, maybe the 1st choice ("Is
>> it good idea at all") is worth more attention.
> Ah, this is a question about which parts of task-base a DISTRO should
> include or not (by use of it's DISTRO_FEATURES). Not about whether
> task-base should give distros the choice in the first place.
Ok.
> Is Angstrom (the only DISTRO which currently has this feature enabled)
> meant to be a hand-holding-for-naive-users distro, or a power-users distro?
Apparently, leaning more towards the first, than to the second. On my
memory, at least some MTD-related utility was cut from Angstrom for
the reasons that users may shoot themselves in foot with it. Other
util (ipkg-link) is not incuded for purely idiosyncratic reasons, bit
with the same motivation - "users may mess up with it".
But well, I'm not arguing if you should include the utils in
question or not, but rather on more general question what should go
into standard image (or images of different types), and what not.
Then, it would be easier to decide on particulars, and assess, if some
exception is worth here or there. Motivation is that it's not possible
to fit any useful util at all, and space is precious.
> And yes, it's most likely that an end-user distro would put a shell script
> wrapper around the bootloader utility to safeguard the user for normal
> end-user operations like changing the rootfs load location, or setting up
> nfsroot operation.
> -- Rod
--
Best regards,
Paul mailto:pmiscml@gmail.com
next prev parent reply other threads:[~2007-12-03 14:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-02 1:47 RFC: Inclusion of bootloader utilities in task-base Rod Whitby
2007-12-02 8:19 ` Koen Kooi
2007-12-02 10:06 ` Rod Whitby
2007-12-02 19:27 ` Paul Sokolovsky
2007-12-02 21:25 ` Rod Whitby
2007-12-03 14:19 ` Paul Sokolovsky [this message]
2007-12-03 14:33 ` Rod Whitby
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=783254142.20071203161951@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.