|
Hey Aaron - thanks for the reply.
I'm not sure ibmichroot is the thing to do - maybe you can weigh in - this
is meant only to install Ghostscript and then execute 1 piece of it from an
RPGLE program.
I'm going this route because none of the binaries sites seem to have
Ghostscript as they used to do - the UCLA one, the BULL one - all kind of
dead.
I'm not going to be doing any development in PASE.
AND I'm on a pretty short time leash - far too long fighting with the
problem of printing as we are trying to do. So a PDF to PCL conversion will
likely take care of us, and Ghostscript is supposed to have that.
I'm going to go ahead with my limited authorization and see what happens -
will report what happens, and cheer if it's all good.
Cheers
Vern
On 8/12/2016 1:34 PM, Aaron Bartell wrote:
A couple things:--
- I don't recall why Tony initially made setup2.sh, but I am fairly
certain
setup.sh in ibmiperzl project should have incorporated the changed from
setup2.sh.
- You should be using what's on bitbucket. We need help migrating
documentation out of YiPs so we can eventually sunset the YiPs page(I
agree, it is confusing, as your experiencing). If anyone would like to
help with that it would be much appreciated.
- The success of junk.sh leads me to believe it might have to do with the
authority of your profile. Also, while it is a pain to have authority
issues, it's a good thing to bump into if it was meant to be in place,
because it's proving the security is working. The perzl.org rpms
~should~
require you to have high authority because they will have potentially
significant changes to other PASE processes on your system. Specifically,
think of PASE as having a primary library list named PATH that everyone
shares (PATH is the name of an environment variable). Then imagine
somebody installing a new RPG *SRVPGM in a new library that has
~same-named
exports~ as other RPG *SRVPGMs already in your library list. This will
obviously cause issues when a calling RPG program attempts to resolve RPG
sub procedure calls.
- Further to the above comment about security, one of the reasons the
ibmichroot(n1) project was created was so you could be a *USER class user
and still have full authority to install things in your chroot environment
(they are also sometimes called "chroot jails").
- If you want to stick with ibmiperzl** then I think you need to get a
higher authority profile involved. Let us know what authorities are
needed
so we can update the ibmiperzl readme (or even better, do a
fork/pull-request with the change).
**Opinion: I recommend using ibmichroot over ibmiperzl for most things
because they have duplication of effort(n2), but ibmichroot has the
additional feature of chroot.
n1 - https://bitbucket.org/litmis/ibmichroot
n2 -
https://bitbucket.org/litmis/ibmiperzl/issues/2/ibmiperzl-vs
-ibmichroot-duplication-of
On final note, I know some will critique the various projects/sites
mentioned here and say "what sort of a mess are you guys creating and why
aren't you cleaning things up?" And to that I'd say, I am sorry we have a
mess and I ask for community support to help tidy things up.
Aaron Bartell
litmis.com - Services for open source on IBM i
On Fri, Aug 12, 2016 at 12:42 PM, Vernon Hamberg <
vhamberg@xxxxxxxxxxxxxxx>
wrote:
Another thing - I see on the litmis ZIP file a setup.sh and wwwperzl.sh -
I see on a YIPS site that there's a setup2.sh and a new wwwperzl.sh
So which should I be using? I hope I have the details right!
Thanks again
Vern
On 8/12/2016 11:10 AM, Aaron Bartell wrote:
First, are you running this from an SSH session (i.e putty from your
laptop) or from CALL QP2TERM?This is the IBMi Open Source Roundtable (OpenSource) mailing list
Second, when I run into issues like this I try to eliminate possible
issues
(i.e. ownership) and incrementally build up to the issue. Run both of
the
below commands and let us know if they both run successfully.
$ echo "echo 'something'" >> junk.sh
$ chmod +x junk.sh
Aaron Bartell
litmis.com - Services for open source on IBM i
On Fri, Aug 12, 2016 at 10:47 AM, Vernon Hamberg <
vhamberg@xxxxxxxxxxxxxxx>
wrote:
Folks
I downloaded the ZIP from the litmis page on bitbucket - made the
download
directory in /QOpenSys - put contents of ZIP into it - CD's to it - and
did
this from the "instructions" on the litmis page -
First I ran ls -l and got this -
ls -l
total 22304
-rwxrwxrwx 1 guest 0 1105 Jul 13 11:06 LICENSE
-rwxrwxrwx 1 guest 0 4754 Jul 13 11:06 README.md
-rwxrwxrwx 1 guest 0 192 Jul 13 11:06 ftpcompile.sh
-rwxrwxrwx 1 guest 0 2408448 Jul 13 11:06 rpm.rte
-rwxrwxrwx 1 guest 0 1676 Jul 13 11:06 setup.sh
-rwxrwxrwx 1 guest 0 397520 Jul 13 11:06
wget-1.9.1-1.aix5.1.ppc.rpm
-rwxrwxrwx 1 guest 0 7260160 Jul 13 11:06
www.oss4aix.org.deps.tar
-rwxrwxrwx 1 guest 0 608761 Jul 13 11:06
www.oss4aix.org.site.dirs
-rwxrwxrwx 1 guest 0 233 Jul 13 11:06 wwwclean.sh
-rwxrwxrwx 1 guest 0 139066 Jul 13 11:06 wwwinstall.sh
-rwxrwxrwx 1 guest 0 12461 Jul 13 11:06 wwwperzl.sh
All the objects have x, but I did this anyhow, as in the "instructions"
chmod +x setup.sh
chmod: setup.sh: Operation not permitted.
So it appears either I don't have the right authority or it balks
because
everything already has x mode - too long since I did this with Debian
18
years ago!
Thanks
Vern
--
This is the IBMi Open Source Roundtable (OpenSource) mailing list
To post a message email: OpenSource@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/opensource
or email: OpenSource-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/opensource.
--
To post a message email: OpenSource@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/opensource
or email: OpenSource-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/opensource.
This is the IBMi Open Source Roundtable (OpenSource) mailing list
To post a message email: OpenSource@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/opensource
or email: OpenSource-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/opensource.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
