Sponsored Content
Full Discussion: Soft link
Top Forums Shell Programming and Scripting Soft link Post 302939394 by sea on Wednesday 25th of March 2015 06:19:36 AM
Old 03-25-2015
Code:
ln -sf /path/of/origin_new /path/to/destination

Will overwrite the destination softlink with the new origin.

hth
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Differences between hard link and soft link

Hi all! I'd like to know the differences between hard links and soft links. I've already read the ln manpage, but i'm not quite sure of what i understood. Does a hard link sort of copy the file to a new name, give it the same inode number and same rights? What exactly should I do to do this:... (3 Replies)
Discussion started by: penguin-friend
3 Replies

2. UNIX for Dummies Questions & Answers

Difference between hard link and soft link in unix

Hi All, Can any one please explain me what is the difference between hard link and soft link in UNIX. Thanks in advance Raja Chokalingam. (2 Replies)
Discussion started by: RAJACHOKALINGAM
2 Replies

3. UNIX for Dummies Questions & Answers

hard/soft link question

I am curious about one thing. Lets say I have a file file-a to which new generations are created on demand by simply archiving it (ex: file-a.tar.gz) and having the new one created with the same original filename file-a. Now what I want to know is if I create a hard/soft link to file-a, what... (1 Reply)
Discussion started by: Browser_ice
1 Replies

4. UNIX for Dummies Questions & Answers

Hard Link vs SOft Link????

Hi PLease let me know the usage of Hard Link vs Soft Link i.e what is the basic difference and what happens when one file is changed or deleted in both the cases??? thanks (3 Replies)
Discussion started by: skyineyes
3 Replies

5. UNIX for Dummies Questions & Answers

Difference between hard link and soft link

Hi Experts, Please help me out to find out difference between a hard link and a soft link. I am new in unix plz help me with some example commands ( for creating such links). Regards S.Kamakshi :) (2 Replies)
Discussion started by: kamakshi s
2 Replies

6. Red Hat

Soft Link Ownership After Reboot

Hi, I have created soft links for some devices /dev/xvd*1. The owner of the soft links is oracle:dba. The problem is after reboot the ownership is changed to root:root. How can I permanently change the ownership to oracle:dba? Thanks. (2 Replies)
Discussion started by: Gbyte
2 Replies

7. Shell Programming and Scripting

soft link issue

Hi , When installing oracle software a set of directories are created under the home directories. Since the home directory is usually not big , i would like to create a soft link from the home directory to mount point with alot of free space , that way the logs will not be wriiten under the... (1 Reply)
Discussion started by: yoavbe
1 Replies

8. Shell Programming and Scripting

how to remove soft link

hi i have create a soft link using below command. ln -s <filename> <dirmane>where file name i use is t1 and dir name was t2. i deleted the dir t2 using command rm -rf to remove the soft link . however again i create a file a using the name t2 and when i just try to link t1 to t2 ... (1 Reply)
Discussion started by: scriptor
1 Replies

9. Solaris

Soft link issue

I did restore from netbackup for root file system on separate slice instead of corrupted one. After restoration I found there are number of soft link issues lie e.g libabcxyx > /mnt/usr/lib it should be libabcxyz > /usr/lib does any have solution to change symbolic link changed in... (1 Reply)
Discussion started by: nimish_mehta
1 Replies

10. UNIX for Advanced & Expert Users

A query on soft-link

Hi All, I tried creating a soft link with the file itself. It got created successfully. bash-3.2$ ls -l a lrwxrwxrwx 1 ebrigup other 1 Oct 5 19:14 a -> a bash-3.2$ Can anyone explain what is the possible use of it. I dont see any except practically wasting an inode... (2 Replies)
Discussion started by: brij123
2 Replies
icmstart.rc(7)						      icmstart resource file						    icmstart.rc(7)

NAME
icmstart.rc - The icmstart(1) resource file DESCRIPTION
The icmstart.rc file defines the initial files of a program that are installed by icmstart(1). By default icmstart.rc is found in /etc/icmake/icmstart.rc, but if a file $HOME/.icmake/icmstart.rc is found then the latter file is used by icmstart(1). $HOME/.icmake/icmstart.rc in turn is overruled by specifying a -c option when invoking icmstart(1). The default resource file contains the following specifications, preparing for the construction of a C++ program using icmbuild(1): CLASSES P main.cc P main.ih P usage.cc P version.cc P ? scanner P ? parser The icmstart.rc file may contain: o empty lines, which are ignored; o lines beginning with a hash-character (#), also ignored; o Optionally: a P (don't install with icmstart xxx library) or an L (don't install with icmstart xxx program), followed by a blank; see also icmstart(1). o Optionall: a ? (followed by a blank) following the optional P or L in which case the installation of the element must be confirmed by the user. o Source path names. Relative path names are interpreted relative to the current working directory. Environment variables are not expanded, the initial tilde character is interpreset as the user's home directory. o Source path names followed by a destination (relative to the directory initialized by icmstart(1)). A source path may be either a file or a directory. If a directory is specified then all files in and below that directory will be installed. When specifying a destination a path may be specified as well. However, the destination path is always interpreted relative to the instal- lation directory specified when calling icmstart(1). If a destination is omitted, the source is installed as specified below icmstart(1)'s destination directory. EXAMPLES
The following entries can be used in an icmstart.rc file: o source `Source' must be in the skeleton directory visited by icmstart(1) and is installed as source in the destination directory specified when calling icmstart(1). o source dest `Source' must be in the skeleton directory visited by icmstart(1) and is installed as dest in the destination directory specified when calling icmstart(1). o ~/path `~/path' is installed as ~/path in the destination directory specified when calling icmstart(1). The ~-character is expanded to the user's home directory. o ~/path dest `~/path' is installed as dest in the destination directory specified when calling icmstart(1). The ~-characteris expanded to the user's home directory. o /path `/path' is installed as ./path in the destination directory specified when calling icmstart(1). o /path dest `/path' is installed as dest in the destination directory o ? source The user must confirm the installation of source. o ? source dest The user must confirm the installation of source as dest in the destination directory specified when calling icmstart(1). o # text Interpreted as comment and ignored. The #-character must be the first character on the line. o an empty line Empty lines are skipped. FILES
The mentioned paths are sugestive only and may be installation dependent: o /usr/share/icmake/icmconf Example of an icmbuild configuration file; o /usr/share/icmake/CLASSES Example of an icmbuild CLASSES file. o /usr/share/icmake/icmstart.rc Default skeleton resource file. SEE ALSO
icmake(1), icmbuild(1), icmconf(7), icmstart(1) BUGS
None reported COPYRIGHT
This is free software, distributed under the terms of the GNU General Public License (GPL). AUTHOR
Frank B. Brokken (f.b.brokken@rug.nl). icmake.7.18.00.tar.gz 1992-2012 icmstart.rc(7)
All times are GMT -4. The time now is 09:02 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy