

that sounds horrible.
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
a stop job for UID 1000… 1:45 minutes
oh oh and then it changes to 3 minutes something when 1:45 passes! where was that configured mr poettering??
you forgot nvidia
drink some Wine and there will be your Windows
what desktop is that? fedora kde has separate options for shutdown and shutdown-and-update, same for reboot. I think it’s a native plasma 6 feature, integrates with packagekit and systemd’s special boot mode.
untattended updates are good. except of course if you want to gatekeep hard, but let’s pretend you do not. if the pros can easily turn it off there’s absolutely no problems with it. and we can. but for real desktop systems, it needs to be on by default.
it was a mod removal: https://lemmy.ml/modlog/14
they say rule 1, which is
Be civil and nice.
this look like a candidate for yepowertrippingbastards. what was that site that can show the mod that deleted the content, and sometimes the deleted content too?
why did you delete the other post? or was it a mod?
Videoconferences? Forget about it. Images that look normal? You don’t need them.
what? these are non-existent. jitsi works fine. webaudio api was disabled by default a few years ago, but not anymore.
but I have no idea what do you mean with images
This theory is based on my understanding that computers don’t go all the way to sleep anymore and reenabling S3 restores normal sleeping.
yeah, now that you say that is probably most laptops in the last few years. but I don’t think desktops do it. wrong, even my 4+ years old pc motherboard supports it according to /sys/power/mem_sleep
no I mean piping a downloaded script to the interpreter