HDTenEightyP/NetNews huggingface dataset:
From: kgnome@cs.concordia.ca (MATIS stephane)
Subject: Re: Help! Installing 3.0 on external HD
Organization: Computer Science, Concordia University, Montreal, Quebec
Date: Sun, 10 Jan 1993 03:40:40 GMT

Hello Folks!

	I have a related question. I have just installed 3.0 on my
external Fujitsu 2624F and decided to make the internal Quantum into a
swapdrive. But, I wanted a 50/50 disk.

	So, I go off to format and build the Quantum and the "partition"
button is hazed. Why ? Ok, I ignore it, and build the disk with
"swapdisk" as name.

	No problemo ?... ok it worked but then during boot-up I get
lot's of complaints from the machine (cannot swap to
/private/vm/swafile.front) and it seem to swap to external.

	Finally, with all this... I cannot get the "recycler" to work.

	My questions are :

	1. How can I get my internal quantum to partition 50/50, so that
	   I can build half for emergency boot and the other for
	   swapping.

	2. Why am I having "recycler" problems.

	Thanks folks...


+---------------------------------+   ___     ___       ___
| Stephane I. Matis               |  /   \_BATLLETECH  /\__\ Viva NeXT! 
| E-Mail : kgnome@cs.concordia.ca |  \___/   \___/     \/__/ NeXTSTEP 3.0!
| "It Just Works..." - Steve Jobs |      \___/   
+---------------------------------+       Wolfnet Operative & NeXThead
From: ambi@it-next2.bu.edu (Mike Amirault)
Newsgroups: comp.sys.next.sysadmin
Subject: Re: URGENT HELP: restore with od's not working!!
Date: 11 Jan 93 00:24:11 GMT
Reply-To: ambi@it-next2.bu.edu

In article <106628@bu.edu> ambi@it-next2.bu.edu (Michael Amirault) writes:
> 
>  Here's the problem:
> 
>  I performed a level 0 dump using the following command:
> 
> 	% dump 0o /dev/sd2a
> 
>  This dumped the contents of the drive to two NeXT optical disks.
>  However when doing a restore via:
> 
> 	% restore rjvf /dev/od1a
> 


 I figured out the problem. Doind a restore with the command:

% restore rjvf /dev/rod1a    

 will work and eject the disk, whereas the command:

% restore rjvf /dev/od1a

 will not eject the disk...

mike
Newsgroups: comp.sys.next.sysadmin
From: jchin@prodigy.bc.ca (Joseph Chin)
Subject: Re: sendmail problem
Reply-To: jchin@prodigy.bc.ca
Organization: Prodigy Technologies Corp.
Date: Thu, 7 Jan 1993 22:29:22 GMT

In article <1993Jan7.222028.4493@prodigy.bc.ca> jchin@prodigy.bc.ca  
(Joseph Chin) writes:
> I've just noticed that since I upgraded to 3.0, I can no 
> longer send email to accounts within my domain 
> (prodigy.bc.ca). Is there a bug in the 3.0 sendmail.cf 
> file? The NeXT is a mail client on the network, and the 
> mail host is a Sun Sparc server. Everything worked fine 
> before the 3.0 upgrade. 

I forgot to add that the following was found in the  
/usr/spool/mqueue/syslog file:
Jan  7 13:39:25 johnette sendmail[942]: AA00939: to=jchin, delay=00:00:04,  
stat=Service unavailable, mailer=etherl

Joe
--
Joseph Chin				Prodigy Technologies Corp.
jchin@prodigy.bc.ca (NeXTmail welcome)	Vancouver, British Columbia
phone 16046874636 / fax 16046871671	Canada
 **** "Heaven won't take me and Hell's afraid I'll take over!" ****
Newsgroups: comp.sys.next.sysadmin
From: tilley@ccu.umanitoba.ca (Richard Tilley)
Subject: Re: Need help on discovering cause of kernel crashes.
Organization: University of Manitoba, Winnipeg, Canada
Date: Tue, 5 Jan 1993 22:42:20 GMT

In <1993Jan2.174935.418@znext.cts.com> zeke@znext (james dehnert) writes:

