lancalot

joined 2 weeks ago
[–] [email protected] 3 points 2 hours ago

Thank you for the clarification 😊!

[–] [email protected] 2 points 11 hours ago (2 children)

I tried to find sources on that but failed. Could you help me out?

[–] [email protected] 2 points 18 hours ago* (last edited 17 hours ago)

The .deb package can be found on Github.

~~I find it peculiar that it doesn't seem to be packaged by any distro. Debian does have a package called level-zero. But, while they're linked, it doesn't seem to be the exact same thing.~~

Edit: It's packaged under intel-compute-runtime.

[–] [email protected] 1 points 1 day ago* (last edited 1 day ago)

Thank you for the reply! And apologies for the late response*.


First of all, I owe you another apology for the deleted comment; I was still in the process of cooking and accidentally sent the undercooked message.

They will get a little more respect from me when they stop trying to target programmers and gamers. Because of course everyone uses Steam and VScode.

As per its README (I'm paraphrasing):

Bazzite started as a project to resolve some of the issues that plague SteamOS:

  • Mainly out of date packages (despite an Arch base).
  • The lack of a functional package manager.
  • Issues pertaining to persistence of installed software across updates. (Reinstalling that obscure VPN software you spent an hour trying to get working in SteamOS isn't fun.)
  • No easy full disk encryption OOTB.
  • No Secure Boot support.

Like, SteamOS is a pretty cool operating system that allows both Linux enthusiasts and Linux newbs to enjoy playing (most of) their favorite games on Linux. But the former may find it too restrictive, while the latter may want to import that experience over to other devices. Bazzite aims to be that solution. Were it not for the success of the Steam Deck (and by extension SteamOS), such pressing need wouldn't even have arisen. So Bazzite isn't trying to target gamers as "an easy way to attract users" (or whatever the insinuation may be); its raison d'être is to address SteamOS' limitations.

Regarding the targeting of programmers, you could be right on that. But I suppose it's fine as VS Code's inclusion (and other goodies) is only confined to the respective -dx images. I regard Bluefin (and Aurora; its KDE Plasma spin-off) as the opinionated distro its maintainers like to use for themselves (i.e. programmers). I'd argue this actually makes it suitable for most people. But your average Linux user is a lot more sensitive towards 'bloat'. So it's definitely not for everyone.

It just feels very much like it is being run by young edgy programmers.

I guess my reply would be that I simply don't feel that way. And factually, it's being worked on by people that work (or have worked) at places like Canonical, Red Hat and (even) Microsoft. So, while that doesn't necessarily dismiss them as being "young edgy", it does make it easy to trust and be confident in their proficiency and competence. I wonder what other distros are maintained by such a star ensemble.

It is the same group that is trying to force crappy “dark mode” everywhere.

This is probably some meme or meta joke/reference I didn't get. Please feel free to enlighten me.

What’s the bigger program is the lack of internet knowledge about how to fix problems. With Ubuntu and Debian there are tons of stack overflow pages on all of the various issues. Sure things have changed over time but it still the most documented distro. I can look up “how do I fix X Linux Mint” and I will get an answer. With the Bazzite immutable base almost all of the help online will be useless.

I admitted to as such in my first comment. But, what if, instead of looking up questions in your favorite search engine, you visit their support channels and get the exact answer within a couple of moments? This last bit has been based on my own experience*.

Immutable Linux requires that you understand Linux under the hood.

Instinctively, I just absolutely have to disagree on this. The most clear-cut counterexample would be how NixOS -the granddaddy of ~~immutable~~ atomic distros if you will- doesn't adhere to many Linux conventions (including FHS). Therefore, "understanding (traditional) Linux under the hood" might have even been detrimental and wasteful for the many things you'd have to unlearn.

Beyond the overlap in Linux 101 that most distros adhere to and/or the basics everyone should know about their operating system, could you please demonstrate how "understanding (traditional) Linux under the hood" becomes necessary with atomic distributions?

[–] [email protected] 11 points 2 days ago (1 children)

Maybe PikaOS?

But, IIRC, they are not innovative like CachyOS is; CachyOS actually tries to push performance enhancements forward. PikaOS, on the other hand, only implements the improvements found by others (like CachyOS).

[–] [email protected] 2 points 3 days ago (3 children)

Don’t go straight to immutable Linux.

My first foray into Linux was through what you'd refer to as immutable Linux; shortly after the release of Fedora Kinoite. I'm literally the embodiment of the antithesis to your statement.

It is very new

This is factually true. So I can't simply deny that. But being more precise is helpful:

and I don’t like the focus.

Could you be more elaborate 😜?

[–] [email protected] 5 points 3 days ago* (last edited 3 days ago) (5 children)

First step: Decide on the so-called desktop environment. A shortlist is provided below. For a new user, this should be decisive when choosing between beginner-friendly distros.


Before going over to the next (and final) step, we need to set the stage for our contenders:

  • Versions of Linux Mint. Linux Mint has (rightfully so) become the face of Linux for beginners. Stand out feature would be how crazy popular it is; it's a joy to look up your problem through a search engine and find solutions for it.
  • Images of uBlue. Where Linux Mint tries to smooth the rough edges of the "traditional Linux model" as nicely as possible, uBlue's images can be referred to as revolutionary by comparison. The model strikes some (re)semblance to what you might know from your phone or chromebook. These images aren't even close to reaching their full potential, but have already garnered/amassed a wide audience for how they (at least attempt to) solve some of Desktop Linux' long-standing issues. Note that finding solutions for your problems might not be as straightforward. However, documentation is decent and they've been very helpful on Discord.

Final step: Pick the distro corresponding to your preferred desktop environment. The list found below (ordered alphabetically) isn't trying to be exhaustive on desktop environments.

[–] [email protected] 30 points 3 days ago (17 children)

Check out the random button on Distrowatch (distrowatch.com/random.php) - it's like a Linux lottery, but you always win something weird!

[–] [email protected] 2 points 5 days ago

Great response! Much appreciated!

[–] [email protected] 2 points 5 days ago (2 children)

Interesting. Have you also tried openSUSE Aeon(/Kalpa)? Though I assume you're a KDE user and thus waiting for Kalpa to become mature before a test ride.

Could you elaborate on what you didn't like about Aurora and Bazzite; especially about how that experience made you more appreciative of openSUSE?

Thank you in advance!

[–] [email protected] 2 points 5 days ago

What distro do you use

I daily drive secureblue.

and why?

Long story short; I love me some security. Unfortunately, My device is far from ideal for running Qubes OS. From within the remaining options, secureblue comes out on top for me.

 

Greetings fellow privacy enthusiasts!

I'm searching for a privacy-respecting media box that can run Android apps. The streaming device market features options like Shield TV, Chromecast and various Amlogic boxes. However, finding one that truly embraces FOSS principles while meeting essential needs has proven challenging.

Essential requirements:

  • Android app compatibility - specifically need to run certain apps
  • Strong privacy and security features
  • Reliable, long-term software support (I've grown weary of devices becoming obsolete within 2-3 years)
  • Budget-conscious: Aiming for under 150€, though I'm willing to invest appropriately for the right solution
  • Willing to invest significant time in initial setup, but afterwards it should "just work" with minimal maintenance
  • Timely and automatic security updates (ideally close to upstream releases)

My initial research suggests two potential approaches, though I'm not entirely certain about all implications:

  1. Mainstream devices (like Nvidia Shield) that can be degoogled through ADB commands
  2. Devices that are officially supported by LineageOS

While both paths seem promising, each raises certain concerns. For instance, degoogling might require ongoing maintenance, and running LineageOS could mean losing some device-specific functionality (as is the case with Shield).

The Raspberry Pi, with its open-source foundation and community-driven LineageOS development, seems interesting, though the lack of institutional backing raises some concerns about long-term reliability.

I'm still learning about the security implications of these choices. While I understand that phones running LineageOS don't match GrapheneOS's security standards, I'm uncertain how these considerations translate to a media box environment.

I'm open to exploring:

  • Custom firmware solutions
  • Alternative hardware platforms
  • Creative, FOSS-friendly approaches that preserve privacy while maintaining Android compatibility

Has anyone in the community successfully navigated these choices? Your experiences and insights would be invaluable, particularly regarding long-term viability and security considerations.

view more: next ›