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