From: Suso <suso@suso.eigenmann.indiana.edu>
Newsgroups: suso.linux-help
Subject: Re: New UNIX user
Date: Thu, 29 Oct 1998 20:39:56 +0000
Organization: A poorly-installed InterNetNews site
NNTP-Posting-Host: suso.eigenmann.indiana.edu
In-Reply-To: <36380A70.277A434A@indiana.edu>
Xref: news.suso.org suso.linux-help:14






  Hi Ben,

  Answers are below the questions.

On Thu, 29 Oct 1998, Benjamin F. Keil wrote:

> Hello "Suso,"
> 
>     I'm a new kid in town, just got my Linux box up and running this week.
> TCP/IP is working great, and I'm only having a little trouble with my IPX
> protocol.  This is my first experience with unix-like systems, and I have
> to say that compiling a custom kernal is quite a rush...  I've got X11
> running well with fvwm2, and some fun things like Netscape and Arena and
> the Gimp, etc.

  What distribution are you running? I saw on iu.linux that you mentioned
Stampede. Are you running Stampede? If so, it's the only major
distribution that I haven't tried yet. Would you be open to letting me
copy the CD?

>   As far as help I could use:
> 
> o Currently, I set up IPX by becomming the superuser, running
>    ipx_configure with the automatic options and then attempt to mount a
>   filesystem.  When I do this, it makes an EtherII network and an 802.2
>   network.  I then turn off the automatic options and remove the 802.2
>   network by hand.  How can I set up my system scripts (Slackware 3.5)
>   make these steps unnecessary?  That is, I'd to login to my locker,
>   etc., without becoming the super user.

  Depending on how you are setup, you'll want to run this command as
superuser to add the ipx:

   ipx_interface add -p eth0 etherII

  To make this automagically happen at boottime you'll want to add this
command to your '/etc/rc.d/init.d/network' boot script. Make sure you put
it last in the script so that all the proper networking stuff is
initialized first. I may post a patch file here or an example later of the
details of how this works. I do mine manually now, so I am not aware of
any complications with putting the command in the network script. But
putting the command last in the network script would be the most likely
place to put it.

  As for mounting your locker, you'll want to run this command

   ncpmount -S [xenon or neon]  -V [whatever volume] -u [your username] 
      -U [your username].users.iub [mount point]

  So if I wanted to mount my locker to a directory called xenon, I would
type:

   ncpmount -S xenon -V L01 -u suso -U suso.users.iub xenon/

  You can also create a file in your hoem directory called .nwclient that
holds some of the information about mounted drives. You might do a 
'man nwclient' to get the details about how that file works. I don't
recall there being a way to have it enter your password automatically, but
there may be a way.

  To see the results of mounting your locker you can type:

   df -a

 
  You might have to install the ipx and netware tools if your distribution
doesn't have them, but most do. Also if the ncpmount program doesn't work
as a normal user, you might have to put the suid bit on the ncpmount and
ncpumount programs. That's done like this:

    su -   
    chmod u+s | which ncpmount
    chmod u+s | which ncpumount
    


> o Also, any help you could give me with regards to setting up a netware
>   printer (HP LJ 8000 N) -- and appropriate word processing, spreadsheet,
>   database software to use with it -- would be very much appreciated.


  I haven't tried printing in the dorm yet, but this is the command that
you'd use over and ipx network:

  nprint -S servername -U username -q PRINTQUEUE  filename


  You can figure out the PRINTQUEUE for your dorm by going to some
windows95/NT machine and looking at what it's set to in the properties for
the printer. 

  Halls of Residence computing is really hairy about us Linux users
setting up ipx stuff. But don't sweat it.


  Let me know if you get things printing and working.

  Thanks,

  Suso