🚀 go-pugleaf

In article <1992Aug19.194102.3029@kakwa.ucs.ualberta.ca>, dave@nakiska.ucs.ualberta.ca (David Ross) writes:
|> In article <1992Aug18.153253.3473@midway.uchicago.edu>  
|> eer1@midway.uchicago.edu(Paul Woods) writes:

[munch]

|> > to change it on several of my NeXT's.  HOW DO I PATCH THE OS SO THAT IT  
|> WILL  
|> > ALLOW ME TO CHANGE THE HOSTID.  I am not a programmer (not really  
|> anyway) so  
|> > please keep it on a very simple level.
|> > 
|> > Thanks,
|> > 
|> > Paul-
|> 
|> Hi Paul.  You can't change the hostid of a Sun or a NeXT.  (Unless there  
|> is some sort of magical system patch to do it). I missed your previous  
|> posting so I don't really understand why you would want to.
|>  

[munch]

|> 
|> The system call sethostid(2) doesn't really seem to work (there's no man  
|> page for it either).  In generic BSD I assume it is possible to set your  
|> hostid.  In fact I know it is on some machines - I've done it.  However  

[munch]

Well, err. Not quite right. Mach actually has the ability to change
the host id with 'sethostid()', but NeXT chose to disable that feature.
Eric P. Scott found out which table entry has to be patched in NS 2.1.
The output of 'cmp -l /sdmach.old /sdmach' on my machine would give
(it does _not_, as there are some other patches as well...):

sdmach.binpatch:
---- CUT HERE ----
579602   0   1
579607 240 217
579608 214 206
---- CUT HERE ----

This will re-enable the 'sethostid()'-call. For information on how to
apply the patch and some other kernel hacks, see my recent postings
on comp.sys.next.software (topic: RAMDISK).


cheers, Uwe

Uwe Meyer-Gruhl                      "Close female relative wear combat boots"
Lehrstuhl Informatik IX
Technische Universitaet Muenchen     email:MeyerGru@Informatik.TU-Muenchen.DE
Orleansstr. 34, D-8000 Muenchen 80   tel: ++49 89 48095-209