/baot/ - *BSD And Other Things

man.openbsd.org/ifconfig.8#BRIDGE
openbsd.org/faq/faq6.html#Bridge

His rage is palpable.

Attached: 1539693994191.png (474x451, 270K)

(1/3)
OpenBSD is a meme
>Filesystem
SSD TRIM is vital to supporting SSDs, as without it, they degrade quickly due to unnecessary reads and writes. Sadly, OpenBSD has decided not to support this.
OpenBSD also does not offer a modern filesystem option. You simply get the very old BSD "Fast File System" or FFS.
Why is this important? Because when most people think of a secure system, they think of being resistant to evil hackers breaking into it. But that's only one part of security. InfoSec can be generally split up into three components: Confidentiality, Integrity, and Availability.
In this triad, availability seems to be the one that's lacking here. Who cares how hack-resistant your system is if the data you're protecting is corrupted?
That's not even getting into the volume management stuff that's missing, and the snapshots, and the everything.
"b-b-but MUH BACKUPS!!"
What are you even saying? That bitrot all of a sudden doesn't exist anymore? That backups are the one and only thing you should do and should not be supplemented by a more stable filesystem?
You do realize that if the filesystem is not secure and does not protect against bitrot and corruption, your precious backups are going to be fucked, because you'll be backing up corrupted data. Who even knows how far you'll have to roll back in order to get to a clean state?
"ZFS is one big thing! Very not-Unix! Just combine tools, bro"
OpenBSD doesn't have logical volume management either. Even if it did, FFS doesn't have the checksumming, bitrot protection, etc. Even if it did, OpenBSD softraid doesn't support as many RAID levels as other operating systems' solutions. It's just a worse deal all around.

Attached: puf800X689.gif (800x689, 69K)

(2/3)
>Security
"Only two remote holes in the default install!!!!!!!"
Yay!
I hope you realize that this literally only applies to a base system install with absolutely no packages added. In other words, not exactly representative or meaningful towards... anything really.
OpenBSD also does not have NFSv4 support even 18 years after its standardization. This is an issue security-wise because version 4 is the only one to offer authentication with Kerberos plus encryption with the krb5p option.
A common retort to this argument is that the NFSv4 protocol is "bloated", and that's why OpenBSD doesn't support it. Going off this, the OpenBSD project seems to think that authentication and encryption are bloat. Take a moment to consider that. It's certainly a very strange stance indeed, for such a "security-focused" operating system.
Let's of course not forget that OpenBSD lacks a Mandatory Access Control solution such as SELinux, AppArmor, or TrustedBSD, which provide benefits that are relevant to companies, organizations, and governments looking to better secure their systems and classified data.

Attached: no-sign-hi.png (600x600, 20K)

(3/3)
>Sustainability
A few years ago, OpenBSD was actually in danger of shutting down because they couldn't keep the fucking lights on. How could anyone see this as a system they could rely on, when it could be in danger of ending at any time?
"but it's open source! Someone could just fork it"
Oh yeah because surely they'll be able to maintain the entire OS
Actually now that I think about it, that really depends on the person/organization that does it. And they might actually have some sense and be able to fix some of the issues listed here.
It's official. OpenBSD would be better off if it shut down and was restarted.
>C Standards-compliance
"B-But OpenBSD is written in strictly standards-compliant C! Clearly that's better than muh GNU virus!"
So you're not allowed to create extensions to the standard? You should only implement the standard and nothing more? Keep in mind that this is nothing like EEE, as the GNU C extensions are Free Software, with freely available source code, as opposed to proprietary shite. People should be allowed to innovate and improve things.
If you're gonna be anal about standards-compliance, then why let people make their own implementations anyway? Why not have the standards organizations make one C implementation and force everyone to use it?
>Miscellaneous
OpenBSD's pf has inferior performance, as it only utilizes one core of one processor. GNU/Linux's netfilter firewall does not have this problem. Neither does pfsense.
OpenBSD does not support any 802.11 Wi-Fi standard newer than 'n'. It also lacks Bluetooth.
WINE doesn't exist on OpenBSD.

Attached: NOpenBSD.png (1000x1000, 168K)

this isn't twitter retard

You are my favorite poster.
t.OpenBSD user.

Attached: 1536720824728.gif (500x375, 198K)

>> 68223572
>> 68223583
>> 68223593
Meme as dumb as ever.

- SSDs handle wear leveling in firmware now.
- OpenBSD's base system is nicely full featured. You can do a lot without installing anything external. The only package on my router is Tor and the only one on my webserver is CGit.
- Along with the base system OpenBSD has security features like ASLR, strict malloc, retguard, stack canaries, and more, that benefit ALL packages. I'd rather run packaged software on OpenBSD than Linux.
- You make a big deal about NFSv4 but you don't actually use it, because it sucks.
- Every RHEL machine I've ever seen in industry has SELinux turned off. Your fancy MAC won't do you any good if it's too complicated for even sysadmins to use.
- The call for donations worked. These days OpenBSD has no trouble keeping the lights on:
openbsdfoundation.org/campaign2014.html
openbsdfoundation.org/campaign2015.html
openbsdfoundation.org/campaign2016.html
openbsdfoundation.org/campaign2017.html
openbsdfoundation.org/campaign2018.html
- OpenBSD isn't strict ISO C, they happily and logically extend the standard where it makes sense. Meanwhile GNU land gives you shitty extensions like strfry() and not anything useful. 2018, and you still can't call arc4random(), arc4random_buf(), or arc4random_uniform() with glibc! What a fucking joke.

Only decent point is lack of a good filesystem, but FFS with software RAID will be enough to prevent bitrot. Nothing wrong with running DragonFly/HAMMER2 on your backup server if you feel that way.

how do i install openbsd and access the anime on my ext4 filesystems ?

NFS, SMB, SSHFS

>john carmack donated to openbsd
badass

I tried to boot DragonFly BSD on VirtualBox and it kept giving me kernel panic on random times at booting. Finally when I raised RAM to 4 GB it let me to installation after few restarts and when I selected FS HAMMER2, it formatted the disk and gave me another kernel panic during installation. Could there be something I do wrong? Anybody installed this on Vbox?

According to their docs "HAMMER is designed for use on storage media greater than 50G".

Maybe that's the issue?

>no GCC 7 or 8 in ports

Very much might be the case because I gave it only 10 Gigs which I thought with grain of luck might be sufficient. I will try 50 or even better their recommended 128G. But still I'm worried about the kernel panics during booting. However, couldn't I fit NetBSD on 10 GB disk?

compiling gcc yourself is easy