>  My ususally robust 040' 3.0 system seems to be crashing at will latley.  I  
>keep getting "mach: trap:" and "mach: panic: (Cpu 0) illegal instruction"  
>errors in /usr/adm/messages, but I dont know how to discover what is causing  
>these errors.  I have been using Mamakos SLIP lately, but I'm sure I would have  
>seen alot of trafic on the subject if that was causing system crashes.
>  Can anyone tell me how to trace these problems, or which FM to R?

I get these if I try to start WindowServer on a headless cube.
SLIP not involved. Please summarize anything you find.
-- 
This space is not blank!
Newsgroups: comp.sys.next.sysadmin
From: sherwood@space.ualberta.ca (System Administrator)
Subject: Re: fstab entry for a CDROM
Organization: University Of Alberta, Edmonton Canada
X-Newsreader: TIN [version 1.1 PL6]
Date: Wed, 6 Jan 1993 18:16:55 GMT

Brian Lakeman (lakeman@drifter.acm.ndsu.NoDak.edu) wrote:
: I'm going to export my cdrom to other machine on the network, but the 
: cdrom is ejected everytime someone logs off of the console.  I tried  
: copying the fstab entry I get from 'mount -p' into /etc/fstab and loading
: that, but that didn't work.  I tried mounting it from a shell, but I had 
: no success.
: 
: Any help would be greatly appreciated.
: 
: -Bri
: 
Try this:
	While no one is logged in, insert the CD.  Now log in over the net
and do an explicit mount where you want it.  This should stay put.

	Warning:  To date I've not found a way to disable the eject button.
If another Unix box has the cd mounted by nfs, things can get sticky if you
eject a disk that someone else is looking at.  Good candidates for automounts.
--
=> Sherwood Botsford                   sherwood@space.ualberta.ca <= 
=> University of Alberta         Lab Manager, Space Physics Group <=         
=> tel:403 492-3713                             fax: 403 492-4256 <=         
Newsgroups: comp.sys.next.sysadmin
From: yann@dagobah.fdn.org (Yann Lechelle)
Subject: Re: Console -PowerOffDisabled option wont stay in effect (OS 3.0)
Reply-To: yann@dagobah.fdn.org
Organization: Individual
Date: Tue, 12 Jan 1993 10:11:08 GMT

to answer Douglas Scott:

have you tried the default database instead of the ttys file ? It works  
for me, at least.

---
/ ================================================= \
\ Yann Lechelle                     (Paris, FRANCE) /
/ yann@dagobah.fdn.org               Email/NeXTmail \
\ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ /
/ "grep me no patterns and I'll tell you no lines." \
\ ================================================= /
-- 
/ ================================================= \
\ Yann Lechelle                     (Paris, FRANCE) /
/ yann@dagobah.fdn.org               Email/NeXTmail \
\ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ /
From: chwe@chwe1.spc.uchicago.edu (Michael Suk-Young Chwe)
Newsgroups: comp.sys.next.sysadmin
Subject: Help! Installing 3.0 on external HD
Date: 5 Jan 93 22:28:22 GMT
Reply-To: chwe@quads.uchicago.edu
Organization: University of Chicago Computing Organizations

I have been having all sorts of problems installing system 3.0
on my external hard disk.  Before trying to upgrade, I had system 2.1
on both my internal (105M Quantum from NeXT) and external (1G Fujitsu)--
the external's SCSI ID was set up so that it would be the default
bootup drive.
After plugging in a friend's CD-rom with the 3.0 CD, and running 
UpgradePrep.app from the CD-Rom tools diskette, it took me a long
time to get the computer to read the CD-rom.  Finally it did and I
did the automatic installation on my external drive, which seemed
OK.  But after installation, booting from my external drive 
puts me into a System Panic window, which eventually stops and
then tries to boot again.  I tried booting from the CD-rom as detailed
in the manuals but this did not work either.  If I unplug the external
and CD-rom I can still boot up from my internal drive, luckily.  
Currently I can't access my external drive at all (I've tried
bsd(1,0,0) from the ROM Monitor to boot from my internal drive, 
but I haven't tried changing the SCSI ID of the external drive,
which involves opening the enclosure and moving the jumpers).

