SCIENTIFIC-LINUX-USERS Archives

November 2015

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Nico Kadel-Garcia <[log in to unmask]>
Reply To:
Nico Kadel-Garcia <[log in to unmask]>
Date:
Sat, 14 Nov 2015 09:32:56 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (28 lines)
On Sat, Nov 14, 2015 at 1:56 AM, Benjamin Lefoul
<[log in to unmask]> wrote:
>>Be clear that replacing /usr/local with a symlink in the form you describe is *not* compliant with the FSH.
>
> Actually it is, in both FHS version 2.3 and version 3.0.
>
> http://refspecs.linuxfoundation.org/FHS_3.0/fhs/ch04s02.html
>
> The following directories, or symbolic links to directories, are required in /usr.
> Directory       Description
> bin     Most user commands
> lib     Libraries
> local   Local hierarchy (empty after main installation)
> sbin    Non-vital system binaries
> share   Architecture-independent data

Wow, thank you, good point, thanks for the correction, I was looking
further down the documentation at the subdirectories.

I'd written:
> A symlink form /usr/local to a read-only AFS space is *not* the same
> thing as symlinks for /usr/local/bin, /usr/local/etc,
> /usr/local/share, /usr/local/lib, etc. Be clear that replacing
> /usr/local with a symlink in the form you describe is *not* compliant
> with the FSH. Not that it's not useful in your environment, but just
> so you appreciate that you may have issues with core packages such as
> the "filesystem" package.

ATOM RSS1 RSS2