Seems to work fine with LXQT, couldn't get enlightenment to work, apparently the current version in pkgsrc is rather old as well.
So I'll run this for now and have a second laptop just in case with #NetBSD#BSD#Linux#OpenSource#LXQT
@al1r4d@SDF The same BIOS bootloader is used on 32-bit and 64-bit x86, which is why it just says NetBSD/x86. We usually call the 64-bit variant amd64, since AMD invented it.
The core part of the BIOS bootloader has to be written in 16-bit assembler code, so it's rather irrelevant whether it's running on a 32-bit or 64-bit machine.
Are there people around which are living with all defaults? Default WM, Default vim / emacs config, etc? So install an OS & tools without changing anything?
@dreid@bitprophet Curses is standardized in the X/Open Portability Guide, but we (and to a lesser extent Solaris) are the only vendors using non-ncurses versions today.
The menu and form libraries come from AT&T, specifically UNIX System V Release 4.2.
However, I doubt the colour specification comes from Unix at all, but rather ANSI and IBM.
Alas, I have to consider some other hardware that is more BSD friendly than what I currently have for my main laptop. Wifi worked great on NetBSD, whereas it was flaky on FreeBSD, but the audio input was the flaky one.
A ThinkPad, maybe? I'll gladly accept hardware recommendations for BSD-friendly models from at least a decade ago (read: cheap).
Current status: Deciding between Void and Alpine for the next episode of The Main Machine Trials®
@greggyb@jutty Sadly most from Lenovo have BIOS whitelists by default, forbidding you from changing the card, though there's the option of getting an X230 with Coreboot pre-installed from various vendors.
I've been using an X260 for the past years, though I use an USB WiFi device (urtwn) or ethernet for reliability.
New development policy: code generated by a large language model or similar technology (e.g. ChatGPT, GitHub Copilot) is presumed to be tainted (i.e. of unclear copyright, not fitting NetBSD's licensing goals) and cannot be committed to NetBSD.
@onepict i've probably said this 100+ times now - this policy is for committers (foundation members) only, who've all already signed contracts with a clause about tainted code.
the policy is for base only, which has strict rules about copyright for Reasons™0. We are not opting out of running any third-party code that might have used an auto-completion tool. Since the BSD license requires strict attribution, our code in base can't be used to train LLMs either.