Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Sun 08 Dec 2019, 00:04
All times are UTC - 4
 Forum index » Advanced Topics » Cutting edge
tiny_puduan_ascii-PreAlpha11.5 (made via a woof-next fork)
Moderators: Flash, Ian, JohnMurga
Post new topic   Reply to topic View previous topic :: View next topic
Page 3 of 6 [82 Posts]   Goto page: Previous 1, 2, 3, 4, 5, 6 Next
Author Message
s243a

Joined: 02 Sep 2014
Posts: 2199

PostPosted: Wed 10 Jul 2019, 23:42    Post subject:  

s243a wrote:
s243a wrote:
The package managers that I'm using:
1. sc0tmann's pkg
2. mistfires ppm3

seem to depend on the symlink:
/initrd/pup_ro1

and there seems to be a bug in my ISO where this isn't being created properly in the initrd0/init script. I don't know if it was an issue with the woof-CE snapshot that I pulled or something that I did. However, in the short term I'm going to patch with a fix like follows:

Code:

#!/bin/sh
. /etc/rc.d/PUPSTATE
SAVE_REL="$(echo $PUPSAVE | cut -d',' -f3)"
SAVE_PATH="/initrd/mnt/dev_save$SAVE_REL"

if [ -d "$SAVE_PATH" ] ; then
  if [ -d /initrd/pup_ro1 ]; then
     cp -arfv --remove-destination "$SAVE_PATH"
     rm -rf /initrd/pup_ro1
  elif [ -L /initrd/pup_ro1 ]; then
    rm -rf /initrd/pup_ro1
  fi
  if [ ! -L /initrd/pup_ro1 ]; then
    ln -sv "$SAVE_PATH" /initrd/pup_ro1 #for after switch
  fi
fi

https://pastebin.com/0gLTFNdv

Maybe I"ll call this script when starting x. I'll test this sortly.

Eventually, of course a I'll both:
1. debug my /initrd/init script
2. remove the dependencies of said package managers on this symlink.

The reason for the later is that the symlink is for lagacy apps:

gyrog tells me that:
Quote:
That symlink is there for old utilites that have /initrd/pup_ro1 hardcoded, rather than being coded the better way.

https://github.com/puppylinux-woof-CE/woof-CE/issues/1469#issuecomment-504771021

More about this topic can be found in the thread:
Process Substitution & The pup initr0/init


After more thought I think the following is more what I want:

Code:

#!/bin/sh
. /etc/rc.d/PUPSTATE
SAVE_REL="$(echo $PUPSAVE | cut -d',' -f3)"
SAVE_PATH="/initrd/mnt/dev_save$SAVE_REL"

if [ -d "$SAVE_PATH" ] ; then

  if [ -d /initrd/pup_ro1 ] && [ ! -L /initrd/pup_ro1 ]; then
     cp -arfv --remove-destination /initrd/pup_ro1 "$SAVE_PATH"
     rm -rf /initrd/pup_ro1 
     ln -sv "$SAVE_PATH" /initrd/pup_ro1 #for after switch
  fi
fi


I'm wondering if the missing symlink is due to not having the right version of aufs-tools. For some reason I have a mount.aufs binary that requires too new a version of libc. I'm not sure how I would have got this "too new" version because my libc is newer than the one in devaun ascii.

Anyway, full mount fails if mount.aufs is too new. Also "busybox mount" fails if we use tinycores version of busybox. Here's an example that fails from sc0ttman's pkg:
Code:

busybox mount -t aufs -o remount,udba=reval unionfs / #remount with faster evaluation mode.

https://gitlab.com/sc0ttj/Pkg/blob/master/usr/sbin/pkg#L4918

the reason is that tinycore has separated the busybox applets into two parts. Those which only root can use are in /bin/busybox. Those in which some non-root users can use are in busybox.suid

I could create a wrapper script for busybox that calls the correct binary, although there would be a slight performance cost to do this.

Edit 1:
Here is more on this error:
Code:


      #120102 install may have overwritten a symlink-to-dir...
      #tar defaults to not following symlinks, for both dirs and files, but i want to follow symlinks
      #for dirs but not for files. so, fix here... (note, dir entries in .files have / on end)

https://gitlab.com/sc0ttj/Pkg/blob/master/usr/sbin/pkg#L4820

Code:

#120107 rerwin: need quotes around some paths in case of space chars. remove '--unlink-first' from tar (was introduced 120102, don't think necessary).

