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.
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.
https://linux-tc-notes.sourceforge.net/tc/doc/cls_u32.txt:
The base operation of the u32 filter is actually very simple. It extracts a bit field from a 32 bit word in the packet, and if it is equal to a value supplied by you it has a match. The 32 bit word must lie at a 32 bit boundary.
Try removing all the superfluous default routes.
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
.
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?
We have those on I2P already, see tracker2.postman.i2p for example.
You should not torrent over the tor network, but you can torrent over the I2P network. qBittorrent even has experimental I2P support built in.
But you can do this.
Memory safety would be the main advantage.
You can give chisel a try. It tunnels all traffic over http/https, and the client can then create port forwards, just as with ssh, to access other services.