Trinux
Network
Configuration
NOTE: This documentation has *NOT* been updated to reflect changes in Trinux 0.890. The trinux-ide boot floppy contains the popnics.tgz kernel package which includes the following modules: 3c509.o 3c59x.o 8139too.o eepro100.o via-rhine.o pcnet32.o tulip.o. Which are automatically probed based on the file in \tux\config\modules on the boot floppy. This is should support most (but not all) popular nics, or at least the one's I have in my systems or that you can pick up at Fry's, CompUSA, or Best Buy. A complete set of unpackaged kernel modules is available in here. If the default doesn't work, delete the popnics.tgz package and find the kernel module and place it in the modules directory on the boot floppy. Reboot trinux and get a prompt (you may have to hit RETURN or CTRL-C) after it tells you no network devices were found and then manually install the kernel module using the insmod command (assuming you needed to install the National Semiconductor Driver). 
# cd /lib/modules
# insmod natsemi.o
# dmesg
# ifconfig -a

Assuming the module was correctly installed and shows up when you type ifconfig, then edit \tux\config\modules file to add the name of the kernel module. 


# fmount
# cd /floppy/tux/config
# nano modules
# cd /
# fumount
Do *not* delete the af_packet.o mii.o or 8390.o modules!

Supported NICs
Trinux supports provide in-built support for nearly a dozen of the most common NIC. Additional cards may be supported through kernel modules. I have included the name of the driver as it is listed in the kernel configuration file and the module name (if it were compiled) into the kernel). This information can help you research your card using the Red Hat Hardware Compatibility List and/or the Linux Ethernet HOWTO.

The following Ethernet cards should be supported in the default kernel

  • 3Com Etherlink 509 series (ISA)
  • 3Com Etherlink 590/905 series (PCI)
  • Realtek 8139 (PCI)
  • NE2000/Realtek 8129 (PCI)
  • NE2000 (ISA)A
  • AMD PCNet 32
  • Intel EtherExpress Pro 10/100
  • SMC EtherPower II
  • DEC Tulip

    The following Ethernet cards should be supported through kernel modules. Download the kernel module and add it to the boot floppy and your NIC should be detected automatically
    Driver Module Name

    Network Configuration
    Trinux is Network Operating System, period. While it theoretically could be used to perform backup and recovery or file integrity checking, use tomsrtbt instead. Also, Trinux is not designed to be your DSL/Cablemodem router/firewall. See freesco, Linux Router Project, or floppyfw.

    By default, trinux will use DHCP to configure the interface. If DHCP is not selected, the user will be prompted for the IP address/netmask, gateway, and DNS server. If you do not want to use DHCP, delete file named dhcp on the boot floppy in the /tux/options directory. You can delete the file from Windows or from within Trinux

    If you want to assign a permanent IP address, DNS server, default gateway, etc. You will need to create (or modify) several text files in the /tux/config directory on the boot floppy. Assuming the following configuration: eth0=192.168.0.200/24, eth1=192.168.1.200/24, gateway=192.168.0.1, dns=192.168.0.25, you could enter the following commands from within Trinux: 

    	mount -t msdos /dev/fd0 /floppy
	cd /floppy/tux/config
	echo "192.168.0.200 255.255.255.0" > eth0
	echo "192.168.1.200 255.255.255.0" > eth1
	echo "192.168.0.1" > gateway
	echo "192.168.0.25" > dns
    Hardware Compatibility
    Here are some of the hardware configurations I have successfully tested withTrinux. In general, it is safe to say that Trinux will boot on any 486 desktop with at Least 16mb of RAM. If you tweak the ramdisk size by editing the ramdisk file on the boot floppy you can make it run on machines with less memory. If you recompile the kernel to support 386's with math co-pro it should work on a 386, although I don't know why you'd want to (I have 386-20 still running at home, so I should know.)