Summary: | /etc/init.d/domainname error with sys-apps/baselayout-1.12.0_pre17 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Sebastian Bergmann (RETIRED) <sebastian> |
Component: | [OLD] baselayout | Assignee: | Gentoo's Team for Core System packages <base-system> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | High | ||
Version: | 2006.0 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 129223 |
Description
Sebastian Bergmann (RETIRED)
![]() confirmed That initscript is dead (see changelog), just delete it. ;) <snip> 03 Apr 2006; Roy Marples <uberlord@gentoo.org>: ... Punted the domainname script. Functionality has been in conf.d/net so you can do this. dns_domain_lo="foo" nis_domain_lo="bar" </snip> That, of course, makes the error go away but I still have no $HOSTNAME variable anymore. yeah i read the changelog + the /etc/conf.d/net.example they is nothing at all about "dns_domain_lo" or "nis_domain_lo" i thing it should be dns_domain_eth0 to make it quick read the "net.example" here are my modifed /etc/conf.d/net as a example with router @ 192.168.1.1 and a static ip 192.168.1.2 (no dhcp) ----------- config_eth0=( "192.168.1.2 netmask 255.255.255.0 broadcast 192.168.1.255" ) routes_eth0=( "default via 192.168.1.1" ) dns_domain_eth0="your.domain" dns_servers_eth0="ip1 ip2" --------- i have deleted the /etc/resolv.conf (make backup) stoped and removed the domainname service : /etc/init.d/domainname stop rc-update del domainname reboot all looks good (In reply to comment #4) > yeah i read the changelog + the /etc/conf.d/net.example > they is nothing at all about "dns_domain_lo" or "nis_domain_lo" > i thing it should be dns_domain_eth0 From net.example # System # For configuring system specifics such as domain, dns, ntp and nis servers # It's rare that you would need todo this, but you can anyway. # This is most benefit to wireless users who don't use DHCP so they can change # their configs based on ESSID. See wireless.example for more details # To use dns settings such as these, dns_servers_eth0 must be set! # If you omit the _eth0 suffix, then it applies to all interfaces unless # overridden by the interface suffix. #dns_domain_eth0="your.domain" #dns_servers_eth0="192.168.0.2 192.168.0.3" #dns_search_eth0="this.domain that.domain" #dns_options_eth0=( "timeout 1" "rotate" ) #dns_sortlist_eth0="130.155.160.0/255.255.240.0 130.155.0.0" # See the man page for resolv.conf for details about the options and sortlist # directives #ntp_servers_eth0="192.168.0.2 192.168.0.3" #nis_domain_eth0="domain" #nis_servers_eth0="192.168.0.2 192.168.0.3" Which has been there for months. Not a bug. then baselayout should delete the domainname script in light of the fact portage sucks at this (In reply to comment #6) > then baselayout should delete the domainname script in light of the fact > portage sucks at this > What is needed, above all, is warnings in the ebuild about all these changes... :/ We can't expect users to read the changelog entry and search for more informations in this bugzilla :/ The domainname init script is now removed from the system and a warning is displayed by the ebuild. Someone needs to make a much more public announcement of this. It took me two hours to figure this out, and let me tell you, it was frustrating... This sucks. "It's rare that you would have to set these" my arse, what about if you want dnsdomainname, nisdomainname, and hostname --fqdn to work on your server? What interface to use when you have 4? Why do we have to do stupid things like this to contend with mobile users? I spent too much time fixing a system after this issue bit me. My solution, similar to comment 4 and 5 was to put this in my /etc/conf.d/net file: nis_domain="YOUR_NIS_DOMAIN_NAME" I wonder why dhcpd did not set domainname when it did update my /etc/yp.conf from the yp master. Won't this move make Gentoo to become more "odd" when compared to tohers distros configurations? I thought that the move from /etc/hostname -> /etc/conf.d/hostname and /etc/domainname -> /etc/conf.d/domainname as a bad move. not really, the usage of plain files in /etc/ was Gentoo specific as no other distro used that schema (In reply to comment #7) > We can't expect users to read the changelog entry and search for more > informations in this bugzilla :/ That's how I got here :) (In reply to comment #10) > This sucks. "It's rare that you would have to set these" my arse, what about > if you want dnsdomainname, nisdomainname, and hostname --fqdn to work on your > server? What interface to use when you have 4? Why do we have to do stupid > things like this to contend with mobile users? Exactly what I'm thinking -- is there any solution to this that *doesn't* break things like `hostname --fqdn`? (In reply to comment #14) Heh, disregard. Fixed my issue, as far as I can tell, by doing the following: -Setting the variable in /etc/conf.d/net as described above -changing the /etc/hosts entry to list the fqdn first, i.e. a.b.c.d server.example.net server The resolver returns the first entry from hosts (default) so setting that properly seems to fix the output of `hostname --fqdn`. (sorry for the bugzilla necromancy) |