|
From: Diego T. <dt...@co...> - 2004-09-05 22:55:27
|
i've been compiling the new 1.3.1 from cvs, and i've found a full new interactive script to install the iso on the usb storage device. wow! :) so, couple of questions: if i configure an alternative partition to hold the configuration scripts, what size should i choose? why are we supporting 3 boot methods? (syslinux, lilo & grub?) shouldn't syslinux be enough? why there are two choices between the initrd fs? cramfs/ext2... shouldn't we stay with cramfs? maybe a little advice about the partition type on the configuration partition could be a good thing... :) -- -- gnupg keyfingerprint -- 48AF 5BF9 8F54 2966 64CC 2327 7CD0 DD91 B09D 5799 -- Use of a keyboard or mouse may be linked to serious injuries or disorders. Diego Torres - dtorres at anthalia dot org - Madrid / España |
|
From: Diego T. <dt...@co...> - 2004-09-05 23:28:22
|
On Mon, Sep 06, 2004 at 12:54:50AM +0200, Diego Torres wrote:
when using install-usb with syslinux, on these lines...
---snip snip snip---
if [ "$BOOTLOADER" = "syslinux" ]; then
mkdosfs $PARTITION > /dev/null || return 1
echo "Installing syslinux MBR"
SIZE=$(du -b $TMPDIR/iso-mnt/boot/syslinux/mbr.bin | cut -f 1 )
dd if=$TMPDIR/iso-mnt/boot/syslinux/mbr.bin of=$DEVICE count=$SIZE || return 1
echo installing SysLinux boot sector
$TMPDIR/iso-mnt/boot/syslinux/syslinux $PARTITION || return 1
--------------------
or just by executing the followin:
./syslinux /dev/scsi/host0/bus0/target0/lun0/part1
i get the same error:
sh: line 1: mcopy: command not found
which is suprising... could anyone try it?
--
-- gnupg keyfingerprint -- 48AF 5BF9 8F54 2966 64CC 2327 7CD0 DD91 B09D 5799
-- Use of a keyboard or mouse may be linked to serious injuries or disorders.
Diego Torres - dtorres at anthalia dot org - Madrid / España
|
|
From: Diego T. <dt...@co...> - 2004-09-05 23:49:32
|
On Mon, Sep 06, 2004 at 01:28:01AM +0200, Diego Torres wrote:
> sh: line 1: mcopy: command not found
> which is suprising... could anyone try it?
fixed by installing the mtools package.
next problem:
Installing syslinux MBR
0+1 registros leídos
0+1 registros escritos
304 bytes transferred in 0,025659 seconds (11848 bytes/sec)
installing SysLinux boot sector
copying files
cp: se omite el directorio `./tmp-install2usb/iso-mnt/boot/grub'
cp: se omite el directorio `./tmp-install2usb/iso-mnt/boot/syslinux'
cp: fallo al conservar el propietario de `./tmp-install2usb/disk-mnt/LICENSE': Operación no permitida
copying source file bootcd.iso to device mounted on ./tmp-install2usb/disk-mnt/bootcd.iso
Copying etc.tar.bz2 to ./tmp-install2usb/etc-mnt/etc.tar.bz2
syncing and unmounting (this could take a while)
#
this will cause a failure, because we are using cp -p when copying the
LICENSE file, and the file owners attribute can't be copied to a fat32
partition.
should i remove the "-p" from install-usb?
----install-usb-----
echo "copying files"
# Warnings about not copying subdirs cause spurious eixt here so ignore status...
cp -p $TMPDIR/iso-mnt/boot/* $TMPDIR/disk-mnt/ &> /dev/null # || return 1
cp -p $TMPDIR/iso-mnt/{DEVIL-LINUX,LICENSE} $TMPDIR/disk-mnt/ &> /dev/null || return 1
^^
cat $TMPDIR/iso-mnt/isolinux.cfg | sed -e s%"/boot/"%""% > $TMPDIR/disk-mnt/syslinux.cfg || return 1
cat $TMPDIR/iso-mnt/boot/message | sed -e s%"/boot/"%""% > $TMPDIR/disk-mnt/message || return 1
copy_iso_file $DLISO $TMPDIR/disk-mnt/bootcd.iso || return 1
--------------------
--
-- gnupg keyfingerprint -- 48AF 5BF9 8F54 2966 64CC 2327 7CD0 DD91 B09D 5799
-- Use of a keyboard or mouse may be linked to serious injuries or disorders.
Diego Torres - dtorres at anthalia dot org - Madrid / España
|
|
From: Heiko Z. <he...@zu...> - 2004-09-06 13:46:15
|
Diego Torres wrote:
>On Mon, Sep 06, 2004 at 01:28:01AM +0200, Diego Torres wrote:
>
>
>>sh: line 1: mcopy: command not found
>>which is suprising... could anyone try it?
>>
>>
>
>fixed by installing the mtools package.
>
>next problem:
>
>Installing syslinux MBR
>0+1 registros leídos
>0+1 registros escritos
>304 bytes transferred in 0,025659 seconds (11848 bytes/sec)
>installing SysLinux boot sector
>copying files
>cp: se omite el directorio `./tmp-install2usb/iso-mnt/boot/grub'
>cp: se omite el directorio `./tmp-install2usb/iso-mnt/boot/syslinux'
>cp: fallo al conservar el propietario de `./tmp-install2usb/disk-mnt/LICENSE': Operación no permitida
>copying source file bootcd.iso to device mounted on ./tmp-install2usb/disk-mnt/bootcd.iso
>
>Copying etc.tar.bz2 to ./tmp-install2usb/etc-mnt/etc.tar.bz2
>syncing and unmounting (this could take a while)
>#
>
>this will cause a failure, because we are using cp -p when copying the
>LICENSE file, and the file owners attribute can't be copied to a fat32
>partition.
>
>should i remove the "-p" from install-usb?
>
>----install-usb-----
>echo "copying files"
># Warnings about not copying subdirs cause spurious eixt here so ignore status...
>cp -p $TMPDIR/iso-mnt/boot/* $TMPDIR/disk-mnt/ &> /dev/null # || return 1
>cp -p $TMPDIR/iso-mnt/{DEVIL-LINUX,LICENSE} $TMPDIR/disk-mnt/ &> /dev/null || return 1
> ^^
>cat $TMPDIR/iso-mnt/isolinux.cfg | sed -e s%"/boot/"%""% > $TMPDIR/disk-mnt/syslinux.cfg || return 1
>cat $TMPDIR/iso-mnt/boot/message | sed -e s%"/boot/"%""% > $TMPDIR/disk-mnt/message || return 1
>copy_iso_file $DLISO $TMPDIR/disk-mnt/bootcd.iso || return 1
>--------------------
>
>
>
It would probably be a good idea, to make the script a little more
intelligent and use the -p only when it's not FAT.
Heiko
|
|
From: Heiko Z. <he...@zu...> - 2004-09-06 13:44:09
|
Diego Torres wrote: >i've been compiling the new 1.3.1 from cvs, and i've found a full new >interactive script to install the iso on the usb storage device. wow! :) > >so, couple of questions: > >if i configure an alternative partition to hold the configuration >scripts, what size should i choose? > > Something between 10 MB and 10 GB ? ;-) It needs to hold your etc.tar.bz2, so a couple of MB should be enough. >why are we supporting 3 boot methods? (syslinux, lilo & grub?) shouldn't >syslinux be enough? > > syslinux -> FAT lilo/grub -> EXT2/3 It's just sometimes you need to use a different bootloader for some reason, why basically provide you with that. >why there are two choices between the initrd fs? cramfs/ext2... >shouldn't we stay with cramfs? > > The 2.6 Kernel currently can't boot from a cramfs InitRD, that's the reason why we have ext2 in there. >maybe a little advice about the partition type on the configuration >partition could be a good thing... :) > > > ??? Heiko |
|
From: Diego T. <dt...@co...> - 2004-09-06 23:21:13
|
On Mon, Sep 06, 2004 at 09:45:33AM -0400, Heiko Zuerker wrote: > >maybe a little advice about the partition type on the configuration > >partition could be a good thing... :) > ??? i mean, do i use fat32 or ext2 for the configuration partition? now i'm using ext2, but this should be documented somewhere (with the syslinux/lilo/grub/partition size info) -- -- gnupg keyfingerprint -- 48AF 5BF9 8F54 2966 64CC 2327 7CD0 DD91 B09D 5799 -- Use of a keyboard or mouse may be linked to serious injuries or disorders. Diego Torres - dtorres at anthalia dot org - Madrid / España |
|
From: Heiko Z. <he...@zu...> - 2004-09-07 17:32:30
|
Diego Torres wrote: >On Mon, Sep 06, 2004 at 09:45:33AM -0400, Heiko Zuerker wrote: > > >>>maybe a little advice about the partition type on the configuration >>>partition could be a good thing... :) >>> >>> >>??? >> >> > >i mean, do i use fat32 or ext2 for the configuration partition? > >now i'm using ext2, but this should be documented somewhere (with the >syslinux/lilo/grub/partition size info) > > It actually doesn't matter what you use for your config partition, the mount command autodetects the format. Heiko |