HDTenEightyP/NetNews huggingface dataset:
From: andy@orchid.bdc.ubc.ca (Andrew Dwelly)
Subject: Postscript Printer Description
Organization: University of British Columbia, Vancouver, B.C., Canada
Date: Thu, 1 Oct 1992 20:04:02 GMT


Ever since I upgraded to NS 3.0, bioth enscript and the print manager
have been complaining that the printer description files for our 2 
remote printers are missing.

The enscript documentation mentions these file but does not describe them
or where they ought to be. Printing does not seem to be working
properly so they may be fairly important.

Does anyone know anything about the ppd files ?

Andy Dwelly (andy@bcu.ubc.ca)
Newsgroups: comp.sys.next.sysadmin
From: Hal.Varian@umich.edu
Subject: Re: Fast find won't in 3.0
Reply-To: Hal.Varian@umich.edu
Organization: University of Michigan Math Dept
Date: Mon, 5 Oct 1992 01:15:45 GMT

In article <HARDY.92Oct1223541@golem.ps.uci.edu> hardy@golem.ps.uci.edu  
(Meinhard E. Mayer (Hardy)) writes:
> In preparation for the update to 3.0 (and the news that find stopped
> working), i got and compiled gnu find3.07.  Except from a slighly
> different directory structure  (find.codes is now kept in
> /usr/local/lib/locate)it works fine.  One caveat however: if you have
> NFS mounted disks, it may be necessary to remove these from the
> updatedb script; otherwise the sorting and hashing may fill up an
> already swol;len swapfile. 
> 
> --
> Hardy 
> -----
> Meinhard E. Mayer,  Department of Physics, UC Irvine 
> e-mail: hardy@golem.ps.uci.edu (preferred) or MMAYER@UCI.BITNET

I got gnu find and it seems to work well.  However, it only indexes my root  
filesystem.  I have an external SCSI disk, mounted as \Users, and I want it to  
index that as well (or maybe instead of \).  

How do I get updatedb to index \Users?

--
Hal.Varian@umich.edu    Hal Varian
voice: 313-764-2364     Dept of Economics
fax:   313-764-2364     Univ of Michigan
                        Ann Arbor, MI 48109-1220
Newsgroups: comp.sys.next.sysadmin
From: cmumford@iat.holonet.net (Chris Mumford)
Subject: Only 2 Fax Modems in 3.0?
Organization: HoloNet (BBS: 510-704-1058)
Date: Wed, 7 Oct 1992 02:58:35 GMT

Wouldn't it be awesome if NeXT ported NeXTStep to the SGI?
From: borchers@poogh.llnl.gov (Robert R. Borchers)
Newsgroups: comp.sys.next.sysadmin
Subject: Re: AppleTalk and 3.0. It does not work.
Date: 30 Sep 92 16:17:39 GMT

In article <1992Sep29.170327.20939@news2.cis.umn.edu>  
jalegre@htlv.med.umn.edu (John Alegre) writes:
> Has anyone got AppleTalk connections to work under 3.0?
--
I got it working first time, but I have not had time to run down all the  
prooerties. I do, for example, see the hundreds of zones on our network  
and can mount the file structure on my mac, and another one I have access  
to. One interesting thing is that i get the entire file structure on my  
hard disk, hot just the folder that is published under system 7.0.1 I also  
had no problem installing my printer, after i found the correct driver,  
since there are three. Bob

Robert R. Borchers
L-414
Livermore, Ca 94551
borchers@llnl.gov
NeXTmail Welcome
Xref: sparky comp.sys.next.sysadmin:5625 comp.sys.next.software:1960
From: nevai@mps.ohio-state.edu (Paul Nevai)
Newsgroups: comp.sys.next.sysadmin,comp.sys.next.software
Subject: Are the NeXT versions of post-bin, smail-bin, and mail-bin available?
Date: 4 Oct 92 23:14:56 GMT
Reply-To: pali+@osu.edu
Organization: Department of Mathematics, The Ohio State University
NNTP-Posting-Host: ops.mps.ohio-state.edu
Originator: nevai@ops.mps.ohio-state.edu

