And those exploits are features in Chromium browsers.

Nonsense.

Partitioning have benefits. It is quite easy to set up "modern gnu/linux" since they all use a graphical installer. For sizes you can refer to openbsd's disklabel(8) man page.

It increase stability and security. Not only for enterprise.

Can you take some word for hardened_malloc or linux-hardened?

You are only speaking for the CIA, which has no good intentions.

Do you live in Viet Nam? I thought foreign are mostly friendly and respect differences, but the people who live on other's land aren't. Those people are screaming for ambiguous "freedom" but blatantly violate that freedom.

Edit: since this clown calls me “misinformation” spreader and asks for evidence, it is easy to look at one of the two long investigation articles I wrote, in which in share DivestOS XMPP room chat logs with Micay bullying DivestOS dev into banning me otherwise he will initiate a harassment campaign on social media against him.

Don't think that's related

Similar stuff was done (calling neonazi in issue tracker) against Bromite project that used what should be open sourced code, but is not.

https://twitter.com/GrapheneOS/status/1537851090514890752

That's personal emotion against bromite and lead to unacceptable wording. But Micay can't force others to remove their code if they do not violate it. nevertheless, Vanadium code is free in Linux communities' opinion, right?? (I'd not consider that since it is GPL)

simply: The license of vanadium is still gpl and is it free in your opinion?

There is no freedom in his code licensing

Evidence required.

Most of them grant infinite freedom, with one requirement. (Not restrictive like *GPL.)

Others like vanadium are restrictive under GPL

https://github.com/GrapheneOS/hardened_malloc/commit/c3a580727a9a844da05ae4e2787a937253b09427

You guys should not listen to TheAnonymouseJoker, this is the evidence of him spreading misinformation.

(Please note I'm not in GrapheneOS community (banned), nor putting myself in the class of privacy racers.)

harassing and witch hunting any critics

You can criticize GrapheneOS just because Micay will care about your words. But you can't do with something like OpenBSD because the developers are much knowledgeable and they never cared your words. They maintain an operating system for themselves and will not develop features to please users.

You can only criticize some small project with a developer that isn't good in communication. You are truly a petty person.

having a little social media army with sockpuppets to do this

No loser, the community is the army. (their quality isn't better than any Calyx or Lineage). The developers don't even have enough time to please user with a beautiful user interface then why they would screaming on social medias like you are doing.

But they maintained hardened_malloc and you never take a word for it.

(arch still use systemd)

and linux still not have base system software sandboxed (you can't enforce)

Currently it takes ~50 minutes to recompile the kernel

try make with -j

No it works. When on my windows 10 machine boots in < 15s. When off it takes a minute (HDD)

You can create either logical volume or physical partition, but make sure you have different partition for different mount point: /, /usr, /usr/local (keep small on linux), /var, /opt (if you use), /tmp (if you have little ram or don't want to use memory filesystem).

What do you mean by your comment.

I haven't said something about logical volumes vs physical partitions.

Split the filesystem to more partition.

have a 1G /, 500M for /boot, have partitions for /usr, /usr/local (this isn't used on linux so keep it small), /var, /home, and /tmp if you have little ram. Otherwise use memory-based filesystem (tmpfs), for /tmp I allocate less than 1/4 of my RAM.

For partition size, refer to https://man.openbsd.org/disklabel.8#AUTOMATIC_DISK_ALLOCATION

Remember to keep /usr/local small on most distro (perhaps I will allocate 5G), and increase /usr, create /opt too to prevent the disaster and allocate it the size for /usr/local. Don't allocate all disk space, a 200G home is enough for most people and leave the rest unallocated. the formatting and fsck would be faster on smaller filesystem.

And if you find other "cache" location, try log out and rm -rf the location, if login doesn't break, I would mount tmpfs on that cache location too.

Don't sign up. Or better don't be anonymous.