[106] in netbsd-help mailing list archive

home help back first fref pref prev next nref lref last post

Re: su and reactivate

daemon@ATHENA.MIT.EDU (John Hawkinson)
Wed Mar 15 00:35:27 1995

Date: Wed, 15 Mar 95 00:35:07 -0500
To: yoav@MIT.EDU
Cc: bdrosen@livewire.mit.edu, netbsd-help@MIT.EDU
In-Reply-To: "[104] in netbsd-help mailing list archive"
From: John Hawkinson <jhawk@MIT.EDU>


Brett asked:

>  No Hesiod information available for livewire.mit.edu
>  No Hesiod information available for livewire.mit.edu
> 
> is there any way to avoid this other than getting hesiod
> info added for my host?i  ie hack the scripts?
> has anyone done this ?

Yoav suggested:

} yes.. you can get rid of the hesiod thing rather easily..
} create (or just add to) the file
} 	  /etc/namedb/named.local
}  
} the following line:
} livewire.cluster.ns.athena.mit.edu. 99999999 HS TXT "lpr ajax"

I think this is a poor recommendation/situation. The problem is that
/etc/athena/save_cluster_info is called by reactivate, and will fail
unlessthere's cluster info.

It's generally an unreasonable requirement for us to expect computers in
dorms to have cluster information, and as such, the port should not
require it to behave sanely.

[Incidently, using ajax is probably a really poor idea for livewire]

As such, we ought to fix reactivate to not complain, and provide some
sane default (not an athena printer). Since the only use of cluster information
for NetBSD at present is printer info, we might forgo it entirely.
I dunno. Followups to netbsd-dev, I guess...

--jhawk

home help back first fref pref prev next nref lref last post