I must prefix this installation story first, by giving a little bit of history on the install, then it may make more sense. I tried to install this, on what is now my NTSERV2 machine. It is a very nice PII-233 machine with SCSI drives, ATI video, and 128Mb RAM, but Caldera would have nothing to do with this. It is now installed on a 486/66 with 52Mb RAM, and a 1.6Gb IDE drive, but that is what it wanted. I did better in the end by having it there instead, but that is another story entirely. So keep in mind that these install instructions are mostly for the attempt on the PII/SCSI machine.
Here we go. This is what I did to TRY to install it on this machine configuration :
Current System Configuration :
- ASUS P2L97S ATX Motherboard with onboard Adaptec SCSI
- Intel Pentium II 233Mhz processor
- 128 Mb 168Pin DIMM's
- 4.5 Gig Seagate Barracuda Ultra2Wide drive
- Toshiba SCSI 20x CDRom
- SMC 9332DT Dual Ethernet 10/100 network (PCI)
- ATI 8Mb Expert RageII Video card
- PS/2 Mouse
Now I went thru some "hoops" to make this work, or at least I thought, but it failed anyway. Here is what I did :
- Went into SCSI utility from bootup, with CTRL-A and choose device 2 for boot, which is my 'cuda disk
- Insert CDRom and reset
- Hit enter at "boot:" prompt
- A whole bunch of messages flash by. If you would like to see them, use the "Shift-PG UP" and "Shift-PG DN" keys to scroll thru.
Here are some of the errors from that screen :
- I got a bunch of "unkown PCI device" errors, and assume they are from "device probing", but dont know for sure
- It correctly found the 233Mhz processor
- Only found 64 Meg of the memory ????
- Seems to have found the NIC and setup IGMP, ICMP, UDP, and TCP
- Shows linux kernel version 2.0.29 with gcc version 2.7.2.1
- Found two serial ports
- Found floppy
- Mounted root filesystem and started syslogd and klogd
- At this point, I was instructed to type "pnp" to disable PNP for the installation
- Hit Enter to continue
- Choose english and continue - this will begin LISA 2.3
- Choose US keyboard map
- LISA tells that no CDRoms or Hard Disks are detected. Says that this is normal for SCSI
- Anser NO to question about "have all been detected"
- Anser YES to cautions probing option for new hardware detected
- Answer OK for continue - Use "ALT-F6" to view messages, "ALT-F8" for errors and "ALT-F1" for GUI
- Continue - we will use hard disk at ID 2, and id didnt find the Ethernet NIC !!!!
- Choose NO to question about "have all been detected"
- Choose 3 to load kernel modules
- Choose 4 to load driver for NIC
- Tried 15, the DEC Chip Tulip (dc21x4x) PCI
- Left optional parameters blank
- Module tulip.o loads and is immediately usable.
- Choose OK (It does also find both ports on that card)
- Choose continue
- Choose 1 to return to previous menu (from load kernel modules menu)
- Choose 1 to finish kernel management (from kernel modules menu)
- Choose YES to change Linux Partitions (NOTES:I used "n" to add partitions, and "t" to change type for swap)
- Choose the default /dev/sda and continue
- Choose Y to fdisk the disk
- It wouldnt let me do anything, so I went back to the "Hard Disk Selection" menu and chose "No Further Changes"
- Message comes up saying "Select Partition for Swap", which I chose type of (0x82, Linux Swap)
- Check on OK (2) for dev/swap
- Choose CDRom for source of installation
- Choose (12) SCSI-CDRom-1 for source (/dev/scd0, 11, 0)
- Confirmation message appears
- Comes up with message about no available partition (DOS or Linux), please use fdisk to create partition. Click Continue and OK to reboot.
- Choose YES to format
- Choose YES to check for defective sectors
- Choose NO to include additional partitions. This is used to make separate filesystems
- Choose individual series selection (7). Initially I tried this method, but actually upon retries, I ended up going with (5) which is all packages which take 667Mb.
- Selected all packages except : (8)TEX and (13)Xemacs
- Continue
- OK to continue
- Prompt for FQDN : caldera.getthru.com
- Network Card : YES
- device name for network card : eth0
- IP for card : 192.168.1.9
- Subnet Mask : 255.255.255.0
- Broadcast : 192.168.1.255
- I had two ethernet "cards" so I had to repeat the above 6 steps again.
- default router/gateway is 192.168.1.1
- DNS : 192.168.1.1
- Do not use NIS
- Local time, (111) East/US
- Mouse of (7) PS/2 (bus mouse)
- No printer available
- Set root password : ********
- user "col" will be created
- comes up with message about "No boot loader/active partition"
- Install LILO boot manager into master boot record (1)
- Choose (1)for /vmliuz in bootdir
- use boot ramdisk of /boot/initrd.gz (needed for SCSI)
- Label the LILO as Linux (caldera)
- Accept default bootstr of "load_ramdisk=1 ramdisk_size=2880"
- "no further LILO entries"
- Aprove LILO.conf
- Choose YES to "Install LILO as configured"
- LILO boot manager successfully configure is OK
- Select services to start : All defaults plus (11)SMB
- Went with ATI Mach64, but to no avail. Ended up with (3)
- Choose YES to run XF86Setup now
- OK to postpone test to the end
- OK to continue
- Return to boot into new system
- Enter to switch to GUI
- Configure all settings (I had BIG problems, so I went and ran /usr/bin/X11/XF86Setup after the install finished)
Thats it for actual installation. Now I usually perform some additional setup tasks before I consider the system ready to use. They follow:
- Login as root (on console) and do "startx" to start the GUI.
- Picked up netscape navigator from ftp.caldera.com at pub/netscape/navigator.
- Install navigator using : "rpm -i --force nescape"
- updated date and time using timetool
- vi /.rhosts and setup hosts on the local network. Make sure perms are 600
- copied over working smb.conf from another server and fine tuned the variable pieces. (needed to edit locks, any names and shares)
- run the "/etc/rc.d/rc3.d/S91smb start" command to start up Samba
- Copy the Big Brother program over, so that the machine can be monitored.
As I mentioned earlier, this just would not work the way I wanted, so I ended up loading on much "less" hardware. I am happy with the current results, and aside from the hardware failure of my disk, I have had no problems whatsoever with this. I even go the Seagate (now Veritas) Backup Exec agent to work with this machine. It automatically loads the i.BCS Intel Binary Compatibilty Services kernel module, and just plain works.