Unlike 2.6 which I tried to install on a NexGen chip, I put this one on an AMD K6/233 with no problems. So I guess they should call it "Solaris for Intel Compatible"....
Current System Configuration :
Now the fun stuff :
This will begin the WebStart 3.0 Installation .......
Solaris Install Begins ......
Continued installation :
Further Configuration :
GCC:
TCL/TK:
GNUmake (about 10 minutes)
APACHE (about 10 minutes)
SUDO (about 10 minutes)
SAMBA (about 1 hour)
QPopper (about 30 minutes)
SAR (seconds ...)
top (about 3 minutes)
It found all controllers, motherboard, floppy, keyboard, mouse, drives, network, etc
Finds device of /pci@0,0/pci-ide@7,1/ide@1/sd@0,0:a
I was warned at this point that I was missing a capable partition, since it was a new drive. I was further warned that Solaris 8 requires 457 Mb for installation. I allowed the installer to do this for me.
Slice was /dev/dsk/c0d0, size was 512 Mb, cylinder start was 3
Boot primary section advises that boot device is /pci@0,0/pci-ide@7,1/ide@0/cmdk0,0:b
Hostname
Solaris8
IP address
207.86.37.8
Netmask
255.255.255.0
IPv6
No
Name Service
none
Slice
Size
/
500 Mb
swap
512 Mb
/var
500 Mb
/usr
2000 Mb
/opt
2000 Mb
free
4204 Mb
domain getthru.com
nameserver 207.86.37.2
hostresorder local bind
#ident "@(#)elxl.conf 1.3 98/02/23 SMI"
#
# Copyright (c) 1998, by Sun Microsystems, Inc.
# All rights reserved.
#
# Driver.conf file for the 3Com 3C90x
#
# To force full duplex operation, uncomment the following line:
full-duplex=1;
#
# To force half duplex operation, uncomment the following line:
#full-duplex=0;
#
# To force 10Mbps operation, uncomment the following line:
#speed=10;
#
# To force 100Mbps operation, uncomment the following line:
speed=100;
#
/usr/local/samba/bin/smbd -D
/usr/local/samba/bin/nmbd -D
Filename is : GNUgcc.2.95.2.i86pc.Solaris.8.pkg.tgz
ln -s /usr/local/bin/gmake /usr/local/bin/make
Filename is : cu-sudo-v1.5.4.tar.Z
(298857 byes)
cc=gcc
WORKGROUP=your workgroup name
Filename is : qpopper3.0b20.tar.Z
(2408406 byes)
#####
##### Qualcomm's Qpopper pop daemon
#####
pop3 stream tcp nowait root /usr/local/lib/qpopper qpopper -s
#####
##### Qualcomm's Qpopper pop daemon
#####
pop3 110/tcp # Post Office 3 daemon
Filename is : top-3.5beta9-sol8-intel-local.gz (60548 bytes)
Patch, Security :
Sun Solve's WebSite is where I got the information, on what patches to install. I had to download from two different areas. security patches. Keep in mind that I dont run any external ftp servers, or some of the other stuff, like sendmail, that are so vulnerable to many companies. These types of fixes didnt apply to me, but may to you. (I renamed the patches to shorten the names, and make them more understandable).
It is extremely important to be sure that you have enough free space available in /, /usr, /var, and /opt, so that you dont have incomplete packages installed. The recommended minimum is 4Mb.
For what its worth, I installed these packages into /usr/local/Install/patches. They will create many subdirectories and files underneath themselves, upon the untarring process, so be prepared for even more space to be used up.
I installed the following patches, in this order :.
$ su
Password: <type your root password>
# cd /usr/local/Install/patch
# unzip 8_x86_Recommended.zip
# cd 8_x86_Recommended
# ./install_cluster
# "y" to confirm continue
# more /var/sadm/install_data/Solaris_8_x86_Recommended_log
--> to be sure all is ok. I recieved errors for the following patches :
The following patches were not able to be installed:
109952-01
108881-02
but its ok.
# cd /
# /etc/shutdown -g0 -y -i6
--> to reboot and make sure only new patches are in use
# ./install_cluster Patch cluster install script for Solaris 8 x86_Recommended *WARNING* SYSTEMS WITH LIMITED DISK SPACE SHOULD *NOT* INSTALL PATCHES: With or without using the save option, the patch installation process will still require some amount of disk space for installation and administrative tasks in the /, /usr, /var, or /opt partitions where patches are typically installed. The exact amount of space will depend on the machine's architecture, software packages already installed, and the difference in the patched objects size. To be safe, it is not recommended that a patch cluster be installed on a system with less than 4 MBytes of available space in each of these partitions. Running out of disk space during installation may result in only partially loaded patches. Check and be sure adequate disk space is available before continuing. Are you ready to continue with install? [y/n]: y Determining if sufficient save space exists... Sufficient save space exists, continuing... Installing patches located in /usr/local/Install/patch/8_x86_Recommended Using patch_order file for patch installation sequence
The second section was the maintenance update, and it was called "mu1_Intel.zip" as of this writing. Initially I hadnt loaded it, but for about 2-3 weeks now, I have been experiencing a condition where the box will crash anywhere from 5-18 hours apart. It regularly panic's with the messages shown below:
Sep 17 16:44:02 solaris8 unix: [ID 836849 kern.notice] Sep 17 16:44:02 solaris8 panic[cpu0]/thread=e0ee01a0: Sep 17 16:44:02 solaris8 unix: [ID 911988 kern.notice] BAD TRAP: type=e (Page Fa ult) rp=ef65eb70 addr=1c occurred in module "genunix" due to a NULL pointer dere ference Sep 17 16:44:02 solaris8 unix: [ID 100000 kern.notice] Sep 17 16:44:02 solaris8 Sep 17 16:44:02 solaris8 unix: [ID 839527 kern.notice] top: Sep 17 16:44:02 solaris8 unix: [ID 702911 kern.notice] Page Fault Sep 17 16:44:02 solaris8 unix: [ID 418083 kern.notice] Bad kernel fault at addr= 0x1c Sep 17 16:44:02 solaris8 unix: [ID 764221 kern.notice] pid=28886, pc=0xfe86b618, sp=0xef65ebdc, eflags=0x10246
As I mentioned, sometimes this was every 5 hours, sometimes up to 18 hours apart, but at least every day. It filled up my /var filesystem eventually from having so many core files written to /var/crash/solaris8 directory. I am up for 2 days at this point and it seems pretty stable.
Update as of 10-12-2000 : this is working well and has been up for weeks now. Seems that it was just what the doctor ordered.
StarOffice 5.2:
Instructions, notes are here
Updates :
As of 12-28-2001, this server is now becoming my internal mail server as well. It is runnning the latest version of qpopper and houses all my mail. I am tired of switching mail accounts, so finally I will have a pluzzi.com mail address that I will have at least until 2010 (which is when my domain will need to be renewed). This process involved patching to the latest cluster of patches for recommended security and kernel (12) levels, as well as stopping all inet services. Since I also updated the maintenance update, I will offer this tip (I thought I already posted it somewhere, but .....) - the mu6 cant be unzipped in a /tmp of 600Mb or less. Thats what I have, and I run out of free files. There is space, but not enough inodes/files available. I extract into /opt/mu and link that to /tmp/mu to run the install. Doing all this fixed some bugs while running solaris8 on my non-intel x86 based chips. Now I can successfully run ALL KDE applications on the companion cd.
To make sendmail work properly, I had to convert it from a cronjob which ran every five minutes and processed the queue, back to a full running daemon. On servers which dont do legit sendmail processing, I no longer like to leave the daemon up all the time, since its an exposure. However, since this really is a mail server now, it makes sense to have sendmail up at all times.
The two files which I needed to populate were /etc/mail/local-host-names and /etc/mail/relay-domains. These contain the domain names for any domains which I recieve mail for. So in my case, it has pluzzi.com as its information. This allows the sendmail daemon to understand which domains are housed locally and which to relay. Setting those two files and restarting sendmail (/etc/init.d/sendmail stop ; /etc/init.d/sendmail start) was all that was required to make it all work.
For reference, I have included a link to the Solaris ability to set/change Solairs network interface parameters while the system is up. I always had to keep referring to my email for this and finally decided to put it on the web.
These are a few links to some good information on how to cable up a serial console, if you are not using the graphics card, or need to use a remote console solution. Sun Cables and Sun Cables 2