Installing VMWare Server 1.0.2 on Slackware 11.0 in style

Install slackware 11.0 how you like. Package minimalism is your friend.
You will need the base X11 package and libsasl.

mkdir /etc/pam.d
mkdir /etc/rc.d/rc0.d through rc6.d
mkdir /etc/rc.d/init.d
make sure rc.sysvinit is executable.


Build a kernel with bonding, 802.1q VLAN support, and 802.1d bridging support.
go into /usr/src/linux/Documentation/networking and compile ifenslave:
# gcc -Wall -O -I/usr/src/linux/include ifenslave.c -o /sbin/ifenslave

Edit your rc.local to set up all of your networking (the MTU thing is needed 
  in 2.4 but does not appear necessary in 2.6):

# Build Ethernet channel bond
insmod bonding mode=0 miimon=100
ifconfig bond0 up
ifenslave bond0 eth0 eth1

# Create VLANs
modprobe 8021q
vconfig add bond0 2
vconfig add bond0 3
vconfig add bond0 4

ifconfig bond0.2 mtu 1492 up
ifconfig bond0.3 mtu 1492 up
ifconfig bond0.4 mtu 1492 192.168.1.12 netmask 255.255.255.0 up

route add default gw 192.168.1.1

--- END OF FILE rc.local ---

Get the latest kernel and build to suit. 2.6.20.1 worked flawlessly.

Install VMWare Server. When you go to configure it, it will fail to build
the vmmon module. Don't worry, this appears to be a deliberate ploy by VMware
to 'encourage' use of supported operating systems. Do this to fix:

Go to /usr/lib/vmware/modules/source and unpack vmmon.tar into a new directory.
Edit vmmon-only/include/compat_kernel.h. Go to line 21 and change it from

static inline _syscall1(int, compat_exit, int, exit_code);
  To
static inline _syscall1(int compat_exit, int exit_code);

Repack the vmmon-only dir and its contents into a replacement vmmon.tar file.

Re-run the vmware configuration script: vmware-config.pl .

When you get to the point of doing network configuration, use the editor mode
  to set up the networks as you like. vmnet2 for vlan2, vmnet3 for vlan3,
  vmnet4 for vlan4.

At this point you've got a working multi-vlan vmware server. Next is some 
  replication magic.