The Linux Thread - The Autist's OS of Choice

  • 🐕 I am attempting to get the site runnning as fast as possible. If you are experiencing slow page load times, please report it.
>doesn't like bootloaders
>makes another bootloader


do... do these people know how the pc architecture works? other systems i can't argue, most arm devices straight up execute the kernel with an initd, skipping the need for a bootloader. (whether its a config file like the pi, or baked in like an android device, it just directly boots it)
but the pc architecture has a bootloader as a part of the spec so other os's can run on it.

hell you configure grub to load non-linux systems or to chain load another bootloader.
i 100% bet potting was behind this in his quest to have systemd be every part of a linux system.
 
Ok yea an EFI boot is already part of systemd. Is the article referring to replacing grub with booting the kernel directly? How does it handle legacy systems that aren't able to boot the kernel directly, such as MBR systems or systems that can't read ext4?
Well, the kernel gets installed on the EFI partition, so only the kernel needs to read ext4.
Legacy, yep, GRUB.
I've heard that if you can edit the EFI Variables, either through your 'BIOS' or other means you can provide different boot options.

I like grub, I'm sticking to grub, especially for dual boot.
 
systemd-boot was previously called gummiboot, a very minimalist bootloader, to boot EFI binaries. Notice I said EFI binaries, not linux kernels, because it actually requires the EFI stub to be present on the kernel binary. It just uses the standard EFI services API to hand control over to the binaries. Why would one do this when they can boot the kernel directly? Mostly to allow kernel boot parameters to be set in an associated config file without recompiling the kernel or needing an initramfs.

Grub even on EFI has a lot more functionality than systemd-boot/gummiboot, most which are irrelevant to normal users, stuff like TPM measured boot support, secure boot + MOK hand off, support for accessing the kernel binaries on filesystems that UEFI doesn't understand (like EXT4). If you use systemd-boot or directly boot the kernel from EFI, you'll need to place the kernel on the EFI system partition, usually it means on a FAT32 partition.

Edit: grub can still load traditional kernels without the EFI stub on the kernel binary, including compressed zImage/bzImage. EFI services will still be useable by the kernel so long as the right drivers are enabled, since its part of the ACPI standard rather than a boot protocol.
 
it would be nice if I could reboot my server without having to plug a display in so it doesn't hang during the grub boot
 
elilo is your friend.
EFIStub already exists, so of course that wheel has to be reinvented.
Right now I do have my system set to boot the kernel directly (by accident) and it works fine, but it doesn't let me choose to boot in safe mode or roll back to an older kernel
Sorry for being late, I think I have explain why I considered that presentation awful.

It is because that developer is biased towards "Muh security/language safety" (He said that because Grub is coded in C, it will be unsafe) and towards a workflow made for him. Using dual boot will be very tiresome without an GRUB menu replacement since accessing UEFI boot menu repeatedly is annoying. A lot of people use dual boot configurations since they need to use Windows separately.

I agree C language requires manual intervention and carefulness to make sure you don't have memory leaks or get out of bounds of allocated memory in the program. But that's what I like about C. It is an old and efficient programming language which doesn't restrict you in how you code, Rust though, while better suited for high security purposes, has a lot of checks that makes it more restrictive. Also Rust isn't as efficient as C, though in certain cases it gets close to C performance.

Also it is not a good sign that the person responsible for this presentation works for RedHat/Fedora. They have a bit of arrogance similar to Gnome devs.
 
Last edited:
it would be nice if I could reboot my server without having to plug a display in so it doesn't hang during the grub boot
Do you know for sure if it's GRUB related? Where does it end up hung if you turn it on without having a display plugged in, and then plug one in.

I recall that GRUB at least used to support using a serial console rather than a regular monitor at boot, so I wouldn't expect that to automatically fail. It could well be an issue earlier in the boot with your BIOS not wanting to boot without a display (which could be cunty to deal with), or something later with your init trying to start up a display manager when it shouldn't (which should be very easy to deal with with a normal sysvinit, and probably surmontable even with systemd).
 
  • Informative
Reactions: Vecr and i440BX
Do you know for sure if it's GRUB related? Where does it end up hung if you turn it on without having a display plugged in, and then plug one in.

