public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: cygwin@cygwin.com, eldlistmailingz@tropicsoft.com
Subject: Re: The 'mount' function different from Linux
Date: Fri, 17 Aug 2018 09:46:00 -0000	[thread overview]
Message-ID: <9ca36e93-7b21-f133-bb82-38ec4949ed05@redhat.com> (raw)
In-Reply-To: <1e1e10c0-fa24-0191-7f8e-c8748184d079@tropicsoft.com>

On 08/16/2018 04:08 PM, Edward Diener wrote:
> The 'mount' function in cygwin is decidedly different from Linux. What 
> is the reason for this ?

- POSIX does not specify mount(1) - it is inherently non-portable and 
platform specific.  So any expectation of similarity between platforms 
is bound to break (as you've discovered)

- Cygwin isn't mounting devices into the OS, but creating mappings for 
Cygwin to use. On Linux, the mount command is actually manipulating 
block devices and the kernel; on Cygwin, everything in the mount command 
is in userspace. Windows as the kernel did the actual device 
manipulation earlier on.  As such, the tool REALLY CANNOT mimic what 
Linux does, because it IS NOT doing the same things.

-- 
Eric Blake, Principal Software Engineer
Red Hat, Inc.           +1-919-301-3266
Virtualization:  qemu.org | libvirt.org

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

      reply	other threads:[~2018-08-16 21:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-17  9:41 Edward Diener
2018-08-17  9:46 ` Eric Blake [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=9ca36e93-7b21-f133-bb82-38ec4949ed05@redhat.com \
    --to=eblake@redhat.com \
    --cc=cygwin@cygwin.com \
    --cc=eldlistmailingz@tropicsoft.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).