/woof-code/rootfs-skeleton/usr/local/petget/installpkg.sh#L26

Code:

tar -x --strip=2 --directory=${DIRECTSAVEPATH}/ -f ${tarball} #120102. 120107 remove --unlink-first

/woof-code/rootfs-skeleton/usr/local/petget/installpkg.sh#L254


related to how tinycore splits up the busybox apps between busybox and busybox.suid. I want to do something like the following:

Code:

if [ ! $1 ]; then
  busybox mount || busybox.suid mount || mount-FULL || exit 1
  exit 0
fi


which is a replacement to the following line in the puppy mount script:

Code:

[ ! $1 ] && exec busybox mount

/rootfs-skeleton/bin/mount#L17

So basically I'm using some fallback commands here in case busybox doesn't have the mount applet. If I created the wrapper script that I suggested above then I wouldn't need to do this but I think the less code that depends on said wrapper script the more robust the code will be.

I'm not an expert on everything linux so I don't know if my code is equivalent but the best I can tell is that all the exec does is to avoid executing the remainder of the script. I think the same thing can be acompblished with the exit command.

_________________
Find me on minds and on pearltrees.
Back to top
View user's profile Send private message Visit poster's website 
s243a

Joined: 02 Sep 2014
Posts: 2199

PostPosted: Thu 11 Jul 2019, 00:00    Post subject:  

Another thing that I noticed is that the save button on the desktop seems to delete the symlinks /initrd/pup_ro1 and /initrd/pup_rw. I posted a related question about this on github:

Quote:

I noticed in my build ( a woof-next fork) clicking the save button on the desktop causes the symlinks /initrd/pup_ro1 and /initrd/pup_rw to disapear. I looked in both the files snapmergepuppy and save2flash and I can't see any place where these symlinks are recreated and I don't know what layer in which these symlinks are supposed to reside. I did notice though that in a lot of the snapmergepuppy code the initrd directory is excluded.

This means that I can't troubleshoot this issue at the moment. Maybe, I'll add a hack at the end of snapmerge puppy to fix these symlinks if they are missing.

https://github.com/puppylinux-woof-CE/woof-CE/issues/1469#issuecomment-510318923

_________________
Find me on minds and on pearltrees.
Back to top
View user's profile Send private message Visit poster's website 
darry19662018

Joined: 31 Mar 2018
Posts: 651
Location: Rakaia

PostPosted: Sun 14 Jul 2019, 03:27    Post subject:  

This Pup is coming a long nicely. Look forward to the next release - I use this regularly now set up with clipgrab and basic multimedia setup.
_________________
Puppy Linux Wiki: http://wikka.puppylinux.com/HomePage

https://freemedia.neocities.org/
Back to top
View user's profile Send private message Visit poster's website 
darry19662018

Joined: 31 Mar 2018
Posts: 651
Location: Rakaia

PostPosted: Sun 14 Jul 2019, 06:42    Post subject:  

Wiki entry: http://wikka.puppylinux.com/Tiny_Puduan
_________________
Puppy Linux Wiki: http://wikka.puppylinux.com/HomePage

https://freemedia.neocities.org/
Back to top
View user's profile Send private message Visit poster's website 
darry19662018

Joined: 31 Mar 2018
Posts: 651
Location: Rakaia

PostPosted: Mon 15 Jul 2019, 04:04    Post subject:  

Right finally made a smaller iso with my additions to the original iso as described earlier using an adrv instead of a save folder - using dir2sfs and isomaster https://archive.org/download/tiny_puduan_asciiprealpha11revised/iney_puduanascii_Prealpha11%28rev4%29%28darry1966%29.iso
_________________
Puppy Linux Wiki: http://wikka.puppylinux.com/HomePage

https://freemedia.neocities.org/
Back to top
View user's profile Send private message Visit poster's website 
s243a

Joined: 02 Sep 2014
Posts: 2199

PostPosted: Fri 19 Jul 2019, 15:22    Post subject:  

darry19662018 wrote:
I have been working with this iso and have go quite a lot working including mpv and a working firewall, isomaster, retrovol, pfind, xarchive and peasy firewall monitor as well as getting ntp, ntpd set-up working for correct system time.

I made an iso using isomaster as remaster2 wouldn't work here is my first working iso
https://archive.org/details/tiny_puduan_asciiprealpha11revised

