You are not logged in.
Hi all!
I'm an old enthusiastic crunchbang user switching to bunsenlabs (even happier with it so far!) after my computer broke few days ago.
After installing the system to the new machine, from a live system I deleted the $HOME directory and copied my old one from a backup I've made.
When rebooting I noticed that many of my old configuration files (.Xresources, openbox rc, autostart, menu and so on) where automatically renamed (e.g. .Xresources~2018-03-19T20:01:36~) and replaced with the standard bunsenlabs versions.
Obviously this is not a prblem at all but, just out of curiosity, which is the process responsible for that?
Offline
which is the process responsible for that?
That's our bl-user-setup script doing it's work
We use it to configure the user's desktop on the first login, it leaves a file behind after running and will not run again if that file is present.
So to stop it from starting, create the file before the first login (when copying the old files over):
touch ~/.config/bunsen/bl-setup
Perhaps bl-user-setup should check for any openbox configuration files in ~/.config rather than our specific stamp to cover this case.
Offline
Thank you!
Now i know a little bit more bunsenlabs in-depths.
Keep up the good work! I plan this will be my distro of choice for many years ahead.
Offline
Perhaps bl-user-setup should check for any openbox configuration files in ~/.config rather than our specific stamp to cover this case.
Or it could touch something outside of $HOME? edit: probably enough to be outside of .config dir, like touch "$HOME/.dontDeleteMe"
^ EDIT; After some tinkering both bad ideas, just leave it as it is. It is expected from the user to be able to merge backups.
Last edited by brontosaurusrex (2018-03-22 06:42:48)
Offline