• 0 Posts
  • 33 Comments
Joined 1 year ago
cake
Cake day: June 19th, 2023

help-circle


  • In the case of Dracut, I’m not sure what it does exactly, but the kernels will almost definitely not be identical. In the “EFI kernel”, uneeded modules (meaning most of them) are usually omitted.

    You could probably also have different kernels in terms of version number, although it might complicate things. Kinda depends on whether they recycle data structures from the first kernel and whether those remain compatible. I don’t really know whether this is actually done tho.

    The reason why multiple kernels (or bootloaders for that matter) are used is that there are different levels of “readiness” in your system. Say you have LVM and a LUKS encrypted partition (in whatever order). Systemctl-boot will load the kernel and it’s initramfs, but can’t be bothered to deal with complicated file system shenanigans. That would complicate the whole program significantly.

    So it just loads a Linux kernel which has these capabilities. That kernel can deal with LVM, decrypt the LUKS partition (or ask for a password), mount whatever btrfs nonsense is inside and then hand it over to the proper kernel. The proper kernel can in turn rely on having all its stuff mounted and ready, instead of having to worry about all this.

    You could do with just one kernel, but Dracut allows you to rapidly create bootable kernel + initramfs pairs of which you might need multiple (e.g. for dual booting, backup). Moreover, you probably wouldn’t really want it to fiddle with your kernel all the time, especially when it’s customised already.


  • The kernel in the EFI partition is used as a tool to bootstrap hardware and memory for your proper kernel, which is chainloaded.

    There is a simple reason for that: The Linux kernel can do anything a bootloader needs to do, especially for itself, so why not use it as one?

    That said, in most setups there is another bootloader before that, which loads the kernel itself and the initramfs for that kernel. That can be for example systemd-boot, formerly known gummiboot, a minimal bootloader meant to (auto-)discover EFI compatible stuff it can load.

    Dracut creates a setup / boot chain like that.







  • The reason is very simple: They rely on Google Safetynet (basically self-diagnosis). And that will immediately tell you off if it notices your device is rooted. And while you can have a lengthy discussion regarding whether this makes your phone less secure or not, this is another simple argument from Google’s POV: The device has obviously been tampered with, we don’t want to put any resources into covering this case. As far as we are concerned, you shouldn’t use our OS like this.

    So basically laziness.









  • First came programmer socks, then Rust was invented, and now (fe)men are taking matters into their own hands, correcting the gender gap in IT themselves. What’s not to understand here?

    Seriously tho, I don’t think it’s against anyone. It’s just a meme, probably originating from a high share of queer people in the IT domain and the rising popularity of anime and manga culture, where femboys are sometimes idealised.


  • The documentary host went on:

    After hearing about their “totally riced” setup for hours, the exhausted predator dies a painless death in the icy waters. A mercy the breedable Rust peers of the Arch user, drunk on their freshly claimed victory, will not share. Already displaying socks as part of their mating ritual, no baby-faced creature that knows its way around a terminal is safe. They are not taken by force however. Rather they freeze, smitten by the confidence the incredibly annoying apex predator radiates. Feeling used, but also strangely satisfied, the confused boy is left wondering why they aren’t using Arch, when Wiki and the AUR are so incredibly useful. Maybe it’s that symbiosis that keeps them together: Curiosity, Fear and the common Arch user’s incredible displays of power.