[opensuse] yast2 and domainname
It is possible to run openSUSE without a domain name. Networking and all works fine. However, if you run yast to configure a network device, it insists on the domain name being set before it will accept any changes. This seems more of a policy issue than a requirement to run a system. Why? Things like the HOST and HOSTNAME environment variables are effected by this. One needs to set a temp domain name in yast, and then remove it with a call to hostnamectl. It would be nice if yast2 allowed the domain name to remain empty if it was so when yast was started. I think this started in oS 12.3. Anyone know if it is the same in oS 13.1 (I can't test it yet...)? -- Yours sincerely, Roger Oberholtzer Ramböll RST / Systems Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 roger.oberholtzer@ramboll.se ________________________________________ Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden www.rambollrst.se -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wed, 2013-11-13 at 16:07 +0100, Roger Oberholtzer wrote:
It is possible to run openSUSE without a domain name. Networking and all works fine.
However, if you run yast to configure a network device, it insists on the domain name being set before it will accept any changes. This seems more of a policy issue than a requirement to run a system. Why?
Things like the HOST and HOSTNAME environment variables are effected by this. One needs to set a temp domain name in yast, and then remove it with a call to hostnamectl.
It would be nice if yast2 allowed the domain name to remain empty if it was so when yast was started. I think this started in oS 12.3. Anyone know if it is the same in oS 13.1 (I can't test it yet...)?
Hi I gave up on this years ago. It's broken. Not just that but have you noticed that when you use yast, the fqdn is written to /etc/HOSTNAME? hostname returns the fqdn. Disaster! That really screws up anything dns critical like Kerberos. Just don't use yast I'm afraid. L x -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wednesday, November 13, 2013 04:12:50 PM lynn wrote:
I gave up on this years ago. It's broken. Not just that but have you noticed that when you use yast, the fqdn is written to /etc/HOSTNAME? hostname returns the fqdn. Disaster!
Exactly. $HOSTNAME comes from that source.
That really screws up anything dns critical like Kerberos. Just don't use yast I'm afraid.
We have some rather inexperienced folk who sometimes need to enable DHCP or something in a test situation. yast is such an easy way to allow this. Or was... -- Yours sincerely, Roger Oberholtzer Ramböll RST / Systems Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 roger.oberholtzer@ramboll.se ________________________________________ Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden www.rambollrst.se -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Roger Oberholtzer wrote:
However, if you run yast to configure a network device, it insists on the domain name being set before it will accept any changes. This seems more of a policy issue than a requirement to run a system. Why?
I would think that it assumes if you're configuring for a network, you'll also be using host names and it has to know what the local domain name is, so you can access resourses, without having to use the fully qualified domain name. i.e "mycomper" vs "mycomputer.mynetwork.net". -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wednesday, November 13, 2013 10:21:21 AM James Knott wrote:
Roger Oberholtzer wrote:
However, if you run yast to configure a network device, it insists on the domain name being set before it will accept any changes. This seems more of a policy issue than a requirement to run a system. Why?
I would think that it assumes if you're configuring for a network, you'll also be using host names and it has to know what the local domain name is, so you can access resourses, without having to use the fully qualified domain name. i.e "mycomper" vs "mycomputer.mynetwork.net".
Using the FQDN when appropriate is expected. But that only make s sense if the computer is know by aFQDN. When on a private network, this need not be the case. Say a single computer with many ethernet-based measurement sensors. Or just a couple of computers on a local LAN. Granted this is probably a small use group. But requiring the domainname with no discussion is, IMHO, an inappropriate solution. If you have/use a domain name, give it. If not, don't. As I wrote, oS networking works fine without a domain name. Only yast has this draconian requirement. -- Yours sincerely, Roger Oberholtzer Ramböll RST / Systems Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 roger.oberholtzer@ramboll.se ________________________________________ Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden www.rambollrst.se -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 13/11/2013 16:28, Roger Oberholtzer a écrit :
As I wrote, oS networking works fine without a domain name. Only yast has this draconian requirement.
at install time a random domain name is created. Is this a problem (I mean, is having a random domain name do hurt anything)? thanks jdd -- http://www.dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wednesday, November 13, 2013 04:41:37 PM jdd wrote:
Le 13/11/2013 16:28, Roger Oberholtzer a écrit :
As I wrote, oS networking works fine without a domain name. Only yast has this draconian requirement.
at install time a random domain name is created. Is this a problem (I mean, is having a random domain name do hurt anything)?
No. It is not the random one. I mean that you must have a domain name at all for yast to accept network interface settings. This applies during install and later in yast. And as Lynn pointed out, the hostname is set so as to include this domain name. Maybe if the domain name is set that is common practice. But why must the domain name be set at all in yast? -- Yours sincerely, Roger Oberholtzer Ramböll RST / Systems Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 roger.oberholtzer@ramboll.se ________________________________________ Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden www.rambollrst.se -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
why must the domain name be set at all in yast?
hostname
Le 13/11/2013 16:58, Roger Oberholtzer a écrit : linux-hld1.site all this is semi-random -- http://www.dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2013-11-13 16:58, Roger Oberholtzer wrote:
On Wednesday, November 13, 2013 04:41:37 PM jdd wrote:
Le 13/11/2013 16:28, Roger Oberholtzer a écrit :
As I wrote, oS networking works fine without a domain name. Only yast has this draconian requirement.
at install time a random domain name is created. Is this a problem (I mean, is having a random domain name do hurt anything)?
No. It is not the random one. I mean that you must have a domain name at all for yast to accept network interface settings. This applies during install and later in yast. And as Lynn pointed out, the hostname is set so as to include this domain name. Maybe if the domain name is set that is common practice. But why must the domain name be set at all in yast?
I don't see why you do not want a domain name. :-? -- Cheers / Saludos, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar)
participants (5)
-
Carlos E. R. -
James Knott -
jdd -
lynn -
Roger Oberholtzer