Yup. I'm running -current on 2 machines and it kicks my ass every now and then. But these aren't production machines, so it's not a big deal.
One thing I didn't mention is that it is technically possible to re-package the binary RPMs provided by AMD, but I don't know if anyone has done that for slackware yet. I don't suggest taking that on since it is an entire workload in addition to whatever else this machine is doing. That said, I may be able to take a look at it this weekend. It might be as simple as running rpm2tgz over and over, which, if so, I could probably get some packages going for 14.2. Maybe, I'll have to set aside some time to fiddle with it. As for 15.0, I honestly think the only reason it's been so long is because of the webstore BS. Keeping the dev team small makes an obvious positive impact on the quality of the distro, but there are downsides :-( On Tue, Sep 10, 2019 at 4:17 PM Rich Shepard <rshep...@appl-ecosys.com> wrote: > On Tue, 10 Sep 2019, Ben Koenig wrote: > > > If upgrading to -current is an option, the hardware you have will work > > out-of-the-box. > > Ben, > > Over all the years I've run Slackware I've read that -current should not be > used on production machines. Since this new desktop will be (as soon as I > get backup software properly working) my daily workstation and postfix, > postgresql, etc. server I need stability and reliability. Sigh. > > It's been a long time since Pat and crew issued an update (there used to be > 3 minor versions between major version upgrades) so I hope 15.0 is out Real > Soon Now. > > Thanks, > > Rich > _______________________________________________ > PLUG mailing list > PLUG@pdxlinux.org > http://lists.pdxlinux.org/mailman/listinfo/plug > _______________________________________________ PLUG mailing list PLUG@pdxlinux.org http://lists.pdxlinux.org/mailman/listinfo/plug