From: pklo...@gmail.com   
      
   > > > On Tuesday, July 13, 2021 at 5:09:00 PM UTC-4, Steve wrote:    
   > > Thanks Patrick. I will try all your suggestions. One note on the update   
   try - I did this from a telnet session on my raspberrypi, not from the //e   
   console. After reboot and from the console/tty, update reported my system was   
   up to date. Telnet may    
   have been my achilles heel.   
   > I manually downloaded update.2502. All went well (222778 bytes). Unpaked   
   update.6502. All went well. Rebooted. but build is still 2491, not 2502.   
   Repeated the steps. Rebooted - build is still 2491. Is build msg wrong or is   
   a2osx not being updated - how    
   can I tell? ${ROOT}tmp/LATEST says build is 2502. Unpak did replace all the   
   files.    
   >    
   > PS: Patrick, I am registered on slack if you prefer I go there. Which   
   discussion group?    
   > --Steve   
      
   On slack, use the invite I posted above to join the a2osx group and the   
   #testing-94 channel is the most active.  There are other channels their for   
   asm, forth, bbs (acos) etc.   
      
   On the failure to update via telnet session, that was probably the cause, but   
   not because of some different user behavior of a process via a telnet session   
   vs. the console but simply because of memory.  WHen you boot a2osx, you have   
   like 26K of free main    
   mem.  Load the U2 drivers and network stack and you are down to 16K.  Load   
   telnetd and you are down to xx.  Load httpd at same time and down more.    
   httpget manually is a 2k process that needs another 1k to download the file.    
   unpak about the same.  but    
   the update script called from the adm script are text files that have to fully   
   loaded in memory and they have a lot of comments.  they take probably another   
   5K.  I am guessing you ran out of memory.  I am waiting for the csh/cc system   
   to be complete    
   before a rewrite to save that.  In the future, do updates with out the servers   
   running.   
      
   On your system saying its running 2491, its not, you did the update, but    
   ../etc/version (what actually holds the value uname uses) and ../etc/issue the   
   file that gets displayed at boot up, did not get remade.  edit ../etc/issue to   
   say what you like :)     
   and do this at prompt   **echo  2502 > ../etc/version**  that will fix the   
   internal number so update will work right   
      
   Patrick   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)