SEO

Upon boot, I get the kernel messages saying that etc/hostname should no
longer be used, and I should switch to etc/conf.d/hostname. Same goes for
etc/dnsdomainname and etc/conf.d/domainname.

How is that done?.

Can I jst delete the /etc/hostname and /etc/dnsdomainname files, and add the
appropriate "tux" and "homenetwork" entries as explained in the
installdocs, and keep domainname in my default runlevel?.

/Stig

Stig Mogensen wrote:
> Upon boot, I get the kernel messages saying that etc/hostname should no
> longer be used, and I should switch to etc/conf.d/hostname. Same goes for
> etc/dnsdomainname and etc/conf.d/domainname.
>
> How is that done?.

Look inside the files you just mentioned in /etc/conf.d/ - the files
themselves contain their setup instructions.

> Can I jst delete the /etc/hostname and /etc/dnsdomainname files, and add the
> appropriate "tux" and "homenetwork" entries as explained in the
> installdocs, and keep domainname in my default runlevel?.

Yes. See
http://groups-beta.google.com/group/...0c55a03f?hl=en

Paul Bredbury wrote:

> Stig Mogensen wrote:
>> Upon boot, I get the kernel messages saying that etc/hostname should no
>> longer be used, and I should switch to etc/conf.d/hostname. Same goes for
>> etc/dnsdomainname and etc/conf.d/domainname.
>>
>> How is that done?.
>
> Look inside the files you just mentioned in /etc/conf.d/ - the files
> themselves contain their setup instructions.

Well....I wouldn't call it "instructions"), but now my etc/conf.d/hostname
contains HOSTNAME="tux", and etc/conf.d/domainname has
DNSDOMAIN="homenetwork".

>> Can I jst delete the /etc/hostname and /etc/dnsdomainname files, and add
>> the appropriate "tux" and "homenetwork" entries as explained in the
>> installdocs, and keep domainname in my default runlevel?.
>
> Yes. See
>
http://groups-beta.google.com/group/...0c55a03f?hl=en

Excellent...thank you.

/Stig

And so, Stig Mogensen just had to say ...

>
> [...]and etc/conf.d/domainname has DNSDOMAIN="homenetwork".

But, is that a "FQDN" (fully qualified domain name)?
--
oNb
Warning: abortion has been proven to be fatal to the fetus.

oldNbald wrote:
>>[...]and etc/conf.d/domainname has DNSDOMAIN="homenetwork".
>
> But, is that a "FQDN" (fully qualified domain name)?

No, it's not. But it is a domain name, and it's fine for a home
network. All the PCs which can't be called something like
"www.kernel.org", still have to have a host name and domain name of some
sort.

And so, Paul Bredbury just had to say ...

> No, it's not. [...]

So, when you're in CLI, or there's an app which shows your DN, does it go
something like mine ? - codybeau.(none) .
--
oNb

oldNbald wrote:
> So, when you're in CLI, or there's an app which shows your DN, does it go
> something like mine ? - codybeau.(none) .

Yeah, it shows me "... .(none)" at login, and "domainname" returns
"(none)" instead of "homenetwork".

Then again, I also have a Gentoo server which supposedly has a FQDN,
with which "domainname" also returns "(none)". However, "dnsdomainname"
returns the expected string.

I've just read a little of
http://www.linux-nis.org/nis-howto/HOWTO/glossary.html , since
"domainname" cares about NIS ("Network Information Service") rather than
DNS.

Home users would need to "emerge ypserv" to set up NIS, for zero benefit
that I can see. It's for sharing passwords between PCs in a workgroup,
to allow hot-desking, it seems.

I'm surprised that Linux by default uses NIS to determine the domain
name, rather than DNS.

And so, Paul Bredbury just had to say ...
[...]
> Home users would need to "emerge ypserv" to set up NIS, for zero benefit
> that I can see.[...]

Yes, this is home-based stand-alone system for a single family and there's
no need for ypserv, plus, everything is working as desired. Think I'll
leave well enough alone
--
oNb

Stig Mogensen <norman_bates@linuxmail.org> wrote:
> Upon boot, I get the kernel messages saying that etc/hostname should
> no longer be used, and I should switch to etc/conf.d/hostname. Same
> goes for etc/dnsdomainname and etc/conf.d/domainname.
>
> How is that done?.
>
> Can I jst delete the /etc/hostname and /etc/dnsdomainname files, and
> add the appropriate "tux" and "homenetwork" entries as explained in
> the installdocs, and keep domainname in my default runlevel?.

Yes, and no. Unfortunately, the switch to /etc/conf.d/domainname was
ill thought out, or rather, the warning message was not thought through.
There's apps that *depend* on /etc/hostname being present, among them
yp-tools.

My advice: Leave the /etc/hostname entry, and duplicate (or create a
symlink/hardlink) in /etc/conf.d/ (until the devs sort out their mess
and revert back for compatibility reasons :-))

Regards,
--
*Art

Paul Bredbury <i@hate-spam.com> wrote:
>
> I've just read a little of
> http://www.linux-nis.org/nis-howto/HOWTO/glossary.html , since
> "domainname" cares about NIS ("Network Information Service") rather
> than DNS.
>
> Home users would need to "emerge ypserv" to set up NIS, for zero
> benefit that I can see. It's for sharing passwords between PCs in a
> workgroup, to allow hot-desking, it seems.

NIS (YP) is a lot more than that. It allows sharing any kind of map
files, and the most common use is for sharing a hosts file and automount
maps. It's also useful for other things, like sharing printcap and
aliases.

It's most useful when combined with dhcpd, NFS and autofs.

> I'm surprised that Linux by default uses NIS to determine the domain
> name, rather than DNS.

It doesn't.

The domain name queries carried out by gethostbyname() and
gethostbyaddr() use a combination of any or all of the
name server named(8), a broken out line from /etc/hosts,
and the Network Information Service (NIS or YP), depending
upon the contents of the order line in /etc/host.conf.
(See resolv+(8)). The default action is to query
named(8), followed by /etc/hosts.

Regards,
--
*Art