4,378 karma · joined December 10, 2013
You can get GPU accelerated YouTube videos in OpenBSD, provided you have a supported GPU in the first place. You have to use Firefox and enable gfx.webrender.all and layers.acceleration.force-enabled in about:config. I've been able to get up to 2Kp60 smooth as butter on Intel HD 530 graphics in OpenBSD 7.0. 4Kp60 plays and drops a few frames, but my monitor is 2K so I have no need for 4K playback anyway.
Two of my Linux workstations are Sandy Bridge and Kaby Lake, and my real world experience bears this out. I can't distinguish between the two for everyday use cases; only synthetic benchmarks show any real advantage in the newer system. I can't speak for Windows performance differences, as my only Windows system is my gaming rig with a Ryzen 5 3600, which of course trounces both of the workstations no matter the OS.
For Microsoft on the other hand, this is breaking new ground with Windows users. Microsoft has slowly been easing their users into a OS-as-a-Service paradigm, the next logical step for them is to require your credit card info (which to be clear, isn't required...yet) to continue to use the OS on the computer you bought outright. After all, the other major software players are pushing subscriptions instead of license purchases (Adobe, Parallels, Codeweavers, and Microsoft themselves with 365, among so many others), so why not charge a fee to use their preloaded and -- in the eyes of the average consumer -- required OS?
Maybe it's just me, but I do this at work all the time. I create build sheets out of just plain text before I fire up the circuit simulator, so I've got a good mind map of it and something to refer back to. Granted I'm not dealing with advanced circuits, it's usually industrial machinery and motor control, or at most a simple digital timer circuit, but I do just fine with plain text for something highly technical.
Today, the OpenBSD installer literally does all of that for you. It sets the /etc/installurl to a sane default (the OpenBSD CDN URL), it does WiFi autoconfig even if your firmware is not available yet, it has an automatic partitioning feature, and it attempts a firmware update, all before you reboot the first time. Sure, there are a few after-boot setup steps left to do, but no more so than in Slackware 15.0. Both OSes give you a command line after install, both expect you to tweak the OS to your own needs from its base configuration, and OpenBSD even helps you set up your regular user account in the installer rather than leaving you to do it afterwards as Slackware does.
This is why I don't like to talk about systemd on any internet forum; it always leads to people like you ready to attack any position around the subject, and me having to defend a position I don't even hold (I don't think systemd sucks, I think its developers could do better though). I am done with this thread.
https://bugs.freedesktop.org/show_bug.cgi?id=76935#c10
----- Adding "hacks" but not testing to ensure said hacks don't cause issues:
Lennart Poettering 2014-02-21 13:49:25 UTC
To make this work we'd need a patch, as nobody of us tests this.
Comment 3 Michael Shigorin 2014-04-04 06:30:57 UTC
Hope all of you either test all the combinations or do not break at will those you don't have the time and inclination to test, at least in system-wide components that are not specific to systemd, while pushing the latter hard.
Comment 4 Lennart Poettering 2014-04-04 14:56:43 UTC
Well, cgroups-less kernels are explicitly not supported by systemd. However we added some hacks to allow it to boot to a certain degree even if a lot of things will not work correctly afterwards. In this mode when you boot you will actually get a warning on screen and bootup is delayed by 10s to make sure the user understands this.
Now, this mode recently broke, and it will segfault early on. I am happy to take a patch to 'fix' this again, but I will not work on this as i dont run kernels like this, and as mentioned its not really supported anyway...
Another option is to simply be honest amd stop supporting in entirely, and refuse booting completely. And I figure this is what I will eventually do if nobody cares enough to send me a patch to fix that segfault.
Again, I didn't want my comment to start a heated discussion about systemd, but inevitably that happens. If I had praised it someone else would have come along to tell me how much it sucks (I don't think it sucks, personally, I just have issues with its current development process).
Hopefully this guide will stay up to date given the "move fast, break things, wontfix" approach the systemd authors currently have with the project.
I still hang on to a PIII based Dell Latitude laptop from 2001 and Slackware -current runs surprisingly well on it (along with BeOS 5.1 from my original disc, QNX RTOS, OpenBSD, NetBSD, and a few other obscure OSes from its generation to today).
USB flash drives were a massive leap forward in sneakernet data shifting.
[1] https://www.codeweavers.com/crossover#linux
[2] https://forums.macrumors.com/threads/crossover-and-bottles.5...
It's not because they believe in open source and free software, it's more that they realized they can coexist with and even benefit from helping such projects. It's a beneficial means to a selfish end, but it's better than the old Microsoft who just wanted to destroy anything related to Linux and free software out of pure spite.
Now that I think about it, it definitely could be USB related on those other machines too. I've used the same cheap USB KVM for years and it has polling issues in Windows 10, I didn't even consider that might be the source of my issues elsewhere. I'll try it without the KVM and see what happens. Thanks!
The problem, as others have said, is the lack of dedicated manpower. This is one of those situations where I wish I was a developer, I'd dive right in and try to get Haiku to daily-driver stability on the platform. There is work being done on porting to ARM already, and my hope is that as the X86/64 platform matures, focus can shift to ARM and the Pi specifically.
My biggest issue running Haiku bare metal has persisted across hardware and form factors though: Stability. I can't seem to keep a machine running for more than a few days without a kernel panic or a frozen GUI. I haven't tried the latest snapshot on my "newest" acquisition, a Haswell era HP EliteDesk castoff from work, it's my project for this coming weekend and I'm looking forward to seeing how long I can keep it running.