Sorry for slightly off topic question. Where is a forum to ask questions about using A2OSX? Thanks.
--Steve

Steven Nelson wrote:
> Sorry for slightly off topic question. Where is a forum to ask questions
> about using A2OSX? Thanks.
> --Steve
>

I think you just found it. Ask away. :-)

On Tuesday, July 13, 2021 at 3:00:33 PM UTC-5, pklo...@gmail.com wrote:
> On Tuesday, July 13, 2021 at 3:56:23 PM UTC-4, D Finnigan wrote:
> > Steven Nelson wrote:
> > > Sorry for slightly off topic question. Where is a forum to ask questions
> > > about using A2OSX? Thanks.
> > > --Steve
> > >
> > I think you just found it. Ask away. :-)

I put my new Uthernet2 card in my iie. Copied newest STABLE.800.po and created 800k disk using Asimov on my IIGS. Booted 800k disk on IIe and copied the files to CFFA disk (CF1/A2OSX/) A2OSX.SYSTEM seems to run fine. Join network with nets2 in root directory. Ran 'adm update a2osx' fine (It took forever ... ~8hr).
Now on to httpd. Where are the web pages supposed to go? How to connect from a browser?
telnetd. Can telnet from my raspberrypi but some linefeeds are missing so prompt overwrites last line of output. Any fix/workaround?
Where are the help files and man pages? Other than the Feb 2020 guides I am running blind with just my linux skills (minimal at best but google helps).
Lots of newbie questions but I'll start with these. Thanks.
--Steve

On Tuesday, July 13, 2021 at 5:09:00 PM UTC-4, Steve wrote:
> I put my new Uthernet2 card in my iie. Copied newest STABLE.800.po and created 800k disk using Asimov on my IIGS. Booted 800k disk on IIe and copied the files to CFFA disk (CF1/A2OSX/) A2OSX.SYSTEM seems to run fine. Join network with nets2 in root directory. Ran 'adm update a2osx' fine (It took forever ... ~8hr).
> Now on to httpd. Where are the web pages supposed to go? How to connect from a browser?
> telnetd. Can telnet from my raspberrypi but some linefeeds are missing so prompt overwrites last line of output. Any fix/workaround?
> Where are the help files and man pages? Other than the Feb 2020 guides I am running blind with just my linux skills (minimal at best but google helps).
> Lots of newbie questions but I'll start with these. Thanks.
> --Steve

- On the **adm update a2osx** issue, the two longest running tasks in this script are 1) download of the update file and 2) unpaking that file. I just tested on my //e (set to turn off accelerator :) ) and the download took 45 seconds using the U2 and the unpak took just under 5 minutes. There is a bug in the update in one version, but I am not sure you had that one, but if you did, it should either do nothing (buy tell you that it updated your computer) or exit with an error. The only thing I can think of is that you were dropping packets for some reason, and the retransmit delay was growing too long. I would like you to try the following (where you can see what is happening)... start a2osx, you will be in root directory... nets2 to start network.. cd ../tmp to go into tmp directory. httpget update.a2osx.net -u update.2502 -o update.2502 download file, you will see progress. see if it starts to slow down... if it completes quickly, then chtyp 0cf update.2502 (if you have a more current build you can do chtyp pak update.2502, if not you are changing file type to 0cf with a zero). now cd .. to go into directory with a2osx.system in it and do unpak tmp/update.2502 that will make sure you are current. it should take 5 minutes. reboot. my timing was done on //e cffa and u2 so it should be the same.

- For httpd, you need to create a file in etc called httpd.conf containing the following lines:
# HTTPD Config file
ServerName myserver.mydomain.org:6580
Listen 6580
DocumentRoot ${ROOT}srv/www

change the myserver.mydomain.org to be whatever your box responds too and the 6580 (in both places) to the port you want httpd to listen on, you can make it 80, or if you are like a lot of people that have 1 ip address and a cable modem or something that needs to point to different web servers, you can use a different port. The DocumentRoot points to where your web site pages are stored. note ${ROOT} basically points to the directory where A2OSX.SYSTEM is located. so etc for instance is referenced by ${ROOT}etc see how there is no / between because ${ROOT} actually means /FULLBOOT/ not /FULLBOOT or in your case i am guess /CF1/A2osX/ so in that dir make an srv subdir (for server data) and in that dir make a sub dir called www (for web server data). or make a directory anywhere and point DocumentRoot at that ( it does not have to be relative, it can be /MYHD/mydir which means the pages will be served from the volume /MYHD and the directory on the volume called mydir ). If you want our sample pages, i could put a PAK file of them available for you on the server to httpget. To connect from a browser, first try http://ip.address.of.u2/webpage:6580 if that works, then try with domain name stuff. note. an apple is not a speed demon, so it can take time for the first page to load, especially if you have a lot of graphics on it or something. also note, just a text file called hello that only has the line It worked! can be served, so put that in your web dir and try http://ip/hello:6580

- on telnetd, one of two things, either the term type is not being set right on linux side, make sure you are set for vt100, or ansi should work. there is also some setting in telnet called "crlf" that you can turn on and off (i think you have to have a settings file, not a telnet person :) ) I do remember having this problem myself, and I think it was solved by getting the TERM type set right.

- Help/man files are actually in process for the next release (and possibly demo at kansasfest next week!). There is a lot of doc on the github pages.. It is for the 0.93 release (httpd is 0.94 thing, so not in yet). I will push an update after kfest is over and when the new online help goes out.

Patrick

On Tuesday, July 13, 2021 at 5:08:27 PM UTC-5, pklo...@gmail.com wrote:
> 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.

One more question: Does cifsd work? Example?
Thanks,
--Steve

On Tuesday, July 13, 2021 at 7:33:16 PM UTC-5, Steven Nelson wrote:
> On Tuesday, July 13, 2021 at 5:08:27 PM UTC-5, pklo...@gmail.com wrote:
> > 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 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