Tiny Core Linux

General TC => General TC Talk => Topic started by: RedPenguin on January 18, 2011, 09:32:38 PM

Title: Backup $PATH or exectuables?
Post by: RedPenguin on January 18, 2011, 09:32:38 PM

I have installed SABnzbd to TinyCore and all works well.

I have compiled par2cmdline for TinyCore and it also works perfectly.

Now the only problem I see is, how do I keep par2, par2create, par2verify, par2repair in a place such as /usr/bin or /usr/local/bin?

I read about /opt/.filetool.lst but I am not sure it's a good idea to put in /usr/bin or /usr/local/bin, as that could have weird side effects with extensions.

What would be the best way to keep par2 in PATH so it's always there for SAB?

Title: Re: Backup $PATH or exectuables?
Post by: gerald_clark on January 18, 2011, 09:38:30 PM

You need to create extensions that can be loaded on boot.
http://wiki.tinycorelinux.com/Creating+Extensions

Title: Re: Backup $PATH or exectuables?
Post by: tinypoodle on January 18, 2011, 10:03:16 PM

Any executables in /home/tc/.local/bin are in path and will be backed up by default.

In order to have executables in other locations, symlinking them to /home/tc/.local/bin would be one approach, another one would be to have wrapper scripts in /home/tc/.local/bin which specify the path to executables.

Title: Re: Backup $PATH or exectuables?
Post by: jerramy on January 18, 2011, 10:13:13 PM

This is probably a cheesy way to do it, but you could have your bootlocal.sh script copy them to bin on bootup from somewhere in your home directory, or perhaps just have bootlocal.sh create symlinks there.

Title: Re: Backup $PATH or exectuables?
Post by: RedPenguin on January 18, 2011, 10:26:08 PM

Quote from: gerald_clark on January 18, 2011, 09:38:30 PM

You need to create extensions that can be loaded on boot.
http://wiki.tinycorelinux.com/Creating+Extensions

Thank you so much, that worked like a charm.

Title: Re: Backup $PATH or exectuables?
Post by: gerald_clark on January 18, 2011, 10:30:14 PM

Happy to be of assistance.

Title: Re: Backup $PATH or exectuables?
Post by: RedPenguin on January 19, 2011, 01:35:22 AM

Quote from: tinypoodle on January 18, 2011, 10:03:16 PM

Any executables in /home/tc/.local/bin are in path and will be backed up by default.

In order to have executables in other locations, symlinking them to /home/tc/.local/bin would be one approach, another one would be to have wrapper scripts in /home/tc/.local/bin which specify the path to executables.

I don't seem to have this .local directory, or do you just create it?

Title: Re: Backup $PATH or exectuables?
Post by: tinypoodle on January 19, 2011, 02:33:54 AM

Quote from: RedPenguin on January 19, 2011, 01:35:22 AM

Quote from: tinypoodle on January 18, 2011, 10:03:16 PM

Any executables in /home/tc/.local/bin are in path and will be backed up by default.

In order to have executables in other locations, symlinking them to /home/tc/.local/bin would be one approach, another one would be to have wrapper scripts in /home/tc/.local/bin which specify the path to executables.

I don't seem to have this .local directory, or do you just create it?

The latter   ;)

You may have to log out and in again for it to become in effect (I wouldn't know if there was a better way so profile would get re-read).

Title: Re: Backup $PATH or exectuables?
Post by: Rich on January 19, 2011, 02:48:12 AM

Hi RedPenguin
.local if you have it is a hidden directory. Open a terminal and type "ls -a" without the
quotes. This will show all files and directories. Type "mkdir .local/bin". If it does not
exist it will be created, if it does system will tell you so. Copy your executables to
.local/bin. When you shutdown they will be backed up. When you restart the .profile
will add /home/tc/.local/bin to your path when you open a terminal.