#soluslinux — Public Fediverse posts

@zimmatore Solus is still being actively developed, right? I know it was dead for a second there after the split between it and the Budgie project, but I remembered it coming back.

Honestly, I like it as a rolling release similar to Silverblue in that I *never* install anything through the distro repos except for terminal tools and otherwise pull everything from Flathub and AppImage that I can so I just have a solid system powering a stable set of tools.

What are you planning to use it for?
#SolusLinux #SolusBudgie #Linux

@zimmatore Solus is still being actively developed, right? I know it was dead for a second there after the split between it and the Budgie project, but I remembered it coming back.

Honestly, I like it as a rolling release similar to Silverblue in that I *never* install anything through the distro repos except for terminal tools and otherwise pull everything from Flathub and AppImage that I can so I just have a solid system powering a stable set of tools.

What are you planning to use it for?
#SolusLinux #SolusBudgie #Linux

@zimmatore Solus is still being actively developed, right? I know it was dead for a second there after the split between it and the Budgie project, but I remembered it coming back.

Honestly, I like it as a rolling release similar to Silverblue in that I *never* install anything through the distro repos except for terminal tools and otherwise pull everything from Flathub and AppImage that I can so I just have a solid system powering a stable set of tools.

What are you planning to use it for?
#SolusLinux #SolusBudgie #Linux

So, #Debian has a bit of a reputation on flimsy hardware support. You couldn't even install D12 on a Z8xxx series CPU without fiddling with it unless you wanted to end up with an unbootable system.

I happen to have next to me another "special" system, a Chromebox with an 8th-gen Intel CPU. Which have a notoriously heinous sound subsystem (there's a paid driver for Windows).

I've dropped #CachyOS, #Ubuntu, #Fedora, #ElementaryOS, #ZorinOS, #MXLinux, #Bazzite, #AlpineLinux, #SolusLinux, #VanillaOS, and a few more on this system.

NONE of them was able to correctly configure audio on this machine. Some would not even detect an audio sink, others would have an "Analog Audio" sink, but no HDMI. Others would have a "Dummy Output". Fedora even listed my network-connected AV Receiver as an audio sink (!), but not HDMI.

And then there's Debian 13... Which correctly outputs over HDMI **OUT OF THE BOX**...

WAT

#Linux

So, #Debian has a bit of a reputation on flimsy hardware support. You couldn't even install D12 on a Z8xxx series CPU without fiddling with it unless you wanted to end up with an unbootable system.

I happen to have next to me another "special" system, a Chromebox with an 8th-gen Intel CPU. Which have a notoriously heinous sound subsystem (there's a paid driver for Windows).

I've dropped #CachyOS, #Ubuntu, #Fedora, #ElementaryOS, #ZorinOS, #MXLinux, #Bazzite, #AlpineLinux, #SolusLinux, #VanillaOS, and a few more on this system.

NONE of them was able to correctly configure audio on this machine. Some would not even detect an audio sink, others would have an "Analog Audio" sink, but no HDMI. Others would have a "Dummy Output". Fedora even listed my network-connected AV Receiver as an audio sink (!), but not HDMI.

And then there's Debian 13... Which correctly outputs over HDMI **OUT OF THE BOX**...

WAT

#Linux

So, #Debian has a bit of a reputation on flimsy hardware support. You couldn't even install D12 on a Z8xxx series CPU without fiddling with it unless you wanted to end up with an unbootable system.

I happen to have next to me another "special" system, a Chromebox with an 8th-gen Intel CPU. Which have a notoriously heinous sound subsystem (there's a paid driver for Windows).

I've dropped #CachyOS, #Ubuntu, #Fedora, #ElementaryOS, #ZorinOS, #MXLinux, #Bazzite, #AlpineLinux, #SolusLinux, #VanillaOS, and a few more on this system.

NONE of them was able to correctly configure audio on this machine. Some would not even detect an audio sink, others would have an "Analog Audio" sink, but no HDMI. Others would have a "Dummy Output". Fedora even listed my network-connected AV Receiver as an audio sink (!), but not HDMI.

And then there's Debian 13... Which correctly outputs over HDMI **OUT OF THE BOX**...

WAT

#Linux

So, #Debian has a bit of a reputation on flimsy hardware support. You couldn't even install D12 on a Z8xxx series CPU without fiddling with it unless you wanted to end up with an unbootable system.

I happen to have next to me another "special" system, a Chromebox with an 8th-gen Intel CPU. Which have a notoriously heinous sound subsystem (there's a paid driver for Windows).

I've dropped #CachyOS, #Ubuntu, #Fedora, #ElementaryOS, #ZorinOS, #MXLinux, #Bazzite, #AlpineLinux, #SolusLinux, #VanillaOS, and a few more on this system.

NONE of them was able to correctly configure audio on this machine. Some would not even detect an audio sink, others would have an "Analog Audio" sink, but no HDMI. Others would have a "Dummy Output". Fedora even listed my network-connected AV Receiver as an audio sink (!), but not HDMI.

And then there's Debian 13... Which correctly outputs over HDMI **OUT OF THE BOX**...

WAT

#Linux

So, #Debian has a bit of a reputation on flimsy hardware support. You couldn't even install D12 on a Z8xxx series CPU without fiddling with it unless you wanted to end up with an unbootable system.

I happen to have next to me another "special" system, a Chromebox with an 8th-gen Intel CPU. Which have a notoriously heinous sound subsystem (there's a paid driver for Windows).

I've dropped #CachyOS, #Ubuntu, #Fedora, #ElementaryOS, #ZorinOS, #MXLinux, #Bazzite, #AlpineLinux, #SolusLinux, #VanillaOS, and a few more on this system.

NONE of them was able to correctly configure audio on this machine. Some would not even detect an audio sink, others would have an "Analog Audio" sink, but no HDMI. Others would have a "Dummy Output". Fedora even listed my network-connected AV Receiver as an audio sink (!), but not HDMI.

And then there's Debian 13... Which correctly outputs over HDMI **OUT OF THE BOX**...

WAT

#Linux

@VildaVedo AFAIK, this is not specific to fedora, but the way #GnomeSoftware handle system updates. I have the same behavior if I update system packages via Gnome Software in #debian, and it’s also the behaviour in #SolusLinux since they migrated to Gnome Software.

@VildaVedo AFAIK, this is not specific to fedora, but the way #GnomeSoftware handle system updates. I have the same behavior if I update system packages via Gnome Software in #debian, and it’s also the behaviour in #SolusLinux since they migrated to Gnome Software.

Solus entra in una nuova epoca! Arriva Polaris, il nuovo repository stabile, con aggiornamenti a systemd, rimozione di Python 2 e GNOME 49. Scopri cosa significa per il tuo sistema Linux. #SolusLinux #Polaris #EpochBump #LinuxNews

https://www.linuxeasy.org/solus-nuova-epoca-repository-polaris-linux/?utm_source=mastodon&utm_medium=jetpack_social

Solus entra in una nuova epoca! Arriva Polaris, il nuovo repository stabile, con aggiornamenti a systemd, rimozione di Python 2 e GNOME 49. Scopri cosa significa per il tuo sistema Linux. #SolusLinux #Polaris #EpochBump #LinuxNews

https://www.linuxeasy.org/solus-nuova-epoca-repository-polaris-linux/?utm_source=mastodon&utm_medium=jetpack_social

Solus entra in una nuova epoca! Arriva Polaris, il nuovo repository stabile, con aggiornamenti a systemd, rimozione di Python 2 e GNOME 49. Scopri cosa significa per il tuo sistema Linux. #SolusLinux #Polaris #EpochBump #LinuxNews

https://www.linuxeasy.org/solus-nuova-epoca-repository-polaris-linux/?utm_source=mastodon&utm_medium=jetpack_social

Solus entra in una nuova epoca! Arriva Polaris, il nuovo repository stabile, con aggiornamenti a systemd, rimozione di Python 2 e GNOME 49. Scopri cosa significa per il tuo sistema Linux. #SolusLinux #Polaris #EpochBump #LinuxNews

https://www.linuxeasy.org/solus-nuova-epoca-repository-polaris-linux/?utm_source=mastodon&utm_medium=jetpack_social

"Solus is an unusually stable, unusually simple to use rolling release distribution. Everything is pretty straight forward, everything works (at the lower levels), everything installed and updated smoothly."
(But choose your desktop!)

a review of @Solus 4.7 and #Budgie 10.9 by @distrowatch: https://distrowatch.com/weekly.php?issue=20250310#solus

Solus origin: #Ireland
website location: California

#decoupling #nonAligned #alternatives #EuropeAlternatives #nonUS #distros #LinuxDistributions #desktop #FOSS #FLOSS #Linux #Solus #SolusDistribution #SolusLinux #Budgie #BudgieDesktop #rollingDistributions #rollingRelease

"Solus is an unusually stable, unusually simple to use rolling release distribution. Everything is pretty straight forward, everything works (at the lower levels), everything installed and updated smoothly."
(But choose your desktop!)

a review of @Solus 4.7 and #Budgie 10.9 by @distrowatch: https://distrowatch.com/weekly.php?issue=20250310#solus

Solus origin: #Ireland
website location: California

#decoupling #nonAligned #alternatives #EuropeAlternatives #nonUS #distros #LinuxDistributions #desktop #FOSS #FLOSS #Linux #Solus #SolusDistribution #SolusLinux #Budgie #BudgieDesktop #rollingDistributions #rollingRelease

"Solus is an unusually stable, unusually simple to use rolling release distribution. Everything is pretty straight forward, everything works (at the lower levels), everything installed and updated smoothly."
(But choose your desktop!)

a review of @Solus 4.7 and #Budgie 10.9 by @distrowatch: https://distrowatch.com/weekly.php?issue=20250310#solus

Solus origin: #Ireland
website location: California

#decoupling #nonAligned #alternatives #EuropeAlternatives #nonUS #distros #LinuxDistributions #desktop #FOSS #FLOSS #Linux #Solus #SolusDistribution #SolusLinux #Budgie #BudgieDesktop #rollingDistributions #rollingRelease

"Solus is an unusually stable, unusually simple to use rolling release distribution. Everything is pretty straight forward, everything works (at the lower levels), everything installed and updated smoothly."
(But choose your desktop!)

a review of @Solus 4.7 and #Budgie 10.9 by @distrowatch: https://distrowatch.com/weekly.php?issue=20250310#solus

Solus origin: #Ireland
website location: California

#decoupling #nonAligned #alternatives #EuropeAlternatives #nonUS #distros #LinuxDistributions #desktop #FOSS #FLOSS #Linux #Solus #SolusDistribution #SolusLinux #Budgie #BudgieDesktop #rollingDistributions #rollingRelease

"Solus is an unusually stable, unusually simple to use rolling release distribution. Everything is pretty straight forward, everything works (at the lower levels), everything installed and updated smoothly."
(But choose your desktop!)

a review of @Solus 4.7 and #Budgie 10.9 by @distrowatch: https://distrowatch.com/weekly.php?issue=20250310#solus

Solus origin: #Ireland
website location: California

#decoupling #nonAligned #alternatives #EuropeAlternatives #nonUS #distros #LinuxDistributions #desktop #FOSS #FLOSS #Linux #Solus #SolusDistribution #SolusLinux #Budgie #BudgieDesktop #rollingDistributions #rollingRelease

I could have sworn Solus Linux supported Secure Boot. Sadly, I get this error when trying to boot the USB. I can press "OK" and it brings me right back to my PCs UEFI menu. 😢

#Uefi #SecureBoot #Linux #Solus #SolusLinux

I could have sworn Solus Linux supported Secure Boot. Sadly, I get this error when trying to boot the USB. I can press "OK" and it brings me right back to my PCs UEFI menu. 😢

#Uefi #SecureBoot #Linux #Solus #SolusLinux

I could have sworn Solus Linux supported Secure Boot. Sadly, I get this error when trying to boot the USB. I can press "OK" and it brings me right back to my PCs UEFI menu. 😢

#Uefi #SecureBoot #Linux #Solus #SolusLinux

I could have sworn Solus Linux supported Secure Boot. Sadly, I get this error when trying to boot the USB. I can press "OK" and it brings me right back to my PCs UEFI menu. 😢

#Uefi #SecureBoot #Linux #Solus #SolusLinux

Whoa, Hybrid Sleep saved me from a power outage on my ThinkCentre M910q.

I came home to blinking clocks on my oven and microwave, and expected to see some journal replay stuff when I booted my little desktop, but it just jumped right back to the lock screen.

So nice! I don't recall ever having hibernate working properly on linux, before. :BlobCatDerpy:

#Solus #linux #SolusLinux

Whoa, Hybrid Sleep saved me from a power outage on my ThinkCentre M910q.

I came home to blinking clocks on my oven and microwave, and expected to see some journal replay stuff when I booted my little desktop, but it just jumped right back to the lock screen.

So nice! I don't recall ever having hibernate working properly on linux, before. :BlobCatDerpy:

#Solus #linux #SolusLinux

Whoa, Hybrid Sleep saved me from a power outage on my ThinkCentre M910q.

I came home to blinking clocks on my oven and microwave, and expected to see some journal replay stuff when I booted my little desktop, but it just jumped right back to the lock screen.

So nice! I don't recall ever having hibernate working properly on linux, before. :BlobCatDerpy:

#Solus #linux #SolusLinux

Whoa, Hybrid Sleep saved me from a power outage on my ThinkCentre M910q.

I came home to blinking clocks on my oven and microwave, and expected to see some journal replay stuff when I booted my little desktop, but it just jumped right back to the lock screen.

So nice! I don't recall ever having hibernate working properly on linux, before. :BlobCatDerpy:

#Solus #linux #SolusLinux

Whoa, Hybrid Sleep saved me from a power outage on my ThinkCentre M910q.

I came home to blinking clocks on my oven and microwave, and expected to see some journal replay stuff when I booted my little desktop, but it just jumped right back to the lock screen.

So nice! I don't recall ever having hibernate working properly on linux, before. :BlobCatDerpy:

#Solus #linux #SolusLinux

Just remembering something before I shuffle off to bed...

I'd like to write a "vrms" / "check-dfsg-status" - style script for #eopkg.

The idea is that it looks through your package repo and warns you if any packages are proprietary. It's quite easy to do on Debian, as it relies on whether or not any packages are from the Contrib or Non-Free repos. I wrote one for flatpak that looks at the license of each installed package, and searches for stuff like (GPL|MIT|BSD|etc...).

I also wrote one for #arch years and years ago, but found it was a futile effort, as hundreds of packages in the base install just had "custom" in the license field.

So far, it's looking quite promising:

$ eopkg info $(eopkg -N li |cut -f1 -d" ") |grep ^Licenses |cut -f2- -d: |tr , "\n" |sed 's/^[[:space:]]*//; s/[[:space:]]*$//' |grep -v "^$" |uniqsort
      2 Artistic-Perl-2.0
      2 Bitstream-Vera
      2 BSD-3-Clause-Attribution
      2 BSD-4-Clause
      2 CC-BY-4.0
      2 CC-BY-SA-3.0
      2 CC-PDDC
      2 CDDL-1.0
      2 Copyright
      2 CPL-1.0
      2 EPL-1.0
      2 EUPL-1.2
      2 GFDL-1.2
      2 GFDL-1.3
      2 GFDL-1.3-only
      2 gnuplot
      2 GPL-1.0-only
      2 GPL-1.0-or-later
      2 GPL-2.0-later
      2 GPL-2.0-only WITH Classpath-exception-2.0
      2 GPL-2.0-only WITH Linux-syscall-note
      2 JasPer-2.0
      2 LGPL-2.0
      2 LGPL-2.0-or-later WITH WxWindows-exception-3.1
      2 LGPL-3.0
      2 MPL-2.0-or-later
      2 PDDL-1.0
      2 PostgreSQL
      2 Rdisc
      2 Unlicense
      2 X11
      4 AGPL-3.0-only
      4 AOMPL-1.0
      4 BSD
      4 bzip2-1.0.6
      4 GFDL-1.1-or-later
      4 IJG
      4 Info-ZIP
      4 Libpng
      4 libtiff
      4 OLDAP-2.8
      4 Public-Domain
      4 WTFPL
      6 AGPL-3.0-or-later
      6 Artistic-2.0
      6 BSD-4-Clause-UC
      6 CC-BY-3.0
      6 EULA
      6 OpenSSL
      6 TCL
      8 GFDL-1.2-only
      8 HPND
      8 LGPL-2.1
      8 Python-2.0
      8 SGI-B-1.0
     10 0BSD
     10 BSL-1.0
     10 Distributable
     10 OFL-1.1
     12 CC-BY-SA-4.0
     12 GFDL-1.2-or-later
     14 GPL-3.0
     16 MPL-1.1
     18 GPL-2.0
     20 Apache-2.0 WITH LLVM-exception
     20 Zlib
     22 LGPL-3.0-only
     32 CC0-1.0
     32 ISC
     36 GPL-3.0-only
     38 Artistic-1.0-Perl
     56 GFDL-1.3-or-later
     56 MPL-2.0
     94 Apache-2.0
    110 LGPL-2.0-only
    112 BSD-2-Clause
    122 LGPL-3.0-or-later
    126 LGPL-2.1-only
    136 GPL-2.0-only
    214 LGPL-2.0-or-later
    232 GPL-3.0-or-later
    278 BSD-3-Clause
    416 LGPL-2.1-or-later
    442 MIT
    548 GPL-2.0-or-later

#Solus #SolusLinux

Just remembering something before I shuffle off to bed...

I'd like to write a "vrms" / "check-dfsg-status" - style script for #eopkg.

The idea is that it looks through your package repo and warns you if any packages are proprietary. It's quite easy to do on Debian, as it relies on whether or not any packages are from the Contrib or Non-Free repos. I wrote one for flatpak that looks at the license of each installed package, and searches for stuff like (GPL|MIT|BSD|etc...).

I also wrote one for #arch years and years ago, but found it was a futile effort, as hundreds of packages in the base install just had "custom" in the license field.

So far, it's looking quite promising:

$ eopkg info $(eopkg -N li |cut -f1 -d" ") |grep ^Licenses |cut -f2- -d: |tr , "\n" |sed 's/^[[:space:]]*//; s/[[:space:]]*$//' |grep -v "^$" |uniqsort
      2 Artistic-Perl-2.0
      2 Bitstream-Vera
      2 BSD-3-Clause-Attribution
      2 BSD-4-Clause
      2 CC-BY-4.0
      2 CC-BY-SA-3.0
      2 CC-PDDC
      2 CDDL-1.0
      2 Copyright
      2 CPL-1.0
      2 EPL-1.0
      2 EUPL-1.2
      2 GFDL-1.2
      2 GFDL-1.3
      2 GFDL-1.3-only
      2 gnuplot
      2 GPL-1.0-only
      2 GPL-1.0-or-later
      2 GPL-2.0-later
      2 GPL-2.0-only WITH Classpath-exception-2.0
      2 GPL-2.0-only WITH Linux-syscall-note
      2 JasPer-2.0
      2 LGPL-2.0
      2 LGPL-2.0-or-later WITH WxWindows-exception-3.1
      2 LGPL-3.0
      2 MPL-2.0-or-later
      2 PDDL-1.0
      2 PostgreSQL
      2 Rdisc
      2 Unlicense
      2 X11
      4 AGPL-3.0-only
      4 AOMPL-1.0
      4 BSD
      4 bzip2-1.0.6
      4 GFDL-1.1-or-later
      4 IJG
      4 Info-ZIP
      4 Libpng
      4 libtiff
      4 OLDAP-2.8
      4 Public-Domain
      4 WTFPL
      6 AGPL-3.0-or-later
      6 Artistic-2.0
      6 BSD-4-Clause-UC
      6 CC-BY-3.0
      6 EULA
      6 OpenSSL
      6 TCL
      8 GFDL-1.2-only
      8 HPND
      8 LGPL-2.1
      8 Python-2.0
      8 SGI-B-1.0
     10 0BSD
     10 BSL-1.0
     10 Distributable
     10 OFL-1.1
     12 CC-BY-SA-4.0
     12 GFDL-1.2-or-later
     14 GPL-3.0
     16 MPL-1.1
     18 GPL-2.0
     20 Apache-2.0 WITH LLVM-exception
     20 Zlib
     22 LGPL-3.0-only
     32 CC0-1.0
     32 ISC
     36 GPL-3.0-only
     38 Artistic-1.0-Perl
     56 GFDL-1.3-or-later
     56 MPL-2.0
     94 Apache-2.0
    110 LGPL-2.0-only
    112 BSD-2-Clause
    122 LGPL-3.0-or-later
    126 LGPL-2.1-only
    136 GPL-2.0-only
    214 LGPL-2.0-or-later
    232 GPL-3.0-or-later
    278 BSD-3-Clause
    416 LGPL-2.1-or-later
    442 MIT
    548 GPL-2.0-or-later

#Solus #SolusLinux

Just remembering something before I shuffle off to bed...

I'd like to write a "vrms" / "check-dfsg-status" - style script for #eopkg.

The idea is that it looks through your package repo and warns you if any packages are proprietary. It's quite easy to do on Debian, as it relies on whether or not any packages are from the Contrib or Non-Free repos. I wrote one for flatpak that looks at the license of each installed package, and searches for stuff like (GPL|MIT|BSD|etc...).

I also wrote one for #arch years and years ago, but found it was a futile effort, as hundreds of packages in the base install just had "custom" in the license field.

So far, it's looking quite promising:

$ eopkg info $(eopkg -N li |cut -f1 -d" ") |grep ^Licenses |cut -f2- -d: |tr , "\n" |sed 's/^[[:space:]]*//; s/[[:space:]]*$//' |grep -v "^$" |uniqsort
      2 Artistic-Perl-2.0
      2 Bitstream-Vera
      2 BSD-3-Clause-Attribution
      2 BSD-4-Clause
      2 CC-BY-4.0
      2 CC-BY-SA-3.0
      2 CC-PDDC
      2 CDDL-1.0
      2 Copyright
      2 CPL-1.0
      2 EPL-1.0
      2 EUPL-1.2
      2 GFDL-1.2
      2 GFDL-1.3
      2 GFDL-1.3-only
      2 gnuplot
      2 GPL-1.0-only
      2 GPL-1.0-or-later
      2 GPL-2.0-later
      2 GPL-2.0-only WITH Classpath-exception-2.0
      2 GPL-2.0-only WITH Linux-syscall-note
      2 JasPer-2.0
      2 LGPL-2.0
      2 LGPL-2.0-or-later WITH WxWindows-exception-3.1
      2 LGPL-3.0
      2 MPL-2.0-or-later
      2 PDDL-1.0
      2 PostgreSQL
      2 Rdisc
      2 Unlicense
      2 X11
      4 AGPL-3.0-only
      4 AOMPL-1.0
      4 BSD
      4 bzip2-1.0.6
      4 GFDL-1.1-or-later
      4 IJG
      4 Info-ZIP
      4 Libpng
      4 libtiff
      4 OLDAP-2.8
      4 Public-Domain
      4 WTFPL
      6 AGPL-3.0-or-later
      6 Artistic-2.0
      6 BSD-4-Clause-UC
      6 CC-BY-3.0
      6 EULA
      6 OpenSSL
      6 TCL
      8 GFDL-1.2-only
      8 HPND
      8 LGPL-2.1
      8 Python-2.0
      8 SGI-B-1.0
     10 0BSD
     10 BSL-1.0
     10 Distributable
     10 OFL-1.1
     12 CC-BY-SA-4.0
     12 GFDL-1.2-or-later
     14 GPL-3.0
     16 MPL-1.1
     18 GPL-2.0
     20 Apache-2.0 WITH LLVM-exception
     20 Zlib
     22 LGPL-3.0-only
     32 CC0-1.0
     32 ISC
     36 GPL-3.0-only
     38 Artistic-1.0-Perl
     56 GFDL-1.3-or-later
     56 MPL-2.0
     94 Apache-2.0
    110 LGPL-2.0-only
    112 BSD-2-Clause
    122 LGPL-3.0-or-later
    126 LGPL-2.1-only
    136 GPL-2.0-only
    214 LGPL-2.0-or-later
    232 GPL-3.0-or-later
    278 BSD-3-Clause
    416 LGPL-2.1-or-later
    442 MIT
    548 GPL-2.0-or-later

#Solus #SolusLinux

Just remembering something before I shuffle off to bed...

I'd like to write a "vrms" / "check-dfsg-status" - style script for #eopkg.

The idea is that it looks through your package repo and warns you if any packages are proprietary. It's quite easy to do on Debian, as it relies on whether or not any packages are from the Contrib or Non-Free repos. I wrote one for flatpak that looks at the license of each installed package, and searches for stuff like (GPL|MIT|BSD|etc...).

I also wrote one for #arch years and years ago, but found it was a futile effort, as hundreds of packages in the base install just had "custom" in the license field.

So far, it's looking quite promising:

$ eopkg info $(eopkg -N li |cut -f1 -d" ") |grep ^Licenses |cut -f2- -d: |tr , "\n" |sed 's/^[[:space:]]*//; s/[[:space:]]*$//' |grep -v "^$" |uniqsort
      2 Artistic-Perl-2.0
      2 Bitstream-Vera
      2 BSD-3-Clause-Attribution
      2 BSD-4-Clause
      2 CC-BY-4.0
      2 CC-BY-SA-3.0
      2 CC-PDDC
      2 CDDL-1.0
      2 Copyright
      2 CPL-1.0
      2 EPL-1.0
      2 EUPL-1.2
      2 GFDL-1.2
      2 GFDL-1.3
      2 GFDL-1.3-only
      2 gnuplot
      2 GPL-1.0-only
      2 GPL-1.0-or-later
      2 GPL-2.0-later
      2 GPL-2.0-only WITH Classpath-exception-2.0
      2 GPL-2.0-only WITH Linux-syscall-note
      2 JasPer-2.0
      2 LGPL-2.0
      2 LGPL-2.0-or-later WITH WxWindows-exception-3.1
      2 LGPL-3.0
      2 MPL-2.0-or-later
      2 PDDL-1.0
      2 PostgreSQL
      2 Rdisc
      2 Unlicense
      2 X11
      4 AGPL-3.0-only
      4 AOMPL-1.0
      4 BSD
      4 bzip2-1.0.6
      4 GFDL-1.1-or-later
      4 IJG
      4 Info-ZIP
      4 Libpng
      4 libtiff
      4 OLDAP-2.8
      4 Public-Domain
      4 WTFPL
      6 AGPL-3.0-or-later
      6 Artistic-2.0
      6 BSD-4-Clause-UC
      6 CC-BY-3.0
      6 EULA
      6 OpenSSL
      6 TCL
      8 GFDL-1.2-only
      8 HPND
      8 LGPL-2.1
      8 Python-2.0
      8 SGI-B-1.0
     10 0BSD
     10 BSL-1.0
     10 Distributable
     10 OFL-1.1
     12 CC-BY-SA-4.0
     12 GFDL-1.2-or-later
     14 GPL-3.0
     16 MPL-1.1
     18 GPL-2.0
     20 Apache-2.0 WITH LLVM-exception
     20 Zlib
     22 LGPL-3.0-only
     32 CC0-1.0
     32 ISC
     36 GPL-3.0-only
     38 Artistic-1.0-Perl
     56 GFDL-1.3-or-later
     56 MPL-2.0
     94 Apache-2.0
    110 LGPL-2.0-only
    112 BSD-2-Clause
    122 LGPL-3.0-or-later
    126 LGPL-2.1-only
    136 GPL-2.0-only
    214 LGPL-2.0-or-later
    232 GPL-3.0-or-later
    278 BSD-3-Clause
    416 LGPL-2.1-or-later
    442 MIT
    548 GPL-2.0-or-later

#Solus #SolusLinux

Just remembering something before I shuffle off to bed...

I'd like to write a "vrms" / "check-dfsg-status" - style script for #eopkg.

The idea is that it looks through your package repo and warns you if any packages are proprietary. It's quite easy to do on Debian, as it relies on whether or not any packages are from the Contrib or Non-Free repos. I wrote one for flatpak that looks at the license of each installed package, and searches for stuff like (GPL|MIT|BSD|etc...).

I also wrote one for #arch years and years ago, but found it was a futile effort, as hundreds of packages in the base install just had "custom" in the license field.

So far, it's looking quite promising:

$ eopkg info $(eopkg -N li |cut -f1 -d" ") |grep ^Licenses |cut -f2- -d: |tr , "\n" |sed 's/^[[:space:]]*//; s/[[:space:]]*$//' |grep -v "^$" |uniqsort
      2 Artistic-Perl-2.0
      2 Bitstream-Vera
      2 BSD-3-Clause-Attribution
      2 BSD-4-Clause
      2 CC-BY-4.0
      2 CC-BY-SA-3.0
      2 CC-PDDC
      2 CDDL-1.0
      2 Copyright
      2 CPL-1.0
      2 EPL-1.0
      2 EUPL-1.2
      2 GFDL-1.2
      2 GFDL-1.3
      2 GFDL-1.3-only
      2 gnuplot
      2 GPL-1.0-only
      2 GPL-1.0-or-later
      2 GPL-2.0-later
      2 GPL-2.0-only WITH Classpath-exception-2.0
      2 GPL-2.0-only WITH Linux-syscall-note
      2 JasPer-2.0
      2 LGPL-2.0
      2 LGPL-2.0-or-later WITH WxWindows-exception-3.1
      2 LGPL-3.0
      2 MPL-2.0-or-later
      2 PDDL-1.0
      2 PostgreSQL
      2 Rdisc
      2 Unlicense
      2 X11
      4 AGPL-3.0-only
      4 AOMPL-1.0
      4 BSD
      4 bzip2-1.0.6
      4 GFDL-1.1-or-later
      4 IJG
      4 Info-ZIP
      4 Libpng
      4 libtiff
      4 OLDAP-2.8
      4 Public-Domain
      4 WTFPL
      6 AGPL-3.0-or-later
      6 Artistic-2.0
      6 BSD-4-Clause-UC
      6 CC-BY-3.0
      6 EULA
      6 OpenSSL
      6 TCL
      8 GFDL-1.2-only
      8 HPND
      8 LGPL-2.1
      8 Python-2.0
      8 SGI-B-1.0
     10 0BSD
     10 BSL-1.0
     10 Distributable
     10 OFL-1.1
     12 CC-BY-SA-4.0
     12 GFDL-1.2-or-later
     14 GPL-3.0
     16 MPL-1.1
     18 GPL-2.0
     20 Apache-2.0 WITH LLVM-exception
     20 Zlib
     22 LGPL-3.0-only
     32 CC0-1.0
     32 ISC
     36 GPL-3.0-only
     38 Artistic-1.0-Perl
     56 GFDL-1.3-or-later
     56 MPL-2.0
     94 Apache-2.0
    110 LGPL-2.0-only
    112 BSD-2-Clause
    122 LGPL-3.0-or-later
    126 LGPL-2.1-only
    136 GPL-2.0-only
    214 LGPL-2.0-or-later
    232 GPL-3.0-or-later
    278 BSD-3-Clause
    416 LGPL-2.1-or-later
    442 MIT
    548 GPL-2.0-or-later

#Solus #SolusLinux

Happy to report that I've added support for #SolusLinux' #eopkg to all of my little package utilities: https://codeberg.org/rldane/scripts/commit/73d34d376cabf5d209f85ca8eafaef92395cb5e0

cc @solusspider

#Solus

Happy to report that I've added support for #SolusLinux' #eopkg to all of my little package utilities: https://codeberg.org/rldane/scripts/commit/73d34d376cabf5d209f85ca8eafaef92395cb5e0

cc @solusspider

#Solus

Happy to report that I've added support for #SolusLinux' #eopkg to all of my little package utilities: https://codeberg.org/rldane/scripts/commit/73d34d376cabf5d209f85ca8eafaef92395cb5e0

cc @solusspider

#Solus

Happy to report that I've added support for #SolusLinux' #eopkg to all of my little package utilities: https://codeberg.org/rldane/scripts/commit/73d34d376cabf5d209f85ca8eafaef92395cb5e0

cc @solusspider

#Solus

Happy to report that I've added support for #SolusLinux' #eopkg to all of my little package utilities: https://codeberg.org/rldane/scripts/commit/73d34d376cabf5d209f85ca8eafaef92395cb5e0

cc @solusspider

#Solus

Ok, this is crazy weird...

I deleted my ~/.config/syncthing folder and started syncthing again to re-set it up from scratch, and everything was back! My config, my folders, everything!!

I looked in ~/.config/, and no syncthing!

I did a find, and the config folder is in ~/.local/state/syncthing!!

Has anyone heard of ~/.local/state/? Is that a #Solus thing?
I'd never encountered it before.

Phew!!

#SolusLinux

Ok, this is crazy weird...

I deleted my ~/.config/syncthing folder and started syncthing again to re-set it up from scratch, and everything was back! My config, my folders, everything!!

I looked in ~/.config/, and no syncthing!

I did a find, and the config folder is in ~/.local/state/syncthing!!

Has anyone heard of ~/.local/state/? Is that a #Solus thing?
I'd never encountered it before.

Phew!!

#SolusLinux

Ok, this is crazy weird...

I deleted my ~/.config/syncthing folder and started syncthing again to re-set it up from scratch, and everything was back! My config, my folders, everything!!

I looked in ~/.config/, and no syncthing!

I did a find, and the config folder is in ~/.local/state/syncthing!!

Has anyone heard of ~/.local/state/? Is that a #Solus thing?
I'd never encountered it before.

Phew!!

#SolusLinux

Ok, this is crazy weird...

I deleted my ~/.config/syncthing folder and started syncthing again to re-set it up from scratch, and everything was back! My config, my folders, everything!!

I looked in ~/.config/, and no syncthing!

I did a find, and the config folder is in ~/.local/state/syncthing!!

Has anyone heard of ~/.local/state/? Is that a #Solus thing?
I'd never encountered it before.

Phew!!

#SolusLinux

Ok, this is crazy weird...

I deleted my ~/.config/syncthing folder and started syncthing again to re-set it up from scratch, and everything was back! My config, my folders, everything!!

I looked in ~/.config/, and no syncthing!

I did a find, and the config folder is in ~/.local/state/syncthing!!

Has anyone heard of ~/.local/state/? Is that a #Solus thing?
I'd never encountered it before.

Phew!!

#SolusLinux

#HelloWorld

First #toot from #Solus!

#SolusLinux

#HelloWorld

First #toot from #Solus!

#SolusLinux

#HelloWorld

First #toot from #Solus!

#SolusLinux

#HelloWorld

First #toot from #Solus!

#SolusLinux

#HelloWorld

First #toot from #Solus!

#SolusLinux

I really want to like #SolusLinux, as there's not a lot of good semi-rolling-release distros, but the fact that /usr/bin/python is symlinked to python2 gives me mega heebie-jeebies.

Guys, I don't mean to be rude. It's a wonderful distro made by wonderful people.

But PYTHON TWO? In 2025? That's a security jump-scare!

:BlobCatBlankieScared: :BlobFoxScared:

#solus #infosec #python

I really want to like #SolusLinux, as there's not a lot of good semi-rolling-release distros, but the fact that /usr/bin/python is symlinked to python2 gives me mega heebie-jeebies.

Guys, I don't mean to be rude. It's a wonderful distro made by wonderful people.

But PYTHON TWO? In 2025? That's a security jump-scare!

:BlobCatBlankieScared: :BlobFoxScared:

#solus #infosec #python

I really want to like #SolusLinux, as there's not a lot of good semi-rolling-release distros, but the fact that /usr/bin/python is symlinked to python2 gives me mega heebie-jeebies.

Guys, I don't mean to be rude. It's a wonderful distro made by wonderful people.

But PYTHON TWO? In 2025? That's a security jump-scare!

:BlobCatBlankieScared: :BlobFoxScared:

#solus #infosec #python

I really want to like #SolusLinux, as there's not a lot of good semi-rolling-release distros, but the fact that /usr/bin/python is symlinked to python2 gives me mega heebie-jeebies.

Guys, I don't mean to be rude. It's a wonderful distro made by wonderful people.

But PYTHON TWO? In 2025? That's a security jump-scare!

:BlobCatBlankieScared: :BlobFoxScared:

#solus #infosec #python

I really want to like #SolusLinux, as there's not a lot of good semi-rolling-release distros, but the fact that /usr/bin/python is symlinked to python2 gives me mega heebie-jeebies.

Guys, I don't mean to be rude. It's a wonderful distro made by wonderful people.

But PYTHON TWO? In 2025? That's a security jump-scare!

:BlobCatBlankieScared: :BlobFoxScared:

#solus #infosec #python

@solusspider

I was running my RasPi "server" on an SSD connected to a USB3-to-SATA adapter, but I wanted to transfer it over to a USB 3 SSD so I could put the SATA SSD in my ThinkCentre. I don't know how I lucked out, but the two SSDs are the same size down to the BYTE.

I dd'ed the data from the SATA SSD to the USB3 SSD overnight, plugged the USB3 SSD into my rPi, and boom, it booted and everything's fine there.

Put the SATA SSD into the ThinkCentre (man, that plastic drive cage/carrier/rail was terrible! XD) and formatted with KDE Partition Manager.

Total panic on boot; it didn't know how to prompt for a password to the SSD, which was set to be /home.

Did some "ducking" around just now, and I know how to add a keyfile, so I should be able to get it running tonight with the 1TB SSD as my /home and the NVME as /.

So far, so good!

Looking forward to getting my package scripts working with eopkg. The syntax is pretty nice and obvious, way easier than Arch's pacman or the various disparate pkg_ utilities in OpenBSD.

#Solus #SolusLinux

@solusspider

I was running my RasPi "server" on an SSD connected to a USB3-to-SATA adapter, but I wanted to transfer it over to a USB 3 SSD so I could put the SATA SSD in my ThinkCentre. I don't know how I lucked out, but the two SSDs are the same size down to the BYTE.

I dd'ed the data from the SATA SSD to the USB3 SSD overnight, plugged the USB3 SSD into my rPi, and boom, it booted and everything's fine there.

Put the SATA SSD into the ThinkCentre (man, that plastic drive cage/carrier/rail was terrible! XD) and formatted with KDE Partition Manager.

Total panic on boot; it didn't know how to prompt for a password to the SSD, which was set to be /home.

Did some "ducking" around just now, and I know how to add a keyfile, so I should be able to get it running tonight with the 1TB SSD as my /home and the NVME as /.

So far, so good!

Looking forward to getting my package scripts working with eopkg. The syntax is pretty nice and obvious, way easier than Arch's pacman or the various disparate pkg_ utilities in OpenBSD.

#Solus #SolusLinux

@solusspider

I was running my RasPi "server" on an SSD connected to a USB3-to-SATA adapter, but I wanted to transfer it over to a USB 3 SSD so I could put the SATA SSD in my ThinkCentre. I don't know how I lucked out, but the two SSDs are the same size down to the BYTE.

I dd'ed the data from the SATA SSD to the USB3 SSD overnight, plugged the USB3 SSD into my rPi, and boom, it booted and everything's fine there.

Put the SATA SSD into the ThinkCentre (man, that plastic drive cage/carrier/rail was terrible! XD) and formatted with KDE Partition Manager.

Total panic on boot; it didn't know how to prompt for a password to the SSD, which was set to be /home.

Did some "ducking" around just now, and I know how to add a keyfile, so I should be able to get it running tonight with the 1TB SSD as my /home and the NVME as /.

So far, so good!

Looking forward to getting my package scripts working with eopkg. The syntax is pretty nice and obvious, way easier than Arch's pacman or the various disparate pkg_ utilities in OpenBSD.

#Solus #SolusLinux

@solusspider

I was running my RasPi "server" on an SSD connected to a USB3-to-SATA adapter, but I wanted to transfer it over to a USB 3 SSD so I could put the SATA SSD in my ThinkCentre. I don't know how I lucked out, but the two SSDs are the same size down to the BYTE.

I dd'ed the data from the SATA SSD to the USB3 SSD overnight, plugged the USB3 SSD into my rPi, and boom, it booted and everything's fine there.

Put the SATA SSD into the ThinkCentre (man, that plastic drive cage/carrier/rail was terrible! XD) and formatted with KDE Partition Manager.

Total panic on boot; it didn't know how to prompt for a password to the SSD, which was set to be /home.

Did some "ducking" around just now, and I know how to add a keyfile, so I should be able to get it running tonight with the 1TB SSD as my /home and the NVME as /.

So far, so good!

Looking forward to getting my package scripts working with eopkg. The syntax is pretty nice and obvious, way easier than Arch's pacman or the various disparate pkg_ utilities in OpenBSD.

#Solus #SolusLinux

@solusspider

I was running my RasPi "server" on an SSD connected to a USB3-to-SATA adapter, but I wanted to transfer it over to a USB 3 SSD so I could put the SATA SSD in my ThinkCentre. I don't know how I lucked out, but the two SSDs are the same size down to the BYTE.

I dd'ed the data from the SATA SSD to the USB3 SSD overnight, plugged the USB3 SSD into my rPi, and boom, it booted and everything's fine there.

Put the SATA SSD into the ThinkCentre (man, that plastic drive cage/carrier/rail was terrible! XD) and formatted with KDE Partition Manager.

Total panic on boot; it didn't know how to prompt for a password to the SSD, which was set to be /home.

Did some "ducking" around just now, and I know how to add a keyfile, so I should be able to get it running tonight with the 1TB SSD as my /home and the NVME as /.

So far, so good!

Looking forward to getting my package scripts working with eopkg. The syntax is pretty nice and obvious, way easier than Arch's pacman or the various disparate pkg_ utilities in OpenBSD.

#Solus #SolusLinux

me mude a #soluslinux gente les cuento mi experiencia:

bonita distro,esta infravalorada,e pedido ayuda y e preguntado cosas sobre la distro en el foro de solus y muchos me respondieron de una manera muy amable,no se burlaron de mi por no saber nada o similares.

en cuanto a uso se resume en:
rapida
estable
sus repos tienen lo esencial
budgie desktop es hermoso y se siente bastante practico.

la recomendaria?
SIIIIIIII

me mude a #soluslinux gente les cuento mi experiencia:

bonita distro,esta infravalorada,e pedido ayuda y e preguntado cosas sobre la distro en el foro de solus y muchos me respondieron de una manera muy amable,no se burlaron de mi por no saber nada o similares.

en cuanto a uso se resume en:
rapida
estable
sus repos tienen lo esencial
budgie desktop es hermoso y se siente bastante practico.

la recomendaria?
SIIIIIIII