What to do and how to do, this was a question to me at the beginning. I have no idea about isolinux. Fortunately I found that there is an answer called Cooking Up Some Slack(CUSS). After reading over that, I got to know something and began the process.

1 Prepare the packages
I pulled the -Current repository from rsync://rsync.osuosl.org/slackware/slackware-current to my workstation. Some directories and files are not necessary for the installation, to save bandwidth and time, it is sensible to –exclude them, like source/, pasture/, testing/, and so on.

2 Customize initrd.img
The initrd.img contains the system and scripts for installation. Most things will be customized here.

First, uncompress the initrd.img file to a directory. The initrd.img in -Current now is a gzipped cpio archive, rather than a gzipped image as in former versions(before and include 11.0).

$ gzip -cd initrd.img|cpio -i

Most of the installation scripts are stored in usr/lib/setup directory.

Second, to reduce the size of initrd.img, I deleted some directories, e.g., lib/modules/’kernel-version’(retain the -smp directory, I just use -smp to boot), usr/lib/setup(you need installpkg script at least), usr/man, and some files, e.g., scripts related to LVM in sbin/ directory(I don’t use LVM), odd files in etc/ directory, and so on.

Third, customize the environment and script during installation. The files related are etc/profile, etc/rc.d/rc.S, and also etc/inittab, etc/issue and so on, if you want.

This is some pieces of my setup script:

#!/bin/sh
#
# Copyright (c) 2008, Cherife Li .
# All rights reserved.
#
# Redistribution and use of this script, with or without modification,
# is permitted, and must retain the copyright above.
#
# THIS SOFTWARE IS PROVIDED BY THE AUTHOR “AS IS” AND ANY EXPRESS OR
# IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
# WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
# DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT,
# INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
# (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
# SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
# HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
# STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
# IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
# POSSIBILITY OF SUCH DAMAGE.
#
# Notice:
# - This script is used for one logical disk(not LVM).
# - The disk will be formatted to reiserfs file system.
# - I don’t care about the keyboard map setting.
#
# Bugs, advise, suggestion, or others, if any, please mail me.
#

TMP=/var/log/setup/tmp
SRC=/var/log/setup/src
DEST=/mnt

KERNEL=”`cut -f 5 -d ‘ ‘ /proc/cmdline|cut -f 2 -d =`”
KNAME=”huge-smp”
KVERSION=”`uname -r`”

