[openbeosnetteam] Re: our package
- From: "v r" <vreikine@xxxxxxxxx>
- To: openbeosnetteam@xxxxxxxxxxxxx
- Date: Tue, 31 Aug 2004 10:17:11 -0500
One of the reasons why Unix has these files in /etc directory is that user
files can be located on NFS volume. Or to be more precise, network stack can be
started independently of starting user-mode application and even mounting user
volumes. I am quite realistic about Haiku being long way before be multiuser
system with user home directories located on some distributed FS. Still, if
network stack is in kernel, then /beos/system/settings should be used, if it's
user-mode stack than home/settings should be used with a fallback mechanism. If
I understand it correctly Waldemar went through this dilema before with his PPP
driver - it has to be started by user but it should perform as kernel-mode
driver, hence where to put settings question.
Besides testing purposes, there is also POSIX compatiblity goal and for that
Haiku will need to have /etc directory - will it contain actual files or
symbolic links is a different story.
Had posibility of using attributes for those settings been already discussed ?
I am not following all discussions here.
'protocols', 'networks', resolve.conf' files are quite small and can easily fit
into a BMessage,
'services' is not that small but I think it's unnecessary big on Unix, usually
a very small subset of listed services is used.
----- Original Message -----
From: "Axel Dörfler" <axeld@xxxxxxxxxxxxxxxx>
Date: Tue, 31 Aug 2004 14:30:23 +0200 CEST
To: openbeosnetteam@xxxxxxxxxxxxx
Subject: [openbeosnetteam] Re: our package
> "Waldemar Kornewald" <Waldemar.Kornewald@xxxxxx> wrote:
> > Hrrm, we can put it on our TODO list, but I think it is already well-
> > placed at /etc.
> > Which of those files would you like to see in home/config/etc, too?
>
> For now (for the testing packages), I would like to see all of them
> somewhere else than /etc. I like Philippe's suggestion - that would
> solve the issue with only little collateral damage :)
>
> > We have
> > protocols - makes no sense to allow overriding it by the user
> > services - well, I do not think this is necessary
> > resolv.conf - that one might be useful
> > networks - should not be needed
>
> Personally, I would like "protocols" to disappear completely and the
> rest should go into a settings directory, like:
> B_USER_SETTINGS_DIRECTORY/network/ (for now B_COMMON_SETTINGS_DIRECTORY
> should be the better choice).
>
> Bye,
> Axel.
>
>
--
_______________________________________________
Find what you are looking for with the Lycos Yellow Pages
http://r.lycos.com/r/yp_emailfooter/http://yellowpages.lycos.com/default.asp?SRC=lycos10
- Follow-Ups:
- [openbeosnetteam] Re: our package
- From: Axel Dörfler
- [openbeosnetteam] Re: our package
- From: Lars Hansson
- [openbeosnetteam] Re: our package
- From: Lars Hansson
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: Axel Dörfler
- [openbeosnetteam] Re: our package
- From: Lars Hansson
- [openbeosnetteam] Re: our package
- From: Lars Hansson