*BSD News Article 27075


Return to BSD News archive

Newsgroups: comp.os.386bsd.questions
Path: sserve!newshost.anu.edu.au!munnari.oz.au!constellation!news.uoknor.edu!ns1.nodak.edu!netnews.nwnet.net!news.uoregon.edu!cs.uoregon.edu!sgiblab!swrinde!cs.utexas.edu!uunet!hearst.acc.Virginia.EDU!cabell.vcu.edu!csc3dmd
From: csc3dmd@cabell.vcu.edu (Dean M. Deaver)
Subject: Question about BSD as a networking solution
Message-ID: <1994Feb8.210500.21327@cabell.vcu.edu>
Organization: Virginia Commonwealth University
Date: Tue, 8 Feb 1994 21:05:00 GMT
Expires: Tue, 15 Feb 1994 05:00:00 GMT
Lines: 19


My situation:  I'm a 3rd year comp.sci. student working for a small
auto recycling firm.  I have very little experience (at this point)
in networking.  Hopefully I can pursue a career in it.

My problem:  The company I work for runs an inventory system under
PC-MOS.  We have 8 workstations on this network.  Our accounting and
marketing computers (4 of them) are on a separate network running
Lan-tastic.  My boss wants to combine the two systems, and since he's
paying half my tuition bills, I've been elected to find a solution.
By the way, our server is a mere 486 DX 33, but we can upgrade if
necessary.  Is BSD (or any unix, for that matter) a viable solution?
What are the (ballpark) costs involved?  I realize this is a loaded
question, but I'm trying to rule out any unsensible ideas from the
start.  I also have plenty of time to work on the project.  

Can anyone help me?  If so, any suggestions would be greatly
appreciated.  (side note:  we also want to employ a bar coding system
in our inventory software.)