A bit of pre-prep work to create the boot floppy which was required for my installation :

• Insert CD and Floppy into a Windoze machine if possible.
• cd to the cdrom directory
• cd to the dosutil directory
• type "mkboot"

Begin installation ....

• Be sure to set the BIOS to be CD bootable if possible.
• Insert boot floppy (if required, which it was in my case) and CD and restart Server.
• The screen will time out and proceed forward in 120 seconds (undocumented) if you dont do anything, or become pre-occupied with other problems, as happened to me.

Now the options :

• Answer "YES" to the color display question.
• Respond "OK" to introduction screen.
• Choose "US Keyboard" for keyboard type.
• Skip extra hardware detection.
• Respond "OK" at the probe screen.
• Choose "NO" for parallel support for install option (nice feature to have however).
• Choose "OK" to scrren about hardware finding results - in my case nothing was found.
• Select cdrom for installation media.
• Insert the cdrom if not already done in above steps.
• Choose the extended verbose mode of installation, because more is always better.
• For networking, choose "LAN (no PPP).
• Networking options I chose were for "IP Alias" and "Reverse ARP".
• Filesystem options chosen were : VFat (W95), SMB/LANMgr, SysV, UFS(BSD).
• Other network options were : lp (printer) and iBCS (required for backup exec client) .
• I didnt have any SCSI devices, so I chose "NO" for that option.
• Partition disks, on /dev/hda (ST310210A) using CFDISK - information shown below :

Disk as it appeared prior to slicing :

cfadisk 0.81, drive hda, 16 heads, 63 sectors, 19767 cylinders

Name	Flags	Partition Type	FSType	Label	Size in Mb
hda1	Boot	Primary	DOSFAT16(big)	[Dak& Disk]	1953.00
.	.	Pri/Logs	Free Space	.	7776.08

Disk as it appeared after to slicing :

cfadisk 0.81, drive hda, 16 heads, 63 sectors, 19767 cylinders

Name	Flags	Partition Type	FSType	Label	Size in Mb
hda1	Boot	Primary	Linux	"boot o/s"	1000.13
hda2	.	Primary	Linux Swap	"swap"	.
hda5	.	Logical	Linux	"local"	1999.76
hda6	.	Logical	Linux	"logs"	1000.13
hda7	.	Logical	Linux	"home"	500.07
hda8	.	Logical	Linux	"apps"	1999.76
.	.	Pri/Logs	Free Space	.	2973.31

• Write the information to disk, then quite, and finally choose done.
• Use /dev/hda2 for swap and check for bad blocks.
• Choose /dev/hda1 for root.

Filesystems should appear as follows :

Format all partitions during selection

Device	Size in Mb	Partition Type	Mount Point
/dev/hda1	1024096	Linux	/
/dev/hda5	2047720	Linux	/usr/local
/dev/hda6	1024096	Linux	/var/log
/dev/hda7	512032	Linux	/home
/dev/hda8	2047720	Linux	/export/apps

• Load network module "3c90x (Boomerang) and 3c59x (Vortex) - the o/s contains support for the 3c515 which is a nice feature since so many non-M/S system dont include this feature.
• I did allow auto probe, but no bootp .
• Network information :

  IP address	207.86.37.6
  Netmask	255.255.255.0
  Gateway	207.86.37.2
  DNS	207.86.37.2
  Domain Name	getthru.com
  Hostname	turbo.getthru.com
  2nd and 3rd DNS	NULL

