0 Followers
0 Following
1 Posts
Yo! Apologies for the spam. I just wanted you to know that I appreciated this interaction and adore your enthusiasm towards Manjaro. Wish ya tha best. Bye!

As others have stated, reviving them through Linux should be a piece of cake.

However, how many is “a tonne”? This is important information for the community to provide recommendations on administrating those systems.

Do you use it?

Nope.

What are your problems with it?

If you meant problems from usage; none, as I’m not using Manjaro.

Besides, I don’t need to use Manjaro to state the problems some of its users have experienced.

Btw, I’ve read your comment(s) under this post in which you clearly outline your thoughts on Manjarno. My only question at this point would be why you or whosoever haven’t voiced this to Manjarno’s maintainer? One of Manjaro’s contributors has opened issues in Manjarno and it has gone as you’d expect; i.e. the truth prevailed and Manjarno changed some of its content. Instead of throwing a tantrum at random users on Linux, perhaps consider having a dialogue with Manjarno’s maintainer. You’d at least be more productive.

So you’re really butthurt, eh 😂. Don’t worry; I won’t initiate any further contact. Consider growing up though. Cheers.

Last year, this piece was written on it. And, based on an extremely small sample size (N=1), the takeaway was basically that the 1% lows (and the 0.1% lows) do seem to benefit on some games.

But, there are so many factors at play, it’s pretty hard to back up any claim of performance increase (or decrease). However, if you’ve got the time and you want to play around, then please feel free to benchmark the 1% lows (and 0.1% lows) on different distros and come to your own conclusions.

Linux-Kernel Optimierung für Gaming - Custom Kernel

Der Kernel ist das Herzstück eines jeden Betriebssystems. Was, wenn wir den Kernel an unsere speziellen Bedürfnisse anpassen könnten? Genau das ist die Idee hinter einem Custom Kernel. Und heute kompilieren wir einen eigenen!

John Dekka Tech - Linux, Tech-News, Gaming und Tutorials
Small nitpick; layering is technically only a thing on Fedora Atomic. Not all immutable distros subscribe to it.

First of all, I’d like to apologize if I misunderstood the situation. Communication only through text can be hard. And, in retrospect, I agree with you that I should have been more careful with my writing.

Secondly, please dismiss my last two replies. Especially the first is atrocious, while the second one was written under time pressure. Something that I should have not done to my fellow human being.

Thirdly, you’ve had another conversation with another user under this post. And I got most of what I wanted to get out of this conversation from that one already. And, I’d have to agree that that person was a lot more punctual and eloquent when wording their views. Thus, I understand why my writings might have felt as a downgrade by comparison.

Fourthly, thank you for your time. I appreciate it. And I wish you a great day.

Fifthly, there’s actually one thing that I really want to know 😅. But, I’ll not bring it up, unless you allow me.

Cheers.

I’m glad to be proven wrong.

Thank you for being more optimistic than I am.

😅. Alright, I’ll digest it for ya.

You said: “If rolling release causes the system to implode, doesn’t that make arch more user friendly?”

Which, if I’ll have to guess, is what you understand from the following sentences of mine:

  • “But, did I understand you correctly, that you hint towards the curious observation that rolling distros in general are technically ‘immortal’ while point-release distros eventually implode on themselves?”
  • “The inevitable implosion happens once every two years at worst.”

Which, are the only two instances I used the word. And, in both instances, it is pretty clear that I meant. I even just checked this with a LLM and it agrees with me on this.

However, the question you posed (i.e. “If rolling release causes the system to implode, doesn’t that make arch more user friendly?”) has many faults within it:

  • Like, if rolling release cause a system to implode (which I never said nor implied), then, because an implosion is clearly undesirable and thus not user friendly, Arch (as a rolling release distro) would also have been less user friendly (not more user friendly*).

So, what did you actually try to convey with that sentence? Did you make a mistake while formulating it? If so, what did you actually intend to say/ask?

Regarding me quoting myself; it’s pretty simple. I just want to ask you if you think that a distro with the following policy can be considered user friendly. And if so, could you explain why you think that’s the case? Policy:

“Note: It is imperative to keep up to date with changes in Arch Linux that require manual intervention before upgrading your system. Subscribe to the arch-announce mailing list or the recent news RSS feed. Alternatively, check the front page Arch news every time before you update.”

When I quoted the text found below, I wanted to ask you why you feel pacman is better than apt. I agree with you that I could (and perhaps should) be more explicit.

it’s package manager is just better than apt

You didn’t lay out “fault in my logic”

I meant the following parts of my previous writings:

I’m relatively new Linux user (just over two years now), so please bear with me. But, did I understand you correctly, that you hint towards the curious observation that rolling distros in general are technically ‘immortal’ while point-release distros eventually implode on themselves? If so, wouldn’t it be more correct to attribute this to the release model (i.e. point vs rolling) instead? Because, IIRC, this issue persists on openSUSE Leap, but doesn’t on openSUSE Tumbleweed. While both utilize zypper as their package manager.

But, if you noticed, I didn’t actually explicitly mention Arch’s install or its unopinionatedness as its downfall; which are indeed solved by its derivatives. The problem is with updates. At least on Debian and Ubuntu LTS, packages are (mostly) frozen and thus updates are in general non-existent and thus are not able to cause issues. The inevitable implosion happens once every two years at worst. Is that bad? Sure. But does it cause any trouble within those two years? Nope. And honestly, I don’t blame anyone that simply prefers to worry about updates once every two years instead of daily.

To make it easier for you:

  • Is Debian (according to you) not robust because it breaks eventually?
  • Do you acknowledge that this occurs beyond the Debian ecosystem?
  • Do you acknowledge that this occurrence seems to be found on distros with point releases, but not on distros with rolling releases?
  • Do you acknowledge that, therefore, blaming the package manager for this lack of robustness is perhaps an oversight?
  • And do you acknowledge that, with openSUSE Tumbleweed (rolling release distro) and openSUSE Leap (point release distro), this is perhaps most evident. As both rely on zypper, but the former is basically ‘immortal’, while the latter will eventually succumb to some major release.
  • Thus, do you acknowledge that, in fact, that Debian’s lack of robustness can not justifiably be attributed (solely) to apt. Nor, can Arch’s (seemingly) superior robustness not justifiably be attributed (solely) to pacman?
  • And thus, do you acknowledge that, we can’t continue to make the claim of robustness as it doesn’t hold any truth in retrospect?
General recommendations - ArchWiki

I honestly suspect the main issue is related to either the opinionatedness of Ubuntu compared to Debian or the absence of Snap. Why do you think that Distrobox will help them with their choice?