Re: [IBMiOSS] Python, ACS, Open Source and MKDocs

[Joe Pluta <joepluta@xxxxxxxxxxxxxxxxx>]

Thanks, Kevin!  I've found two competing pages on the subject.  There's 
the one you mention below, which (among other things) tells me how to 
set my path permanently via .profile.  I also found this page:

https://www.shieldadvanced.com/Blog/ibm-i/setting-up-ssh-access-to-ibm-i/

Here, Chris uses .profile to change the shell to bash, but then uses 
.bashrc to set the path.  These two pages slightly conflict, and also I 
note that the first page doesn't seem to change the shell for the 
session.  I admit I'm pretty clueless here, but I'm doing my best.  
Chris' page also mentions 5733SC1 which I don't have installed, but that 
hasn't stopped me from starting the SSHD server (which in turn enabled 
the open source package management option of ACS). Interestingly, 
though, there is no SSHD server in my list of servers in System i Navigator.

Anyway, I'm dragging slightly further afield here.  I of course tried to 
do it my own way and stuffed the PATH and the exec both into my 
.profile, like so:

 ************Beginning of data**************
PATH=/QOpenSys/pkgs/bin:$PATH
exec /QOpenSys/pkgs/bin/bash
 ************End of Data********************

Seems like it might work.  Then I don't have to fiddle with .bashrc.  
But who knows, maybe that's a bad idea.  It gives me results I don't 
particularly like when I start my session.  For starters, I see this:

bash: cannot set terminal process group (-1): A system call received a 
parameter that is not valid.
bash: no job control in this shell
bash-4.4$

And at that point, the shell does strange things (it responds to 
keyboard input in an odd way, and I have to hit enter twice to see 
things).  But as has been pointed out, QSH probably isn't the way to go 
anyway, so my next trick is to get another session attached.  Maybe 
PuTTY, maybe something else.  I can't remember what I used in the past 
to talk to my VM sessions.


On 12/17/2020 5:33 PM, Kevin Adler wrote:
>     Sounds like you have found the 5733-OPS version. It's likely you need to
>     set your PATH. See
>     [1]https://ibmi-oss-docs.readthedocs.io/en/latest/troubleshooting/SETTING_PATH.html
>      
>      
>
>       ----- Original message -----
>       From: Joe Pluta <joepluta@xxxxxxxxxxxxxxxxx>
>       Sent by: "OpenSource" <opensource-bounces@xxxxxxxxxxxxxxxxxx>
>       To: opensource@xxxxxxxxxxxxxxxxxx
>       Cc:
>       Subject: [EXTERNAL] Re: [IBMiOSS] Python, ACS, Open Source and MKDocs
>       Date: Thu, Dec 17, 2020 5:28 PM
>        
>       Thank you, Quintin!  I can now indeed report that my python3 version is
>       3.4.10!
>
>       That's step one.  Now I have to figure out what Jack is talking about.
>
>       On 12/17/2020 2:27 PM, Quintin Holmberg wrote:
>       > Joe,
>       > Python2 and Python3 install alongside each other. "Python --version"
>       will invoke the Python2 interpreter. "Python3 --version" will invoke the
>       Python3 interpreter.
>       >
>       > --
>       > Quintin Holmberg
>       >
>       >
>       > -----Original Message-----
>       > From: OpenSource <opensource-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
>       Joe Pluta
>       > Sent: Thursday, December 17, 2020 1:52 PM
>       > To: opensource@xxxxxxxxxxxxxxxxxx
>       > Subject: [IBMiOSS] Python, ACS, Open Source and MKDocs
>       >
>       > So I'm beginning down the road of installing the MKDocs package that
>       Richard mentioned a few weeks ago.  I managed to stumble my way through
>       getting the latest version of IBM i ACS (not happy with that process at
>       all, but I digress).  I started the SSHD server, and ACS magically
>       downloaded and installed a bunch of open source goodies.  But I see
>       Python 2, not Python 3.    So I went to the Available packages and I saw
>       python3, as well as a whole suite of what I can only assume are
>       python3-related packages.  I wanted to start with the minimum, so I
>       asked it to install python3. Everything went smoothly (I don't like that
>       I seem to have to X out of the installation progress window, but that's
>       a nitpick). The package is installed.  However, when I run python
>       --version, I still see Python 2.7.16.
>       >
>       > So what does that tell me?  Is there additional configuration
>       required, or should I just continue on with my journey?  I'm just
>       concerned that I need other things for MKDocs to run, but I also don't
>       want to download the entire 500GB of additional python3 stuff if I've
>       already hosed things up.
>       >
>       > Any guidance would be much appreciated.
>       >
>       > Thanks!
>       >