linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Karl O. Pinc" <kop@meme.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH 2/2] hid2hci: when recovering from S3 use parent devpath
Date: Tue, 11 Aug 2009 17:49:53 +0000	[thread overview]
Message-ID: <1250012993.30168.7@mofo> (raw)
In-Reply-To: <4A6E19FF.5070207@dell.com>

On 08/06/2009 08:47:10 PM, Kay Sievers wrote:
> Honestly the entire split of / and /usr, like we usually do, is just
> plain stupid in the first place. It might be ok if we would put the
> desktop stuff in /usr, but spreading random commandline tools and
> libraries around causes nothing but trouble for no good reason.

Theory says that /usr can be mounted read-only, which could
improve system security for those binaries that live there
or have other advantages regarding media used, storage sharing, etc.
http://www.pathname.com/fhs/pub/fhs-2.3.html#THEUSRHIERARCHY

The other side of the argument is that / is supposed to be
able to be kept small.
http://www.pathname.com/fhs/pub/fhs-2.3.html#THEROOTFILESYSTEM

As storage gets increasingly cheaper relative
to the rest of the hardware it seems most of the
arguments for a separate /usr get weaker, but not all.
I suppose if you have a compelling argument for re-balancing
what goes where you could convince the folks on
freestandards-fhs-discuss@lists.sourceforge.net.
(At least that's where such talk went last I paid attention.)

Regards,

Karl <kop@meme.com>
Free Software:  "You don't pay back, you pay forward."
                 -- Robert A. Heinlein


  parent reply	other threads:[~2009-08-11 17:49 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-27 21:19 [PATCH 2/2] hid2hci: when recovering from S3 use parent devpath Mario Limonciello
2009-07-27 21:35 ` Marcel Holtmann
2009-07-27 22:36 ` Mario Limonciello
2009-07-27 22:42 ` Marcel Holtmann
2009-07-28  0:04 ` Kay Sievers
2009-07-28 18:10 ` Mario Limonciello
2009-07-31 18:53 ` Kay Sievers
2009-07-31 19:35 ` Mario Limonciello
2009-08-05  7:47 ` Kay Sievers
2009-08-06 22:03 ` Mario Limonciello
2009-08-07  0:27 ` Kay Sievers
2009-08-07  0:44 ` Marcel Holtmann
2009-08-07  0:57 ` Kay Sievers
2009-08-07  1:28 ` Marco d'Itri
2009-08-07  1:47 ` Kay Sievers
2009-08-07  3:48 ` Marco d'Itri
2009-08-11 17:49 ` Karl O. Pinc [this message]
2009-08-11 22:22 ` Marcel Holtmann

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=1250012993.30168.7@mofo \
    --to=kop@meme.com \
    --cc=linux-hotplug@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).