13,408 karma · joined November 10, 2019
I'd stay away just for this reason alone. Anybody that says this is either joking or has no clue how the real world works.
https://en.wikipedia.org/wiki/De_Bruijn%E2%80%93Newman_const...
>Why has noone done this before?
This is a joke.
R.I.P. Dolly
https://github.com/ReFirmLabs/binwalk/wiki/Supported-Signatu...
Yes it wasn't truly 32-bit but the core was not MS-DOS. It was a hybrid. The Win95 kernel was 32-bit and drove almost all of the system, including memory. 16-bit DOS was used as a launching pad and then it's job shifted to handle 16-bit graphics and other hardware that was unable to work with the new 32-bit kernel. So you booted 16-bit DOS, and as WIN.EXE executed, the system transmorphed from 16-bit into a 32-bit (kernel) OS but some of that core 16-bit driver code was designed to remain welded onto it. Even more impressive is how you could dissolve this 32-bit level and return the system to 16-bit DOS. That remains a very impressive achievement 30 years later. Happy anniversary Windows 95!
Yep. Good catch, I think you win the argument. These are all distros that are under development and their underlying issues should never be called-out as handing the user frustration as they willingly chose to become a victim of the kernel.
https://bugzilla.kernel.org/show_bug.cgi?id=218770
https://lore.kernel.org/linux-f2fs-devel/20240409203411.1885...
https://lkml.iu.edu/hypermail/linux/kernel/2511.2/07280.html
https://lkml.iu.edu/hypermail/linux/kernel/2511.2/07260.html
https://bugzilla.suse.com/show_bug.cgi?id=1226043
https://lists.opensuse.org/archives/list/bugs@lists.opensuse...
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/15478...
https://www.reddit.com/r/archlinux/comments/1cvwo93/arch_run...
I'm sure this will age like a fine wine by 2040.
"I need it to work on a random Thursday, not wait for fsck after ever reboot"