61–70 of 107 posts
Since SystemD has become so prevalent in Linux, I've been looking longingly at BSD. The only problem is that I have a large number of machines that I'd need to move over, and it's a pretty intimidating amount of work. But I'm planning on beginning the move, one system at a time...
Take a look at GhostBSD while you're at it. I wouldn't recommend OpenBSD for normal day-to-day usage....
>If you install a library, there is no split between library and header files. There is no zlib-dev package as an addition to zlib. You get everything at once. And that's good?
>If you install a library, there is no split between library and header files. There is no zlib-dev package as an addition to zlib. You get everything at once. And that's good?
well, it's what happens if you actually install a package from source, and so is congruent with what it really means to 'install ' seems preferable to accepting arbitrary segmentation of packages into subsets based on some random package maintainers preference.. also, it's not 1993 and having 100kb of headers on my system is not really a big deal.
Since SystemD has become so prevalent in Linux, I've been looking longingly at BSD. The only problem is that I have a large number of machines that I'd need to move over, and it's a pretty intimidating amount of work. But I'm planning on beginning the move, one system at a time...
I use daily two fine linux distributions that do not have systemd: void and slackware. It is a real pleasure to run htop and see that all the running processes do not even fill a 25-line terminal.
I can confirm that acme-client so far is the only sane client I've seen. No nonsense of multi-megabyte downloads of endless Python scripts or esoteric bash scripts. Just good old C tool as it should be. Every *nix should use it by default.
Since SystemD has become so prevalent in Linux, I've been looking longingly at BSD. The only problem is that I have a large number of machines that I'd need to move over, and it's a pretty intimidating amount of work. But I'm planning on beginning the move, one system at a time...
Systemd is indeed prevalent, but you can very well use linux without it (and it is much better!) I use daily two fine linux distributions that do not have systemd: void and slackware. It is a real pleasure to run htop and see that all the running processes do not even fill a 25-line terminal.
What are the desktop GUI environments or window managers available on OpenBSD that are comparable to those on Linux? I see a mention of running X as a user, but nothing more. What about desktop hardware support? Does it have working drivers for different WiFi chipsets, video cards, trackpad, etc. (referring only to x86 based systems)?
>What are the desktop GUI environments or window managers available on OpenBSD that are comparable to those on Linux? I'll answer this honestly; All of the X11 based ones until SystemD and wayland came about are essentially supported or working. Gnome created a hard dependency on systemd and thus can't be used any longer on openbsd. Wayland (and thus; Sway) is not supported by OpenBSD. But i3, xmonad, KDE4, XFCE4 and…
Since SystemD has become so prevalent in Linux, I've been looking longingly at BSD. The only problem is that I have a large number of machines that I'd need to move over, and it's a pretty intimidating amount of work. But I'm planning on beginning the move, one system at a time...
After ~20 years of using Debian, I switched my desktop PC to OpenBSD about a year ago due to concerns about the direction Linux has taken (eg. systemd).
It was easier to set up the kind of minimalist desktop I like than on Debian, where I have to change a lot of defaults (eg. switching to sysvinit). The package manager is great, and there are ~10k packages available for 6.4. I'm now looking at switching my server to OpenBSD. I'm keeping some dedicated audio workstations on Linux for now (need the raw performance and drivers), but my impression of OpenBSD so far has been very good.
OpenBSD caveats: Video and audio can be a little glitchy. Releases are only supported for one year. ABI can change between releases. There's no filesystem journal. The only non-BSD filestems supported are msdos and ext2fs (and read/write speeds on those are slow).
> Xserver without root permissions There must have been a regression. There still was lingering suid root binaries that OpenBSD got bit by recently. I mean, it was security fix #1 for release 6.4: https://www.openbsd.org/errata64.html
AFAIK that suid binary was used to enable starting the X server without a display manager. It still actually ran as non-root.
Last time I tried the full disk encyrption [sic] it was an awful setup compared to Linux. > https://why-openbsd.rocks/fact/meltdown-spectre/ Uh, yeah. They did that, just like Linux did before them. I especially like the reply to the announcement that was "uh… I hope you didn't spend these two months coming up with that solution. We already did that for Linux, so you could have just asked".