On Friday 22 August 2003 14.21, Buchan Milne wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Any comment on this??? > > Buchan Milne wrote: > > Damien Chaumette wrote: > >>Well, there are mutliples cases : > >> > >> o static IP > >> you set your HOSTNAME (/etc/sysconfig/network) > >> > >> o DHCP > >> you can ask a name to your DHCP server (DHCP_HOSTNAME), and it'll > >> return either this one or another, then initscripts use it as > >> your HOSTNAME. > > > > What if the dhcp server returns > > dhcp-vlan-adsl-xxx-xxx-xxx-xxx.myisp.mydomain.com and the user doesn't > > want to have hostname dhcp-vlan-adsl-xxx-xxx-xxx-xxx as hostname? > > > >>Then you have zeroconf which is subdivided in two parts : > >> > >> o zcip which handle the IP dynamic configuration (only with DHCP) > >> o tmdns always installed, to resolve names. > >> > >>Zeroconf hostname (/etc/tmdns.conf) is set to your real hostname value > >>by default or one you specified in drakconnect. > > > > IMHO this is wrong. Hostname should be set, tmdns will use `hostname` if > > you don't set it manually in the config file. There is no case where you > > will want a different hostname taken by tmdns than `hostname`, so IMHO > > drakconnect should leave tmdns.conf alone. > > BTW, I think this issue is also causing problems for samba, since often > HOSTNAME is unset, so `hostname` gives localhost. Then, samba uses this > hostname, and clients try to connect to \\localhost, which obviously > does not work. > > Also, this breaks the winbind setup, since 'smbpasswd -j' will either > try and join to a pre-made account (in the case of a non-admin join), as > localhost (which will not work), or it will try and create a new account > (in the case of an admin-join), which will only work for the first > machine joined this way (if at all). > > Finally, a number of packages generate self-signed certificates, either > during installation or for first startup, and then the cert will have > 'CN=localhost', so if ther use changes the hostname, they will have to > regenerate or live with the complaints. > > This is a really major issue. No machine should *ever* use localhost as > it's hostname if it is connected to a network, especially if running > samba, cups, apache etc etc. > > I think I must file a bug on drakconnect, but I haven't had time to test > this myself. > > >>Let user set a hardcoded hostname when using dhcp will only lead to > >>unresolved names. > > > > No, that's precisely *why* tmdns will *default* to using the set > > hostname!!! It's fine if the IP resolves to multiple hostnames, but it's > > better that it resolves to the name the user wants (but this should be > > an advanced configuration). > > Please consider this issue ... it should not be necessary to touch > tmdns.conf. Ever. > > Regards, > Buchan
I think you may rest on this pb as the new installation may have done the right thing. As a user I have the possibility to add both zeroconf and the full name of the computer. I used both and got: zeroconf = Pelles full hostname = Pelles.brisen.home.lan And got the following in /etc/sysconfig/network: HOSTNAME=Pelles.brisen.home.lan NETWORKING=yes The installation failed to boot but they seem to be on the right way. regards guran -- Mandrake Linux Cooker 9.2 kernel-2.4.22.0.6mdk-1-1mdk Only in a society that has 'a priori' defined what is the truth can the result from the evolution of life be defined false.
