4 ms·

I use this technique, based on a bare git repo https://www.atlassian.com/git/tutorials/dotfiles https://www.atlassian.com/git/tutorials/dotfiles Works quite we

I use this technique, based on a bare git repo https://www.atlassian.com/git/tutorials/dotfiles https://www.atlassian.com/git/tutorials/dotfiles Works quite well ... but I'm really, really ready for a rebuild of how Linux systems are built. I hope systemd-homed will deliver. Imagine you could ssh into a machine with a flag that forwards your local config. Or even your local bin.

politelemon 6y ago
That sounds really convenient. How far away is the homed system from adoption?
wbl 6y ago
You mean what we had with project Athena for decades? Or NFS mounted homework? Or plan 9?
- segfaultbuserr 6y ago
  NFS, The Network is the Computer (TM). It's a bit strange that now it's a Cloudflare trademark.
- curryst 6y ago
  > Or NFS mounted homework? I would not wish this pain on others. It works great when your systems are homogenous. It rapidly becomes a pain when you need to make customizations that only apply in a particular network, or on hosts with a particular OS version, etc. My bashrc has basically just become a monstrosity to control what files get sourced for this particular host. Answering why a particular env car is set to what it is ends with me trying to trace what files get loaded, what they set, and the order they get loaded in. Much more painful than separating the concerns and having Ansible template out my bashrc.
  - heroprotagonist 6y ago
    I moved to splitting my bashrc into multiple files and having my main bashrc source them from a ~/.bashrcd directory. At heart it's a short snippet that just checks for existence and sources each file in the directory: https://github.com/targaryen/bashrcd/blob/master/install/install_brcd.sh#L46 https://github.com/targaryen/bashrcd/blob/master/install/ins... I added aliases to list/edit/remove entries from the .bashrcd directory and resource it. And a script I can call with a one-liner to edit bashrc on a new machine to add the sourcing and the helper aliases. It'll load alphabetically so I can prefix entries with a number to specify load order (defaulting to 0100 so I don't need to specify this in the commands unless I explicitly changed them). So the end result is that I can quickly edit or create a new bashrc entry by running 'ebrc entryname'. This opens ~/.bashrcd/0100--entryname in vi, and when it's saved it'll re-source so the add/change takes effect immediately. Or 'lbrc' to list contents of the directory, or 'rbrc entryname' to remove ~/.bashrcd/0100--entryname It's fairly simplistic but takes away most of the cognitive load of managing a complex bashrc.
Arnavion 6y ago
I don't think systemd-homed does anything for dotfiles, let alone portable dotfiles. The user record only contains (the path to) a skeleton directory used to create the homedir if it doesn't already exist. Populating such a newly-created homedir with your dotfiles is still your responsibility.

politelemon 6y ago

That sounds really convenient. How far away is the homed system from adoption?

wbl 6y ago

You mean what we had with project Athena for decades? Or NFS mounted homework? Or plan 9?

segfaultbuserr 6y ago
NFS, The Network is the Computer (TM). It's a bit strange that now it's a Cloudflare trademark.
curryst 6y ago
> Or NFS mounted homework? I would not wish this pain on others. It works great when your systems are homogenous. It rapidly becomes a pain when you need to make customizations that only apply in a particular network, or on hosts with a particular OS version, etc. My bashrc has basically just become a monstrosity to control what files get sourced for this particular host. Answering why a particular env car is set to what it is ends with me trying to trace what files get loaded, what they set, and the order they get loaded in. Much more painful than separating the concerns and having Ansible template out my bashrc.
- heroprotagonist 6y ago
  I moved to splitting my bashrc into multiple files and having my main bashrc source them from a ~/.bashrcd directory. At heart it's a short snippet that just checks for existence and sources each file in the directory: https://github.com/targaryen/bashrcd/blob/master/install/install_brcd.sh#L46 https://github.com/targaryen/bashrcd/blob/master/install/ins... I added aliases to list/edit/remove entries from the .bashrcd directory and resource it. And a script I can call with a one-liner to edit bashrc on a new machine to add the sourcing and the helper aliases. It'll load alphabetically so I can prefix entries with a number to specify load order (defaulting to 0100 so I don't need to specify this in the commands unless I explicitly changed them). So the end result is that I can quickly edit or create a new bashrc entry by running 'ebrc entryname'. This opens ~/.bashrcd/0100--entryname in vi, and when it's saved it'll re-source so the add/change takes effect immediately. Or 'lbrc' to list contents of the directory, or 'rbrc entryname' to remove ~/.bashrcd/0100--entryname It's fairly simplistic but takes away most of the cognitive load of managing a complex bashrc.

Arnavion 6y ago

I don't think systemd-homed does anything for dotfiles, let alone portable dotfiles. The user record only contains (the path to) a skeleton directory used to create the homedir if it doesn't already exist. Populating such a newly-created homedir with your dotfiles is still your responsibility.