OESF Portables Forum
General Forums => General Discussion => Topic started by: bam on July 26, 2006, 03:51:51 am
-
How can one extract the files from this? Tried mounting it as a cramfs or sqaushfs, no-joy. Any other ideas?
-
aybe anm
How can one extract the files from this? Tried mounting it as a cramfs or sqaushfs, no-joy. Any other ideas?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=136439\"][{POST_SNAPBACK}][/a][/div]
maybe something along the lines of an iso buster? is it maybe .bin as in cd image stuff?
-
hmmm dunno, its the cacko initrd.bin file.
-
Try jffs2 then - search the forum for "mount AND jffs2"
Si
-
oh yea that makes sense
-
Dear bam,
(using koen's way of saying it) lardman and adf is bullshit.
initrd.bin is similar to initrd.img used in normal linux boot.
It is a gzipped image. To mount it, first gunzip, plus
kernel have to have initrd support, then use this command
mount -t ext2 -o loop initrd /mnt
to mount it.
br,
felix.
-
tried to 'gunzip -d initrd.bin' = no-joy, any other ideas?
-
tried to 'gunzip -d initrd.bin' = no-joy, any other ideas?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=136563\"][{POST_SNAPBACK}][/a][/div]
mount it as a disk image? change the suffux to .img?
-
hmmm, didnt think of that....duh!
-
(using koen's way of saying it) lardman and adf is bullshit.
I wouldn't, you just appear to be rude (even more so as you're not actually right).
initrd.bin is similar to initrd.img used in normal linux boot.
It is a gzipped image. To mount it, first gunzip, plus
kernel have to have initrd support, then use this command
mount -t ext2 -o loop initrd /mnt
to mount it.
No initrd.bin I've ever seen for a Zaurus uses ext2, they are always compressed, which means a choice of ro cramfs or rw jffs2.
Assuming it's not cramfs, best to try jffs2.
Si
-
Assuming it's not cramfs, best to try jffs2.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=136583\"][{POST_SNAPBACK}][/a][/div]
The best way to check it is to use 'file', however:
angstrom@serenity:~/website/unstable/images/20060725/c7x0$ file *
Angstrom-bootstrap-image-test-20060725-c7x0.rootfs.ext2: Linux rev 0.0 ext2 filesystem data
Angstrom-bootstrap-image-test-20060725-c7x0.rootfs.img: data
Angstrom-bootstrap-image-test-20060725-c7x0.rootfs.tar.bz2: bzip2 compressed data, block size = 900k
modules-2.6.16-c7x0.tgz: gzip compressed data, from Unix, last modified: Tue Jul 25 14:29:58 2006
updater.sh.c7x0: data
zImage-2.6.16-c7x0-20060725122119.bin: data
note how it differs from:
angstrom@serenity:~/website/unstable/images/20060725/a780$ file *
Angstrom-bootstrap-image-test-20060725-a780.rootfs.jffs2: Linux jffs2 filesystem data little endian
Angstrom-bootstrap-image-test-20060725-a780.rootfs.tar.gz: gzip compressed data, from Unix, last modified: Tue Jul 25 13:51:54 2006
the zImage and roofts.img both have the sharp-sl header prepended, so file doesn't recognize them. That header could also explain why it won't mount/uncompress/etc
-
I have been able to mount jffs2 filesystems from pdaX certainly, and also the Sharp cramfs offerings.
Si