Linux/Unix naming conventions...

[gaf at blu.org (Jerry Feldman)]

Picky picky :-) 
I think I did mention that the file system, the kernel and the loader do 
not care, maybe except for shared libraries (shared objects).
Most shared libraries have the .so extension by convention. On Linux 
systems you will find most of these symlinked to a versioned library:
/usr/lib/libm.so -> ../../lib/libm.so.6   
This is not 100% standard on all Unix systems. HP-UX has a different 
convention.
                                      
Derek Martin wrote:
> On Thu, 23 Dec 1999, Jerry Feldman wrote:
> 
> > Secondly, the file extensions do have meaining. In the development world:
> 
> O.k. Jerry, I'm being pedantic again, but Unix doesn't care about the
> extensions of the files... it's only at the application level that they
> (can) make a difference.  Most applications don't treat, for example, a .c
> file any differently than any other.  It really is more a matter of the
> file extensions having a meaning to humans, than to the OS.
> 
> 
> -- 
> Derek D. Martin
> Senior UNIX Systems/Network Administrator
> Arris Interactive
> derek.martin at ne.arris-i.com
> 

-- 
Jerry Feldman <gaf at blu.org>
Boston Linux and Unix user group
http://www.blu.org


-
Subcription/unsubscription/info requests: send e-mail with
"subscribe", "unsubscribe", or "info" on the first line of the
message body to discuss-request at blu.org (Subject line is ignored).