From: Marcin Juszkiewicz <openembedded@hrw.one.pl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: RFC: Task-base rewrite
Date: Fri, 13 Apr 2007 08:19:54 +0200 [thread overview]
Message-ID: <200704130819.55884.openembedded@hrw.one.pl> (raw)
In-Reply-To: <461EB337.7020302@whitby.id.au>
Dnia piątek, 13 kwietnia 2007, Rod Whitby napisał:
> No tests yet, but it has the support of nslu2-linux distros.
;)
Idea of splitting into separate packages comes from my discussions with
Richard about differencies between Poky task-base and OE task-base.
During last Easter I had more time to think about correct implementation
and wanted to make small rootfs creation easier then it was before.
And nslu2 rootfs is big - Cliff Brake created 1.7M rootfs for his Compulab
board.
Cliff: can you look at task-boot contents and tell does it need something
removed/added to create minimal image?
> I especially like the dropbear/openssh selection capability.
Too many people complain about having dropbear in their rootfs ;)
--
JID: hrw-jabber.org
OpenEmbedded developer/consultant
I don't know. I don't care. And it doesn't make any difference.
next prev parent reply other threads:[~2007-04-13 6:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-04 21:28 RFC: Task-base rewrite Marcin Juszkiewicz
2007-03-04 22:55 ` Koen Kooi
2007-03-05 8:04 ` Marcin Juszkiewicz
2007-03-07 17:09 ` Koen Kooi
2007-03-08 13:57 ` Marcin Juszkiewicz
2007-04-12 18:35 ` Marcin Juszkiewicz
2007-04-12 19:19 ` Koen Kooi
2007-04-12 22:26 ` Richard Purdie
2007-04-12 22:31 ` Rod Whitby
2007-04-13 6:19 ` Marcin Juszkiewicz [this message]
2007-04-13 8:47 ` Marcin Juszkiewicz
2007-04-17 3:22 ` Cliff Brake
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=200704130819.55884.openembedded@hrw.one.pl \
--to=openembedded@hrw.one.pl \
--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.