Yum won't install SDK

Does anybody has an idea why the nightly image cannot be
mounted using 
the loopback device?

This is the output of the terminal:

[teuslocalhost olpc]$ ls -l
total 493296
drwxrwxr-x  2 teus teus      4096 Jun 20 11:01 image
-rwxrwxr-x  1 teus teus        72 Jun 13 09:00 olpc
-rw-rw-r--  1 teus teus 504627200 Jun 20 16:51 
olpc-stream-development-7-20060609_1600-ext3.img
[teuslocalhost olpc]$ sudo mount -o loop,offset=32256 -t
ext3 
olpc-stream-development-7-20060609_1600-ext3.img
/home/teus/olpc/image
mount: wrong fs type, bad option, bad superblock on
/dev/loop1,
       missing codepage or other error
       In some cases useful info is found in syslog - try
       dmesg | tail  or so

Thanks,

Teus.

--
olpc-software mailing list
olpc-softwareredhat.com
https://www.redhat.com/mailman/listinfo/olpc-software

On Tue, Jun 20, 2006 at 05:23:38PM +0200, Teus Benschop
wrote:
> Does anybody has an idea why the nightly image cannot
be mounted using 
> the loopback device?
> 
> This is the output of the terminal:
> 
> [teuslocalhost olpc]$ ls -l
> total 493296
> drwxrwxr-x  2 teus teus      4096 Jun 20 11:01 image
> -rwxrwxr-x  1 teus teus        72 Jun 13 09:00 olpc
> -rw-rw-r--  1 teus teus 504627200 Jun 20 16:51 
> olpc-stream-development-7-20060609_1600-ext3.img
> [teuslocalhost olpc]$ sudo mount -o loop,offset=32256 -t
ext3 
> olpc-stream-development-7-20060609_1600-ext3.img
/home/teus/olpc/image
> mount: wrong fs type, bad option, bad superblock on
/dev/loop1,
>       missing codepage or other error
>       In some cases useful info is found in syslog -
try
>       dmesg | tail  or so

I think the offset you are passing is incorrect. According
to the tools
at http://hg.fedoraproject.org/hg/olpc/tools/image--devel
, the first
partition tbegins at $DISK_BYTES_PER_SECTOR  which is
defined to be 

  DISK_BYTES_PER_SECTOR=$[ $DISK_SECTOR_SIZE *
$DISK_SECTORS_PER_TRACK ]

Where 

  DISK_SECTOR_SIZE=512
  DISK_SECTORS_PER_TRACK=32

Which gives you an offset of 16384,  not 32256. 

Even then, this would give you the offset of the first
patition (/boot),
the main partiiton (/) is located further into the disk
image. I don';t
have the time to figure out the maths for the offset of /
just at the 
moment, but you can see the geometry information at

http://hg.fed
oraproject.org/hg/olpc/tools/image--devel?f=be0754b1c131;fil
e=conf/partition-ext3.conf

Regards,
Dan.
-- 
|=- Red Hat, Engineering, Emerging Technologies, Boston.  +1
978 392 2496 -=|
|=-           Perl modules: http://search.cpan.o
rg/~danberr/              -=|
|=-               Projects: http://freshmeat.net/
~danielpb/               -=|
|=-  GnuPG: 7D3B9505   F3C9 553F A1DA 4AC2 5648 23C1 B3DF
F742 7D3B 9505  -=| 

--
olpc-software mailing list
olpc-softwareredhat.com
https://www.redhat.com/mailman/listinfo/olpc-software

Teus Benschop wrote:
> Does anybody has an idea why the nightly image cannot
be mounted using
> the loopback device?

krsticaeryn:~/olpc-sdk> fdisk -lu
olpc-2006_05_23_15_11-ext3.img
[...]
Disk olpc-2006_05_23_15_11-ext3.img: 0 MB, 0 bytes
16 heads, 32 sectors/track, 0 cylinders, total 0 sectors
Units = sectors of 1 * 512 = 512 bytes

                         Device Boot      Start         End 
    Blocks
  Id  System
olpc-2006_05_23_15_11-ext3.img1   *          32       20479 
     10224
  83  Linux
olpc-2006_05_23_15_11-ext3.img2           20480      839679 
    409600
  83  Linux
[...]

Now look at the start number for the second partition down,
and multiply
by 512 bytes; with this image, you'll get 512*20480 =
10485760.

rootaeryn:~/olpc-sdk# losetup /dev/loop0 -o 10485760
olpc-2006_05_23_15_11-ext3.img
rootaeryn:~/olpc-sdk# mount /dev/loop0 /mnt/olpc
rootaeryn:~/olpc-sdk# ls /mnt/olpc
bin   dev  home  lost+found  mnt  proc  sbin     srv  tmp 
var
boot  etc  lib   media       opt  root  selinux  sys  usr

Cheers,

-- 
Ivan Krstic <krsticfas.harvard.edu> | GPG: 0x147C722D

--
olpc-software mailing list
olpc-softwareredhat.com
https://www.redhat.com/mailman/listinfo/olpc-software

Teus Benschop wrote:
> Does anybody has an idea why the nightly image cannot
be mounted using
> the loopback device?
> 
> This is the output of the terminal:
> 
> [teuslocalhost olpc]$ ls -l
> total 493296
> drwxrwxr-x  2 teus teus      4096 Jun 20 11:01 image
> -rwxrwxr-x  1 teus teus        72 Jun 13 09:00 olpc
> -rw-rw-r--  1 teus teus 504627200 Jun 20 16:51
> olpc-stream-development-7-20060609_1600-ext3.img
> [teuslocalhost olpc]$ sudo mount -o loop,offset=32256 -t
ext3
> olpc-stream-development-7-20060609_1600-ext3.img
/home/teus/olpc/image
> mount: wrong fs type, bad option, bad superblock on
/dev/loop1,
>       missing codepage or other error
>       In some cases useful info is found in syslog -
try
>       dmesg | tail  or so

Are you sure the offset is correct?
I've a simple script to automatically mount images like
that:
http://ww
w.pixelbeat.org/scripts/lomount.sh

Pádraig.

--
olpc-software mailing list
olpc-softwareredhat.com
https://www.redhat.com/mailman/listinfo/olpc-software

Thank you, Daniel and Ivan, the information and examples you
gave solved
the problem. Teus.

--
olpc-software mailing list
olpc-softwareredhat.com
https://www.redhat.com/mailman/listinfo/olpc-software

Does anybody know how to start an X program within the OLPC
simulator?

I mounted the image, went to /home/olpc and found .xinitrc,
but any 
programs called there do not seem to start on boot.

Any help is appreciated.

Teus.

--
olpc-software mailing list
olpc-softwareredhat.com
https://www.redhat.com/mailman/listinfo/olpc-software