|
MinGW-notify digest, Vol 1 #1377 - 1 msg: msg#00020gnu.mingw.announce
Send MinGW-notify mailing list submissions to mingw-notify-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@xxxxxxxxxxxxxxxx To subscribe or unsubscribe via the World Wide Web, visit https://lists.sourceforge.net/lists/listinfo/mingw-notify or, via email, send a message with subject or body 'help' to mingw-notify-request-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@xxxxxxxxxxxxxxxx You can reach the person managing the list at mingw-notify-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@xxxxxxxxxxxxxxxx When replying, please edit your Subject line so it is more specific than "Re: Contents of MinGW-notify digest..." This list is used to send updates of submitted patches, bug reports and file releases. You are discouraged from posting to this list. If you wish to unsubscribe you can do so at https://lists.sourceforge.net/lists/listinfo/mingw-notify. Today's Topics: 1. [ mingw-Bugs-1475483 ] mount Function not implemented (SourceForge.net) --__--__-- Message: 1 Date: Fri, 26 May 2006 19:20:12 -0700 To: noreply-pyega4qmqnRoyOMFzWx49A@xxxxxxxxxxxxxxxx From: "SourceForge.net" <noreply-pyega4qmqnRoyOMFzWx49A@xxxxxxxxxxxxxxxx> Subject: [Mingw-notify] [ mingw-Bugs-1475483 ] mount Function not implemented Bugs item #1475483, was opened at 04/24/06 05:00 Message generated for change (Comment added) made by sf-robot You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=102435&aid=1475483&group_id=2435 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: msys Group: None >Status: Closed Resolution: Remind Priority: 5 Submitted By: anatoly techtonik (techtonik) Assigned to: Earnie Boyd (earnie) Summary: mount Function not implemented Initial Comment: Can't mount a path in MSYS. --- user@STATION /etc $ mount help mount: not enough arguments Usage: mount [OPTION] [<win32path> <posixpath>] ... user@STATION /etc $ mount d:/temp /e2 mount: /e2: Function not implemented user@STATION /etc $ mount d:\temp /e2 mount: /e2: Function not implemented user@STATION /etc $ cd /d/temp user@STATION /d/temp $ --- ---------------------------------------------------------------------- >Comment By: SourceForge Robot (sf-robot) Date: 05/26/06 19:20 Message: Logged In: YES user_id=1312539 This Tracker item was closed automatically by the system. It was previously set to a Pending status, and the original submitter did not respond within 30 days (the time period specified by the administrator of this Tracker). ---------------------------------------------------------------------- Comment By: Keith Marshall (keithmarshall) Date: 04/28/06 06:11 Message: Logged In: YES user_id=823908 FWIW, I've attached a pair of rough and ready scripts, which provide rudimentary mount/umount manipulation of /etc/fstab, directly from the command line. I've not attempted to make them especially robust, but used sensibly, they get the job done. To deploy them, unpack the tarball into /bin, and rename to remove the `.sh' extensions. Do note that they continue to (ab)use the /etc/fstab file, as if it were /etc/mnttab, so I've not provided any of the functionality which is normally attributed to /etc/fstab, (/etc/vfstab on SunOS); neither have I included any support for mount options -- syntax is restricted to: mount mount win32path mountpoint umount mountpoint umount win32path ---------------------------------------------------------------------- Comment By: Keith Marshall (keithmarshall) Date: 04/26/06 11:00 Message: Logged In: YES user_id=823908 > Are changes to /etc/mnttab persistent across login sessions? Changes to /etc/fstab are, at present. If we modifiy the DLL code to read /etc/mnttab instead of /etc/fstab, then that should continue to be the case. We could then redesignate /etc/fstab to work with a modified mount command, to specify default mount points for paths we want to "mount" intermittently, just as it would be used on a modern *nix system. Even without the modification, we could kludge something that would offer similar functionality, but the file name usage might seem odd, to users coming from a *nix background. > BTW where are sources for mount.exe ? I can't find them via ViewCVS. Neither ViewCVS nor anonymous CVS are reliable sources on SF at present; the content of these repositories have not been updated, to match the development status, for several weeks now, following a hardware failure. See the SF Site Status page for more info. ---------------------------------------------------------------------- Comment By: Earnie Boyd (earnie) Date: 04/26/06 07:33 Message: Logged In: YES user_id=15438 http://cvs.sourceforge.net/viewcvs.py/mingw/msys/rt/src/winsup/utils/ uses http://cvs.sourceforge.net/viewcvs.py/mingw/msys/rt/src/winsup/cygwin/ uses http://cvs.sourceforge.net/viewcvs.py/mingw/msys/rt/src/newlib/ ---------------------------------------------------------------------- Comment By: anatoly techtonik (techtonik) Date: 04/26/06 06:47 Message: Logged In: YES user_id=669020 The idea with automatic modification of /etc/mnttab seems rather good to me. Are changes to /etc/mnntab persistent across login sessions? BTW where are sources for mount.exe ? I can't find them via ViewCVS. ---------------------------------------------------------------------- Comment By: Earnie Boyd (earnie) Date: 04/26/06 04:22 Message: Logged In: YES user_id=15438 Yes, it is a bug I need to get to that adding a device while msys-1.0.dll is active in memory doesn't DDTRT. Closing your MSYS session and reopening or touching the /etc/fstab would have allowed cp foo /e to work. ---------------------------------------------------------------------- Comment By: Keith Marshall (keithmarshall) Date: 04/25/06 15:29 Message: Logged In: YES user_id=823908 Curiously, I've recently been giving some thought to this. Working with USB storage media can be a bit of a pain, and I've found that editing /etc/fstab can help MSYS to actually recognise that /e really does mean the hot-plug media device I just plugged in, rather than a *file* called /e -- yes that happened to me yesterday; `cp foo /e' created a file called /e, instead of putting a copy of foo on my memory stick! To solve this, I found I needed to edit /etc/fstab, adding the line `e:/ /usb', so adding /usb to the internal mount table, and then `cp foo /usb' did the deed. This got me to thinking that a pair rudimentary scripts, emulating the most basic syntax of mount and umount, and simply adding or removing lines from /etc/fstab on demand, and so capitalising on the dynamic mapping feature, might be convenient. I haven't yet had time to develop the idea further, but if I do, I'll certainly share it. It would be nice, although not essential, if MSYS *did* read /etc/mnttab -- this, with the double `t' is, IIRC, the name commonly used in UNIX systems -- instead of /etc/fstab. That way we more closely emulate modern UNIX behaviour; otherwise we would have to insist on: mount realpath virtualpath umount eitherpath (Of course we could still let mount with no args invoke `/bin/mount.exe', to display the current mount table). ---------------------------------------------------------------------- Comment By: Earnie Boyd (earnie) Date: 04/25/06 03:57 Message: Logged In: YES user_id=15438 When /etc/fstab is modified the mount points are refactered dynamicly. There are a few bindings that are necessary for the operation of MSYS those cannot be changed by the user. I would be appreciative of modification to the MSYS mount code to allow a user to define mount points in /etc/fstab and then control those mounts with /etc/mntab. Then mount would change /etc/mntab based on /etc/fstab and MSYS would read /etc/mntab for the changes dynamicly. I will not personally do this because I don't really see the need since changing /etc/fstab will dynamicly change the internal mount table. ---------------------------------------------------------------------- Comment By: anatoly techtonik (techtonik) Date: 04/24/06 21:44 Message: Logged In: YES user_id=669020 Quote: "These automatic file system bindings are not changable by the user. User defined file system bindings can be created by specifying them in the /etc/fstab directory as explained in table 2." This doesn't explain why it is not possible to make user defined file system bindings work at runtime? ---------------------------------------------------------------------- Comment By: Earnie Boyd (earnie) Date: 04/24/06 09:26 Message: Logged In: YES user_id=15438 See the /doc/msys directory. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=102435&aid=1475483&group_id=2435 --__--__-- _______________________________________________ MinGW-notify mailing list MinGW-notify-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@xxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/mingw-notify End of MinGW-notify Digest |
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| Previous by Date: | MinGW-notify digest, Vol 1 #1376 - 3 msgs: 00020, mingw-notify-request-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f |
|---|---|
| Next by Date: | MinGW-notify digest, Vol 1 #1378 - 1 msg: 00020, mingw-notify-request-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f |
| Previous by Thread: | MinGW-notify digest, Vol 1 #1376 - 3 msgsi: 00020, mingw-notify-request-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f |
| Next by Thread: | MinGW-notify digest, Vol 1 #1378 - 1 msg: 00020, mingw-notify-request-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
| News | FAQ | advertise |