Re: [Dextrose] Problem with olpc-os-builder: ZD image of 20 MB
On Thu, Oct 14, 2010 at 7:07 PM, James Cameron wrote: > On Wed, Oct 13, 2010 at 10:32:26PM +0200, Bernie Innocenti wrote: >> Note that there's a real limit to observe: the old DOS 8+3 naming >> scheme. Otherwise, the OFW will display a mangled name. > > OpenFirmware will still fs-update or copy-nand from a mangled name if it > is typed correctly. Yeah, workable for developers but I don't think our signing machinery can do the right thing to produce an fs.zip for long names. (Who could predict what your long filename will mangle to?) So no four-finger-salute to upgrade in the field (or anywhere with secure machines) will work. In fact, our signing scripts should complain loudly about anything that isn't 8.3 as it'll only lead to tears and loathing. m -- martin.langh...@gmail.com mar...@laptop.org -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Dextrose] Problem with olpc-os-builder: ZD image of 20 MB
On Wed, Oct 13, 2010 at 10:32:26PM +0200, Bernie Innocenti wrote: > Note that there's a real limit to observe: the old DOS 8+3 naming > scheme. Otherwise, the OFW will display a mangled name. OpenFirmware will still fs-update or copy-nand from a mangled name if it is typed correctly. If you really need longer file names, use a filesystem that supports them correctly. Current versions of OpenFirmware appear to work fine with ext2. I'm able to fs-update from ext2 on 4 GB or 160 GB drives. But if you suspect any of the laptops are on older firmware, it is best to stick to FAT. -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Dextrose] Problem with olpc-os-builder: ZD image of 20 MB
On Wed, 2010-10-13 at 13:56 -0200, Daniel Castelo wrote: > With this configuration: > > [buildnr_from_file] > suffix=uy > path=uy-buildnr-0.88-1.5 > > When the version number has three digits the process fail. Seems like > the image name couldn't have more than nine characters. > For example with the image name: os100uy.zd the process > Its very strange, because I know that many dextrose builds have long > names. Yes, it's strange. Versions with 3 digits and 2 or 3 letters of suffix always worked well for me! Perhaps there are some invisible blanks in the .ini or in the buildnr file? Note that there's a real limit to observe: the old DOS 8+3 naming scheme. Otherwise, the OFW will display a mangled name. -- // Bernie Innocenti - http://codewiz.org/ \X/ Sugar Labs - http://sugarlabs.org/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Dextrose] Problem with olpc-os-builder: ZD image of 20 MB
With this configuration:
[buildnr_from_file]
suffix=uy
path=uy-buildnr-0.88-1.5
When the version number has three digits the process fail. Seems like the
image name couldn't have more than nine characters.
For example with the image name: os100uy.zd the process fail.
Its very strange, because I know that many dextrose builds have long names.
If i change
On Wed, Oct 6, 2010 at 11:24 AM, Bernie Innocenti wrote:
> On Wed, 2010-10-06 at 09:42 -0200, Daniel Castelo wrote:
> > Hi! We could generate XO 1.5 images (dextrose images) with olpc os
> > builder, but sometimes we get a strange behaviour: at the end of the
> > process olpc os builder give us this error message:
> >
> > /home/latu/olpc-os-builder-1.1.0.dextrose.uy_4Oct/modules/sd_card_image/
> image.50.makefs.sh: line 54: * 512: syntax error: operand expected (error
> token is "* 512")
> >
> > and the size of the ZD image generated is just 20 MB.
> >
> > Have you ever seen this behaviour?
>
> I've never seen it myself. Here's the relevant code:
>
> 48 local img_sectors=$(sfdisk -uS -l $img | grep img2 | awk '{print $4}')
> 49 echo "(1 losetup error is normal here)"
> 50 losetup -d /dev/loop6 || :
> 51 losetup -o $((8192 * $BLOCK_SIZE)) --sizelimit $((131072 *
> $BLOCK_SIZE)) /dev/loop6 $img
> 52 echo "(1 losetup error is normal here)"
> 53 losetup -d /dev/loop7 || :
> 54 losetup -o $(((8192 + 131072) * $BLOCK_SIZE)) --sizelimit
> $(($img_sectors * $BLOCK_SIZE)) /dev/loop7 $img
>
> The error probably occurs because $img_sectors is uninitialized. Try
> adding some debug stamennts just after line 48. For example:
>
> echo '*** BEGIN DEBUG ***'
> sfdisk -uS -l $img
> echo '---'
> sfdisk -uS -l $img | grep img2
> echo '---'
> sfdisk -uS -l $img | grep img2 | awk '{print $4}'
> echo '*** END DEBUG ***'
>
> --
> // Bernie Innocenti - http://codewiz.org/
> \X/ Sugar Labs - http://sugarlabs.org/
>
>
--
Ing. Daniel Castelo
Plan Ceibal - Área Técnica
Avda. Italia 6201
Montevideo - Uruguay.
Tel.: 2 601 57 73 Interno 2228
E-mail : dcast...@plan.ceibal.edu.uy
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
Re: [Dextrose] Problem with olpc-os-builder: ZD image of 20 MB
On Wed, 2010-10-06 at 09:42 -0200, Daniel Castelo wrote:
> Hi! We could generate XO 1.5 images (dextrose images) with olpc os
> builder, but sometimes we get a strange behaviour: at the end of the
> process olpc os builder give us this error message:
>
> /home/latu/olpc-os-builder-1.1.0.dextrose.uy_4Oct/modules/sd_card_image/image.50.makefs.sh:
> line 54: * 512: syntax error: operand expected (error token is "* 512")
>
> and the size of the ZD image generated is just 20 MB.
>
> Have you ever seen this behaviour?
I've never seen it myself. Here's the relevant code:
48 local img_sectors=$(sfdisk -uS -l $img | grep img2 | awk '{print $4}')
49 echo "(1 losetup error is normal here)"
50 losetup -d /dev/loop6 || :
51 losetup -o $((8192 * $BLOCK_SIZE)) --sizelimit $((131072 * $BLOCK_SIZE))
/dev/loop6 $img
52 echo "(1 losetup error is normal here)"
53 losetup -d /dev/loop7 || :
54 losetup -o $(((8192 + 131072) * $BLOCK_SIZE)) --sizelimit $(($img_sectors
* $BLOCK_SIZE)) /dev/loop7 $img
The error probably occurs because $img_sectors is uninitialized. Try
adding some debug stamennts just after line 48. For example:
echo '*** BEGIN DEBUG ***'
sfdisk -uS -l $img
echo '---'
sfdisk -uS -l $img | grep img2
echo '---'
sfdisk -uS -l $img | grep img2 | awk '{print $4}'
echo '*** END DEBUG ***'
--
// Bernie Innocenti - http://codewiz.org/
\X/ Sugar Labs - http://sugarlabs.org/
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
