Hey
I have a init.rc modded so I can have ext2 in my boot.img
But it is not working...
http://pastebin.com/TxixgL3C
line 89 was this:
mount rfs /dev/stl13 /data nosuid nodev check=no
but should become:
mount ext2 /dev/stl13 /data noatime nodiratime nosuid nodev check=no || mount rfs /dev/stl13 /data nosuid nodev check=no
But somehow it is not working and I believe Android takes it for rfs...
If i just replace it with:
mount ext2 /dev/stl13 /data noatime nodiratime nosuid nodev check=no
Everything works fine...
What's wrong?
Hmmm anyone please?
Related
From a telnet session
# cat /proc/filesystems
nodev sysfs
nodev rootfs
nodev bdev
nodev proc
nodev debugfs
nodev sockfs
nodev pipefs
nodev anon_inodefs
nodev futexfs
nodev tmpfs
nodev inotifyfs
nodev devpts
cramfs
nodev ramfs
vfat
yaffs
yaffs2
Click to expand...
Click to collapse
# cd bin
# ls
start
ioctl
smd
insmod
sleep
iftop
setprop
ifconfig
setconsole
id
sendevent
hd
schedtop
getprop
route
getevent
rmmod
dmesg
rmdir
df
rm
wpa_supplicant
wpa_cli
dd
wlan_loader
toolbox
telnetd
system_server
svc
surfaceflinger
renice
su
ssltest
sh
servicemanager
date
service
sdutil
sdptool
rild
radiooptions
qemud
reboot
pm
playmp3
ping
netcfg
cmp
mountd
monkey
mediaserver
logwrapper
logcat
linker
ps
itr
installd
input
htclogkernel
chmod
hostapd_cli
hostapd
hcid
hciattach
flash_image
fillup
printenv
dvz
dumpsys
dumpstate
dhcpcd
cat
dexopt
debuggerd
debug_tool
dbus-daemon
dalvikvm
app_process
notify
am
akmd
dumpcrash
netstat
mv
mount
wipe
mkdosfs
watchprops
mkdir
vmstat
lsmod
umount
ls
top
log
sync
ln
stop
kill
Click to expand...
Click to collapse
So from my understanding I can only mount sdcards with fat32, fat16, fat12 or yaffs2. Only formatting of fat is supported as well. cramfs doesn't seem that interesting as it is read-only. yaffs2 is made for NAND and I don't know how similar it is to SD-cards. I formatted my card with ext3 before I saw this info and it didn't work. I'm using fat32 for now, but as a (almost) linux purist and the limitations of file size and names I'm interested in using something else.
The Kaiser, Vogue and Freerunner can use both ext2 and ext3 because of a custom kernel. Is that the only way?
There was someone in #android on Freenode that got a 4 GB partition in ext2 to work.
[email protected]:~/logs$ cat freenode_#android.log | grep "ext2"
[Mon Dec 1 2008] [00:11:55] <sparkle> i just cheat and have a 4gb ext2 partition, but that's not really an option for any app you want to ship to the masses
Click to expand...
Click to collapse
Try asking him.
(S)he has loaded the ext2 module. This can be done with root access, but all those without are out of luck (for now anyways )
HTC Magic G2
1, Used other Rom before
2, Current recovery is cm-1.4
3, SPL is the original SHIPMENT SPL HBOOT-1.33.0009H
Use cm-1.4 for 32A to Wipe,and apply any zip from sd to flash the Cyanogen_4.0.1-32a, but apps2sd cannot be automatically enabled,also autoswap
As we all know what would be the problem? SPL? Recovery? SD card partition? Currently used in the second partition is EXT3.
busybox df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 96.3M 12.0k 96.3M 0% /dev
tmpfs 4.0M 0 4.0M 0% /sqlite_stmt_journals
/dev/block/mtdblock3 90.0M 62.0M 28.0M 69% /system
/dev/block/mtdblock5 295.8M 27.4M 268.4M 9% /data
/dev/block/mtdblock4 80.0M 1.3M 78.7M 2% /cache
/dev/block//vold/179:1
6.9G 4.6G 2.3G 67% /sdcard
after #mount -a
# mount
mount
rootfs on / type rootfs (ro)
tmpfs on /dev type tmpfs (rw,mode=755)
devpts on /dev/pts type devpts (rw,mode=600)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
tmpfs on /sqlite_stmt_journals type tmpfs (rw,size=4096k)
/dev/block/mtdblock3 on /system type yaffs2 (ro)
/dev/block/mtdblock5 on /data type yaffs2 (rw,nodev)
/dev/block/mtdblock4 on /cache type yaffs2 (rw,nosuid,nodev)
/dev/block//vold/179:1 on /sdcard type vfat (rw,dirsync,nosuid,nodev,noexec,uid=
1000,gid=1000,fmask=0711,dmask=0700,allow_utime=0022,codepage=cp437,iocharset=is
o8859-1,shortname=mixed,utf8)
/dev/block/mmcblk0p2 on /system/sd type ext3 (rw,errors=continue,data=ordered)
I just got an android tablet for Christmas running 2.1 and the battery life is being chewed away, so I was going to remove the phone services suggested in here
http://www.smartqmid.com/phpBB3/viewtopic.php?f=17&t=1691&start=0
I have rooted my device and logged in to terminal using 'su'
However, all the files are read-only
I have tried the following commands.
chmod 777 /system (just comes back "read-only file system)
chmod 777 /system/app/Phone.apk (just comes back "read-only file system)
mount -o rw,remount /dev/block/mtdblock3 (the mount commands just kick me back asking me to retype in the command)
mount -o remount,rw /system (the mount commands just kick me back asking me to retype in the command)
mount -o rw,remount /system (the mount commands just kick me back asking me to retype in the command)
Here is my currently mounted directories
rootfs / rootfs rw 0 0
tmpfs /dev tmpfs rw,relatime,mode 755 0 0
devpts /dev/pts devpts rw,relatim,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
tmpfs /sqlite_stmt_journals tmpfs rw, relatime,size 4096k 0 0
/dev/block/mtdblock3 /system yaffs2 ro, relatime 0 0
/dev/block/mtdblock4 /data yaffs2 ro, relatime 0 0
/dev/block/mtdblock5 /cache yaffs2 ro, relatime 0 0
/dev/block/mtdblock6 /local yaffs2 ro, relatime 0 0
usage for the command mount looks like this
mount [-r] [-w] [-o options] [-t type] device directory
Eh, I think I got it
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
Can someone post the nexus 5 mount points?
xda6969 said:
Can someone post the nexus 5 mount points?
Click to expand...
Click to collapse
Code:
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,barrier=1 wait
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 noatime,nosuid,nodev,barrier=1,data=ordered,nomblk_io_submit,noauto_da_alloc,errors=panic wait,check,encryptable=/dev/block/platform/msm_sdcc.1/by-name/metadata
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 noatime,nosuid,nodev,barrier=1,data=ordered,nomblk_io_submit,noauto_da_alloc,errors=panic wait,check
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 nosuid,nodev,barrier=1,data=ordered,nodelalloc,nomblk_io_submit,errors=panic wait
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware vfat ro,shortname=lower,uid=1000,gid=1000,dmask=227,fmask=337 wait
/dev/block/platform/msm_sdcc.1/by-name/boot /boot emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/recovery /recovery emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/misc /misc emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/modem /radio emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/sbl1 /sbl1 emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/tz /tz emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/rpm /rpm emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/sdi /sdi emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/aboot /aboot emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/imgdata /imgdata emmc defaults defaults
Thank you.
Is it ok to use mmcblk in src links when building cyanogenmod?
I forgot to change them and its bulding for a few hours now. Should I stop it?
My fstab looks like this:
Code:
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
/dev/block/mmcblk0p24 /system ext4 ro,errors=panic wait
/dev/block/mmcblk0p27 /data ext4 nosuid,nodev,noatime,noauto_da_alloc,discard,journal_async_commit,errors=panic wait,check,encryptable=footer,length=-16384
/dev/block/mmcblk0p25 /cache ext4 noatime,nosuid,nodev,barrier=1,noauto_da_alloc wait,check
/dev/block/mmcblk0p13 /efs ext4 noatime,nosuid,nodev,noauto_da_alloc,journal_async_commit,errors=panic wait
/dev/block/mmcblk0p22 /persist ext4 nosuid,nodev,data=ordered,nodelalloc wait
/dev/block/mmcblk0p1 /firmware emmc ro,shortname=lower,uid=1000,gid=1000,dmask=227,fmask=337,context=u:object_r:firmware_file:s0 wait
/dev/block/mmcblk0p2 /firmware-modem emmc ro,shortname=lower,uid=1000,gid=1000,dmask=227,fmask=337,context=u:object_r:firmware_file:s0 wait
/dev/block/mmcblk0p16 /boot emmc defaults defaults
/dev/block/mmcblk0p17 /recovery emmc defaults defaults
/dev/block/mmcblk0p26 /preload ext4 defaults defaults
# VOLD
/devices/soc.0/7864900.sdhci/mmc_host/mmc* auto vfat default voldmanaged=extSdCard:auto,noemulatedsd
/devices/platform/msm_hsusb_host/usb*sda auto vfat default voldmanaged=UsbDriveA:auto
/devices/platform/msm_hsusb_host/usb*sdb auto vfat default voldmanaged=UsbDriveB:auto
/devices/platform/msm_hsusb_host/usb*sdc auto vfat default voldmanaged=UsbDriveC:auto
/devices/platform/msm_hsusb_host/usb*sdd auto vfat default voldmanaged=UsbDriveD:auto
/devices/platform/msm_hsusb_host/usb*sde auto vfat default voldmanaged=UsbDriveE:auto
/devices/platform/msm_hsusb_host/usb*sdf auto vfat default voldmanaged=UsbDriveF:auto
Hi,
Try reading and posting your question here:
http://forum.xda-developers.com/showthread.php?t=667298
The experts there may be able to help.
Good luck!