Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: rbowman Newsgroups: comp.os.linux.misc Subject: Re: rPI Goes Public Date: 29 Jun 2024 07:11:02 GMT Lines: 25 Message-ID: References: <666e2a36@news.ausics.net> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Trace: individual.net PS67FM3hH6OP/VUnJu+w1AzHsFzeAUd9W1iWbLBmZD1+8cfspz Cancel-Lock: sha1:RwkSf7mt47P2nS68FN0O5Vp9CUQ= sha256:nxHcVGsMH3sJD8k320Bvs8KcdC4I81oTTINYBWtofSk= User-Agent: Pan/0.149 (Bellevue; 4c157ba) Xref: csiph.com comp.os.linux.misc:56611 On Sat, 29 Jun 2024 01:02:18 -0400, 26xh.0712 wrote: > So, for now, I'm into Arch derivatives. Manjaro is now very good but > there are a couple others I'd consider. My one gripe with Manjaro is > the update model ... which quickly gets to basically reloading the > entire 2+gb system, rather like Tumbleweed, and that takes time and > bites into the monthly data allotment. I avoided the Red Hat family after the gcc 2.96 fiaso in the early '2000s but recently gave Fedora a shot on one of my backup machines. I knew what i was getting into but the KDE spin 40 has a huge number of updates. They've even managed to copy the Windows 'Don't turn you machine off' message. > Clearly boards like BeeLink and BMax fit into a different niche from > Pi's - for some apps you WANT all those I/O pins and there's no > substitute. However I had been using Pi's for apps that did not need > those pins. Pi5/WORM has forced me to a fork in the road, Pi doesn't > do it all anymore. I've got a few Pico Ws and may go the route of using one Pico as the loader/debugger for the target Pico to get around the pin problem with a conventional Linux box. They're cheap enough.