iso: https://archive.org/download/tiny_puduan_asciiprealpha11revised/tiny_puduan_asciiPrealpha11%28revised%29.iso


The actual command is:
Code:

/usr/sbin/remasterpup2


At this point though it might take some troubleshooting to get it to work Sad

I have done some of this troubleshooting and will give it a try.

_________________
Find me on minds and on pearltrees.
Back to top
View user's profile Send private message Visit poster's website 
s243a

Joined: 02 Sep 2014
Posts: 2199

PostPosted: Fri 19 Jul 2019, 15:48    Post subject:  

s243a wrote:
s243a wrote:
s243a wrote:
The package managers that I'm using:
1. sc0tmann's pkg
2. mistfires ppm3

seem to depend on the symlink:
/initrd/pup_ro1

and there seems to be a bug in my ISO where this isn't being created properly in the initrd0/init script. I don't know if it was an issue with the woof-CE snapshot that I pulled or something that I did. However, in the short term I'm going to patch with a fix like follows:

Code:

#!/bin/sh
. /etc/rc.d/PUPSTATE
SAVE_REL="$(echo $PUPSAVE | cut -d',' -f3)"
SAVE_PATH="/initrd/mnt/dev_save$SAVE_REL"

if [ -d "$SAVE_PATH" ] ; then
  if [ -d /initrd/pup_ro1 ]; then
     cp -arfv --remove-destination "$SAVE_PATH"
     rm -rf /initrd/pup_ro1
  elif [ -L /initrd/pup_ro1 ]; then
    rm -rf /initrd/pup_ro1
  fi
  if [ ! -L /initrd/pup_ro1 ]; then
    ln -sv "$SAVE_PATH" /initrd/pup_ro1 #for after switch
  fi
fi

https://pastebin.com/0gLTFNdv

Maybe I"ll call this script when starting x. I'll test this sortly.

Eventually, of course a I'll both:
1. debug my /initrd/init script
2. remove the dependencies of said package managers on this symlink.

The reason for the later is that the symlink is for lagacy apps:

gyrog tells me that:
Quote:
That symlink is there for old utilites that have /initrd/pup_ro1 hardcoded, rather than being coded the better way.

https://github.com/puppylinux-woof-CE/woof-CE/issues/1469#issuecomment-504771021

More about this topic can be found in the thread:
Process Substitution & The pup initr0/init


After more thought I think the following is more what I want:

Code:

#!/bin/sh
. /etc/rc.d/PUPSTATE
SAVE_REL="$(echo $PUPSAVE | cut -d',' -f3)"
SAVE_PATH="/initrd/mnt/dev_save$SAVE_REL"

if [ -d "$SAVE_PATH" ] ; then

  if [ -d /initrd/pup_ro1 ] && [ ! -L /initrd/pup_ro1 ]; then
     cp -arfv --remove-destination /initrd/pup_ro1 "$SAVE_PATH"
     rm -rf /initrd/pup_ro1 
     ln -sv "$SAVE_PATH" /initrd/pup_ro1 #for after switch
  fi
fi


I'm wondering if the missing symlink is due to not having the right version of aufs-tools. For some reason I have a mount.aufs binary that requires too new a version of libc. I'm not sure how I would have got this "too new" version because my libc is newer than the one in devaun ascii.

Anyway, full mount fails if mount.aufs is too new. Also "busybox mount" fails if we use tinycores version of busybox. Here's an example that fails from sc0ttman's pkg:
Code:

busybox mount -t aufs -o remount,udba=reval unionfs / #remount with faster evaluation mode.

https://gitlab.com/sc0ttj/Pkg/blob/master/usr/sbin/pkg#L4918

the reason is that tinycore has separated the busybox applets into two parts. Those which only root can use are in /bin/busybox. Those in which some non-root users can use are in busybox.suid

I could create a wrapper script for busybox that calls the correct binary, although there would be a slight performance cost to do this.

Edit 1:
Here is more on this error:
Code:


      #120102 install may have overwritten a symlink-to-dir...
      #tar defaults to not following symlinks, for both dirs and files, but i want to follow symlinks
      #for dirs but not for files. so, fix here... (note, dir entries in .files have / on end)

https://gitlab.com/sc0ttj/Pkg/blob/master/usr/sbin/pkg#L4820

Code:

#120107 rerwin: need quotes around some paths in case of space chars. remove '--unlink-first' from tar (was introduced 120102, don't think necessary).

