Bleeding Edge BSD reddit / BSD ---------------------------------------------------------------------- reebs12 · 2018-04-04 15:32 Hi Folks, I was wondering if there is any equivalent to Arch Linux in the BSD world? You know, rolling release, seeking to get the lastest version of software... ---------------------------------------------------------------------- rushsteve1 · 2018-04-04 15:44 FreeBSD CURRENT maybe? The ports tree or equivalent in most BSDs is usually very up to date anyway. ---------------------------------------------------------------------- deux3xmachina · 2018-04-04 15:49 All BSD's have the option to run snapshots or even just rebuild/upgrade using the "master" source repo and use software from the ports collection, so both yes and no. None of them are nearly as unstable as Arch, so it's really your pick on what interests you most. ---------------------------------------------------------------------- reebs12 · 2018-04-04 16:02 Arch is not unstable. At least for me. ---------------------------------------------------------------------- deux3xmachina · 2018-04-04 16:04 Glad you had that experience, many others would disagree. Point remains. ---------------------------------------------------------------------- reebs12 · 2018-04-04 16:09 Have you used Arch Linux yourself? Which problems did you have? ---------------------------------------------------------------------- Smallzfry · 2018-04-04 16:14 Newer packages aren't always tested nearly as well, so there's a much higher chance of running into hardware issues. Also, if you don't update frequently then you can end up with dependency problems that prevent core functions from working, although I don't know anyone personally who has let it lapse that bad. ---------------------------------------------------------------------- MaxPayneNoir · 2018-04-04 16:16 Hi, all BSDs have rolling-release/cutting-edge develop branches ('CURRENT' branch) containing all the new features and packages. a snapshot/nightly-build for the preferred arch can be downloaded and installed quite easily. All new additions/changes in system/software commits can be tracked on the respective mailing lists/news feeds: you can join the *BSD-current communities on mailing lists and IRCs. - [OpenBSD -current](https://www.openbsd.org/faq/current.html) - [NetBSD-current](https://www.netbsd.org/docs/current/) - [FreeBSD CURRENT](https://www.freebsd.org/doc/handbook/current- stable.html) However, If what you're looking for is a bleeding-edge BSD with a binary package management system, then [TrueOS](https://www.trueos.org/) is probably a more advisable choice ---------------------------------------------------------------------- MaxPayneNoir · 2018-04-04 16:32 personally i only used Arch for 2 weeks in my life (first experience with systemd and didn't like it; on the plus side I wasn't happy enough with community and moderation on forums/IRCs, nor with the AUR thing) , however it looked quite stable to me; personally I can't criticize Arch from this point of view. On the other hand, current BSD branches are very stable, so you shouldn't worry about this ---------------------------------------------------------------------- deux3xmachina · 2018-04-04 17:06 Yes, I used to run Arch exclusively for a period of about 2yrs. In several upgrades my GUI wouldn't work, my kernel and initramfs failed to boot properly, systemd systemd'd all over the place causing much confusion, and frequently ran into conflicts with libraries for certain packages causing me to pick one XOR the other to complete the upgrade. It was a pretty decent system when it worked, but I never knew how long that would last. After switching to \*BSD entirely, I know when I'm responsible for my system breaking, what I did, and how I can fix it. The same simply was not true of Arch, but I'm glad I used it, as it helped me get more comfortable with the command line and how to troubleshoot \*NIX systems Edit: additional note about my time with Arch (and technically every other Linux): audio has never been a bigger pain in the ass to configure, troubleshoot, and maintain. On my BSD systems, I only need to set a sysctl and it's set for all applications. It was confusing initially, but it has not been a continuous headache just to get audio going to the right device consistently. ---------------------------------------------------------------------- nekros99 · 2018-04-04 17:25 I’d highly recommend against using -current releases (at least for NetBSD), if more packages is what you want. The soname requirements for packages are often not bumped (the packages require unbumped sonames but they are bumped in base) and sometimes symbols are missing. They are only meant for testing purposes. ---------------------------------------------------------------------- yourhelpfulfriend · 2018-04-04 17:30 OpenBSD -current has worked very well for me. Many other people will say the same. [If you read about their release process](https://www.op enbsd.org/papers/asiabsdcon2009-release_engineering/) you'll find that they place a unique emphasis on keeping their development branch in a working state. ---------------------------------------------------------------------- rkoberlin · 2018-04-04 18:09 It's a pretty widely accepted truth that if you keep a single Arch installation long enough you will inevitably encounter a situation where you have to decide if it's easier to fix whatever broke during the update, or just nuke and pave. Arch as a learning experience is a wonderful thing, but for production use BSD is just better. ---------------------------------------------------------------------- thfrw · 2018-04-04 18:23 A few years ago, before jumping on the BSD train, I ran Arch and was pretty excited about running *cutting edge* by updating the rolling release regularly. All the excitement vanished when X11 broke after an update with no ready way to fix or revert and I was essentially stranded without a working graphical desktop. Not sure if things changed over at Arch Linux since then, but I haven't had such issues on OpenBSD-current and have no good reason to return to try it. ---------------------------------------------------------------------- rkoberlin · 2018-04-04 18:31 I don't think they have. A guy that I work with was running Arch on his workstation, and an update broke Wayland. He eventually got it up again by removing Wayland and switching to X, but whenever he moved the cursor from his middle (vertical) monitor over to his right, it would spawn a second cursor in his middle monitor. He lived with this for about two days before switching to a Mac. ---------------------------------------------------------------------- BumpitySnook · 2018-04-04 18:43 FreeBSD CURRENT's got a binary package management system as well ;-). ---------------------------------------------------------------------- deux3xmachina · 2018-04-04 19:05 Honestly, even for the learning experience there are better ways to go about it, they just aren't as popular. I can say I'm glad I *ran* Arch, but would never recommend it to someone. ---------------------------------------------------------------------- MaxPayneNoir · 2018-04-04 19:07 is software packaged for CURRENT? yes , there are, just checked....thanks ;) Believe it or not, I wasn't aware of this, always used to compile from source on. How safe/stable is it to use binaries on CURRENT? ---------------------------------------------------------------------- ashfixit · 2018-04-04 19:11 TrueOS tracks FreeBSD 12-current.. For a nice desktop distro and pretty pkg management. ---------------------------------------------------------------------- techsnapp · 2018-04-04 20:24 I agree! ---------------------------------------------------------------------- apancetta · 2018-04-04 21:37 in the BSD world the packages and base are separate things, so you can use a stable base and current packages. For packages: Everything is close to bleeding edge, because they don't have the resources to backport patches for years like Debian. You can go more bleeding edge by having -current, it's a little more painful but not very different. for base: there is a long term stable for all of them, and -current is a big difference. e.g. on netbsd often there's no hardware support on stable releases and you will want to use -current. most developers use it so it rarely stays broken for long. ---------------------------------------------------------------------- BumpitySnook · 2018-04-04 23:20 Generally works just fine. ---------------------------------------------------------------------- kstoneman · 2018-04-04 23:27 OpenBSD -current also has binary package management ;-). In fact, whenever I update -current, I immediately run 'doas pkg_add -u -D snap' afterward and all my packages are automagically updated. ---------------------------------------------------------------------- jggimi · 2018-04-05 02:36 > you can use a stable base and current packages Not on OpenBSD. It is explicitly **not** a supported capability. ---------------------------------------------------------------------- devnexen · 2018-04-05 08:40 That's correct, you do not want to try this if you do not want issues. ---------------------------------------------------------------------- devnexen · 2018-04-05 08:43 From experience, all major BSD (DragonflyBSD included) work fine in the what is called the -CURRENT context. FreeBSD has no issues running both ports compiled from sources and the binaries kind together (as long the port did not get the broken flag in the meantime), done that for couple of years. OpenBSD, base and ports must match otherwise work correctly which is consistent, e.g. if you want to work in current/last bleeding edge context, the port versions must follow ... ---------------------------------------------------------------------- dannomac · 2018-04-05 13:50 "Unstable" can have multiple meanings. One of them is crashes a lot, another is changes a lot. Arch is certainly the latter. FreeBSD- CURRENT, OpenBSD-current, NetBSD-current, and Dragonfly-unstable are also the latter. ---------------------------------------------------------------------- dlyund · 2018-04-09 16:30 I have used Arch. It was the last in a long line of Linux distributions I used, around the time systemd infected everything, before moving onto FreeBSD and settling on OpenBSD. I run OpenBSD on laptop, desktop, and we now use it exclusively on our servers at work. I lost track of the number of times Arch exploded on me. Thankfully I wasn't using it for anything particularly critical. I've never had that experience with OpenBSD. It [pretty much] works out of the box and easily goes the 6 months to a year that I usually leave between updates. I haven't run OpenBSD -current as I don't want the hassle of a rolling release anymore but I've heard good things. ---------------------------------------------------------------------- reebs12 · 2018-04-09 19:21 I am sad to hear you had a bad experience with Arch. As a bleeding distro, and as 'unstable' as it might be, it is by far my favourite distro of the *NIX world. ---------------------------------------------------------------------- dlyund · 2018-04-09 19:56 Arch was great back in the good old days. I chose it because of it's relatively clean design and simple configuration. I used Arch solidly for a few years before systemd came in and then most of what I loved about Arch was lost. It turns out that the BSD systems (OpenBSD in particular) have a much cleaner design and simpler configuration than even Arch did, back in it's hayday. I don't miss it. If I was going to run Linux today I'd probably try Void and Alpine but I don't see that happening. OpenBSD does everything I want or need and if it doesn't I'm confident I'll find what I'm looking for among the other BSDs e.g. ZFS or HammerFS for storage. ---------------------------------------------------------------------- Hinulog · 2018-04-25 21:02 Sanity.