11–20 of 40 posts
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.
Installation instructions: ftp https://raw.githubusercontent.com/segaboy/vulkan-netbsd/main/scripts/setup-env.sh !^^^^^! 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
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 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.
Earlier quoted context omitted.
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.
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.
> Vulkan is now available looks inside: > What this is NOT (yet): Running Vulkan programs
Installation instructions: ftp https://raw.githubusercontent.com/segaboy/vulkan-netbsd/main/scripts/setup-env.sh !^^^^^! 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
Earlier quoted context omitted.
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.
There are already Vulkan components in pkgsrc and wip.
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.
Lavapipe? So it's just Mesa software rendering stuff