3 ms·
> That's what Slackware was supposed to be After many many years of using Slackware, I still believe NetBSD was used as inspiration for the design of Slackware
by jmclnx 3y ago
> That's what Slackware was supposed to be
After many many years of using Slackware, I still believe NetBSD was used as inspiration for the design of Slackware.
BTW, I really like pkgsrc, I wish that ended up being a standard for Linux instead of all the multiple package/dependency managers that exist.
And NetBSD is really my favorite BSD, I only wish it worked without a minor hardware issue on the Laptop I have. I may end up putting in a PR for 10.0 BETA once I am sure of the issue.
- NikkiA 3y agoMore likely 386BSD than NetBSD back then, although the timeline between the two is only a year and a bit apart. Back in '92 I was interested in 386BSD, but told to check out linux (which was at 0.12 at the time), back then it was the root/boot disk distro, then mcc, then slackware.
- exikyut 3y agoWhat's the minor hardware issue?
- jmclnx 3y agoI have a Laptop with 2 video Chips, Intel and Nvidia. The Nvidia chip gets very hot, even when I disable it on boot. The CPU Temp stays low. The Nvidia chip is in the lower left corner of the Laptop, and it cannot be disabled by a BIOS Switch. Since NetBSD has Nouveau support, I want to be sure 10.0 BETA supports that specific chip before deciding what to do. FWIW, same thing heat issue happens with OpenBSD, but OpenBSD has no Nvidia support, luckily OpenBSD is able to ignore it. Slackware, no issue with Nouveau and heat.
- exikyut 3y agoI see, interesting. Definitely sounds like a kernel thing, and I honestly wonder if it isn't a BIOS/firmware issue with the Nvidia GPU handling incomplete initialization sanely. I wonder what would happen if you just tried booting DOS or some other OS on the thing. Or just sat in the BIOS? If booting into something barebones leaves everything cool, and depending on how long it takes for the chip to get warm, perhaps you could move a `for (;;);` further and further down into the OpenBSD kernel and find the point things get cranky that way. Extremely hacky approach though, I'll definitely concede that point >.> (But if you want to try it, I would wholeheartedly recommend looking into something like iPXE, which would let you download each test kernel over HTTP at boot time and make the iteration process tolerable. This assumes you have a second machine though...)