10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
I have problem
find "$@" -type l -printf "%l\n" 2>/dev/null | awk -F/ '
NF > n {deepest = $0; n=NF}
END {print "Output:", deepest}'
My script should search all arguments which are directories for longest symbolic link path but i want Output to be this way
Output:
'/xxx/xxx/xxx/link ->... (1 Reply)
Discussion started by: xpukm
1 Replies
2. UNIX for Dummies Questions & Answers
Hi, trying to understand more about symblic link, when I compiled a program called "match" in one folder ~/downloadsoftware/I want this program to be accessible like a system command by putting a symbolic link in /usr/bin/ Not by setting the $PATH method in .bashrc at this time.
What I did is:... (4 Replies)
Discussion started by: yifangt
4 Replies
3. UNIX for Dummies Questions & Answers
Hi everybody,
I read about treads realted to this issue but they did not resovle issue given below.
Please help me resolve issue given below
I have html file under /srv/www/htdocs/actual_folder
ls actual_folder/
test.html
and following link works... (0 Replies)
Discussion started by: newbielgn
0 Replies
4. Shell Programming and Scripting
Hi,
Can anyone please advise why the following is not working as I expected it to be?
Test script as below:
#!/bin/ksh
for checkdir in dir*
do
echo "Checking ${checkdir}"
if ; then
echo "... ${checkdir} is a directory"
elif Output from sample run as below:
$:... (8 Replies)
Discussion started by: newbie_01
8 Replies
5. Shell Programming and Scripting
Hi all,
Can anyone please confirm if the command below is the only way that I can get what the symbolic link is set to?
mnlxd110(oracle)/db/posd2/dba$: ls -l | grep "^l"
lrwxrwxrwx 1 oracle dba 28 Aug 9 2011 bdump -> diag/rdbms/posp1/posp1/trace
mnlxd110(oracle)/db/posd2/dba$:... (7 Replies)
Discussion started by: newbie_01
7 Replies
6. UNIX for Dummies Questions & Answers
Hi ,
i am trying to make a symbolic link for an existing directory, but i am facng some problems regarding the usage of command.
If there is no directory i can make a symbolic link, but for an existing directory i am not able to.
can anyone post me the exact usage if we already have the... (1 Reply)
Discussion started by: sahasra
1 Replies
7. Shell Programming and Scripting
Hello All,
This may be a silly question to some but I am really stuck.
Is there a way to reverse the following;
sudo rm /bin/sh
sudo ln -s /bin/bash /bin/sh
It was part of a driver compile/installation procedure by Digi for Ubuntu stating that dash isn't supported and a symbolic link... (2 Replies)
Discussion started by: LAVco
2 Replies
8. Shell Programming and Scripting
Hi,
i am trying to create sym links on sles 11 , but it seems i am doing something wrong.
oracle@tests:/u01/app/oracle/oradata/ACIS> pwd
/u01/app/oracle/oradata/ACIS
oracle@tests:/u01/app/oracle/oradata/ACIS> ln -s /db/ACIS/dbase/dbf/ /u01/app/oracle/oradata/ACIS/... (2 Replies)
Discussion started by: tonijel
2 Replies
9. UNIX for Dummies Questions & Answers
hello folks
how y'all doin
well i have some questions about symbolic link and hard link
hope some one answer me
i open terminal and join as root
and i wrote ln -s blah blah
then i wrote ls
i see red file called blah blah
but didn't understand what is this can some one explain and... (2 Replies)
Discussion started by: detective linux
2 Replies
10. UNIX for Dummies Questions & Answers
question abt symbolic link ...
i'm doing the following ...
ln -s x.sh ./scripts/y.sh
and
cat ./scripts/y.sh
it is giving following error
cat: cannot open y.sh
Any reason u an think of ?
But it is working fine when i goto scripts directory and cretae the symbolic link.
... (1 Reply)
Discussion started by: bhargav
1 Replies
GIT-INDEX-PACK(1) Git Manual GIT-INDEX-PACK(1)
NAME
git-index-pack - Build pack index file for an existing packed archive
SYNOPSIS
git index-pack [-v] [-o <index-file>] <pack-file>
git index-pack --stdin [--fix-thin] [--keep] [-v] [-o <index-file>]
[<pack-file>]
DESCRIPTION
Reads a packed archive (.pack) from the specified file, and builds a pack index file (.idx) for it. The packed archive together with the
pack index can then be placed in the objects/pack/ directory of a Git repository.
OPTIONS
-v
Be verbose about what is going on, including progress status.
-o <index-file>
Write the generated pack index into the specified file. Without this option the name of pack index file is constructed from the name of
packed archive file by replacing .pack with .idx (and the program fails if the name of packed archive does not end with .pack).
--stdin
When this flag is provided, the pack is read from stdin instead and a copy is then written to <pack-file>. If <pack-file> is not
specified, the pack is written to objects/pack/ directory of the current Git repository with a default name determined from the pack
content. If <pack-file> is not specified consider using --keep to prevent a race condition between this process and git repack.
--fix-thin
Fix a "thin" pack produced by git pack-objects --thin (see git-pack-objects(1) for details) by adding the excluded objects the
deltified objects are based on to the pack. This option only makes sense in conjunction with --stdin.
--keep
Before moving the index into its final destination create an empty .keep file for the associated pack file. This option is usually
necessary with --stdin to prevent a simultaneous git repack process from deleting the newly constructed pack and index before refs can
be updated to use objects contained in the pack.
--keep=<msg>
Like --keep create a .keep file before moving the index into its final destination, but rather than creating an empty file place <msg>
followed by an LF into the .keep file. The <msg> message can later be searched for within all .keep files to locate any which have
outlived their usefulness.
--index-version=<version>[,<offset>]
This is intended to be used by the test suite only. It allows to force the version for the generated pack index, and to force 64-bit
index entries on objects located above the given offset.
--strict
Die, if the pack contains broken objects or links.
--threads=<n>
Specifies the number of threads to spawn when resolving deltas. This requires that index-pack be compiled with pthreads otherwise this
option is ignored with a warning. This is meant to reduce packing time on multiprocessor machines. The required amount of memory for
the delta search window is however multiplied by the number of threads. Specifying 0 will cause Git to auto-detect the number of CPU's
and use maximum 3 threads.
NOTE
Once the index has been created, the list of object names is sorted and the SHA-1 hash of that list is printed to stdout. If --stdin was
also used then this is prefixed by either "pack ", or "keep " if a new .keep file was successfully created. This is useful to remove a
.keep file used as a lock to prevent the race with git repack mentioned above.
GIT
Part of the git(1) suite
Git 1.8.3.1 06/10/2014 GIT-INDEX-PACK(1)