NetBSD noob question: what’s going on with this command? Is pkg_add not a package manager? If you already have pkg_add why do you need pkgin? I am familiar with `pkg` on FreeBSD, and `pkg_add` on OpenBSD, but they are both perfectly good enough on their own, I never wanted to install another package manager.
I set it up on an Arm SBC last year and I have to say it did not seem as involved a process as that blog post. I hope it hasn't become more complicated.
I've been trying NetBSD 11.1 on an RPi1 these last few days.
It takes a long time to install anything and I don't expect to surf the web on it, but it's nice to have this OS as an option.
I wanted to try out openconnect-saml on it, but the install failed because of lack of RAM/swap. I have managed to run xfreerdp over openconnect on it though (FreeBSD had better performance).
Read the original gemini version then. I have not looked at it, but gemtext has no support for setting fonts at all, so it can not use a font you dislike unless you set that up in your gemini client.
He's got me thinking I could recreate something that looks like 4dwm and put my NetBSD Pi into a defunct O2 case. A "good" O2 from 96-97 would have been 200MHz w/ 256MB of RAM and a 1600SW display (1600x1024).
You lost me there. Why are ppl still using this electron monstrosity when there are so many better alternatives? (Like dd, WIN32Imager, USBImager, DiskImager, etc.)?
I mean, Etcher is bigger than the entire NetBSD image, what the hell?
They're probably commenting on Linus Torvald's decision to accept commits that may or may not have been assisted with agentic coding in part or whole, getting accepted/rejected on a merit basis instead.
(Apparently that's too much gray area for some zealots)
NetBSD noob question: what’s going on with this command? Is pkg_add not a package manager? If you already have pkg_add why do you need pkgin? I am familiar with `pkg` on FreeBSD, and `pkg_add` on OpenBSD, but they are both perfectly good enough on their own, I never wanted to install another package manager.
They have a nice wiki page around running on Arm which might be helpful (and subpages for the main boards).
https://wiki.netbsd.org/ports/evbarm/
I set it up on an Arm SBC last year and I have to say it did not seem as involved a process as that blog post. I hope it hasn't become more complicated.
It takes a long time to install anything and I don't expect to surf the web on it, but it's nice to have this OS as an option.
I wanted to try out openconnect-saml on it, but the install failed because of lack of RAM/swap. I have managed to run xfreerdp over openconnect on it though (FreeBSD had better performance).
He spends half the tutorial getting Wi-Fi working, then installs a modern desktop environment styled after a desktop environment from 1993.
next level nostalgia
You lost me there. Why are ppl still using this electron monstrosity when there are so many better alternatives? (Like dd, WIN32Imager, USBImager, DiskImager, etc.)?
I mean, Etcher is bigger than the entire NetBSD image, what the hell?
(Apparently that's too much gray area for some zealots)