if [ -d $TMP ]; then
rm -rf $TMP/* 1>/dev/null 2>&1
else
mkdir $TMP
fi

for i in $SRC $DEST; do
if [ -d $i ]; then
umount -f $i 1>/dev/null 2>&1
else
mkdir -p $i 1>/dev/null 2>&1
fi
done

echo
echo “+==============================================+”
echo ” Preparing the hard disk for installation …”
echo
sleep 3

DISK=`fdisk -l|grep ‘^Disk\ \/’|cut -f 2 -d ‘ ‘|cut -f 1 -d :|head -n1`

# clear existing partition(s), if any
PARTNUM=”`fdisk $DISK -l|tail -n1|cut -f 1 -d ‘ ‘|cut -c 9`”
while [ $PARTNUM -gt 0 ]; do
if [ $PARTNUM -gt 1 ]; then
echo -ne “d\n$PARTNUM\n” >> $TMP/fdisk.del
else
echo -ne “d\nw\n” >> $TMP/fdisk.del
fi
let PARTNUM=PARTNUM-1
done
cat $TMP/fdisk.del|fdisk $DISK

# Partition the hard disk into two partitions.
# one for swap with 2000M, the other for root(/) with the left of disk.
echo -ne “n\np\n1\n\n+2000M\n\nn\np\n2\n\n\nt\n1\n82\nw\n”|fdisk $DISK

# Active swap partition and add it to fstab temp
SWAP_PART=${DISK}1
mkswap -v1 $SWAP_PART
swapon $SWAP_PART
printf “%-16s %-16s %-11s %-16s %-3s %s\n” “$SWAP_PART” “swap” “swap” “defaults” “0″ “0″ >> $TMP/fstab.tmp

# Format root (/) partition, mount it, and add it to fstab temp
ROOT_PART=${DISK}2
echo “y”|mkreiserfs $ROOT_PART 1>/dev/null 2>&1
mount $ROOT_PART $DEST || exit 1
printf “%-16s %-16s %-11s %-16s %-3s %s\n” “$ROOT_PART” “/” “reiserfs” “defaults,noatime” “1″ “1″ >> $TMP/fstab.tmp

echo
echo ” The hard disk is ready for installation.”
echo “+=============================================+”
echo
#sleep 3

echo
echo “+=============================================+”
echo ” Processing the package installation …”
echo
sleep 3

# Mount the Slackware source
for MEDIA in \
/dev/hdc /dev/hdd /dev/hda /dev/hdb \
/dev/hde /dev/hdf /dev/hdg /dev/hdh \
/dev/hdi /dev/hdj /dev/hdk /dev/hdl \
/dev/sr0 /dev/sr1 /dev/sr2 /dev/sr3 \
/dev/pcd0 /dev/pcd1 /dev/pcd2 /dev/pcd3;
do
mount -t iso9660 -o ro $MEDIA $SRC 1>/dev/null 2>&1
if [ $? = 0 ]; then
break
fi
done

if [ "`mount|grep "$SRC"`" = "" ]; then
echo
echo “Couldn’t found the installation source!”
echo “Abort …”
echo
exit 1
else
# Process the installation
echo
echo “Found the installation source.”
echo “Now going to install the packages …”
echo
sleep 3
for series in a ap d l n; # you may do some change here
do
installpkg -root $DEST -priority ADD $SRC/slackware/$series/*.tgz
done

echo
echo ” All packages have been installed.”
echo “+=============================================+”
echo
sleep 3
fi

# config system
echo
echo “+==============================================+”
echo ” Configuring the system, wait for a while …”
echo

# Permission issue
chmod 755 $DEST $DEST/var/spool/mail 1>dev/null 2>&1

# Kernel setting
(cd $DEST/boot
rm -rf vmlinuz config System.map 1>/dev/null 2>&1
cp -a $SRC/kernels/$KERNEL/System.map.gz ./System.map-$KNAME-$KVERSION.gz
cp -a $SRC/kernels/$KERNEL/bzImage ./vmlinuz-$KNAME-$KVERSION
cp -a $SRC/kernels/$KERNEL/config ./config-$KNAME-$KVERSION
gzip -df System.map-$KNAME-$KVERSION.gz
ln -sf vmlinuz-$KNAME-$KVERSION vmlinuz
ln -sf config-$KNAME-$KVERSION config
ln -sf System.map-$KNAME-$KVERSION System.map
)

# Boot loader
cat > $DEST/etc/lilo.conf << EOF
boot = $DISK
timeout = 0
change-rules
reset
vga = normal
image = /boot/vmlinuz
root = $ROOT_PART
label = default
read-only
EOF
lilo -r $DEST -C /etc/lilo.conf

# Network
for nicm in \
e1000 tg3 eepro100 epic100 8139too 8139cp pcnet32 hp100 ne2k-pci olympic rcpci 3c59x acenic de4x5 dgrs sktr skge tulip via-rhine yellowfin dl2k ns83820;
do
modprobe $nicm 2> /dev/null
grep -q eth /proc/net/dev
if [ $? = 0 ]; then
echo “/sbin/modprobe $nicm” > $DEST/etc/rc.d/rc.netdevice
chmod 755 $DEST/etc/rc.d/rc.netdevice
break
else
rmmod $nicm 2> /dev/null
fi
done

if [ ! -f $DEST/etc/rc.d/rc.netdevice ]; then
echo
echo “Warning: No network interface card found.”
echo “Maybe, you need to check the card(s) or the modules.”
echo
fi

[... Network setups, e.g., $DEST/etc/rc.d/rc.inet1.conf, $DEST/etc/networks, \
$DEST/etc/hosts, $DEST/etc/HOSTNAME, $DEST/etc/resolv.conf, here \
snip...]

# Time config
cat $DEST/usr/share/zoneinfo/Asia/Shanghai > $DEST/etc/localtime
cat > $DEST/etc/hardwareclocl << EOF
localtime
EOF

# The /etc/fstab file
cat $TMP/fstab.tmp > $DEST/etc/fstab
printf “%-16s %-16s %-11s %-16s %-3s %s\n” “#/dev/cdrom” “/mnt/cdrom” “auto” “noauto,owner,ro” “0″ “0″ >> $DEST/etc/fstab
printf “%-16s %-16s %-11s %-16s %-3s %s\n” “#/dev/fd0″ “/mnt/floppy” “auto” “noauto,owner” “0″ “0″ >> $DEST/etc/fstab
printf “%-16s %-16s %-11s %-16s %-3s %s\n” “devpts” “/dev/pts” “devpts” “gid=5,mode=620″ “0″ “0″ >> $DEST/etc/fstab
printf “%-16s %-16s %-11s %-16s %-3s %s\n” “proc” “/proc” “proc” “defaults” “0″ “0″ >> $DEST/etc/fstab
printf “%-16s %-16s %-11s %-16s %-3s %s\n” “tmpfs” “/dev/shm” “tmpfs” “defaults” “0″ “0″ >> $DEST/etc/fstab

# Misc
cat > $DEST/etc/sysctl.conf << EOF
[... snip ...]
EOF

rm -f $DEST/var/spool/mail/root
sed -i '/^c[2-6].*agetty/s/^/#/' $DEST/etc/inittab
sed -i '/^\/sbin\/modprobe.*[parport_pc|lp|agpgart]/s/^/#/' $DEST/etc/rc.d/rc.modules
echo "blacklist ipv6" >> $DEST/etc/modprobe.d/blacklist
chroot $DEST /sbin/ldconfig
chroot $DEST /usr/bin/passwd root

# All finished
echo
echo “+=========================================================+”
echo ” Wooow, all done.”
echo ” Now you may reboot with CTRL-ALT-DELETE, enjoy. ;-)”
echo “+=========================================================+”
echo
cat /etc/wel.come

Last, rebuild the initrd.img.

$ find . | cpio -o -H newc | gzip -9 > /PATH/TO/isolinux/initrd.img

3 Customize the kernel
Re-build the kernel with your own config, then copy System.map.gz, bzImage, config, to the kernels/huge-smp directory, or an new directory in kernels/. I removed the ‘kernel-version’ subdirectory of kernels/, as I just use the -smp kernel.
Then modify isolinux/isolinux.cfg to fit the changes.

4 Specify the packages to install
In the slackware/ directory, I just put the packages needed here, and removed the unneeded packages. (The setup script will install all the packages in the series directories.) It is possible to use tagfile to install packages. But I just want a small ISO to build the installation CD/DVD. Which method to use depends on the need. The former is preferred to my situation. If using the later, slackbasics.org has an intro to the tagfiles.
I also added some packages built by myself. :-)

5 Build the ISO image
At the top directory of the ISO source,
$ mkisofs -o /tmp/slackware-install-cd.iso -R -J -V "Slackware Install CD" -hide-rr-moved -v -d -N -no-emul-boot -boot-load-size 4 -boot-info-table -sort isolinux/iso.sort -b isolinux/isolinux.bin -c isolinux/isolinux.boot -A Slack-CD .(do not forget this dot)
then this ISO image could be used to burn an install CD/DVD.

That’s all.

Notes:

Today Willy Tarreau gave me some advise. So I took a short time re-ran this benchmark. Here follows the detail.

platform
Everything kept unchanged except for the proxy_server, I replaced it with this new one:

    o OS: Linux 2.6.21.5-smp i686 (Slackware 12.0)
    o CPU:  Intel(R) Xeon(TM) CPU 3.06GHz x 2
    o MEM: 1024M x 6
    o DISK: RAID 5
    o Ethernet controller:  Intel Corporation 82546EB Gigabit Ethernet Controller

file pool
This time, I generated 2 sets of 10Mbyte files, one is 1,000 files of 10kbyte size, and the other is 10 files of 1MByte size.

benchmark

    * client: http_load
    * proxy server: varnish 1.1.2, squid 2.6.STABLE18, and squid 3.0.STABLE2.
    * http server: nginx/0.6.28

Using the same configurations of nginx, varnish, and squid 2/3, got the results below:

+++ 10KByte +++

$ http_load -verbose -parallel 100 -fetches 100000 ./10k.urls

100000 fetches, 100 max parallel, 1.024e+09 bytes, in 14.7505 seconds
10240 mean bytes/connection
6779.43 fetches/sec, 6.94213e+07 bytes/sec
msecs/connect: 0.400918 mean, 11.452 max, 0.067 min
msecs/first-response: 14.0161 mean, 1779.32 max, 0.24 min
HTTP response codes:
code 200 — 100000

* Squid 2.6.STABLE18:

100000 fetches, 100 max parallel, 1.024e+09 bytes, in 26.1771 seconds
10240 mean bytes/connection
3820.13 fetches/sec, 3.91181e+07 bytes/sec
msecs/connect: 0.497665 mean, 2990.79 max, 0.055 min
msecs/first-response: 21.0663 mean, 3018.84 max, 4.071 min
HTTP response codes:
code 200 — 100000

* Squid 3.0.STABLE2:

— 60.0027 secs, 100000 fetches started, 96249 completed, 0 current
100000 fetches, 100 max parallel, 9.85651e+08 bytes, in 102.375 seconds
9856.51 mean bytes/connection
976.8 fetches/sec, 9.62785e+06 bytes/sec
msecs/connect: 2.56114 mean, 91.428 max, 0.061 min
msecs/first-response: 27.8048 mean, 94.563 max, 1.288 min
3751 timeouts
3745 bad byte counts
HTTP response codes:
code 200 — 96255

+++ 1MByte +++

$ http_load -verbose -parallel 100 -fetches 1000 ./1m.urls

* Varnish 1.1.2:

— 60 secs, 6640 fetches started, 6540 completed, 100 current
10000 fetches, 100 max parallel, 1.04858e+10 bytes, in 91.1719 seconds
1.04858e+06 mean bytes/connection
109.683 fetches/sec, 1.15011e+08 bytes/sec
msecs/connect: 36.9187 mean, 9019.28 max, 0.08 min
msecs/first-response: 26.7986 mean, 475.462 max, 18.781 min
HTTP response codes:
code 200 — 10000

* Squid 2.6.STABLE18:

— 60 secs, 5856 fetches started, 5756 completed, 100 current
10000 fetches, 100 max parallel, 1.04858e+10 bytes, in 103.829 seconds
1.04858e+06 mean bytes/connection
96.3126 fetches/sec, 1.00991e+08 bytes/sec
msecs/connect: 2.4862 mean, 2994.65 max, 0.063 min
msecs/first-response: 15.9743 mean, 134.817 max, 8.222 min
HTTP response codes:
code 200 — 10000

* Squid 3.0.STABLE2:

— 60 secs, 6083 fetches started, 5983 completed, 100 current
10000 fetches, 100 max parallel, 1.04858e+10 bytes, in 103.054 seconds
1.04858e+06 mean bytes/connection
97.0367 fetches/sec, 1.0175e+08 bytes/sec
msecs/connect: 6.6513 mean, 3022.23 max, 0.089 min
msecs/first-response: 16.0642 mean, 787.308 max, 0.741 min
HTTP response codes:
code 200 — 10000

proxy server system status

+++ 10KByte +++

10k-varnish-iostat_xm5
10k-squid2-iostat_xm5
10k-squid3-iostat_xm5
10k-varnish-vmstat5
10k-squid2-vmstat5
10k-squid3-vmstat5

+++ 1MByte +++

1m-varnish-iostat_xm5
1m-squid2-iostat_xm5
1m-squid3-iostat_xm5
1m-varnish-vmstat5
1m-squid2-vmstat5
1m-squid3-vmstat5

proxy status

)-: Hmm, I’m still not satisfied with these results, especially the something about squid3.
Maybe I need to optimize the configuration of the proxies?

Today, I finished a benchmark to compare the caching performance and status between Varnish and Squid, which get widely focused on as reverse proxies.
Here we go.

platform

The test-network is made up of:

    * D-Link 1024R, a 24-port Gigabit Switch
    * http_server:
          o OS: Linux 2.6.21.5-smp i686 (Slackware 12.0)
          o CPU: Intel(R) Xeon(TM) CPU 2.80GHz x 2
          o MEM: 1024M x 6
          o DISK: SEAGATE ST373405LC SCSI Disk
          o Ethernet controller: Intel 82546EB PRO/1000 MT Dual Port Server Adapter
    * proxy_server:
          o OS: Linux 2.6.21.5-smp i686 (Slackware 12.0)
          o CPU:  Intel(R) Pentium(R) III CPU family 1133MHz GenuineIntel
          o MEM: 1024M
          o DISK: SEAGATE ST318406LC SCSI Disk
          o Ethernet controller:  Intel 82557/8/9 PRO/100+ Server Adapter
    * client
          o OS: Linux 2.4.31 i686 (Slackware 10.2)
          o CPU: Intel(R) Xeon(TM) CPU 2.80GHz x 2
          o MEM: 1024M x 6
          o Ethernet controller: Intel 82546EB Gigabit Ethernet Controller

file pool

#!/bin/sh
#
# Written for generating 2 sets of 100Mbyte files,
# one is 1,000 files of 100kbyte size, and
# the other is 10 files of 10MByte size.
# by Cherife Li
#

docroot=/home/wwwroot/

# generate the first set
mkdir -p $docroot/100k
cd $docroot/100k
for i in `seq 1 10`; do
mkdir -p files-$i;
for j in `seq 1 100`; do
dd if=/dev/zero of=files-$i/$j bs=100K count=1 2> /dev/null;
done;
done

# generate the second set
mkdir -p $docroot/10m
cd $docroot/10m
for i in `seq 1 5`; do
mkdir -p files-$i;
for j in `seq 1 2`; do
dd if=/dev/zero of=files-$i/$j bs=10M count=1 2> /dev/null;
done;
done

$ cd /home/wwwroot/
$ find ./100k/ | grep 'files.*/.' | sed 's#./#http://benchmark.lo/#' > 100k.urls
$ find ./10m/ | grep 'files.*/.' | sed 's#./#http://benchmark.lo/#' > 10m.urls

