Yes, for example, syncing on a kernel panic could lead to data corruption (which is why we don't do that). For the same reason REISUB is not recommended anymore: The default advice for a locked-up system should be SysRq B.
0v0
Try perhaps the solution in https://unix.stackexchange.com/questions/648084/docker-interface-tears-down-wifi-internet
Try removing all the superfluous default routes.
I think glider can do this, with -strategy rr
(Round Robin mode). I have not used it in this way myself, so you might need to experiment a little. Proxychains can also do this, but it doesn't present a socks5 interface itself (it uses LD_PRELOAD
, so it won't work everywhere).
Argon2id (cryptsetup default) and Argon2i PBKDFs are not supported (GRUB bug #59409), only PBKDF2 is.
There is this patch, although I have not tested it myself. There is always cryptsetup luksAddKey --pbkdf pbkdf2
.
Consider the string abc
. From the end, moving backwards, when does it match \w+
, and what does it match? When it reaches c
, it matches c
. And from the front, moving forwards? When it reaches a
, it matches abc
. This is why it acts differently.
The regexp itself always looks forward, the BACKWARD argument just determines which direction the point should move after a match.
Because once it hits the ultimate character of a word, \w+
matches that (single) character, next time it matches the penultimate character, etc. You'd need \W\w+
to make it look far enough back to the beginning of the word.
This seems right and exactly the way I've set it up. On subvolid=5 I have subvolumes @
and @home
, in /etc/fstab
I mount /
as subvol=@
, and /home
as subvol=@home
.
Could you run sudo lshw -C network
and post the output for the wireless interface?
singlelogin.re still worked for me recently.
Source