All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Chad C. Walstrom" <chewie@wookimus.net>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Mandrake 8.1 and LVM
Date: Fri Nov 30 14:18:01 2001	[thread overview]
Message-ID: <20011130142015.F23836@wookimus.net> (raw)
In-Reply-To: <NBBBKLKHMJHIJLHOGAOJOEDKJCAA.steve.wray@the.net.nz>

[-- Attachment #1: Type: text/plain, Size: 1782 bytes --]

On Fri, Nov 30, 2001 at 09:41:21PM +1300, Steve Wray wrote:
> > Reason #1:  Mount /usr as read-only.  There is only one reason why you
> 
> ONLY if you also have /usr/share (for one, there may be others) on writeable
> partitions!!!

Why would you want/need to have /usr/share writeable?  FHS 2.2 states:

        4.11  /usr/share : Architecture-independent data

        4.11.1  Purpose

        The /usr/share hierarchy is for all read-only architecture
        independent data files. [25]

        This hierarchy is intended to be shareable among all architecture
        platforms of a given OS; thus, for example, a site with i386,
        Alpha, and PPC platforms might maintain a single /usr/share
        directory that is centrally-mounted.  Note, however, that
        /usr/share is generally not intended to be shared by different
        OSes or by different releases of the same OS.

        Any program or package which contains or requires data that
        doesn't need to be modified should store that data in /usr/share
        (or /usr/local/share, if installed locally).  It is recommended
        that a subdirectory be used in /usr/share for this purpose.

        Game data stored in /usr/share/games must be purely static data.
        Any modifiable files, such as score files, game play logs, and so
        forth, should be placed in /var/games.

        ...

        Footnote: 
        25.  Much of this data originally lived in /usr  (man,  doc)  or
        /usr/lib (dict, terminfo, zoneinfo).

-- 
Chad Walstrom <chewie@wookimus.net>                 | a.k.a. ^chewie
http://www.wookimus.net/                            | s.k.a. gunnarr
Get my public key, ICQ#, etc. $(mailx -s 'get info' chewie@wookimus.net)

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

  reply	other threads:[~2001-11-30 14:18 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-29 15:53 [linux-lvm] Mandrake 8.1 and LVM Sarwer Zafiruddin
2001-11-29 16:01 ` mitch
2001-11-29 16:06   ` Steve Wray
2001-11-29 18:07   ` Theo Van Dinter
2001-11-30  1:59     ` Chad C. Walstrom
2001-11-30  2:40       ` Steve Wray
2001-11-30 14:18         ` Chad C. Walstrom [this message]
2001-11-30 15:53           ` mitch
2001-11-30 19:31             ` Chad C. Walstrom
2001-12-01  0:15               ` mitch
2001-11-30 16:00           ` Petro
2001-11-30 19:27             ` Chad C. Walstrom
2001-11-30 16:04           ` Steve Wray
2001-11-30 19:24             ` Chad C. Walstrom
2001-11-30 10:47       ` Theo Van Dinter
2001-11-30 11:37         ` Luca Berra
2001-11-30 12:02           ` svetljo
2001-12-02  8:24             ` Luca Berra
2001-12-01 10:30     ` Wolfgang Weisselberg
  -- strict thread matches above, loose matches on Subject: below --
2001-12-02  8:55 Luca Berra
2001-12-02  9:22 ` galia
     [not found] <Pine.LNX.4.21.0111291810070.435-100000@sol.rune.org>
2001-11-29 17:12 ` Sarwer Zafiruddin
     [not found] <Pine.LNX.4.21.0111291704150.435-100000@sol.rune.org>
2001-11-29 16:14 ` Sarwer Zafiruddin
2001-11-29 16:44   ` Steve Wray
2001-11-30  2:35     ` Luca Berra
2001-12-01 10:17       ` Brian J. Murrell
2001-11-29  7:58 Sarwer Zafiruddin
2001-11-29 11:15 ` Luca Berra
2001-11-29 15:04   ` Steve Wray
2001-11-29 15:16     ` Lars Kellogg-Stedman
2001-11-29 15:42       ` mitch
2001-11-29 15:56         ` Steve Wray
2001-11-29 19:09         ` Lars Kellogg-Stedman
2001-12-03 20:12         ` Mark van Walraven
2001-11-30  2:28     ` Luca Berra
2001-12-01 10:58       ` Brian J. Murrell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20011130142015.F23836@wookimus.net \
    --to=chewie@wookimus.net \
    --cc=linux-lvm@sistina.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.