Are the NeXT versions of post-bin, smail-bin, and mail-bin available (or
equivalent programs for mailing large binary data)? Where? Versions? Please
respond by email. Thanks. Take care...Paul

Paul Nevai                            nevai@mps.ohio-state.edu
P.O. Box 3341                         1-(614)-292-3317 (Office)
Columbus, Ohio 43210-0341, U.S.A.     1-(614)-459-5615 (FAX)
Newsgroups: comp.sys.next.sysadmin
From: cpf@broca.med.virginia.edu(Chris Fall)
Subject: a piddling question
Organization: University of Virginia
Date: Mon, 5 Oct 1992 17:35:03 GMT

When I changed over to 3.0 I moved a lot of stuff around. When I try to open a  
ai file (adobe illustrator) my machine thinks it's a text file. How do I  
reassociate the .ai extension (or any other) with its application?

Chris Fall
Newsgroups: comp.sys.next.sysadmin
From: scott@pascal.geom.umn.edu (Scott S. Bertilson)
Subject: Re: NS 3.0 CD readable on a Sun CDROM?
Organization: Geometry Center, University of Minnesota
Date: Thu, 1 Oct 1992 20:41:35 GMT

In article <1992Sep18.154739.1976@tamsun.tamu.edu>  
Steve.Johnson@math.tamu.edu (Steve Johnson) writes:
> Has anyone successfully mounted the NextStep 3.0 CD on a Sun
> using the Sun CDROM?

  In our experience, it works quite well as long as you don't try
to boot from it.
--
Newsgroups: comp.sys.next.sysadmin
From: haker@whitewater.chem.wisc.edu (Michael  Haker)
Subject: NextAdmin apps crashing on NetInfo server!
Organization: Physical Sciences Lab, UW-Madison
Date: Fri, 2 Oct 92 01:35:58 GMT

The title basically explains our problem.  After upgrading to 3.0 all the  
new NextAdmin applications refuse to run on our NetInfo server.  However  
they do run fine from remote machines.  For example NetInfoManager will  
launch fine but crashes if you try to open a domain.  UserManager crashes  
before it even gets to launch.

Has anyone else run into this kind of problem?  Does anyone have any ideas  
about what might be going on?  We are at wits end, but fortunately we can  
still manage our network remotely.

Thanx
Mike Haker
(e-mail responses prefered	haker@whitewater.chem.wisc.edu)
From: madler@cco.caltech.edu (Mark Adler)
Newsgroups: comp.sys.next.sysadmin
Subject: Re: bug in tar, anyone fixed it?
Date: 6 Oct 92 19:52:18 GMT
Article-I.D.: gap.1asqpiINNpq0
Organization: California Institute of Technology, Pasadena
NNTP-Posting-Host: sandman.caltech.edu


Robert Frank suggests:

