What would you like to see over the next few FreeBSD versions?

I would like to see a port to the 128-bit version of RISC-V, if anyone ever makes chips with those extensions, and if it gets finished (unless it already is, I haven't read about it in a while). It would be cool for FreeBSD to be the first "mainstream" OS to be 128-bit. Sure it would be useless, but it would be COOL!
 
I'd like to see a small change in cp(1). It's still referencing rcp(1) in its SEE ALSO section however... /bin/rcp is currently obsolete according to /usr/src/ObsoleteFiles.inc.

I don't know all the details yet, but I do hope I can get a change request in somehow ;)
 
I just want UrbanTerror in ports. Not urbanterror-data, which I don't know how to use. If OpenBSD can have pkg_add urbanterror and it works in every version that I've used so far we should have it working as well. :D
 
What I want is updated SMB/CIFS2 and later. As current implementation of smbfs is still SMB/CIFS1 and the supports for it is starting to be dropped in other environments.

Up-to-date GPU supports would be wanted, too. nvidia alone is providing supports as for Linux (graphics usages only, though, but CUDA is reported to be usable using Linuxulator and x11/linux-nvidia-libs).

And schedulers with good supports for Asymmetric Multi Processor like P-/E-core and BIG/Little. Maybe other parts would be required overhauling to support them. Not all, but some of them has different instruction sets for each types of cores and scheduler should be aware of them for maximum performance and for avoiding hard-to-analyze problems.
 
My big wish used to be binary upgrades. Which eventually came along with freebsd-update. (Probably well before RedHat managed it.) Now it would just be wireless that works as well as it does on Linux. I don't do that much with my workstation, but I'm able to do everything else I need, both for work and recreation.
 
And schedulers with good supports for Asymmetric Multi Processor like P-/E-core and BIG/Little. Maybe other parts would be required overhauling to support them. Not all, but some of them has different instruction sets for each types of cores and scheduler should be aware of them for maximum performance and for avoiding hard-to-analyze problems.

Agreed. At some point this will be a serious issue we'll need to address.

For the topic though; i'd like
  • in-kernel SMB server (with ZFS integration and full support for NFSv4 ACLs)
  • better zfs/vm integration (ZFS ARC+mmap/page cache)
  • SMF (init/rc.d is old and archaic)
  • bhyve on aarch64
 
What I want is updated SMB/CIFS2 and later. As current implementation of smbfs is still SMB/CIFS1 and the supports for it is starting to be dropped in other environments.
This is my big request. I can do some work using SAMBA clients such as Thunar, but my interaction with our network shares really requires scripting and mounting. Our organization is 100% Microsoft on the server side, so all SMB shares. As far as I can tell, there is no technical or licensing reason to not update, it is just a manpower issue. I don't know how difficult it would be to write the code, but Linux CIFS utils was updated rather quickly, so it can't be an insurmountable challenge. Too bad I'm just a technician/low level admin, and never learned any C programming.
 
Back
Top