Comment 4 for bug 1855318
Revision history for this message
| John W. Brown, Jr. (brownboyjohn) wrote | #4 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
No, this is a real thing. The issue is valid. The explanation does not dismiss it. Even if the assumption that the desktop is somehow looking for these files for autorun functionality, how does that equate into an entire mount point being generated.
Is this fallback behavior of some kind?
Just as the original example illustrated, the automount daemon completely ignores the map file and attempts to mount these 2 mount points instead. It didn't do that before.