Highly recommend against relying on your doctor to answer this. Ask your pharmacist. They will likely have a much better idea on the reason for the suggested limit.

I have used linux the better part of a decade but have never really followed kernel development.

What does it mean for the kernel to be “monolithic”? What would need to change in the kernel for it to no longer be considered “monolithic”?

Systemd’s change is inconsequential. If you really care then you should also fight to remove full name and address from user db.

Also there are still other jurisdictions that have these sorts of laws.

The California law does not require verification. Only attestation.

As someone who does manage more than 100 linux systems. I would choose systemd over anything else any fucking day.

no HDMI support

What distro doesn’t have HDMI support?!

You know I saw that device before and was interested. I think one reason people might like this better is due to the hackability but it sounds like the xteink is fairly hackable too (and probably has better long term support).

Personally I am still trying to go back to physical books before I try another e-reader.

The main point of the device is to be tiny so you can just have it in your pocket. Hopefully, encouraging you to read more by lowering the barrier to start.

Though I am sure this device is not meant for everyone.

Strange I guess I am not aware of any distros that come with network drives pre-configured. But either way that would be a configuration error on the distro’s side then. Waiting for a network share to be available is actually a feature to many.

Say for instance you had critical data on the network share then you might not want to boot if that is not available. And if you don’t then you might mark the share as nobootwait.

Without knowing what the configuration on this specific drive you are having trouble with I really could not say what is wrong.

If you are having those issues with booting maybe it is because you configured your network share incorrectly? If you are waiting on shutdown timeouts for something then just go edit the timeout. systemctl edit <stuck thing>.

Typically when I crawl through journald it is to diagnose a problem with a specific application. Actually, the fact that those logs are easily accessible in a centralized place with easy to understand commands to access them is a reason why systemd (or more specifically systemd-journald) is so great.

The only times that I have had major issues like that was either because (A) I misconfigured something or (B) a package came misconfigured.

Quick someone share the dns haiku.

Do you have a source on the udev thing? I have not heard of this.

Were you looking at man systemd.timer? Pretty much everything you need is on there and it is not too complicated.

That law just says “A person that violates this title[…]”. Which is vague. But it appears to me that this would include the parent.

It is also something that only athe AG can bring charges for. This won’t be something that police are getting out their ticket books for. And if we don’t like how the AG is handling it, we can try to recall them.

there’s not a system in place to assign them responsibility regarding the child accessing places it should not (if we do really think they should not).

That’s what this law does. It provides a system (age attestation) and penalties for violating it.

No. I am more referring to how we left parents to let their children have free reign of the internet and they got injured. It is exactly because we cannot trust parents to moderate what their children do online that these laws are coming up. Do you think we would still get these laws if there were no children on the internet (maybe still for pron but that is because people are prudes).

I see that you edited your comment to take this part out but I do want to talk about it anyways.

You compared this to having automatic roads that shift risky drivers to their own space and how that would be ridiculous. Which it would be. But comparing a law like this to driving is an awful comparison.

Until recently there were very few laws regulating what a child is allowed to access online. But that is just not the same as driving. States require that you get a license, take a test, follow road rules, get your vehicle inspected, and many more requirements. We have these requirements because we know that we should not let an untrained driver on the road.

So fucking true. Once you get more than a hundred systems or so it feels like something new to resolve every day. Especially when your work let’s people with no idea what they are doing have root on “their” servers.

I have dealt with issues ranging from someone uninstalling subscription manager (RHEL) and then clearing the package cache to people replacing chronyd with ntpd for… Reasons? I guess?

I have thought about using bazzite but I prefer debian based as well as using more general purposed distros. So I am just on basic debian.

Usually when I need to do something like this I use python and BeautifulSoup4. You basically get the content of the web page and use bs4 to parse it and pull out the correct link. You will need to look at the source of the page to understand their page format.

If python requests isn’t able to get the right data then you might need to use selenium to use a full web browser to render the page and run any Javascript that might populate the page. Then you send that page content to bs4.

Edit: I know someone posted a link to archive but I figured some instructions would also be useful.

I’m not sure that I would recommend a newer user use sysrq. It is a very powerful tool that you definitely should not be blindly following from a random internet post without knowing what each command does.

In a truly frozen system then it can be good, but only as a final last resort. If the system can be unfrozen by other methods then that should be preferred instead.

There are a couple of things you can do. If it is frozen then try pressing ctrl+alt+1/2/3/4 to swith to a different terminal this will let you either restart your DE or reboot the system safely.

As far as debugging it I would typically start with looking at journal logs journalctl -b-1 should show you logs from the last boot.