this post was submitted on 05 Feb 2024
68 points (100.0% liked)
Linux
48176 readers
897 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
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Aha, would you mind elaborating? That sounds like quite the issue for Pacman to break its own dependencies.
Ah okay, I was under the impression that the installation didn't require installing from source with the new binary system -- I thought it was more akin to Arch's installation where you just select your kernel binary in Pacman, then download, and install.
Would you have any resources/documentation for me to look into this more?
I misworded my original post -- I was referring to things like updating the kernel. I thought that maybe the kernel would be a binary, so it would not have to be recompiled like how I would assume it usually does.
This sounds very appealing to me, but I must admit that these sorts of configurations do seem like they would be mildly daunting to juggle on a production machine.
There was a bug with http/2 in a particular version of curl, which was very quickly updated in the arch repos and rolled out to users; It broke pacman's ability to sync.
It's one of those frustrating things that happens, and someone has to hit the bug first. It's nice to have a "stable" and "testing" branch so that users explicitly opt-in to bleeding edge packages.
This is just the base system - it's like any other distribution's base install except that we don't have an official 'installer'; Gentoo distributes tarballs that users unpack following the guidance in the handbook.
From there most packages can be installed as a binary if the USE flags line up (and it has been asked to do so), otherwise portage will compile it for you.
After unpacking the system image you can install a binary kernel, have portage compile one for you, or manage it manually (but still let portage fetch sources)
https://wiki.gentoo.org/wiki/Dispatch-conf
It comes down to user choice. That can now be entirely binary or from source (or from source but managed by portage)
It's actually pretty straightforward - you nominate packages that you want to run on ~arch (testing) and add them to some config files. Portage handles the rest.
It may be best for me to simply attempt to install Gentoo in a VM to see for myself, but, out of curiosity, how does the base image differ from something like the
.iso
that Arch Linux distributes to allow you to install the distro? So, if one were to install a binary kernel, would they still need to initially compile anything? Or could one theoretically do a full Gentoo install without the need of compiling?No idea, I don't arch.
Theoretically you can install a desktop amd64 system using the binhost without compiling anything (or if compilation is required there won't be much), I haven't tried though I have seen other users do it successfully.
There are options for binary kernels, just so you are aware.
As for documentation related to configuration of
portage
and/etc/portage/make.conf
, I would, of course, be remiss to not point you to the Gentoo Handbook. The wiki contributors do really great work and the community is generally quite welcoming and open to implementation-specific questions.