Lavapipe is CPU rendering, it doesn't really prove much. But also, Vulkan on BSDs is totally possible and isn't something esoteric, FreeBSD has it.
> Build goal only: This targets compilation and linkage of the Vulkan stack. Runtime GPU acceleration is not available under VirtualBox; the software driver (Lavapipe) is the target.
I don't understand why this would ever be a problem, even without LLM assistance it's something that sounds like a weekend project?
I dunno, that feels very BSD to me. Presumably, they had a ftp utility first, and then when somebody wanted to download files over http they looked around and decided that the obvious thing to do was to add it to the existing file transfer/download program. Same as continuing to add functions to ifconfig rather than inventing a new ip tool.
Oldest supported machine for NetBSD is VAX 780 from 1978(!!!). One of the first system supporting mmu, 32 bit cpu, virtual memory etc etc
This machine is so slow that it takes a lot of time to generate ssh keys etc. We talking here hours hehe
NetBSD is known to support like 60 architectures - many of them low end embedded systems: so ftp AS A CHOICE (you have other options!) is very smart and easy
I think GP is confused why the ftp command also handles http(s) :)
I hate to imagine what a 780 running NetBSD would be like, too.
I tried netbooting NetBSD on my MicroVAX 3400, which is about 2.5x the performance of the 780. It did, literally, take 6+ hours to slog through making RSA keys.
> I think GP is confused why the ftp command also handles http(s) :)
Exactly - I even suspected for a second that `ftp` on NetBSD is something else entirely, not an actual FTP client with HTTP/HTTPS URLs bolted on. It's not - it still accepts a host as an argument and opens a CLI if there's an FTP server to talk to.
Lavapipe is CPU rendering, it doesn't really prove much. But also, Vulkan on BSDs is totally possible and isn't something esoteric, FreeBSD has it.
> Build goal only: This targets compilation and linkage of the Vulkan stack. Runtime GPU acceleration is not available under VirtualBox; the software driver (Lavapipe) is the target.
I don't understand why this would ever be a problem, even without LLM assistance it's something that sounds like a weekend project?
Installation instructions:
That's... a bit unorthodox. FreeBSD has a `fetch`[1] utility for this, I wasn't aware NetBSD puts that in `ftp`[2].Interesting choice. I wonder what led to it.
[1] https://man.freebsd.org/cgi/man.cgi?fetch
[2] https://man.netbsd.org/ftp.1
I dunno, that feels very BSD to me. Presumably, they had a ftp utility first, and then when somebody wanted to download files over http they looked around and decided that the obvious thing to do was to add it to the existing file transfer/download program. Same as continuing to add functions to ifconfig rather than inventing a new ip tool.
Oldest supported machine for NetBSD is VAX 780 from 1978(!!!). One of the first system supporting mmu, 32 bit cpu, virtual memory etc etc
This machine is so slow that it takes a lot of time to generate ssh keys etc. We talking here hours hehe
NetBSD is known to support like 60 architectures - many of them low end embedded systems: so ftp AS A CHOICE (you have other options!) is very smart and easy
I think GP is confused why the ftp command also handles http(s) :)
I hate to imagine what a 780 running NetBSD would be like, too.
I tried netbooting NetBSD on my MicroVAX 3400, which is about 2.5x the performance of the 780. It did, literally, take 6+ hours to slog through making RSA keys.
> I think GP is confused why the ftp command also handles http(s) :)
Exactly - I even suspected for a second that `ftp` on NetBSD is something else entirely, not an actual FTP client with HTTP/HTTPS URLs bolted on. It's not - it still accepts a host as an argument and opens a CLI if there's an FTP server to talk to.
Elliptic curve key gen is much faster on slow hardware. You're waiting around on primality tests that aren't necessary with modern keys.
> Vulkan is now available
looks inside:
> What this is NOT (yet): Running Vulkan programs
Technically, it isn't wrong, if you consider Vulkan the technology rather than the service
This is a nice project but looks like is either AI written or AI assisted and I haven’t seen mention of that in any of the docs.
There are already Vulkan components in pkgsrc and wip.
Which ones? I'm asking, because I wouldn't have done anything at all if this was pre-existing.
I have never had a need for NetBSD, but in case I ever do, I’m glad it’s there. Especially with Linux deprecating old platforms.
This looks like an unofficial effort but hopefully it gets refined and integrated.
NetBSD already has relevant packages officially.
Which packages? I couldn't find what I needed, and that's the whole reason for building all this.
I expected this to be official from the title but it doesn’t seem to be.
Lavapipe? So it's just Mesa software rendering stuff
That's the start. The idea is to get Vulkan running first. More to follow.