The bootleg boot script

Harm copied a RAMdisk from Ubuntu-7.0.4 and it it changed just a few files:

  find -mtime -7 -exec ls -ld {} \;
  drwxr-xr-x  11 root root 4096 2007-07-10 12:23 .
  drwxr-xr-x  13 root root 4096 2007-07-10 12:17 ./scripts
  -rw-r--r--  1 root root 2726 2007-07-05 09:22 ./scripts/local
  -rwxr-xr-x  1 root root 5009 2007-07-05 17:35 ./scripts/start_bootleg
  -rwxr-xr-x  1 root root 5009 2007-07-05 17:35 ./scripts/start_bootleg.iwi
  -rwxr-xr-x  1 root root 5008 2007-07-05 17:36 ./scripts/start_bootleg.wing

When in /conf/initramfs.conf BOOT is set to local, /scripts/local is run by init. At the end of /scripts/local, a Conference under Docker is added which starts the script /scripts/start_bootleg.

Example 1.  Bootleg intervention

# Bootleg intervention : By
# Initial : Mon May 21 16:53:33 CEST 2007
# This is the new bootleg intervention for 2.6.20 kernels and up
# Using cpio initrd's

# Unmount the root fs from the initrd script
umount /root

echo "Starting bootleg"
sleep 1      # calm down a little bit


# Mount the ubuntu root fs again
mount ${roflag} -t ${FSTYPE} ${ROOTFLAGS} ${ROOT} ${rootmnt}

# End Bootleg intervention

This start_bootleg script mounts an NFS share from a server [44] and starts a secondary script that resides on the mount [45] Once the secondary script is running, the boot is considered to be in its 2nd boot phase.

[44] Which server is configured in the start_bootleg script itself. Typically this is the file server for the domain.

[45] Which secondary script is also configured in the start_bootleg script. As of this writing, bootleg is started.