Where Can I get Memory Image context?

明明ml30j53.img的檔案系統就是minix~~~
...
mitelinux:/# cat /proc/mounts
rootfs / rootfs rw 0 0
/dev/root / minix ro 0 0
none /proc proc rw 0 0
none /dev/pts devpts rw 0 0
/dev/ram /mnt/ram minix rw 0 0
mitelinux:/# cat /etc/fstab
/dev/hda1 / minix defaults 1 1
none /proc proc defaults 0 0
none /dev/pts devpts gid=5,mode=620 0 0
mitelinux:/# df -h
Filesystem Size Used Available Use% Mounted on
/dev/hda1 30.2M 10.8M 19.3M 36% //dev/ram 502.0k 40.0k 462.0k 8% /mnt/ram

但我怎麼mount就是沒辦法~~~
Where Can I get Memory Image context?
#mount -t minix ml30j53.img rootfs/ -o loop
功力還不夠啊~~~誰能幫幫我~~思考中~~

[更新]
錯錯不是minix，我還在研究到底是什麼??
csl@csl-desktop:~$ file ml30j53.img
ml30j53.img: x86 boot sector, LInux i386 boot LOader; partition 1: ID=0x83, starthead 1, startsector 63, 62433 sectors, extended partition table (last)\011
看起來像是在Memory Image中的大合體??好像是把所有東西放在一起??
但要放在一起，難道Memory Image沒有filesystem嗎?
...
原來
csl@csl-desktop:~$ qemu-img info ml30j53.img
image: ml30j53.img
file format: raw
virtual size: 31M (32047104 bytes)
disk size: 31M
它是一個raw file format，
/*
raw
Raw disk image format (default). This format has the advantage of being simple and easily exportable to all other emulators. If your file system supports holes (for example in ext2 or ext3 on Linux or NTFS on Windows), then only the written sectors will reserve space. Use qemu-img info to know the real size used by the image or ls -ls on Unix/Linux.
*/
難怪怎麼mount都沒辦法...
還要再努力才行啊~~~
[/更新]