Johannes Meixner
Johannes Meixner
@thomasmerz what does ``` # lsblk -ipo NAME,TYPE,FSTYPE,SIZE,MOUNTPOINTS,UUID ``` show on your system? I am in particular interested in the UUID. I assume when it is one btrfs on your...
@lzaoral my intent was not to reproduce it with one btrfs that consists of two partition devices because I assumed that the "spanning multiple disk devices" in the error message...
@thomasmerz ReaR never was able and never will be able to "recreate even the most weird disk setups that you even don't imagine right now". I assume that even the...
@rear/contributors could you please have a look here? I think this should be fixed for ReaR 2.8 because otherwise the minor issue https://github.com/rear/rear/issues/3151 would not be fixed in ReaR 2.8...
I have the same `.vimrc` ``` " An empty vimrc file to avoid that 'vi' inside the ReaR recovery system shows " Failed to source defaults.vim - Press ENTER or...
If I knew why I would "just fix" it, cf. https://github.com/rear/rear/issues/3238#issuecomment-2551334213
Ah! `/etc/vimrc` is not a dot-file - I missed that. I will try to fix it this way for ReaR 2.8...
Unfortunately it neither works with /etc/vimrc nor with /etc/.vimrc in the ReaR recovery system.
Unfortunately it neither works with /etc/vim/vimrc nor with /etc/vim/.vimrc in the ReaR recovery system.
In my ReaR recovery sytem made on SLES 15 SP6: ``` RESCUE localhost:~ # vim --version -bash: vim: command not found RESCUE localhost:~ # vi --version VIM - Vi IMproved...