61–70 of 81 posts
Something like 99% of the use cases I've seen for OpenBSD are servers that have no keyboard, mouse, video, audio or other plugged into them. It's completely unsurprising that bluetooth and gamepad support isn't a priority.
The rumor is that OpenBSD devs run it on Thinkpads while most FreeBSD devs are using MacOS as their main OS.
Earlier quoted context omitted.
> If you have SSD->LUKS->GPT->LVM->Ext4, then a bug on any of the (newer, buggier) components before your journaled FS means you lost data And yet it's never happened to me. Dozens upon dozens of systems. Linux or Windows or Mac for that matter. I've toted around a laptop with whole disk encryption for > 15 years and never lost data. Not once. Even after a forced power off. I have, however, lost data to major FS corr…
> I've toted around a laptop with whole disk encryption for > 15 years and never lost data. me too. Until I did. Negative anecdotes in a discussion about rare events are unhelpful. My point is not that journaling is useless and should be dropped (I only use openBSD in things that are either readonly storage or virtualized on a host which does have proper FS). My point is that the "new setup" used by most distros intr…
Something like 99% of the use cases I've seen for OpenBSD are servers that have no keyboard, mouse, video, audio or other plugged into them. It's completely unsurprising that bluetooth and gamepad support isn't a priority.
Earlier quoted context omitted.
Most setups nowadays do full disk encryption outside of the FS, so the journal doesn't help much. If you have SSD->LUKS->GPT->LVM->Ext4, then a bug on any of the (newer, buggier) components before your journaled FS means you lost data.
> If you have SSD->LUKS->GPT->LVM->Ext4, then a bug on any of the (newer, buggier) components before your journaled FS means you lost data And yet it's never happened to me. Dozens upon dozens of systems. Linux or Windows or Mac for that matter. I've toted around a laptop with whole disk encryption for > 15 years and never lost data. Not once. Even after a forced power off. I have, however, lost data to major FS corr…
OpenBSD supports UEFI.
This was interesting to me. > I have grievances against OpenBSD file system. Every time OpenBSD crash, and it happens very often for me when using it as a desktop, it ends with file corrupted or lost files. This is just not something I can accept. Doesn’t openbsd use a fancy-ish ZFS type file system? I have the same grievance with XFS on Linux though. For as much as people say how awesome it is, the few nodes I have…
This was interesting to me. > I have grievances against OpenBSD file system. Every time OpenBSD crash, and it happens very often for me when using it as a desktop, it ends with file corrupted or lost files. This is just not something I can accept. Doesn’t openbsd use a fancy-ish ZFS type file system? I have the same grievance with XFS on Linux though. For as much as people say how awesome it is, the few nodes I have…
Nope. FFS2.
I keep a special laptop for all financial stuff. It is not that expensive and the inconvenience is limited. And on it I have CubesOS, but I guess OpenBSD would also be a good choice.
I assume you meant QubesOS not CubesOS which I don't know of. You can totally run QubesOS as a host, it helps for hardware compat and fs perf/stability, and run OpenBSD alongside Fedora or Debian VMs as guests.
> flatpak: I really like software distribution done with flatpak, packages are all running in their own namespace, they can't access all the file system, you can roll back to a previous version, and do some interesting stuff As of today flatpak still has holes you can drive a truck through.
I still don't understand the slapdash approach the desktop Linux crowd took, Qubes is a much better approach. Such unprofessional software engineering pervades FLOSS with the worn and tired "but it's a hobby project" when it's a core dependency necessary for international corporate, government, and military strategic systems. (I also don't understand the lack of appropriate support for critical projects either, but i…
> flatpak: I really like software distribution done with flatpak, packages are all running in their own namespace, they can't access all the file system, you can roll back to a previous version, and do some interesting stuff As of today flatpak still has holes you can drive a truck through.
I still don't understand the slapdash approach the desktop Linux crowd took, Qubes is a much better approach. Such unprofessional software engineering pervades FLOSS with the worn and tired "but it's a hobby project" when it's a core dependency necessary for international corporate, government, and military strategic systems. (I also don't understand the lack of appropriate support for critical projects either, but i…
Earlier quoted context omitted.
OpenBSD had Soft Updates, which isn't really journaling but sort of similar. It was suppose to help with with file system integrity, in the case of crashes. OpenBSD removed it last year because it got in the way of VFS updates, and was hard for the team to maintain[1]. I love OpenBSD, but it really does need a modern filesystem. The current team might be to small or just not have the right people to do a new filesyst…
BSDs bet on permissive license hoping companies would drop code on them. Turned out companies were either using linux or dumping abandoned code as GPL to strategically keep out of competitors. BSD licenses were a thing before GPL lost the final battle, when linus accepted the tainted-kernel compromise. Now it's a relic of a bygone time, which show allegiance to a side on a war that no longer matters.