mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: viro@parcelfarce.linux.theplanet.co.uk
To: Ron House <house@usq.edu.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Bug or Feature? Multiply mounted device
Date: Fri, 16 Jul 2004 08:05:31 +0100	[thread overview]
Message-ID: <20040716070531.GA12308@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <40F75738.4040601@usq.edu.au>

On Fri, Jul 16, 2004 at 02:19:04PM +1000, Ron House wrote:
> Hi all, apologies for posting here, but I need to ask the guys who know 
> for sure. In my fstab, I have two entries for my DOS HD so I can mount 
> it with or without CRLF mangling, as follows (sorry for the line splitting):
> 
> /dev/hda5   /d      vfat 
> rw,suid,dev,async,users,umask=033,uid=1500,gid=1001,conv=b 0 0
> /dev/hda5   /dc     vfat 
> rw,suid,dev,async,users,umask=033,uid=1500,gid=1001,noauto,conv=a 0 0
> 
> I just noticed with my new Linux setup (kernel 2.4.20-8smp - don't know 
> what all that means) that it will let me mount both at once, so I can 
> see the partition as either /d or /dc at the same time. I may be going 
> mad, but I seem to recall with my previous kernel that I couldn't do this.
> 
> My question: Bug or feature? If I write all sorts of stuff to both 
> logical devices, will it correctly sort it all out on the same physical 
> device, or will I wreck the partition? All help much appreciated!

You will get both mountpoints as aliases to the tree.  Note that all
fs-specific flags will be ignored on subsequent mounts right now.
Eventually different flags will give you -EBUSY.

BTW, conv= is silently ignored by vfat, so your conv=a is a no-op - that
stuff simply doesn't belong in kernel and CRLF mangling had been removed
quite a while ago (try to make it play nice with mmap(2) and see how soon
you'll run away screaming).


      reply	other threads:[~2004-07-16  7:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-16  4:19 Ron House
2004-07-16  7:05 ` viro [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=20040716070531.GA12308@parcelfarce.linux.theplanet.co.uk \
    --to=viro@parcelfarce.linux.theplanet.co.uk \
    --cc=house@usq.edu.au \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®