message_size_limit = 20480000

The above is roughly 20MB and is more than enough on a typical server.

/var/qmail/control/smtproutes

The contents is straight forward… to relay mail destined for domain.com through smtp.yourdomain.com add the following;

domain.com:smtp.yourdomain.com

If you want to relay ALL mail through smtp.yourdomain.com add;

:smtp.yourdomain.com


# omreport storage pdisk controller=0
Invalid controller value. Read, controller=0
No controllers found.


After some digging through the Dell mailling lists it became apparent that i’m missing the Dell Firmware Tools on my installation. Installing the firmware tools solved the problem.


# yum -y install dell_ft_install

# srvadmin-services.sh restart


Once done, all was fine.

mkdir -p /var/opt/xen/iso_import

Copy your ISO image to this directly, but be careful as the control domain filesystem has limited space and if this fills up, unpredictable behaviour will follow.

Next up you need to create the repository by running

xe sr-create name-label=ISOs type=iso device-config:location=/var/opt/xen/iso_import device-config:legacy_mode=true content-type=iso

You need to mount the new repository so it’s available on XenCenter

xe-mount-iso-sr /var/opt/xen/iso_import

You can now proceed to create your VM using the ISO repository you just added.

For disk layout, you can do whatever your comfortable with or follow the software that will be running on your servers guides for setting up the disk slices etc.

Start by installing only the core product, If I remember correctly it’s around 1.2GB in size. Once this has been done, and you have logged into your machine install the following packages from DVD/CD-ROM;

mkdir /mnt/cdrom
mount -F hsfs /dev/dsk/c0t2d0s2 /mnt/cdrom
pkgadd -d /mnt/cdrom/Solaris_10/Product/*ssh*

This will install;

SUNWsshcu SUNWsshdr SUNWsshdu SUNWsshr and SUNWsshu

pkgadd -d /mnt/cdrom/Solaris_10/Product/SUNWbash

Generate host keys;

/lib/svc/method/sshd -c
svcadm enable ssh
svcadm restart ssh

Or another way of generating host keys;

cd /etc/ssh
ssh-keygen -t rsa -f ssh_host_rsa_key
ssh-keygen -t dsa -f ssh_host_dsa_key
svcadm enable ssh
svcadm restart ssh


Install openssl, wget either from DVD/CD-ROM or you can grab it from the sunfreeware.com FTP site.

vi get_files.sh

#!/bin/sh

ftp -i -n -v ftp.sunfreeware.com << EOF
user "anonymous" "your@email.com"
cd pub/freeware/sparc/10
bin
mget gzip-1.4-sol10-sparc-local
mget wget-1.12-sol10-sparc-local.gz
mget libintl-3.4.0-sol10-sparc-local.gz
mget openssl-0.9.8l-sol10-sparc-local.gz
mget libiconv-1.13.1-sol10-sparc-local.gz
mget libgcc-3.4.6-sol10-sparc-local.gz
bye
EOF

:wq

chmod +x get_files.sh

./get_files

Once downloaded, install gzip first as you’ll need it to extract the rest of the archived packages you just downloaded;

pkgadd -d . gzip-1.4-sol10-sparc-local all
gunzip *.gz
pkgadd -d . <packagename> all

You now have a basic skeleton machine with SSH, bash and wget.

svcadm enable ssh

svcadm restart ssh

If you need to login as root, remember to set PermitRootLogin to yes and restart the daemon.

Enable automatic startup of X on boot
Change the default run level in /etc/inittab to 5
id:5:initdefault:

Solaris 10

Disable automatic startup of X on boot
# /usr/dt/bin/dtconfig -d

Enable automatic startup of X on boot
# /usr/dt/bin/dtconfig -e

boot cdrom - w

Your solaris installation will start in text mode.

This tutorial is NOT for upgrading your kernel, if you want to upgrade your kernel please read this tutorial.

1) Make a copy of your GENERIC kernel (never use GENERIC unless you want your changes wasted when you do a cvsup update)
root@machine# cd /usr/src/sys/i386/conf
root@machine# cp GENERIC CUSTOMEKERNEL

2. Edit the CUSTOMKERNEL to configure support for new hardware. Make sure all the required modules are loaded. If a dependancy is missing, your kernel build will fail.

3. Compile and install your new kernel.

root@machine# cd /usr/src
root@machine# make buildkernel KERNCONF=CUSTOMKERNEL
root@machine# make installkernel KERNCONF=CUSTOMKERNEL

4. Reboot and you have a fully customised kernel build.

* If you are running your system in securelevel you will need to make some changes before doing the actual kernel installation! In your /etc/rc.conf set kern_securelevel to kern_securelevel=”-1″ and reboot your machine, then proceed with the install of your custom kernel. After your custom kernel has been installed you can change the values back to whatever your requirements are.

* By doing a “make clean” on every kernel build defeats the purpose of a makefile. There are times when the build should be cleaned up, you can do it by doing a “make clean” or “config -r” to clean up obj. By doing it every time may make your kernel build run twice as long and it’s not necesary!

To launch two backends of the same type, you can assign a name to each launch like this;

launch=gmysql:connection1,gmysql:connection2

gmysql-connection1-host=10.10.10.1
gmysql-connection1-user=pdns
gmysql-connection1-dbname=pdns

gmysql-connection2-host=10.10.10.2
gmysql-connection2-user=pdns
gmysql-connection2-dbname=pdns