@avidamoeba@lemmy.ca
@avidamoeba@lemmy.ca avatar

avidamoeba

@avidamoeba@lemmy.ca

This profile is from a federated server and may be incomplete. Browse more on the original instance.

avidamoeba,
@avidamoeba@lemmy.ca avatar

Search for access panels such as water shutoff valves.

avidamoeba, (edited )
@avidamoeba@lemmy.ca avatar

It’s been pretty good here for a couple of months. The ability to rank up/down, block/pin sources is a really good feature. When it fails, there’s always !g.

avidamoeba, (edited )
@avidamoeba@lemmy.ca avatar

So much for the legendary hardware support of Linux!

Edit: Forgot “/s”, but look at this lively discussion!

avidamoeba, (edited )
@avidamoeba@lemmy.ca avatar

I doubted. I checked. Check passed.


<span style="color:#323232;">$ sudo apt search liboobs 
</span><span style="color:#323232;">Sorting... Done
</span><span style="color:#323232;">Full Text Search... Done
</span><span style="color:#323232;">liboobs-1-5/jammy 3.0.0-4 amd64
</span><span style="color:#323232;">  GObject based interface to system-tools-backends - shared library
</span><span style="color:#323232;">
</span><span style="color:#323232;">liboobs-1-5-dbg/jammy 3.0.0-4 amd64
</span><span style="color:#323232;">  GObject based interface to system-tools-backends - debug symbols
</span><span style="color:#323232;">
</span><span style="color:#323232;">liboobs-1-dev/jammy 3.0.0-4 amd64
</span><span style="color:#323232;">  GObject based interface to system-tools-backends - dev files
</span>
avidamoeba,
@avidamoeba@lemmy.ca avatar

libass

avidamoeba, (edited )
@avidamoeba@lemmy.ca avatar

You already said it. Flatpak and Snap both include an entire system around updates and rollback which provide some pretty strong guarantees for update success. AppImage does not. It’s got some libs available that an individual developer could use to implement their own update mechanism but isn’t a built-in. And besides, without a system-level component that manages install/update/rollback, you can’t have any guarantees about the update process. You’re back to the Windows-world per-app update.exe paradigm (or update.sh in Linux).

avidamoeba,
@avidamoeba@lemmy.ca avatar

If they received a lot of money from their work and they used it to increase the impact of their projects, they wouldn’t be billionaires. The money would have been spent on the projects. If Linus headed a non-profit that received 10B a year revenue and spent most of it, leaving Linus with 0.5M-1M yearly salary, he wouldn’t be a billionaire and the billions spent on the Linux project would have had a significant impact. If on the other hand he pocketed 1B a year, there would be 1B less for the Linux project. And Linus would have been/become a different person.

avidamoeba, (edited )
@avidamoeba@lemmy.ca avatar

This is perfect. Well done. 👏

If still unclear, the sentient virus is:the child

avidamoeba,
@avidamoeba@lemmy.ca avatar

Parent comment is right. The body of documentation generated for Ubuntu by the community is an enormous asset. It’s one of the important side effects of it being the most used distro.

avidamoeba, (edited )
@avidamoeba@lemmy.ca avatar

This is not 2005 when the vast majority’s experience with interactive UX on a screen was Windows. People today operate Android, iOS much more so than Windows. Thus they are able to grok multiple OS chrome paradigms without much difficulty. And then the OS chrome is rather simple and therefore learning it doesn’t cost much or yield significant benefits should you have gotten that knowledge for free. Therefore the argument for choosing an OS based on its chrome is as shallow as the chrome itself. The difficult stuff is things not working due to defects (bugs), finding solutions and implementing them and that’s where the OS choice yields the highest benefit. On that front few options beat Ubuntu LTS other than perhaps Debian, but Debian isn’t novice-friendly.

avidamoeba,
@avidamoeba@lemmy.ca avatar

For 17 years now… Main machine hasn’t been reinstalled since 2014…

avidamoeba,
@avidamoeba@lemmy.ca avatar

I don’t know what’s available in Europe, but I’ve used Pluggable and StarTech dongles. They both work fine with Ubuntu without configuration. One of them is a Class 1 device, the other one Class 2. The Class 1 receiver has much better range and better connection stability. So the only useful thing I have to say is - look for a Class 1 receiver if you want the best range possible.

avidamoeba, (edited )
@avidamoeba@lemmy.ca avatar

Sounds like the decisions about what to make, how to make it and for whom to make it are done by the people doing the work. 🤔🫢

avidamoeba,
@avidamoeba@lemmy.ca avatar

Is it? I’ve been on Debian/Ubuntu since 2005 and I’ve never seen anything on-screen whenever I’ve gotten a kernel oops.

avidamoeba,
@avidamoeba@lemmy.ca avatar

I love this! Not only for the comedic value, but throwing kernel oopses on-screen when they can’t be easily captured when unprepared would be of great help in solving system problems. Unlike the cryptic messages Windows displays, Linux kernel messages are quite useful.

avidamoeba,
@avidamoeba@lemmy.ca avatar

Unless you make your host OS read-only, it itself will keep writing while running your docker containers. Furthermore slapping read-only in a docker container won’t make the OS you’re running in it able to run correctly with an RO root fs. The OS must be able to run with an RO root fs to begin with. Which is the same problem you need to solve for the host OS. So you see, it’s the same problem and docker doesn’t solve it. It’s certainly possible to make an Linux OS that runs on an RO root fs and that’s what you need to focus on.

avidamoeba, (edited )
@avidamoeba@lemmy.ca avatar

In short, it’s difficult. You have to be careful to only use themes that are are tested to work with your version of GNOME. That’s why while using GNOME, I’d stick with whatever stock theme variants come preinstalled. At least you get a few accent colors on Ubuntu. You can always change your wallpaper. 🥹

  • All
  • Subscribed
  • Moderated
  • Favorites
  • localhost
  • All magazines
  • Loading…
    Loading the web debug toolbar…
    Attempt #