Any help or suggestions would be very much appreciated!  I've been
out of the country for the last four months so I haven't been able 
to keep up with the current folklore on system 3.0--so excuse me if
this is an old question.  Please repost or send email (regular,
not NeXT) to chwe@chwe1.spc.uchicago.edu.

Thanks in advance,
Michael Chwe
Dept of Economics
University of Chicago
Newsgroups: comp.sys.next.sysadmin
Subject: HELP popper
From: frank@ifi.unibas.ch (Robert Frank)
Date: Mon, 11 Jan 1993 16:02:06 GMT
Reply-To: frank@ifi.unibas.ch
Organization: Institut fuer Informatik
Keywords: popper

Uff! I guess I should have paied attention to all help requests about running  
popper on the NeXT. I am now in the position to have to run the POP 3 protocol  
on NeXTStep 3.0. 

I have some sources which will compile without problems (inserted one missing  
'char' type declaration) and which will actually start. But if I try to connect  
to the popper (inetd and services properly configured and niloaded), it just  
dies without any warning or error. Debuggin is enabled, but nothing shows up in  
the log files.

Any help would be greatly appreciated! Thank's in advance.

P.S. If mail returns errors, you may asume that it arrived any way. We are  
currently reconfiguring our servers, which causes some problems.
--
Robert Frank                         tel. + (061) 321 99 67                 
Institut fuer Informatik             fax  + (061) 321 99 15                 
University of Basel, Switzerland                                            
Mittlere Strasse 142      rfc822: frank@ifi.unibas.ch (NeXT mail accepted)  
CH-4056 Basel          X400: S=frank;OU=ifi;O=unibas;P=switch;A=arcom;C=ch
Newsgroups: comp.sys.next.sysadmin
From: ambi@it-next2.bu.edu (Michael Amirault)
Newsgroups: comp.sys.next.sysadmin
Subject: URGENT HELP: restore with od's not working!!
Date: 9 Jan 93 18:02:58 GMT


 Here's the problem:

 I performed a level 0 dump using the following command:

	% dump 0o /dev/sd2a

 This dumped the contents of the drive to two NeXT optical disks.
 However when doing a restore via:

	% restore rjvf /dev/od1a

 It will read and restore the first disk fine but then won't eject
 the first disk when it needs the second. It keeps reporting that the
 disk in the wrong one.  HELP!!  How do I get my data off of the second
 disk?? I've tried all sort of permutations of the restore command and
 all of them fail when the program says it's ejecting the first disk
 and waiting for the second but never actually ejected the first disk.

 This problem is with a NeXTCube '040 running NeXTStep 3.0.

 Any help would be greatly appreciated!

 Mike
From: f_cnnghamjk@ccsvax.sfasu.edu
Newsgroups: comp.sys.next.sysadmin
Subject: a way to warn the console user
Date: 12 Jan 93 20:50:07 CST
Organization: Stephen F. Austin State University

Can someone suggest a way to warn the console user that I'm about to reboot
the machine? Write, talk or shutdown are great ONLY IF s/he has Terminal 
running.
 
I've tried using Alert from ShellPanels, but I'm told...
 
    DPS client library error: Could not form connection, host local host
 
Thanks.
 
Randomly, Kelly Cunningham
<deviate@lipschitz.sfasu.edu><f_cnnghamjk@ccsvax.sfasu.edu><jkellyc@tenet.edu>
 NeXTMail (favored) MIME (ok)     VMS Mail (tolerated)          MIME (ok)
"There is no reason for any individual to have a computer in their home."
               -- Ken Olson, President and visionary, Digital Equipment, 1977
"NeXTSTEP is probably the most respected piece of software on the planet."
                                                -- October 1992 Byte Magazine
From: matthews@oberon.umd.edu (Mike Matthews)
Newsgroups: comp.sys.next.sysadmin
Subject: Re: Help! Installing 3.0 on external HD
Date: 11 Jan 93 01:30:16 GMT
Organization: Los Alamos National Laboratory, NM

