galculator 2.1.2 (Kindle ver)

[nasser]

was able to make it work by running the mkdir and cp commands by hand in kterm..
those 3 tiny buttons now have unclipped characters..

but something weird happening..

i had earlier followed some post here to change home from /tmp/root to /home/root

now running

echo $HOME

or

echo ~

still gives

/tmp/root

as the output..

but.. doing a

mntroot ro

or a

mntroot rw

is not affecting /tmp/root.. it's affecting /home/root..

so.. i did:

1. mntroot rw

2. mkdir -p /home/root/.config/galculator

3. cp /mnt/us/extensions/galculator/.config/galculator/galculator.conf /home/root/.config/galculator/galculator.conf

which works.. but should i leave root fs in rw mode..

would like our experts' explanation for above behaviour..

[ixtab]

Originally Posted by nasser

was able to make it work by running the mkdir and cp commands by hand in kterm..
those 3 tiny buttons now have unclipped characters..

but something weird happening..

i had earlier followed some post here to change home from /tmp/root to /home/root

now running

echo $HOME

or

echo ~

still gives

/tmp/root

as the output..

but.. doing a

mntroot ro

or a

mntroot rw

is not affecting /tmp/root.. it's affecting /home/root..

so.. i did:

1. mntroot rw

2. mkdir -p /home/root/.config/galculator

3. cp /mnt/us/extensions/galculator/.config/galculator/galculator.conf /home/root/.config/galculator/galculator.conf

which works.. but should i leave root fs in rw mode..

would like our experts' explanation for above behaviour..

[root@kindle root]# ls -la / | grep tmp
lrwxrwxrwx    1 root     root             8 Jan  2  1970 tmp -> /var/tmp
[root@kindle root]# mount
rootfs on / type rootfs (rw)
/dev/root on / type ext3 (ro,noatime,nodiratime,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 /lib/firmware/cyttsp type cramfs (ro,noatime,nodiratime)
/dev/loop/3 on /usr/share/X11/xkb type cramfs (ro,noatime,nodiratime)
/dev/loop/4 on /usr/java/lib/fonts type cramfs (ro,noatime,nodiratime)
/dev/loop/5 on /etc/kdb.src type cramfs (ro,noatime,nodiratime)
/dev/loop/6 on /usr/lib/locale type cramfs (ro,noatime,nodiratime)
/dev/loop/7 on /usr/share/keyboard type cramfs (ro,noatime,nodiratime)
/dev/mmcblk0p3 on /var/local type ext3 (rw,relatime,errors=continue,data=writeback)
/dev/loop/0 on /mnt/base-us type vfat (rw,noexec,noatime,nodiratime,fmask=0022,dmask=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
fsp on /mnt/us type fuse.fsp (rw,nosuid,nodev,noatime,user_id=0,group_id=0)

The answer to all your questions lies above, namely in what is mounted where. /tmp is just a symlink to /var/tmp, and /var is a tmpfs, so it will disappear after shutdown.

/home would be on the root partition, and thus read-only in normal use. And yes, I agree that it's a bad idea to leave root mounted rw for normal use.

You have two options here: use a home directory on the USB partition (/mnt/us), or in /var/local. The advantage of the former is that you can edit files via USB, the advantage of the latter is that it's a real filesystem, not FAT32. I suggest to go for /var/local/home/root, or /var/local/root, or whatever you please.

[baf]

@nasser

To have galculator config in /mnt/us/extensions/galculator/galculator.conf change galculator/usr/bin/run.sh to:

#!/bin/sh
GALCULATOR_CONFIG=/mnt/us/extensions/galculator/galculator.conf \
GTK_IM_MODULE=kindle \
GTK2_RC_FILES=/mnt/us/extensions/galculator/pixmaps/gtkrc \
/mnt/us/extensions/galculator/usr/bin/galculator

[baf]

By the way, I think it looks better in landscape on KT

[nasser]

well.. baf seems to have found a simple solution..
but thanks to ixtab for explaining..
i need to fix my home location..
need to read and understand in detail..
am still puzzled by why echo $HOME and cp to ~ still recognise /tmp/root as home.. whereas mntroot and galculator itself consider /home/root..

[twobob]

@baf Excellent point. I forgot about that lol.

Yeah, I'm not sure why the HOME isn't being honoured either.

EDIT: Updated top post

[baf]

One more thing:
This path in your run.sh is wrong:

GTK2_RC_FILES=/mnt/us/extensions/galculator/pixmaps/gtkrc

should be:

/mnt/us/extensions/galculator/usr/share/pixmaps/gtkrc

[baf]

Very nice calculator by the way.
Thanks twobob!

[baf]

Originally Posted by twobob

Yeah, I'm not sure why the HOME isn't being honoured either.

Galculator uses g_get_home_dir() to get user's home dir and this function takes it from passwd file rather than from env variable.

[ixtab]

Originally Posted by baf

Galculator uses g_get_home_dir() to get user's home dir and this function takes it from passwd file rather than from env variable.

Originally Posted by nasser

am still puzzled by why echo $HOME and cp to ~ still recognise /tmp/root as home.. whereas mntroot and galculator itself consider /home/root..

As baf said. Your current shell instance still uses the old values. Logging out and back in should fix that.

[twobob]

Originally Posted by baf

One more thing:
This path in your run.sh is wrong:

GTK2_RC_FILES=/mnt/us/extensions/galculator/pixmaps/gtkrc

should be:

/mnt/us/extensions/galculator/usr/share/pixmaps/gtkrc

Originally Posted by baf

Galculator uses g_get_home_dir() to get user's home dir and this function takes it from passwd file rather than from env variable.

Double thanks
I have learned something...

Will fix.

EDIT: Done.

[nasser]

Originally Posted by baf

By the way, I think it looks better in landscape on KT

looks great..
how to enable landscape mode..? on..PW?

[nasser]

Originally Posted by ixtab

As baf said. Your current shell instance still uses the old values. Logging out and back in should fix that.

i've done a restart more than once after doing the home location fiddle.. surely that should be enough..?

..and i go to the kindle CLI either through kterm or ssh.. in both, i come out by typing exit.. or in the case of kterm sometimes, by using the 2 finger menu>quit option.. don't these count as a "logout"..?

will check again..

[ixtab]

Hmmm... I don't know. For me, it works as it should:

$ ssh root@kindle
[root@kindle root]# mntroot rw
system: I mntroot:def:Making root filesystem writeable
[root@kindle root]# grep ^root /etc/passwd 
root:x:0:0:root:/tmp/root:/bin/sh
[root@kindle root]# sed -i -e 's/\/tmp\/root/\/var\/tmp\/root/' /etc/passwd 
[root@kindle root]# grep ^root /etc/passwd 
root:x:0:0:root:/var/tmp/root:/bin/sh
[root@kindle root]# mntroot ro
system: I mntroot:def:Making root filesystem read-only
[root@kindle root]# echo $HOME
/tmp/root
[root@kindle root]# ^D
Connection to kindle closed.
$ ssh root@kindle
[root@kindle root]# echo $HOME
/var/tmp/root

[nasser]

there seems to be a difference between logging in through ssh and "logging in" through kterm.. see screenshots..
ssh recognises the "new" home at /home/root..
while the kterm session is still hung up on /tmp/root..