benchmark

 ______        ____________        ___________
|      |--A-->|            |--B-->|           |
|client|      |proxy server|      |http server|
|______|<--D--|____________|<--C--|___________|

    * client: http_load
    * proxy server: varnish 1.1.2, squid 2.6.STABLE18, and squid 3.0.STABLE2.
    * http server: nginx/0.6.28

The Nginx http server only ran the stand alone http service.
The proxy server ran the proxy service only the one been benchmarking at a time.

http_load
It’s a good load-generator as it

    * allows random fetches from a list of URLs
    * allows a large number of parallel requests
    * is portable.

There are also other test tools, check this page for detail.

+++ 100KByte +++

$ http_load -verbose -parallel 100 -fetches 100000 ./100k.urls

* Varnish 1.1.2:

— 60 secs, 6868 fetches started, 6768 completed, 100 current
— 120 secs, 13720 fetches started, 13620 completed, 100 current
— 180 secs, 20570 fetches started, 20470 completed, 100 current
— 240 secs, 27432 fetches started, 27332 completed, 100 current
— 300 secs, 34285 fetches started, 34185 completed, 100 current
— 360 secs, 41140 fetches started, 41040 completed, 100 current
— 420 secs, 47996 fetches started, 47896 completed, 100 current
— 480 secs, 54854 fetches started, 54754 completed, 100 current
— 540 secs, 61709 fetches started, 61609 completed, 100 current
— 600 secs, 68565 fetches started, 68465 completed, 100 current
— 660 secs, 75419 fetches started, 75319 completed, 100 current
— 720 secs, 82279 fetches started, 82179 completed, 100 current
— 780 secs, 89131 fetches started, 89031 completed, 100 current
— 840 secs, 95989 fetches started, 95889 completed, 100 current
100000 fetches, 100 max parallel, 1.024e+10 bytes, in 876.794 seconds
102400 mean bytes/connection
114.052 fetches/sec, 1.16789e+07 bytes/sec
msecs/connect: 116.758 mean, 9111.16 max, 0.256 min
msecs/first-response: 120.03 mean, 2494.66 max, 0.614 min
HTTP response codes:
code 200 — 100000

