Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
Fast-Nop2805121dDebian devs: its FREE garbage!
Rest of the world: it's free GARBAGE!
Wisecrack385521dand not a single fuck dropped in the whole post.
here borrow mine: FUCK.
IntrusionCM262121d@Root that's very sad.
Calamares though is not Debian specific, it's a joint effort used by many distributions, but lacks developers.
So you might find it in alot of other distributions like manjaro.
But one advice though.
Don't go down the Gentoo route in your current mental state. Gentoo takes time, since you need to compile stuff by yourself.
It's great once you get the hang out of it, since you learn about lot of the inner ways of how linux works, packaging and so on.
But it takes time and patience.
And I really don't think you have that atm.
(and I love Gentoo. It's my main distribution since dozen years...)1
ParkCity421021dbeen using g/fdisk wherever i can, i never trust graphical partitioning apps;
are you using gdisk to partition gpt tables, or fdisk?
Got Debian 10 to install — had better luck with the cli-only installer — and now it freezes when starting KDE.
FFS I give up.
elgringo209321dDid you did a checksum or md5sum to validate the integrity of the ISO ?
IntrusionCM262120d@ParkCity the fun thing here is...
Both could break the installer in fun ways.
If you want a 100 % working way to install debian manually, use a chroot plus debootstrap after partitioning and formatting (using a live cd with a kernel matching the target kernel and current filesystem utils).
But that's not the point here, and I guess noone would do it like this (except me, who hates any kind of installer because of all the questions involved...).
The reason installers are very "brittle" is because there are magnitons of things going possibly wrong.
Depending on library and used partition manager, some tools fail to validate the ESP partition.
Missing BIOS boot partition (some installers still enforce this).
There are several more, just some pointers to why this is like it is.
Sometimes the EFIVARFS is the culprit.
The EFIVARFS is modified by the efibootmgr which is called by grub-install.
There were numerous issues with EFIVARFS in the past and still exist.
A funny one was eg this:
Debian 10 added support for secureboot, which should be mentioned, since you should make sure that the shim is installed correctly and work's TM.
The thing is (and actually this is a mini rant since I get root's frustration)...
We're still only at the UEFI stage.
That's not the largest part.
It's just UEFI, aka the "bootloader".
And yes... I've unfucked many many many systems via Live CD.
And many many many times it was'nt even the fault of linux or (U)efi per se, but rather bad mobo supplier.
It's disturbing, but BIOS upgrade plus EFIVARFS nuke plus Secure boot key reset plus reinstall is something I can do in my sleep.
Might be one of the many reasons I hate UEFI.
IntrusionCM262120dCalling MBR deprecated. This is really absurd.
Fast-Nop2805120dWhat worries me most are the segfaults because they point to shitty coding practice, lack of defensive programming, and they probably didn't bother to use static code analysis tools.
Another concern is, what else besides the installer did these clowns code?
Root6569519dDevuan (Beowulf), which is based on Debian 10, installed perfectly the first attempt.
Still no WiFi, but that’s completely normal for me 🙄