From: "Canek Peláez Valdés" <caneko@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] bindmount or symlink?
Date: Mon, 12 Mar 2012 23:45:48 -0600 [thread overview]
Message-ID: <CADPrc81C3LS1TbHt01-aVkUXdL-2JuWXhBH2NwtMeK7kTjmXbw@mail.gmail.com> (raw)
In-Reply-To: <CAA2qdGXxxur_3GB1ynTYLgnACgxASDKLLAOyStuzS4LQh6YX=A@mail.gmail.com>
On Mon, Mar 12, 2012 at 11:39 PM, Pandu Poluan <pandu@poluan.info> wrote:
> On Tue, Mar 13, 2012 at 12:11, Canek Peláez Valdés <caneko@gmail.com> wrote:
>> On Mon, Mar 12, 2012 at 11:04 PM, Pandu Poluan <pandu@poluan.info> wrote:
>>> I am seriously thinking of splitting the storage of directories under /usr,
>>> e.g., /usr/portage and /usr/source actually living somewhere else, on
>>> different partition and different filesystem. Let's say something mounted on
>>> /mnt/Persistent.
>>>
>>> My question: should I use bindmount or symlinks to do that? What's the
>>> drawbacks/benefits for either?
>>
>> I'm sorry, I don't understand. What's the problem of having the
>> following in /etc/fstab?
>>
>> LABEL=Portage /usr/portage ext4 noatime,auto 0 2
>> LABEL=Source /usr/source ext4 noatime,auto 0 2
>>
>> (Replace LABEL=Portage with /dev/sda7, if you want to.)
>>
>> Why do you need to bindmount or link the directories when you can
>> mount them wherever you want?
>>
>
> Because I am avoiding "single partition per directory". And a slight
> mistake in my original email, it's not just /usr but also /var (and
> other root-based directories that will not interfere with boot-up /
> operations)
>
> Let me give an example:
>
> Let's say I have /dev/sdc and /dev/sdd, both having single partition
> each (/dev/sdc1 and /dev/sdd1).
>
> /dev/sdc1 will be formatted reiserfs mounted into /mnt/Persistent1
>
> /dev/sdd1 will be formatted ext4 mounted into /mnt/Persistent2
>
> Directories not really necessary for daily operations, such as
> /usr/src, /usr/portage, /var/db/pkg, and so on and so forth, will each
> be a subdir under either /mnt/Persistent1 or /mnt/Persistent2
> according to each directory's nature.
>
> Let's take the example of /usr/src ... I can either make /usr/src a
> symlink to /mnt/Persistent1/src, or bindmount /mnt/Persistent1/src to
> /usr/src
All of that sounds incredible complicated. Interesting choice of
partition handling.
> What will be the benefits/drawbacks for bindmount vs symlink?
In my experience, and if you are not dealing with NFS, no respectable
program cares about a dir being a symlink, so I would use symlinks
(they are easier to handle).
Regards.
--
Canek Peláez Valdés
Posgrado en Ciencia e Ingeniería de la Computación
Universidad Nacional Autónoma de México
next prev parent reply other threads:[~2012-03-13 5:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-13 5:04 [gentoo-user] bindmount or symlink? Pandu Poluan
2012-03-13 5:11 ` Canek Peláez Valdés
2012-03-13 5:39 ` Pandu Poluan
2012-03-13 5:45 ` Canek Peláez Valdés [this message]
2012-03-13 6:59 ` Alan McKinnon
2012-03-13 8:05 ` Pandu Poluan
2012-03-13 8:15 ` Canek Peláez Valdés
2012-03-13 8:52 ` Philipp Riegger
2012-03-13 9:00 ` Pandu Poluan
2012-03-13 9:12 ` Canek Peláez Valdés
2012-03-13 10:35 ` Nilesh Govindrajan
2012-03-13 11:38 ` Alan McKinnon
2012-03-13 10:58 ` Alan McKinnon
2012-03-13 18:06 ` Walter Dnes
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=CADPrc81C3LS1TbHt01-aVkUXdL-2JuWXhBH2NwtMeK7kTjmXbw@mail.gmail.com \
--to=caneko@gmail.com \
--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