/woof-code/rootfs-skeleton/usr/local/petget/installpkg.sh#L26

Code:

tar -x --strip=2 --directory=${DIRECTSAVEPATH}/ -f ${tarball} #120102. 120107 remove --unlink-first

/woof-code/rootfs-skeleton/usr/local/petget/installpkg.sh#L254


related to how tinycore splits up the busybox apps between busybox and busybox.suid. I want to do something like the following:

Code:

if [ ! $1 ]; then
  busybox mount || busybox.suid mount || mount-FULL || exit 1
  exit 0
fi


which is a replacement to the following line in the puppy mount script:

Code:

[ ! $1 ] && exec busybox mount

/rootfs-skeleton/bin/mount#L17

So basically I'm using some fallback commands here in case busybox doesn't have the mount applet. If I created the wrapper script that I suggested above then I wouldn't need to do this but I think the less code that depends on said wrapper script the more robust the code will be.

I'm not an expert on everything linux so I don't know if my code is equivalent but the best I can tell is that all the exec does is to avoid executing the remainder of the script. I think the same thing can be acompblished with the exit command.


I found another related bug to this. The following command from sc0tmann's pkg is an issue:

Code:

busybox mount -t aufs -o remount,udba=reval unionfs /

_________________
Find me on minds and on pearltrees.
Back to top
View user's profile Send private message Visit poster's website 
darry19662018

Joined: 31 Mar 2018
Posts: 651
Location: Rakaia

PostPosted: Fri 19 Jul 2019, 18:23    Post subject:  

keep up the good work mate - you have made huge strides with getting this working.Smile

By the way I had to install fuse don't know whether that has any bearing?

_________________
Puppy Linux Wiki: http://wikka.puppylinux.com/HomePage

https://freemedia.neocities.org/
Back to top
View user's profile Send private message Visit poster's website 
s243a

Joined: 02 Sep 2014
Posts: 2199

PostPosted: Fri 19 Jul 2019, 22:15    Post subject:  

darry19662018 wrote:
keep up the good work mate - you have made huge strides with getting this working.Smile


thanks for your encouragment Smile

Quote:

By the way I had to install fuse don't know whether that has any bearing?


I don't think that fuse is required but I'll keep this in mind just in case I'm wrong.

Anway, regarding how busybox is split I have a plan for the wrapper function.

I'm going to create a directory called:
Code:

/bin/bb_utils


that will link each busybox util to either busybox.nosuid or busybox.suid.

I have a rough outline of the script (not tested yet):
https://pastebin.com/411AzLuR

which will create all the necessary symlinks and a wrapper function that will simply take the command passed to busybox and call the coresponding util located in /bin/bb_utils.

One can if they want to test to see if an ap works with only busybox utilities (rather than the full version), simply prepend /bin/bb_utils to the PATH variable.

Now regarding as to why tinycore may have done this. I belive that for the busybox login manager to work correctly the suid bit needs to be set but perhaps for some applets busybox allows elevated privlages that others think it shouldn't allow elevated privalges. If that happens to be the case then having these apps in a seperate multi-call binary would prevent busybox from doing this.

P.S. for the above script that I'm starting to write, I probably also want to redirect (i.e. change the symlink of) each util symlinked to busybox to the appopriate binary.

Edit: I've done some testing of the mk_busybox_utils in the above link. It is working okay now so I'll try to remaster.

_________________
Find me on minds and on pearltrees.
Back to top
View user's profile Send private message Visit poster's website 
s243a

Joined: 02 Sep 2014
Posts: 2199

PostPosted: Sat 20 Jul 2019, 22:52    Post subject:  

I noticed something else regarding the remaster script. After fixing a bunch of errors (i.e. installing mising dependencies for the remaster script), I get an error that my pup is too old. However, the Irony here is that the DISTRO_IDSTRING doesn't exist on newer versions of puppy:

Code:

if [ ! "$DISTRO_IDSTRING" ];then #101107
  #need some stuff in here if want to support older puppies. maybe also more fixes needed further down.
 /usr/lib/gtkdialog/box_ok "RemasterPup" error "Sorry, your Puppy is too old for this script"
 exit
else

/woof-code/rootfs-packages/puppycore_noarch/usr/sbin/remasterpup2#L673 (s243a .. first commit)
/woof-code/rootfs-skeleton/usr/sbin/remasterpup2#L142 (woof-CE f27b1c0 on Oct 1, 2016)

