View Single Post
Old 02-19-2016, 06:52 PM   #3
knc1
Going Viral
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
Quote:
Originally Posted by XXCoder View Post
t1_timeout seem to contain that setting, but I don't see how to alter it, even when I use mntroot rw. Oddly there seem to be few copies so I'm uncertain how to change.

One suggests this command (it's for k5 not pw2 so paths is wrong)
sed -e 's/600/900/' /etc/kdb.src/luigi/system/daemon/powerd/t1_timeout.bkp > /etc/kdb.src/luigi/system/daemon/powerd/t1_timeout

but it did not work either. I could not make backup file (with BKP ext) first as it says read only.
There seems to be two details that you are overlooking -

That: mntroot ro/rw command **only** effects the filesystem mounted at: '/' (root of the system tree) -
The rw or ro status does not propagate to other filesystems mounted in the system tree.

In addition to a file system mount to be marked ro/rw - it is possible that the file system is inherently read-only (I.E: Does not support write operations).

For example:
Code:
[root@kindle root]# mount
rootfs on / type rootfs (rw)
/dev/root on / type ext3 (ro,noatime,nodiratime,barrier=0,data=writeback)
none on /proc type proc (rw,nosuid,nodev,noexec,relatime)
none on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
tmpfs on /dev/shm type tmpfs (rw,relatime)
devpts on /dev/pts type devpts (rw,relatime,gid=5,mode=620)
tmpfs on /var type tmpfs (rw,relatime,size=32768k)
/dev/loop/2 on /usr/share/X11/xkb type cramfs (ro,noatime,nodiratime)
/dev/loop/3 on /usr/java/lib/fonts type cramfs (ro,noatime,nodiratime)
/dev/loop/4 on /etc/kdb.src type cramfs (ro,noatime,nodiratime)
/dev/loop/5 on /usr/lib/locale type cramfs (ro,noatime,nodiratime)
/dev/loop/6 on /usr/share/keyboard type cramfs (ro,noatime,nodiratime)
/dev/mmcblk0p3 on /var/local type ext3 (rw,relatime,errors=continue,barrier=0,data=writeback)
fsp on /mnt/us type fuse.fsp (rw,nosuid,nodev,noatime,user_id=0,group_id=0,allow_other)
/dev/loop/0 on /mnt/base-us type vfat (rw,noexec,noatime,nodiratime,fmask=0000,dmask=0000,all)
ext2 on /var/local/swpmnt type ramfs (rw,relatime,size=3M)
Note the type of filesystem behind /dev/loop/4 -
It is cramfs -
cramfs is a read-only filesystem, it does not have a 'write' function.
cramfs can only be 'created' or 'read'.
knc1 is offline   Reply With Quote