* Squid 2.6.STABLE18:

— 60 secs, 6898 fetches started, 6798 completed, 100 current
— 120 secs, 13748 fetches started, 13648 completed, 100 current
— 180 secs, 20595 fetches started, 20495 completed, 100 current
— 240 secs, 27439 fetches started, 27339 completed, 100 current
— 300 secs, 34287 fetches started, 34187 completed, 100 current
— 360 secs, 41136 fetches started, 41036 completed, 100 current
— 420 secs, 47983 fetches started, 47883 completed, 100 current
— 480 secs, 54829 fetches started, 54729 completed, 100 current
— 540 secs, 61675 fetches started, 61575 completed, 100 current
— 600 secs, 68523 fetches started, 68423 completed, 100 current
— 660 secs, 75371 fetches started, 75271 completed, 100 current
— 720 secs, 82221 fetches started, 82121 completed, 100 current
— 780 secs, 89065 fetches started, 88965 completed, 100 current
— 840 secs, 95909 fetches started, 95809 completed, 100 current
100000 fetches, 100 max parallel, 1.024e+10 bytes, in 878.411 seconds
102400 mean bytes/connection
113.842 fetches/sec, 1.16574e+07 bytes/sec
msecs/connect: 116.02 mean, 9114.65 max, 0.224 min
msecs/first-response: 115.596 mean, 619.381 max, 0.86 min
HTTP response codes:
code 200 — 100000

* Squid 3.0.STABLE2:

— 60 secs, 6885 fetches started, 6785 completed, 100 current
— 120 secs, 13720 fetches started, 13620 completed, 100 current
— 180 secs, 20577 fetches started, 20477 completed, 100 current
— 240 secs, 27418 fetches started, 27318 completed, 100 current
— 300 secs, 34266 fetches started, 34166 completed, 100 current
— 360 secs, 41111 fetches started, 41011 completed, 100 current
— 420 secs, 47957 fetches started, 47857 completed, 100 current
— 480 secs, 54812 fetches started, 54712 completed, 100 current
— 540 secs, 61656 fetches started, 61556 completed, 100 current
— 600 secs, 68503 fetches started, 68403 completed, 100 current
— 660 secs, 75346 fetches started, 75246 completed, 100 current
— 720 secs, 82198 fetches started, 82098 completed, 100 current
— 780 secs, 89040 fetches started, 88940 completed, 100 current
— 840 secs, 95891 fetches started, 95791 completed, 100 current
100000 fetches, 100 max parallel, 1.024e+10 bytes, in 876.658 seconds
102400 mean bytes/connection
114.07 fetches/sec, 1.16807e+07 bytes/sec
msecs/connect: 115.858 mean, 9111.16 max, 0.26 min
msecs/first-response: 116.423 mean, 3318.18 max, 29.481 min
HTTP response codes:
code 200 — 100000

+++ 10MByte +++

$ http_load -verbose -parallel 100 -fetches 1000 ./10m.urls

* Varnish 1.1.2:

— 60 secs, 100 fetches started, 0 completed, 100 current
— 120 secs, 196 fetches started, 96 completed, 100 current
— 180 secs, 231 fetches started, 131 completed, 100 current
— 240 secs, 304 fetches started, 204 completed, 100 current
— 300 secs, 389 fetches started, 289 completed, 100 current
— 360 secs, 434 fetches started, 334 completed, 100 current
— 420 secs, 509 fetches started, 409 completed, 100 current
— 480 secs, 585 fetches started, 485 completed, 100 current
— 540 secs, 637 fetches started, 537 completed, 100 current
— 600 secs, 714 fetches started, 614 completed, 100 current
— 660 secs, 786 fetches started, 686 completed, 100 current
— 720 secs, 844 fetches started, 744 completed, 100 current
— 780 secs, 915 fetches started, 815 completed, 100 current
— 840 secs, 987 fetches started, 887 completed, 100 current
1000 fetches, 100 max parallel, 1.04858e+10 bytes, in 899.718 seconds
1.04858e+07 mean bytes/connection
1.11146 fetches/sec, 1.16545e+07 bytes/sec
msecs/connect: 129.428 mean, 3128.09 max, 0.291 min
msecs/first-response: 1003.12 mean, 9619.7 max, 120.662 min
HTTP response codes:
code 200 — 1000

* Squid 2.6.STABLE18:

— 60 secs, 103 fetches started, 3 completed, 100 current
— 120 secs, 178 fetches started, 78 completed, 100 current
— 180 secs, 255 fetches started, 155 completed, 100 current
— 240 secs, 322 fetches started, 222 completed, 100 current
— 300 secs, 379 fetches started, 279 completed, 100 current
— 360 secs, 458 fetches started, 358 completed, 100 current
— 420 secs, 518 fetches started, 418 completed, 100 current
— 480 secs, 583 fetches started, 483 completed, 100 current
— 540 secs, 661 fetches started, 561 completed, 100 current
— 600 secs, 721 fetches started, 621 completed, 100 current
— 660 secs, 786 fetches started, 686 completed, 100 current
— 720 secs, 863 fetches started, 763 completed, 100 current
— 780 secs, 926 fetches started, 826 completed, 100 current
— 840 secs, 984 fetches started, 884 completed, 100 current
1000 fetches, 100 max parallel, 1.04858e+10 bytes, in 894.062 seconds
1.04858e+07 mean bytes/connection
1.11849 fetches/sec, 1.17282e+07 bytes/sec
msecs/connect: 137.644 mean, 9128.16 max, 0.283 min
msecs/first-response: 131.811 mean, 3509.99 max, 28.891 min
HTTP response codes:
code 200 — 1000

* Squid 3.0.STABLE2:

— 60 secs, 105 fetches started, 5 completed, 100 current
— 120 secs, 190 fetches started, 90 completed, 100 current
http://benchmark.lo/10m/files-2/2: timed out
http://benchmark.lo/10m/files-2/2: byte count wrong
http://benchmark.lo/10m/files-1/1: timed out
http://benchmark.lo/10m/files-1/1: byte count wrong
http://benchmark.lo/10m/files-5/2: timed out
http://benchmark.lo/10m/files-5/2: byte count wrong
http://benchmark.lo/10m/files-3/2: byte count wrong
http://benchmark.lo/10m/files-3/2: byte count wrong
http://benchmark.lo/10m/files-3/2: byte count wrong
http://benchmark.lo/10m/files-1/1: byte count wrong
http://benchmark.lo/10m/files-2/1: timed out
http://benchmark.lo/10m/files-2/1: byte count wrong
http://benchmark.lo/10m/files-1/1: byte count wrong
http://benchmark.lo/10m/files-2/1: byte count wrong
http://benchmark.lo/10m/files-2/1: byte count wrong
http://benchmark.lo/10m/files-4/2: timed out
http://benchmark.lo/10m/files-4/2: byte count wrong
http://benchmark.lo/10m/files-2/2: byte count wrong
http://benchmark.lo/10m/files-3/2: byte count wrong
http://benchmark.lo/10m/files-3/2: byte count wrong
http://benchmark.lo/10m/files-3/2: byte count wrong
http://benchmark.lo/10m/files-4/2: byte count wrong
http://benchmark.lo/10m/files-4/2: byte count wrong
http://benchmark.lo/10m/files-2/2: byte count wrong
http://benchmark.lo/10m/files-4/2: byte count wrong
http://benchmark.lo/10m/files-3/2: byte count wrong
http://benchmark.lo/10m/files-3/2: byte count wrong
http://benchmark.lo/10m/files-3/2: byte count wrong
http://benchmark.lo/10m/files-2/2: byte count wrong
http://benchmark.lo/10m/files-2/2: byte count wrong
http://benchmark.lo/10m/files-2/2: byte count wrong
http://benchmark.lo/10m/files-3/2: byte count wrong
http://benchmark.lo/10m/files-1/1: byte count wrong
http://benchmark.lo/10m/files-1/1: byte count wrong
http://benchmark.lo/10m/files-4/2: byte count wrong
http://benchmark.lo/10m/files-2/1: byte count wrong
http://benchmark.lo/10m/files-2/1: byte count wrong
http://benchmark.lo/10m/files-1/1: byte count wrong
http://benchmark.lo/10m/files-2/2: byte count wrong
http://benchmark.lo/10m/files-2/1: byte count wrong
http://benchmark.lo/10m/files-4/2: byte count wrong
http://benchmark.lo/10m/files-2/2: byte count wrong
http://benchmark.lo/10m/files-4/2: byte count wrong
— 180 secs, 260 fetches started, 160 completed, 100 current
http://benchmark.lo/10m/files-2/2: byte count wrong
http://benchmark.lo/10m/files-1/1: byte count wrong
http://benchmark.lo/10m/files-3/2: byte count wrong
http://benchmark.lo/10m/files-2/2: byte count wrong
http://benchmark.lo/10m/files-2/1: byte count wrong
http://benchmark.lo/10m/files-3/2: byte count wrong
http://benchmark.lo/10m/files-3/2: byte count wrong
http://benchmark.lo/10m/files-2/2: byte count wrong
http://benchmark.lo/10m/files-2/2: byte count wrong
http://benchmark.lo/10m/files-2/2: byte count wrong
http://benchmark.lo/10m/files-2/1: byte count wrong
http://benchmark.lo/10m/files-4/2: byte count wrong
http://benchmark.lo/10m/files-2/2: byte count wrong
http://benchmark.lo/10m/files-2/2: byte count wrong
http://benchmark.lo/10m/files-2/2: byte count wrong
— 240 secs, 315 fetches started, 215 completed, 100 current
— 300 secs, 395 fetches started, 295 completed, 100 current
— 360 secs, 464 fetches started, 364 completed, 100 current
— 420 secs, 521 fetches started, 421 completed, 100 current
— 480 secs, 596 fetches started, 496 completed, 100 current
— 540 secs, 664 fetches started, 564 completed, 100 current
— 600 secs, 725 fetches started, 625 completed, 100 current
— 660 secs, 798 fetches started, 698 completed, 100 current
— 720 secs, 865 fetches started, 765 completed, 100 current
— 780 secs, 929 fetches started, 829 completed, 100 current
— 840 secs, 997 fetches started, 897 completed, 100 current
1000 fetches, 100 max parallel, 1.03922e+10 bytes, in 886.272 seconds
1.03922e+07 mean bytes/connection
1.12832 fetches/sec, 1.17258e+07 bytes/sec
msecs/connect: 130.639 mean, 3127.72 max, 0.21 min
msecs/first-response: 186.15 mean, 3578.41 max, 34.601 min
5 timeouts
53 bad byte counts
HTTP response codes:
code 200 — 1000

proxy server status

+++ 100KByte +++

100k.varnish.iostat_xm5.log
100k.varnish.vmstat5.log
100k.squid2.iostat_xm5.log
100k.squid2.vmstat5.log
100k.squid3.iostat_xm5.log
100k.squid3.vmstat5.log

+++ 10MByte +++

10m.varnish.iostat_xm5.log
10m.varnish.vmstat5.log
10m.squid2.iostat_xm5.log
10m.squid2.vmstat5.log
10m.squid3.iostat_xm5.log
10m.squid3.vmstat5.log

After finished each benchmark, the status is as follow:

conclusion

The data here, the reference in your mind.
That which is the better choice as a caching proxy, depends on your own judgement.

notes

1. Varnish can cache files immediately.
I found this while comparing the fetching of 10MB files.
Varnish just request the nginx server for the file only once, but Squid will requests them for about
10 times of varnish does.

2. Varnish provides easier access to proxy status.

3. Squid is more than a web proxy, while Varnish is more than an http accelerator (cache proxy).
The Varnish web site claims that Varnish is ten to twenty times faster than the popular Squid
cache on the same hardware.

An simple intro from the FUSE website:

With FUSE it is possible to implement a fully functional filesystem in a userspace program.  Features include:

    * Simple library API
    * Simple installation (no need to patch or recompile the kernel)
    * Secure implementation
    * Userspace - kernel interface is very efficient
    * Usable by non privileged users
    * Runs on Linux kernels 2.4.X and 2.6.X
    * Has proven very stable over time

The following figure shows the path of a filesystem call:

Operating Systems FUSE Supportes are Linux-2.4.X, Linux-2.6.X, FreeBSD, NetBSD, Mac OS X, Windows, OpenSolaris, GNU/Hurd. Check this link for detail.

There are various types of Filesystems based on FUSE, like:

# ArchiveFileSystems - accessing files inside archives (tar, cpio, zip, etc.)
# CompressedFileSystems - accessing files in a compressed image (gz, zlib, LiveCDs, etc.)
# DatabaseFileSystems - storing files in a relational database (MySQL, BerkeleyDB, etc.) \
    or ones allowing searching using tags or SQL queries
# EncryptedFileSystems - storing files in a more secure way by using a secret key
# MediaFileSystems - storing files on media devices such as cameras and music players \
    or accessing and categorizing media files
# HardwareFileSystems - provide access to weird hardware
# MonitoringFileSystems - provide notification when a file changes
# NetworkFileSystems - storing files on remote computers, including file servers and web sites
# NonNativeFileSystems - traditional disk-based file systems that aren't standard on \
    Linux (NTFS, ZFS, etc.)
# UnionFileSystems - merging multiple file systems into a single tree
# VersioningFileSystems - file systems that remember old versions of files and ones which \
    provide access to version control systems

Check this link for up-to-date detail.

SystemImager is a part of System Installation Suite which automates Linux installs, software distribution, and production deployment.

SystemImager makes it easy to do automated installs (clones), software distribution, content or data distribution, configuration changes, and operating system updates to your network of Linux machines. You can even update from one Linux release version to another!

It can also be used to ensure safe production deployments. By saving your current production image before updating to your new production image, you have a highly reliable contingency mechanism. If the new production enviroment is found to be flawed, simply roll-back to the last production image with a simple update command!

Some typical environments include: Internet server farms, database server farms, high performance clusters, computer labs, and corporate desktop environments.

Benchmark

Check this link for detail.

Useful Resource

    * Article on linux.com: Automate Linux installation and recovery with SystemImager
    * HowTo sur Capweb.biz : Cr茅er des images de votre syst猫me Linux avec SystemImager (FR)
    * Clustering Is Not Rocket Science
    * Avatars and Grid 2.0 (article on Grid Today quoting SystemImager as a core component \
        used in the famous virtual world Second Life)
    * Automating Xen Virtual Machine Deployment (how to integrate SystemImager with Xen to \
        create a totally open source deployment framework of virtual machines) 

    * The Linux Enterprise Cluster
    * High Performance Linux Clusters with OSCAR, Rocks, OpenMosix, and MPI
    * Linux Clustering: Building and Maintaining Linux Clusters
    * Distributed and Parallel Systems: From Instruction Parallelism to Cluster Computing
    * High Performance Computing Clusters with Intel庐 Architecture, Part 2 

    * System Installation Suite: Massive Installation for Linux - Sean Dague

    * SystemImager @ Ottawa Linux Symposium 2002 - Sean Dague
    * SystemImager @ LinuxTag 2007 in Berlin - Andrea Righi, Brian Elliott Finley, Erich Focht
          o Get paper and presentation of the talk in PDF 

    * SystemImager at CINECA
          o The IBM BCX/5120 cluster in CINECA uses SystemImager
    * SystemImager at niflheim
          o Wiki about SystemImager used for the NIFLHEIM cluster installation

In kernel space, the inotify API provides a mechanism for monitoring file system events. Inotify can be used to monitor individual files, or to monitor directories. When a directory is monitored, inotify will return events for the directory itself, and for files inside the directory.

In user space, there are several tools use inotify, such as pyinotify, IWatch, incron, logsend, mswatch, inotail, inotify-tools and the others I don’t know of.
On Dec 3, inotify-tools was added into Slackware-Current repository. As the style of Patrick Volkerding and Slackware Distro, I think inotify-tools is worthy more to use.

Inotify-tools currently consists of a library called “libinotifytools” and two programs called “inotifywait” and “inotifywatch“, with a third kinda sorta planned but don’t hold your breath.

Libinotifytools library provides a thin layer on top of the basic inotify interface. The primary use is to easily set up watches on files, potentially many files at once, and read events without having to deal with low-level I/O. There are also several utility functions for inotify-related string formatting.

Inotifywait efficiently waits for changes to files using Linux’s inotify interface. It is suitable for waiting for changes to files from shell scripts. It can either exit once an event occurs, or continually execute and output events as they occur, and can recursively watch entire directory trees.

Inotifywatch listens for filesystem events using Linux’s inotify interface, then outputs a summary count of the events received on each file or directory.

How to use them? Please check their man pages for further information :-)

Below is a test on inotifywait. On one console monitored outputs, on another did some operation.

monitoring console:

root@ws:~# inotifywait -mr --format '%w %f %e' /home/cherife
Setting up watches.
Beware: since -r was given, this may take a while!
Watches established.
/home/cherife/tmp/ test CREATE,ISDIR
/home/cherife/tmp/ test OPEN,ISDIR
/home/cherife/tmp/ test CLOSE_NOWRITE,CLOSE,ISDIR
/home/cherife/tmp/ test OPEN,ISDIR
/home/cherife/tmp/test/  OPEN,ISDIR
/home/cherife/tmp/ test CLOSE_NOWRITE,CLOSE,ISDIR
/home/cherife/tmp/test/  CLOSE_NOWRITE,CLOSE,ISDIR
/home/cherife/tmp/test/ new CREATE,ISDIR
/home/cherife/tmp/test/ new OPEN,ISDIR
/home/cherife/tmp/test/ new CLOSE_NOWRITE,CLOSE,ISDIR
/home/cherife/  OPEN,ISDIR
/home/cherife/  CLOSE_NOWRITE,CLOSE,ISDIR
/home/cherife/ tmp OPEN,ISDIR
/home/cherife/tmp/  OPEN,ISDIR
/home/cherife/ tmp CLOSE_NOWRITE,CLOSE,ISDIR
/home/cherife/tmp/  CLOSE_NOWRITE,CLOSE,ISDIR
/home/cherife/tmp/ test OPEN,ISDIR
/home/cherife/tmp/test/  OPEN,ISDIR
/home/cherife/tmp/ test CLOSE_NOWRITE,CLOSE,ISDIR
/home/cherife/tmp/test/  CLOSE_NOWRITE,CLOSE,ISDIR
/home/cherife/tmp/test/new/ foo CREATE
/home/cherife/tmp/test/new/ foo OPEN
/home/cherife/tmp/test/new/ foo MODIFY
/home/cherife/tmp/test/new/ foo CLOSE_WRITE,CLOSE
/home/cherife/  OPEN,ISDIR
/home/cherife/  CLOSE_NOWRITE,CLOSE,ISDIR
/home/cherife/ tmp OPEN,ISDIR
/home/cherife/tmp/  OPEN,ISDIR
/home/cherife/ tmp CLOSE_NOWRITE,CLOSE,ISDIR
/home/cherife/tmp/  CLOSE_NOWRITE,CLOSE,ISDIR
/home/cherife/tmp/ test OPEN,ISDIR
/home/cherife/tmp/test/  OPEN,ISDIR
/home/cherife/tmp/ test CLOSE_NOWRITE,CLOSE,ISDIR
/home/cherife/tmp/test/  CLOSE_NOWRITE,CLOSE,ISDIR
/home/cherife/tmp/ test OPEN,ISDIR
/home/cherife/tmp/test/  OPEN,ISDIR
/home/cherife/tmp/ test CLOSE_NOWRITE,CLOSE,ISDIR
/home/cherife/tmp/test/  CLOSE_NOWRITE,CLOSE,ISDIR
/home/cherife/tmp/test/ new OPEN,ISDIR
/home/cherife/tmp/test/new/  OPEN,ISDIR
/home/cherife/tmp/test/ new CLOSE_NOWRITE,CLOSE,ISDIR
/home/cherife/tmp/test/new/  CLOSE_NOWRITE,CLOSE,ISDIR
/home/cherife/tmp/test/new/ foo OPEN
/home/cherife/tmp/test/new/ foo ACCESS
/home/cherife/tmp/test/new/ foo CLOSE_NOWRITE,CLOSE
/home/cherife/tmp/ test OPEN,ISDIR
/home/cherife/tmp/test/  OPEN,ISDIR
/home/cherife/tmp/ test CLOSE_NOWRITE,CLOSE,ISDIR
/home/cherife/tmp/test/  CLOSE_NOWRITE,CLOSE,ISDIR
/home/cherife/tmp/test/ new OPEN,ISDIR
/home/cherife/tmp/test/new/  OPEN,ISDIR
/home/cherife/tmp/test/new/ foo DELETE
/home/cherife/tmp/test/ new CLOSE_NOWRITE,CLOSE,ISDIR
/home/cherife/tmp/test/new/  CLOSE_NOWRITE,CLOSE,ISDIR
/home/cherife/tmp/test/ new DELETE,ISDIR
/home/cherife/tmp/test/new/  DELETE_SELF
/home/cherife/tmp/test/new/  IGNORED

operations:

[cherife@ws:~/tmp/test $] history|tail -6
520  mkdir -p tmp/test/new
521  echo "this is a test." > tmp/test/new/foo
522  cd tmp/test
523  cat new/foo
524  rm new/ -r
525  history|tail -6

In some case, yeah, it’s very powerful and useful for system administration.

Okay, maybe you need to read about slackware package howtos before continuing reading ;)

The related files are as below. You’d better use the newest ones in my SlackBuild directory.

slack-desc

varnish: VARNISH - a high-performance HTTP accelerator
varnish:
varnish: Varnish is targeted primarily at the FreeBSD 6 and
varnish: Linux 2.6 platforms, and will take full advantage
varnish: of the virtual memory system and advanced I/O
varnish: features offered by these operating systems.
varnish:
varnish: Homepage: http://varnish.projects.linpro.no/
varnish:
varnish:

rc.varnishd

#!/bin/sh
# Written to start/stop/restart varnishd.
# by Cherife Li <cherife@dotimes.com>
#

VARNISH_VCL_CONF=/etc/varnish/default.vcl
VARNISH_PIDFILE=/var/run/varnish.pid
VARNISH_LOCKFILE=/var/lock/subsys/varnish
VARNISH_DAEMON=/usr/sbin/varnishd
VARNISH_PARAM="-p thread_pool_max=1500 \
                                -p thread_pools=5 \
                                -p listen_depth=512 \
                                -p client_http11=off"

VARNISH_LOG_PIDFILE=/var/run/varnishlog.pid
VARNISH_LOG_LOCKFILE=/var/lock/subsys/varnishlog
VARNISH_LOG_DAEMON=/usr/bin/varnishlog
LOGFILE=/var/log/varnish.log
VARNISH_LOG_OPTS="-a -w ${LOGFILE} \
                                      -D -P ${VARNISH_LOG_PIDFILE}"