in woof-CE the code was changed in Oct 14, 2016 but I don't know when said change was merged into the master branch. I keep hering about "frequent rebacing" and I don't know how one is to keep track of it all! I think that the removal of the ID string was part of the "rationalization" branch and I think that said branch was a fairly recent topic on this forum.

Anway, I updated remasterpup2 on May 31 but for some reason these updates didn't get reinstalled into the rootfs that I was building. I will troubleshoot this later. For now I will copy the newer version of this file and remaster. Once I have sucesfully remastered I will tourbleshoot my build process.

_________________
Find me on minds and on pearltrees.
Back to top
View user's profile Send private message Visit poster's website 
s243a

Joined: 02 Sep 2014
Posts: 2199

PostPosted: Sun 21 Jul 2019, 02:06    Post subject:  

It occured to me that since I can't find a pet for cdrtools I can get the files by copying them from dpup stretch. Here is the list of files:

Code:

/etc/default/cdrecord
/etc/default/rscsi
/usr/bin/cdda2mp3
/usr/bin/cdda2ogg
/usr/bin/cdda2wav
/usr/bin/cdrecord
/usr/bin/devdump
/usr/bin/genisoimage
/usr/bin/isodebug
/usr/bin/isodump
/usr/bin/isoinfo
/usr/bin/isovfy
/usr/bin/mkhybrid

/usr/bin/mkisofs
Code:

/usr/bin/readcd
/usr/bin/readom
/usr/bin/scgcheck
/usr/bin/scgskeleton
/usr/bin/wodim
/usr/lib/siconv/cp10000
/usr/lib/siconv/cp10006
/usr/lib/siconv/cp10007
/usr/lib/siconv/cp10029
/usr/lib/siconv/cp10079
/usr/lib/siconv/cp10081
/usr/lib/siconv/cp1250
/usr/lib/siconv/cp1251
/usr/lib/siconv/cp1252
/usr/lib/siconv/cp1253
/usr/lib/siconv/cp1254
/usr/lib/siconv/cp1255
/usr/lib/siconv/cp1256
/usr/lib/siconv/cp1257
/usr/lib/siconv/cp1258
/usr/lib/siconv/cp437
/usr/lib/siconv/cp737
/usr/lib/siconv/cp775
/usr/lib/siconv/cp850
/usr/lib/siconv/cp852
/usr/lib/siconv/cp855
/usr/lib/siconv/cp857
/usr/lib/siconv/cp860
/usr/lib/siconv/cp861
/usr/lib/siconv/cp862
/usr/lib/siconv/cp863
/usr/lib/siconv/cp864
/usr/lib/siconv/cp865
/usr/lib/siconv/cp866
/usr/lib/siconv/cp869
/usr/lib/siconv/cp874
/usr/lib/siconv/iso8859-1
/usr/lib/siconv/iso8859-10
/usr/lib/siconv/iso8859-11
/usr/lib/siconv/iso8859-13
/usr/lib/siconv/iso8859-14
/usr/lib/siconv/iso8859-15
/usr/lib/siconv/iso8859-16
/usr/lib/siconv/iso8859-2
/usr/lib/siconv/iso8859-3
/usr/lib/siconv/iso8859-4
/usr/lib/siconv/iso8859-5
/usr/lib/siconv/iso8859-6
/usr/lib/siconv/iso8859-7
/usr/lib/siconv/iso8859-8
/usr/lib/siconv/iso8859-9
/usr/lib/siconv/koi8-r
/usr/lib/siconv/koi8-u
/usr/sbin/rscsi

_________________
Find me on minds and on pearltrees.
Back to top
View user's profile Send private message Visit poster's website 
s243a

Joined: 02 Sep 2014
Posts: 2199

PostPosted: Mon 22 Jul 2019, 10:28    Post subject:  

Here is my first remaster attempt in tiny_puduan:
tiny_puduan_ascii-PreA11-Remaster_1-s243a.iso (267MB)

The only thing that I tested so far is the firefox-ESR browser on a hard drive installation of tiny_puduan.

