You can sue them if the work is not public domain or 0BSD, MIT no attrib,...
scratchandgame
joined 9 months ago
Years ago some Linux howtos or Linux distributions during their installation recommended to have several different partitions (I believe some of the BDSs like OpenBSD still offer such an option during installation)
There are advantages of having multiple partitions for multiple mount points.
OpenBSD can do partitioning for you, and it is not recommended to use a huge single root partition. If you can't do partitioning, use the default layout.
One advantage of that for /home is that you can have different mount options like noexec for preventing the execution of files inside your home directory which can be a good security measure.
If you never do development.
Anyone just having / and /home in separate partition are actually windows users, or not sysadmin.
Is there a Linux for people who are deeply entrenched in how Windows works
How Windows works is different I think?
I’m not above googling command lines that I can copy and paste but I’ve spent HOURS trying to figure this out and have gotten no where…
You don't need.
I heard you are using a debian-based distro, can you read the man pages for apt?
Then use apt to find docker, and get it.
Once it’s installed in the terminal, how the hell do I find docker so I can start playing with it?
It is not installed in the terminal. It is installed on the system, ON DISK!
docker should be installed on /usr/bin. It is on PATH. Type docker and see what happen. If not, try searching on /usr/bin (on BSDs third party software are separated from base, so docker should be installed on /usr/local/bin)
And the docker service should be started, if not. Use the fucking systemctl to start it. The service name should be docker, if I recall correctly
Their kernel is just fine.
It is just fine, yeah. The things that restrict what the user can do is the interfaces.
I do not do that. Pretty sure most said in your thread that you write weird stuff, and I also tried talking to you to no avail.
You are doing that. You dispose contributions like hardened_malloc. Why don't you spread more misinformation about it? Maybe when hardened_malloc have a bug you will.
You can only laugh on some security bugs of Pixel. You thought "debloat" is enough. This is insufficient. (And using adb to debloat can be considered overkill. Your software recommendation is insane and overkill. Being both insufficient and overkill are the current infamous attitude of current privacy communities, including privacy guides, privsec.dev, grapheneos community and other "degoogled" android communities)
Your OpenBSD fandom sounds like TempleOS meme. Weird. Pass.
???
Can you take some word for hardened_malloc or linux-hardened?
So when it comes to kernel modifications, I’m old school…
what I actually need is understanding the kernel.
At least process, memory management, ipc, handling device, etc.. Reading "The design and implementation of the 4.4BSD operating system", but I think I need to read something before reading that book.
Apps aren't even distributed via snap or flatpak. we have the option to install software we need and compile those are snap or flatpak only.
Forgot to link a comment on that website: https://marc.info/?l=openbsd-misc&m=158908598913596&w=2