# Default address and port to bind to
# Blank address means all IPv4 and IPv6 interfaces, otherwise specify
# a host name, an IPv4 dotted quad, or an IPv6 address in brackets.
VARNISH_LISTEN_ADDRESS=
VARNISH_LISTEN_PORT=80

# Telnet admin interface listen address and port
VARNISH_ADMIN_LISTEN_ADDRESS=127.0.0.1
VARNISH_ADMIN_LISTEN_PORT=81

# The minimum number of worker threads to start
VARNISH_MIN_THREADS=1

# The Maximum number of worker threads to start
VARNISH_MAX_THREADS=100

# Idle timeout for worker threads
VARNISH_THREAD_TIMEOUT=120

# Cache file location
VARNISH_STORAGE_FILE=/var/lib/varnish_storage.bin

# Cache file size: in bytes, optionally using k / M / G / T suffix,
# or in percentage of available disk space using the % suffix.
VARNISH_STORAGE_SIZE=1G

# Backend storage specification
VARNISH_STORAGE="file,${VARNISH_STORAGE_FILE},\
                                    ${VARNISH_STORAGE_SIZE}"

# Default TTL used when the backend does not specify one
VARNISH_TTL=120

# VARNISH_DAEMON_OPTS is used by the init script.
# If you add or remove options, make sure you
# update this section, too.
VARNISH_DAEMON_OPTS="\
-a ${VARNISH_LISTEN_ADDRESS}:\
     ${VARNISH_LISTEN_PORT} \
-f ${VARNISH_VCL_CONF} \
-T ${VARNISH_ADMIN_LISTEN_ADDRESS}:\
     ${VARNISH_ADMIN_LISTEN_PORT} \
-t ${VARNISH_TTL} \
-w ${VARNISH_MIN_THREADS},\
     ${VARNISH_MAX_THREADS},\
     ${VARNISH_THREAD_TIMEOUT} \
-u nobody -g nobody \
-P ${VARNISH_PIDFILE} \
-s ${VARNISH_STORAGE}"

case "$1" in
'start')
        echo -n "Starting varnish daemon..."
        $VARNISH_DAEMON \
                $VARNISH_DAEMON_OPTS \
                $VARNISH_PARAM > /dev/null 2>&1
        $VARNISH_LOG_DAEMON $VARNISH_LOG_OPTS
        touch $VARNISH_LOCKFILE $VARNISH_LOG_LOCKFILE
        echo
        ;;
'stop')
        echo -n "Stopping varnish daemon..."
        kill -9 `cat $VARNISH_PIDFILE`
        kill -9 `cat $VARNISH_LOG_PIDFILE`
        rm -f $VARNISH_PIDFILE $VARNISH_LOG_PIDFILE \
                  $VARNISH_LOCKFILE $VARNISH_LOG_LOCKFILE
        killall varnishd 2> /dev/null
        echo
        ;;
'restart')
        $0 stop
        sleep 1
        $0 start
        ;;
*)
        echo "usage $0 start|stop|restart"
        exit 1
esac

exit 0

varnish.SlackBuild

#!/bin/sh
# Build/install varnish the way Slackware's binary package is made:
# Written by Cherife Li <cherife@dotimes.com>

# Set initial variables:
PRGNAM=varnish
VERSION=1.1.2
ARCH=${ARCH:-i486}
BUILD=${BUILD:-1}
CWD=$(pwd)
TMP=${TMP:-/tmp/SBo}
PKG=$TMP/package-$PRGNAM
OUTPUT=${OUTPUT:-/tmp}

DOCUMENTATION="ChangeLog LICENSE INSTALL README"

if [ "$ARCH" = "i386" ]; then
  SLKCFLAGS="-O2 -march=i386 -mcpu=i686"
elif [ "$ARCH" = "i486" ]; then
  SLKCFLAGS="-O2 -march=i486 -mtune=i686"
elif [ "$ARCH" = "i686" ]; then
  SLKCFLAGS="-O2 -march=i686 -mtune=i686"
fi

set -e

rm -rf $PKG
mkdir -p $TMP $PKG $OUTPUT
cd $TMP
rm -rf $PRGNAM-$VERSION
tar -xvf $CWD/$PRGNAM-$VERSION.tar.gz
cd $PRGNAM-$VERSION
chown -R root:root .
chmod -R u+w,go+r-w,a-s .

CFLAGS="$SLKCFLAGS" \
CXXFLAGS="$SLKCFLAGS" \
./configure \
  --prefix=/usr \
  --sysconfdir=/etc/varnish/ \
  --localstatedir=/var \
  --mandir=/usr/man

make -j3 || exit 1
make install DESTDIR=$PKG || exit 1

mkdir -p $PKG/etc/{varnish,rc.d} $PKG/usr/man
cat $TMP/$PRGNAM-$VERSION/etc/default.vcl > $PKG/etc/default.vcl.new
cat $TMP/$PRGNAM-$VERSION/etc/zope-plone.vcl > $PKG/etc/zope-plone.vcl.new
cat $CWD/rc.varnishd > $PKG/etc/rc.d/rc.varnishd.new

# Strip everything for good measure:
( cd $PKG
  find . | xargs file | grep "executable" | grep ELF |\
        cut -f 1 -d : | xargs strip --strip-unneeded 2> /dev/null
  find . | xargs file | grep "shared object" | grep ELF |\
        cut -f 1 -d : | xargs strip --strip-unneeded 2> /dev/null
)

mkdir -p $PKG/usr/doc/$PRGNAM-$VERSION
cp -a $DOCUMENTATION $PKG/usr/doc/$PRGNAM-$VERSION
cat $CWD/$PRGNAM.SlackBuild > \
        $PKG/usr/doc/$PRGNAM-$VERSION/$PRGNAM.SlackBuild

( cd $PKG/usr/man
  find . -type f -exec gzip -9 {} \;
  for i in $( find . -type l ) ; do ln -s $( readlink $i ).gz $i.gz ; rm $i ; done
)

mkdir -p $PKG/install
cat $CWD/slack-desc > $PKG/install/slack-desc
cat $CWD/doinst.sh > $PKG/install/doinst.sh

cd $PKG
/sbin/makepkg -l y -c n \
        $OUTPUT/$PRGNAM-$VERSION-$ARCH-$BUILD$TAG.tgz

Tarball download
Download a tarball including the three files above, but without the varnish source code.

Enjoy (-: