home bbs files messages ]

Just a sample of the Echomail archive

Cooperative anarchy at its finest, still active today. Darkrealms is the Zone 1 Hub.

   RBERRYPI      Support for the Raspberry Pi device      21,939 messages   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]

   Message 19,306 of 21,939   
   68g.1499 to Scott Alfter   
   Re: It is now very nearly impossible to    
   01 Feb 24 01:32:15   
   
   INTL 3:770/1 3:770/3   
   REPLYADDR 68g.1499@etr6.net   
   REPLYTO 3:770/3.0 UUCP   
   MSGID:  2bf3429c   
   REPLY:  b229649c   
   PID: SoupGate-Win32 v1.05   
   On 1/30/24 6:05 PM, Scott Alfter wrote:   
   > In article ,   
   > Chris Green   wrote:   
   >> I can't us Pi Imager because it's very broken on Ubuntu:-   
   >   
   > Sounds like something you should take up with the Ubuntu packagers.  I   
   > maintain a Gentoo ebuild for rpi-imager (it's in my overlay...sudo eselect   
   > repository enable salfter && sudo emaint sync -r salfter), and it works like   
   > a champ.   
   >   
   > More recently, I've migrated my print server (an ancient RPi Model B) from   
   > Raspbia^H^H^H^H^H^H^HRPi OS to Alpine, and it's running headless.  The   
   > Alpine install needed to be done on a spare Raspberry Pi, but once it was up   
   > and running with ssh access, I was able to do the rest of the setup over the   
   > network.  Once I had it configured as I wanted it, I brought the MicroSD card   
   > over to another computer to image it and shipped the image home so I could   
   > blast it onto an SD card.  It's a much lighter-weight system now...could put   
   > it on a 128MB SD card, if I had one that small. :) The server runs headless,   
   > with just two printers, a network cable, and a power supply plugged in.   
      
      
      Ok ... I'm not gonna ask why you'd want a completely separate   
      print server, based on an old Pi, rather than just printing   
      directly from/to whatever   :-)   
      
      In any case, the "headless" problem is more of a problem   
      with RP-OS based on Worm. They completely changed how the   
      networking was done, and while there IS a CL command   
      with lots of obscure params it's just not as straight-up as   
      it used to be. I posted info on where to look and templates   
      for customizable network defs in order to speed people   
      along in this aspect. Alas that's not the only thing Worm   
      has pointlessly messed-up. Oh, and BullsEye won't run on   
      a Pi-5 - you get a testy little message on boot.   
      
      Normally I rec RP-OS because it's probably best-tuned to   
      the boards, easiest tweaking for all the little devices   
      and pins and such. But NOW ... maybe some ARE better off   
      with 3rd-party systems depending. Arch, G2, even Fedora   
      derivs, may be more friendly for "headless". Can't really   
      rec RHEL derivs anymore since IBM ruined it all, don't   
      want to build critical stuff on beta (or worse) code.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)   
   SEEN-BY: 10/0 1 15/0 90/1 103/705 105/81 106/201 128/260 129/305 135/225   
   SEEN-BY: 153/757 7715 218/0 1 601 700 840 870 930 220/70 221/1 6 226/17   
   SEEN-BY: 226/30 100 227/114 229/110 112 113 200 206 307 317 400 426   
   SEEN-BY: 229/428 470 550 616 664 700 240/1120 266/512 267/800 282/1038   
   SEEN-BY: 291/111 292/854 301/1 113 812 310/31 320/219 322/757 335/364   
   SEEN-BY: 341/66 342/200 396/45 460/58 633/280 712/848 770/1 3 100   
   SEEN-BY: 770/330 340 772/210 220 230 5020/400 1042 5058/104 5075/35   
   PATH: 770/3 1 218/840 221/6 301/1 218/700 229/426   
      

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]


(c) 1994,  bbs@darkrealms.ca