• Log of install is kept in /tmp/turbopkg.log.
• Choose "CUSTOM" for the package choice options .
• Deselect the NetWare, AppleTalk, News Services, and UPS tools.
• Install regular kernel, no SMP and no APM.
• Install LILO boot loader into the /dev/hda1 MBR (recommended approach).
• The extra LILO instructions remains blank.
• Allow video card to probe for X configuration (version 4.3.2) - mine came back as N/A.
• Select S3Trio 64 (generic) card.
• 1 Mb video RAM (1024).
• Keymap is US, 101 Key, US English layout.
• Generic P/S 2 Mouse (Emulate 3rd button).
• 2 Button configuration.
• For monitor select custom (I use a program called pc-config for this.)
• 1024 x 768 in 256 color with 75 Khz.
• Princeton / Ultra 70F for custom description.
• Select 75 hz for the bandwidth value.
• (High Frequency) SVGA, 1024 x 768 @ 75.
• 8 bpp color.
• 1024 x 768 / 800 x 600 for video mode.
• Configure Automatically, 100 dpi fonts.
• Test shows 1024x768@75.33 and 800x600@72.07.
• Choose graphical login.
• Filenames worth remembering during this process were : /etc/Sysconfig/x-windows-system and /etc/X11/Xf86Config.
• Choose US/Eastern time zone.
• No printers defined.
• Allow auto probe of the ISA devices (use turbopnpcfg to reconfigure later if needed).
• Service to enable :
• AMD
• Arpwatch
• Autofs
• routed
• named
• sendmail
• Use the "TurboDesk/AfterStep" Window Manager/desktop/GUI setup.
• Remove floppy and choose finish.
• Kernel version is 2.2.12.

Further Configuration :

• Modify /etc/inetd.conf for telnet/ftp access.
• Modify /etc/hosts.allow for access on the network.
• Use xturbopkg for package information/installation/removal.
• Use xturbocpanel like redhat's linuxconf for administration after installation.
• Create a good /.profile and /.rhosts
• cp /etc/mail/sendmail.cf /etc/mail/sendmail.cf.orig
• Modify sendmail.cf, /etc/hosts for the unqualified domain problem. Set the /etc/hosts alias for the hostname as the hostname with a trailing dot. In addition, change the $FW macro in sendmail for the domain name to simply be the first part prior to the first dot.
• After modifying things like the hostname, and any other specifics in /usr/local/samba/lib/smb.conf file, start up samba, for easier downloads by :

  	  /usr/local/samba/bin/smbd -D
  	  /usr/local/samba/bin/nmbd -D
  	

• Now for optional software :

  SUDO (about 10 minutes)

  • Download sudo file from ftp://ftp.cs.colorado.edu/pub/sudo.
  
          Filename is : cu-sudo-v1.5.4.tar.Z (298857 byes)
  • move to /usr/local/Install/sudo
  • uncompress and extract
  • change to directory, run ./configure
  • edit the newly created Makefile for Paths.
  • make
  • make install
  • mkdir /var/adm/bin if not already in place
  • chmod 700 /var/adm/bin
  • mv /usr/local/etc/visudo /var/adm/bin/visudo
  • Thats it !!!

  Backup Exec Agent (about 10 minutes)

  ftp over the Seagate BackupExec agent, so that we can do nightly backups to the "enterprise backup server". If you dont have a copy, like I did, you can get it from Veritas' FTP Site, just look for the be__agnt.tar file.

• Create the /usr/local/Install/seagate/backup_exec/agent directory to store the ftp tar file.
• Create the /usr/local/seagate/backup_exec/agent destination directory, where the program will run from.
• Untar the file, so that it can be installed.
• Run the "INSTALL" script.
• Choose the /usr/local/seagate/backup_exec/agent directory for the destination.
• Setup the shares and backup server options, for the script.
• Run the "INSTALL" script.
• After the installation completes, startup the agent, by running "/etc/rc.d/rc3.d/S96agent.be start".
• Switch over to the backup server, and make sure it sees the new "turbo" Linux agent.

Network problems :

I had many problems getting my ISA ethernet card to properly work while my PCI ethernet card was working. It seems that even though I had properly configured everything, and could manually start it up after loading the correct kernel module, there were problems getting this to work after a reboot. Here is how I got around the problems :

