On Mon, 12 Feb 2001 [EMAIL PROTECTED] wrote:
> On 12 Feb 2001, at 18:41, Jack Coates wrote:
>
> > Just want to solicit some feedback on my dedicated server
> > appliance.
>
> > Everything is built into a single root.lrp with centralized
> > configuration (i.e. linuxrc does everything necessary to initialize
> > hardware and configure the system, then an application rc will do
> > everything necessary to initialize the applications being served).
>
> BSD-style init scripts? If not entirely, might be a good idea -
> keeps to a standard method, allowing any admin to find things where
> they expect.
>
Interesting... I like the SysV system for /etc/init.d/service
start|stop|restart|status though. My only experience with the BSD style is
Slackware 2.0 though, so my apologies and please let me know if a similar
capability is there.
> > My question is, should I remove package capabilities entirely from
> > the user interface? In other words, I would use apkg to load
> > packages during boot, but once booted there would be no capability
> > to add and remove packages -- and since only the Boot-disk can be
> > or needs to be backed up, package backup code can be stripped down
> > as well.
>
> Except once you back up the root, then apkg is no longer available to
> the boot process. I like the goals, but without extracting apkg and
> package management from the system entirely, it probably won't work.
>
> However, extracting a package can be reduced to:
>
> # cd / ; gunzip -c - < pkg.lrp | tar xf -
>
That's what I'm thinking. There's a lot of space tied up in the assumption
of interactive packages.
> > So, would the lack of an interactive package tool totally spoil a server
> > appliance for you?
>
> My bias - likely evident from Oxygen's direction - is to be able to
> modify the base to whatever one wants. But I like your ideas too.
>
> Some development notes:
> * If you're using BSD-style startup rc files, then update-rc.d is
> irrevelant and can be erased.
That file and POSIXness are currently on the table, so to speak :-)
> * Oxygen development continues... are you using the most recent
> version?
12-10, though I've made radical enough changes that I wouldn't want to
start over with a new image unless there were something really compelling.
> * One of the newer versions will have an "official" document branding
> it with the MIT/X License; perhaps you might want this?
>
Unless you're willing to retroactively extend such licensing. Are you
saying that the first Oxygen releases were not open licensed, or just that
they weren't documented as such?
> Would it be worth it to create a "initscrp.lrp" (for "initscripts")
> for BSD and SysV inits? Using Oxygen as it is, with two scripts -
> perhaps bsd-init.lrp and sysVinit.lrp - changing over COULD be as
> easy as:
>
> # apkg -i /mnt/sysVinit # "install" SysV init
> # apkg -r sysVinit # remove SysV init from system
> # apkg -i /mnt/bsd-init # install BSD init
> # apkg -s root # Safe backup
>
For the Oxygen core, yes, I think a lot of people would like something
like that. The Ladybug philosophy so far seems to be "if you have to ask
yourself whether you need this file, you probably don't." :-)
_______________________________________________
Leaf-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/leaf-devel
