public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Kevin Chadwick <ma1l1ists@yahoo.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: Should /usr be merged with /? (Was: Re: [gentoo-user] Re: Anyone switched to eudev yet?)
Date: Sun, 30 Dec 2012 14:08:48 +0000	[thread overview]
Message-ID: <20121230140848.42068bc2@kc-sys.chadwicks.me.uk> (raw)
In-Reply-To: <CAG2nJkNhbNkowvc9sYf+wBu5VBeBXBocEP=bOfg6Nsv6eRnhaA@mail.gmail.com>

On Sun, 30 Dec 2012 20:19:44 +0800
Mark David Dumlao <madumlao@gmail.com> wrote:

> > I'd certainly be happy "fixing" FHS to say that tools for mounting
> > and recovering "essential system partitions" be located in /, and
> > that these "essential system partitions" contain the tools for
> > mounting and recovering non-essential partitions.  
> 
> The beef with the comment on /home being nonessential is besides the
> point, /usr, /var, or /opt could have been some special case FUSE
> filesystem, making it still impossible to predict which files _should_
> be in /. The more relevant matter here is that plan FHS, in
> combination with FUSE, makes that difficult.

That's not best practice though is it and I completely disagree with the
rules you seem to believe the english language has too. 

It is not a difficult problem, just FUSE is not expected or intended
for that, if that changes it is easily fixed immediately by the admin
or by the packager preferably in concert with some root management body
or project. 

Many/All of these issues that have come up are actually of 0 effect, we
are not talking about preventing users from merging them as most Linux
users do because they just hit ok ok ok in ubuntus installation but
about a major degradation due to some devs whim and without I might add
proper community involvement or commentry ALLOWED. One things for sure
real problems will arise directly due to this merge if this merge
becomes standard and possibly with won't fixes used leading to
pointlessly breaking existing servers and linux becoming even more of an
unorganised mess.

On windows production machines I arrived at putting c: on it's own
smaller partition and program files on a larger partition. It meant I
could have many more c: backups and restore much more quickly too
resulting in much higher uptime and reduced loss in the cases that
registry restore wasn't good enough and system restore is crap. With
windows 7 it's not so beneficial as windows 7 is huge but still useful
as everything is getting huge on windows these days. You do get the
occasional dumb program perhaps fixable with a drive link within c:.

Windows 8 should be more reliable but I expect brings new issues in this
area due to app restrictions and where sandboxing could have been used
for security instead.


      reply	other threads:[~2012-12-30 14:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-28 17:16 Should /usr be merged with /? (Was: Re: [gentoo-user] Re: Anyone switched to eudev yet?) Mark David Dumlao
2012-12-28 17:33 ` Bruce Hill
2012-12-28 17:46   ` Mark David Dumlao
2012-12-28 17:56     ` Michael Mol
2012-12-28 18:53 ` Kevin Chadwick
2012-12-29  4:27   ` Mark David Dumlao
2012-12-29  7:00     ` Paul Colquhoun
2012-12-29 14:03       ` Kevin Chadwick
2012-12-30 12:19       ` Mark David Dumlao
2012-12-30 14:08         ` Kevin Chadwick [this message]

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=20121230140848.42068bc2@kc-sys.chadwicks.me.uk \
    --to=ma1l1ists@yahoo.co.uk \
    --cc=gentoo-user@lists.gentoo.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