Date: Sun, 13 Feb 2011 10:59:37 +1030 From: "Daniel O'Connor" <doconnor@gsoft.com.au> To: Warren Block <wblock@wonkity.com> Cc: "Julian H. Stacey" <jhs@berklix.com>, hackers@freebsd.org Subject: Re: memstick.img is bloated with 7% 2K blocks of nulls Message-ID: <C51A098A-940A-4A74-9A93-7E8D93A72E2D@gsoft.com.au> In-Reply-To: <alpine.BSF.2.00.1102121510440.3827@wonkity.com> References: <201102111909.p1BJ9UAE097045@fire.js.berklix.net> <66758C9D-DCE2-4381-A4B1-956A48423CDD@kientzle.com> <alpine.BSF.2.00.1102121510440.3827@wonkity.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 13/02/2011, at 8:45, Warren Block wrote: > On Sat, 12 Feb 2011, Tim Kientzle wrote: >> Alternatively, of course, is there any way to use >> isofs instead of ufs for memstick.img? >=20 > Devin Teske's DruidBSD (http://druidbsd.sourceforge.net/) uses the = same image for CD, hard disk, or memstick. I don't know the technical = details. (VirtualBox didn't like it, but maybe it's a trivial fix.) I would guess it uses ISOLinux plus some voodoo hackery the same as = various Linux distros which do the same trick. For work I have made a FAT32 USB stick which uses syslinux to load an = MFS containing the loader & kernel and sysinstall then reads the install = files off FAT32. I did it this way so that people using it could edit = the configuration file without needing a BSD box handy. In theory the loader can read off FAT32 so the kernel could go onto the = flash drive too, however I couldn't get it to work :( -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?C51A098A-940A-4A74-9A93-7E8D93A72E2D>