Thanks for your reply
I've found that the file system keeps read-only because the system.img
is inside another image file named system.sfs which is the types of
squashfs.
Squashfs is a compressed read-only filesystem for Linux, and Android-
x86 will use it to compress the system.image by default.
After adding the USE_SQUASHFS=0 making option, the file system now is
rw.
ref:
http://cwhuang.info/2009/07/add-squashfs-to-android-x86#more-263
On 9月17日, 下午10時34分, 홍야 <
redyar...@gmail.com> wrote:
> "system.img" use ext2 file Image. Sometime to change contents in system.img,
> I used to try below command:
> # mount -t ext2 -o loop ./system.img ./test_folder
>
> 2010/9/17 HCfon <
fon0...@gmail.com>
>
>
>
> > Hi, everyone
>
> > I'm working with eclair-x86 and I want to make some WiFi usb doungle
> > working.
> > I need to alter the driver/libharware_legacy code frequently. For
> > compiling single
> > module, the time is acceptable. But for the time to dump usb image to
> > my usb
> > disk is quite long. I think if the system folder can mount wirtable so
> > I can just
> > copy my new module into the system folder without wating for dumping
> > the usb
> > image?
>
> > I've tried alter the origional content of init script:
> > mount -o loop /sfs/system.img system
> > to:
> > mount -o rw,loop /sfs/system.img system
>
> > but it's not working. I'm not familliar with mounting, so can anyone
> > give me some
> > hints to work around this? Thanks.
>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Android-x86" group.
> > To post to this group, send email to
andro...@googlegroups.com.
> > To unsubscribe from this group, send email to
> >
android-x86...@googlegroups.com<android-x86%2Bunsubscribe@googlegr
oups.com>
> > .
> > For more options, visit this group at
> >
http://groups.google.com/group/android-x86?hl=en.- 隱藏被引用文字 -
>
> - 顯示被引用文字 -