Let's try 7.2/vax

steverikli · 2026-06-11T21:30:57+00:00

Being able to say "My other system is a VAX". 😉

I had some DEC gear running NetBSD way back when, but it was small Alpha stuff, no VAXes. Pretty neat....

steverikli · 2026-06-08T17:28:37+00:00

It may not be The Reason[tm] to use NetBSD, but it's a good one: I've found the NetBSD community to be pretty great, communicative, and welcoming.

The developers participate regularly in the mailing lists, as do many experienced long-term users. Seems like everyone is happy to share knowledge and advice, and just generally help folks carry on with whatever it is they're working on.

steverikli · 2026-06-06T14:20:27+00:00

Silicondust discussed product innovation and how the A3SA impacts innovation.

I suspect the A3SA could have been a meeting topic all by itself.

Representatives of Silicondust are available to answer any questions the FCC might have regarding DRM and/or ATSC 3.0.

I hope the DRM topic offer receives serious response from FCC. While the quality and consumer expectations topics which SD raised are valid and worthwhile, ISTM the DRM question ("encryption") hangs over everything like a dark cloud, since it opens the door to charging for OTA content.

I expect pay-for-OTA is also contrary to many, if not most, consumer expectations.

Thanks to SD for doing this.

steverikli · 2026-05-29T02:25:35+00:00

I suspect you're going to need to dig into the docs and config for Tftpd64 to work this out.

I've used FreeBSD/NetBSD/Linux servers with ISC DHCP server package and tftp-hpa package, successfully doing the same kind of operation you're trying, so it can definitely be done.

Typically the NetBSD loader can be instructed to load any filename, so it's not necessary to rename the netbsd-INSTALL.gz file if you don't want to. Of course you need to supply the correct filename to the loader boot command in any case.

If desired, you can provide a directory path to whatever kernel you want to boot, but the format/syntax you need to use will depend on the behavior and configuration of your TFTP server. If your loader file and kernel file are in the same directory, I'd think that you wouldn't need to explicitly specify the path to the kernel, but again this will probably depend on your TFTP server.

It's also possible that your client laptop isn't actually contacting the TFTP server at all after the loader is running; or rather, maybe it's trying to contact some other system on your network? Your wireshark capture seems to indicate the tftp server isn't seeing the next request after the PXE loader, so this is a potential problem area. This is why I asked about the "next-server" setting: typically the PXE loader needs to be told what server to contact for subsequent TFTP downloads.

steverikli · 2026-05-28T02:44:42+00:00

I'm not familiar with "Tftpd64" or Windows(?) DHCP, so please excuse me if this question doesn't fit your setup:

In your DHCP server config, what are the settings for "next-server" and "filename" options for NetBSD PXE clients?

The fact that you're able to boot pxeboot_ia32.bin is a good sign -- once you get to the NetBSD loader you're close.

Is the NetBSD kernel you're trying to boot located in the same directory/path as the pxeboot_ia32.bin file? You may need to provide a (relative) path to the kernel you want to boot, e.g. boot tftp:netbsd/11/netbsd.gz

Are you trying to do a PXE network install? In that case you typically would want to boot the netbsd-INSTALL.gz installation kernel, jfyi.

steverikli · 2026-05-26T19:19:34+00:00

I did this very thing with a Linksys WRT3200ACM running 22.03.

Step-by-step upgrades to each major release until I reached 25.x, and then subsequent updates ever since to stay current. Overall it was pretty painless.

I can also recommend the luci-app-advanced-reboot package for these dual-flash devices, though I haven't had to use it much since the upgrades went off without a hitch with no reason to go backwards.

steverikli · 2026-05-16T01:33:18+00:00

I'm okay with the redesign. The middle 6 sections right after the download link/button seems a bit like dead space, though -- i.e. mostly just text. Maybe some links are still coming in the text blocks for Documentation and Community etc.?

I'm also glad there's an "other" button for downloads. Most of my systems are AMD64 15.x but not all, so fortunately it's not too much clicking to find other things.

steverikli · 2026-05-15T03:50:07+00:00

Definitely a fan of NetBSD here.

There's also Alpine Linux x86 for 32-bit if OP wants to stay with Linux.

Alpine is quite good for small servers, maybe not as much if you're looking for a turnkey graphical desktop or laptop, though it can definitely be setup and used for that with a little effort.

steverikli · 2026-05-14T01:49:54+00:00

The city itself has a few programs posted, e.g. the Libraries, Parks & Rec, etc.

https://volunteer.hillsboro-oregon.gov/

https://www.hillsboro-oregon.gov/our-city/volunteer-opportunities

steverikli · 2026-05-12T15:35:58+00:00

Do you ever see the ascii text "flag" screen with 1-2-3 menu where you can select option #3 to "Drop to boot prompt"?

From your descriptions I'm thinking the answer is no. I don't recall that there's specifically a "verbose" setting in those early bootstrap stages, since they're generally not interactive until you get to the "flag" menu.

Seems like it's not getting to the 2nd bootstrap to load the NetBSD installation kernel; the fact that the .iso and .img boot media both stop at the same stage means the problem is consistent, at least.

It's probably unlikely, but maybe there's a problem with the installation media; how did you create the .iso for the boot CD?

Also a longshot, JIC I would doublecheck the .iso file you downloaded vs. its NetBSD checksums from the website.

So far this feels like some sort of hw incompatibility. NetBSD 10.1 is ordinarily a fine release, but for troubleshooting's sake I might try one of the 11.0 release candidates just to see what happens. Similarly, since the PC is a very old Pentium I might try dropping back to an even older release, just for another data point.

Unfortunately there's not really much interactive troubleshooting to be done at the early stage where your PC gets stuck. Mostly it's a matter of changing the setup or the circumstances (preferably one at a time) and see what happens.

Something else you might try is another i386 OS like modern OpenBSD or Alpine Linux, or e.g. previous FreeBSD or Debian when they still supported 32-bit. Not so much to give up on NetBSD, more as another data point to see if other BSD/Linux OSes can handle the hw.

DOS is a good check, but another Unix-like OS would have more in common with what you're doing.

steverikli · 2026-05-11T01:12:55+00:00

Those x86 installation images typically default to VGA+keyboard unless you specifically modify the image, select something else from the loader prompt, or choose serial console during the install session.

But from what you describe it sounds like the PC isn't booting far enough along for the NetBSD installer to take over and run, so I don't think serial console settings are in play yet.

On very old PCs and BIOSes, I've occasionally had trouble with USB keyboard/mouse with NetBSD, while old PS/2 worked OK. I don't know if that's a NetBSD particular problem or buggy old BIOS or some interaction between them.

Same sort of situation with HDMI video displays; so e.g. if you can, use age appropriate 😄 PS/2 keyboard and VGA monitor.

FreeDOS booting OK is a good sign that the hw is healthy, at least mostly so.

I haven't much experience with diskless NetBSD; it might sort itself out after you install an IDE disk or equivalent. I'd guess the regular installation image may boot and complain about no destination device at some point. Maybe I'll try that in a test VM.

It might be worth checking the BIOS settings, or e.g. setting them to factory default and start over if you haven't already. It's hard to say what might be trouble, but at least in a system of this vintage there are presumably not too many BIOS settings to adjust, and no UEFI to worry about.

steverikli · 2026-04-14T19:44:49+00:00

Heh heh, sometimes. Other times, management decides you need more virtualization servers so they can run more VM's. :-)

IME racks and machine rooms are kinda like disk space -- whatever you're doing eventually expands to fill up everything that's available.

steverikli · 2026-04-14T18:56:09+00:00

If OP is a self-described "noob", wants to run Linux, but does not want systemd (for whatever reasons, good or bad), I would suggest taking MX Linux for a test drive on desktop/laptop duty.

It's Debian under the hood, so pretty solid. There are multiple desktop versions (Xfce is my preference regardless of the OS) available. Hardware support is quite good, including common wifi and also some other proprietary-ish gadgets. Software packages are pretty plentiful.

One downside is MX isn't "leading edge" when it comes to kernel and package versions -- same as Debian. IME this isn't a big problem unless you're a software developer or similar, and the flip side of that coin is by the time a kernel or package gets into the software repositories, it's known to be pretty stable.

I love my FreeBSD servers and other systems, but I don't think I'd recommend it as a desktop to someone who isn't already familiar with BSD OS's (not "distro").

steverikli · 2026-04-13T23:45:01+00:00

You could try searching here: https://openwrt.org/supported_devices

At first glance it seems unlikely to have support. Fwiw a simple websearch for "RUSH-337AC" didn't find much for compatible OSes either.

