u/DarthRazor
I have an early X4 that predates this whole locking fiasco, so data over USB still works
I'm sticking with the vendor International F/W because it suits me the best - I convert everything to XTC because the results are perfect to my eyes. Can a future factory F/W update blow the USB data fuse and lock an unlocked device?
From research, the answer is NO, but there are a lot smarter people here than me, so I thought I'd ask
The NetBSD Project is pleased to announce NetBSD 11.0 RC3, the first release candidate of the nineteenth major release of the NetBSD operating system
I go through this guessing game every time I install NetBSD. Today I installed 11.0-RC1 on an old Dell D430 (Core2 Duo w/2GB RAM and a 20GB drive). Easy peasy- even the internal Dell wifi card worked when I downloaded the missing firmware)
Now I'm installing packages and I see a whole bunch of Python versions available. I usually go for the oldest for max compatibility when I software, but with the small HD, I'm trying to stay lean.
Do packages in the repository have specific versions as dependencies? I don't want multiple versions installed. Is that a thing? Thanks in advance
V3.10.0 just went live when checking for updates. I was on V3.0.8-EN. Updating now.
Changelog says:
I learned something new today. While browsing in the distribution_files directory on the TinyCore website to grab the 32-bit version of the boot files, I noticed that there was both a core.gz as well as a core64.gz, and the same for modules, etc. Note that this was core64.gz and not corepure64.gz
Interesting! I did some reading on the forums and core64.gz of a fully supported hybrid bid that supports the 64-bit address space (to access more than 4GB RAM), but is made to be used with the 32-bit userland (i.e. extensions).
Pretty neat - I'll be booting with core64.gz from now on. I like the bigger variety of 32-bit extensions over the CorePure64 ecosystem.
Short version: please recommend any good YouTube videos where the host does a side by side comparison of the 7300 and 710 user interfaces
Long version: I'm slowly easing myself back into ham radio after a 30 year lapse and am looking to get an HF rig from this century.
I've read countless posts about the Icom 7300 vs Yaesu 710 and for me they're both pretty equal. What's going to tip the balance is the user interface. The consensus is that the 7300 shines here, but that's very subjective. I'm looking to find out what shines best for me
I bought a Retevis RA79 (instead of the Quansheng UV-K5) mainly to play around with custom firmware, but I'd like to have a backup of the original firmware in case I get into trouble and need to revert.
I can't seem to find it on the webpage. Would anyone have a link they could share?
I have an old TYT MD380 (UHF only, no GPS) gathering dust that I'd like to upgrade with md80tools or OpenRTX firmware. I've gathered all the tools I need but can't find the OEM firmware packages on the TYT download site in case things go sideways.
I'm looking for firmware MD380-D13.32, which I believe is the last version for my radio that currently has D13.20 installed.
Does anyone have a link to D13.32 or D13.20? My Google skills have failed me.
I have an old TYT MD-80 (UHF only, no GPS) gathering dust that I'd like to upgrade with md80tools or OpenRTX firmware. I've gathered all the tools I need but can't find the OEM firmware packages on the TYT download site in case things go sideways.
I'm looking for firmware MD380-D13.32, which I believe is the last version for my radio, which currently has D13.20.
Does anyone have a link to D13.32 or D13.20? Google has failed me.
They say that CW is like riding a bike - you never forget. I was licensed in 1982 and solid at 15 WPM , but have been out of the hobby for decades and now I feel like I'm the comical circus elephant riding a bike.
Did primarily CW and VHF for probably 10 years, then marriage, kids, career, and life took priority. Life has slowed down, kids are out and have kids, and I'm looking at retirement next year, so I'm trying to get back into CW. I suck at it. I'm also on medical leave for a a few weeks, so I'm bored and have the time before returning to work.
Are there any online "refresher" resources you can recommend, or do I just start with the standard learning CW from scratch sites?
If you're a TinyCore fan, check this out. spirit OS is a curated distro based on TinyCore. Never heard of it till now. From their home page:
Spirit OS is a lightweight remaster of Tiny Core Linux 16.1, designed for very old 32-bit computers (without UEFI). It includes IceWM 3.6.0, full multimedia support (video/music with codecs), Wi-Fi tools, and a lightweight browser. Powered by glibc 2.40 and Linux kernel 6.12.11-tinycore, it's everything you need to bring your old PC back to life in 2025.
Included Software
I've been around these parts since the Wetshavers sub, but don't post often and haven't logged my shaves since I bearded myself 5 years ago.
I've been a 99% boar user for at least a decade, and have always cold-water shaved and never soak my boar brush before shaving. Just a quick 10 second thorough rise under running water and start straight to loading. Let's call it Raw Hoggin'
Maybe some of you would like to try it as an Austere August challenge?
TinyCore 16.1 has been released today with minor fixes.
Both 32-bit and 64-bit flavours are up, but as usual, no "64-bit Plus" version exists, solidifying my theory that the 64-bit version is a second class citizen ;-)
I'm going to ask what is potentially a very stupid question. To answer the "why" question, I mainly live in the terminal, but am uncomfortable with very wide views due to visual acuity.
When I open my first terminal, it's too wide for comfort, so I always open a second terminal and work in the master. I can't live without tiling mode but feel what I'm doing is a waste of resources, plus it covers my conky stats
Is there a creative way (or patch) to open a first window in the master area only (not full screen)? Opening a second window should behave as expected - first window goes to stack and new window goes to master. Killing one of the two windows leaves the remaining windows in ma