From: Rod Whitby <rod@whitby.id.au>
To: Paul Sokolovsky <pmiscml@gmail.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: RFC: Inclusion of bootloader utilities in task-base
Date: Tue, 04 Dec 2007 01:03:19 +1030 [thread overview]
Message-ID: <475413AF.9050603@whitby.id.au> (raw)
In-Reply-To: <783254142.20071203161951@gmail.com>
Paul Sokolovsky wrote:
> 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.
That's my goal too. A couple of sentences at the top of each image file
giving it's intent would go a long way to answering these questions.
For example, I'm writing a nas-server-image.bb file right now, and I've
put at the top:
# This image is intended to provide a configuration
# for a network attached storage server device.
#
# Key features are:
#
# 1) Must be able to mount attached storage devices like
# internal disks, external USB disks, etc. Should support
# various filesystem choices, but ext2 at a minimum.
#
# 2) Must be able to boot from internal flash, or directly
# from a filesystem stored on the attached storage.
#
# 3) Must be able to share that storage across the network
# using various protocols like Samba, NFS, etc.
#
# 4) Bonus points for being able to support other central
# network services like a central gateway machine might.
#
# Although it is tested with the Angstrom distro, it is
# intended to be distro-agnostic.
-- Rod
prev parent reply other threads:[~2007-12-03 14:37 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
2007-12-03 14:33 ` Rod Whitby [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=475413AF.9050603@whitby.id.au \
--to=rod@whitby.id.au \
--cc=openembedded-devel@lists.openembedded.org \
--cc=pmiscml@gmail.com \
/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.