On Wed, 22 Jan 2025 17:06:34 +0100 Hans <hans.ullr...@loop.de> wrote:
> > "It shows" ??? What shows? How? > > See: > > root@protheus3:~# ls -la /boot/efi/ > insgesamt 7 > drwx------ 4 root root 1024 1. Jan 1970 . > drwxrwxrwx 5 root root 4096 19. Jan 20:28 .. > drwx------ 5 root root 1024 18. Jan 12:10 EFI > drwx------ 2 root root 1024 18. Jan 12:43 'System Volume Information' > > root@protheus3:~# ls -la /efi/ > insgesamt 7 > drwx------ 4 root root 1024 1. Jan 1970 . > drwxr-xr-x 26 root root 4096 22. Jan 16:43 .. > drwx------ 5 root root 1024 18. Jan 12:10 EFI > drwx------ 2 root root 1024 18. Jan 12:43 'System Volume Information' > root@protheus3:~# Ah. I would have done something like "diff -r /efi /boot/efi". Since you have a Windows installation, there's a lot below that EFI directory. > The installation I did was a little bit tricky. As I needed to > transfer my old Debian from ssd to nvme and it is dual-boot, I first > installed Windows, then installed debian. After ist, backuped /etc to > somewhere. Then rsynced / , / home, /var, /usr and so on to the NVME. > After ist, rsynced the backupped /etc back, so that I got all the > devicenames back. > > This worked well so far. Instead of this little issue. I'm glad it's working well. My usual process for such a situation is a bit more complicated and probably safer. I back up a lot of the same stuff you do. I then restore it to /crc/<hostname>, and compare them with what the installer has put in place. In particular, a lot of "find /crc/<hostname> -name "*~" to locate files I have edited in the past. I then diff those against their new replacements and accept the changes I want. Tedious, but probably safer, and it gets me thinking about my customization. -- Does anybody read signatures any more? https://charlescurley.com https://charlescurley.com/blog/
