I am trying to upgrade the tar version on my system.
Below is the current version.
# tar --version
tar (GNU tar) 1.17
If we execute tar --help
Handling of file attributes:
--acls Save the ACLs to the archive
--atime-preserve don't change access times on dumped files
We can see --acls option available.
I downloaded 1.25 tar version, compiled and now I see --acl option is not available in the latest tar version.
Am I missing something ? or That option is replaced with some other option ?
The solution to your problem is that you are using -- with your acl(option). Don't do that, you have to use a single dash(-).
So, the option would be tar -acl archive.tar!
This will help you for sure.
Related
I am seeking to use Presage and have been following the instructions in the Read Me file, found at https://sourceforge.net/p/presage/presage/ci/master/tree/
First, I installed Presage following the setup file under Downloads. Then, as a Windows user, I downloaded the Cygwin environment. When I go to unpack Presage, using the code given in the Presage Read Me guide, in the Cygwin command prompt, I receive this output:
tar (child): presage-*tar.bz2: Cannot open: No such file or directory
tar (child): Error is not recoverable: exiting now
tar: Child returned status 2
tar: Error is not recoverable: exiting now
Running the most recent installer for Presage created a new document folder called Presage within my user folder. I tried copying both the file itself, and then the entire folder, to Downloads, but this did not resolve anything. Similarly, I tried moving Cygwin to Downloads, but this did not help. I then conducted a search for presage.tar.gz, which is what I want to untar. The Presage installer provided files presage_theme.tar.gz and presage_files.tar.gz, but no presage.tar.gz.
I then tried the second most recent release of Presage, but this did not fix the problem, either.
What is happening?
Thanks for your help!
In your Download directory, where Presage.tar.gz is located, open your Cygwin terminal, then follow the instructions as also provided in Presage:
NOTE: This will extract the file to the current (Download) directory.
STEP 1: Unpacking Presage
On Linux/Unix, uncompress and untar the distribution with:
tar zxvf presage_theme.tar.gz && tar zxvf presage_files.tar.gz
or
tar -xzvf presage_theme.tar.gz && tar -xzvf presage_files.tar.gz
(This should uncompress 2 different directories for you presage_theme and presage_files)
STEP 2: Configuring Presage
Configuring Presage to different platforms, environments and
operating systems is simply a matter of running
./configure
in the top-level directory of the distribution. This will configure
Presage for your system. Should you require additional options, try
./configure --help
to see the available options.
STEP 3: Compiling Presage
Kick off the compilation with
make
This will build the Presage system, libraries and available
plugins.
STEP 4: Installing Presage
Install Presage and its support libraries and plugins by typing
make install
For posterity: The problem was that my version of Windows was not compatible with even the most recent version of Presage. There is a patch fix available for it online.
I have a virtual machine which has Spark 1.3 on it but I want to upgrade it to Spark 1.5 primarily due certain supported functionalities which were not in 1.3. Is it possible I can upgrade the Spark version from 1.3 to 1.5 and if yes then how can I do that?
Pre-built Spark distributions, like the one I believe you are using based on another question of yours, are rather straightforward to "upgrade", since Spark is not actually "installed". Actually, all you have to do is:
Download the appropriate Spark distro (pre-built for Hadoop 2.6 and later, in your case)
Unzip the tar file in the appropriate directory (i.e.where folder spark-1.3.1-bin-hadoop2.6 already is)
Update your SPARK_HOME (and possibly some other environment variables depending on your setup) accordingly
Here is what I just did myself, to go from 1.3.1 to 1.5.2, in a setting similar to yours (vagrant VM running Ubuntu):
1) Download the tar file in the appropriate directory
vagrant#sparkvm2:~$ cd $SPARK_HOME
vagrant#sparkvm2:/usr/local/bin/spark-1.3.1-bin-hadoop2.6$ cd ..
vagrant#sparkvm2:/usr/local/bin$ ls
ipcluster ipcontroller2 iptest ipython2 spark-1.3.1-bin-hadoop2.6
ipcluster2 ipengine iptest2 jsonschema
ipcontroller ipengine2 ipython pygmentize
vagrant#sparkvm2:/usr/local/bin$ sudo wget http://apache.tsl.gr/spark/spark-1.5.2/spark-1.5.2-bin-hadoop2.6.tgz
[...]
vagrant#sparkvm2:/usr/local/bin$ ls
ipcluster ipcontroller2 iptest ipython2 spark-1.3.1-bin-hadoop2.6
ipcluster2 ipengine iptest2 jsonschema spark-1.5.2-bin-hadoop2.6.tgz
ipcontroller ipengine2 ipython pygmentize
Notice that the exact mirror you should use with wget will be probably different than mine, depending on your location; you will get this by clicking the "Download Spark" link in the download page, after you have selected the package type to download.
2) Unpack the tgz file with
vagrant#sparkvm2:/usr/local/bin$ sudo tar -xzf spark-1.*.tgz
vagrant#sparkvm2:/usr/local/bin$ ls
ipcluster ipcontroller2 iptest ipython2 spark-1.3.1-bin-hadoop2.6
ipcluster2 ipengine iptest2 jsonschema spark-1.5.2-bin-hadoop2.6
ipcontroller ipengine2 ipython pygmentize spark-1.5.2-bin-hadoop2.6.tgz
You can see that now you have a new folder, spark-1.5.2-bin-hadoop2.6.
3) Update accordingly SPARK_HOME (and possibly other environment variables you are using) to point to this new directory instead of the previous one.
And you should be done, after restarting your machine.
Notice that:
You don't need to remove the previous Spark distribution, as long as all the relevant environment variables point to the new one. That way, you may even quickly move "back-and-forth" between the old and new version, in case you want to test things (i.e. you just have to change the relevant environment variables).
sudo was necessary in my case; it may be unnecessary for you depending on your settings.
After ensuring that everything works fine, it's good idea to delete the downloaded tgz file.
You can use the exact same procedure to upgrade to future versions of Spark, as they come out (rather fast). If you do this, either make sure that previous tgz files have been deleted, or modify the tar command above to point to a specific file (i.e. no * wildcards as above).
Set your SPARK_HOME to /opt/spark
Download the latest pre-built binary i.e. spark-2.2.1-bin-hadoop2.7.tgz - can use wget
Create the symlink to the latest download - ln -s /opt/spark-2.2.1 /opt/spark
Edit files in $SPARK_HOME/conf accordingly
For every new version you download just create the symlink to it (step 3)
ln -s /opt/spark-x.x.x /opt/spark
I am neophyte on Mac especially on terminal. Though I've read lots of materials, I am still very confused and do not know what I should do.
I need to use aspell on MAC. I followed a tutorial (http://wiki.lyx.org/Mac/MacSpelling) to install it and I've installed Xcode and gcc. In one step, it required me to "type ./configure, followed by ". I did it, but terminal showed:
-bash: ./configure: No such file or directory
This webpage (http://ubuntuforums.org/showthread.php?t=1849525) showed the configure in under "/usr/local/src/configure" but when I cd to this directory I found I do not have the /src/ folder.
/usr/local$ ls
CODEOFCONDUCT.md README.md include/ opt/
CONTRIBUTING.md SUPPORTERS.md info/ share/
Cellar/ bin/ lib/
LICENSE.txt etc/ libexec/
Library/ git/ man/
What show I do? How can I use the ./configure?
Thank you so much.
You likely don't have the command line development tools installed.
Try
xcode-select --install
It also looks like you have homebrew installed. I believe that there is a formula for aspell, so you can try
brew install aspell
The aspell-0.60.6.1 tarball does have a configure script inside its own source tree (so it is located at aspell-0.60.6.1/configure). So you should start with something like (to do outside of /usr/local/, for example in your $HOME/freesoftsource/ directory if you have one, or maybe even simply in your $HOME if you dare).
wget ftp://ftp.gnu.org/gnu/aspell/aspell-0.60.6.1.tar.gz
tar xzvf aspell-0.60.6.1.tar.gz
cd aspell-0.60.6.1
./configure
You may want to add some options to the ./configure above.
You should read aspell installing instructions
N.B. As with most GNU software using configure, the location of the source tree (extracted from the source tar archive as above) does not matter much.
I hope to pack the nodejs(includes its installed module via npm) and javascript code to one execute file for different plateform(windows, osx, linux).
Is it possible or any solution?
Your comment welcome
From my understanding, you can't really create an executable file for multiplatforms. Each platform has it's own packaging format to make it binary executable. What you can do is to create a x.tar.gz file and expand it to your target platform. I myself haven't done it but theoretically it's possible. Here is an example (assuming you're using GNU tar for all your platforms):
To pack it, do:
tar cvzf nodeproject.tar.gz nodeproject
To expand, do
tar xvzf nodeproject.tar.gz
I've installed a newer version of svn on my system in ~my/home/bin and put the path to it.
So now from command line a newer version of svn is used instead of the old one, located in /usr/bin/.
However svnant keeps using an older svn in /usr/bin.
How can I tell svnant to use a newer svn?
As seen there svnant does not always uses the executable : http://subclipse.tigris.org/svnClientAdapter.html
1st-JavaHL native (JNI) subversion library (http://svn.apache.org/repos/asf/subversion/trunk/subversion/bindings/javahl/)
2nd-JavaSVN (pure Java) subversion API implementation (http://tmate.org/svn/)
3rd-svn(.exe) command line client wrapper
For the first too you would have to upgrade the jar.
If it really uses the executable you should try putting your executable in the path first before the other svn exe or linking it to /usr/bin
ln -s /home/yourself/bin/svn /usr/bin/svn
You may want to do something like:
mv /usr/bin/svn /usr/bin/svn_old
ln -s ~/your/home/bin/svn /usr/bin/svn
So you have a copy of the old one if you need it, while linking the currently used binary to your new version.
Add your new svn path to java.library.path