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 21,668 of 21,939   
   bp to All   
   Re: Javascript restriction in Trixie   
   14 Dec 25 17:30:01   
   
   MSGID: <10hk3me$6453$2@dont-email.me> a32489d9   
   REPLY: <10h9fov$s9su$2@dont-email.me> 7b2fa724   
   PID: PyGate 1.5.2   
   TID: PyGate/Linux 1.5.2   
   CHRS: ASCII 1   
   TZUTC: 1100   
   REPLYADDR bp@www.zefox.net   
   REPLYTO 3:633/10 UUCP   
   bp@www.zefox.net wrote:   
   > bp@www.zefox.net wrote:   
   >> Daniel James  wrote:   
   >>> On 07/12/2025 18:55, bp@www.zefox.net wrote:   
   >>>> WARNING: Use --enable-native-access=ALL-UNNAMED to avoid a warning for   
   callers in this module   
   >>>    
   >>> Have you done that?   
   >>    
   >> After a fashion, yes. I tried appending   
   >> --enable-native-access=ALL-UNNAMED   
   >> on the command line, but it made no difference.   
   >>    
   >> Clearly, the restriction is new(ish) and there's no obvious reason to    
   >> think that's the right place put the option. The references I found on-line   
   >> to this change date from 2025, the application was last updated in 2022   
   IIRC.   
   >>    
   >> Thanks for writing!   
   >>    
   >> bob prohaska   
   >>    
   > It turns out there's a problem report that resembles mine at   
   > https://github.com/florentbr/OWON-VDS1022/issues/76   
   > but it doesn't offer an explicit resolution.    
   >    
   > At this point I have Trixie and Bookworm installs that don't connect    
   > and a somewhat older Bookworm install that worked out of the box. So   
   > far, the one that works is on a 33 bit Pi2.   
      
   I made a copy of the working microSD, booted that and verified it could   
   communicate with the 'scope. Then I invited the system to upgrade and   
   it made about 350 changes to packages. After that, the 'scope couldn't   
   be connected to.    
      
   So, clearly, an incompatibility has been introduced by the upgrade.    
      
   Is there some way to selectively update and revert when trouble strikes?   
   It isn't something I _have_ to fix, but it might be useful to know now.   
      
   Thanks for reading,   
      
   bob prohaska   
      
      
   --- PyGate Linux v1.5.2   
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)   
   SEEN-BY: 105/81 106/201 128/187 129/14 305 153/7715 154/110 218/700   
   SEEN-BY: 226/30 227/114 229/110 112 134 200 206 275 300 317 400 426   
   SEEN-BY: 229/428 470 616 664 700 705 266/512 291/111 292/854 320/219   
   SEEN-BY: 322/757 342/200 396/45 460/58 633/10 280 414 418 420 422   
   SEEN-BY: 633/509 2744 712/848 770/1 902/26 2320/105 5020/400 5075/35   
   PATH: 633/10 280 229/426   
      

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


(c) 1994,  bbs@darkrealms.ca