All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Linda A. Walsh" <lkml@tlinx.org>
To: Karel Zak <kzak@redhat.com>
Cc: util-linux@vger.kernel.org
Subject: Re: Q: (RFE?)  How do you specify the 'no-canonicalize' option in fstab?
Date: Fri, 25 Jul 2014 21:46:15 -0700	[thread overview]
Message-ID: <53D33297.20502@tlinx.org> (raw)
In-Reply-To: <20140725072143.GN26781@x2.net.home>

Karel Zak wrote:
>>>> no-canonicalize in /etc/fstab?
>>> Why do you want something like this?
> Well, I'm trying to help you, so it would be nice to have more
> information about your use-case...
---
    Was my description still unclear?  when I use a "symbolic link"
to a file or to a device, when I look at where I am, I want to
see what I typed in as part of the path.

If I'm in my home dir, I can cd into
bin/audio to work on scripts.  If I want to test with large
files, they are in /Audio, where the scripts dir is
under /Audio/scripts.

If I am making a short change and not testing, I usually
work by cd'ing into the local path ~/bin/audio -- I wouldn't
be real happy if it dumped me in /Audio/scripts each time, even
though that would be a canonical name.

Same with Devnames -- If I use the standard /dev/VG/LV in
constructing a name, being passed a mutated form forces an
automated script to go belly up -- looking for the VG after
/dev/, and looking for LV's under the VG.

So in my usecase, I'd like to mount the volumes using
/etc/fstab and still be able to use the no-canonicalize
option. 


??  Reasonable to be able to specify the switch
via fstab and provide consistency with the command
line option?

      parent reply	other threads:[~2014-07-26  4:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-24  4:32 Q: (RFE?) How do you specify the 'no-canonicalize' option in fstab? Linda A. Walsh
2014-07-24  7:32 ` Karel Zak
2014-07-25  2:20   ` Linda A. Walsh
2014-07-25  7:21     ` Karel Zak
2014-07-25  7:44       ` Linda A. Walsh
2014-07-26  4:46       ` Linda A. Walsh [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=53D33297.20502@tlinx.org \
    --to=lkml@tlinx.org \
    --cc=kzak@redhat.com \
    --cc=util-linux@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 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.