HDTenEightyP/NetNews huggingface dataset:
From: marcu@leland.Stanford.EDU (Marc Albert Ullman)
Subject: Re: printing to a LaserWriter on the ethernet - how to set it up???
Organization: DSG, Stanford University, CA 94305, USA
Date: Wed, 30 Sep 92 19:53:09 GMT

In article <1abscnINNhpn@zaphod.mps.ohio-state.edu> pali+@osu.edu writes:
>PRESENT SETUP: LaserWriter IIg on AppleTalk to a GatorBox; Mac IIfx, NeXT
>(cube) and GatorBox on the ethernet. I can print from both machine OK.
>
>PROBLEM: I want to eliminate the middleman(person) (=GatorBox) by putting my
>LaserWriter II on the ethernet so that I would not depend on our
>administrators who may occasionally turn the GatorBox off at unexpected
>times.
>
>QUESTION: how do I set the system up? Obviously, I'll need a printcap stuff
>somewhere in the CUBE but what I should put in it is what I don't know. I wan
>to continue printing from both machines.

Four easy steps:

	1) Install the AppleTalk Package

	2) Enable AppleTalk via the preferences app

	3) Reboot to start atalk daemon (could do by hand if brave)

	4) Use print manager to configure printer using atalk communications.
	   Note: if the first three steps were successful, you'll now see
	   AppleTalk as a choice under the Communications item in the
	   Create New/Modify Existing Printer panel.

	   Select "Apple LaserWriter IIg" for the printer type--yes, NeXT
	   is the first vendor I've seen that actually supports the IIf and
	   IIg printers.  You can control PhotoGrade and FinePrint, etc.
	   from the regular print panel in all applications.  Aren't object
	   oriented operating systems wonderful?!

	That's all there is to it.  No mucking with printcap/netinfo, etc.
	It just works...

--Marc Ullman
  Stanford University
From: madler@cco.caltech.edu (Mark Adler)
Newsgroups: comp.sys.next.sysadmin
Subject: loginwindow option
Date: 30 Sep 1992 12:50:16 GMT
Organization: California Institute of Technology, Pasadena
NNTP-Posting-Host: sandman.caltech.edu


I found out how I killed my system: as suggested in section 9 of the
NextAdmin documentation, I added the option "-PowerOffDisabled true",
as shown in the example, to the console line of /etc/ttys.  Then
loginwindow simply hangs.  I took it out, and now it works again.

Instead, I have it now in root's default database, and that seems to
work.  (I.e. "dwrite loginwindow PowerOffDisabled true".)

Mark Adler
madler@cco.caltech.edu
Newsgroups: comp.sys.next.sysadmin
From: paul@seer.demon.co.uk (Paul Lynch)
Subject: Re: Desjet and 3,0
Organization: Demon Internet Services.
Date: Wed, 30 Sep 1992 19:37:40 GMT
Originator: paul@seer.demon.co.uk

In article <dillon.0ojg@overload.Berkeley.CA.US>  
dillon@overload.Berkeley.CA.US (Matthew Dillon) writes:
>     Note that your serial cable to the HP500[C] must be wired properly  
for
>     hardware flow control, and note that the HP500[C] does not use RTS  
for
>     flow control, but DTR.  It's a mess.  I don't know how you would do  
it
>     on a non-turbo machine (which doesn't have hardware flow control).
> 
> 					    -Matt
> 
I do believe that you might be in error.  It's the 030 machine that don't  
do flow control, not the nonTurbo 040s.

Paul
-- 
Paul Lynch
P & L Systems                        (NeXTmail) paul@seer.demon.co.uk
Tel: (0494)671501                           paull@cix.compulink.co.uk
Fax: (0494)680228                            76711.451@compuserve.com
Newsgroups: comp.sys.next.sysadmin
From: woo@ornl.gov(John W. Wooten)
Subject: NeXT Network versus NFS?
Organization: Oak Ridge National Laboratory
Date: Mon, 5 Oct 1992 13:49:29 GMT

I'm getting ready to install NeXT's at several schools in our area.  At  
the central location, I will have a larger disk drive and intend to put  
the full development software, all references, manuals, etc.  The other  
NeXTs have IP access via T1 lines to this NeXT.

What are the pros and cons of making the central NeXT the Configuration  
Manager with the others seeing it's disks, versus just exporting the  
large external disk and having the others mount it?

What happens if the Central configuration manager is down?  Can the  
others even run?  I know they can't see the data structure, but I don't  
want to build in a single point of failure.

Will there have to be a lot of reconfiguration if NFS is used?  I'm  
looking for simple things I can do that minimize configuration and  
operation support requirements.

-----------------
J. W. Wooten
Newsgroups: comp.sys.next.sysadmin
From: ferdi@cgrg.ohio-state.edu (Ferdi Scheepers)
Subject: Need UpgradePrep.
Organization: OSU Advanced Computing Center for the Arts and Design
Distribution: na
Date: Sat, 3 Oct 1992 20:55:00 GMT

I don't have a floppy drive, so I can't access UpgradePrep on the 
CD-ROM Tools Release 3.0 floppy disk. I'd appreciate help from some
kind soul. 

I have a 2400 baud modem connection to my University account (I know,
it will take about two hours to transfer...), so if someone could 
tar, compress and encode the contents of the floppy disk and e-mail
it to me, I at least have a shot at upgrading!

If you're in a position to help but are not sure how to go about it,
send me mail anyway and we can get the ball rolling.

Cheers
Ferdi
Newsgroups: comp.sys.next.sysadmin
Subject: Re: bug in tar, anyone fixed it?
From: frank@ifi.unibas.ch (Robert Frank)
Date: Tue, 6 Oct 1992 08:48:06 GMT
Reply-To: frank@ifi.unibas.ch
Organization: Institut fuer Informatik

In article <ti6ls.718300894@tuhhco>  writes:
> As the man pages say "The current limit on file name length is 100  
characters."
> Has anyone fixed this bug?
> 
> 
>  
/*****************************************************************************/
> /*      Ludger Solbach, AB Techn. Inf. VI, TU Hamburg-Harburg, Germany        
*/
> /*                         Tel.: 040/7718-3357                                
*/
> /*                   Email: solbach@tu-harburg.dbp.de                         
*/
>  
/*****************************************************************************/

YEP, GNU! get GNUtar... (it's all over the places, on many different servers)
--
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
                   ( if all fails try frank@urz.unibas.ch )
Newsgroups: comp.sys.next.sysadmin
From: Michael_Pizolato@afs.com (Michael Pizolato)
Subject: Re: while I'm posting...
Reply-To: Michael_Pizolato@afs.com
Date: Mon, 28 Sep 1992 13:28:38 GMT

In article <Bv5G09.H04@usenet.ucs.indiana.edu> francisr@indiana.edu (Rob  
Francis) writes:
> Quick question. What determines if the /Net directory looks like a globe or a  
> folder?  I added a mount to a machine the same way I did on my machine with  
> /Net as the mount point and net as an option.  It works on mine, but the other  
> machien just shows /Net as a folder.  Both are running 3.0.  nidump fstab .  
> looks the same on both machines.  Guesses?

If you are looking at the second machine's /Net via the first machine's /Net, it will appear as a folder.  I.E. if the path you're looking at in the file viewer of the first machine is /Net/secondMachine/Net, you will see a folder rather than a globe.  You will also notice that none of the stuff in the second machine's /Net shows in the browser.  This has always been the case in my experience (V2.1 through V3.0), though I don't know the reason (probably some limitation of NFS, or, less likely, a decision t





o disallow such viewing by the designers, for impeccable reasons, I'm sure ;-).

Michael

--
Michael_Pizolato@afs.com
~18 kyu
Q16
NeXTMail appreciated
From: dylan@midiline.la.ca.us (Comrade D)
Newsgroups: comp.sys.next.sysadmin
Subject: Can't dial in (SUMMARY)
Date: Wed, 30 Sep 92 15:46:39 PDT
Organization: MIDILine BBS - Altadena, CA - (818) 797-3285

Thanks to those (John, Jim, Mark, Bernhard) who responded
to my post.  Unfortunately, I had no luck getting dial-in
to work with my DoveFax modem.  I originally asked this:

>  Very basic question...  I'm having no luck configuring
>  my NeXTcube under 2.1 and DoveFax for dial-in (dial-out
>  works fine).
>  
>  I followed Mark Adler's modem.setup notes with no luck.
>  Also checked through NeXTanswers, the SysAdmin manuals,
>  etc...
>  
[ parts deleted ]
>  
>  I'm not sure what to look for, but it isn't consistent
>  in any case.  After I "KILL -HUP 1" it starts out with
>  a getty process, like so:
>  
>    536 ?  U     0:00 - D2400 ttyda (getty)
>  
>  Then a new process appears like so:
>  
>    536 da S     0:00 login -p n:
>  
>  Sometimes the login looks like:
>  
>    190 da S     0:00 login -p carrier
>  
>  or
>  
>    190 da S     0:00 login -p in:
>  
>  And then the getty process disappears.  Very often no
>  connection occurs.  When the connections do occur the
>  login prompt (I assume) appears just as garbage, as if
>  maybe the parity was wrong.
>  
>  In the console window I get:
>  
>  Sep 18 10:18:02 angst mach: zs0: recv buffer overrun Sep
>  18 10:18:04 angst login: 1 LOGIN FAILURE ON ttyda, in:
>  Sep 18 10:18:10 angst login: 1 LOGIN FAILURE ON ttyda,
>  rd:

John Robison (john@oceania.com), Jim Chorn
(onion.rain.com!nestmoi!jim), Mark Adler
(cco.caltech.edu!madler), and Bernhard Nocker
(bnocker@cosy.sbg.ac.at) all suggested the problem was due
to modem echo, some saying it could be caused by a bad
cable.  Jim suggested I try the ATE0 command to turn off
local echo.  Bernhard sent me the modem profiles (with the
AT&V command) that might work.

Unfortunately, I can't do anything about it if the cable is
to blame.  The DoveFax's cable is an unconnectable part of
the unit.  I tried the ATE0 and suggested modem profiles,
with no luck.  I'm starting to think I need to save up and
get a ZyXEL...

Meanwhile, has ANYONE out there got a DoveFax modem setup
for dialin successfully?


-------------------------------------------------------------------
Dylan Kohler
dylan@angst.com     (NeXTmail welcome)
From: rmyers@dec5200.acs.uci.edu (Richard Myers)
Subject: DNS with slip (under 3.0)
Newsgroups: comp.sys.next.sysadmin
Organization: University of California, Irvine
Keywords: resolv.conf, slip 
Date: 30 Sep 92 18:13:27 GMT

I'm using l.m.'s SLIP for the NeXT, and would like to use a nameserver
as I did under 2.1.
In the docs it says (NeXT Admin) that all I need to do to enable DNS
(Darpa Name Server?, I'm at a pc right now... :-( is to create the
file /etc/resolv.conf with the appropriate domainname and nameserver
lines and I'm a happy camper.  GREAT!!  So I grab my old resolv.conf
and it doesn't work...

I can ping any internet address I want - fine.
I can use nslookup ('nslookup ics.uci.edu') - fine.
	So the resolv.conf is correct!
But I can't ping ics.uci.edu, or finger @ics, or anything spiffy like
that.
I'm running as a 'Non-Netinfo machine'.
Any idea what the problem is?
Kurt
Newsgroups: comp.sys.next.sysadmin
From: wtmahavi@ponder.csci.unt.edu (William Ted  Mahavier)
Subject: Thanks for responses to "silly kermit questions"
Organization: UNT Mathematics Dept.
Date: Tue, 29 Sep 1992 02:18:20 GMT

Thank you for all the responses.  The problem required
excerpts from several of your responses to fix, but
we are up and running now.  

Newsgroups: comp.sys.next.sysadmin
From: kurrer@lisboa.ks.uiuc.edu (Christian Kurrer)
Subject: Re: lpr works but print panel does not
Reply-To: kurrer@lisboa.ks.uiuc.edu
Organization: University of Illinois at Urbana
Date: Tue, 6 Oct 1992 17:01:41 GMT

In article <BvoypD.5zt@world.std.com> gsk@world.std.com (Geoffrey S  
Knauth) writes:
> A friend asks:
> 
> "I simply cannot get buckaroo (in Wendy's office) to print via the
> NeXTstep print panels.  It is driving me to distraction.  Printing the
> Unix way (lpr) works fine, so I know the daemons and the NetInfo stuff
> for printer routing (printcap) is all set up correctly, but whenever
> you try to print from buckaroo from a NeXT print panel, it spins for
> 30 seconds before saying `Unable to connect to printer daemon.'  That's
> hogwash, since I can clearly connect to the printer daemon via lpr."
> 
> "Any idea what the print panel is doing that lpr is not?
> Any idea how to fix this (it works from other computers)."
> -- 
> Geoffrey S. Knauth, Marble Associates, Inc.               

I got exactly the same problem on our Next Network. But as people reboot  
their machine pretty often, these problems appear and disappear  
continuously. 

I'd be interested in the solution, too.

Christian Kurrer
Newsgroups: comp.sys.next.sysadmin
From: louie@sayshell.umd.edu (Louis A. Mamakos)
Subject: Re: SLIP Server Configuration
Keywords: SLIP, server
Organization: University of Maryland, College Park
Date: Sun, 4 Oct 1992 15:09:36 GMT

In article <1992Oct3.192357.3207@mnemosyne.cs.du.edu> lmccullo@nyx.cs.du.edu (Michael McCulloch) writes:

>I want 'gandalf' to act as my SLIP server. The dial-out procedure for 'frodo'
>attempts dial-out and the modem then connects with 'gandalf' at work. However,
>the syslog file gives the following error:

Let's examine the log closely...

>Oct  3 13:34:35 frodo tcldiald[130]: Authorized packet [140.165.32.210 -> 140.165.32.59], proto TCP (6)
>Oct  3 13:34:35 frodo tcldiald[130]: Started pid 566 to bring up interface slip0
>Oct  3 13:34:36 frodo diald-slip0[566]: tracing TCL commands
>Oct  3 13:34:36 frodo diald-slip0[566]: makecall: Attempting connection to "gandalf.tbe.com" via "slip0"
>Oct  3 13:34:36 frodo diald-slip0[566]: (Begin unix.tcl for interface slip0 site gandalf.tbe.com)
>Oct  3 13:34:36 frodo diald-slip0[566]: (mtu 1006 atimeo 300 wtimeo 300 ipkts 0 opkts 0)
>Oct  3 13:34:36 frodo diald-slip0[566]: (Start of ZyXEL dialing script, dialing xxx-xxxx)
>Oct  3 13:34:37 frodo diald-slip0[566]: (Modem firmware version U1496E  V M4.13)
>Oct  3 13:34:37 frodo diald-slip0[566]: (set parameters)
>Oct  3 13:34:37 frodo diald-slip0[566]: (Dialing xxx-xxxx)
>Oct  3 13:35:04 frodo diald-slip0[566]: (Connected ^M)
>Oct  3 13:35:04 frodo diald-slip0[566]: (Begin Unix login)

Here's the telling error, of course:

>Oct  3 13:35:27 frodo diald-slip0[566]: Script Error: waiting for password

Looking at the fragment of the TCL script that generates this error:

	expect timeout {error "waiting for password"} "*assword:*"

We see that it is expecting to see a Password: prompt from the other
side.

>I have an account on 'gandalf' that possesses the following settings:
>
>Enter user identifier (login or uid): slip0
>Entry is now:
>   1)  login ...... slip0

I believe that this is your problem.  The /bin/login program won't prompt for a
password unless there is one present on the account.  

>   2)  password ... (none)

>   3)  name ....... 
>   4)  userid ..... 100
>   5)  groupid .... 4 (uucp)
>   6)  login dir .. /
>   7)  login sh ... /usr/dialupip/bin/dudisc_slip0
>   
>Is this what I should have on the server side? I also made a copy of
>/usr/dialupip/bin/dudisc and renamed it /usr/dialupip/bin/dudisc_slip0.

There is a command /usr/dialupip/bin/duinstall which will do this for
you.  Actually, it just makes links to the dudisc program.

>What's the deal with the password -- or is my account spec for slip0 screwed?
>Or do I have to have a .netrc on the client side????

I would either modify the login-unix.tcl script to not expect a password 
prompt, or add a password to the account and have the login-unix.tcl script
supply it when asked.

louie
From: frank@fnbc.com (Frank Mitchell)
Newsgroups: comp.sys.next.sysadmin
Subject: Re: NS3.0 FloppyDisk Eject Problem
Date: 30 Sep 92 22:20:30 GMT
Organization: First National Bank Of Chicago, Chicago IL, USA

In article <1992Sep30.044536.23554@udel.edu> stark@superc.che.udel.edu (Scott  
M. Stark) writes:
> 
> It appears that common denominator
> in the disk problem are autolaunched dock extender's.

Confirmation point: I stopped autolaunching Engage (and twiddled the Disk 
Preferences in Workspace slightly), and my disks now eject.  This doesn't 
eliminate Workspace->Preferences(Disk Options) as an accomplice to the crime,
though...

--
Frank Mitchell,	Business Systems Analyst, First National Bank of Chicago
email:frank@fnbc.com (NeXTmail)

"In a way, staring into a computer screen is like staring into an eclipse. 
It's brilliant and you don't realize the damage until its too late."
-- Bruce Sterling, LA Times, 2/20/92
From: edmbv@alf.uib.no (Bj|rn Asle Valde)
Newsgroups: comp.sys.next.sysadmin
Subject: Exporting cd-rom (dos/fat) filesystems
Keywords: cd-rom, nfs, export, dos
Date: 6 Oct 92 17:01:07 GMT
Organization: SiO Data NeXTSenter, Bergen|Oslo, Norway

Did anyone successfully nfs export an cd-rom with ms-dos(fat)
filesystem type. Clients would be pc's with pc-nfs and normal
unix nfs box'es. I'm assuming NeXTSTEP version 3. I don't have
much time to scan news these days, mail responses would be
very much appreciated.

Regards, -bav
-- 
   ,__o   Bjorn Asle Valde	SiO Data NeXTSenter	tel +47-5-317041
 _-\_<,   valde@SioData.uio.no	Christiesgt. 13		fax +47-5-320238
(*)/'(*)  			N-5015 Bergen, Norway
Newsgroups: comp.sys.next.sysadmin
From: jeffo@uiuc.edu (J.B. Nicholson-Owens)
Subject: How to prevent an nidump of the passwd's?
Reply-To: jeffo@uiuc.edu (J.B. Nicholson-Owens)
Organization: University of Illinois at Urbana
Date: Sat, 3 Oct 1992 17:49:08 GMT

Other than making the 'nidump' command unavailable via removing the read and  
execute permissions (which really wouldn't help if someone were to get the  
command from somewhere else), how can the password data be protected from being  
read by just anyone on the system?  That is, what needs to be changed so that  
the passwords come out either with asterisks for where the real encrypted  
password would be or just making the entire output from 'nidump passwd /'  
unavailable?

Thanks.
-- 
-- Jeff (jeffo@uiuc.edu)
-- NeXTmail ok
Newsgroups: comp.sys.next.sysadmin
From: gvh@metrosoft.com (Gordon Van Huizen)
Subject: DOS and Mac floppies w/ 3.0
Reply-To: gvh@metrosoft.com (Gordon Van Huizen)
Organization: Metrosoft
Date: Tue, 29 Sep 1992 00:33:09 GMT

I recall a few people posting about not being able to mount DOS floppies  
under 3.0. I'm having trouble with this as well, and noticed that the  
DOS.label file in /usr/filesystems/DOS.fs contains utter garbage:

3     {   

Not very pretty. The console log shows something to the effect of:

DOS File System: Initialized
Sep 28 17:24:17 Workspace: Mounted floppy disk at /3Ff91{@ F

Sometimes the DOS disk shows up the Workspace (with a cheery little name  
that matches the console log entry), sometimes it doesn't. I don't seem to  
be able to eject it in any event. (The eject menu is DIM, and dragging it  
to the recycler does nothing).

Can I just changed the contents of DOS.label? Anyone else experiencing  
this?

WRT Mac floppies, thanks to whoever posted the little goodie about  
removing anything other than mac.fs. That did the trick and FloppyWorks no  
longer has a stranglehold on my Mac floppies. The lack-o-eject plagues Mac  
disks too on occasion. I'm not running Engage...

In a related note, be aware that if you drag a Mac file from a Mac fs to a  
NeXT fs, you will lose the resource fork. To access the .#rsrc# file, it  
MUST still be on a Mac fs.

Gordon
-- 
----------------------------------------------------------------
Gordon Van Huizen           vox: 619.488.9411  fax: 619.488.3045
Metrosoft                   gvh@metrosoft.com [NeXTmail welcome]
----------------------------------------------------------------
Newsgroups: comp.sys.next.sysadmin
From: nhuebner@magnus.acs.ohio-state.edu (Nancy J Huebner)
Newsgroups: comp.sys.next.sysadmin
Subject: NeXT Locks Up
Date: 1 Oct 92 14:11:08 GMT
Organization: The Ohio State University

One of our NeXT keeps hanging up.  The person using the NeXT is only using NeXT
mail at this time.  He isn't doing anything fancy, just trying to read mail
others send him and trying to send mail.  Since last week everytime he gets intothe mail he gets a spinning disk and he can't do anything.  Yesterday when this
happened the machine was rebooted, turned off, etc.  When he tried to log on he got the spinning disk at the login window and couldn't even get on the machine.
They gave up and turned the machine off.

About two/three weeks ago he used the machine all morning. When he came back 
from lunch the screen was dark (like when it is turned off).  They checked the
cables, etc.  They pushed the power button but nothing.  Silly as it may seem
I had them check the electrical outlet to be sure electricity was coming from 
it and it was.  Finally they called the Office of Equipment Repair.  OER 
replaced the battery and everything seemed to be fine until last week.

Any ideas? Are these things related?

Thanks in advance.

Nancy J. Huebner
(njh@kiwi.swhs.ohio-state.edu)
From: zenon@resonex.com (Zenon Fortuna)
Newsgroups: comp.sys.next.sysadmin
Subject: Re: bug in tar, anyone fixed it?
Date: 6 Oct 92 13:31:48 GMT
Article-I.D.: resonex.1992Oct6.133148.12377
Organization: Resonex Inc., Sunnyvale CA

In article <1992Oct6.084806.10760@urz.unibas.ch> frank@ifi.unibas.ch writes:
>In article <ti6ls.718300894@tuhhco>  writes:
>> As the man pages say "The current limit on file name length is 100  
>characters."
>> Has anyone fixed this bug?
>> 
>/*****************************************************************************/
>> /*      Ludger Solbach, AB Techn. Inf. VI, TU Hamburg-Harburg, Germany        
>YEP, GNU! get GNUtar... (it's all over the places, on many different servers)
>--
>Robert Frank                         tel. + (061) 321 99 67                 


I do not understand the answer. The gnutar still has the default NAMSIZ set
to (only ?) 100 characters. Maybe Robert thought about the path length ?

	-Z.
From: pcwood@astro.ocis.temple.edu (Paul Wood )
Newsgroups: comp.sys.next.sysadmin
Subject: identd
Date: 5 Oct 92 15:00:44 GMT
Organization: Temple University
X-Newsreader: Tin 1.1 PL5

Hello,
	Has anyone installed the identd properly on their next system?
I have made several attempts.  My entries look like this
/etc/services (yes its niloaded):
ident   113/tcp auth
/etc/inetd.conf:
ident     stream  tcp  nowait  kmem   /usr/etc/identd    identd

I tried sys instead of kmem, I tried setgid kmem on identd.  I also tried
setgid sys on identd.  Everytime I try the test program I get this:

system says host is 129.32.1.21
authuser says host is 129.32.1.21
system says username is pcwood
authd cannot figure out your username

Any clues?
--
                                                                                           __^__                                            __^__
          ( ___ )------------------------------------------( ___ )
           |  /|   Paul Wood is pcwood@astro.temple.edu     |\  |
           | / |   Temple University Computer Services      | \ |
           |___|   Unix Systems Administrator/Programmer    |___|
          (_____)------------------------------------------(_____)
             V                                                V
Newsgroups: comp.sys.next.sysadmin,comp.sys.ibm-pc