New SystemD Feature

https://github.com/systemd/systemd/issues/2402

are they too poor to host their own git servers?

pottering is a bad person

But I use Gentoo, not systemDisease.

>>4
You use Gentoo replacements for parts of SystemD that embed themselves deeper and deeper each month.

Ahaha, you can literally destroy your BIOS with SystemD now! People had better never run sudo prepended code they find on shitoverflow or ubongoforums or IRC ever again.

EFI is a horrible designed-by-committee bloated mess. That's the real problem here. Use regular BIOS or replace it with Coreboot.

>>7
Why do you think so?

>>7
Who are you quoting?

>>9
Fuck all the way off.

>>9

being an anus

>>7
I use BIOS.

In fact, I've never used "UEFI" and don't even know what the hell it's for.

>>13
just go to a first world country

>>14
No, we're already full.

>>13
It's like a BIOS replacement.

Not sure, but... How is this not a kernel problem?
I don't know shit about EFI or kernel dev'ing, though..

Kernel Apps

Killer Kernal Apps

Linux sucks. Use *BSD

no fucking dumb shit like this

>>16
Why would you need to replace BIOS?

>>21
To be able to boot to dubs for example.

>>21
EFI natively supports multiple boot targets. BIOS has all sorts of outdated hardware checks and magic numbers that are unnecessary for today's context. You can prove the correctness of your bootup sequence with the use of secure boot.

>>21
You need 16-bit magic.

>>7
EFI is bloated, but there aren't any better alternatives. The Linux native bootloader interface is not cleaner by any stretch of the imagination - it's mostly a pile of undocumented hacks accreted to support various BIOS limitations. And as for BIOS -

>>21
The IBM "compatible" BIOS is an awful pile of historical kludges with countless limitations that appear arbitrary if you aren't intimately familiar with its twisted history. If you are writing 16 bit BIOS code you are literally coding for a dead architecture; the rest of the world has moved on to 32 bit or even 64 bit clean code and what remains over in BIOS land has developed unbelievable rot.

It is unfortunate that the base EFI specification contains so much inessential cruft - it would be nice if an industry group would prune it down to just the essential boot loading and configuration interfaces, but it'll probably never happen. In practice, the bare minimum is defined by what Microsoft uses, and sadly includes such awfulness as firmware graphics, HID, and ACPI.

>>25

there aren't any better alternatives

The thing it was supposed to replace is a fine alternative. I hope it gets replaced with something better some day, but it's better than EFI. It's an ``awful pile of historical kludges'' but nobody seems to be able to implement EFI correctly either, putting them in the exact same boat except one is a slightly smaller heap of shit.

Linux is for /g/ros
Everybody here runs BSD

>>27
Cudder runs windows 95.

Cudder runs TempleOS.

>>25

clean code

I know you don't mean that in the AGiLE sense, but some evil part of me likes to imagine BIOS writers being forced to only use five instructions per function.

>>26

except one is a slightly smaller heap of shit

It's not smaller when you consider the tooling and documentation. Nobody writes compilers for 16 bit x86 anymore^[1], and there are countless niggles in the interface specs that date back to the days when Compaq was a major player in the PC market. People are not going to keep this stuff around forever.

The largest voice for keeping BIOS around comes from people who have made a living out of recycling very old ideas (namely Linux developers). The bit they seem to miss is that this only works when the ideas you're recycling are mostly good.

[1] And no, your rotting copy of Watcom and gcc's 16 bit mode don't count

EFI natively supports multiple boot targets.

Total enterprise-level bullshit. What the fuck does "natively supports" even mean WHEN IT REQUIRES A WHOLE FUCKING PARTITION ON THE DISK TO EVEN BOOT? With BIOS, all it does is load the first 512 bytes of the selected boot device (could even be network) to 0000:7c00 and jump to it. Nothing could be simpler.

Real BIOSes are not written in anything other than Asm (I have the source, I know.)

ducks kek'em

>>32

care to share that asm bios with us?

>>34
Don't you know Cudder, the master of blue balls?
First 10 months: ``I just have to clean the source code a little, I'll release once I'm finished''
Following 18 months: ``Actually, I'll rewrite some parts of the code, after that I'm going to release''
The next 2 years: ``Development is slow, I'm busy these days... here's a piece of it for now [posts 40 lines of code]''
After that: ``All right, I'm back on track! Working on it again''
10 months later: ``Actually, this could use some clean up before release...''
-->>> GO BACK TO BEGINNING <<<--

Where is the browser, Cudder?

>>35
>>36
Just ignore namefags desu.

>>37
Just optimize quotes desu

>>33
Nice dubs, buddy!

Any day lennart poettiring doesn't break into your house and pee on your computer is an above average day with SystemD.