I find it odd, because venv is a “Suggested package”, actually. It isn’t in the list of new packages that will be installed with python3 by default.
I think the next major release of apt is supposed to be easier to read. Unless Debian neuter it.
I find it odd, because venv is a “Suggested package”, actually. It isn’t in the list of new packages that will be installed with python3 by default.
I think the next major release of apt is supposed to be easier to read. Unless Debian neuter it.
I mean, we have systemd-bsod now…
Not that I’ve ever seen it of course.
Ah, that’s the misunderstanding. The original comment was talking about “watching something on another pc”. Like playing a video from a desktop PC on a laptop in another room. So it’s the samba server we want to prevent from sleeping, not the client. Yes it’d be nice to have a 24/7 media server set up, but for the simple case of sharing a file from one PC to another, it’d be nice for the server not to sleep in the middle of it by default.
For sure, I don’t know the internals of Samba, but surely the server knows that it’s serving a file no matter how the client accesses it. I don’t think a few dbus messages would cause issues.
I have my own service that looks at the network traffic via /proc and a few other things. That sends the system to sleep itself if everything looks truly idle.
I do think it would be nice for a file server like samba to inhibit sleep using the standard interface for it. But yeah, I appreciate there are complications, like video playback is presumably pulling a small extent of a file at a time, so there would have to be some kind of timer before releasing the inhibition or the system would sleep between transfers.
EDIT: I just took a look; with loglevel set to 3 for smb and smb2 I see log messages like:
smbd_smb2_read: fnum 1712966762, file my_video.mkv, length=262144 offset=82366464 read=262144
These occur at most 10 seconds apart when playing a video over a share from another host. I don’t see why the smbd daemon couldn’t inhibit sleep untill smbd_smb2_read hasn’t run for a minute or so. You could have a script that monitors that log output and does this externally but it’d be nice to have built in.
Not every program or service on your system
Of course not, but plenty do when running a task where the user is unlikely to make inputs and also doesn’t want the machine to sleep. Firefox can call org.gnome.SessionManager.Inhibit over dbus with the “video-playing” description, same for VLC. Transmission can call that interface while a transfer is in progress (with a config toggle). It seems a pretty reasonable default for samba to do the same while a long-running file transfer is ongoing.
[Samba] doesn’t copy your files for you.
Sure but it has to know when a transfer is running. It would be nice to have the option to inhibit sleep if the transfer is runs for a significant amount of time.
It should use systemd-inhibit (or whatever the dmesg dbus service is) to tell the system it’s busy. How else would the system know?
Don’t hurt me
Brush tools.
I would encourage you not to split things up too finely. A single repo for your environment would allow you to see all related changes with git. E.g. if you set up a new VM it might need a playbook to set something up, a script to automate a task, and a DNS entry. With a well put together commit message explaining why you’re making those changes there’s not much need for external documentation.
Maybe if you want some more info organised in a wiki, point to the initial commit where you introduced some set up. That way you can see how something was structured. Or if you have a issue tracker you can comment with research on something and then close the issue when you commit a resolution.
Try not to have info spread out too much or maintaining all the pieces will become a chore. Make it simple and easy to keep up.
Usually aluminium or glass. There’s a metallic coating applied to the outside surfaces that stores the data. That layer is very thin though, so most of the material is the substrate.
Why not switch to NixOS and run Duplicacy in an Arch Distrobox on top?
Oh right, that makes sense. I was only thinking of Matter as serving low bandwidth devices but it also runs over WiFi and ethernet so I guess it can do video for security cameras etc. and evidently Casting audio and video also.
Also Matter is the smart home interop standard. Seems close enough for some confusion in what Matter compatible means on a device.
Microsoft PowerToys has a pseudo-tiling wm for Windows. There are loads of new options on Linux so while few people from the total population are using them, I think they’re growing.
I’m sure you could get by without a terminal on modern desktop oriented distros. Windows has it’s own weirdness, like having to manually edit the registry. Just because there’s a GUI for that doesn’t make it a better user experience. A ton of issues are basically unfixable by users on Windows and Mac. I’m not decompiling their kernel to figure out why sleep is so flakey. Linux is much more reliable.
ldconfig
sets up links and caches for loading library code. That might be an issue if your install is broken between updates. You can use ldd
to check if code can be looked up. ldd /usr/lib/x86-64-linux-gnu/libpcre2-8.so.0
should show no errors. Likewise for ldd /usr/sbin/init
.
(Your paths may vary)
Core utils has this AI built in: yes
Liberté, égalité, fromagé ou la mort!
Make sure it doesn’t go from suck to blow!
Is there any reason to keep the existing set-up? If it’s just one drive, you could replace it with another and install Alma or something fresh. Then you could copy over whatever config the old system had to get up and running again. You could swap to the old drive if you needed to revert. If you have a spare machine, you could stand up the fresh setup side-by-side with the old one before swapping over.