[openbeosnetteam] Re: our package
- From: "Axel Dörfler" <axeld@xxxxxxxxxxxxxxxx>
- To: openbeosnetteam@xxxxxxxxxxxxx
- Date: Thu, 02 Sep 2004 12:44:34 +0200 CEST
"Waldemar Kornewald" <Waldemar.Kornewald@xxxxxx> wrote:
> > I think that there is no need for such a directory either - the
> > system
> > directory itself should only contain the base OS, and no user or
> > system
> > settings at all. All components of the OS should come with useful
> > built
> > -in settings.
> That is what I searched for as the best solution. :)
> I can try to write a small perl script that translates those etc
> files into structures
> and then we can import it into our libbind. I cannot imagine that
> "services" changes
> often (if at all)I will try to integrate the following into libbind
> and libnet:
> services
I agree with Lars on the "services" file, though :)
> protocols
>
> Is /etc/networks only used by "route"? If so, we could possibly drop
> it? :)
Dunno, but possibly.
> > Anything else should either go to B_COMMON_SETTINGS_DIRECTORY or,
> > to a
> > lesser extent, B_USER_SETTINGS_DIRECTORY. Since we don't have a
> > common
> > directory right now, I would vote for adding one, either just a /
> > boot/
> > config/ folder which contains that stuff or a /boot/common/ folder.
> /boot/system/config would be better, IMHO. That would allow the same
> naming
> scheme as in /boot/home/config.
You would have the same under either /boot/config or /boot/common/
config/ - "system" would not be correct, since that should only be the
system (i.e. /boot/beos/system/), also it would be confusing to have
two system folders at different places.
> But we already have /boot/system/add-ons. Should we replace it with a
> link and
> move the folder to /boot/system/config (or /boot/config?) in order to
> be more
> consistent with the /boot/home/config directory structure?
Ah, you are actually confused, too :) The directory you were looking
for is /boot/beos/system/ - and I don't think this should get another
config directory.
> > /etc is a symbolic link right now, and we probably can't remove it
> > either. The point is, that I don't think this directory makes a lot
> > of
> > sense. I would better like to separate application data, and
> > settings.
> > I would suggest to add two new kind of folders to any BeOS system:
> > - B_{COMMON|USER}_DATA_DIRECTORY for most of the stuff which you
> > can
> > now find in /etc (keymaps, timezones, etc.) - if you have a better
> > name
> > for that, please tell :)
> > The other options I would have are "shared", "database", "storage",
> > ...
> > - but I think of these, "data" is best.
> > - B_{COMMON|USER}_CACHE_DIRECTORY for web and other cache data
> > (persistent but non-critical data)
> >
> > Any comments or critics? I would really like to see these
> > directories
> > with Haiku R1.
> Yes, let's add them. Should they go under /boot/home||system/config/?
Not under "system" - as I tried to say, this should be a static
directory - one that you can exchange without losing anything but
features that the installed version delivers or not.
I think they should be under:
/boot/home/config/
and
/boot/config/
Bye,
Axel.
- Follow-Ups:
- [openbeosnetteam] Re: our package
- From: Waldemar Kornewald
- References:
- [openbeosnetteam] Re: our package
- From: Waldemar Kornewald
Other related posts:
- » [openbeosnetteam] our package
- » [openbeosnetteam] Re: our package
- » [openbeosnetteam] Re: our package
- » [openbeosnetteam] Re: our package
- » [openbeosnetteam] Re: our package
- » [openbeosnetteam] Re: our package
- » [openbeosnetteam] Re: our package
- » [openbeosnetteam] Re: our package
- » [openbeosnetteam] Re: our package
- » [openbeosnetteam] Re: our package
- » [openbeosnetteam] Re: our package
- » [openbeosnetteam] Re: our package
- » [openbeosnetteam] Re: our package
- » [openbeosnetteam] Re: our package
- » [openbeosnetteam] Re: our package
- » [openbeosnetteam] Re: our package
- » [openbeosnetteam] Re: our package
- » [openbeosnetteam] Re: our package
- » [openbeosnetteam] Re: our package
- » [openbeosnetteam] Re: our package
- » [openbeosnetteam] Re: our package
- » [openbeosnetteam] Re: our package
- » [openbeosnetteam] Re: our package
- » [openbeosnetteam] Re: our package
- » [openbeosnetteam] Re: our package
- » [openbeosnetteam] Re: our package
- » [openbeosnetteam] Re: our package
- » [openbeosnetteam] Re: our package
- » [openbeosnetteam] Re: our package
- » [openbeosnetteam] Re: our package
- » [openbeosnetteam] Re: our package
- » [openbeosnetteam] Re: our package
- [openbeosnetteam] Re: our package
- From: Waldemar Kornewald
- [openbeosnetteam] Re: our package
- From: Waldemar Kornewald