Quote:
Originally Posted by NiLuJe
@knc1: For future ref:
Code:
/dev/root 340.2M 229.2M 93.9M 71% /
tmpfs 125.1M 60.0K 125.0M 0% /dev
tmpfs 125.1M 0 125.1M 0% /dev/shm
tmpfs 190.0M 300.0K 189.7M 0% /var
/dev/loop/2 216.0K 216.0K 0 100% /lib/firmware/cyttsp
/dev/loop/3 2.5M 2.5M 0 100% /usr/share/X11/xkb
/dev/loop/4 72.9M 72.9M 0 100% /usr/java/lib/fonts
/dev/loop/5 1.3M 1.3M 0 100% /etc/kdb.src
/dev/loop/6 7.9M 7.9M 0 100% /usr/lib/locale
/dev/loop/7 7.7M 7.7M 0 100% /usr/share/keyboard
/dev/mmcblk0p3 62.0M 17.7M 41.1M 30% /var/local
fsp 1.4G 49.2M 1.3G 4% /mnt/us
/dev/loop/0 1.4G 49.2M 1.3G 4% /mnt/base-us
Code:
rootfs / rootfs rw 0 0
/dev/root / ext3 rw,noatime,nodiratime,data=writeback 0 0
none /proc proc rw,nosuid,nodev,noexec,relatime 0 0
none /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
tmpfs /dev/shm tmpfs rw,relatime 0 0
devpts /dev/pts devpts rw,relatime,gid=5,mode=620 0 0
tmpfs /var tmpfs rw,relatime,size=194560k 0 0
/dev/loop/2 /lib/firmware/cyttsp cramfs ro,noatime,nodiratime 0 0
/dev/loop/3 /usr/share/X11/xkb cramfs ro,noatime,nodiratime 0 0
/dev/loop/4 /usr/java/lib/fonts cramfs ro,noatime,nodiratime 0 0
/dev/loop/5 /etc/kdb.src cramfs ro,noatime,nodiratime 0 0
/dev/loop/6 /usr/lib/locale cramfs ro,noatime,nodiratime 0 0
/dev/loop/7 /usr/share/keyboard cramfs ro,noatime,nodiratime 0 0
/dev/mmcblk0p3 /var/local ext3 rw,relatime,errors=continue,data=writeback 0 0
fsp /mnt/us fuse.fsp rw,nosuid,nodev,noatime,user_id=0,group_id=0 0 0
/dev/loop/0 /mnt/base-us vfat rw,noexec,noatime,nodiratime,fmask=0022,dmask=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
(That's during the update process, hence the rw rootfs).
... Which reminds me: Yup, the KDB DB is in a loop mounted cramfs on the PW, so, yeah, use kdb set. [You'll probably have to remount said cramfs rw, though]. |
The cramFS file system does not have a "write mode";
sorry about that.
Whatever "kdb set" is, it must be doing its thing to a ram copy of the fs.
Guess we will have to write up a HowTo on reading and re-building replacement cramFS systems.
It is relatively easy on *nix but I understand that the Windows tools sort of suck.
Note also (HEY - twobob): the vfat partition is now mounted "noexec".
Just another challenge there at out smarting lab126.