TZUTC: -0500   
   MSGID: 55096.sync@1:103/705 2d604748   
   REPLY: 55085.sync@1:103/705 2d5fc3ec   
   PID: Synchronet 3.18c-Linux  Nov  9 2020 GCC 4.8.5   
   TID: SBBSecho 3.30-Linux master/88b423313 Sep 29 2025 GCC 12.2.0   
   COLS: 196   
   BBSID: HDCBBS   
   CHRS: CP437 2   
   FORMAT: flowed   
   NOTE: FSEditor.js v1.104   
     Re: Upgrading from v3.18 on CentOS7 to Ubuntu 25.04   
     By: Digital Man to Jason on Wed Oct 22 2025 10:01 pm   
      
    >  > I then do the /sbbs/exec/jsexec update and it doesn't seem to work.   
    >   
    > What makes you say that? Is the update.js current (the latest from the Git   
   repo)?   
      
   I think this may be the problem, so im going to start over with the upgrade   
   and try this. Question, after i compile with symlinks, it appears that it's   
   symlinking the executables but not any of the .js files. Is this right? Did i   
   miss a step somewhere in the instructions? I would have thought it would have   
   moved this stuff over?   
      
   Also, should it link the executables or create a symlink for the exec folder   
   over to the exec folder inside of the repo directory? This is where it gets   
   fuzzy for me because i'm not reading this in the instructions or im not   
   understanding it properly. I am dense at times, so it's probably me, but im   
   confused.. should i just move update.js script over by itself then?   
      
   For context, here is the header in my current exec/update.js file:   
      
   /* $Id: update.js,v 1.10 2020/05/05 01:09:27 rswindell Exp $ */   
      
   Here is the one in /sbbs/repo/exec:   
      
   /* Synchronet v3.15+ update script (to be executed with jsexec) */   
      
   So definitely a newer version there.   
      
   Also, the compile did create the symlinks for the update_to_v319 and   
   update_to_v320 but not one for update.js   
      
   Here is the files from my /sbbs/exec folder:   
      
   -rw-r--r--  1 sbbs sbbs   5244 Nov 10  2020 update.js   
   lrwxrwxrwx  1 root root     62 Oct 23 04:16 upgrade_to_v319 -> /   
   bbs/repo/src/sbbs3/gcc.linux.x64.exe.release/upgrade_to_v319   
   lrwxrwxrwx  1 root root     62 Oct 23 04:16 upgrade_to_v320 -> /   
   bbs/repo/src/sbbs3/gcc.linux.x64.exe.release/upgrade_to_v320   
      
      
   ----   
      
    > Look at the ctrl/main.ini file - does it have your BBS name, etc. in it? If   
   not, then there was no conversion of the your old ctrl/*.cnf files to   
   ctrl/*.ini, and if that's the case, then you   
    > ran   
    > the wrong update.js or something like that.   
      
   Here is a sample of the first few fields in the main.ini up to my system   
   password which i didn't copy here:   
      
   Hard Drive CafeHDCBBSMontgomery, Alabama!!!!!!!!!!!!JasonThe Guru   
      
   ----   
      
   What I am going to do is attempt to re-do the update on this new server,   
   manually copy over the new update.js file over to the /sbbs/exec directory and   
   then attempt to run that and see what I get. Maybe this will solve all my   
   issues. Still would like to know if i missed a step or something i didn't read   
   right. But as always thanks DM for your quick response! You've always been   
   great for me and I appreciate you!   
      
   ---   
    þ Synchronet þ Hard Drive Cafe - hdcbbs.com   
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)   
   SEEN-BY: 4/0 88/0 90/0 93/1 103/705 105/81 106/201 124/5016 128/187   
   SEEN-BY: 129/14 153/757 7715 154/10 30 110 203/0 218/700 221/0 6 226/30   
   SEEN-BY: 227/114 229/110 206 317 400 426 428 470 700 705 240/1120   
   SEEN-BY: 240/5832 263/1 266/512 280/464 5003 5006 291/111 292/8125   
   SEEN-BY: 301/1 310/31 320/219 322/757 341/66 200 234 342/200 396/45   
   SEEN-BY: 423/120 460/58 633/280 712/848 770/1 900/0 102 106 902/0   
   SEEN-BY: 902/19 26 904/0 13 905/0 5019/40 5020/400 5075/35   
   PATH: 103/705 280/464 341/66 902/26 229/426