@sendpaws I know...

@LineageOS's #fork is used for #Waydroid and #Google does restrict access to Releases to "Partners"...

• Basically pulling a #grsecurity / #RedHat on them...

#grsec #Tivolization #Enshittification #Paywalling #RHEL

@gnuplusmatt @hor32 yes, because #grsecurity / #grsec did came through with #paywalling their stuff before...

• Worse than #tivolization!

@katyswain I din't think that #CCSS is good either, but the demands of #GPLv3 are not compatible with the (adnitteldy shitty) reality of how #IP, #Licensing and #Patents work and thus it kneecaps a lot of things.

• GPLv3 caused #Apple to freeze their #bash version and divest into #LLVM and adopt #zsh.

• As @landley showed, enforcing the #GPL(v2) resulted in exactly 0 code being committed to #BusyBox and it only made said project look toxic and litigatious.

• Also i've yet to see anything happen re: #paywalled #SourceCodeAccess for #grsec & #RedHat #Linux. Maybe #GPLv4 will ban #paxwalling and force violators to work on #GNU / #HURD?

I chose #0BSD for _OS/1337 because as with any "intellectual labour", one cannot force others to collaborate and I'd rather have people join in out of the goodness of their hearts instead of just dumping some random git commit that is useless.

#OS1337

@tauon @radmin granted #SystemD is a suite of utilities and like the #grsec patches & tools they work best together.

• OFC the criticism is valid and I don't deny the problems that occur not just to you...

All I'm saying is that what came before was objectively worse!

• Personally I had the opposite experience cuz once you want to find a mistake, #journalctl actually prints useful error messages with journalctl -xe $ServiceName …

@carlwgeorge @vermaden @samurro @tara Well, that confirms you went #ReplyGuy on me in the most disingenious way possible, wasting everyones' time and patience in the process.

• Gues what: Good luck with that sales.pitch, cuz I'd rather give @ubuntu or @opensuse my money cuz that nonchalant attitude is insulting.

If you (or #RedHat / #IBM) don't want to support #OpenSource or anyone using anything they made for #RHEL without paying, then shure you can do that but then don't expect people to like you.

• #grsec already did that and I'm shure it resulted in 0 extra customers.

#CentOS was in fact a "gateway distro" and had Red Hat not axed it I would've convinced my (fmr.) boss to consider paying for an RHCSA, but alas I've invested time and effort migrating from CentOS to #UbuntuLTS and even negotiated commercial support from #Canonical instead, because they were more friendly and welcoming.

• Personally, I think that Red Hat should just be honest and just stop any #Linux contributions, instead try to upsell their customers to #zOS on z/Architecture #Mainframe|s instead cuz that was such a great business...

Even "Source Available" like #Tarsnap is better - espechally in #finance - because having actual #SourceCode available is a matter of #trust.

• And #transparency is the reason people choose #Linux over #Solaris and other #Unix-esque OSes.

But I'm not getting paid to prevent Red Hat from continuing to shoot itself in the foot...

• In fact, I'd love to short it into the ground!

https://infosec.space/@kkarhan/113065846313541796

#thxbye #next #EOD

@soulexpress nodds in agreement

• EVERY SINGLE ONE OF THEM!

Like there's a reason I only got a copy of #SubgraphOS as non-public alpha under the precondition to not redistribute and was allowed to preview it because that thing was unstable and had a lot of known issues the devs were working on to get fixed.

• It's not as if they weren't aware of those, but they also didn't want "#TechIlliterates" using it with a false belief in it being ready to use and trust in.

Not shure how #Subgraph evolved after #grsecurity decided to #paywall access to the #sourcecodes of said #patches and #tools cuz those were used in said distro as a means to harden it.

• But then again the #grsec devs seem to be so toxic, their entire Wikipedia Article got nuked and only an old archive version exists.

@SweetAIBelle @OS1337 shure.

I'm convinced that a fully-fledged image of that would be similar to #toybox's #mkroot, which is @landley 's reference implementation for a toxbox + #musl / #linux system.

• Last time I checked it came out just below 4 MB, but that was the premade image using only the stuff toybox included [and linux & being statically compiled against musl] like #gzip instead of #xz for compression, so there already is room to shave a few hundred kB without reducing functionality out of the get-go as I've seen with my build tests of #kernel666...

Either way, we're close to his reference matterial AFAICT and I do think that OS/1337 can become a good and solid foundation for #minimalist & #embedded systems.

For comparison:

• #YoctoLinux is quite #THICC in comparison (using LSB & #GNUtils for the most part!) and stuff like #OpenADK seems to be overly complex...

  • tho #Viprinet hasn't updated their stuff in like 8 years and I sincerely hope that's just them loginwalling access to #SourceCode like #grsecurity to paying customers only and not them such old Kernels.

Speaking of #grsec, I wounder if Bruce Perens actually sued them for allegedly violating #GPLv2 when in fact said license allows #paywalling aka. restricting access to buyers of the product it contains.

#OS1337