Some comments
- This install comes with the firefox-ESR browser because I haven't created a script yet to trim (or modularlize e.g. ADRV) it after the remaster
- If you are running in pmedia=usb mode then there will be a script called after snap merge puppy called /usr/bin/fix_initrd. This script will recreate the pup_ro1 link if it is broken. in other modes I don't think this script does anything yet.
- busybox is now a wrapper script that will call one of two multi-call binaries (either busybox.suid or busybox.nosuid). It does this by using the symlinks in the folder /bin/bb_utils
- many changes were made to the script /usr/sbin/pkg these changes were mainly to use variables instead of explcit paths so as to allow better instegration with mistfire's PPMv3
- added missing dependencies for the remaster script to work.
- used recent remaster script from master branch of woof-CE

_________________
Find me on minds and on pearltrees.
Back to top
View user's profile Send private message Visit poster's website 
s243a

Joined: 02 Sep 2014
Posts: 2199

PostPosted: Sun 28 Jul 2019, 02:11    Post subject:  

I'm calling this 11.1 because there are easy improvments that I haven't made yet:

tiny_puduan_ascii-PreAlpha11.1.iso

Testing has been limited to installing firefox-esr and testing pmount. The remaster script should work now but I haven't tested it yet. The above busybox wrapper improments are also included.

To install firefox-esr first update the repo db and then install with the following commands:

Code:

pkg --get libjsoncpp1
pkg --get libvpx4
pkg --get firefox-esr


Alternatively you can use JRB's portable browser installer which is available via the menus. Note that in pmedia=usbflash mode you'll get better perofmrance if the browser is installed in the save file/folder but if it is installed on a hard drive (or usb 3.0) then the ram savings of installing ouside of the save area might justfy the io cost of not running in ram.

DIsclaimer, there is a possible segmentation fault issue in the script:
/usr/local/petget/0setup

but this script seems to suceed in updating the repo databases. Another way to update the repo databases is with the command:
Code:

pkg --repo-update


This latter command uses 0setup if the repo is added in the puppy way but uses it's own scripts if the repo is added the debian way. Refer to the pkg wiki for more information:

https://gitlab.com/sc0ttj/Pkg/wikis/home

Last edited by s243a on Sun 28 Jul 2019, 02:19; edited 3 times in total
Back to top
View user's profile Send private message Visit poster's website 
darry19662018

Joined: 31 Mar 2018
Posts: 651
Location: Rakaia

PostPosted: Sun 28 Jul 2019, 02:13    Post subject:  

https://www.dropbox.com/s/aqa556rh8ye1y8b/tiny_puduan_ascii-PreAlpha11.1.iso?dl=0]tiny_puduan_ascii-PreAlpha11.1.iso
_________________
Puppy Linux Wiki: http://wikka.puppylinux.com/HomePage

https://freemedia.neocities.org/
Back to top
View user's profile Send private message Visit poster's website 
s243a

Joined: 02 Sep 2014
Posts: 2199

PostPosted: Tue 30 Jul 2019, 00:35    Post subject:  

s243a wrote:
darry19662018 wrote:
Well this Pup is quite a journey.


It's quite preliminary but the bugs posted in this thread thus far will help alot. Smile

Quote:
Got .pet installing working by finding a missing link to .petget in /usr/sbin which links to /usr/local/petget

Alternatively, one could create a script that calls "pkg -i". Thanks for noticing this Smile. What I think I will do is create a script that calls "pkg -i" by default but if not installed will try some fallbacks like petget.


Here's a first draft of the script /usr/sbin/petget:

Code:

#!/bin/sh
PKG_PATH="`which pkg`"
if [ ! -z "$PKG_PATH"]; then
  "$PKG_PATH" -i "$@"
else
  CUR_DIR=dirname "$(readlink -f "$0")" #https://stackoverflow.com/questions/59895/get-the-source-directory-of-a-bash-script-from-within-the-script-itself
  cd "$CUR_DIR"
  PETGET_PATH="../local/petget/petget" #See if a relative path is possible (useful in prefixed systems)
  [ ! -x "$(readlink -f "$PETGET_PATH")" ] && PETGET_PATH="/usr/local/petget/petget" #otherwise use absolute paths
  "$PETGET_PATH" "$@"
fi


I'll test it now.

_________________
Find me on minds and on pearltrees.
Back to top
View user's profile Send private message Visit poster's website 
Display posts from previous:   Sort by:   
Page 3 of 6 [82 Posts]   Goto page: Previous 1, 2, 3, 4, 5, 6 Next
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » Advanced Topics » Cutting edge
Jump to:  

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.1509s ][ Queries: 12 (0.0116s) ][ GZIP on ]