PDA

View Full Version : Network Operating System (NOS)


lilac
10-16-2004, 09:17 AM
hello everybody,

i'm a new member in this forum. i have some questions about the network operating system. i have an assignment to analyze about the network operating system, but i'm quite blind about it. so can anybody help me ?

ECA
10-16-2004, 10:04 AM
WELL,
Probably...
But which OS are you looking at...
What is the server controlling, or is just a file server. there are many types and kinds.
Whats your hardware. And configuration.

spankers
10-16-2004, 11:15 AM
I assume you are talking about the generic term as in ...
http://compnetworking.about.com/library/glossary/bldef-nos.htm

Google is your friend. As a Network Operating System covers quite a bit of territory (types of operating systems, protocol stacks, supporting hardware, etc.), perhaps you could focus your question to something more specific.

lilac
10-16-2004, 08:36 PM
thank u very much 'spankers'. i've been told that for the NOS, Novell are leading now. is that true ? so can u give me an information about the Novell ? i'm trying to evaluate an overall performance and information about Novell's capability... thank u.

ECA
10-16-2004, 11:36 PM
Novell?
WOW, you going back along ways.
I would think, Linux and UNIX are in the lead..

spankers
10-17-2004, 02:36 AM
Considering that Novell now owns SuSE Linux, I'd think Novell has the potential to take the lead. Given that Novell successfully migrates their Netware stuff to Linux, I'd say that they will have one of the most flexible "enterprise class" operating systems out there (the Linux kernel in and of itself supports multiple network protocol stacks and a huge variety of hardware). Of interest is that Novell bought UNIX from AT&T and they still claim to own the UNIX System V copyrights after selling a portion of the UNIX business to SCO in 1995.... and UNIX was one of the original NOS.

In addition to buying SuSE, Novell has also recently bought Ximian, a company developing applications for the Linux GNOME desktop. One of those applications, Evolution, is the only Linux email client I know of that is compatible with the Microsoft Exchange server. If Novell then adds their Groupwise application functionality to Evolution, then it may very well become one of the most robust "groupware" applications out there.

http://www.novell.com/linux/ximian.html

If you're looking for benchmark numbers for Netware, you'll have to find that the hard way (unless someone on this board is a Netware guru). The little experience I had with Netware was many years ago. Google may get you some results.
Luck,
Ed

ECA
10-17-2004, 09:50 AM
Novell, has long been into server systems and transferring there knowledge to Linux will be great..
Unix is the main server OS for the internet, and Linux was its son/daughter.
But Linux is going the way of a FULL OS, rather then as UNIX being a server control OS.
Hopfully it wont become as Bloated as Windows.

spankers
10-17-2004, 10:22 AM
One of the nice thing about Linux is the level of modularity in the OS.... so you can choose your level of bloat. In the latest 2.6 kernels there are options to remove what were once unremovable features... reducing the size of the kernel. The embedded applications for the Linux kernel will be a big driver to keep this level of modularity.

As far as Unix being a server OS... any OS with networking capabilities can act as a server. Unix has been used for desktop workstations for quite some time, although most would consider the early Unix workstations to be a bit on the pricey side. The Linux kernel has had, for a year and a half or so, a compile time option to enable preemptive scheduling, which provides better performance for desktop use (it reduces latency for user events), vice the standard scheduler (non preemptive) which works better for server applications (Kernel -- "I don't care if there was a mouse click... leave me alone, I'm busy. I'll get to your damn mouse click when I'm done").

Modular schedulers and kernel hotswap are in development. These features will allow switching out schedulers without recompiling the kernel and swapping kernels without a reboot, respectively. Good stuff!

lilac
10-18-2004, 08:29 AM
wow, thank u for the information. i think i'll try to find more about it on the internet. but can anybody maybe give their opinions about the comparisons between unix, linux and novell ? thank u...

llbbl
10-18-2004, 12:57 PM
Abbreviated as NOS, an operating system that includes special functions for connecting computers and devices into a local-area network (LAN). Some operating systems, such as UNIX and the Mac OS, have networking functions built in. The term network operating system, however, is generally reserved for software that enhances a basic operating system by adding networking features. Novell Netware, Artisoft's LANtastic, Microsoft Windows Server, and Windows NT are examples of an NOS.


http://www.webopedia.com/TERM/N/network_operating_system_NOS.htm

Why would you run a NOS system over a router for your DHCP and DNS? It seems like plug and play router with web administration is much easier to setup and maintain. Running a web server or file server is one thing but for general internet and WAN connectivity it doesn't make sense anymore to use a NOS ... right??

spankers
10-18-2004, 01:51 PM
It depends on the environment. For a home or other small network, DHCP can be provided from a router. DNS from the router is only a DNS proxy usually (i.e., it forwards all DNS requests to the actual DNS server). For any network where you want your own DNS (for instance, I am running BIND9 on a Linux box at home for caching DNS... my ISP has had trouble with DNS) ya gotta run a server.

The big reasons to use a NOS (god I HATE that term) for DNS/DHCP is that the server based DNS/DHCP services allow better control and if you want hosts with dynamic IP addresses to be assigned domain names (e.g., DHCP+DNS... dynamic 192.168.154.25 is laptop3.yourdomain.com) then you have no choice but to use a server based product.

About three years ago I was using a Linux box as a router/firewall and it did a great job. I just got tired of using ipfwadm/iptables to configure the firewall. There are software front ends now that make configuring easier now.

My Wireless Access Point died on me while doing a firmware upgrade a few months ago... I am now using a Linux box with a generic 802.11g card and a 100Base-T port as an ethernet bridge/WAP. Works very nicely but is a bit clunky.

Enough rambling from me....

You get more features and options from using a server/NOS (it really is a stupid term, how many OSes don't have networking features anymore... even PDA's).

llbbl
10-19-2004, 06:54 AM
yea I like term server much better when talking about computers. NOS is too well known in racing as nitrus. :D

lilac
10-24-2004, 03:08 AM
dear members,
i'm now focusing on novell netware 6.5 and novell professional 9.2. can anybody give opinions about the pros n cons in using them ?

ECA
10-24-2004, 11:41 AM
OK,
If you create a NOS, you have to KNOW that it will be compatible with Each computer OS you attach to it.
That every Link you create hardware wise, wireless, wifi, hardwire, cable, will work with it.(the ones you wish to use)
adapting LATER, is not a nice thing.