In article <1993Jan10.170814.9221@znext.cts.com> zeke@znext.cts.com writes:
>  so the syntax should be 
>	'b sd(0,2,0)' to boot off of sd2 partition a.  The NeXT only has one  
>controller ( unless you have an extra cpu card a la Spherical ) an that one  
>defaults to 0.  The syntax provided would probably confuse the system, and the

Um, no.  The first number is the SCSI ID, the second is the LUN (which lots
of people theorize will always be 0 on the NeXTs because they only have one
SCSI channel; makes sense to me but I can't confirm or deny it personally),
and the last is the partition number.

It loads the boot block off the device you ask for (it *may* check all
devices if the first one fails, but my experience with that suggests it
doesn't), and then it boots the kernel off of whatever device has it,
starting with the one you specify (e.g. a bsd(2,0,0) will check SCSI ID 2 for
a kernel, and if it can't find that, it'll check the rest of your devices).
-a will indeed ask you for the rootdevice, but you can always

bsd(2,0,0)- rootdev=sd1

Note the dash and the space.  You can replace the dash with 'sdmach' as well,
which is what the ROM monitor does for you, assuming a SCSI disk.

Be forewarned that if your root device is NOT /dev/sd0a, /etc/fstab is
incorrect and when you try to do a mount -o remount,rw / in /etc/rc.boot, it
ain't gonna work very well.

>  Zeke

I've booted off of non-sd0 devices before, and I know the syntax is
bsd(x,0,0) where x is the SCSI ID.  The other stuff I'm extrapolating from
the "nbuf" hack as I always used -a when I had to specify an alternate root
partition.
------
Mike Matthews, matthews@oberon.umd.edu (NeXTmail accepted)
------
Nothing recedes like success.
		-- Walter Winchell
From: joe@mathcs.emory.edu (Joe Christy)
Newsgroups: comp.sys.next.sysadmin
Subject: Thick vs. Thin 3.0
Date: 8 Jan 1993 17:01:14 -0500
Organization: Mathematical Sciences Research Institute
Distribution: world
NNTP-Posting-Host: emory.mathcs.emory.edu
Summary: What's the difference

Does anyone have a diff of the files in NeXTStep 3.0 as installed on a
400Meg disk as compared to what gets installed on a 100Meg disk?

Joe Christy   |      Head of Mathematical Computing      | Two wrongs
joe@msri.org  | Mathematical Sciences Research Institute | don't make a right,
(510)643-6069 |          1000 Centennial Drive           | but three lefts do
**************|           Berkeley, CA 94720             |********************
From: fxg@balmuff.informatik.rwth-aachen.de (Felix Gatzemeier)
Newsgroups: comp.sys.next.sysadmin
Subject: Where is the Window Server port in 3.0?
Date: 4 Jan 93 08:17:41 GMT
Organization: Rechnerbetrieb Informatik - RWTH Aachen
NNTP-Posting-Host: balmuff.informatik.rwth-aachen.de
Summary: Loginwindow says: "Can't find WindowServer Port" NSWSd isn't in 3.0.

Panic!

After trying to build a tiny Network (one NeXTstation, one os/9 machine) and some
fatal chowning (chown myname .*), the NeXT boots fine until it hits Loginwindow,
which states that it can't find the window server port. This port seems to have
been provided by a NSWSd in NS 2.x, but this is no longer the case (man page says:
no longer supported).
After a lot of re-chowning from a working system and the CD-ROM, nothing changed.
So we booted from the CD and reinstalled NS 3.0. No change.
We noticed that init starts the window server, then loginwindow, in the working
system. On the chrashed system, init is started with an argument -x, on the
working one with -xx.

Any ideas on that? Where IS the Window server port now? What ARE the init arguments?

Thanks,

   Felix

(please reply by email (non-NeXT), I'm not that frequently on the net. I will
summarize when the problem is solved. email: fxg@pool.informatik.rwth-aachen.de)

Newsgroups: comp.sys.next.sysadmin
From: eoliver@ralph.cs.haverford.edu (Erik Oliver)
Subject: Re: rc.local
Organization: Haverford College Computer Science Department
Date: Sat, 9 Jan 1993 16:22:04 GMT

In article <1993Jan8.150428.29811@neptune.inf.ethz.ch> rpajarol@iiic.ethz.ch (Renato Bruno Pajarola) writes:
>Hi people,
>since I have the new NextStep3.0, over all it's very good, I can't do
>some things I did bevore.
>
>Especially things I want to do at boot-up time.
>
>In NS2.1 I had entries in the rc.local to play a sound and to power the
>printer off. The entries looked something like this:
>
>sndplay /LocalLibrary/Sounds/mysound.snd &
>
>...
>
>nppower off
>
>...
>
>

As a rule of thumb, you should include full paths in 'rc' and 'cron'
run scripts because frequently environment variables that might normally
assist unix in finding executables are not avaialable.  

Peraps under 2.0 either the PATH environement was set somehow by the
time rc.local ran or these executables were stored somewhere different,
I can't say.

But, I would suggest trying to type the whole path out:
eg: /usr/bin/runthisapp 

Etc.  Also, there may be some issues involving when disk mounting occurs
preventing the sounds from playing.  (I can't really say.)

-Erik
From: louie@sayshell.umd.edu (Louis A. Mamakos)
Newsgroups: comp.sys.next.sysadmin
Subject: Re: Help! Installing 3.0 on external HD
Date: 12 Jan 1993 19:04:31 GMT
Organization: The University of Maryland, College Park
NNTP-Posting-Host: sayshell.umd.edu

In article <17898@umd5.umd.edu> matthews@oberon.umd.edu (Mike Matthews) writes:
>In article <1993Jan10.170814.9221@znext.cts.com> zeke@znext.cts.com writes:
>>  so the syntax should be 
>>	'b sd(0,2,0)' to boot off of sd2 partition a.  The NeXT only has one  
>>controller ( unless you have an extra cpu card a la Spherical ) an that one  
>>defaults to 0.  The syntax provided would probably confuse the system, and the
>
>Um, no.  The first number is the SCSI ID, the second is the LUN (which lots
>of people theorize will always be 0 on the NeXTs because they only have one
>SCSI channel; makes sense to me but I can't confirm or deny it personally),
>and the last is the partition number.

Um, close. :-)  The first number is the SCSI controller target number
(usually referred to as the "SCSI ID"), the second is the logical unit
number and the third the partitition number of the disk.

The LUN has nothing to do with the NeXT; it is used when the addressed
SCSI controller on the SCSI bus has more than one unit attached to it.
In days past, when disks didn't have embedded SCSI controllers, you'd
have a seperate SCSI controller on the bus which could have one or
more {ESDI, SMD, ST-506} drives attached to it.  The LUN (Logical Unit
Number) could be used to select amongst the units/disk attached to the
controller.

Louis Mamakos

Newsgroups: comp.sys.next.sysadmin
From: CCGREG@mizzou1.missouri.edu (Greg Johnson)
Subject: Upgrading to 3.0 from bottom up hasn't yet worked for me
Organization: University of Missouri
Date: Tue, 05 Jan 93 14:14:12 CST

We have a 3-level netinfo network with about four midlevel application
servers and 60 machines.  Most user definitions and home mounts are at
the top level.  I thought I'd be least disrup.tive to upgrade to 3.0
from the bottom up.  Upgrading a couple of lowest level machines
worked fine.  But when I upgraded a midlevel host (in place, not
from a clean disk), access problems occur.  Users with homes in
the midlevel's domain still work ok, but users with homes elsewhere
cannot access their homes.  They can login, but get a blank screen.
Root can see the list of homes on a remote file system, but can't go
further down as it could before.
 
Here's a representative fstab entry from the top level:
     mugcnx1:/Users /Net nfs rw,net,timeo=14,intr,noquota 0 0
 
Here's the 2.0 exports line:
     /Users -access=allmunx,root=mugcnx1:mugcnx2:muebnx1:     ...etc..
 
mugcnx1 is the 2.0 toplevel, muebnx1 is the 3.0 midlevel.
 
Another irritating thing.  In using UserManager.app from the 3.0 midlevel
host to a 2.1 toplevel netinfo passwd server, the app locks.  "ps" shows
it is trying to readUserLanguage.  3.0 netinfo data for user adds an
"info" directory, and it looks like UserMangler is trying to access a
dwrite for System Language--somewhere.
 
I guess I'll go ahead and upgrade the toplevel server, and hope that
this will solve the problems.  I hope this is not some idiot little
item this idiot has overlooked, or that somewhere it says "upgrade
networks from the top down".  For the curious, I can provide nidump &
nilist output.  If anybody has insight,reply direct, I'll summarize.
If anybody is contemplating a similar upgrade, well, stay tuned.
 
:  Greg Johnson, Senior Scientific Programmer/Analyst -- Campus Computing
:  233 Heinkel Building, University of Missouri, Columbia, MO 65203
:  ccgreg@mizzou1.missouri.edu / ccgreg@monad.missouri.edu / 314-882-2000
Newsgroups: comp.sys.next.sysadmin
From: harit@kripalu.com
Subject: NeXTMail and .signature file
Reply-To: harit@kripalu.com
Organization: Kripalu Center
Date: Tue, 5 Jan 93 13:26:08 GMT

Under 3.0 NeXTMail is not using the .signature file to append my name to  
messages.  News does this and I thought 2.0 mail did.  I did change sendmail.cf  
files in the process when I switched to PSI net.  If anyone can suggest how to  
get this to work, or sone equivelent I would appreciate it.

-- 
Michael Allen Latta
Kripalu Center
harit@kripalu.com
(413)448-3288
Newsgroups: comp.sys.next.sysadmin
From: vasco@bvl.pt (antonio vasconcelos)
Subject: Re: HELP popper
Organization: Bolsa de Valores de Lisboa
X-Newsreader: Tin 1.1 PL4
Date: Tue, 12 Jan 1993 10:05:01 GMT

frank@ifi.unibas.ch (Robert Frank) writes:
: to the popper (inetd and services properly configured and niloaded), it just  
: dies without any warning or error. Debuggin is enabled, but nothing shows up in  
: the log files.

What about /etc/syslog.conf ??? Have you add the propper lines ?
This is the line I added to mine, (under NS 2.2)

	local0.notice;local0.debug	/usr/spool/mqueue/POPlog

Have o tried:

	telnet localhost 110 

The popper should show up and send a message to your terminal, you
can end the connection just typing 'quit' (no quotes) and ENTER.

Like this...
***********************************************************
~> telnet localhost 110
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
+OK UCB Pop server (version 1.7b1) at jessica.bvl.pt starting.
quit
+OK Pop server at jessica.bvl.pt signing off.
Connection closed by foreign host.
~>
***********************************************************

If the popper don't show up, try telnet to port 109, 109 is the pop2
port, maybe your /etc/services is not correct. (Or maybe is something
with NS 3.0, in that case, forget everything I said... I don't know
nothing about it).

: Any help would be greatly appreciated! Thank's in advance.

I hope this helps...

-- 
regards,
  ____
|/asco
----------------------------------------------------------------------
Newsgroups: comp.sys.next.sysadmin
From: Zacharias J. Beckman <zac@dolphin.com>
Subject: HELP: NS 3.1 Boots Only in Single-User Mode!
Reply-To: zac@dolphin.com
Organization: Dolphin Software
Distribution: usa
Date: Thu, 7 Jan 1993 16:49:53 GMT

Hello,

A few days ago, our server had a horrible crash.  Everything on the network  
locked up tight and needed to be restarted the hard way.  When the server  
came back up, it refused to boot in multi-user mode.  The boot parameter of  
"-nbu=128" was being ignored, and the default 16 buffers were used.

When the system started to boot Mach, it declared that it couldn't write to  
mtab because the file system was read only!!!  The only way around this at  
present is to boot in single-user mode, then continue the multi-user startup.

Has anyone run into this sort of problem before, or have any idea where I an  
look to cure it?  Thanks in advance.
-- 
Zacharias J. Beckman - Dolphin Software Inc. - zac@dolphin.com - use NeXTMAIL!
To be "matter of fact" about the world is to blunder into fantasy.... and dull
fantasy at that, as the real world is strange and wonderful. --- R. A. Heinlen
Those opinions I express herein are my own, I'm fairly sure. --- Z. J. Beckman