Sponsored Content
Top Forums Shell Programming and Scripting Using links with wildcards in bash. Post 302351953 by cop02ia on Thursday 10th of September 2009 04:29:57 AM
Old 09-10-2009
Unfortunately no messages.
Probably because the wildcard (*) symbol was used, the softlinks were not created silently (no errors).
I found out from a different post (which was posted sometime ago) that it probably was caused by ambiguity.
https://www.unix.com/shell-programmin...-links-ln.html
so I'm wondering if someone could elaborate on this matter.


Sorry, my bad.
There was a wrong link created...
In my directory, instead of creating links to all the files, it created a file called:
"*" linking to "../../FtE/lib/*" OR "*.lib" linking to "../../FtE/lib/*.lib"

Here's how it looks with ls -lh:

lrwxrwxrwx 1 cad cad 24 Sep 11 2009 *.lib -> ../../FtE/lib/*.lib

Last edited by cop02ia; 09-10-2009 at 09:14 PM.. Reason: additional info. / correction
 

8 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Wildcards in VI

I'm trying to delete lines from a large text file using VI. Every line that I am wanting to delete start with 'S' - all others do not. (A list of users) I've tried using * but doesn't seem to like it...any ideas... Doesn't have to be VI - but I'm better with VI than sed/awk. (8 Replies)
Discussion started by: peter.herlihy
8 Replies

2. UNIX for Dummies Questions & Answers

wildcards

when writing a shell script (bourne) and using a unix command like 'ls' is there anything special you need to do to use a wildcard (like *)? (3 Replies)
Discussion started by: benu302000
3 Replies

3. UNIX for Dummies Questions & Answers

ls with wildcards

ok, I'm trying to write a script file that lists files with specific elements in the name into a txt file, it looks like this ls s*.dat > file_names.txt can't figure out whats wrong with that line, any ideas? thanks in advance (10 Replies)
Discussion started by: benu302000
10 Replies

4. Shell Programming and Scripting

Symbolic Links - BASH Script

Hi all, This is my first message in this forum. I'd like to know if there is a nice way to get the complete path from a symbolic link. Example: When I do a ls -ltr I see this output. lrwxr-xr-x 1 mmmm users 66 Sep 4 09:58 LINK_SEND ->... (4 Replies)
Discussion started by: rodrimuino
4 Replies

5. UNIX for Dummies Questions & Answers

wildcards NOT

Hi All Please excuse another straightforward question. When creating a tar archive from a directory I am attempting to use wildcards to eliminate certain filetypes (otherwise the archive gets too large). So I am looking for something along these lines. tar -cf archive.tar * <minus all *.rst... (5 Replies)
Discussion started by: C3000
5 Replies

6. UNIX for Advanced & Expert Users

Wildcards

These 2 websites do a GREAT job of explaining different types of wildcards. I learned about the categories of characters which I never knew about at all. GNU/Linux Command-Line Tools Guide - Wildcards GREP (1 Reply)
Discussion started by: cokedude
1 Replies

7. Solaris

Hard Links and Soft or Sym links

When loooking at files in a directory using ls, how can I tell if I have a hard link or soft link? (11 Replies)
Discussion started by: Harleyrci
11 Replies

8. AIX

List all the soft links and hard links

Hi I'm logged in as root in an aix box Which command will list all the soft links and hard links present in the server ? (2 Replies)
Discussion started by: newtoaixos
2 Replies
lib::abs(3pm)						User Contributed Perl Documentation					     lib::abs(3pm)

NAME
lib::abs - "lib" that makes relative path absolute to caller. SYNOPSIS
Simple use like "use lib ...": use lib::abs qw(./mylibs1 ../mylibs2); use lib::abs 'mylibs'; Extended syntax (glob) use lib::abs 'modules/*/lib'; There are also may be used helper function from lib::abs (see example/ex4): use lib::abs; # ... my $path = lib::abs::path('../path/relative/to/me'); # returns absolute path DESCRIPTION
The main reason of this library is transformate relative paths to absolute at the "BEGIN" stage, and push transformed to @INC. Relative path basis is not the current working directory, but the location of file, where the statement is (caller file). When using common "lib", relative paths stays relative to curernt working directory, # For ex: # script: /opt/scripts/my.pl use lib::abs '../lib'; # We run `/opt/scripts/my.pl` having cwd /home/mons # The @INC will contain '/opt/lib'; # We run `./my.pl` having cwd /opt # The @INC will contain '/opt/lib'; # We run `../my.pl` having cwd /opt/lib # The @INC will contain '/opt/lib'; Also this module is useful when writing tests, when you want to load strictly the module from ../lib, respecting the test file. # t/00-test.t use lib::abs '../lib'; Also this is useful, when you running under "mod_perl", use something like "Apache::StatINC", and your application may change working directory. So in case of chdir "StatINC" fails to reload module if the @INC contain relative paths. RATIONALE
Q: We already have "FindBin" and "lib", why we need this module? A: There are several reasons: 1) "FindBin" could find path incorrectly under "mod_perl" 2) "FindBin" works relatively to executed binary instead of relatively to caller 3) Perl is linguistic language, and `use lib::abs "..."' semantically more clear and looks more beautiful than `use FindBin; use lib "$FindBin::Bin/../lib";' 4) "FindBin" b<will> work incorrectly, if will be called not from executed binary (see <http://github.com/Mons/lib-abs-vs-findbin> comparison for details) BUGS
None known COPYRIGHT &; LICENSE Copyright 2007-2010 Mons Anderson. This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself. AUTHOR
Mons Anderson, "<mons@cpan.org>" CONTRIBUTORS
Oleg Kostyuk, "<cub@cpan.org>" perl v5.10.1 2010-11-16 lib::abs(3pm)
All times are GMT -4. The time now is 01:33 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy