▶ No.961844>>968994 >>988229
Because it doesn't support systemd.
▶ No.961846>>961847
Too lazy to backup my files
And make a clean install
Also Is pacbsd good or is it just another meme distro?
▶ No.961847
>>961846
pacbsd is very meme
▶ No.961849
I figured this was some bullshit thread so I went over to /g/ and lo and behold, you made this exact thread there too. Consider suicide, OP.
▶ No.961862>>961867 >>982376 >>988897 >>990013
>>961835 (OP)
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.
>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.
>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.
▶ No.961864
debian just werks so why should I? also X interface a shit. SHIIIIIT.
▶ No.961867>>961879 >>981114 >>981284 >>988101
>>961862
Nice copy pasta shill. Shame that it's all bullshit.
▶ No.961871>>961883 >>961951 >>980861
>>961835 (OP)
>trusting BSD
▶ No.961873
Fully standard compliant C is shitty and insecure. Disabling strict aliasing optimizations allows you to violate the C standard without fear of getting raped by the optimizer. The GNU cleanup extension massively reduces the risk of stale pointers and leaks. And GNU's named struct initializer extension (maybe this is standard C now, or maybe only in C++?) avoids structs potentially getting the wrong values after changing fields.
▶ No.961879>>988197
>>961867
Kinda stale, they're into things like
>yikes
>we are better than this
>toxicity
▶ No.961883>>961919
>>961871
Wasn't this one of the causes that caused OpenBSD to be security focused? iirc Theo talked about 2 egregious bugs that made him go full tinfoil.
▶ No.961919>>981166
>>961883
A 2001 CVE? No, he's been seen as a lolcow at least since the project began. Not sure what he was doing before that.
▶ No.961921
>>961835 (OP)
Giving it a try after FreeBSD, feels snappier on the startup, I like the configuration better. But the wifi isn't stable (it's also a known bug, related to noise detection and packet handling)
▶ No.961930>>961950
>>961835 (OP)
FreeBSD is CoCed. NetBSD is ancient. OpenBSD isn't as secure as the memesters on this board seem to believe unless you install only the base system and nothing else, and never run X, and it's slow anyway. DragonflyBSD doesn't support all of my hardware. The rest of the BSDs are derivatives and too niche to care about. That's why.
▶ No.961936
▶ No.961950>>961954 >>961955
>>961930
>OpenBSD isn't as secure as the memesters on this board seem to believe
Security is not an on/off switch retard. OpenBSD is light years *safer* than windows/linux and it keeps getting better at it.
However OpenBSD is not based because of security alone, but because it is a SANE OS. No systemdick, no bloat, deprecated stuff are deleted, simple to install and use.
▶ No.961951>>961953
>>961871
>posting vuln from 2001
Wew. Anti-OpenBSD shills have lost their touch.
▶ No.961953
>>961951
That's the last time anyone actually used it.
▶ No.961954>>961970
>>961950
Have you actually read OpenBSD's code? It's garbage and a lot of it is left partially implemented. I posted some of their ntfs driver in a previous thread that is missing necessary locks (even left as comments in the code) and would likely let a user scribble over memory. But how many hatted technologists are going to waste their time on an OS no one uses?
▶ No.961955>>961970 >>969067
>>961950
The OpenBSD base system (without X) is reasonably secure, but almost nobody uses just the base system. Actually, when you get right down to it, almost nobody uses OpenBSD, period.
There is a ton of KMS code that was pulled in from freedesktop that remains unaudited to this day. That's not the only wart in the codebase.
The OpenBSD base system is reasonably secure against script kiddies. But every major intelligence agency on the planet has dozens of OpenBSD 0days. If your threat model is protecting your home router from script kiddies, OpenBSD is a solid choice.
▶ No.961970>>961993
>>961954
>>961955
Niggers, these are niggers. Glowniggers fear the puffer fish.
▶ No.961993>>969040
>>961970
What if puffer fish IS the nigger?
▶ No.968994
>>961844
That's a (+), not a (-).
▶ No.969029
>>961835 (OP)
BSD is homosexual security by obscurtiy. pass.
▶ No.969040
>>961993
It sure looks like one.
▶ No.969067>>969069 >>969078
>>961955
Liar, there was no OpenBSD exploits in the cia vault releases. They had lots of stuff for Linux and FreeBSD though. There are more Intel hardware exploits than actual OpenBSD exploits. That really says a lot, because hardware has in theory much more thought and testing put into it at the design and immplementation phases.
▶ No.969069>>969075
>>969067
Why would they go after OpenBSD when nothing runs on it. I doubt they had exploits developed for TempleOS, either.
▶ No.969075>>969087
>>969069
I'm using OpenBSD right now, and I've used it to run web servers, mail servers, DNS, and firewalls. Yeah it doesn't run your games or other Windows stuff (because there's not WINE) but it's an all-around good Unix system, that won't get pozzed with stupid shit like systemdicks and CoCs.
Of course, most people don't actually want a Unix system at all, they want a Windows replacement, with lots of desktop shits galore. And that's exactly why those other OS get pozzed.
▶ No.969078>>969080
>>969067
>Liar, there was no OpenBSD exploits in the cia vault releases.
>implying the vault leaks were everything the CIA had
>implying the CIA is the world's only intelligence agency
Pathetic.
▶ No.969080
>>969078
So all you're capable of doing is make empty statements without any proofs. So long, blackpill shill.
▶ No.969087>>979460
>>969075
>I'm using OpenBSD right now
You're nobody, though.
▶ No.969114>>969246
I don't know much about OpenBSD, but I do know that it's not a nigger-friendly OS. Are all the naysayers ITT just salty nignogs? Should I install OpenBSD on my laptop this weekend?
▶ No.969152
▶ No.969246>>969327
>>969114
It's worth a try if your hardware is supported. Try installing to a USB thing and booting from it. If you see stuff like "device unconfigured" in dmesg, that one device isn't working due to missing driver or missing firmware (but you can use the package manager to fix the later).
▶ No.969327>>969333 >>969366
>>969246
Way ahead of ya, I already installed it. So far so good, very comfy. Can I mix packages and ports? I remember that being an issue in FreeBSD. Also, how can I make acpi calls? I need to kill the nvidia gpu. I have a script for that in Linux, but it obviously doesn't work in OpenBSD.
▶ No.969333>>969351
>>969327
>Can I mix packages and ports?
If you install anything at all beyond the base system, you're opening yourself up to all kinds of security flaws. Only parts of the base system are audited, and OpenBSD has chosen not to implement a lot of modern mitigation techniques. They do have pledge, but most software has not been modified to take advantage of it.
You'd be better off using a Linux distro with good repos and firejail + AppArmor or SELinux.
▶ No.969351>>969369
>>969333 (checked)
I'm just playing around, not actually trying to switch. I simply never tried obsd before and wanted to check it out.
▶ No.969366>>969381
>>969327
Packages are just ports that were built for convenience's sake. All packages come from ports. But some ports don't get built because hardly anyone uses them, or because the license forbids binary distribution. Also, some ports have various FLAVOR options (see "man 7 ports" about this) and you might have to build the package yourself if you want a FLAVOR that's not provided in binary form. So mixing packages and ports is no problem, since they're really equivalent.
I don't know about acpi calls. I guess apci(4) is a good place to start, but I never tried to do anything special like shutdown the GPU (I pretty much just run apm to throttle the cpu). Anyway does it make a difference if the GPU is alive if you're just using the wsfb X server instead (for example)? Does it actually suck tons of power when it's not even being used?
▶ No.969369
>>969351
What that guy said is wrong anyway. OpenBSD added the pledge/unveil framework and that allows a sort of MAC/jail type fine-tuned mitigations on the 3rd-party ports.
Interesting video about pledge:
https://youtube.com/watch?v=FzJJbNRErVQ
▶ No.969381>>969413 >>980077
>>969366
>Does it actually suck tons of power when it's not even being used?
I made measurements.
<powertop-optimized Linux with nvidia gpu killed, minimum brightness:
~7.5 watts
<default OpenBSD with nvidia gpu idling, minimum brightness:
16+ watts
So yeah. More importantly though, the gpu causes noticable coil whine. I rebooted back to Linux because it was driving me insane. I'll have another look at it tomorrow.
▶ No.969413>>969422 >>969423
>>969381
OpenBSD does not support nvidia at all.
I would assume that the only time OpenBSD would be close to Linux in power consumption would be with Intel integrated as that appears to be what the devs dogfood the most on with laptops.
It will take a while for vega to get supported but hopefully that gets sped up now that Theo is shitty at Intel.
It would be pretty great to have a ryzen lappy on OpenBSD.
▶ No.969422>>969426 >>969552
>>969413
My OpenBSD laptop (Thinkpad T60) has Intel integrated graphics. So I can't comment on other GPUs. But all things being equal, power consumption is always much higher with OpenBSD. I don't exactly know why this is.
But I don't care. My laptop's battery will last maybe 10 minutes. And it's getting worse by the day. I always have the AC plugged in. Batteries are shit. The sooner they die the better. That way you can run on AC like a real man.
Only a pansy does anything "on the go." I prefer to do my coding and work in my cozy, dimly lit apartment.
▶ No.969423>>969552
>>969413
>OpenBSD does not support nvidia at all.
I know, how is that relevant? I just want to kill it. Hell, I'd remove it if it weren't integrated into the mobo.
>vega
Doesn't vega require amdgpu? Wasn't that such a clustefuck that not even Linux wanted to merge it? Does this really have any chance of getting into OpenBSD?
▶ No.969426>>969428 >>969645
>>969422
Why use an ancient 14" (potentially 15") screen to program on when you can use a multi-head setup with a desktop?
▶ No.969428>>969645
>>969426
You can use two monitors with the docking station.
▶ No.969512>>969524
▶ No.969524
>>969512
BSD developers are cucks. GPL users are cucks.
▶ No.969552>>969645
>>969422
apmd(8) isn't enabled by default.
https://www.openbsd.org/faq/faq10.html#rc
This dude has some cool stuff:
http://www.eradman.com/posts/openbsd-workstation.html
>>969423
It's relevant because they don't offer any guarantees on how nvidia behaves, maybe enable ampd(8) as shown in my link above?
▶ No.969645
>>969426
>>969428
I don't need multiple monitors. And I even if I wanted an extra monitor I would just use the VGA port. No need for docking station.
>>969552
I always do apm -A. CPU throttling definitely helps, but power consumption is still higher than with Linux or Windows. I don't give a shit.
▶ No.971036
>>961835 (OP)
Because I'm used to GNU/Linux and I don't see why I should spend the time nor energy to change something that works perfectly
▶ No.971094>>971098 >>979425
>>961835 (OP)
>doesn't have software I need
>non-existent graphical (NVidia) drivers
>even worse hardware support than GNU/Linux
Why are you using it?
▶ No.971098>>971105 >>971106 >>971129
▶ No.971105>>971154
>>971098
>if I ignore the problem it will go away
>addressing 1 point out of 3
▶ No.971106>>971154
>>971098
Did he even mention games? All of his points are valid.
▶ No.971129>>971154
>>971098
Mocking extremely popular use cases will surely help
▶ No.971154>>971157
>>971106
>>971129
>>971105
>game fags triggered that a server OS can't play call of duty.
is this board full of children
▶ No.971157>>971158
>>971154
Nobody even mentioned cawadooty, moron. The hardware support/hardware acceleration is very poor, and it still uses FFS, ffs.
▶ No.971158>>971163
>>971157
>Nobody even mentioned cawadooty, moron
stop denying it faggot you just want to play gaymes on your laptop.
>hardware support
for laptops
>hardware acceleration
what the fuck are you doing deep learning?
▶ No.971163>>971169 >>979409 >>979443
>>971158
I hate laptops, I only work on desktops. If I were to build a Ryzen system, I doubt I could get it to work on OpenBSD. (I've also tried to install it on my server, and it wouldn't work.)
▶ No.971169>>971181
>>971163
>I've also tried to install it on my server, and it wouldn't work
Well anon I can tell you really know what you are doing.
▶ No.971181>>971185 >>971190
>>971169
The installer would probe my memory and then fail. (I know that my memory isn't bad.) The install is trivial when it works, I don't see how anyone could mess it up.
▶ No.971185>>971192
>>971181
Well anon sounds like you have bad RAM, and everything else is such shitty quality it does not bother checking. Why don't you go do some diagnostics.
▶ No.971190>>971192 >>971197
>>971181
Wat. There's no step in the OpenBSD installer that probes memory. I've installed the OS hundreds of times and never saw this. All the installer does is ask you questions related to configuration, sets up the disk partitions, and then installs the sets, creates device nodes, creates root and optionally a user account, generates ssh host key, and other such basic stuff.
▶ No.971192>>971204
>>971185
>>971190
One of the very first things the installer does is probe memory. It happens for only an instant though, try installing it on something and pay close attention. I know I don't have bad memory, that box uses SmartOS now.
▶ No.971197>>971212 >>974093
>>971190
On second thought, I guess you're probably talking about the ramdisk kernel that's failing to boot. That's not the intaller, which is really just a shell script that runs after the bsd.rd has booted. I've no idea why it would fail to boot, but you should test your memory with memtest86 or something, just in case. Linux will actually "run" on broken hardware whereas OpenBSD won't (by "run" I mean until things start to get corrupted in unpredictable ways). I've seen it happen on a shitty AMD K6/2 mobo I had long ago.
You could also try to remove one or other other of the ram chips and see if it boots.
▶ No.971204>>974093
>>971192
>I know I don't have bad memory, that box uses SmartOS now.
The RAM is bad and the shit is just not giving a fuck.
▶ No.971212
>>971197
Also the second-stage boot loader has a small shell where you can configure certain things, and memory is one of those. See here:
https://man.openbsd.org/boot.conf
You'll have to quickly hit a key when the prompt comes up, or else it'll boot the kernel right away.
▶ No.974092
>>961835 (OP)
Because it doesn't have a code of conduct.
▶ No.974093>>979436
>>971204
>>971197
The memory is fine, I have tested it. I found someone with the same issue as me:
http://openbsd-archive.7691.n7.nabble.com/Re-HP-Compaq-6005-hanging-on-boot-td59314.html
Now, it *is* an HP Xeon server, so maybe next time I'll buy something else. But I find it strange that server hardware doesn't work, considering routers and servers is the classic OpenBSD use case.
▶ No.974096>>974098
How to setup a RAID6 with OpenBSD ? Which filesystem to use ?
▶ No.974098>>974102 >>974105
>>974096
I thought they only offer one filesystem? For laptops and routers, OpenBSD is good, but I wouldn't use it on a server or (home) desktop.
▶ No.974102
>>974098
idk to be honest, i'd like to try it out with some drives laying around.
I'm supposed to use bioctl to achieve this but documentation isn't clear except for RAID1.
To be more specific, OpenBSD is installed on a small HDD right now. I want to know how to create a RAID6 array with 6 drives.
▶ No.974105>>974108
>>974098
>but I wouldn't use it on a server
Why not specifically? It wouldn't be good for large load, high I/O, distributed sites but for your typical single box soho uses its fine and very stable.
▶ No.974108>>974152
>>974105
He probably means because it doesn't have an advanced filesystem like ZFS or HAMMER2.
That's probably the main answer for most users on /tech/ who aren't using it.
I think it's fine for laptops. Use FreeBSD with ZFS on your NAS for backing up stuff and storing large files and you're fine.
▶ No.974127
>>961835 (OP)
NVidia Card. Plus I still like to game on occasion. I used to use it on my thinkpad though. Really did like it.
▶ No.974152>>974156
>>974108
>FreeBSD
ZFS exists for Linux and OpenBSD's softraid can handle a home NAS just fine
▶ No.974156>>974158
>>974152
ZFS isn't as well integrated for Linux. I don't know why the OpenBSD guys don't just bite the bullet and port it. I've heard they think they don't have the man power, but it sounds like whining to me.
▶ No.974158>>979421
▶ No.979409>>979417
>>971163
Openbsd works fine on ryzen, why would you think that is a problem?
▶ No.979417>>979546
>>979409
I guess that was a bit misleading--I know all x86 CPUs are remarkably backwards compatible. What I should have said is that the Ryzen system I plan to build will use a modern GPU, and OpenBSD does not support modern graphics cards. (I'm not a gamer, I just like using multiple high resolution displays.)
▶ No.979421
>>974158
Nice SSL you got there
▶ No.979425
▶ No.979436>>979441
>>974093
HP is infamous for making buggy BIOS and ACPI implementations. Avoid buying their products. They used to be good, but the quality went to shit after they got that woman CEO. One of their engineers most likely provided fixes for Windows and Linux, but they don't care about smaller OS projects. You can always try to install NetBSD or DragonflyBSD and see if you get lucky though.
▶ No.979441>>979445
>>979436
So what you are saying is that Linux is so much better than OpenBSD that it can correctly run on hardware that is literally broken.
▶ No.979443
>>971163
Laptops are way more power efficient though. I wish it were possible to build a desktop that idles at under 10 watts (including the screen).
▶ No.979445>>979446
>>979441
Enjoy your memory corruption and other subtle bugs when Linux "works" on broken hardware.
▶ No.979446>>979468
>>979445
>modern systems use the bios after they boot
sorry bud it's not 1996 anymore
▶ No.979450
Why use that when i can use 🍀 os
The kosher os
▶ No.979460>>979468
>>969087
>you're nobody
Not him, but I don't see this as something bad. It's like i'm using something that suit my needs but I'm nobody so my point doesn't stand? Most of the time I only lurk here but it always make me sight when somebody is trying to invalidate someone else opinion because he's "nobody" on an anonymous imageboard for outcasts.
▶ No.979468>>979797 >>980080
>>979446
Go back and read his post. The OS didn't boot. The OS got stuck because the BIOS was doing something broken and/or non-standard. The Linux kernel has tons of fixes for this kind of stupid hardware crap, just like it has tons of binary blobs for similar reasons. I always recommended OpenBSD to people as a good gauge to judge hardware by, even if they don't intend to run the OS. Same with code. If it can run in OpenBSD with all the mitigations, that means it's not totally crap that depends on undefined behavior or other dubious shit.
>>979460
I didn't take that as an insult. I like being a nobody. A lot of sysadmins and programmers out there are nobodys who just get the job done and don't go looking for likes on facebook or whatever. If anything, this more humble attitude is the opposite of the SJW infestation that's killing projects these days.
▶ No.979469
>>961835 (OP)
Because my bloody wireless adapter is not supported.
▶ No.979546>>979766
>>979417
>I want to run proprietary nvidia drivers!
You don't belong here.
▶ No.979636
Posting through an OpenBSD packet filter, right now. And surfing through and OpenBSD proxy in another browser window.
▶ No.979766>>979807
>>979546
No, I want to use the amdgpu drivers, with the Polaris cards. I don't buy Nvidia.
▶ No.979797>>980001
>>979468
>The OS didn't boot
Because OpenBSD was incapable of dealing with hardware that Linux and everything else that matters could. Inferior OS.
▶ No.979807>>980157
>>979766
Isn't amdgpu FOSS? If they haven't ported it yet, then maybe you can help?
▶ No.980001>>980403
>>979797
> binary blobs and shitty workarounds are what matters
You deserve the CoCk tbh.
▶ No.980077
>>969381
assuming you're using intel can you test this with hyperthreading disabled in bios? since openbsd disables it and linux doesn't im curious if that would decrease some of the power consumption, of course the video card is another issue
▶ No.980080>>981281
>>979468
try booting with sata set to ide in bios, this can be undone if you have an os already installed
▶ No.980157>>980201
>>979807
amdgpu has dependency issues that prevent its inclusion and more lines of code than the entire OpenBSD kernel by several times over. I'd like to see it too, but it's unlikely that we'll ever see a 1:1 merge of amdgpu in its present state.
https://marc.info/?l=openbsd-misc&m=152465462030464&w=2
▶ No.980201>>980264
>>980157
>more lines of code than the entire OpenBSD kernel by several times over
That seems unreasonably large. I'm guessing intel doesn't have anything that bloated? WHY CAN'T AMD?
▶ No.980264
>>980201
That assumption would be correct. I don't know what AMD's problem is.
AMD
>sloccount /usr/src/linux-4.14.67-gentoo/drivers/gpu/drm/amd
SLOC Directory SLOC-by-Language (Sorted)
1006944 include ansic=1006944
120796 amdgpu ansic=120796
67920 powerplay ansic=67920
9017 amdkfd ansic=9017
704 scheduler ansic=704
28 acp ansic=28
Totals grouped by language (dominant language first):
<ansic: 1205409 (100.00%)
Intel i915
>sloccount /usr/src/linux-4.14.67-gentoo/drivers/gpu/drm/i915
SLOC Directory SLOC-by-Language (Sorted)
111761 top_dir ansic=111761
13572 gvt ansic=13572
7843 selftests ansic=7843
Totals grouped by language (dominant language first):
<ansic: 133176 (100.00%)
▶ No.980286
Ima currently trying it out.:
>I came from gentoo
>I like the manpages
<I didn't like that we got new filesystems
>Already noticed some security aspects .
<if you cant read manpages you are REALLY FUCKED UP!
▶ No.980403>>980406
>>980001
Enjoy your insecure system once you install literally anything because openbsd does not believe in isolation.
▶ No.980406>>980407 >>980412
>>980403
Yeah, I think that is stupid. Theo bloviates about how insecure virtualization is, and yet I doubt he'd be able to crack a properly configured Qubes system, and he'd probably not even be able to exploit a Jail. Until someone finds a way to crack into Qubes boxes, it's _demonstrably_ secure.
▶ No.980407>>980408 >>980409
>>980406
YOU are full of shit. The meltdown bug is proof that a Qubes system would not be secure.
Sure it's patched now, but claiming it is therefore a secure OS is like claiming it was before, when WE NOW KNOW IT WAS NOT!
Do you think the NSA didn't know about these processor level bugs? Are you some kind of government agent?
▶ No.980408>>980423 >>980447
>>980407
>Sometimes an error in the lock is found and someone can pick the lock. Therefor we should say fuck it and leave all our doors open
OpenBSD fags really are retarded.
▶ No.980409>>980417
>>980407
I like how you're BRINGING OUT THE CAPITAL LETTERS--it shows me that you feel personally attacked. The only reason you'd mention Meltdown/Spectre is because you believe the hysterical and very duplicitous lie that was in circulation Jan 2018--that the OpenBSD devs had completely nullified the Spectre/Meltdown vulnerabilities ahead of time. That was false. (Really, why would you bring up a _hardware_ bug when we're talking about virtualization/compartmentalization? Brain-dead?)
▶ No.980412>>980423
>>980406
>Until someone finds a way to crack into Qubes boxes, it's _demonstrably_ secure.
Unless it isn't implemented correctly.
Openbsd defaults to not doing something rather then push something that may be flawed or they can't confidently do out the door. If something is proven flawed and they can't fix it then they take it out. Strait up disabling hyper-threading over a theoretical spectra threat is just the latest example of them doing that. Thats a big performance hit in the name of security.
OpenBSD isn't the fastest OS. Its not for hosting VMs. If those 2 things matter then you should be looking elsewhere rather then expecting the openbsd autists to change.
▶ No.980417>>980423 >>980612
>>980409
>why would you bring up a hardware bug?
Because that bug (meltdown) made virtualization absolutely USELESS for security you fuckwitt!
Also, I'm not taking it personally at all, I'm just annoyed by the claim that Qubes is demonstrably secure when a recent hardware bug proves the contrary.
That is why I KNOW you are government shill trying to give a false sense of safety to the lemmings here!
▶ No.980423
▶ No.980447>>980458
>>980408
It's actually closer to saying you should never use doors and stay inside because it's more secure.
▶ No.980458
>>980447
>never run anything because all software is shit
▶ No.980612>>980617
>>961835 (OP)
>>980417
>Because that bug (meltdown) made virtualization absolutely USELESS for security you fuckwitt!
MFW Theo absolutely called it! https://marc.info/?l=openbsd-misc&m=119318909016582
▶ No.980617
>>980612
>Don't lock your door at all because doors get broken down sometimes
▶ No.980648>>980650
Intel chips aren't a door, they're swiss cheese. Here's a nickel kid, get yourself an ARM SBC. And run something that's not cucked on it. That rules out Linux and FreeBSD.
▶ No.980650>>980658
>>980648
>Stop running this proprietary piece of shit
>Go run this other proprietary piece of shit
▶ No.980658>>980663
>>980650
All the chips are proprietary, even the humble Z80. But none of them are buggy on the scale of Intel. The ARM Cortex A7 was unaffected by all the recent bugs. Most other ARM chips already on the market could be fixed with new firmware. Intel chips are so broken, even that's not even to fix them, and neither are software solutions that OpenBSD and other OS are implemnting (like disabling hyperthreading). INTEL CHIPS ARE SWISS CHEESE! Use anything else and you're better off.
▶ No.980663>>980673
>>980658
This is really just wrong. If shitty proprietary mobile hardware is known for anything, it's not security. Intel at least has the entire VPS market attacking it constantly.
▶ No.980673>>980695
>>980663
> presents no FACTS, just FUD
You're just another Intel cianigger shill. Too bad for you, everyone has figured out Intel sucks ass now.
https://marc.info/?l=openbsd-misc&m=151527756600887&w=2
https://www.raspberrypi.org/blog/why-raspberry-pi-isnt-vulnerable-to-spectre-or-meltdown/
Mind you, I don't recommend the RPi board, since it can't even boot without firmware blob. But there's plenty of other choices.
https://www.fsf.org/resources/hw/single-board-computers
http://linux-sunxi.org/Buying_guide
▶ No.980695>>980830
>>980673
>One particular vulnerability is representative of all of them
>The RPi is only not vulnerable because it lacks basic hardware features
▶ No.980830>>980840
>>980695
Actually, "Spectre" is an entire class of vulnerabilities, and Intel is full of them. There's been quite a few so far, and we're probably not at the end of this yet.
Oh yeah, it lacks features all right. It lacks the cianigger deniability of "oops we bugged again". That's how those motherfuckers operate, in case you haven't been paying attention (also see: inexplicable design and bugs of OpenSSL). They don't like having to do things the hard way. That's why weak crypto is going into Linux, allegedly for IoT devices. That's why they also put weak random generator in Intel chips. Once again, Intel = cianiggers' best friend.
▶ No.980840>>980850
>>980830
>Actually, "Spectre" is an entire class of vulnerabilities
Actually every CPU with any prediction infrastructure at all. You will have no idea how this works. Fucking arm is vulnerable all the same.
▶ No.980850>>980858
>>980840
But that's just it. It's not "all the same". Not even every common ARM chip is vulnerable, and the ones that are can be patched. With Intel you're forced to turn off all kinds of those "features" like hyperthreading and even that's not enough, it only reduces the attack surface. And the kicker is IT'S ALL BY DESIGN.
▶ No.980858>>980986
>>980850
>Not even every common ARM chip is vulnerable
Not literally every cheap. Every fast one. EVERY FAST ARCHITECTURE is effected. (Good) ARM, Sparc, Power, X86, etc. Your ARM arduino clone is fine.
▶ No.980861
>>961871
>last update a year ago
Is it fixed?
▶ No.980865>>980871
Lisp F U C K I N G OS when?
▶ No.980867>>980871 >>980992 >>981281
>>961835 (OP)
I can't get it to boot
▶ No.980871>>980873 >>980876 >>992045
▶ No.980873>>992045
▶ No.980876
>>980871
It was an honest response! I really tried.
▶ No.980986
>>980858
You mean was affected. Those other faster ARM chips are patchable. Intel isn't. Intel isn't patchable. INTEL ISN'T PATCHABLE AND THEY HAVE TO REDESIGN AND FAB NEW ONES(*). You best start believing in ghost stories Intel shill, cause yer in one!
* Yeah we'll get it right this time goyim. Trust us. Dumbfucks.
▶ No.980991>>981475
How do I get openbsd to only output to my external monitor? I'm using a thinkpad laptop but I'm essentially using it as a desktop. I don't want an extended desktop, I only want the external monitor. I am using cwm btw, and the default login manager.
▶ No.980992>>981077
>>980867
Did you disable secureboot
▶ No.981077>>981081
>>980992
>to install the secure os you have to disable secure booting
hmmmmmmmm okay cia
▶ No.981081>>981089
>>981077
secureboot doesn't mean secure against cia, it means secure against user tampering
▶ No.981089>>982557
>>981081
Just like OpenBSD then.
▶ No.981114
>>961867
What part of it is bullshit?
▶ No.981166
>>961919
>muh lolcow
go back to baphomet you dumb nigger
▶ No.981281
▶ No.981284>>981289
>>961867
>it's all bullshit.
>openBSD does not currently support TRIM
▶ No.981289>>981291
>>981284
>inb4 trim is bloat and it should be handled on firmware
▶ No.981291>>981297
>>981289
>trim actually was bloat and IS handled by all hardware in the last 10 years
▶ No.981297>>981336
>>981291
>hurrdurr I don't know the difference between trim and wear leveling
▶ No.981336
>>981297
>When encryption is in use, using the TRIM command reveals information about which blocks are in use and which are not.
TLDR trim is insecure. Get fucked.
▶ No.981475>>981634
>>980991
I only got one monitor, but I'm guessing it would be done via xrandr. Should work the same as on Linux and anything else that uses Xorg.
▶ No.981634>>981640
>>981475
i never deep dived into manually configuring x but i guess it's a nightmare. Where do I look up how to do this?
▶ No.981640>>981650
>>981634
You should learn how to read man pages.
▶ No.981650>>981671
>>981640
i definitely should and i will read it eventually but I'm sick and I can't read a lot per day. just wondered if there was a quick way to do it but nah
▶ No.981671>>981750
>>981650
First execute and empty xrandr command to get a list of monitors and modes.
With the name of the monitor you want to turn off you do:
xrandr --output <monitor-name> --off
▶ No.981750
>>981671
Thank you very much.
▶ No.982252>>982255
Anyone know where rtorrent puts downloaded files by default? For some reason rtorrent doesn't have a manpage. I downloaded some stuff but it's just gone, searching for the filename didn't turn up anything either.
▶ No.982255>>982275
>>982252
Nvm, I found them in the /usr/share/doc/pkg-readme/ directory. Weird...
▶ No.982275>>982299
>>982255
I guess you found the rtorrent docs in there? (not your downloads, because how would you have write access to that dir)
Anyway, yeah not every package has a man page, because they're 3rd party stuff. That's why I have this in my environment:
CDPATH=.:/usr/local/share/doc:/usr/local/share/examples:/usr/local/share
That way I can quickly cd to package name and usually end up in the right place, when there's supplemental docs (or simply no man page at all).
Also you can "pkg_info -L rtorrent" to get the whole list of its files.
▶ No.982299>>982550
>>982275
No I mean the actual downloaded file was in that directory. I doubt it but it's possible I ran rtorrent as root I'm very tired.
Thanks for the other tips. I haven't figured out environment variables yet but I guess that's in the faq.
▶ No.982376>>982377
>>961862
Here’s a nice resource for when you’re too dumb to figure out how to make it work right
▶ No.982377
▶ No.982393
Anyone have experience with bhyve or other BSD based hypervisors? Proxmox has been doing a good job for me, why should I migrate and what sort of benefits would I get?
I don't want to wipe everything I've got just to be disappointed in a shit hypervisor.
▶ No.982550>>982560
>>982299
You'll want to read the ksh manpage, but here's a quick summary:
https://marc.info/?l=openbsd-misc&m=139806803319410&w=2
▶ No.982557>>982568
>>981089
>OpenBSD tries to prevent users from doing stupid crap as its security model
▶ No.982560
▶ No.982568
>>982557
>It's okay to be a buggy piece of shit because anything that has a bug in it the user installed so having no security fine.
▶ No.982643>>982673
How do I grab the devicename of my graphicscard? I'm trying to configure what video driver Xorg uses because I'm getting dropped frames in browser video, in mpv, and in 3d rendering. I didn't see anything in the xorg.conf manpage about how to actually identify the device itself. I'm using an 6200u intel processor with its integrated gpu btw.
▶ No.982673>>982747 >>982754
>>982643
Search for the string "drivers" in /var/log/Xorg.0.log
In mine it has this:
[1062731.836] (II) Loading /usr/X11R6/lib/modules/drivers/wsfb_drv.so
All the drivers are in that directory, and they each have a manpage (and they're also listed at the bottom of the xorg.conf manpage). So you can "man wsfb", "man intel", "man radeon", and whatever else. You probably want the intel driver. So then it it's not already loading it, you can tell it to by creating /etc/X11/xorg.conf with the right stuff. Mine just has this:
Section "Device"
Identifier "Device0"
Driver "wsfb"
EndSection
▶ No.982747
>>982673
Thank you. It was using the modesetting driver. I changed it to intel and it seemed to work. However, it would no longer use my external monitor. So I rolled back to modesetting and tried to configure xorg.conf to use my external monitor as the only monitor. But I must have fucked it up somehow, now I get nothing on either screen. Even booting in single user mode I get nothing. The system is now essentially unusable. Is there anyway I can get to some kind of rescue terminal before x starts? I tried using the ctrl+alt+function keys to get to a console but it does nothing.
▶ No.982754>>982767
>>982673
Thank you. It was using the modesetting driver. I changed it to intel and it seemed to work. However, it would no longer use my external monitor. So I rolled back to modesetting and tried to configure xorg.conf to use my external monitor as the primary and as the only monitor. But I must have fucked it up somehow, now I get nothing on either screen. Even booting in single user mode I get nothing. The system is now essentially unusable. Is there anyway I can get to some kind of rescue terminal before x starts? I tried using the ctrl+alt+function keys to get to a console like in linux but it does nothing.
▶ No.982767>>982787
>>982754
Sounds weird. If you actually went into single-user mode ("boot -s" at the boot loader prompt) then it shouldn't even mount any filesystems other than / and thus can't run X.
I'm not familiar with multi-monitor stuff at all, but maybe you can unplug the second screen and poweroff completely the computer for like 10 seconds (also remove battery if it's a laptop). Maybe something at the hardware level is acting up.
Also if "boot -s" doesn't work for some crazy reason, you can try to boot the install CD, since it gives the options (I)nstall, (U)pgrade, (S)hell. From the shell you can go "mount -r" (read-only) some disk partitions and poke around at logs and config files.
▶ No.982787
>>982767
>but maybe you can unplug the second screen and poweroff completely the computer for like 10 seconds (also remove battery if it's a laptop). Maybe something at the hardware level is acting up.
That's actually it. Only with the external monitor physically disconnected boot -s would take me to console, with it connected it would just go blank after the initial boot messages. Thank you.
Anyways this is what I put in the xorg.conf that caused it.
Section "Monitor"
Identifier "HDMI-1"
Option "Primary" "true"
EndSection
▶ No.982802>>983033 >>983413
I am trying to install OpenBSD on a (((modern))) laptop, but I can't mount the USB storage which contains the wifi firmware. The kernel says that it's called sd2, but when I run #disklabel sd2 I get an error message saying that device doesn't exist. Does this mean that the laptop's MB isn't fully supported? I have tried different ports and USB flash drives. Pls send help. I guess I should try NetBSD, if OpenBSD doesn't support my hardware..
▶ No.983033
>>982802
Is it detecting the flash drive properly? You should get stuff like this in dmesg:
sd1 at scsibus4 targ 1 lun 0: <Flash, Drive AL_USB20, 1.00> SCSI2 0/direct removable
sd1: 495MB, 512 bytes/sector, 1015552 sectors
Also you can maybe try a USB HDD and see if it makes any difference. Or maybe an SD card, if your laptop has those slots.
▶ No.983222>>983236 >>983259 >>983278
▶ No.983236
>>983222
I used the default disklabel layout on my laptop, and it only created a through l, but some of those aren't even OpenBSD stuff. c just represents the whole disk rather than an actual partition, and i is the FAT32 with UEFI. So that's 10 partitions by default. The reasons for making so many are given here:
https://www.openbsd.org/faq/faq4.html#Partitioning
Of course, you can choose custom layout and set it however you want.
▶ No.983266>>983292
How do I even configure xterm? I want a bigger fontsize. I've tried
xterm*font: monospace-18
xterm*font: mono-18
xterm*facesize:18
xterm*facename:mono:pixelsize=18
in .Xsession but it doesn't change anything.
▶ No.983278
>>983222
just do a small one for / then largish ones for /usr/local and /home. fuck security.
▶ No.983280>>983281
.Xdefaults? .Xresources? I don't know what xterm uses, why are you using that ancient horseshit anyway.
▶ No.983281>>983283 >>983285
>>983280
What do you recommend using instead and what makes it better?
▶ No.983283
>>983281
And yes I meant i put it in .Xdefaults, not .Xsession.
▶ No.983285>>983301
>>983281
I use xfce terminal because I like tabs and shit. don't tell anyone though, I'll lose all muh bloat cred.
▶ No.983292>>983302
>>983266
First, xrdb is your friend. "xrdb -query" will show you what the current settings are. Now you can tell if it loaded your config properly.
Second, startx reads ~/.xinitrc, but xdm (and friends) reads ~/.xsession and runs those commands. If you use both methods, you can always make a symbolic link. One of the commands should be something like:
xrdb -merge ~/.Xresources
(see the examples in the startx and xdm manpages)
Also, you're probably not giving enough font information for X to know which one you want. xlsfonts shows you all the avaiable fonts, or you can just show a subset like:
xlsfonts -fn '*mono*'
You can actually pass those strings directly to "xterm -fn <whatever>" and test if you have a valid one. But when you're configuring the .Xresources file, you only need to give as much information as necessary so it knows which one exactly you want to use. For example, here's what I have in mine:
*VT100*faceName: DejaVu Sans Mono
*VT100*faceSize: 15
You can also use xfontsel to preview what the fonts look like.
▶ No.983301
>>983285
Same, can't be bothered to reconfig/fetch configs all the time for urxvt (or whatever is cool with the maymay kids these days).
▶ No.983302
>>983292
Oh, and if you want to directly specifify in a single entry the font string as given by xlsfonts, you can just set it like this:
xterm*font: 9x15
xterm*boldFont: 9x15bold
I had that on another machine with a different monitor. Anyway the xterm manpage tells you all the resources you can set for it, and there's quite a few!
▶ No.983413>>984458
>>982802
OpenBSD uses a static /dev, not a dynamic /dev like you'd get with udev/Linux or most other BSDs. On some occasions (mostly installation), it requires manual intervention. It could stated more clearly, but according to the FAQ:
>The install kernel only has the /dev entries for one wd(4) device and one sd(4) device on boot, so you will need to manually create more disk devices if your desired softraid setup requires them. For example, if you need to support a second and third sd(4) device for a mirrored setup, you could do the following from the shell prompt:
>Welcome to the OpenBSD/amd64 X.X installation program.
>(I)nstall, (U)pgrade, (A)utoinstall or (S)hell? s
># cd /dev
># sh MAKEDEV sd1 sd2
Though the directions are worded for softraid setups, this applies to any system with more than one disk.
▶ No.984451>>984458
ive heard openbsd limits the amount of memory each application can access. how do i go about increasing this limit
▶ No.984458>>984892
>>983413
Wow I feel dumb now. Thanks that fixed the problem.
>>984451
edit /etc/login.conf
Its man-page is rather self-explanatory: https://man.openbsd.org/login.conf
▶ No.984490>>984492
>pkg_add -v gnome
it installed clisp, the worst Common Lisp implementation
▶ No.984492>>984497 >>984503
>>984490
openbsd boots
>x cursor on default black/white dotted background
install gnome
reboot
>black screen
nnnnrgh
▶ No.984497>>984504
>>984492
Did you edit your .xinit?
▶ No.984503
>>984492
i tried runnin mate but its running at molasses pace so i just use cwm for now
▶ No.984504>>984511
>>984497
nope
under previous versions of OpenBSD, fvwm2 would just werk
now the default doesn't work, and adding a DE doesn't make that work either (it doesn't even do nothing--a black screen is a change)
▶ No.984511
>>984504
maybe you dont have accelerated graphics
put "cwm" in your .xsession
ctrl+alt+enter to open a terminal
▶ No.984892
>>984458
>edit /etc/login.conf
I edited dataset-cur and dataset-max under default:\ section. is that correct
▶ No.987740
We can't let the OBSD thread die.
▶ No.987749>>987871
I'm installing NetBSD on a Thinkpad X23 with 128mb of RAM, should I stick to CLI only or use twm or cwm
▶ No.987871>>987872
>>987749
My Xorg process on OpenBSD/amd64 shows about 120 megs in top, so you're probably better to stick with the console (it will be a bit smaller for i386 though). If it has a real framebuffer, you can probably run Links in graphical mode.
Worst case, make an xorg.conf that disables all the X modules and extensions you don't absolutely need. That will also make your system more secure BTW, since those things tend to have really bad code, as mentioned in this video:
https://www.phoronix.com/scan.php?page=news_item&px=mtu1nza
I used to run X just fine on a 486 with 8 megs that had Slackware and the 1.2.x kernels in the mid 90's. Shit's really gotten out of hand with bloat and security problems.
▶ No.987872
>>987871
Also you can probably save memory by only loading a small subset of the fonts, but I forget the details on how to go about that. Search for "TinyX", because they figured that out and got X working on machines with only 4 megs long ago when memory was really expensive.
▶ No.987963
Doesn't run the shitware I want and has poor filesystem support. Otherwise I'd be using it.
▶ No.988036>>988038 >>988087
OpenBSD seems like a great place to learn Unix C Programming. It seems the documentation is on point for the standard library and extremely pleasant to read compared to the GNU version. Not to mention everything is most likely way more consistent than Linux, and the code is of a much higher quality (re: no bloat).
I'm going in. Daily reminder that 6.4 will bring updated graphic drivers too. OpenBSD about to be maximum comfy.
▶ No.988038>>988087 >>988137
▶ No.988085
Reeee I'd install OpenBSD but I need Mathematica for work.
▶ No.988087>>988096 >>988137
>>988036
>>988038
do I really need to do all these fucking steps? https://www.openbsd.org/faq/upgrade64.html#BeforeUpdate
seems faster to just reinstall the whole system if all of this is required
▶ No.988096
>>988087
Well damn. Guess I'm waiting til November.
▶ No.988101
>>961867
don't forget
>oh my sweet, summer child
▶ No.988118
>Why aren't you using BSD?
Butt, sex, and dicks.
▶ No.988137>>988192
>>988038
I think it's going to be released tomorrow. 6.4 is already live on the mirrors, and the top of the ANNOUNCEMENT file is dated October 18, 2018. They've been releasing a couple weeks earlier than the official May 1/November 1 targets for at least a few years, so this would fit the pattern.
http://cdn.openbsd.org/pub/OpenBSD/6.4/
>>988087
You probably don't need to touch the majority of the configuration files that they listed. If they're still at their defaults, sysmerge will do the job just fine by itself. The rest of it amounts to copy-pasting a few lines into a terminal. I'll let you make your own decision, but I don't think it will be as difficult as you make it sound.
▶ No.988192>>988326
>>988137
No arm packages yet (or sparc, etc.) It may be a couple weeks before they release.
http://cdn.openbsd.org/pub/OpenBSD/6.4/packages/
▶ No.988197
>>961879
>oof
>It's almost as if [...].
>I don't know why (I'm/you're) being downvoted.
▶ No.988216>>988227 >>988266 >>988458
the only thing I hate about OBSD after using it for a few weeks is that it my laptop fan is always running at the lowest level, even with apmd -A. it seems OBSD idle at a command prompt runs about 10C hotter than Linux idle in X. correctness at a cost.
▶ No.988227>>988326
>>988216
Surely there must be a way to set the fans manually.
▶ No.988229
>>961844
And then there's this nigger
▶ No.988266
>>988216
Hmm.. my experience is the reverse (T60)
▶ No.988326
The current release is OpenBSD 6.4, released Oct 18, 2018.
>>988192
That's a direct quote from the main page. Packages for slower arches are usually late since they stopped making CD releases.
https://www.openbsd.org/
>>988227
If anybody ever figures this out, please post the solution. I'd really like to throttle the fans on my T60 and G5 tower and haven't ever found a way to do so.
▶ No.988359
▶ No.988458>>988574
>>988216
shoddy linux ACPI support is better than ACPI disabled by default?
Unagnst BTFO
▶ No.988574>>988909
>>988458
ACPI isn't disabled by default. Modern x86 CPUs can't even run without it.
▶ No.988817
>>988815
nice tinfoil, fuck microwaves
▶ No.988818
>>988815
So this is what /tech/ looks like?
▶ No.988897>>988901
>>961862
tired of this being shilled everytime openbd is brought up.
▶ No.988901>>988931 >>988945 >>989029
>>988897
Then you'll love this one:
Reminder: OpenBSD lacks the following:
>A robust filesystem such as ZFS, XFS, or HAMMER2
>Any kind of journaling FS
>SSD TRIM
>SMT/HT
>NFSv4
>Support for more than one core on various parts of the OS, pf being an example
>802.11ac networking
>Nvidia graphics from this decade
>AMD graphics post-2012
>Certain Intel graphics
>Broadcom wireless
>Bluetooth
>WINE
>LUKS/dm-crypt
>Linux compatibility layer
>Mounting ext filesystems
>mesa
>free(1)
>lsblk(8)
>and more
▶ No.988909
>>988574
Don't blame that shill, their scripts on the technical flaws of this or that are often several years out of date.
▶ No.988931>>989078 >>990015
>>988901
>muh features
An operating system isn't a feature list, faggot. OpenBSD prioritises correctness, code quality, and security over speed and features, only adding new stuff and hardware support when they're satisfied with their implementation. Autistic? Sure. Are the results good? Their work is widely copied and reused in other operating systems so I'd say yes.
That said, here's some comments:
>SMT/HT
It doesn't lack SMT, it's disabled by default in the latest release for paranoia reasons. You can always turn it back on if you really want it.
>Nvidia graphics from this decade
Neither does any other FOSS operating system aside from Linux and NetBSD (FreeBSD if you count the proprietary drivers). Even then, support is shoddy thanks to Nvidia refusing to document anything and intentionally making life difficult for freetard driver writers.
>AMD graphics post-2012
2013*
>Broadcom wireless
Similar situation with Nvidia but less ridiculous
>Bluetooth
What the fuck do you want that for, your gimmicky phone speaker?
>WINE
Go bug the Wine developers if you want it so bad.
>LUKS/dm-crypt
OpenBSD has its own disk encryption system, why ape Linux?
>Linux compatibility layer
What do you want, Steam? Fuck off.
>Mesa
That's a lie.
▶ No.988935
>buy tiny business-class Dell desktop
>physically connect ethernet cable to it
>install openbsd 6.4 (shelling out first to get disk encryption)
>pkg_add -v git
>git clone git://git.suckless.org/dwm
>OpenBSD needs another -I nclude
>git clone git://git.suckless.org/st
>patch in colors
>modify colors to not suck
>add 'exec dwm' to ~/.xsession
>rcctl start xenodm
yeah this is cool
but I'm not going to be sitting in front of this thing often
>rsync .pub key over, put it in ~/.ssh/authorized_keys
>/etc/ssh/sshd_config:X11Fowarding yes
>rcctl restart sshd
>click icon on fagbook that launches 'ssh opensbd "/home/anon/st/st"
>tmux (installed by default)
>put fagbook to sleep
>tmux session continues on secure and sane home server
it beats virtualbox
▶ No.988945>>989078
>>988901
most of these are design choices. they won't be implemented until they can be implemented well. also many are just plain wrong:
>802.11ac is supported
>openbsd's fs (UFS2) is quite robust, supporting pretty much everything: zetabytes disk sizes, softraid, full disk encryption and it is journaling
>WINE and bluetooth (which is supported btw) are both fucking gay, what the fuck is wrong with you?
>broadcom wireless is supported
>R9 series of AMD GPUs are supported (hawaii which came out in 2014)
>mesa is also supported
>TRIM: many SSDs have built in wear levelling these days
>SMT/HT was purposely disabled recently as a result of a fundamental flaw in their design[1] it can be turned back on if you wish
>ext2 and ext3 can be mounted normally, ext4 as read-only
>and more
are there more things you would like to be dishonest about?
[1]https://undeadly.org/cgi?action=article;sid=20180824024934
▶ No.989029>>989078
▶ No.989078>>989591
>>988931
>>988945
>>989029
>replying to pasta
RETARDS
▶ No.989513>>989526
CoC'd insecure Lunix lusers ITT bitching about the MasterOS OpenBSD. All my bottom keks!
▶ No.989526>>989895
>>989513
>cuck license < cuck coc
sorry bsd fag but your cuckery runs even deeper
▶ No.989591>>990193
>>989078
>oh it's pasta
>better let it go unchallenged then
▶ No.989895
▶ No.989918
>>961835 (OP)
it’s only secure by obscurity because it’s literally only installed on 200-300 machines worldwide (seriously look it up)
Linux on the other hand patches exploits all the time.
▶ No.989941>>989981
>>961835 (OP)
Because it's a meme hobbyist project literally made to be used by its own developers and nobody else.
▶ No.989981
>>989941
Yeah, they don't want losers like you. I wouldn't either if I made an OS.
▶ No.990013>>990014 >>990144
>>961835 (OP)
Tried 5.whatever, just before they dropped the module support.
No kernel modules and gimped intel cpu thanks to "muh security" is a deal breaker. I'm also ok to use wangblows and gnu/linux, so no specific need for that. HardenedBSD is a more sane option if you still want to jump in the BSD camp.
>>961862
You should delete the "sustainability" part as OBSD is currently swim in the money at least for now.
▶ No.990014>>990015
>>990013
>gimped intel cpu ... is a deal breaker
heard of Spectre have you mate?
Meltdown?
ring any bells?
▶ No.990015>>990016
>>988931
>What do you want, Steam? Fuck off.
FreeBSD use(d) it mostly for oracle java. Funny isn't it?
>>990014
Justifying the lack of patches? When i buy a cpu i want to use every feature of it especially when it's increase the performance.
▶ No.990016
>>990015
>When i buy a cpu i want to use every feature of it
Sure. So gcc and llvm and such versions matter. But the patches your kernel is getting are impairing performance because they're mitigating Spectre shit. I've had to double RAM on tons of servers simply to account for more processes being resident at any given time because Spectre shit causes them to take longer to run to completion.
▶ No.990144>>990188 >>990194 >>990232
>>990013
>You should delete the "sustainability" part as OBSD is currently swim in the money at least for now.
Ya they have beating their fundraising goals for the last few years. Sometimes blowing it out of the water.
https://www.openbsdfoundation.org/campaign2016.html
https://www.openbsdfoundation.org/contributors.html
▶ No.990176
Because vulkan support matters to me
▶ No.990188
>>990144
>they can afford 5 full time developers if they wasted all of their money on it
yeah they are drowning in funds for sure
▶ No.990193
>>989591
>you must always take all bait
▶ No.990194>>990195 >>990227 >>990228
>>990144
>John Carmack
the problem with these FUCKING WHITE MALES is that if they aren't constantly virtue signalling, they might be secretly based
meanwhile
>try to put OpenBSD on Dell XPS 12 and 13
>the 12 fails when trying to install a bootloader
>the 13 has no touchpad, no wifi, no (usb hub) ethernet even after smuggling all the firmware blobs onto it that were asked for
is this 'thinkpads, the OS' ?
▶ No.990195>>990198
>>990194
>thinkpads, the OS
https://deftly.net/posts/2018-10-15-openbsd-on-lenovo-a485.html
not even that. Look at that shit: nothing works. A laptop that can't even suspend isn't a laptop; it's a shitty desktop.
▶ No.990198
>>990195
If a desktop was 12 inches, ran on a battery, had a built in screen, had wifi.
▶ No.990227>>990246 >>990300 >>990305
>>990194
What kind of FUD are you spreading? It works fucking perfect on my macppc, on my Dell P4, on my Gateway laptop (a network services server), my self built AMD Phenom II system (Gigabyte motherboard), and my ThinkPad X200. You're full of shit, probably sucking Corey's fat CoC, and know you wouldn't have a chance of flipping Lord Theo or the rest of the OpenBSD hacker team. You can't own the whole world, sorry faggots!
▶ No.990228
>>990194
Also Atheism is the masterbelief, being the default position and all. christfags are notorious for being unable to logic well
▶ No.990232
>>990144
>The Foundation received $573,000 in new donations during its 2016 Fundraising Campaign.
During 2016 the Foundation paid out $207,000 to support its activities.
>The Foundation received $376,000 in new donations during its 2017 Fundraising Campaign.
During 2017 the Foundation paid out $201,000 to support its activities.
▶ No.990246>>991116
>>990227
>It works fucking perfect on my [ten year old hardware]
k.
▶ No.990300>>990305
>>990227
It's just the same boring troll, m8. He used to post lame "cuck license" bait before Linux got CoCked and ruined his line. So now he posts even stupider shit. No OS supports all hardware, and especially not immediately. So now you still have a bunch of common ARM boards that Linux doesn't support well.
http://linux-sunxi.org/Linux_mainlining_effort
▶ No.990305
>>990227
>>990300
>What kind of FUD are you spreading?
Here we see the linuxtards reacting to bug reports by sticking their head in the sand and making loud noises.
▶ No.990592>>990914
THIS BOARD DESPERATELY NEEDS IDs
▶ No.990911
>Why aren't you using BSD?
It offers nothing I desire yet don't have with many linux distros.
It also lacks many features I do want.
Why ARE you using BSD?
>inb4 "it has a CoC" is considered a legitimate criticism against an OS/kernel rather than dev politics
▶ No.990914
>>990592
there's already a thread: >>>/metatech/1625
▶ No.991116
>>990246
>>It works fucking perfect on my [ten year old hardware]
Everything made in the last few years is botnet.
PPC4LIFE
▶ No.992045
>>980873
>>980871
why emacs/bsd? and hurd isn't ready, best we have is GuixSD for now.. isn't that the closest we can get to lisp os?
▶ No.992049
>>961835 (OP)
I've just installed it.
▶ No.992064>>992068
Is it true that OpenBSD doesn't really do framebuffer graphics like linux?
▶ No.992068
>>992064
AFAIK it's never done that no
but then I haven't done framebuffer graphics under Linux since the 90s either