

maybe the snapshot could be rolled back by a PXE bootable system. but for the second part, btrfs can do snapshots per subvolume, so if you could create a subvolume on user creation that could work
maybe the snapshot could be rolled back by a PXE bootable system. but for the second part, btrfs can do snapshots per subvolume, so if you could create a subvolume on user creation that could work
Btrfs and snapshots could help with atomicity, did you consider that?
do as I say
look babe, it’s a unique 8 point curve for each fan, isn’t that beautiful! do you hear it too?
Also that right click menu is lighters faster than the old school menu. Every application and their mother wants to add shit to the right click menu and it would lag out to the point it would take 10 seconds to open.
if you don’t install all the garbage of the internet, that’s not a problem. it can also be cleaned up, even without regedit.
windows 11
oh… now I understand everything
why would anyone else use your computer? honest question. and do they need access to your local files, or just a machine?
no I mean piping a downloaded script to the interpreter
that sounds horrible.
only of manual duplex printing would be a thing on linux…
I think windows does shut down, but the hardware in your computer does not, and so when booting linux, the hardware does not start with a fresh slate. It’s not reinitialized, keeping configuration and possibly custom firmware from the other OS.
interestingly, it also means malware could also escape a reboot this way… and for the network adapter, maybe it doesn’t even need to be compatible with linux to work.
what you mean though is the fast startup setting of windows. that does hibernate the computer as you say, after it logs out the user.
and at this point it’s also worth noting that this is a setting in the UEFI setup, and this is different to the fast startup setting in windows that also needs to be turned off for other reasons.
DoH, DoT, dnscrypt, whatever else
DoH, DoT, dnscrypt, whatever else
does retrains have any effect with hard? this is what man nfs says:
If neither option is specified (or if the hard option is specified), NFS requests are retried indefinitely. If the soft option is specified, then the NFS client fails an NFS request after retrans retransmissions have been sent, causing the NFS client to return an error to the calling application.
also, do you know what can I do with CIFS/SMB? I have most of my shares through samba :/
well that’s also interesting, but I mainly experience this problem on my desktop. there was a plasma version when even the taskbar panel got frozen, and the kde file manager, double commander too for like a minute, every time they try to do anything with an unreachable network drive. and its even worse on my laptop so there I just don’t mount my shares anymore.
I have been wondering how does windows do it, and programs made for windows, because this is a nonissue there (though windows has its fair share of problems with network shares though…). maybe they just learned to do all IO ops on a different thread…
I think it’s more of a consensus than a debate for those who had an nvidia card. a bunch of things don’t work as they should, because nvidia drivers are bad.
oh! maybe it’s the perfect chance to ask. what do you do with your mounted shares so that processes trying to access it do not hang when the server is unreachable?
mostly I would prefer if that directory read would just fail but anything is better, except unmounting.
I still write my mounts in fstab
all 16 777 216 colors, actually