UupOS Networking


Uup Network Services
  • Filesharing -- On automatically. All systems use it all the time. UNFS
  • DHCP
  • DNS
  • Mail
  • Backup
  • Data Base
  • Webserver
  • FTP
  • Licencing
  • Login

On bootup, workstations should locate all neccessary services automatically.

Network Design

UupOS uses a network-wide file system. This file system consists of the System Domain (//) and a tree of sub-domains. Hosts are assigned into these sub-domains with their entire file systems (/*.*) mounted at the host point. Below is an example path starting with the domain root.


And here is the same folder selected from the GUI list view:

Domain Creation

To set up a UupOS installation, first a Domain Root server must be installed and the root domain set up.

  1. A Name
  2. List of child subdomains
  3. A List of NADs
  4. Primary Server -- Auto or Assigned.
  5. Backup servers -- Auto or Assigned.
As a note of clarification, the // can contain hosts.

Once this is done, subdomains can be added. Subdomains have:
  1. A name
  2. A parent subdomain (or the root domain)
  3. A list of child subdomains.
  4. A list of NADs (See below)
  5. A list of rages of IP addresses of the hosts included in the subdomain
  6. A subdomain server -- Auto or Assigned by IP or MAC
  7. Backup subdomain servers -- Auto or Assigned by IP or MAC
  8. User Groups to whom subdomain is accessable.

An important feature is the automatic assignment of subdomain servers and backups. The goal is to have this be smart enough that most networks will use auto assignment. Assignments will be frequently re-examined by the OS and these assignments will be changed if a more optimal setup is possible.

DHCP is an important part of an Uup network. Although some hosts will use static addressing, most will use DHCP. The DHCP implementation will support the telling of hosts which subdomain they are assigned to and the address of the domain server and primary backup. As a result, the DHCP servers must use the domain database instead of a seperate DHCP config file. Find more info about Uup's DHCP implementation here.

Another note about this subdomain system is that it is independant of IP subnets. Subdomains can either follow IP subnets or not. In other words, one subdomain can span multiple IP subnets and multiple subdomains can share one IP subnet. Further more, a one-to-one setup is obviously possible.

Network Attached Devices

NADs can be add to the Domain tree.
This information must be stored in the domain tree.

  • IP Address
  • Device Type
  • Device Model
  • Driver location
  • Groups which can access

This is mostly for printers, but should be flexible for other devices.

Host Naming Conventions

The default name of Hosts should be based on the MAC. Uup can get this automatically

Naturally, this can be changed. Servers would obviously want something more meaningful. Depending on the network, workstations may also want something more meaningful. The host's Serial Number, physical location, or it's assigned function would make useful names to the System admin.

Naming systems by the assigned user's name makes little sense as it would require extra work for little gain as the user's name and avatar are already listed next to the host's name in the network browser.