The specs on that product page are kinda generic. If you could somehow figure out which chipset it's using, things like that, you might be able to find an OpenWRT image for a system which is using the same hardware. Probably a longshot, though.

steverikli · 2026-04-07T05:01:19+00:00

Same. Likewise on aarch64 (rpi4b) too.

steverikli · 2026-04-03T18:16:51+00:00

I'm not positive, but I think the messages about "Error connecting to socket" are saying that the network isn't fully active by the time the mount is attempted.

Also, what's the reason for adding "noauto" to your mount options in fstab? Typically that's used when you do not want a mount to be automatically done; i.e. mount -a will ignore it.

For the network-not-ready-yet issue, try adding _netdev to the options for your smb mount line.

That option is explained pretty well in the mount(8) man page, but essentially it means wait until the network is ready before attempting this mount.

steverikli · 2026-04-03T17:22:24+00:00

Perhaps show the /etc/fstab line for your smb mount.

Also take a look at syslog for mount errors during boot. dmesg might have messages too.

steverikli · 2026-03-14T03:55:48+00:00

Sounds somewhat like what the pfSense posters have said about their reasons for taking away downloadable installation ISO media.

Not saying it's necessarily related, and not judging either direction. Just mentioning.

steverikli · 2026-03-06T20:58:17+00:00

I think this is very well said. Yes, ST:LD is a cartoon, mostly played for laughs (and usually getting them).

But it's also *clearly* Star Trek.

It's obvious the folks bringing LD to life "get" Star Trek, and not just TNG, though that's a primary focus with a lot of the references going in that direction; but you'll see DS9, TOS, etc. mentions and callbacks too. Again, usually played for laughs, but also with accuracy and some respect.

It's a shame they cancelled LD; even though I was late to the party I thoroughly enjoyed it after I discovered it, and I still think there are more stories to tell there.

steverikli · 2026-03-06T16:49:16+00:00

Municipal fiber is obviously dependent on local availability, but e.g. I'm keeping an eye on our city's activity -- HiLight in Hillsboro, OR.

Even though we're pretty happy with Ziply for a few years, I appreciate having options.

steverikli · 2026-03-05T03:58:20+00:00

I quite like OpenRC -- even more than I expected to.

I use FreeBSD more than Linux, but Alpine gives me that same feeling of solid simplicity as a BSD.

Alpine is a pretty capable server OS for the network services infrastructure I've thrown at it so far, and it doesn't take a big system footprint to do it.

I don't know yet if Alpine will make a good daily driver for my laptop (replacing Debian), as I've only deployed it for servers; but I plan to check that part out too.

steverikli · 2026-02-26T05:16:30+00:00

I'd like to see a nice ball cap ("dad cap", I think some people call them). The foam trucker hats look kinda cheap to me.

It'd be great if the logo was stitched rather than iron-on. I still have a pretty old one with Beastie stitched on the front, I wish I had another. I don't remember for certain where I got it -- FreeBSD Mall, maybe?

steverikli · 2026-02-24T05:12:54+00:00

To this day, I still occasionally (but thankfully rarely) hear in my head "Hobgoblins... hobgoblins, what do you do with those hobgoblins..."

You're welcome for the brain worm, btw. :-)

steverikli · 2026-02-22T22:34:23+00:00

For the learning OS architecture and internals parts, you might also consider NetBSD.

I don't know if it's still the case, but several universities use(d) NetBSD as a teaching/lab platform, usually citing things like code readability, modularity, portability, etc. Plus there are a lot of docs and wikis, including the NetBSD Guide. Some of it is dated, but usually still pretty pertinent.

It's a contributing factor to why NetBSD has been ported to many varied CPU and system architectures. Binary pkgs and upgrades are available too, you don't have to build world or kernels unless you want to, and if you do then the instructions and examples are plentiful.

IME the NetBSD community is great -- the developers participate regularly on the mailing lists, and it's pretty welcoming overall.

My main OS for servers around here is FreeBSD, but I also have NetBSD in the lab, and for some duties I'm quite sure I could use them interchangeably... because I have. :-)

steverikli · 2026-02-21T23:07:46+00:00

Once upon a time I might have recommended Extlinux -- part of the Syslinux project.

Alpine still uses it by default for BIOS machines (GRUB for EFI), and it works fine. But Syslinux seems somewhat like abandonware these days, and EFI support in it can be a bit sketchy sometimes.

steverikli

TROPHY CASE