Slackware vs nn: 'You need a fully qualified domain name'?

[andrew]

Hi,

Has anybody found a resolution to the demands by nn for a fqdn under
slackware when one is already set. I have used an elaborate script to
keep /etc/resolv.conf updated and nn content but there must be a better
way?

Andrew

--
echo 'hfrarg...@tznvy.pbz' | \
tr 'A-M N-Z a-m n-z' 'N-Z A-M n-z a-m'

[Aaron W. Hsu]

andrew <and...@skamandros.invalid> writes:

>Has anybody found a resolution to the demands by nn for a fqdn under
>slackware when one is already set. I have used an elaborate script to
>keep /etc/resolv.conf updated and nn content but there must be a better
>way?

Normally this isn't a problem because you can work around it, but
if I recall correctly, I got around it by editing my hostname value
such that it would return a full domain rather than just the first
part of the domain. I think this was easiest for me. The main issue
is just getting hostname(1) to give out the full name when you
run it without commands. If you can do that, I think NN behaves.

IIRC, this has to do with the way NN and gethostname() work or some
such thing. In normal UNIX, the full domain name is returned, whereas
in Linux/Slackware, only the first part of the name is returned.

There are easy solutions to this problem, but for the life of me, I
do not remember them. It has been too long since I worked on it.

--
Aaron W. Hsu <arc...@sacrideo.us> | <http://www.sacrideo.us>
"Government is the great fiction, through which everybody endeavors to
live at the expense of everybody else." -- Frederic Bastiat
+++++++++++++++ ((lambda (x) (x x)) (lambda (x) (x x))) ++++++++++++++

[Bob Vloon]

Hi Andrew,

> Has anybody found a resolution to the demands by nn for a fqdn under
> slackware when one is already set. I have used an elaborate script to
> keep /etc/resolv.conf updated and nn content but there must be a better
> way?

For me adding the line "domain my.domain.name" to /etc/resolv.conf was
sufficient (Debian Etch / Lenny).

Regards,

Bob