Gentoo Archives: gentoo-embedded

From: "Peter S. Mazinger" <ps.m@×××.net>
To: Chris PeBenito <pebenito@g.o>
Cc: david@×××××××××.com, AJ Armstrong <aja@g.o>, Embedded Gentoo Mail List <gentoo-embedded@g.o>
Subject: Re: [gentoo-embedded] base-layout lite
Date: Mon, 08 Dec 2003 17:59:02
Message-Id: Pine.LNX.4.44.0312090051390.3116-100000@lnx.bridge.net
In Reply to: Re: [gentoo-embedded] base-layout lite by Chris PeBenito
On Sun, 7 Dec 2003, Chris PeBenito wrote:

> On Tue, 2003-12-02 at 13:08, david@×××××××××.com wrote: > > On Tue, Dec 02, 2003 at 12:04:35PM -0700, AJ Armstrong wrote: > > > On 2 Dec 2003 11:44, david@×××××××××.com emitted: > > > > > > > ex: do we really need 500 lines of bash sourced so we can have colored > > > > [ OK ] > > > > I don't think this is really necessary. > > > > > > Not only is it unnecessary, but I think it is _wrong_ if the code is running > > > in an embedded environment. I think we should be starting with what is > > > absolutely required for a system to boot as the baselayout - no frills, no > > > pretification. Those could perhaps be build as optional ebuilds that can be > > > emerged _after_ baselayout for those whose target platforms can support them. > > I agree with this. I'm thinking that baselayout-lite would probably > just have one init script, rc.sysinit or the like. There's not very > many systems that would have/need additional runlevels. So a good place > might be to extract stuff out of /sbin/rc, and other regular baselayout > scripts and merge into one script. > > Solar has also suggested looking at the buildroot baselayout, but I have > been bogged down by my classwork, so I haven't looked yet. > > > Well I'm not sure where to draw the line... > > do we want to still have /var/run PID functionality for example ? Or should we > > leave that up to the embedded user... it could most likely be > > implemented in a few lines of bash. > > > > or maybe some sort of busybox like funcitonality with symlinks... i.e. > > > > /etc/init.d/busyinit > > /etc/init.d/network -> /etc/init.d/busyinit > > This is another good idea :) Especially since busybox is most likely > going to get heavy use. /var/run may or not be around; with something > real simple, without the classic /etc/init.d services, it probably > doesn't need to.
Consider also, that busybox includes minit (another init), better as the default init, has dependency checking between services, parallel startup of services, as I understand it. Wach service has it's own subdirectory where the config/dependency files can be placed To integrate it with a full-blown SysVinit system each service could provide both configs, a sysvinit startup script, and a, let's say minit one. Peter -- Peter S. Mazinger <ps.m@×××.net> ID: 0xA5F059F2 NIC: IXUYHSKQLI Key fingerprint = 92A4 31E1 56BC 3D5A 2D08 BB6E C389 975E A5F0 59F2 ____________________________________________________________________ Miert fizetsz az internetert? Korlatlan, ingyenes internet hozzaferes a FreeStarttol. Probald ki most! http://www.freestart.hu -- gentoo-embedded@g.o mailing list

Replies

Subject Author
Re: [gentoo-embedded] base-layout lite david@×××××××××.com