Nameserver side effects

Andrew Cherenson arc at kaibab.wpd.sgi.com
Mon Jun 24 14:28:40 AEST 1991


In article <1991Jun23.145151.8517 at cs.dal.ca> silvert at cs.dal.ca (Bill Silvert) writes:
>using a fully qualified name in /etc/sys_id, i.e. editing it to read
>"biome.bio.ns.ca" instead of just "biome".  This turns out to have an
>unfortunate side effect though -- uname now returns the first 8
>characters, namely "biome.bi", which confuses all kinds of software.
>For example, I can no longer uucp to other systems, since they don't
>recognize "biome.bi".

Fixed in IRIX 4.0: uname strips the domain.

>I hacked this by putting in a couple of hostname calls in uudemon.poll,
>but this is pretty crude.  I'm wondering whether anything else got
>broken in the process.  Anyone know a clean way out of this?  There
>seems to be a lot of ambiguity about when a fully qualified name is
>needed.  For now I just changed /etc/sys_id back to "biome" and use
>/usr/etc/resolv.conf to solve my nameserver problems, but I wonder if
>there is any way to use a fully qualified hostname without breaking uucp?

The following line in /usr/etc/resolv.conf should work:
domain bio.ns.ca



More information about the Comp.sys.sgi mailing list