• From the SCYLD Computing Corporation's Diagnostics page, I needed to download a few programs to help with this problem.
• First get the mii-diag source code (may need the libmii.c as well)
• Next get the 3c5x9setup source code
• Next get the pci-config source code
• Finally get the vortex-diag source code
• I had trouble compiling the vortex program, even though the instructions are at the bottom of the source code. However, I will give the exact syntax I used anyway - compile the vortex with " cc -O -Wall -o vortex-diag vortex-diag.c".
• I have included links to my pre-compiled versions for anyone else having problems : 3c5x9setup, mii-diag, pci-config, and vortex-diag
• With these programs compiled, I wrote two quick scripts to help me out with this. They are as follows (both designed to run from the directory where all the source code, binaries and libraries are already present - my case is /usr/local/Install/network) :

  fix_100_mbit.sh

  ./mii-diag -F100baseTx-FD
  ./mii-diag 
  
  ## use "./mii-diag" with no options to check
  
  ## all information from the : http://www.scyld.com/diag/index.html website
      

  fix_10_mbit.sh

  ./3c5x9setup -fv
  
  ## use "./3c5x9setup -fv" to check
  
  ## all information from the : http://www.scyld.com/diag/index.html website
      

• Next, I needed to create a startup script that would do this for me on bootup. This looks like ... :

  /etc/rc.d/init.d/nicfix (to set the interface at 100Mbit/Full Duplex)

  echo -n "Setting eth0 to 100Mb - Full Duplex: "
  cd /usr/local/Install/network
  /usr/local/Install/network/fix_100_mbit.sh
  echo
      

  /etc/rc.d/init.d/nicload (one liner to load the kernel module since isapnp wasnt doing it properly)

  /sbin/insmod 3c509
      

• And finally, I needed to modify the /etc/rc.d/init.d/network script to call these pieces upon a proper startup, and at precisely the right time. ( If you dont put this in the right spot in the network script, you can hose your whole network configuration ). I put it between lines 82 and 83, which was in the start area, right after the "for i in $interfaces; do" and the "./ifup $i boot" lines. My inserted text looks like this (remember, I am using eth1 for my problem card - you may need to change this ) :

  #####
  #####  Load 3c509 modules - Paul A. Luzzi - 10-11-2000
  #####
    if [ "$i" = "eth1" ]
      then
        echo "Loading module for 3c509 card:"
        /sbin/insmod 3c509
        echo
      fi
  #####
  #####  End of custom section added by Paul A. Luzzi
  #####
  	

• Installed new c++, g++, and gtk+ compilers and all needed libraries from the free Turbo 6.0 Workstation cd that comes with the Belkin switches. This then allowed me to install nmap, nmapfe, saint, ntop, ngrep, sudo, ethereal, cheops, netcat, and a few other tools for troubleshooting and learning.

During an install of turbo recently on another machine, I ran into a problem where I was trying to use NIS. During the install process, it asks if NIS is in use. Since this install was going to be an NIS client, I answered yes to the question, however the install never asks for an NIS domain name. Therefore after the install completes, on the first reboot, it search indefinately for an NIS master/slave to bind to, but has no domain name set, so it never succeeds. And since you cant interrupt it, and there is no boot disk/cdrom/recovery disk, its something that caused a great deal of struggle for me. I had seen the question asked many times in the newsgroups, but 99% of the answers were to reinstall again. I happen to dislike resinstalls and reboots to fix problems (as any of my peers will gladly let you know), so I was lucky enough to find the one answer that explained it. It is available online in the archives.

The article/posting basically states that in TurboLinux, if you setup NIS to run durring install, you're screwed - plain and simple. You never get the chance to setup your NIS domain, and the server hangs looking for an NIS master on the way up the first time. The fix is as follows :

• After the machine does its post, and is beginning to boot, hit the ctrl c keys a few times and hold down the left ctrl key and that will bring up the lilo prompt
• At the lilo prompt, enter "linux single" or "linux 1". I personally used "linux single" and havent tried the "linux 1" version yet. If you are unsure if its linux or turbolinux that should be entered, simply hitting the TAB key should provide the choices, but you only get about 3 to 5 seconds max, so make it snappy.
• At the "shell" prompt that finally appears, run the command "chkconfig --list". This will list all services and configurations set to run and at which run levels.
• Again at the "shell" prompt, type "chkconfig --del ypbind". This command will modify which runlevels the service runs at. It will prevent ypbind from running at any runlevel, but keeps all config files intact, if there are any.
• Rerun the "chkconfig --list" and you will see that ypbind is set to off for all runlevels now.
• Either "reboot" or "exit" will get you out of the single user mode and reboot back into multi user mode now with no NIS binding problems.