I recall that GRUB at least used to support using a serial console rather than a regular monitor at boot, so I wouldn't expect that to automatically fail. It could well be an issue earlier in the boot with your BIOS not wanting to boot without a display (which could be cunty to deal with), or something later with your init trying to start up a display manager when it shouldn't (which should be very easy to deal with with a normal sysvinit, and probably surmontable even with systemd).
It's not by default anymore, but its still there: https://wiki.archlinux.org/title/working_with_the_serial_console
I'm more worried if BIOS would freak out without a screen. All the new BIOS oprom initialization will check which display output to use depending on if a monitor was attached. Grub doesn't care if the graphics is up or not, it just uses whatever UEFI/BIOS passes it.
 
I will probably have to migrate to some Linux distribution anyway
I heard gentoo is a good one.
 
Scored a cheap laptop with an old i3 to use as a backup machine and thinking of putting Linux on it. Not used Linux in 3-4 years, any developments to be aware of or anything I need to know about current day Linux?

Used to daily drive Mint xfce but not used Linux in years so don't know what the current state of it is, recommended distro, DE etc.
 
I'm confused. Do these faggots propose a solution for people who occasionally have to boot Microsoft OSes? Or is their expectation that their userbase uses only Linux all the time? Reconfigure EFI boot during Linux time to boot to Windows, reconfigure EFI boot during Windows time to boot Linux? This sounds quite absurd and ill thought out to me.
 
I saw lunduke is starting his own distro after recently going in on the state of the Linux scene and the creepy enforcement of far left views. Got me wondering what the least pozzed distros currently out there are? I know Clem is pretty political and OpenSUSEs CEO is pretty out there but I realized I'm pretty out of the loop on these things.
 
I saw lunduke is starting his own distro after recently going in on the state of the Linux scene and the creepy enforcement of far left views. Got me wondering what the least pozzed distros currently out there are? I know Clem is pretty political and OpenSUSEs CEO is pretty out there but I realized I'm pretty out of the loop on these things.
Devuan is pretty apolitical, unless I've missed something recently.
 
Do you know for sure if it's GRUB related? Where does it end up hung if you turn it on without having a display plugged in, and then plug one in.

I recall that GRUB at least used to support using a serial console rather than a regular monitor at boot, so I wouldn't expect that to automatically fail. It could well be an issue earlier in the boot with your BIOS not wanting to boot without a display (which could be cunty to deal with), or something later with your init trying to start up a display manager when it shouldn't (which should be very easy to deal with with a normal sysvinit, and probably surmontable even with systemd).
My previous configuration where I was booting from a SATA SSD would restart fine and have no issues. When I got a NVMe drive I found the bios wouldn't see it, so I plug in a tiny usb drive that I installed the EFI partition and /boot to. Right now if I reboot with no display plugged in then plug on in later it will not get a signal from either the motherboard VGA port or the Nvidia Quadro ports, but if I then plug the tv into the Nvidia card and five a reboot then it goes through the process fine.

I did swap my SAS raid card for a SAS controller card that may have had an effect too, maybe
 
I saw lunduke is starting his own distro after recently going in on the state of the Linux scene and the creepy enforcement of far left views. Got me wondering what the least pozzed distros currently out there are? I know Clem is pretty political and OpenSUSEs CEO is pretty out there but I realized I'm pretty out of the loop on these things.
Gentoo and Alackware I guess. Antix for the ancap/antifa memes.
Chinese Kiryn for MSS backdoor instead of NSA.
Apartheid to say Ja kooporaal Jawohl, Herr Unteroffizier.
Red Star OS to larp as a Jurche apolog-
bestkoreannewsnetwork.jpg
WE INTERRUPT THIS BROADCAST OF FAKE NEWS TO PRESENT TO YOU THE GLORIOUS TRUTH OF OUR GREAT COUNTRY.
DO NOT TRUST THIS MAN AND HIS LIES. AFTER ALL, HE IS A GENTOO USER.
 
My previous configuration where I was booting from a SATA SSD would restart fine and have no issues. When I got a NVMe drive I found the bios wouldn't see it, so I plug in a tiny usb drive that I installed the EFI partition and /boot to. Right now if I reboot with no display plugged in then plug on in later it will not get a signal from either the motherboard VGA port or the Nvidia Quadro ports, but if I then plug the tv into the Nvidia card and five a reboot then it goes through the process fine.

I did swap my SAS raid card for a SAS controller card that may have had an effect too, maybe
Does the server actually boot just with no display possible or does it fail to boot?
 
Does the server actually boot just with no display possible or does it fail to boot?
it fails to boot. it doesn't respond to ssh access attempts and none of the webservices are available, and cannot be seen in the router dhcp list.
 
Back