NetBSD has been broken on the hpcmips platform for any release after NetBSD 7...
On my WorkPad z50, recent kernels (past about NetBSD 9) won't find PCMCIA devices. There also seems to be some general problem with binaries built for the vr41xx MIPS CPUs causing segfaults.
There's a NetBSD developer interested in finding out what's wrong, but I really don't have the resources (and patience) for the required testing all by myself.
So is there anyone out there with one of the supported machines (WorkPad z50 and NEC MobilePro seem to have been reasonably common in the West) and some time to spare to run NetBSD test kernels and report back results?
Full hardware list is at https://wiki.netbsd.org/ports/hpcmips/supported_machines/
The old netbsd-hpcmips mailing list was deemed too low-traffic a couple of years ago, and all discussion about these systems is now on port-mips: https://www.netbsd.org/mailinglists/#port-mips
I didn't know someone made these Dallas RTC replacement boards at some point, and I can't find a listing on eBay currently (the link from forums.sgi.sh/index.php?threads/ds1742w-nvram-rtc-replacement-for-sgi-fuel-tezro-o350.964/ does not seem to exist anymore).
This seems like a better solution than cutting up old Dallas modules in order to disconnect the internal battery and wire up an CR2032 instead.
It's been quite some time since I've last seen this...
I still had a 98LITE folder in my ancient downloads collection with all the files. For some reason it didn't want to run directly off the CD image I created (didn't find a file by its shortened ~8.3 filename), but the problem was gone after copying all files into an installation directory on the harddisk. I initially booted off a FreeDOS floppy with CDROM driver.
(Still waiting for things to fail - never tried the Windows 98 installer from FreeDOS, but we'll see...)
So now I sourced an MSDOS 6.22 boot floppy image with HIMEM.SYS (and an IDE CD driver).
It didn't like the HDD file system created by FreeDOS, so I'm starting from scratch (good thing the floppy image also has xcopy.exe)...
Ah! I was wondering why even the emulated PCnet32 network card was not being found, but the SoftGPU driver docs have a fix: Seems like W98 doesn't detect an PCI bus during installation, and you have to force the Plug and Play BIOS Device to PCI in the device manager, even if Windows thinks it's incompatible.
...when you don't have the correct SCSI cable: Didn't find one with 50pin HD connectors on both sides, so I used an external SCSI case with centronics-style connectors as a passthrough between two 50pin HD to centronics cables...
My main backup media were: ZIP disks (but the one ZIP drive I still have is only borderline operable) and DAT tapes (I have a bunch of DAT drives, but when I tried one of them the last time, it had sticky drive rollers).
@selea I'm using several Shelly Plug S with their Home Assistant integration that's built on CoIoT (but they can also do MQTT). They're running on 2.4GHz Wifi.
I assume it's basically the same hardware as the Nous plugs or others that look similar, but Shelly has their own software (that optionally ties into their cloud stuff).
@selea No, it's off by default and has to be enabled on the web interface after connecting to a Wifi network.
(Well technically you can enable MQTT before, as initial configuration and joining an existing Wifi is done by connecting to a default hotspot network generated by the plug.)
I just got a complaint about my #photography posts, which I concluded came from a troll, but perhaps I’m actually coming off in a way that rubs people the wrong way here.
The complaint was that by posting high resolution images and describing in detail the processes used to create them, I’m merely “showing off” in a way that isn’t useful to most people.
I indeed do rather niche photography, using relatively esoteric gear. I think some people are interested in process and enjoy the results.
Fun: When you use Firefox and just keep it sitting in the background with a couple of Mastodon tabs signed in on your home instance - and all tabs that open a thread from a particular post land on your home instance by default - it will run into one of the Mastodon API limits after two hours or so (tested with about 20 tabs when I was trying to replicate what one of our users reported).
Doesn't seem to happen with Chromium browsers.
(Not that I need that feature, since I have a Lightning VME USB board in my TT, and a compatible USB ethernet dongle - but it would be an interesting additional option to have...)
I remember back in the olden days, when building the Linux kernel we ran make config and went through all the questions, answering yes/no on each one depending on how you wanted to have your kernel configured. Then we ran make to build it.
At some point, when the number of options had grown to make this a bit of a hassle, make menuconfig and make xconfig were introduced, making the process a bit faster.
I haven't built a kernel in a long time (decades?) and I wonder if make config still exists, and if so, how many questions do you have to answer if you were to use it?
@loke I last built custom kernels when the grsecurity patches were still available to everyone, so quite some time ago now.
make menuconfig was manageable, I think you could load a previous config and then revisit the new options? make oldconfig was also a thing to that end?
No, it did not. Tired of hearing this. According to who? In what?
I’ve seen platforms that ceased to exist over the years. I’ve seen social media companies getting acquired or going bankrupt. I’ve seen entire portals losing their users. The Fediverse keeps growing. How is this failing?
From IRC: Apparently $someone intercepted XMPP traffic to jabber.ru (hosted by Hetzner and Linode in Germany) with a middlebox, and this was detected only because the Let's Encrypt certificates used for the interception ran out: https://notes.valdikss.org.ru/jabber.ru-mitm/
This kind of attack is not usually possible without cooperation from the hosting provider, quote: "We believe this is lawful interception Hetzner and Linode were forced to setup."