I'm finally trying out NetBSD.Where's the right place to stick the pkgsrc/ directory? Should you switch to ZFS or just enable journaling in FFSv2? Can you encrypt swap with cgd? Any best practices or modifications for desktop usage?Discuss NetBSD.
dead os
>>107753348This image is straight out of 2005
>>107753348>Where's the right place to stick the pkgsrc/ directory?/usr>Should you switch to ZFS or just enable journaling in FFSv2?Journaling FFSv2 for now unless you're willing to submit bug reports. NetBSD documentation on ZFS is terrible>Can you encrypt swap with cgd?Yes>Any best practices or modifications for desktop usage?https://www.unitedbsd.com/d/439-netbsd-performance-and-power-management-tweaks
>>107753348literally who?
>>107753348cuck license
Bump for interest >>107753408Do you use netbsd as a daily driver? How does it compare to the other bsds?
>>107753348What is the appeal of NetBSD compared to FreeBSD or OpenBSD?
>>107757747It's like OpenBSD but it can run Wine. I think it's filesytem is a little better and it's not super slow. From what I gather FreeBSD is the better server OS and it's not close. Someone else with more experience should correct me though.
>>107757747it's neither obsessed with security nor caters to big corpos for gibs
>>107757747All foreign packages being in its own heirarchy under /usr/pkg/ including it's own /usr/pkg/etc/ directory is nice
>>107757747it's deader than those
pufferfish wit da big ass lip
>>107757911What are you doing here
>>107757470>Do you use netbsd as a daily driver? How does it compare to the other bsds?YesIt's a comfy OS. It reminds me of Solaris. Same SunAudio audio system, the M2 scheduler, autofs etc.
>>107758441also ZFS. But it's not very stable.There's nothing like zones though.
Good luck install it in baremetal, it literally have no drivers
>>107757946spreading whimsy and happiness
>>107758480>it literally have no drivers>it literally supports more hardware than anything else on the planetWhat did he mean by "no drivers"?
>>107758629I assume he's talking about GPU drivers.AMD drivers are generally there but a bit behind Linux.I'd rather cut my dick off than try to use a current gen Nvidia card with any BSD variant.
I run it on my old as fuck Thinkpad T42 with IceWM cause it's about the only thing that actually runs on it these days. It's sorta dead feeling as an OS, but stable as all fuck. I don't use that laptop much, except for when I feel like torturing myself. Core os is not too different from the other BSDs. I wouldn't use it for a desktop really unless you have only a potato at your disposal. Main appeal is that it runs on everything really but that's about it.
>>107757764Wine in NetBSD is severely outdated though. If you want to run wine, definitely FreeBSD.
>>107758453Do they use OpenZFS? Why would it be less stable?
>>107757747It can still run on 1980's era Macintoshs as well as toasters, arcade machines, and the Sega Genisis.
>>107753348>weevis he still doing anything
>>107758876https://pkgsrc.se/emulators/wine>2025-10-24You can also build Proton as it has official support for NetBSD upstream.
>>107753368It's probably been that long since anyone actually used it. I haven't heard really anything about it since that time period and am surprised that it's still going.
>>107761484>Branch: CURRENT, Version: 9.0nb10, Package name: wine-9.0nb10, Maintainer: pkgsrc-usershttps://www.winehq.org/news/2024011601>January 16, 2024>The Wine team is proud to announce that the stable release Wine 9.0 is now available.>This release represents a year of development effort and over 7,000 individual changes. It contains a large number of improvements that are listed below. The main highlights are the new WoW64 architecture and the experimental Wayland driver.And 11.0 may come out these days.
>>107759765No. ZFS from Illumos>Why would it be less stable?Not a lot of people use it so it does not see a lot of testing
>>107757747It can run rumpkernels as userspace processes for added security. All filesystems are implemented like that for removable devices, as such, you don’t risk getting raped each time you use a usb storage key
>>107757747It has, by far, the best documentation of any available BSD. The sources are kept simple, and well organized. The kernel interfaces are very stable and documented in the manual. If you write C and want to improve an OS writing drivers or utilities, NetBSD is the most accessible of all
>>107761649>January 16, 2024> severely outdatedIt's like 2 years, It's nowhere to be "severely" outdated considering it's non-essential you updooter faggot
>>107762715I have read the rumpkernel projects is kinda abandoned by a couple of years, just as the lua in the kernel>>107762834>It has, by far, the best documentation of any available BSD.Meh. To be honest the netbsd internals documentation still has a lot of TODOs sections for like, I guess, at least 15 yearsThe 3rd party documentation of FreeBSD and OpenBSD make up (although they have great official documentation by themselves) for the eventual marginal better docuementationNetbsd doesn't have anything like> "Design and implementation of freebsd operating system"https://github.com/iceqp/books-1/blob/master/The%20Design%20and%20Implementation%20of%20the%20FreeBSD%20Operating%20System%20(2nd%20Edition).pdf Or the collections "Absolute [Free|Open]BSD" by Lucas
>>107762834Every BSD boasts having the best documentation.
>>107762834>DocumentationFor the operating system itself, maybe.But for the rest of the userland, Arch wiki is still more comprehensive.
>>107767754>why doesn't the kernel documentation cover userland>>107757747running ancient machines after everything else has dropped supportrump kernels are/were cool from a developer perspective
>>107767754>Arch wiki is still more comprehensive.The Arch wiki is garbage compared to the old Gentoo wiki. The Arch wiki is basically just a how to for running systemd and it isn't even good for most of that. Good luck finding any information beyond something like:>run this command in terminal because we say so.Nothing is explained in in-depth. Just go look at the horrible page for input devices.Meanwhile, the FreeBSD, OpenBSD and NetBSD handbooks+man pages clearly explain every part of the base system and why things are configured a certain way by default. Then they go further and walk you through plenty of non-default options that you might want to enable/disable for whatever reason.The entire stack in the Linux world these days is a horribly unmaintained undocumented mess. Everything down to the GNU libc barely has any documentation at all. systemd is a black box. Most of the drivers for things like GPUs are a black box. The audio sub-system is still a tangled mess of hacky code that barely works and most people that claim to be "experts" at things like ALSA don't even know why their random commands and config changes work. They just throw random shit at the wall until they get working sound then say it's good enough until it breaks on its own again. Don't even get me started on shit like pulseaudio and pipewire.There is absolutely no comparison between a distro like Arch and the BSDs. Most of the shit in GNU's userland doesn't even provide man pages at all.You're better off spending time learning the BSD systems if you want to understand wtf is going on in modern Linux. It'll at least give you a good foundation for how things are supposed to work before you go wading through the horrible mess Linux's kernel and userspace has become in the last 20 years.It's very obvious that the majority of the people that insist on coming to BSD threads to proclaim how great Linux is do not even know how their own OS works.
