sanos home

Installing sanos

In order to install sanos you first need to make a boot disk. You can either use the compiled version or build sanos from source. If you want to build sanos from source see  Building sanos from source. If you want to use the compiled version download the sanos-bin-x.x.x.zip file from the download page. Unzip the files into a directory (e.g. c:\sanos) and go to the build directory and execute the mkbootdisk batch script:

c:\sanos\build> mkbootdisk

This makes a sanos.flp file in the win\img directory. This file can be written to a blank floppy disk using the mkfloppy utility found in the win\tools directory:

c:\sanos> win\tools\mkfloppy a: win\img\sanos.flp

Boot your computer using the disk. Remember to set Floppy Disk as your first boot device in your BIOS setup. Booting sanos from floppy will not install any files on your hard disk.

If everything goes well you should see something like this:

The boot disk starts the shell as the initial application. You can use many of the standard Unix shell commands like ls, cp, mv, etc. The help command displays all the supported commands.

Viewing system information from the /proc file system

The /proc file system contains a number of virtual files that can be used for displaying system information, e.g. the following command display a list of all threads in the system:

\$ more /proc/threads

The following /proc files can be used:

• memmap - BIOS memory map information
• memusage - Memory usage per allocation type
• memstat - Summary memory statistics
• physmem - Physical memory map
• pdir - Page directory information
• virtmem - Virtual memory ranges
• kmem - Kernel memory
• kmodmem - Kernel module memory
• kheap - Kernel heap statistics
• vmem - User virtual memory map
• cpu - CPU information
• traps - Trap/interrupt statistics
• uptime - Time since last boot
• loadavg - CPU load average
• threads - Thread information
• dpcs - DPC statistics
• handles - Handle table
• syscalls - System call statistics
• files - Open files
• bufpools - Buffer pools
• bufstats - Buffer pool statistics
• kmods - Kernel modules
• umods - User modules
• units - Installed devices from PCI and PnP enumeration
• devices - Installed devices
• screen - Screen buffer
• apm - Advanced Power Management information
• pbufs - Network packet buffers
• netstat - Network packet statistics
• netif - Network interfaces
• arp - ARP table
• udpstat - UDP sockets
• rawstat - RAW sockets
• dhcpstat - DHCP information
• tcpstat  - TCP sockets
• version - Kernel version information

Cofiguring network settings

The default installation is set up to use DHCP to obtain TCP/IP settings from a DHCP server. If you do not have a DHCP server on your network you can either boot without network or manually configure network.

To boot without network remove the following section from os.ini before building the bootdisk:

[netif]

eth0

To configure your network manually change the [netif] section to something like:

[netif]

eth0:ip=192.168.123.5,gw=192.168.123.1,mask=255.255.255.0

You can use the edit program to modify the /etc/os.ini file (i.e. edit /etc/os.ini).

Installing sanos on the hard disk

WARNING: Running the fdisk and setup programs can destroy all files on your hard disk.
DO NOT DO THIS UNLESS YOU KNOW WHAT YOU ARE DOING !!!

The setup utility is configured to install sanos on the hard disk. You can change the setup script in /setup/setup.ini to customize the setup. Before you install sanos on the hard disk you need to make sure that your have at least one partition on the primary hard disk. Also, this partition must be bootable. You can setup the partitions using the fdisk utility on the boot floppy:

• Start the fdisk utility.
• Create new master boot record using the (m)br command.
• Add new partition 0 using the (a)dd command.
• Make the partition bootable using the (b)oot command.
• Commit changes using the (c)ommit command.
• Exit fdisk with the e(x)it command.

If you want to install sanos on the hard disk type:

\$ setup

at the shell prompt after sanos has started. This will install sanos on the first partition of the primary hard disk. After the setup program completes remove the floppy and boot the computer. Now sanos will boot from the hard disk.

Customizing the setup script

When the setup utility is executed it uses the setup script file located in /setup/setup.ini. If you want to use another setup script you can just give its filename as an argument on the command line.

The setup script is an .ini file with a section for each stage of the setup:

#
# setup.ini
#

[setup]
product=Sanos OS

[actions]
format
sysprep
mount
kernel
mkdirs
copy
unmount

[format]
device=hd0a
blocksize=4096
cache=1024
quick=0

[sysprep]
device=hd0a
bootstrap=/setup/boot
loader=/setup/osldr.dll

[mount]
mntfrom=hd0a
mntto=/mnt
fstype=dfs

[kernel]
kernel=/bin/krnl.dll
target=/mnt/bin

[mkdirs]
/mnt/dev
/mnt/proc
/mnt/tmp
/mnt/mnt
/mnt/etc
/mnt/usr

[copy]
/mnt/bin/os.dll=/bin/os.dll
/mnt/bin/sh.exe=/bin/sh.exe
/mnt/bin/edit.exe=/bin/edit.exe
/mnt/bin/httpd.dll=/bin/httpd.dll
/mnt/bin/ftpd.exe=/bin/ftpd.exe
/mnt/bin/telnetd.exe=/bin/telnetd.exe
/mnt/bin/login.exe=/bin/login.exe
/mnt/bin/3c905c.sys=/bin/3c905c.sys
/mnt/bin/pcnet32.sys=/bin/pcnet32.sys
/mnt/bin/ne2000.sys=/bin/ne2000.sys
/mnt/bin/rtl8139.sys=/bin/rtl8139.sys
/mnt/bin/eepro100.sys=/bin/eepro100.sys
/mnt/bin/sis900.sys=/bin/sis900.sys
/mnt/bin/msvcrt.dll=/bin/msvcrt.dll
/mnt/bin/kernel32.dll=/bin/kernel32.dll
/mnt/bin/user32.dll=/bin/user32.dll
/mnt/bin/advapi32.dll=/bin/advapi32.dll
/mnt/bin/wsock32.dll=/bin/wsock32.dll
/mnt/bin/winmm.dll=/bin/winmm.dll
/mnt/bin/jinit.exe=/bin/jinit.exe
/mnt/etc/krnl.ini=/setup/krnl.ini
/mnt/etc/os.ini=/setup/os.ini

[unmount]
path=/mnt