Skip to main content

Sharing one home directory between the Linux machines with the different display resolutions and different pointing devices, keeping $HOME/.config data for each machine

 Back in 1990's, it was common practice to share one home directory between many UNIX servers using NFS. But it is not in these days.

But I have become to want to share my home directory between two different Linux machines: One is  a Debian GNU/Linux installed as a primary OS of a dual boot machine,  and the other is a virtualized Linux box within the Virtualbox running under the Windows 10, a secondary OS of the dual-boot.

They have different display resolutions and pointing devices. These differences led me to an annoying problem: if you open GNOME desktop environment, display and pointing device setting became broken.

Today's GNOME desktop environment stores most of the settings to the files under $HOME/.config directory. But if you share $HOME/.config between two machines, the stored configuration for a particular machine may become incompatible with other machines with different display resolutions and pointing devices.

Indeed, my GNOME desktop has become unusable.


To overcome this problem I renamed $HOME/.config directory to the name which have host name as a suffix.

According to XDG Base Directory Specification, alternative directory of $HOME/.config can be specified with the environment variable XDG_CONFIG_HOME.

So, you can set XDG_CONFIG_HOME like:


$ cat /etc/profile.d/xdg_config.sh

XDG_CONFIG_HOME=$HOME/.config-`hostname`
export XDG_CONFIG_HOME

 

Of cource, the different machines must have different names.

This solution is working perfect for me.

Labels:

Comments

Post a Comment

Popular posts from this blog

Some adjustment to run some daemon services within LXC container

 I built and am running a mail server, using dovecot for IMAP4 server and Power DNS (pdns) for DNS authoritative server, and memcached for back-end service for some mail filter. I also use LXC for staging environment to test my mail server, but running those services is not straight forward. My understanding is that it is because some security features of systemd using Linux kernel namespace function conflict with the use of namespace in LXC container. So, if you want to run memcached, dovecot, and pdns via systemd within LXC container, you have to disable some security features of systemd by configuration. My additional configuration to systemd is as follows: root@myhost:/# cat /etc/systemd/system/memcached.service.d/99-ns.conf [Service] ProtectSystem = no ProtectHome = no PrivateDevices = no PrivateTmp = no cat /etc/systemd/system/dovecot.service.d/99-ns.conf [Service] ProtectSystem = no PrivateDevices = no PrivateTmp = no root@myhost:/# grep -v '#' /etc/systemd/system/pdns.s...
Post a Comment
Read more

Xen on Squeeze failed to start up the X server with an Intel graphics controller

I recently tried to set up Xen on my Squeeze box, with intel 945GM graphics controller. I followed the instruction on Xen - Debian Wiki . I installed the Xen hypervisor, kernel, xen-tools and other stuff, then created a domU image of Ubuntu natty. After that, I rebooted the system. But when X server was about to be launched, the screen became black out,  both keyboard and mouse don't work anymore. I reread the article on the wiki, and figured out the Xorg driver for Intel graphics controller  is suspicious. So, I changed the Xorg driver 'intel' to 'fbdev' wrting /etc/X11/xorg.conf , and rebooted.  This workaround works out! The drawback of the workaround is, 'intel' driver specific features, including DRI and XvMC, are disabled.
1 comment
Read more

Configuring Network Manager for PPPoE connection

When I'm home, I use fiber-optic line with a dedicated old small router (YAMAHA RT107e) for access to the Internet. But I recently became anxious about the router. If it fails, how can I survive until I get another one? So, I tried to connect my Debian desktop PC to the fiber-optic line without the router. The PC have to talk to the other side of the line with PPPoE but I did not know how. In my PC, the Network Manager manages network configuration. So, I had to configure the Network Manager to utilize the pppoe like : nmcli connection add ifname eth0 connection.type pppoe username USERNAME password PASSWORD
Post a Comment
Read more