ftp.nice.ch/peanuts/GeneralData/Usenet/news/1989/CSN-89.tar.gz#/comp-sys-next/1989/Oct/usr-ucb-w

This is usr-ucb-w in view mode; [Up]


Date: Sun 29-Oct-1989 23:53:50 From: Unknown Subject: /usr/ucb/w Remember /usr/ucb/w? And uptime? On my NeXT just recently running 1.0, these are broken -- the error I get is: No namelist I turned on accounting with accton (hey, it was all I could think of) and that seemed to fix nothing. What am I missing?
Date: Sun 01-Nov-1989 07:31:03 From: Unknown Subject: Re: /usr/ucb/w In article <10824@csli.Stanford.EDU> dmr@csli.stanford.edu (Daniel M. Rosenberg) writes: >Remember /usr/ucb/w? And uptime? On my NeXT just recently running 1.0, >these are broken -- the error I get is: >No namelist > >I turned on accounting with accton (hey, it was all I could think of) >and that seemed to fix nothing. > >What am I missing? > There seems to still be a problem with $BOOTFILE (at least on client machines . . .). Here's what I did: (looking at ls -l /*mach*) lrwxrwxrwx 1 root 6 Oct 2 16:48 /mach -> sdmach lrwxrwxrwx 1 root 9 Sep 30 13:25 /mach.dist -> $BOOTFILE -r-xr-xr-x 2 root 562868 Sep 11 19:07 /odmach -r-xr-xr-x 2 root 562868 Sep 11 19:07 /sdmach (i.e., mv mach mach.dist; ln -s sdmach mach) I had to do this on the server, and then reboot various machines . . . Tom Carter tom@csustan.csustan.edu >From: jst@cca.ucsf.edu (Joe Stong)
Date: Sun 04-Nov-1989 06:49:05 From: Unknown Subject: Re: /usr/ucb/w In article <1989Nov1.073103.20961@csustan.CSUStan.Edu> tom@csustan.csustan.edu (Tom Carter) writes: >In article <10824@csli.Stanford.EDU> dmr@csli.stanford.edu (Daniel M. Rosenberg) writes: >>Remember /usr/ucb/w? And uptime? On my NeXT just recently running 1.0, >>these are broken -- the error I get is: >>No namelist > >There seems to still be a problem with $BOOTFILE (at least on >client machines . . .). We had the problem in 0.9, but it's gone (for us) in 1.0. There must be a subtle difference... symlinking offends my sensibilities; here's what I did in 0.9, you might find the concept applicable now. (Didn't NeXT promise in 0.9 that 1.0 would provide a way to "cleanly" set metalinks?) This went in /etc/rc on the clients. -=EPS=- P.S. why is "rup localhost" broken in 1.0? ------- fake_BOOTFILE.c /* * Set $BOOTFILE metalink for diskless NeXT under 0.9 * Eric P. Scott, SFSU Academic Computing, June 1989 * * Usage: fake_BOOTFILE system value [verify] * example: fake_BOOTFILE /sdmach sdmach /mach * * To compile: * cc -O -o fake_BOOTFILE -s -bsd fake_BOOTFILE.c */ #include <stdio.h> #include <nlist.h> struct nlist nl[]={ { { "_boot_file" }, 0, 0, 0, 0 }, { { (char *)NULL }, 0, 0, 0, 0 } }; main(argc, argv) int argc; char *argv[]; { long lseek(); register int k; char bf[64]; if (argc>=3&&argc<=4&&nlist(argv[1], nl)==0&& (k=open("/dev/kmem", 2))>=0) { (void)lseek(k, nl[0].n_value, 0); (void)read(k, bf, sizeof bf); if (argc<4||!strncmp(bf, argv[3], sizeof bf)) { (void)lseek(k, nl[0].n_value, 0); (void)write(k, argv[2], strlen(argv[2])+1); _exit(0); } } _exit(1); } >From: walters@chance.uucp (Chris Walters)

These are the contents of the former NiCE NeXT User Group NeXTSTEP/OpenStep software archive, currently hosted by Marcel Waldvogel and Netfuture.ch.