linuxmemes

Don't forget to restart the kernal

The fact that the Linux source code license is open doesn't give permission to another work about Linux.

An analogy would be a park - you can use it, go running, etc with no issues. But if you setup your easel and make a painting of the park, that painting is an original creative work, and it is protected under copyright laws.

The same for that sticker. Even with the image of Tux being made "free" (attribution) by its creator, this stylized combination of drawing and text is still copyrighted, so we'd have to ask their permission for the stickers.

Tried ACL, it kind of works. However users first respect the creation umask, which is generally 022. Which means they can create files in my directory but I can not delete them.

You can force everyone working with you to set their umask to 000, which clearly is not a really nice solution. However, even this does not solve the problem, since if they copy anything over which does not have 666 permissions then you can not edit it or delete it.

Then you're stuck with a bunch of files by someone else who left you their things that you can not delete.

I still have 1 TB of stuff somewhere from a user which has long been deleted from the system, I have no other way to delete that stuff than contact the system administrator.

You can assign a group and then set permissions to 660 and do some ACL magic which hopefully works to enforce a umask of 0 on group; however you can not create a group without being root, which does not really solve the problem.

To be fair, I would appreciate if users were allowed to create their own groups.

My longest running machine at the moment: 00:31:08 up 378 days, 5:12, load average: 0.00, 0.00, 0.00

My old raspberry pi 1b, which I use as an audio server for my stereo receiver. I typically have 4-5 machines running at any time performing various network-related tasks. I keep user terminals up as well, if they don't consume much (<=10w). GPU hogs get put to sleep.

The TL;DR I remember is that over a decade ago, someone who works on Gnome has decided that a machine with only a single user and a single DE does not need to have a "Log Out" button by default - when people mentioned that logging out of a user is still useful to reload settings, the response was that "just rebooting is fine in that case". Thing is, no one actually noticed those changes until now, because with the X11/Wayland switch, every environment was technically running two DEs and had the logout button. But now with Gnome 50, the switch was completed and the Logout button disappeared for many people (as technically intended, but that feature was implemented so long ago that even a lot of current Gnome devs were confused by it)

https://www.youtube.com/watch?v=HcJJ7UldMc8

How legit is this site? Considering the purchase. Lol

Make you reboot? More like “suggest a reboot”

They tell the user to reboot, and they don't phrase it like it is optional. It's been a while since I've used Ubuntu, for example, but my memory is that they say that a reboot is required, or something along those lines. There is nothing wrong with my using the phrase "make you reboot" for those cases.

not after “many updates” bit after installing a new kernel or graphics drivers on a running graphical desktop environment.

When I was using Ubuntu, I'd get a reboot request like once every couple of weeks to a month. Maybe you don't think that's "many updates", but the point of the sticker was obviously to compare to other operating systems, and in that regard, it was similar to Windows, probably more frequent.