>> YEP, GNU! get GNUtar... (it's all over the places, on many different servers)

Actually, it's already on your NeXT 3.0 system.  It's called (suprise)
gnutar.

David Lemson suggests:

>> Also there is some variant of tar that handles >100 char filenames
>> buried in 3.0, in Installer.app.  I think it's called installer_bigtar.

Right.  I linked it to the name "bigtar" in my path, and I use that
to manually extract selected items out of NeXT .tar.Z files inside
.pkg files, since bigtar is what made them.  I do not know if bigtar
and gnutar use incompatible methods for storing longer names or not.
I do know that bigtar and gnutar are different.

Mark Adler
madler@cco.caltech.edu
From: aberno@godel.questor.wimsey.bc.ca (Anthony Berno)
Newsgroups: comp.sys.next.sysadmin
Subject: Sendmail answers.
Date: Fri, 2 Oct 1992 00:54:46 GMT
Reply-To: aberno@godel.questor.wimsey.bc.ca


In response to my own earlier posting about sendmail woes....

The answer is to use the old sendmail and sendmail.cf files from 2.0 or  
2.1. The 3.0 sendmail seems to have problems with UUCP.

-Anthony
From: erickson@oak.mcs.gvsu.edu (Carl Erickson)
Newsgroups: comp.sys.next.sysadmin
Subject: Re: SLIP doesn't like dialins on two different 3.0 systems
Date: 5 Oct 92 17:24:13 GMT
Reply-To: erickson@oak.mcs.gvsu.edu (Carl Erickson)
Organization: Grand Valley State University

In article <15880@umd5.umd.edu> bchin@is-next.umd.edu (Bill Chin) writes:
> In article <1992Oct3.153228.14683@ni.umd.edu> louie@sayshell.umd.edu (Louis  
A. Mamakos) writes:
> >In article <BvIG4M.1wn@sounds.wa.com> BrianW@SoundS.WA.com writes:
> >>Now that he has upgraded to 3.0 also, we both get the following message  
when  
> >>logging into the SLIP account:
> >>
> >>Can't open TTY for "slip1" m
> >>
> >>Does anyone know what might cause this message?
> >
> >louie
> 
> Also make sure that NXFax isn't running - the way it takes over the serial
> ports conflicts with Transys SLIP (haven't tested it with Teleconnect).
> 
> Bill Chin
> 

This problem arises when using older versions of Transys SLIP (older than
920904?) and NXFax 1.02.  Getting the latest copy of SLIP fixed the
problem for me. I believe this will also be fixed in forth-coming releases
of NXFax.

--
  Carl Erickson,  Asst Professor |  Computer Science Dept      
  Grand Valley State University  |  Allendale MI 49401
                                 |     voice (616) 895-2309
   erickson@oak.mcs.gvsu.edu     |       fax (616) 895-3506
From: tim@rri.UUCP (Tim Buck)
Newsgroups: comp.sys.next.sysadmin
Subject: Re: NS 3.0  (NIM dies with Bus Error!)
Date: 1 Oct 92 16:26:04 GMT
Distribution: comp
Organization: Recognition Research Inc., Blacksburg, VA

In article <1992Sep30.140949.2995@msuinfo.cl.msu.edu> henrich@crs.cl.msu.edu (Chuck Henrich) writes:
>Howdy, I just installed 3.0 on my machine here, and everything appears to be
>working okay, except when I try and run the Netinfomanager app It dies with a
>bus error, any ideas?
>
Do the other networking tools (UserManager, HostManager, SimpleNetworkStarter,
etc.) fail as well?

I had this problem when I upgraded -- I ended up having to do a BuildDisk
from the CD-ROM (overwriting the upgrade).

Has anyone else had this problem?

Timothy Buck   --   rri!tim@vtserf.cc.vt.edu OR timbuck@borg.lib.vt.edu
 Recognition Research, Inc. (703) 231-6500	++ NeXTmail accepted ++
------------------------------------------------------------------------
 Hate Blacksburg's weather? Wait an hour.  Hate the season? Wait a day.
From: peter@merlin.acadiau.ca (Peter Steele)
Newsgroups: comp.sys.next.sysadmin
Subject: 10base-T or thinnet?
Date: 5 Oct 92 21:26:53 GMT
Organization: Acadia University

A new staff member recently arrived and brought with her the first
two NeXT stations we've had on campus. I went through the normal
setup for her stations and connected her to ethernet as I we would
any other Unix workstation. I used the 10base-T port on the stations
as that was the type of connection in her office. However, this
did not work. We brought one of the machines to another location and tried
hooking it up to thinnet using the thinnet port on the back of the
workstation and everything worked fine.

We called NeXT and asked if there was something special that had to be
done to make it recognize the 10base-T port and the guy we spoke to
said it was autosensing and should work automatically on either thinnet
or 10base-T. Still puzzled, we contacted the individual who had hooked
up the machines at their previous location and he said he hooked them
up to 10base-T without any trouble, although he seemed to recall having
to set some prom parameter or something to tell the NeXt which port to
use.

What's the true story? NeXT says the ports are autosensing, and
someone has told us they are not. If someone could clarify this
we'd appreciate it very much. Thanks.

--
Peter Steele        Unix Services Manager            peter.steele@acadiau.ca 
Acadia Univ., Wolfville, NS, Canada B0P 1X0  902-542-2201  Fax: 902-542-4364
From: Hal.Varian@umich.edu
Newsgroups: comp.sys.next.sysadmin
Subject: Re: chown under 3.0
Date: 29 Sep 92 00:52:24 GMT
Reply-To: Hal.Varian@umich.edu
Organization: University of Michigan Math Dept

In article <1992Sep29.002311.8323@ni.umd.edu> louie@ni.umd.edu  
(Louis Mamakos) writes:
> In article <1992Sep28.214104.25073@lsa.umich.edu>  
Hal.Varian@umich.edu writes:
> >In article <28SEP92.15351318@enh.nist.gov> aoml@enh.nist.gov  
> >writes:
> >> We just add a new hp drive purchased from TECOR, when ever  
we  
> >change the onwership of user's files, the whole disk's  
ownership  
> >randemly changed back to one
> >> of our user after few seconds.
> >> 
> >>         The command I use is chown -R directory-name
> >> 
> >>         With -R option, chown seem not only going decending  
> >but also going
> >> up to the whole disk.
> >> 
> >>         has anybody experienced that problem ?
> >>         We are using 2 NeXT stations trubo clolrs on a  
small  
> >network
> >> 
> >> aoml,Ying-Yuang Chen
> >
> >The same thing happened to me with my Fujitsu drive.  I was  
> >running 3.0 beta PR2 when it happened, so I decided to wait  
for  
> >the official release before I tried to figure out what was  
going  
> >on.  
> 
> Yes, don't allow the workspace to auto-mount the disk.  When  
it does,
> the file system is mounted such the each file appears to be  
owned by
> the user that's currently logged in.  If you think about it,  
that's
> the correct behaviour for removable media such as a floppy.
> 
> The solution is configure an entry in /etc/fstab and wherever  
the hell
> it goes in netinfo for that file system.
> 
> louie

Well my fstab entry says
  /dev/sd0a / 4.3 rw,noquota,noauto 0 1
  /dev/sd1a /Users 4.3 rw,noquota,noauto 0 2

As far as I can tell from the documentation, this is what I'm  
supposed to say. 

Here's another strange thing that might help isolate the  
problem.  When I reboot, and login as a user,
I end up in the root directory.  If I logout and log back in  
again, I am in my home directory.  

--
Hal.Varian@umich.edu    Hal Varian
voice: 313-764-2364     Dept of Economics
fax:   313-764-2364     Univ of Michigan
                        Ann Arbor, MI 48109-1220
Newsgroups: comp.sys.next.sysadmin
From: smk5@quads.uchicago.edu (Steve Kramarsky)
Subject: Please Help!! DISK EMERGENCY!
Reply-To: smk5@midway.uchicago.edu
Organization: University of Chicago Computing Organizations
Date: Sun, 27 Sep 1992 06:41:02 GMT

         
  Please, please help me!                                              
  My hardisk has always been flakey and has had both bad block problems and  
'hard' problems ( a bad power source).  It's an external 660 Meg Seagate which
seems to delight in causing me trouble.
               
  Anyway, now it's dead again.  The machine for which it's the boot disk will
  Please, please help me!                          
  My hardisk has always been flakey and has had both bad block problems and
'hard' problems ( a bad power source).  It's an external 660 Meg Seagate which
seems to delight in causing me trouble.
                                                                          
  Anyway, now it's dead again.  The machine for which it's the boot disk will
not boot and fsck hangs with the following message:       
                                                         
   reselect timeout - target 0
                                                                      
there is then several seconds to a minute of no disk activity and then the      
message repeats: reselect timeout - target 0.                             
                                                                                
  This continues as long as I let it untill I power down.                    
                                                          
  Sometimes I can get the machine to boot single user (usually there's
a "reselct timeout - target 0" and then, after a few moments, the drive   
suddenly restarts and the machine boots single-user [no fsck]).  When that 
happens the machine is still no good, because any time I issue a command there
is along delay (30 seconds, a minute or so) then the "reselect timeout" error
and THEN the disk spins and the command executes.  Odd eh?
                                                        
  Anyway since all this prevents fsck from running I can't get the machine
back up and my users are clamoring fo my head.  Is this a hardware problem?
Software?  What could it be?  ANYONE?

Thanks a million in advance,
   Steve
-- 
            Steve Kramarsky, University of Chicago Law School
             steve@faerie.chi.il.us -=NeXTmail always nice=- 
     "All I did was kiss a girl." - Jake, the night before his hanging.
From: slxmw@hydepark.enet.dec.com (869883 Medlyn)
Newsgroups: comp.sys.next.sysadmin
Subject: Help!  Pub. Domain X for Turbo NeXT
Date: 2 Oct 92 15:52:13 GMT
Article-I.D.: cc.1992Oct2.095215.59368
Reply-To: slxmw@hydepark.enet.dec.com (869883 Medlyn)
Distribution: world
Organization: Digital Equipment Corporation



	Does anyone know how to get a public domain X version to run
     properly on a Turbo Station.  I loaded XNext from cs.orst.edu and 
     sonata.cc.purdue.edu and neither would work.  When I ran X the screen
     changed but I couldn't really see a window.  As I moved the mouse 
     around, I could see static moving like something was not displaying
     properly.  

        I would really appreciate any help.  I have assignments that I am 
     have to write in X-windows.  It would be nice to do it on my own 
     machine.  Thanks.

		Dayne Medlyn
                slxmw@cc.usu.edu
Newsgroups: comp.sys.next.sysadmin
From: rallan@helical.com (Robb Aley Allan)
Subject: NS3.0 FloppyDisk Eject ANSWER
Reply-To: rallan@helical.com
Organization: Helical Systems, Ltd.
Date: Wed, 30 Sep 92 19:07:03 GMT

Ain' the net wonderful? Just got the following from NeXT:

   >This is a known bug that isn't specific to Engage!  It has to do with
   >auto-launched apps requesting icons from the Workspace.  Try to see
   >if not autolaunching some apps on your dock fixes this problem.
   >
   > -- Matt Watson NeXT Computer, Inc.  
   >

-- 
Robb Aley Allan, The Gulfstream Group
220 Sunrise Avenue, Palm Beach, FL 33480
voice: 407/ 832-4013   email: rallan@helical.com
Co-founder/director, Gotham Users of NeXT (GUN)
Newsgroups: comp.sys.next.sysadmin
From: death@netcom.com (David Burrowes)
Subject: NS 3.0 startup problems -- help!
Summary: I get two strange problem during boot of NS 3.0 equiped hard disk 
Organization: Netcom - Online Communication Services  (408 241-9760 guest) 
Distribution: usa
Date: Mon, 5 Oct 1992 14:57:59 GMT

In brief:  When I power up my hard disk, and '040  NeXTcube, I get this
message just after the 'testing system' message is replaced by
'loading from hard disk':

   Exception #2 (0x8) 0x100bada

I get dropped into the rom monitor to see this. I can then type 'b' to 
re-start the bootprocess. When it lists all the SCSI devices in the
monitor window, I find that I get the following linefour times: 

   generic SCSI device as sg# at sc0 target 7 lun 7

(where # increments from 0 to 3)

QUESTIONS:
  What is this exceptin #2?  Whatcan I do to get around it?
  Is it normal, with NS3.0 to have the cpu, at scsiID 7 showing up on
    four generic scsi devices like that???

MORE DETAILS:
  These do not occurrwhen I boot with a disk freshly installed with 2.1.
  Initially, I built the disk with 2.1 and then upgraded to 3.0.  Thie
  above problems appeared then.  So, I booted with CD-rom (using OD to
  get it to do so), and built the disk from scratch.  The problem
  persists.
  I've also done a   disk -b /dev/sd0a  with no apparent results.

I'd appreciate any insights anyone can provide!  Please email me or post
to the newsgroup!  If you email me, try any of these addresses:

death@netcom.com
death%kira.uucp@netcom.com
death@kira.uucp

THANKS!

\david john burrowes

Newsgroups: comp.sys.next.sysadmin
From: rallan@helical.com (Robb Aley Allan)
Subject: Re: 3,0 installation woes
Reply-To: rallan@helical.com
Organization: Helical Systems, Ltd.
Date: Mon, 28 Sep 92 16:30:20 GMT

Mike Panzitta writes
   In article <1992Sep28.050130.23485@athena.mit.edu> shanega@athena.mit.edu  
   (Shane G. Artis) writes:
   > 
   > Hi, I have a pair of questions for sysadmin types.  Any hints or
   > clues would be very helpful.
   > 
   > First, I'm trying to install 3.0 on my station from handmade floppies
   ...
   > messages file gave me one clue.  The final line in the file before the
   > most recent booting messages was:
   > 
   > loginwindow: Cannot find windowserver port!
   > 
   > What does this mean I'm missing or doing wrong?  I think everything is
   > all there, but maybe I missed a file somewhere.  I'm pretty sure my
   > permissions are all set correctly and so on.

The following is from an alert NeXT distributed during the PR2 test.

begin NeXT document-------------------------------------------------------------------

Problem #1:  PR1 users mistakenly run UpgradePrep.app from the helper floppy and then  
cannot run the window server.  

UpgradePrep.app is for Release 2 systems only.  

Fix:  Markus Lankeit has prepared a definitive description and work-around for this  
problem:

On the first page of the Upgrading.... documentation: "Upgrading from the Pre-Release 1  
to the Pre-Release 2 ... works just the same as any other upgrade."  After some searching  
I found on page 2: "If you're upgrading from [PR1] to [PR2] ... you don't need to use  
UpgradePrep."

If you do run UpgradePrep on a PR1 system, here's what you have to do to 
fix that machine:

1. boot single user mode
2. blow away /sdmach, then do a ln odmach sdmach
3. replace /usr/lib/NextStep/WindowServer with its PR1 version.
4. replace /usr/lib/NextStep/PS.VM with its PR1 version.
5. reboot
6. now install PR2 from the CD-ROM. 

end NeXT document-------------------------------------------------------------------


I recommend a different method, however.

1. 	launch single-user.
2.	mount the 3.0 CD-ROM disk.
3.	copy /usr/lib/NextStep/WindowServer and /usr/lib/NextStep/PS.VM from the CD-ROM  
to the hard disk.
4.	reboot.

-- 
Robb Aley Allan, The Gulfstream Group
220 Sunrise Avenue, Palm Beach, FL 33480
voice: 407/ 832-4013   email: rallan@helical.com
Co-founder/director, Gotham Users of NeXT (GUN)
Newsgroups: comp.sys.next.sysadmin
From: BrianW@SoundS.WA.com (Brian Willoughby)
Subject: Printing from clean install of 3.0 causes System Panic (3 times)
Reply-To: BrianW@SoundS.WA.com
Organization: SoundSoftware, Bellevue, WA, USA
Date: Fri, 2 Oct 1992 18:25:10 GMT


I did a clean install of 3.0 (Hyper3B) after reformatting my NeXTdimension's  
400M NeXT drive for 1024 byte blocks.

I have tried printing on three occasions, and the system panicked each time.   
Here are the relevant excerpts from /usr/adm/messages (note the large gap  
between the previous message and each panic, showing that nothing else was  
interacting):

- 1 -
Sep 28 08:49:26 sounds syslog: Workspace logged in
Sep 28 15:58:11 sounds mach: panic: (Cpu 0) No more room in kernel map
- 2 -
Sep 28 23:21:28 sounds mach: 	Disk Label: disk.1
Sep 28 23:21:28 sounds mach: 	Disk Capacity 1440 KB, Device Block 512 bytes
Sep 28 23:58:09 sounds mach: panic: (Cpu 0) No more room in kernel map
- 3 -
Sep 29 09:33:41 sounds WindowServer[192]: IPCFlushOutput: failed to flush  
output for stream 0x211524.
Sep 29 09:39:05 sounds mach: panic: (Cpu 0) No more room in kernel map

The first time I printing from NewsGrazer, the second from 3.0's Edit, and the  
third from 2.1's WriteNow.

I have 28MB System and 20M dimension memory and I am running UUCP with  
Mamakos's SLIP.

I just got the Printer Test page to print today after using PrintManager.app  
for the first time since I loaded 3.0 - I'll give printing another trial run,  
but I wanted to get this post out before I take a chance on panicking my  
machine again.
-- 
Brian Willoughby	Software Design Engineer, BSEE NCSU
BrianW@SoundS.WA.com	Sound Signal Processing Software and Consulting
NeXTmail welcome	- NO EMAIL SOLICITATION without prior permission
Newsgroups: comp.sys.next.sysadmin