Re: rPI Goes Public

From	rbowman <bowman@montana.com>
Newsgroups	comp.os.linux.misc
Subject	Re: rPI Goes Public
Date	2024-06-29 07:11 +0000
Message-ID	<le9qc6FfdeeU2@mid.individual.net> (permalink)
References	(9 earlier) <666e2a36@news.ausics.net> <wwvr0cw9itq.fsf@LkoBDZeT.terraraq.uk> <uTidnclGKrILpOP7nZ2dnZfqn_udnZ2d@earthlink.com> <le8ackF8gijU2@mid.individual.net> <C7qcnZNvWPLGCOL7nZ2dnZfqnPSdnZ2d@earthlink.com>

Show all headers | View raw

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.

Back to comp.os.linux.misc | Previous | Next — Previous in thread | Next in thread | Find similar

Thread

rPI Goes Public "26xh.0717" <26xh.0718@e6t4y.net> - 2024-06-11 22:00 -0400
  Re: rPI Goes Public Andy Burns <usenet@andyburns.uk> - 2024-06-12 07:18 +0100
    Re: rPI Goes Public Richard Kettlewell <invalid@invalid.invalid> - 2024-06-12 08:26 +0100
  Re: rPI Goes Public Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-06-12 07:19 +0000
  Re: rPI Goes Public Pancho <Pancho.Jones@proton.me> - 2024-06-12 08:31 +0100
    Re: rPI Goes Public Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-06-12 07:51 +0000
      Re: rPI Goes Public Pancho <Pancho.Jones@proton.me> - 2024-06-12 12:14 +0100
        Re: rPI Goes Public "26xh.0717" <26xh.0718@e6t4y.net> - 2024-06-14 09:53 -0400
    Re: rPI Goes Public Richard Kettlewell <invalid@invalid.invalid> - 2024-06-13 17:39 +0100
      Re: rPI Goes Public Pancho <Pancho.Jones@proton.me> - 2024-06-13 20:21 +0100
        Re: rPI Goes Public Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-06-14 00:21 +0000
          Re: rPI Goes Public Pancho <Pancho.Jones@proton.me> - 2024-06-14 08:46 +0100
            Re: rPI Goes Public Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-06-14 08:21 +0000
            Re: rPI Goes Public Richard Kettlewell <invalid@invalid.invalid> - 2024-06-14 09:44 +0100
              Re: rPI Goes Public Pancho <Pancho.Jones@proton.me> - 2024-06-15 00:16 +0100
                Re: rPI Goes Public Richard Kettlewell <invalid@invalid.invalid> - 2024-06-15 10:14 +0100
                Re: rPI Goes Public not@telling.you.invalid (Computer Nerd Kev) - 2024-06-16 09:56 +1000
                Re: rPI Goes Public Richard Kettlewell <invalid@invalid.invalid> - 2024-06-17 07:36 +0100
                Re: rPI Goes Public "26xh.0712" <26xh.0713@e6t5y.net> - 2024-06-28 00:18 -0400
                Re: rPI Goes Public rbowman <bowman@montana.com> - 2024-06-28 17:32 +0000
                Re: rPI Goes Public Bobbie Sellers <blissInSanFrancisco@mouse-potato.com> - 2024-06-28 10:48 -0700
                Re: rPI Goes Public rbowman <bowman@montana.com> - 2024-06-28 17:56 +0000
                Only you have the power (Was: rPI Goes Public) Lew Pitcher <lew.pitcher@digitalfreehold.ca> - 2024-06-28 18:00 +0000
                Re: Only you have the power (Was: rPI Goes Public) rbowman <bowman@montana.com> - 2024-06-29 07:24 +0000
                Re: Only you have the power (Was: rPI Goes Public) Lew Pitcher <lew.pitcher@digitalfreehold.ca> - 2024-06-29 12:30 +0000
                Re: rPI Goes Public Andy Burns <usenet@andyburns.uk> - 2024-06-28 21:04 +0100
                Re: rPI Goes Public The Natural Philosopher <tnp@invalid.invalid> - 2024-06-29 10:25 +0100
                Re: rPI Goes Public Lew Pitcher <lew.pitcher@digitalfreehold.ca> - 2024-06-29 12:35 +0000
                Re: rPI Goes Public rbowman <bowman@montana.com> - 2024-06-29 17:48 +0000
                Re: rPI Goes Public The Natural Philosopher <tnp@invalid.invalid> - 2024-06-29 10:21 +0100
                Re: rPI Goes Public Bud Frede <frede@mouse-potato.com> - 2024-07-01 07:10 -0400
                Re: rPI Goes Public Bobbie Sellers <blissInSanFrancisco@mouse-potato.com> - 2024-06-28 13:35 -0700
                Re: rPI Goes Public "26xh.0712" <26xh.0713@e6t5y.net> - 2024-06-29 01:02 -0400
                Re: rPI Goes Public rbowman <bowman@montana.com> - 2024-06-29 07:11 +0000
                Re: rPI Goes Public D <nospam@example.net> - 2024-06-29 22:11 +0200
                Re: rPI Goes Public "26xh.0712" <26xh.0713@e6t5y.net> - 2024-07-02 03:00 -0400
                Re: rPI Goes Public D <nospam@example.net> - 2024-07-02 11:47 +0200
                Re: rPI Goes Public "26xh.0712" <26xh.0713@e6t5y.net> - 2024-07-02 02:55 -0400
                Re: rPI Goes Public The Natural Philosopher <tnp@invalid.invalid> - 2024-06-29 10:20 +0100
                Re: rPI Goes Public Pancho <Pancho.Jones@proton.me> - 2024-06-17 00:35 +0100
        Re: rPI Goes Public Richard Kettlewell <invalid@invalid.invalid> - 2024-06-14 09:34 +0100
          Re: rPI Goes Public Pancho <Pancho.Jones@proton.me> - 2024-06-15 00:15 +0100

csiph-web