ljm@TWG.COM (Leo J McLaughlin) (09/22/89)
Folks: >We are in the process of developing some recommendations, within the >University, for various components of networking - one of which is a >network operating system. I have a few questions that I would >appreciate peoples comments on. >1) Whenever all of the OSI-ISO application level services are defined >and implemented, it will rid the need of "network operating systems" >(i.e. Novell, Banyan, 3COM etc.). Do you think this is accurate or am I >missing a function of the network operating system (other than the >operating system) that will not be provided in ISO application layer services. More to the point you are missing a small matter of scale. Yes, it would be possible to build a file sharing system over OSI's application services, but you wouldn't really want to even on a UNIX host. As for PCs, it is unlikely you'll get many people to buy an application requiring a couple of meg of RAM to share files at one or two K per second. >2) What exactly is LAN Manager? What was the motivation for it's >development? My understanding is that it is another session through >application layer "standard" with hooks for OS/2. A network operating system. (What is a network operating system? Good question. In my country we have many bright, idealistic students who ask similar questions. Next question, please?) Depending on who you ask, LAN Manager was developed to allow developers to use one common networking API over many different operating systems and protocols OR to allow many different protocols on differnet operating systems to share one or more network interfaces without requireing driver development from the protocol vendors OR because NetBIOS and sockets were so prevelent that IBM/Microsoft needed to develop a new API to sell new networking software. >3)... >4) Is there any reason why LAN Manager couldn't run on top of another >OS (UNIX, VMS, VM, MVS, ...)? Or is it tightly tied to OS/2? It is in fact intended to be ported to every operating system on the planet. See motivation 1, 2, and/or 3 above. >5) What network and transport layer does LAN Manager run over? Are >those protocols also part of LAN Manager? Couldn't LAN Manager use TCP/IP? It doesn't matter, no, and yes. >6) How are typical PC network operating systems different from say >using PC/NFS? I mean why not just scrap the idea of another protocol >stack and proprietary network operating system in favor of NETBIOS over >standard TCP/IP? I understand the RFC exists for this but I was trying >to make sure I understand the motivation for it. Given that we sell a NetBIOS over TCP/IP based network operating system, I shan't comment. >7) NETBIOS would run on top of TCP correct? I have seen notes >indicating that TCP/IP would run on top of NETBIOS, but that would be a >transport and ip protocol running on top of session? Is that what is really >true? It is NetBIOS over TCP/IP (RFCs 1001, 1002) which is relevant to the topics touched by your missive. TCP/IP over NetBIOS (RFC 1088) is useful for those sites already possessing proprietary networking equipment who wish TCP/IP connectivity. >I guess the root of all of these questions is how can you recommend a >network operating systems when there are so many alternatives and the >wave of the future is STANDARDS? What am I missing? Again, given that we sell a NetBIOS over TCP/IP based network operating system, I shan't comment. enjoy, leo j mclaughlin iii The Wollongong Group ljm@twg.com