Server console

FAQ › EUZOS Server › Server console · Nederlands

What is it?

After installation EUZOS Server starts in the console: the shell of the EUZOS kernel on the server's own keyboard and screen. Nobody logs in on a server. The server console has the shared kernel commands (see the desktop console), plus five server-only commands: installer, packages, workplace, network and firewall. Desktop-only commands are not compiled in and answer with a message.

On a production server the console is restricted to a short list of commands (physical access is the only way in; real management goes through Server Admin).

How do I…?

How do I see which commands exist?

help. On the server it starts with the server lines:

EUZOS Server: no desktop; installer (text), packages (server roles, e.g. workplace)
installer [text]   the installer of EUZOS Server (environment, network, packages, disk); text: in the console
packages           the server packages (Workplace management, more later) and their state
network [...]      fixed address per adapter (NETWORK.TXT)
firewall           the incoming firewall (closed by default); change with Server Admin
workplace [setup [name]|now] EUZOS workplace server: state, set up, sign in now and fill the cache

followed by the shared commands.

Which commands may I use on a production server?

Only these (euzos_profile::console::allowed_on_server plus the harmless commands of allowed_without_session):

Anything else gives: "this command is not available on a production server; available: help, workplace, packages, installer, network, firewall, ip, dhcp, ping, dns, log, reboot, poweroff". Never sshd, profile, stick, run or install.

Which commands does a test-build server allow?

All commands of the server kernel, with the same rules as a test-build desktop (console::line_allowed).

Why does wifi (or mail, browser, …) not work?

It is not in EUZOS Server: the server answers "<command>: not in EUZOS Server, only in EUZOS Desktop (docs/EDITIONS.md)".

Can I use the old Dutch command names?

Yes, for one release, as hidden aliases (not in help): pakketten and pakket-lijst → packages, werkplek → workplace, netwerk → network, plus all shared ones (see the desktop console).

Details

• Header (since 28-10-2026, euzos_ui::console_header): a dark band with the logo, EUZOS Server and the motto "Digital Autonomy, Privacy, Security & Speed" (in the language of the server) under it, and on the right the version and architecture ("v13 · x86-64") with the first address and the uptime under it. The first boot lines (before the heap) show a one-line version in the bitmap font; serial and the boot log start with EUZOS Server v13 | x86-64 | Digital Autonomy, Privacy, Security & Speed. See docs/DESKTOP-DESIGN.md, "Console header".
• Two panes. On a screen of at least 135 columns (1024x768 and up) the console is split: commands and the prompt on the left (with a timestamp), all output on the right, each command's output under a dim header line; PgUp/PgDn scroll the output back. While the text installer runs, and over SSH, the console stays one pane. See Console.
• The console policy checks the line in the old Dutch form (crate::policy_line turns workplace now into werkplek nu, workplace setup into werkplek inrichten) because euzos_profile::console still uses those names; the command itself runs under its English name.
• On a production server crate::environment::shell_allowed first checks allowed_on_server; if that fails the line is refused with the message above.
• Boot: from a USB stick the installer; from the internal disk crate::packages::start starts the set-up roles; with no role the console only (screen::start_up).

Reference

Console commands

Server-only commands:

Desktop commands refused by the server ("not in EUZOS Server, only in EUZOS Desktop"): camera, privacy, sdio, wifi, mobile, offline, serveradmin, pckey, sound, browser, chromium, logout, mail, browserfeedback, explorer, microsoft, vault.

Server-relevant shared commands: ip, dhcp, ping, dns, http, net …, bcm (diagnostics of the Broadcom BCM5717-5720, only present in the server), e1000, rtl8168, sshd, log, ps, mem, pci, usb (with EHCI on the server), usbports, disks, ahci, nvme, install, fetch, stick, try, commit, date, reboot, poweroff, cmos, drivers, chipset, aml, acpi, battery, input, i2c, perf, counter, profile, environment, storage, profiledir, apps, and on x86-64 smp, kill, run, package, process, linuxtrace — see the desktop console and diagnostics. screen exists but only answers "EUZOS Server has no graphical screen, only the console (and the installer of the stick)".

Functions and modules

Config files

See also

• docs/EDITIONS.md ("Console of a production server")
• docs/ENGLISH.md ("Console commands")
• Desktop console