After a recent release of NetBSD 9.0 ( https://www.netbsd.org/releases/formal-9/NetBSD-9.0.html ) what does community members' wishlist for NetBSD 10.0 -try to be more specific of possible :)

- support for running cross-endian binaries on bi-endian architectures like MIPS and PowerPC - XFS driver? even read-only would be nice - stability / usability fixes for macppc - machfb driver fixes to prevent hang on boot - CHRP script to allow boot on new-world systems without needing OF prompt - stability / usability fixes for sgimips - seemingly random kernel panics when under heavy load with newport graphics enabled - would be great to have a driver for the indy VINO graphics capture (its very well documented) - port to gamecube/wii - evbarm port to i.mx6 / sabrelite ... i *might* personally be researching / writing code for literally all of these

Better Atheros WiFi support Keep zfs and dtrace up to date Vscode in pkgsrc Switch to openrc Ungoogled chromium and iridium Arduino support Better risc-v support

* boot+root on zfs * base system as a bunch of packages for easier updates (someone is/was working on this...) * import Ed Schouten's cloudabi patchset * more ARM64 SoCs (jmcneill@ has been absolutely phenomenal at this).

Easy: Better cross-compiling infrastructure for packages AMD64 -> Armv7, Armv8 FreeBSD has poudriere/jails/qemu. John Marino (before he was kicked out) developed gnatcross-aarch64 to do it better (so I think it's probably a dport on DragonflyBSD). I know he was working on NetBSD, so I'm surprised he didn't continue this. NetBSD? Kludge.

I only own x86_64 hardware, but I'm happy to see that the OS lives up to the moto _"Of course it runs NetBSD"_ and is introducing new platforms to the already extensive list :) Honestly, and unlike what others have written, my hard drives are small and CoW file systems are of no use to me. Sorry, but I don't really care about `zfs` and if its introduced, I do hope the possibility to run `FFSv2` is kept, its good enough to me. I do hope to see increasing support for wireless cards and new hardware. Being on pair with Linux-4.4 series is very good already, keep-up the excellent work!! The work already done on virtualization is awesome 🥳 , `nvmm` and `haxm` are great additions and allow those who want/need to run another OS for those, natively unsupported tasks. In all, I'm very happy with NetBSD already. It would be nice to convince Google to compile a version of `widevine` for BSD. I would then be able to convert a few family machines, currently running on Ubuntu base, to NetBSD. They want their Netflix 🤔 Personally, I'd like to see a clean-up of the `pkgsrc` tree. There're loads of packages, where the upstream project is either abandoned or dead. That's a lot of resources being used to patch and maintain software, that could be otherwise pulling/packaging more useful things. But, that's probably just me, as I'm a minimalist but also a modernist ;) Along similar lines, a base system clean-up would be nice, e.g. why `twm` and `ctwm` in base? I know they are small, but a wm should be a users choice and one is more than enough. A similar thought goes for the number of shells in base and few other unnecessary things. I always remove `/games` and `ctwm` and I keep away from `linux-emul`. Again, no big deal, just a thought. One thing, though... More and more things are done on a web-browser, so maybe time to think about how to keep the browser up-to-date. I'm happy running `firefox`, but it would be nice to have it updated in between Q-releases. I know, I can build it from `pkgsrc-current`, but I'd like to stick to **one** release.

Port of recent AMDGPU driver to NetBSD and try to keep it updated, that would be a dream.

> @"[unknown]"#p887 It would be nice to convince Google to compile a version of widevine for BSD. I would then be able to convert a few family machines, currently running on Ubuntu base, to NetBSD. They want their Netflix In my opinion: without an NDA to sign this is unlikely to happen, as far as I can assume from briefly looking into widevine. even getting them to acknowledge your existence seems hard.

@"[deleted]"#p889 Yes, I'm perfectly aware of that. Its all in the hands of google and not on the hands of the OS. I just think it sucks. Netflix uses FreeBSD and even contributes back to it, but FreeBSD users can not watch Netflix because it uses google's `widevine` 👿 The only reason it works on Linux, if you're using the standard `glibC`, which I don't, my Linux machine runs on `musl`, is because it **has to work on ChromeOS** The choice of OS should have **nothing to do with it**. Unfortunately, it does 😢

**fcambus** provided his wishlist items for 10.0: 1) signed packages 2) easy installation on encrypted root 3) LLVM built by default on amd64/i386 4) Spleen by default for framebuffer consoles ;)

- Lima drivers for mali4xx gpus and newer amdgpu version. - Default PKG_PATH set to correct versions and architecture. - Easier install process. Maybe dialog that tells you "Reboot or open shell in installed system" at the end of installation?

Wishlist for NetBSD 10.0

imachocbar

pin that's sad... but I still hope it will though. Or at least some RELEASE-llvm tarballs.

imachocbar I've never tried these but, you could take it for a spin, http://nycdn.netbsd.org/pub/NetBSD-daily/HEAD-llvm/

yeti

imachocbar I played a while ago with HEAD-llvm building own or downloading daily install ISOs and failed to get PkgSrc bootstrapped on those systems.
Then I thought, I'll take a big pause with this and retry it some months later. I already did that delay it again Sam game earlier, it seems to grow into a habit.

JuvenalUrbino

yeti Then I thought, I'll take a big pause with this and retry it some months later. I already did that delay it again Sam game earlier, it seems to grow into a habit.

Playing with pkgsrc and different compilers is quite nice, keep us informed on that 😉.

JuvenalUrbino

yeti Back to PCC! \o/

 export PKGSRC_COMPILER=TurpoPascal

yeti

JuvenalUrbino Nah, I won't touch Pascal again, well unless it gets me a massive bribe.
That PCC is meant:
https://blog.netbsd.org/tnf/entry/portable_c_compiler

unicorn

I wish emacs upgraded to 28.2

unicorn I wish emacs upgraded to 28.2

This is actually pkgsrc and, not really release related.
If you don't mind building a few things from source, there's emacs-git in the wip repository.

rvp

unicorn You can get emacs-28.1 as a binary from 2022Q2 as emacs28.

unicorn

I see 28.2 tar.gz and tar.xz. I download the tar.xz file,how to install it?

Jay

unicorn you can install with pkgin

unicorn

nice,I have had emacs 28.1 installed,thanks

https://mail-index.netbsd.org/current-users/2022/12/08/msg043287.html

nortonham

that's an interesting problem regarding FFS and the installer, although it's strange the response about something completely different.....

NetBSD-10.0_BETA out today

nortonham

pin
roughly how long does it take to go from beta to release?

andreasdr

Arrrrr. I am eager to try this right now.

yeti

Aaaapropos NetBSD10...
...since the GPUFW set was introduced, I had to strip -vga virtio from my QEmu-NetBSD-Guinea-Pig-VM's start scripts.
Which -vga $xyzzy should I use now?
Is that mentioned somewhere?
It's not urgent, as I typically ssh (or tramp) into them, but one open question less would still feel better...

nia

yeti Why did you? There is no GPU firmware for "virtio" anyway, since there's no kernel driver for that.

I'm usually using -vga vmware. It's only supported with a userspace driver in xorg.

nortonham honestly, I don't know but, you could install BETA and later upgrade to RELEASE. Although, there are currently no pre-compiled binaries for 10.

yeti

nia It probably has sneaked into that start script by being a copy of one starting a different OS that supported it and it didn't crash on boot with -vga virtio before GPUFW appeared (9.99.7x). I don't miss it, I just am curious. That's in my genes!

« Previous Page Next Page »