1. It's getting harder and harder to find use for BIOS hardware since most, if not all, 64 bit platforms use EFI and arm does whatever the frick it wants
2. Since it's already a part of systemd you end up reducing waste by putting it to use + efibootmgr scary
>It's getting harder and harder to find use for BIOS hardware since most, if not all, 64 bit platforms use EFI
Libreboot does not support UEFI. >Since it's already a part of systemd you end up reducing waste by putting it to use
I don't use Systemd >efibootmgr scary
No it's not.
1. systemd-boot doesn't support BIOS and won't ever
2. EFISTUB is superior to systemd-boot, systemd-boot is bloat
>systemd-boot doesn't support BIOS and won't ever
no system shipped in the last 12-13 years uses BIOS anymore. any decently modern system uses UEFI. the fricking Core 2 Duo machine I had back in 2008 supported UEFI. if yours doesn't it's time to upgrade, son
anti systemd idiots are the stupidest most illogical morons there are. don't expect any good or ration answer from them. systemd is totally fine and has been for like 13 years
One of the most triumphant victors over the past couple years has been to build the ROS robotics stack on slackware, meaning I can finally ditch ubuntu and systemd for all time. If you like systemd, good for you. It has never ceased to be a pain in my ass.
systemd is fine. why is it a pain in the ass for you, name very specific examples. i bet you can't. let me guess, the tired old hanging job meme? fix you broken job
2 months ago
Anonymous
>a stobjob is running
2 months ago
Anonymous
so fix your broken job. what the frick is wrong with you? why are you so bad at using linux? i'm running debian stable, this problem does not exist. why do you keep spreading the same dead meme when it's literally your fault?
2 months ago
Anonymous
i switched to dinit and never had such problems ever again
2 months ago
Anonymous
but you lied, the problem doesn't exist with systemd. you're just lying over and over
2 months ago
Anonymous
nope
2 months ago
Anonymous
yup
systemd is bloated
nope, and it follows the unix philosophy. there's like 30 binaries and each is a few kilobytes. you're just wrong and a liar
2 months ago
Anonymous
>30 binaries >its not bloated because they are small
You are mentally disabled
2 months ago
Anonymous
what's the problem exactly? other than you're a moron
2 months ago
Anonymous
>the init is only 30 binaries
2 months ago
Anonymous
it's not an init you moron, answer literally any question you fricking homosexual
bro, lilo isn't even shipped with anything, did you time travel from 20 years ago?
Nah, it comes with Slackware and I believe there is package in Gentoo for it.
it's shipped with ubuntu and debian
what more do you need?
Lilo is good but it doesn't support encryption
Just use Limine at this point. It's so much better than what's out there atm it's not even close. Worst part is getting a configuration file going.
Debian and Ubuntu use GRUB now, and it has been the default for quite a long time now.
I dislike GRUB because it loves to break on you for insane reasons.
LILO is better but it may not work for modern computers
>lilo is better
>but it doesn't work
LOL
works on my machine
name processor, distro, and distro version
lilo works on bios
elilo for gpt (never tried though)
name processor, distro, and distro version
works on any hardware as long as it uses bios
notice how you won't name processor, distro, and distro version
i7, slackware 14.2
there
>Slackware 14.2 release notes. Thu Jun 30 2016
>2016
LOL
slackwate 15 is worse since it has partial systemd, so what you gonna do
>worse since it has partial systemd
explain why systemd is bad, you can't
it doesnt work with very old RAID cards so cant boot from a RAID card
that's the dumbest lie i've heard on the board in the past week
elilo works on efi
LI
only boomers will understand
>redpill me on the de facto standard thing that has worked for decades
I don't know if I can, you're too moronic
LILO got filtered because it refused to updoot itself, bootloader efforts migrated to GRUB
why a standardized bootloader needs to be any different from what it is
what would and update do?
Workarounds for shitty BIOSes, filesystem support, 3rd party OS support since a lot of Loonixers dualboot with Shitdowns or something else
I don't think LILO even works with EFI/GPT
ELILO
>his distro doesn't package it anymore
https://packages.gentoo.org/packages/sys-boot/lilo
I never quite understood what is it supposed to do that needs 500k lines
i use systemd
Why would you even want to use this? Did you just wake up from a 20 year coma or something?
>noooo you must updoot
>anti updating
>uses anything past DOS
you're a fricking hypocrite
Ummm, the colors are nice?
cause it works?
I use systemd boot.
Can't wait for systemd-boot to take over GRUB. Compared to GRUB its lot simpler
1. systemd-boot doesn't support BIOS and won't ever
2. EFISTUB is superior to systemd-boot, systemd-boot is bloat
1. It's getting harder and harder to find use for BIOS hardware since most, if not all, 64 bit platforms use EFI and arm does whatever the frick it wants
2. Since it's already a part of systemd you end up reducing waste by putting it to use + efibootmgr scary
>It's getting harder and harder to find use for BIOS hardware since most, if not all, 64 bit platforms use EFI
Libreboot does not support UEFI.
>Since it's already a part of systemd you end up reducing waste by putting it to use
I don't use Systemd
>efibootmgr scary
No it's not.
it doesn't support FDE
Can they be made look like this as easily?
>Not GRUB_TIMEOUT=0'ing
anon...
I'm GRUB_TIMEOUT=2'ing
>White SIR
same here, systemd-boot is comfy
>systemd-boot doesn't support BIOS and won't ever
no system shipped in the last 12-13 years uses BIOS anymore. any decently modern system uses UEFI. the fricking Core 2 Duo machine I had back in 2008 supported UEFI. if yours doesn't it's time to upgrade, son
wouldn't know i use zfsbootmanager
Bootloader is bloat, use efistub.
last in last out?
sounds moronic
lilo has saner configuration
I don't even edit my grub config and would just generate one, because grub config is such a clusterfrick
>turn on computer
>its boots to grub
>it just works
why do you need more
anti systemd idiots are the stupidest most illogical morons there are. don't expect any good or ration answer from them. systemd is totally fine and has been for like 13 years
One of the most triumphant victors over the past couple years has been to build the ROS robotics stack on slackware, meaning I can finally ditch ubuntu and systemd for all time. If you like systemd, good for you. It has never ceased to be a pain in my ass.
systemd is fine. why is it a pain in the ass for you, name very specific examples. i bet you can't. let me guess, the tired old hanging job meme? fix you broken job
>a stobjob is running
so fix your broken job. what the frick is wrong with you? why are you so bad at using linux? i'm running debian stable, this problem does not exist. why do you keep spreading the same dead meme when it's literally your fault?
i switched to dinit and never had such problems ever again
but you lied, the problem doesn't exist with systemd. you're just lying over and over
nope
yup
nope, and it follows the unix philosophy. there's like 30 binaries and each is a few kilobytes. you're just wrong and a liar
>30 binaries
>its not bloated because they are small
You are mentally disabled
what's the problem exactly? other than you're a moron
>the init is only 30 binaries
it's not an init you moron, answer literally any question you fricking homosexual
systemd is bloated
alpine linux uses syslinux. simple as.
Unironically, what still uses LILO?
Maybe an embedded thing? Haven't seen it on x86 in 15 years.
I remember when distros asked to choose between lilo or stitch, these were the times
yes, but systemD-boot as well as rEFInd and Limine are better