public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Pacho Ramos <pacho@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] About suggesting to create a separate partition for portage tree in handbook
Date: Fri, 30 Mar 2012 10:00:02 +0200	[thread overview]
Message-ID: <1333094402.1407.7.camel@belkin4> (raw)
In-Reply-To: <4F720CAE.7070306@gentoo.org>

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

El mar, 27-03-2012 a las 14:53 -0400, Ian Stakenvicius escribió:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
> 
> On 27/03/12 02:47 PM, Rich Freeman wrote:
> > On Tue, Mar 27, 2012 at 2:34 PM, Alexandre Rostovtsev
> > <tetromino@gentoo.org>
> >> The partitioning scheme is something that the user needs to
> >> decide on *before* getting Gentoo up and running. After the user
> >> had finished installing the operating system, it's too late to
> >> inform him about the advantages of a separate /usr/portage.
> > 
> > Yes and no (if you have free space, you could easily move
> > /usr/portage - some other changes are harder).
> > 
> > However, you could extend this line of argument to raid, lvm, and
> > even stuff like the use of systemd or an alternative package
> > manager.  All of those things are much easier to implement if you
> > just start out with them.
> > 
> > I'm all for creating a wiki to talk about some alternative
> > options. Perhaps even link to it at the start of the handbook in
> > the intro (if you're not in a rush and want to read about more
> > advanced configurations, check out ...).
> > 
> > However, I tend to agree that the handbook should be a 
> > nearly-foolproof no-frills Gentoo installation.
> > 
> 
> 
> You know, we have "Code Listing 2.1: Filesystem Example" in Section 4,
> we could always adjust that to have a /usr/portage partition in it
> (take a bit of space away from /home, or something)
> 
> It doesn't recommend/require anything, but when users see it they'll
> think about it.

This would be a good option, but I would anyway add a note warning
people about the cons of having portage tree in a normal partition with
the rest of the system, otherwise people could simply ignore that code
listing because they could thing it's there simply on a try to get all
system "splitted" ;) (for example, I don't usually have a separate
partition for all what is listed there, only /, /home and /usr/portage)


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  parent reply	other threads:[~2012-03-30  8:02 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20337.28987.736877.961717@a1i15.kph.uni-mainz.de>
     [not found] ` <20120327154239.GA17394@gentoo.org>
2012-03-27 17:49   ` [gentoo-dev] About suggesting to create a separate partition for portage tree in handbook Pacho Ramos
2012-03-27 18:01     ` Sven Vermeulen
2012-03-27 18:21       ` Aaron W. Swenson
2012-03-27 18:34       ` Alexandre Rostovtsev
2012-03-27 18:47         ` Rich Freeman
2012-03-27 18:53           ` Ian Stakenvicius
2012-03-27 19:02             ` vivo75
2012-03-27 19:04             ` Aaron W. Swenson
2012-03-27 19:13               ` Ian Stakenvicius
2012-03-27 19:31                 ` Aaron W. Swenson
2012-03-27 19:16             ` Kent Fredric
2012-03-30  8:00             ` Pacho Ramos [this message]
2012-03-27 19:15           ` Sven Vermeulen
2012-03-27 19:20             ` Kent Fredric
2012-03-27 19:29               ` William Hubbs
2012-03-27 19:40                 ` Sven Vermeulen
2012-03-27 19:57         ` Richard Yao
2012-03-27 20:15           ` Kent Fredric
2012-03-27 20:05         ` Alec Moskvin
2012-03-30  8:06           ` Pacho Ramos
2012-03-31  8:44             ` Sven Vermeulen
2012-03-31  9:35               ` Brian Harring
2012-03-31 13:36                 ` Pacho Ramos
2012-03-31 13:34               ` Pacho Ramos
2012-03-31 17:42                 ` Zac Medico
2012-03-31 23:25                   ` Walter Dnes
2012-04-01  0:33                     ` Zac Medico
2013-07-21 11:42                       ` Pacho Ramos
2013-07-21 11:57                         ` Michał Górny
2013-07-21 12:06                           ` Pacho Ramos
2013-07-21 12:15                             ` Michał Górny
2013-07-21 18:00                           ` Zac Medico
2013-07-21 18:55                             ` Michał Górny
2013-07-21 14:26                         ` Michael Weber
2013-07-21 14:46                           ` justin
2013-07-21 17:01                             ` Pacho Ramos
2012-04-01  8:06                     ` Pacho Ramos
2012-04-01 15:28                     ` [gentoo-dev] " Steven J Long
2012-04-02  4:41                       ` Walter Dnes
2012-03-30  7:57         ` [gentoo-dev] " Pacho Ramos
2012-03-30  7:57       ` Pacho Ramos
2012-03-27 18:16     ` Ciaran McCreesh
2012-03-28  7:16       ` Brian Dolbec
2012-03-28 10:35         ` Rich Freeman
2012-03-28 14:53         ` Kent Fredric
2012-03-28 14:59         ` Richard Yao
2012-03-28 15:27           ` Matt Turner
2012-03-28 15:37           ` Rich Freeman
2012-03-28 18:56             ` Brian Dolbec
2012-03-28 17:41         ` Joshua Kinard
2012-03-28 22:27     ` Joshua Saddler
2012-03-29  0:35       ` Dale
2012-03-29  2:21         ` [gentoo-dev] " Duncan
2012-03-29  3:11           ` Dale

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=1333094402.1407.7.camel@belkin4 \
    --to=pacho@gentoo.org \
    --cc=gentoo-dev@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