jamesbunagna

joined 2 weeks ago
[–] [email protected] 1 points 9 minutes ago

That was a great read. Wonderfully detailed. Thank you!

It's a pity that it went down like that. Would you say that a properly matured openSUSE Kalpa would be your perfect setup? Out of curiosity, have you used projects related to Fedora Atomic for long periods of time? If so, how would you compare them?

[–] [email protected] 1 points 6 hours ago

I'm glad to find that the general perception on CachyOS has definitely changed for the better. I believe it was two or three years ago when I stumbled upon CachyOS for the very first time. I don't think it did anything noticeably different back then compared to now. But as it was still relatively new, people didn't quite jump on the bandwagon. As such, I actually received quite a bit of condemnation whenever I tried to recommend the distro to others. I'm glad to see that it's currently flourishing. Congratz to the CachyOS team for sticking to their guns. Whenever a product is good, it will eventually receive recognition.

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

I put it on my partners computer after Aeon crapped itself and put the system in a boot loop until I switched the hard disk out.

It is only release candidate software. As such, I didn't have high expectations. However what you've described here is pretty troublesome. And I'd imagine your partner didn't do crazy stuff that would justify such a reaction by the OS.

I'm personally very interested in the future of openSUSE Aeon. So far, I've mostly seen positive reactions. Therefore, a negative experience as such really piques my interest. If possible, could you elaborate upon what had transpired before the system broke? Or perhaps your partners personal experience with the distro in hindsight.

[–] [email protected] 1 points 16 hours ago

Try invoking ujust distrobox-assemble first. This command is also found on the FAQ page. Enter the container created through this method.

[–] [email protected] 1 points 20 hours ago

FYI, the userns images have been (or are about to be) deprecated.

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

Under the USERNS caption of the FAQ , there's a link to another entry. In there, you may find the following command: ujust toggle-container-domain-userns-creation. After invoking this, distrobox should at least start working.

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

Do you use GNOME?

Yes, I do! I personally prefer GNOME over other DEs anyways, so I'm absolutely fine with that.

They disable GNOME extensions. Did you turn it back on?

They disable the installation of GNOME extensions by users. But, system-wide GNOME extensions are enabled by default. So, GNOME extensions that are found in Fedora's repositories can be installed right out of the box. Thankfully, all my extension needs are taken care of within the extensions found in Fedora's repositories. So, this doesn't constitute a limitation for me. Curiously, I've actually installed extensions through this method ever since I recognized how the other way wasn't remotely as secure. So this (relatively recent) change by secureblue to enforce it upon everyone (at least by default) came as a pleasant surprise.

Did you re-enable XWayland?

Nope. I initially had troubles with playing games through Wine. But I've learned how to use gamescope for that instead. Currently, I'm honestly unaware of anything I'd need XWayland for. Wayland development has definitely come a long way. And while I'm sure some systems and/or workflows don't play nice with it yet, for myself (pure) Wayland is all I need.

Do you use bubblejail?

Currently, I don't think I've got any use for it:

  • The only layered packages are the aforementioned GNOME extensions. I'm unaware if bubblejail can be used to sandbox these. But I'll look into it. Thanks for bringing this up!
  • My GUI apps are taken care of by Flatpak. Which, AFAIK, utilizes bubblewrap already for its sandboxing.
  • My CLI apps are taken care of by Linuxbrew. Perhaps these can be sandboxed using bubblejail, but I wouldn't even know. Thanks for reminding me of this (potential) blindspot!
[–] [email protected] 2 points 1 day ago

Also, I’ve heard about the dev(s) and community being a bit toxic, or at least not being a pleasure to collaborate with. But I can’t verify that.

FWIW, this hasn't been my own experience. If anything, it may give of some "know-better"-vibes like one might recognize from engaging with some of GrapheneOS' community members.

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

Does anybody in this sub using Fedora Secureblue?

I do. And have done so for almost a year now.

What is your opinion?

It's pretty neat. Though, don't expect to roll your way in without any troubles if you don't take the effort to read its documentation. Fedora Atomic already does things its own way. However, secureblue, by virtue of its superior security standard, adds its own set of 'rules' that one should abide. Personally, I absolutely love how this is enforced. But I can understand why it might be a bit overwhelming for those new on the block. But I have personally helped introduce relative newbs to secureblue and they managed (with some help). So you should be fine; their community on Discord also has been pretty helpful in my experience.

So, if your first priority for your desktop operating system is for it to be Linux-based and your second priority is that it's properly hardened, then you simply can't go wrong with secureblue.

I was about to write a long piece comparing different security-focused systems, but I retracted for the sake of brevity. Please feel free to ask a specific comparison if you will.

[–] [email protected] 3 points 1 week ago

I'll keep it relatively brief for fearing unwieldiness.

I’m really not a fan of the “we can’t do anything so let’s sit and wait until everything gets worse” philosophy.

I agree. I hope you're not implying I'm stating otherwise.

but it was accepted because it was the best thing available at the time for the purpose

More like Red Hat pushed it as the new standard and the rest followed suit. Distro maintainers are pragmatic and reasonable people. They'll more often than not go for the path of least resistance.

