FreeLists / openbeosnetteam / [openbeosnetteam] Re: DHCP Client needed,what would stand in theway?

["Axel Dörfler" <axeld@xxxxxxxxxxxxxxxx>]

"Waldemar Kornewald" <Waldemar.Kornewald@xxxxxx> wrote:
> But we still edit driver_settings, can we?

What do you mean with this? driver_settings can be written manually, 
they can be programmatically edited, and written back to a file easily 
with the new API extensions.
BTW I guess I will have to write a newsletter article about the revised 
driver_settings API anyway.

> > It's just that our current get*byname() implementation is based on 
> > ISC Bind client, which use /etc/resolv.conf.
> > Changing the way nameserver(s) list are stored will involve 
> > modifying
> > /
> > forking ISC Bind client code.
> > Not that I'm against it, as our implementation is not a port but an 
> > adaptation, and I always found 
> > these /etc/resolv.conf and /etc/hosts too much Unix-y for BeOS.
> Is it so big?

OTOH, the location /etc for network settings is the right one as long 
as we don't have a /boot/common/settings/ directory (or 
B_COMMON_SETTINGS_DIRECTORY).
I dunno what find_directory() will return for this constant right now, 
but I think we might want to introduce that directory in OpenBeOS, 
maybe even in R1.
The advantage of having common settings files (like /etc/resolv.conf) 
is that everybody who knows Unix a bit will feel at home, and be able 
to config the system immediately without having to use a GUI :)

> > Sounds good.
> > Okay, I'll add this feature on new_stack TODO list...
> > Time to add our driver_settings.c to network/core and new_stack/
> > stack 
> > modules, so!
> > ;-)
> Very nice. :)

It's directly usable like I did for the DriverSettingsTest in src/tests
/kernel/libroot/os/ - just have a look in the Jamfile there.

> > And supporting Network preflet Profiles feature (aka different net 
> > settings) will be far easier that way than with multiple network-
> > related settings files to switch/backup/replace/modify...
> How do you want to do that? Using directories for profiles (and the 
> current profile is just a link to the real profile)?

I would rather like to have more than one settings file, and if it's 
for the single reason that the file doesn't have to be saved that 
often.
I.e. DHCP will change your nameservers everytime, and normally, these 
changes are persistent - of course we could decide to not adopt this 
behaviour.

If there are more than one file per profile, we should just put them 
all into one directory per profile.
Also, (independently from the directory/file structure) we could do 
neat things like have a basic profile that others will inherit if 
specifications are missing.

So we could have a whole basic configuration and the profiles will just 
change the IP address or switch DHCP on/off. I would be okay if that 
advanced feature would only be available through the command line (at 
first), though :)

> <BUG>
> I found another BUG in BeMail: I selected Philippe's reply, removed 
> it, 
> pressed ALT+Z and the colors were lost.
> </BUG>

That's not a bug, but a feature! :-)
The colors stuff is not completely done everywhere (although I tried 
for this release a bit), and the Undo/Redo stuff is almost new and 
buggy anyway.

Adios...
   Axel.