On Friday 28 February 2003 12:27 am, Lyvim Xaphir wrote: > --- Greg Meyer <[EMAIL PROTECTED]> wrote: > > On Thursday 27 February 2003 11:49 pm, Lyvim Xaphir wrote: > > > --- Greg Meyer <[EMAIL PROTECTED]> wrote: > > > > Whatever you're all learning now, be prepared to unlearn when 9.1 > > > > comes out because it's all different. I'm trying to figure it out in > > > > cooker but it's a bear. > > > > -- > > > > Greg > > > > > > Surely you are not saying that /etc/sysconfig/network has disappeared. > > > I had the impression that that config file was part of the SysVinit > > > system, which has been a commonality across both RH and LM for a long > > > time. It has never been part of the mcc specific stuff, as far as I > > > know. > > > > No, it's still there, just all this zeroconf stuff is mucking up the > > works. I cannot get Mandrake to override the hostname given out by the > > dhcp server, so my box that should be named cooker is dhcppc5 instead. > > > > In addition to /etc/sysconfig/hostname, there is > > /etc/sysconfig/network-scripts/ifcfg-eth(x) to contend with. I'll let > > you know when I figure it out. :-) > > -- > > Greg > > OK. Well...I guess I'm wondering some things at this point. First, was > the system told to use dhcp? If so then you should be setting your > hostname within /etc/dhcpd.conf instead of the sysconfig files, and > therefore your system is acting properly. > Well, cooker is using dh-client instead of dhcpd, so dhcpd.conf is out.
> Second, the ..network-scripts/ifcfg-eth(x) files have also traditionally > been part of the SysVinit system, which is near about as old as Red Hat's > System 5 compatibility decision. I'm being somewhat facecious; System 5 > goes back to the 70's, and was (mostly) adopted into the Posix standard > later on. Red Hat adopted posix compatibility as a de facto standard. Or I > should say has always attempted to be as close to posix as possible; some > parts of it are obtuse to conform to. > > What I'm saying is that I have not seen anything yet that is zero-conf > specific in what you are submitting. If zero-conf is mucking with your > config files without your permission or knowledge, then my opinion is that > advanced users should have an option available to deactivate it. Unfortunately, inmy frustration I was using the term zeroconf to refer to all the changes in the networking setup. Between replacing dhcpd with dh-client, adding tmdns and zeroconf and rewriting drakconnect to account for the changes, I am quite frustrated because I have not been able to get it all to work properly out of the box. I do realize it is a beta, and the reason why I am fighting with it is so I can try to help get it right. I am not sure if I am running into bugs, or if I just don't understand what they are trying to do. I suppose if it supposed to work out of the box, and it doesn't, then it is a bug and not me. As I read the zeronconf website, I see it is a project to provide zero configuration networking even when the networks are not set up properly. But contrary to this, the discussion on cooker is heading towards zeroconf won't work right unless dns and dhcp are setup properly, so set it up properly before you report a bug. So which is it? Who knows? I just hope someone takes the time to document all this before 9.1 is released into the wild. -- Greg
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
