Hi Izzy,
> I think I've found the source of the problem, or at least the key
> difference. The bootdisk.ima on the iso image was generated using syslinux
> 3.20. If I take the bootdisk.ima file, and syslinux it using
> this machine, it creates a working boot CD. I'm using syslinux v 2.11, as
>
Eric
Eric Spakman wrote:
> Hi Izzy,
>
>> I think I've found the source of the problem, or at least the key
>> difference. The bootdisk.ima on the iso image was generated using syslinux
>> 3.20. If I take the bootdisk.ima file, and syslinux it using
>> this machine, it creates a working boot CD.
Erich;
Am Donnerstag, 15. Februar 2007 15:51 schrieb Erich Titl:
> Eric
>
> Eric Spakman wrote:
> > Hi Izzy,
> >
> >> I think I've found the source of the problem, or at least the key
> >> difference. The bootdisk.ima on the iso image was generated using
> >> syslinux 3.20. If I take the bootdis
I've created a Bering-uClibc_3.0.1 boot CD with USB thumb drive
support. I want to make the Save config, and Backup modules options in
the menu write their changes to a USB thumb drive. With the old backup
system, you could specify where to write changes. Is there a similar
interface for the
Hi Izzy,
Yes you can specify the backup device, it's the first entry in
'PKGPATH'. (either in leaf.cfg or syslinux.cfg)
# The first entry is the backup device.
# If equal packages exist on multiple devices, the ones on the left
most device have precedence.
PKGPATH="/dev/fd0u1680:msdos"
Eric
>
