begin Craig Caughlin <[EMAIL PROTECTED]> 
> Hi folks,
> I'm trying to understand how to create my own bootable CD and some of you have been 
>kind enough to respond. Charles relied to me by saying:
> 
> Create a new CD image using appropriate software...make sure you use the 
>bootdisk.bin disk image to make the CD bootable.  The proper mkisofs command
> is included in the CD-ROM readme.
> 
> I don't understand how to use the bootdisk.bin image with my Nero software to create 
>the CD (I think Nero only recognizes .nrg, .iso, or .cue files...not .bin)??? He goes 
>on to say: 
 
i think a little confusion is going on here.  if i'm not mistaken, nero
is a cd writer, yes?   there are two things you're going to create: a cd
and a floppy.

1. burn the CD iso image.   ie- make a copy of the cd.  use nero for that.
2. make a copy of a boot floppy.  i don't use windows (at all!), so i
   couldn't tell you how to do it from windows.  however, from linux, you
   want to do:

        dd if=bootdisk.bin of=/dev/fd0

        the file bootdisk.bin is, loosely, a raw copy of the floppy itself.
        it's not an ISO image.

on the c0wz site, there's an excellent tutorial on boot floppies in
general.  it's thorough enough (imho) to be a definitive source on the
topic.  after you set up your router/firewall, you can play around with
creating your own bootfloppy with a larger format, like 1.680MB instead
of 1.44MB.

hopefully, i've said something here that sparked understanding.  if you
understood all this, you can follow the first few steps of the README
file on the dacherstein cd.

> WARNING:  If you need to change root.lrp, the kernel, or any syslinux settings 
>(including root ramdisk size), you'll need to modify the bootdisk.bin floppy-disk 
>image...it's a plain 1.44 Meg disk image, and can be manipulated with all the normal 
>tools (dd, winiamge, rawrite, &c). 
> 
> What does he mean "modify" the bootdisk.bin image, and why would you want to or need 
>to???
 
if you:

  1. if you create a larger capacity boot floppy (optional.  see above)
  2. want to play around with loading different modules (optional)

you need to modify the file syslinux.cfg and/or lrpkg.cfg (both are on
the boot floppy).  that's all i can really think of which is "obvious".
it's up to you.  i don't think there's a pressing need to modify the
boot disk -- i think you can pretty much get by without modifying it.
however, the default list of packages may not be to your liking.  for
example, i can't live without tcpdump.   :)

in dachstein 1.0.1, you *had* to modify syslinux.cfg if the cdrom wasn't
/dev/hda.  in version 1.0.2 it, thankfully, detects the cdrom so you
don't have to do this anymore.

pete

-- 
PGP Fingerprint: B9F1 6CF3 47C4 7CD8 D33E  70A9 A3B9 1945 67EA 951D
PGP Public Key:  finger [EMAIL PROTECTED]

_______________________________________________
Leaf-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-user

Reply via email to