Obviously the criminal here is the person who asked the question and posted a screenshot of the answer.

Thanks. Sorry to see my assumption was correct; that does indeed sound a lot like when they were called OSSO two decades ago.

Notably absent from the list of things they might open source soon is their current “Lipstick” UI, the graphical shell itself.

All of the stuff they plan to open source are things I didn’t even figure out were still closed from my 5-10 minutes of research before writing my previous comments. It is difficult to estimate the number (do you know how?) of other small closed components which they can dribble out over the next years to maintain users’ false hope that they will one day have an actually-open-source operating system.

we’ll see though

my advice is: don’t hold your breath.

Sorry if this sounds bitter, but it’s because I am - I naively believed that OSSO might actually ship a free OS one day (to be fair they didn’t say they would either, but they helped us believe that they might… in effect saying “we’ll see” for years while releasing bits here and there) and it was frustrating to realize that it was never a real possibility.

Got a link about it? Have they just said they plan to make it “more” open, or do they actually plan to make the full OS actually be free software, like AOSP, pmOS, or most of the other things on, eg, the pinephone software page? (note that sailfish is also listed there, but iiuc its UI and some other bits remain closed-source).

It is the direct descendant of Nokia’s OSSO (“Open Source Software Operations”) division, both in terms of people and software.

Unfortunately they’ve been saying on and off that they plan to slowly open source more of it literally since they first started… which was [checks calendar] now 20 years ago. So, I lost my optimism that they would ever finish opening it quite a while ago.

and we’ll open source the hardware and software interface specs so anyone can design, 3D-print, or produce their own modules

oh cool, people can make open source “other half” add-ons for the proprietary “first half” of the phone itself 🙄

i wonder what percentage of jolla customers still mistakenly believe SailfishOS to be open source? (most of the ones i’ve met did…)

1 reason it’s wrong to me: https://nosystemd.org/

Under “Notable bugs and security issues” there is a big list of issues which were all (afaict) fixed many years ago.

There have been reasonable philosophical objections to systemd, some of which are still relevant, and as that site shows there are still many distros without it, but for the vast majority of desktop users who want something that JustWorks… using a mainstream distro with systemd is the way to go.

This blog post from pmOS covers some of the pain of trying to use KDE or GNOME without it.

Would be easier to know how old a kernel release is without looking it up.

I concur, but it would be much easier to make the major version the current year (as many projects do, and Linux should imo) rather than the whole project’s age at the time of a release.

Linux is only 34 years old, btw.

when this is over […] we can finally go back

Hang Don Chafin 🎶

I have to ask: what’s with all the obsession with immutable distro?

I guess the promise of having updates JustWork™? I don’t currently use one but I see the appeal.

However FWIW, unlike its namesake ChromeOS, the “Nixbook OS” this post is about is not actually an immutable distro: the instructions are to install NixOS normally and then clone the nixbook repo into /etc/nixbook and run its install.sh. Among other things it installs an update service which runs git pull on that repo as well as running nixos-rebuild boot --upgrade and flatpak update --noninteractive --assumeyes etc.

Cheers to this guy for what he’s doing, but the name is a little confusing. This approach works but it is not nearly as robust as the immutable distro paradigm implied by the name.

i haven’t used it myself but https://jmp.chat/ looks good if you’re OK with a US or Canadian number.

there is a lemmy community about it here: !sopranica@lemmy.ml.

cc @singpolyma@lemmy.ml

Bespoke is a synthesizer first but “like a DAW in some ways, but with less of a focus on a global timeline. Instead, it has a design more optimized for jamming and exploration.” (youtube trailer, wiki, wikipedia)

“But you can’t copy with Ctrl+C, it’s…” - You can. When something is selected It copies selection to clipboard, otherwise it sends SIGINT.

What terminal emulator are you using where ctrl-c copies instead of sending SIGINT when text is selected? In every one I’ve ever used, ctrl-c still sends SIGINT even with text selected (and one must must use ctrl-shift-C/ctrl-shift-V to copy/paste).

I don’t have any suggestion for getting the behavior you’re asking for, but besides the normal ctrl-(shift)-C/V clipboard FYI you also have two other types of clipboard-like things: one which works anywhere (not only in the terminal) and is actually always automatically copying anything you select and lets you paste from it with middle click (this originated with X Windows but i think most Wayland compositors have also implemented it by now), and another which is found in GNU Readline (used by bash and numerous other REPLs) called the “kill buffer” which can be pasted (or “yanked”) from and cut (or “killed”) to using Emacs keyboard shortcuts (which also include various cursor movement controls).

Notes:

• the kill buffer is local to a given readline context, it’s not shared across different shell windows.
• the list of emacs keybindings in that wikipedia article i linked is currently confusingly referring to the kill buffer as “the clipboard”
• you can drastically reconfigure your readline keybindings and other behavior by editing your .inputrc file, but you cannot achieve what you were originally asking for because there is no concept of text selection in readline.

HTH!