CloverOS GNU/Linux

It's a prebuilt Gentoo image with maxed out CFLAGS and minimal USE flags.

CloverOS GNU/Linux

Git: https://gitgud.io/cloveros/cloveros
ISO: https://cloveros.ga/s/CloverOS-x86_64-20180114.iso
Libre ISO: https://cloveros.ga/s/CloverOS_Libre-x86_64-20180114.iso
GPG: 78F5 AC55 A120 07F2 2DF9 A28A 78B9 3F76 B8E4 2805
IRC: #cloveros on irc.rizon.net
Twitter: https://twitter.com/cloveros_ga
Packages: 3213 https://cloveros.ga/s/packages.html
Rsync: rsync://fr.cloveros.ga/cloveros
License: WTFPL
Booru: http://cloveros.booru.org
Mirrors: https://useast.cloveros.ga https://fr.cloveros.ga https://au.cloveros.ga https://uk.cloveros.ga https://ca.cloveros.ga https://uswest.cloveros.ga

USE flags: USE="-systemd -pulseaudio -avahi

NO SYSTEMD FUCK OFF PÖTTERING

systemd/pulseaudio is AIDS, might as well install windows vista lmao

https://linuxtracker.org/index.php?page=torrent-details&id=4f15525060c74b1e04a6df422f4a92bbad735655

new CFLAGS
CFLAGS="-Ofast -mssse3 -mfpmath=both -pipe -flto=8 -fgraphite-identity -floop-nest-optimize -funroll-loops -fipa-pta -fdevirtualize-at-ltrans -ftracer -fno-plt -fno-semantic-interposition -malign-data=cacheline -mtls-dialect=gnu2 -Wl,--hash-style=gnu"

Minimal ISO (no portage tree, llvm/clang, qt5, gtk3, wpa_gui, firefox, nomacs, gimp, emacs, smplayer/mpv, qasmixer, xarchiver and linux-firmware only has wifi):
https://nl.cloveros.ga/s/CloverOS_Minimal-x86_64-20200126.iso

Imagine thinking you know better than the developers and override CFLAGS with your own bullshit instead of what was proven to work.

>>127
Its mostly useless experimental features or included in -Ofast.
99% of GUI userland stuff has no benefit from speed, only latency matters.

I don't think any programmer uses gentoo. It's just sysadmins who think they know what they're doing but they don't. They're the same people that think if they buy an Android phone with big number on the components they're getting the best when that's just one factor of battery life. The software matters a lot more also the inbuilt network card etc matter a lot too. They want to be experts but don't want to put the mental work in to understand all aspects of it.

I think it's the nerd problem. They got bullied in school so they overspecialize to have a territory which they own, their own safe space if you will. Then they even pride themself to be nerds: idiots which only know their territory and are useless everywhere else, even resistant to learn stuff outside of their domain.

>>129

I think it's the nerd problem. They got bullied in school so they overspecialize to have a territory which they own, their own safe space if you will. Then they even pride themself to be nerds: idiots which only know their territory and are useless everywhere else, even resistant to learn stuff outside of their domain.

This. Chads are dynamic and will pillage the nerd's safe space while he's watching from the corner.

>>129
What if some people just don't like the gnome3/systemd/pulseaudio desktop and ecosystem and just wants a classic 90's era FVWM desktop with no spyware/bloatware?

>>131
I've no idea about pulseaudio and gnome3 but I assume they're shit like anything linux desktop. Systemd however is very good and a massive improvement over shell scripts. It's a good system to manage a modern, complex operating system, the best I've used.

I do not understand why we didn't kill shell scripting 20 years ago. It always was shit and never improved. We should be using a small apl language for one liners and a proper scripting language for scripts. Ruby, perl, lua, python, js, scheme but no we're using bash or even worse powershell. M$ just could've made a library for interacting with the os for ANY of these languages and it would've been great. They could've used js and catch the whole js market onto windows. But they made fucking powershell. FUCK.

I also like FVWM and Nextstep but I don't understand how that is keeping you from using systemd.

The thing is: No smart people, actual good programmers, pros, stayed with the classic shell scripting init. The distros you're using are made by amateurs eg sysadmins.

>>132

actual good programmers
pros

Pick one.

>>132

We should be using a small apl language for one liners and a proper scripting language for scripts. Ruby, perl, lua, python, js, scheme but no we're using bash or even worse powershell. M$ just could've made a library for interacting with the os for ANY of these languages and it would've been great. They could've used js and catch the whole js market onto windows. But they made fucking powershell. FUCK.

your're are right about proper languages but I seriously can't imagine using APL for oneliners. for all its flaws, bash shit makes pipe-based oneliners easy and intuitive. a step up would be a shell language with a similar level of convenience and the ability to drop into a proper lang, like scsh or xonsh. APL for this purpose would just promote ,,clever`` cryptic bullshit for people to masturbate over

>>134
The smart, realistic way is to keep bash but to discourage it for > 5 loc and roll out a decent os api and replace all big scripts with a better alternative eg init.d => systemd.

>>135
systemd is a realistic way of breaking compatibility, making things more complex and reducing security

>>136
Poettering did nothing wrong. Your claims are without source.

Also dude I don't really care I'm not trying to convince you to switch. If you think you know better than all the pros go ahead, maybe you're right. Just know that you'll have to swim upstream.

Stubborn mental midgets are using init.d or openrc and nu-gnu is using some lispy thingy. Mental midgets are mediocre programmers and I've yet to use lisp software that wasn't shit. I'll stick with poettering tyvm.

Poettering is a terrorist in the UNIX ecosystem.

>>137
systemd would be an acceptable init system if it was an init system. but it's not. see this shit: https://www.cvedetails.com/cve/CVE-2018-15688/ https://www.cvedetails.com/cve/CVE-2017-1000082/ . it's not just that well-written systems wouldn't have bugs like that (but yeah, a well-written system wouldn't have bug like that). it's that those bugs are only possible because systemd does shit it shouldn't be doing, like DHCP or parsing usernames.

>>137
based

systemd is Linux turning into a real OS not a gay hobby machine. the neckbeards are triggered because it's too hard for them to understand, because they aren't programmers.

sure is /g/ in here

I switched to systemd-free distro because systemd isn't only insecure, its slow and eats quire a bit of ram.
Unfortunately lots of software has recently begun to depend on systemd, some even incompatible with systemd shims.

>>141
I don't go there for a long time. What's the /g/ro consensus on systemd nowadays? I can remember heavy anti systemd shilling.

>>142
Do you have sources on that? I feel like systemd is quite faster. Startup still is much faster with systemd isn't it? Also what init are you using?

>>143 sysvinit. Was ubuntu with systemd that regularly shown up at top lines of 'top', now top at idle is Xorg/compton.

>>144
Are you sure it's actually faster? It may be that all your deamons are on one process in systemd and with sysvinit they're distributed over multiple processes but take more power summed.

Every package was just rebuilt with >>125
https://twitter.com/cloveros_ga/

Fuck off nazi lonux

Anyone who either defends or uses systemd gargles multiple cocks.

>>148
What do you use?

>>149
upstart

>>150
What's upstart?

>>151
an init system

>>149
Still on Debian 7.1 with the old init system

>>153
It's actually a lot easier than you'd expect to just replace systemd with sysvinit in later releases. I used Wheezy until well after its EOL too, but it became untenable in the end—programmers are smooth-brained neophiles and they'll break anything and everything to force you to go along with their bullshit.

>>154
>updating the OS
Smol brain
>scripting new functionality in as and when you need it
Big brain

not much