Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

seriously the best operating system i have ever used, and i've tried ubuntu, debian, alpine, gentoo, osx, windows, solaris, freebsd, netbsd, openwrt.

it's also one of the best products i have ever used, staying consistent, being well documented, extreme application of principle of least surprise. learn it once, use it forever kind of product.

regularly scheduled updates, extreme focus on technology, hardly any politics. if we want software development to become engineering, this is probably what it's going to look like.



I do not know why you are being down-voted, but I agree with you.

Plus with 7.4 you can use ktrace(1) to find memory leaks, I have been waiting for this release since it was announced a few month ago.

No more third party applications to look for leaks :)

FWIW, upgrading is the easiest of any OS I have work with.


The number of security innovations they have originated or adopted is impressive.

https://www.openbsd.org/innovations.html

OpenBSD just refuses many things that are must have, like Nvidia, ZFS, .. so it's not a option for all things. For things it can do, it's often the best.


Let us know when you can add "journaling file system" to the list.


> Soft updates (softdep) have been disabled for future VFS work [See earlier report].

Hopefully some acceptable filesystem will be added in the near future.


A port of Dragonfly BSD's HAMMER2 is being worked on[0], but that repo also has this bit:

"This repository will be abandoned once Linux or FreeBSD is stabilized with write support. OpenBSD is not the main area of interest."

[0] https://github.com/kusumi/openbsd_hammer2


i have never had a problem with the filesystems.


Good for you. I had.

On OpenBSD 6.x, after power outage/intel drm kernel freeze I had catastrophic data losses. This is not acceptable for me on a desktop/workstation OS. Linux FS stability is better since the 2.4 era in my experience.


I wasn't quite as bad for me, but every once in a while, after a power outage (or the very, very rare kernel panic), I need to get out the laptop and the serial cable to manually fsck my headless server box, because the automatic fsck wouldn't continue on its own.

It's pretty annoying, to say the least. But OpenBSD is such a fantastic system overall, I keep using it, and just wait for them to adopt a journaling filesystem. (And have good backups.)


I really liked the trunk (4) virtual network device, and lots of small stuff, and the barebones experience had its own appeal.

Now that softdeps is disabled and the vfs getting an overhaul I might try it again... in a few years.


You've never had to fsck a 10TB spinning disk then...


[flagged]


Look, I'm a big fan of OpenBSD (and use it myself), but journaling filesystems are many decades old at this point, and they have very clear advantages. One is not to have to sit through an excruciatingly long fsck after a power outage, with a real chance to lose data. This is not an esoteric scenario.

OpenBSD will be better once it adopted a journaling filesystem, until then nobody claimed it's "bullshit".


Is spinning rust esoteric now? Is fsck esoteric? If so, when did that happen?


In 20 years of running Linux on spinning rust I've not had to fsck. *Knocks on wood*. My first Linux FS was ext3.

Correction: I realized I've run it in vain attempts to recover SD cards. It always failed.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: