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