A network operating system (NOS) is a specialized operating system for a network device such as a router, switch or firewall.
Historically operating systems with networking capabilities were described as network operating system, because they allowed personal computers (PCs) to participate in computer networks and shared file and printer access within a local area network (LAN). This description of operating systems is now largely historical, as common operating systems include a network stack to support a client–server model.
History[edit]
Theseus is a new OS written from scratch in Rust to experiment with novel OS structure, better state management, and how to shift OS responsibilities like resource management into the compiler. We are continually working to improve the OS, including its fault recovery abilities for higher system availability without redundancy, as well as. Note: The headings on this list indicate the Macintosh System bundle names; the bullet points indicate the version of the System File included in that bundle. This is to make it clearer for people searching for specific bundle versions as opposed to System File versions. Finder File versions are not indicated. 1 Classic Mac OS 1.1 Macintosh System Software (0 - 0.3) 1.1.1 System File 1 1.1.2.
Early microcomputer operating systems such as CP/M, MS-DOS and classic Mac OS were designed for one user on one computer.[citation needed]Packet switching networks were developed to share hardware resources, such as a mainframe computer, a printer or a large and expensive hard disk.[1] As local area network technology became available, two general approaches to handle sharing of resources on networks arose.[citation needed]
Historically a network operating system was an operating system for a computer which implemented network capabilities. Operating systems with a network stack allowed personal computers to participate in a client-server architecture in which a server enables multiple clients to share resources, such as printers.[2][3][4] Early examples of client-server operating systems that were shipped with fully integrated network capabilities are Novell NetWare using the Internetwork Packet Exchange (IPX) network protocol and Banyan VINES which used a variant of the Xerox Network Systems (XNS) protocols.[citation needed]
These limited client/server networks were gradually replaced by Peer-to-peer networks, which used networking capabilities to share resources and files located on a variety of computers of all sizes. A peer-to-peer network sets all connected computers equal; they all share the same abilities to use resources available on the network.[3] The most popular peer-to-peer networks as of 2020 are Ethernet, Wi-Fi and the Internet protocol suite. Software that allowed users to interact with these networks, despite a lack of networking support in the underlying manufacturer's operating system, was sometimes called a network operating system. Examples of such add-on software include Phil Karn's KA9Q NOS (adding Internet support to CP/M and MS-DOS), PC/TCP Packet Drivers (adding Ethernet and Internet support to MS-DOS), and LANtastic (for MS-DOS, Microsoft Windows and OS/2), and Windows for Workgroups (adding NetBIOS to Windows). Examples of early operating systems with peer-to-peer networking capabilities built-in include MacOS (using AppleTalk and LocalTalk), and the Berkeley Software Distribution.[citation needed]
Today, distributed computing and groupware applications have become the norm. Computer operating systems include a networking stack as a matter of course.[1] During the 1980s the need to integrate dissimilar computers with network capabilities grew and the number of networked devices grew rapidly. Partly because it allowed for multi-vendor interoperability, and could route packets globally rather than being restricted to a single building, the Internet protocol suite became almost universally adopted in network architectures. Thereafter, computer operating systems and the firmware of network devices tended to support Internet protocols.[5]
Network device operating systems[edit]
Network operating systems can be embedded in a router or hardware firewall that operates the functions in the network layer (layer 3).[6] Notable network operating systems include:
Proprietary network operating systems[edit]
- Cisco IOS, a family of network operating systems used on most Cisco Systemsrouters and current Cisco network switches. Earlier switches ran the Catalyst Operating System CatOS
- RouterOS by MikroTik.
- ZyNOS, used in network devices made by ZyXEL.
NetBSD, FreeBSD, or Linux based operating systems[edit]
- DD-WRT, Linux kernel based DD-WRT is Linux-based firmware for wireless routers and access points as well as low-cost networking device platforms such as the LinksysWRT54G
- Dell Networking Operating System, DNOS9 is NetBSD based, while OS10 uses the Linux kernel
- Extensible Operating System runs on switches from Arista and uses an unmodified Linux kernel
- ExtremeXOS (EXOS), used in network devices made by Extreme Networks
- FTOS or Force10 Operating System, is the firmware family used on Force10 Ethernet switches
- OpenWrt used to route IP packets on embedded devices
- pfSense, a fork of M0n0wall, uses PF
- SONiC, a Linux-based network operating system developed by Microsoft
- Cumulus Linux distribution, which uses the full TCP/IP stack of Linux
- VyOS, an open source fork of the Vyatta routing package
- ONOS, an open source SDN operating system (hosted by The Linux Foundation) for communications service providers that is designed for scalability, high performance and high availability.
See also[edit]
References[edit]
- ^ abAnn McHoes & Ida M. Flynn (2012). Understanding Operating Systems (6 ed.). cengage Learning. p. 318. ISBN9781133417569.CS1 maint: uses authors parameter (link)
- ^Dean, Tamara (2009). 'Network Operating Systems', Network+ Guide to Networks, 421(483)
- ^ abWinkelman, Dr. Roy (2009). 'Chapter 6: Software', An Educator's Guide to School Networks, 6.
- ^Davis, Ziff (2011). 'network operating system', PCmag.comRetrieved 5/7/2011.
- ^Ann McHoes & Ida M. Flynn (2012). Understanding Operating Systems (6 ed.). cengage Learning. p. 305. ISBN9781133417569.CS1 maint: uses authors parameter (link)
- ^Al-Shawakfa, Emad; Evens, Martha (2001). 'The Dialoguer: An Interactive Bilingual Interface to a Network Operating System.', Expert Systems Vol. 18 Issue 3, p131, 19p, Retrieved 5/7/2011.
External links[edit]
Phil Mac And Louie Unbroken
If you intend to use the graphical interface and installed Phenix using theMac or Windows graphical installers, no further configuration is necessary -just double-click the icon for the main Phenix GUI. Instructions below arefor users of the command-line installer and/or programs.
Setting up the command-line environment
Once you have successfully installed PHENIX, to set up your environmentplease source the phenix_env file in the phenix installation directory(for example - replace '' with the actual installed version,such as '1.8.4-1496'):
or
To run jobs remotely, you need to source the phenix_env in your .cshrc(or equivalent) file.
If you used the graphical Mac installer, you can find the files here: Dash 4 5 3.
The following environmental variables should now be defined (here withexample values):
It is not necessary (or useful) to define environmental variables forSOLVE/RESOLVE for PHENIX. If you have them set in your environment theyare ignored by PHENIX.
Documentation
You can find documentation in the PHENIX GUI (under the Help menu).Alternatively, you can use a web browser to view the documentationsupplied with PHENIX, by typing: Mac doesn t recognize usb.
If this doesn't work because of browser installation issues then you canpoint a web browser to the correct location in your PHENIX installation(for example):
or:
For license information please see the LICENSE file.
Phil Manos
For the source of the components see SOURCES.
Help
You can join the PHENIX bulletin board and/or view the archives:
Phil Mcstowe
Alternatively you can send email to:
