Once in a while, fellas come into our list and forums, express their magnificent ideas, about why we should do this, Linux did that. Another groups just love to fork and spoon other projects. Some people are just whining, I'm one of those.
GNU/Linux is a runaway project. It's not going to be disappear, but it's turning to a gigantic unmanageable mess, as happened to windows. Here is an example:
There's a patch (clock_nanosleep) [1] on glibc which affects libc6 on WSL/Ubuntu and it turned to a bug [2]. There was a workaround [3] for WSL/Ubuntu and it fixed, but it's affected WSL/Kali too. Hence on the WSL/Kali you can't
Footnotes:
[1] https://sourceware.org/git/?p=glibc....c;h=3537ecb49cf7177274607004c562d6f9ecc99474
[2] Error:
[3] Comment out
- Thinking and sparking new ideas are not a unique process which you possess, billions do the same thing on daily basis, through history.
- Forking projects are fine, but it doesn't make you Thomas Edison
- Could you handle the maintenance phase of your puppy, or we suppose to do that for you?
GNU/Linux is a runaway project. It's not going to be disappear, but it's turning to a gigantic unmanageable mess, as happened to windows. Here is an example:
Code:
Linux -> -> Ubuntu
|-> Debian ->|
-> -> Knoppix -> BackTrack -> Kali -> WSL/Kali
GNU ->|
-> libc ................................................... apt upgrade. No fix for WSL/Kali. You have to trace-back all the way to Ubuntu project.Footnotes:
[1] https://sourceware.org/git/?p=glibc....c;h=3537ecb49cf7177274607004c562d6f9ecc99474
[2] Error:
Code:
Errors were encountered while processing:
libc6:amd64
E: Sub-process /usr/bin/dpkg returned an error code (1)[3] Comment out
set -e in /var/lib/dpkg/info/libc6\:amd64.postinst and force a apt -f install