Mar 15 13:45:46 erlangen systemd: Started Mein WPA-Service. Mar 15 13:45:46 erlangen wpa_supplicant: Successfully initialized wpa_supplicant Mar 15 13:45:46 erlangen systemd: Starting Mein WPA-Service. Main PID: 3663 (code=exited, status=0/SUCCESS)ĬGroup: /usr/sbin/wpa_supplicant -B -i wlp3s0 -c /etc/wpa_supplicant/wpa_nf Process: 3662 ExecStart=/sbin/ip l set wlp3s0 up (code=exited, status=0/SUCCESS) Process: 3663 ExecStart=/usr/sbin/wpa_supplicant -B -i wlp3s0 -c /etc/wpa_supplicant/wpa_nf (code=exited, status=0/SUCCESS) Process: 3661 ExecStop=/sbin/ip l set wlp3s0 down (code=exited, status=0/SUCCESS) Loaded: loaded enabled vendor preset: disabled)Īctive: active (exited) since Fri 13:45:46 CET 14min ago Question: If I move the root parition into a logical volume via the rescue system, what do I have to change to inform GRUB about these changes for the next boot?Įrlangen:~ # systemctl status - Mein WPA-Service Clear to me, that this could only be established when VPS is started with a rescue system, with all partitions / logical volumes are available, but not mounted. Not sure but I guess that for this it would be easier if the rooot partition would also be on a logical volume.
#Qmapshack proj4 5.0 how to
From new Leap installations I know, that it's possible to start with a complete encrypted setup, but do we have any "recipes" how to get this afterwards, avoiding a complete new installation? I'm of course aware that LUKS/dmcrypt can only encrypt empty partitions, but I've enough space left on my VPS to create additional logical volumes and move the existing data to the newly created encrypted logical volumes. Would like to change it to get all partitions encrypted, preferable with a single pass phrase to be asked at boot time, not pass phrases for each logical volume / encrypted file system
All other mount points like /var, /srv, /home, /tmo as LVM logical volumes.
I've a VPS, Leap 15.0, with root partition as a "plain" partition.
0 kommentar(er)
