Quote:
Originally Posted by natemcnutty
I was thinking about this and wanted to make sure it didn't get lost in the sea of posts. I added /bin back to the sysinit.rc and stopped it from remounting /system as read-only, and data now works on first boot. It also fixed root because it now has busybox and read-write access to /system.
I know we wanted to get rid of /bin from sysinit.rc, so I'm trying to see if I can symlink /system/bin /bin during sysinit.rc and fix anything that is missing from /system/bin that is in /bin (for rootfs or initramfs).
|
Next version we have busybox integrate?
Quote:
Originally Posted by Starfox
Just as a general comment, having more than one primary FAT partition on any media leads to bad things(tm). DOS was never really designed to have multiple primary FAT, and that limitation is inherited even to this day.
Partition tables are very finicky, and do not necessarily follow how it is laid out on disk. In fact, unless you create all the partition in a single shot from a blank disk, how you think is the nth partition will not be how the entry on disk is.
That and most automount scripts do not look for more than one partition. Unless there is a good reason why you need two FAT32 on your card, you are running a very unsupported config.
-- Starfox
|
neopeek version need two partition(1st FAT32, 2nd ext3), xdandroid install guide told us format 1st partition before install, so I create 3st partition to store some apps,books,musics... then mount it to /sdcard/sdcard2, so ,after I re-install, I need't to copy apps,books,musics to SD-card again