[syslinux] Remotely Wipe Hard Drive

Miller, Shao shao.miller at yrdsb.edu.on.ca
Wed Jun 16 12:21:54 PDT 2010


Matthew,

As John "Warthog9" Hawley mentioned, B. K. O. has images which do not
require PXE servers.  You might take a look.

The image file used to "hijack the next boot" need not be in use when
you're ready to manipulate the HDD.  It could be a FAT filesystem with
Syslinux installed to it which could then use MEMDISK to boot yet
another image, this time as a RAM disk.

But it seems that you have nowhere to put a disk restoration image, if
that's also one of your goals.  In that case, consider the
aforementioned "hijacking" method, but also consider BIOS -> MBR ->
"hijack image" -> Syslinux -> gPXE with embedded script to SAN-boot.
You could SAN-boot a DOS image somewhere on the network and restore your
disk restoration image from there.  As long as it's guaranteed that
clients only perform read operations (and not write) on the SAN disk,
then it's safe to have multiple clients connected at the same time,
even.

- Shao Miller




More information about the Syslinux mailing list