From: James <wireless@tampabay.rr.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: Profile listings
Date: Mon, 15 Jun 2015 04:27:18 +0000 (UTC) [thread overview]
Message-ID: <loom.20150615T061507-672@post.gmane.org> (raw)
In-Reply-To: 201506150138.26147.dilfridge@gentoo.org
Andreas K. Huettel <dilfridge <at> gentoo.org> writes:
> > Note {embedded << minimal << default} I still have some vintage gentoo
> > systems running which have very few flags set and include (USE="-*") in
> > make.conf. And a {state-machine/executive/rtos << embedded(linux)},
> > just so we are on the same page.
> Would be interesting to know what you mean exactly by "minimal" (there
> is no such profile) and "embedded".
Let me state this again, from the top down. Ok Say I install the default
profile, for say and arm64 system (a dev board with graphics chip like
96board. I can install gentoo on that with a minimum number of packages.
But let's say all I really want is IPtables (or nftables) and ssh.
Surely the default profile has more than is need. So if everything not
absolutely was stripped out, it'd be a minimized gentoo system (my
nomenclature). This would eventually include a very trimmed kernel,
and very few processes running. I use to build these (some years ago)
and it was easy, just put {USE=-*} in make.conf and add a very few flags.
X86 mostly.
Now say I go to the gentoo_embedded_handbook and build a minimum system
for an arm 7 chip. It is even small than this aforementioned minimal
gentoo system, as it is embedded (yocto) or OE would be straightforward now,
but Linaro is bloated for an embedded system).
SO we have this relationship:
embedded << minimal << default as far as I am concerned with profiles.
I undertand the history of gentoo, so I know, particularly below a default
profile, it's been adhoc. Maybe the minimal should use 'sys-apps/S6' just
for grins?
OK? I not saying this is the current way it is in gentoo, there is no
mapping between and embedded gentoo system and a default gentoo system;
so I am going to develop one, for my interests. Input from others is welcomed.
James
next prev parent reply other threads:[~2015-06-15 4:27 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-14 19:22 [gentoo-user] Profile listings James
2015-06-14 20:40 ` Andreas K. Huettel
2015-06-14 22:21 ` [gentoo-user] " James
2015-06-14 23:38 ` Andreas K. Huettel
2015-06-15 4:27 ` James [this message]
2015-06-14 23:12 ` [gentoo-user] " Andrew Savchenko
2015-06-15 4:37 ` [gentoo-user] " James
2015-06-15 12:15 ` Martin Vaeth
2015-06-15 15:25 ` James
2015-06-16 17:42 ` James
2015-06-16 20:26 ` Neil Bothwick
2015-06-17 8:18 ` Martin Vaeth
2015-06-17 16:11 ` James
2015-06-18 7:05 ` Martin Vaeth
2015-06-18 15:21 ` James
2015-06-18 17:33 ` Martin Vaeth
2015-06-18 18:44 ` James
2015-06-18 19:59 ` Martin Vaeth
2015-06-19 19:46 ` James
2015-06-21 3:29 ` Jonathan Callen
2015-06-21 16:17 ` James
2015-06-19 2:27 ` Bruce Schultz
2015-06-19 19:56 ` James
2015-06-19 20:38 ` Neil Bothwick
2015-06-20 2:51 ` James
2015-06-21 16:09 ` James
2015-06-21 17:49 ` Neil Bothwick
2015-06-21 20:02 ` Alan McKinnon
2015-06-21 23:53 ` Peter Humphrey
2015-06-22 13:38 ` James
2015-06-22 14:47 ` Martin Vaeth
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=loom.20150615T061507-672@post.gmane.org \
--to=wireless@tampabay.rr.com \
--cc=gentoo-user@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox