|
From: Bruce S. <bw...@ar...> - 2003-05-18 17:17:37
|
> > Speaking of testing, what good is the results of "make dist"? > > Can that be used for testing some how? > > Actually for testing you'd only need to run 'make iso'. Yes, that's what I've been doing. I've been wondering about the purpose of "make dist", and this jogged my memory to ask. I've never even run a "make dist" command. Why would I want to? What's it good for? I'm missing the point again! :-) > Another tip: > Put a dos formated disk into drive a: then do > dd if=/dev/fd0 of=floppy-image > You can mount this > mount floppy-image /mnt -o loop > cd /mnt > rm * (only if floppy was not empty) > tar -xvjf /path-to/etc.tar.bz2 > cd homedir > umount /mnt OK, that creates an _un_tar'ed etc directory in the floppy image, but I thought the boot process wanted /etc tar'ed up? Shouldn't the "tar -xvjf /path-to/etc.tar.bz2" command be: "cp /path-to/etc.tar.bz2 /mnt" instead??? > Now configure vmware to use the bootcd.iso and the floppy-image > files as cdrom and floppy drive. Right. Got 'ya. > For testing you'd usually cd to tmp/ISO/initrdtree and create > your scripts there (except for config/etc/initrd/linuxrc, > config/etc/initrd/links and tmp/ETC/etc/init.d/functions). > > Then run 'scripts/build.sh iso' and retest with vmware. Will do, thanks again! - BS |