160
submitted 1 year ago by IverCoder@lemm.ee to c/linux@lemmy.ml
you are viewing a single comment's thread
view the rest of the comments
[-] tcit@beehaw.org 6 points 1 year ago

Isn't Fedora Silverblue builds moving to OCI-based as well?

[-] throwawayish@lemmy.ml 12 points 1 year ago* (last edited 1 year ago)

Yup, we've even been able to engage (to some extent) with it for the last couple of months.

It does require some know-how to set up, at least if you're unaware of uBlue; a community project that is set on offering said OCI images of Fedora Silverblue (batteries included) with different desktop environments (even those that aren't offered by Fedora (yet)). Bazzite, that has received some significant traction and exposure since it's very recent 1.0 image, is just one of the provided OCI images.

They even offer a very easy way for everyone to engage in building their own custom OCI image. I got mine spin up within two hours or so without knowing how git or containerfiles worked beforehand, it's that simple.

[-] s20@lemmy.ml 3 points 1 year ago

Hey, I've seen the "batteries included" thing several times related to ublue, but I don't understand what it means here. Could you explain?

I know what the idiom generally means - everything you need to get started - and even the origin of the expression. I just don't know what the metaphorical "batteries" are here.

[-] throwawayish@lemmy.ml 5 points 1 year ago* (last edited 1 year ago)

Due to legal reasons, Fedora is not able to distribute their distro with everything baked in to ensure (close to) maximum functionality out of the box. Notoriously, codecs required for (some of the) hardware acceleration and enabling the use of some multimedia file types are not delivered out of the box. Therefore, users are required to set those up themselves. Thankfully, RPM Fusion steps in to the rescue and makes it a lot easier for the end user to acquire these nonetheless.

But..., what if retroactively Fedora is forced to remove even more stuff and what if the solution is not directly available on RPM Fusion and thus requires (advanced) manual intervention in order to resolve the problem for the end user? Which actually happened just a few months ago with the mesa drivers*. Or what if a new Nvidia update causes troubles and you can't boot into your system? Which actually happens once every often if you don't pay attention and/or are unlucky. These are real problems that require real solutions; solutions which Fedora can't offer in the most elegant way in fear of the court (rightfully so).

This is where the "batteries included"" expression comes in. The aforementioned two problems were nonexistent on images provided by uBlue. Because problematic images are hold back by default automatically, which cautions them to resolve it ASAP and within a day (so far) the workaround gets built-in to the image and the end-user just gets the solution without ever noticing that something was wrong in the first place. Why? Because the end user's system never got the update without the workaround in the first place. An interaction unique as such within the Linux space is simply unheard of. I'm only aware of Vanillas OS that might be able to pull off something similar in the near future. Which is why I'm also very excited to see how it develops. Furthermore, as the end user you never had to go to the RPM fusion page in the first place to get/set up the earlier mentioned codecs as they were actually built-in to the image by default. That, is also part of the "batteries included" expression.

If you're interested, please consider checking out their documentation. Furthermore, please feel to inquire, if you so desire 😉 !

[-] s20@lemmy.ml 1 points 1 year ago

Alright, got it. Thanks for the explanation! I'm actually running ublue on two computers right now (bazzite on my desktop, beyond on my laptop, although I'm rebasing soon), so I'm not like a total noob to all this, and I have read the docs. I was just having trouble parsing an idiom.

[-] brokenix@emacs.ch 2 points 1 year ago

@s20 @throwawayish whats the difference between idiom and boilerplate code
--- pardon my ignorance , haven't read the article yet

[-] s20@lemmy.ml 3 points 1 year ago* (last edited 1 year ago)

In this case, I'm using idiom in its "I was a Creative Writing Major at College" sense; that is:

A speech form or an expression of a given language that is peculiar to itself grammatically or cannot be understood from the individual meanings of its elements, as in "keep tabs on".

*credit to Wordnik.com

So my use of the word here just means "expression" or "figure of speech," which is probably what I should have said in the first place; sorry for the confusion.

Edit: a grammatical correction no one but me would probably notice or care about.

this post was submitted on 28 Aug 2023
160 points (100.0% liked)

Linux

48335 readers
1301 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago
MODERATORS