public inbox for util-linux@vger.kernel.org
 help / color / mirror / Atom feed
From: Karel Zak <kzak@redhat.com>
To: Aleksey Midenkov <midenok@gmail.com>
Cc: util-linux@vger.kernel.org
Subject: Re: Per-filesystem default mount options
Date: Wed, 23 Oct 2013 17:27:44 +0200	[thread overview]
Message-ID: <20131023152744.GB21504@x2.net.home> (raw)
In-Reply-To: <CAF8BazB4jsWj0_3Ns14o5qDF2wVch9_K5u_ZsJ8GwjMyNZb6Uw@mail.gmail.com>

On Sat, Oct 19, 2013 at 08:03:29AM +0400, Aleksey Midenkov wrote:
> On Fri, Oct 18, 2013 at 12:34 PM, Karel Zak <kzak@redhat.com> wrote:
> > On Wed, Oct 16, 2013 at 06:13:17PM +0400, Aleksey Midenkov wrote:
> >> Is it possible to specify per-filesystem default mount options
> >> somewhere in configuration file?
> >
> >  /etc/fstab, or tune2fs for extN, or /etc/nsfmount.conf for NFS.
> >
> >  The per-filesystem-type default options are also hardcoded in kernel.
> >
> 
> I'm sorry for my misguide and, perhaps, a wrong start. What I mean is
> per-fs type default mount options. That's true, they are hardcoded in
> kernel. But, there is a need to have them customized. I know, there is
> ton of user-level utils that maybe can provide it. But... I feel that
> this basic feature is important for the core. That's why I decided to
> ask here in hope that you will discuss this with me.

 If you really need a generic (on device independent solution), then I
 don't see a better way than improve libmount for read something 
 like /etc/mount/<fsname>.conf. The problem is that such feature will 
 not be usable for non-libmount applications.

> I keep stumbling upon this lack for a million-th times for as long as
> 15 years. Every barely installed host, f.ex. even routers that have no
> ability to install another utils except the 'mount', they require me
> each time to put charset from command line. And you know, this is the
> common source for errors for non-latin countries like your servant's.

 I understand the pain for removable media, but for regular disks you
 can use /etc/fstab, right?

> When charset option is forgotten the filenames are garbled after copy.
> And you not always notice it because non-latin ones are somewhere deep
> inside. But after some time passed you see the surprise...

 I understand.

    Karel

-- 
 Karel Zak  <kzak@redhat.com>
 http://karelzak.blogspot.com

  parent reply	other threads:[~2013-10-23 15:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-15 17:31 Per-filesystem default mount options Aleksey Midenkov
2013-10-16 14:13 ` Aleksey Midenkov
2013-10-18  8:34   ` Karel Zak
2013-10-22 14:12     ` Aleksey Midenkov
     [not found]     ` <CAF8BazB4jsWj0_3Ns14o5qDF2wVch9_K5u_ZsJ8GwjMyNZb6Uw@mail.gmail.com>
2013-10-23 15:27       ` Karel Zak [this message]
2013-12-13 12:49         ` Aleksey Midenkov
2013-12-19 10:58           ` Karel Zak

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=20131023152744.GB21504@x2.net.home \
    --to=kzak@redhat.com \
    --cc=midenok@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox