From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Lennart Sorensen <lsorense@csclub.uwaterloo.ca>
Cc: Jan Kiszka <jan.kiszka@web.de>, Xenomai <xenomai@xenomai.org>
Subject: Re: [Xenomai] [Xenomai-git] Philippe Gerum: copperplate: add configuration tunable for registry moint point
Date: Fri, 2 Jan 2015 16:22:45 +0100 [thread overview]
Message-ID: <20150102152245.GG1492@daedalus> (raw)
In-Reply-To: <20150102151027.GF1492@daedalus>
On Fri, Jan 02, 2015 at 04:10:27PM +0100, Gilles Chanteperdrix wrote:
> On Fri, Jan 02, 2015 at 10:05:03AM -0500, Lennart Sorensen wrote:
> > On Fri, Jan 02, 2015 at 01:51:33PM +0100, Gilles Chanteperdrix wrote:
> > > And as I explained, the standard sucks. /mnt on the distro I use
> > > contains the following directories:
> > >
> > > cdrecorder
> > > cdrom
> > > dvd
> > > floppy
> > > hd
> > > memory
> > > tmp
> > > zip
> > >
> > > and it puts the following text in /mnt/README
> > >
> > > The purpose of the /mnt directory is to provide a place for the admin to
> > > mount block device temporarily. Any of the subdirectories of /mnt may be
> > > used, or volumes may even be mounted directly on /mnt (which is the
> > > traditional way of doing things, though /mnt/tmp is also provided for
> > > the purpose of mounting any kind of volume temporarily).
> > >
> > > See the /media directory also.
> > >
> > > IOW: it leaves the choice to the user. What Philippe does is exactly
> > > the same: let the user choose whether he want to use the non
> > > standard sotlution that does not suck and that use to be a standard
> > > practice in Linux world, or the standard solution that sucks.
> > >
> > > I thought we agreed this was a sensible solution.
> >
> > So your README file even says the traditional way is to mount on top
> > of /mnt, which again means /mnt/xenomai stops working if you do what it
> > says is traditional in the README on that system. Good reason not to
> > rely on anything in /mnt
>
> You deliberately misread the README. It says that you may mount
> under whatever directory under /mnt makes sense for you OR that if
> you want, you can use /mnt. In the first case, using /mnt/xenomai
> will not break anything, in the second case yes, it will break
> things. But as I already said, I believe not many users are using
> the second solution because it inconvenient: if you do that, you
> have only one mount point for temporary thing, so the standard
> decided for you that you only mount one temporary thing at a time. I
> do not know about you, but I sometimes need to mount more than one
> thing temporarily, which is why I have plenty directories under
> /mnt.
And from a pure technical point of view, the perturbation induced by
a temporary mount on /mnt will be well, temporary, as soon as you
unmount, you will be able to access /mnt/xenomai again. And I doubt
the application itself will notice anything, as it will have kept
the /mnt/xenomai directory opened and so will be able to keep
accessing it, even if something else is mounted on top of /mnt.
--
Gilles.
next prev parent reply other threads:[~2015-01-02 15:22 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.787.1420134217.6101.xenomai-git@xenomai.org>
2015-01-02 10:28 ` [Xenomai] [Xenomai-git] Philippe Gerum: copperplate: add configuration tunable for registry moint point Jan Kiszka
2015-01-02 10:58 ` Philippe Gerum
2015-01-02 11:11 ` Jan Kiszka
2015-01-02 12:51 ` Gilles Chanteperdrix
2015-01-02 13:05 ` Jan Kiszka
2015-01-02 13:41 ` Gilles Chanteperdrix
2015-01-02 15:05 ` Lennart Sorensen
2015-01-02 15:10 ` Gilles Chanteperdrix
2015-01-02 15:22 ` Gilles Chanteperdrix [this message]
2015-01-02 15:47 ` Lennart Sorensen
2015-01-02 18:06 ` Gilles Chanteperdrix
2015-01-02 12:56 ` Gilles Chanteperdrix
2015-01-02 13:06 ` Jan Kiszka
2015-01-02 13:29 ` Philippe Gerum
2015-01-02 13:24 ` Jan Kiszka
2015-01-02 14:02 ` Philippe Gerum
2015-01-02 13:56 ` Jan Kiszka
2015-01-02 14:16 ` Gilles Chanteperdrix
2015-01-02 15:06 ` Gilles Chanteperdrix
2015-01-02 15:59 ` Jan Kiszka
2015-01-02 18:03 ` Gilles Chanteperdrix
2015-01-02 18:07 ` Philippe Gerum
2015-01-02 18:09 ` Jan Kiszka
2015-01-02 19:20 ` Philippe Gerum
2015-01-02 19:15 ` Jan Kiszka
2015-01-02 19:31 ` Philippe Gerum
2015-01-02 19:28 ` Jan Kiszka
2015-01-02 19:55 ` Philippe Gerum
2015-01-02 19:49 ` Jan Kiszka
2015-01-02 20:18 ` Philippe Gerum
2015-01-02 22:05 ` [Xenomai] registry daemon mangement (was: Re: [Xenomai-git] Philippe Gerum: copperplate: add configuration tunable for registry moint point) Jan Kiszka
2015-01-02 22:17 ` Gilles Chanteperdrix
2015-01-03 18:36 ` [Xenomai] registry daemon mangement Philippe Gerum
2015-01-03 20:09 ` Jan Kiszka
2015-01-03 20:55 ` Philippe Gerum
2015-01-04 13:03 ` Jan Kiszka
2015-01-03 19:40 ` [Xenomai] [Xenomai-git] Philippe Gerum: copperplate: add configuration tunable for registry moint point Gilles Chanteperdrix
2015-01-03 20:17 ` Jan Kiszka
2015-01-03 22:25 ` Gilles Chanteperdrix
2015-01-07 18:14 ` Jan Kiszka
2015-01-12 10:42 ` Gilles Chanteperdrix
2015-01-12 11:19 ` Jan Kiszka
2015-01-12 11:34 ` Gilles Chanteperdrix
2015-01-12 11:59 ` Jan Kiszka
2015-01-12 14:35 ` Philippe Gerum
2015-01-12 14:34 ` Jan Kiszka
2015-01-13 9:22 ` Philippe Gerum
2015-01-13 9:11 ` Jan Kiszka
2015-01-13 9:45 ` Philippe Gerum
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=20150102152245.GG1492@daedalus \
--to=gilles.chanteperdrix@xenomai.org \
--cc=jan.kiszka@web.de \
--cc=lsorense@csclub.uwaterloo.ca \
--cc=xenomai@xenomai.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 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.