NetNews Usenet Archive 1992 #31/NN_1992_31.iso/spool/comp/unix/sys5/r4/1031

Internet Message Format | 1992-12-28 | 1.7 KB

Xref: sparky comp.unix.sys5.r4:1031 comp.sys.novell:10888
Newsgroups: comp.unix.sys5.r4,comp.sys.novell
Path: sparky!uunet!elroy.jpl.nasa.gov!sdd.hp.com!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!mcdchg!chinet!les
From: [e-mail] (Leslie Mikesell)
Subject: Re: Novell bought USL?
Message-ID: <[e-mail]>
Organization: Chinet - Public Access UNIX
References: <[e-mail]> <[e-mail]> <[e-mail]>
Date: Mon, 28 Dec 1992 18:03:33 GMT
Lines: 21

In article <[e-mail]> [e-mail] (Gary Heston) writes:

>Unixware does not provide DOS-type networking support (IPX/SPX) as a
>server; only as a client (always possible that I missed something, though).

This seems slightly insane to me.  The obvious place for a unix machine
in a PC network is a server where one has the ability to log in over
the network to run unix if desired but the normal mode of operation is
to run off the shelf PC applications with the unix machine handling the
shared disk space and printers.  This gives you the usual unix communications
capability (nfs, uucp, mail, etc. among similar machines), the ability
to perform backups at the server, and the ability to dial in to access
your mail and files remotely, all as part of the base package.  If you
need special print filtering you can write a normal unix program to
do it instead of an NLM. The various forms of lanman/X give you this.
If you can log into a unix machine over the network (especially if it's
the place where your network files are stored), why do you need one on
your desk?

Les Mikesell
  [e-mail]