I think for this next synch update I might just start a whole new fresh install and then move everything over. I haven't updated since the repository switch. Does that make more sense or should I try and update?
I think for this next synch update I might just start a whole new fresh install and then move everything over. I haven't updated since the repository switch. Does that make more sense or should I try and update?
You should update. There's never a need for a "fresh install".
Re: Upgrading
By: Digital Man to The Lizard Master on Wed Nov 02 2022 04:05 pm
I think for this next synch update I might just start a whole new fresh install and then move everything over. I haven't updated since the repository switch. Does that make more sense or should I try and update?
You should update. There's never a need for a "fresh install".
Okay thanks, I'l just do a backup. I saw you did a full video on full linux install, can I reference that for update too or do you happen to have an update one as well?
Appreciate the support as always!
No video, but there's instructions here: https://wiki.synchro.net/howto:git
Re: Upgrading
By: Digital Man to The Lizard Master on Thu Nov 03 2022 12:50 pm
No video, but there's instructions here: https://wiki.synchro.net/howto:git
Perfect! I'm sure I'm really close with this. I cloned fine into repo dir, I compiled fine after seeing an earlier reply you had for the libarchive-dev package, but this is where my linux shortcomings come up. It gets to the end and I get this:
make: *** No rule to make target 'symlinks'. Stop.
This is what I would run in the past:
make RELEASE=1 setcap symlinks
After a bit of googling I'm thinking it has to do with the fact I initially installed in /home/ubuntu/ and that itself is a symlink. Without wasting anyone's time, am I on the right track? I'm not sure why it would work without issue before though. I think I'm real close though thanks!
Re: Upgrading
By: Digital Man to The Lizard Master on Thu Nov 03 2022 12:50 pm
Perfect! I'm sure I'm really close with this. I cloned fine into repo dir, I compiled fine after seeing an earlier reply you had for the libarchive-dev package, but this is where my linux shortcomings come up. It gets to the end and I get this:
make: *** No rule to make target 'symlinks'. Stop.
This is what I would run in the past:
make RELEASE=1 setcap symlinks
More likely, you don't have the SBBSCTRL env var set. https://wiki.synchro.net/install:nix#errors
This is what I would run in the past:
make RELEASE=1 setcap symlinks
Instead of "symlinks" there it should be SYMLINK=1
Re: Upgrading
By: The Lizard Master to Digital Man on Fri Nov 04 2022 03:49 pm
Re: Upgrading
By: Digital Man to The Lizard Master on Thu Nov 03 2022 12:50 pm
Perfect! I'm sure I'm really close with this. I cloned fine into repo dir, I compiled fine after seeing an earlier reply you had for the libarchive-dev package, but this is where my linux shortcomings come up. It gets to the end and I get this:
make: *** No rule to make target 'symlinks'. Stop.
This is what I would run in the past:
make RELEASE=1 setcap symlinks
Instead of "symlinks" there it should be SYMLINK=1
Re: Upgrading
By: Digital Man to The Lizard Master on Fri Nov 04 2022 01:00 pm
More likely, you don't have the SBBSCTRL env var set. https://wiki.synchro.net/install:nix#errors
I believe it's set correct. This is what the command line looks like (after it seems like everyhing went fine for compile, etc).
sudo `whereis -b setcap | cut -d" " -f2` 'cap_net_bind_service=+ep' gcc.linux.x64.exe.release/sbbs
make: *** No rule to make target 'symlinks'. Stop. ubuntu@ip-172-31-45-118:~/sbbs/repo/src/sbbs3$ printenv SBBSCTRL /home/ubuntu/sbbs/ctr
I haven't moved the exec dir, I'm just using stanard synch structure so I don't think I need to set the SBBSEXEC ev.
Which makefile are you referring to? "symlinks" is only a valid target for t src/sbbs3/GNUmakefile and only if/when the SBBSCTRL or SBBSEXEC env vars are set.
Which makefile are you referring to? "symlinks" is only a valid target for t src/sbbs3/GNUmakefile and only if/when the SBBSCTRL or SBBSEXEC env vars are set.
Okay, I think it was a permissions issue (and probably one that still persists). I got a permission error when I tried to execute
make RELEASE=1 setcap symlinks
So then I was running sudo make RELEASE=1 setcap symlinks and getting the symlinks error. I reset the folder permissions on sbbs, and now it appears to run completely and without issue.
However, I still don't see any files getting updated in my main SBBS directory so I'm still missing something. But I am no longer getting any error running that command. Is there anything permissions wise that I need to look out for? I recursively updated the folders so they were all set to the sub user.
Okay, well scratch all this, I had written this and not restarted. It now says copyright 2022! I got some javascript errors logging in which I will check into now. So I guess in the future one thing I can add to the install list is to check permissions I guess? Sorry about that!
Okay, well scratch all this, I had written this and not restarted. It now says copyright 2022! I got some javascript errors logging in which I will check into now. So I guess in the future one thing I can add to the install list is to check permissions I guess? Sorry about that!
Re: Upgrading
By: The Lizard Master to Digital Man on Mon Nov 07 2022 03:36 pm
Okay, well scratch all this, I had written this and not restarted. It now says copyright 2022! I got some javascript errors logging in which I will check into now. So I guess in the future one thing I can add to the install list is to check permissions I guess? Sorry about that!
Looks like I am all upgraded fine except missing some of the /exec files. I copied over the ones I noticed coming up with errors (i.e. preext.js, I just didn't have it). Is there a standard method to update these? Or just download off git and save?
The Lizard Master wrote to Digital Man <=-
Okay, well scratch all this, I had written this and not restarted. It now says copyright 2022! I got some javascript errors logging in which I will check into now. So I guess in the future one thing I can add to the install list is to check permissions I guess? Sorry about that!
Looks like I am all upgraded fine except missing some of the
/exec files. I copied over the ones I noticed coming up with
errors (i.e. preext.js, I just didn't have it). Is there a
standard method to update these? Or just download off git and
save?
You mean prextrn.js? It's in the exec directory of the repo you cloned (e.g. in sbbs/repo/exec). The "standard" method is that your sbbs/exec directory is as symlink to the sbbs/repo/exec directory, but if it's not, you could copy the files manually, though you risk overwriting any of your own local changes that way.
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 409 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 48:33:51 |
| Calls: | 8,570 |
| Files: | 13,222 |
| Messages: | 5,929,190 |