A clear cut example of this would be how most distros don't opt for btrfs in combination with time shift or snapper for snapshot functionality. So clearly, they are not really trying to offer the best solution. Instead they just try to push a system that's as easy as they come for them to maintain and act accordingly.

the community needed a standard

And we already had one: SysVinit. Don't try to rewrite history.


I initially started writing a reply on the remaining text but noticed that my writings were continued to be misunderstood. Therefore, I decided to retract any further reply and will choose to stop engaging in this conversation. Thank you for the engagement. However, I would like to offer a small piece of advice as a fellow Lemmy user:

In future conversations, whether they are debates or discussions, please try to understand what the other person is saying. Avoid creating a straw man argument. If needed, ask for clarifications to ensure you fully grasp their point. If you continue to have difficulty understanding, consider alternative approaches to gain a better understanding.

I don't know how this conversation deteriorated, but I'll let it be. Thank you once more. For the record, I don't think this conversation will be productive moving forward. You seem to be focused on your own points without trying to understand the other side, which is fine. You don't have to try to understand me; I may not be important. However, the ideas I try to convey might be, and it's more important to consider and understand those.

Anyhow, I wish you the best.

[–] [email protected] 1 points 1 week ago* (last edited 1 week ago) (2 children)

I think I better understand you now. Btw, I had changed my previous reply moments before I read your reply. My bad*.

I meant that I support this distro as long as it’s not immutable because I’m an opponent of immutability on the desktop. If they’re also making other kinds of systems, immutability may be beneficial there.

Have you been around since before the introduction of systemd? Systemd's introduction was a lot more invasive and threatening to 'traditional' distros than immutables are today. Distros changed to systemd over night. Only Arch and Debian had communities that succeeded in establishing systemd-less derivatives. By contrast, the interest for immutability in existing distros (almost always) means a parallel distro is created with (at least initially) immutability tacked on.

So, please correct me if I'm wrong, but I feel as if you're being too aggressive/overreactive considering how nonthreatening immutable desktops are to traditional distros.

Sometimes ~~innovation~~ change is bad or rushed (such as removal of X11 on Fedora).

Fixed that for you 😉.

Often only people with the newest hardware can benefit from it anyways.

Fair, but as unfortunate as it is, that's basically a consequence of consumerism. I don't like it, don't get me wrong.

They don’t care about regular users making the products worse for them which is basically egoism.

I don't think this applies to Linux overall. Fedora (and Red Hat by extension) have a vision that made them default to Wayland by default. So you'd be right to blame their policy. But this is nothing new for Fedora; they're known to push bold changes. You might not like it or disagree with them. Fine. But is it important enough to hate them for it? Isn't life too short for that?

There is a reason for proprietary products having legacy support after all.

Are you implying that doesn't apply to Linux? I don't understand. On an open system like Linux is, this doesn't really seem to hold much weight. You can swap stuff around as you see fit.

[–] [email protected] 9 points 1 week ago* (last edited 1 week ago) (4 children)

They claim to have a lot of features.

What features are you referring to?

As I understand it, it's basically trying to answer the following question: What if we could start over and use existing building blocks to make a simple yet complete system using the Linux kernel? All changes have been made in accordance to that basic premise. From replacing GNU in GNU/Linux with BSD, to choosing dinit over systemd as init system.

I hope they succeed (as long as it’s not immutable)

Are you one of those with a raging hateboner towards everything immutable? I ask this as I don't see any reason to bring this up in the first place.

FWIW, I absolutely hope for it to succeed as well. Innovation (of any kind) pushes the industry forward. When people oppose innovation for whatever reason, it always reminds me of Henry Ford's famous quote: "If I had asked people what they wanted, they would have said faster horses."

 

Hey folks! After using Fedora Atomic for quite a while and really appreciating its approach, I've been eyeing one particular feature from NixOS: its congruent system management. Inspired from Graham Christensen's "Erase your darlings" post, I'd like to explore implementing something similar to NixOS' impermanence module on Fedora Atomic as one step towards better state management.

Why not just switch to NixOS? Well, while NixOS's package management and declarative approach are incredible, I specifically value Fedora's stringent package vetting and security practices. The nixpkgs repository, despite its impressive scope, operates more like a user repository in terms of security standards.

I've already made some progress with the following:

  • Fedora Atomic's shift to bootable OCI containers has helped with base system reproducibility when one creates their own images. This process has thankfully been streamlined by templates offered by either uBlue or BlueBuild
  • Using chezmoi for dotfiles (would've loved home-manager if it played nicer with SELinux)

My current (most likely naive and perhaps even wrong) approach involves tmpfs mounts and bind mounts to /persist, along with systemd-tmpfiles. I'm well aware this won't give me the declarative goodness of NixOS, nor will it make the system truly stateless - there's surely plenty of state I'm missing - but I'm hoping it might be another step in the right direction.

Particularly interested in:

  • Best practices for managing persistent vs temporary state
  • Working with rpm-ostree's (or bootc') assumptions
  • Tools or scripts that might help
  • Alternative approaches that achieve similar goals

Thanks in advance!

view more: next ›