The scenario is: Let’s say I have autofs_enable , working with media map. If I have a CD in CD drive , all is well and when the system is fully booted up /media contains a directory through which I can access the content of the CD-ROM. Now if you eject this CD , and insert a new one, nothing happens. /media does not contain a new access point for the new disk inserted in the device. What I would expect is when I change the media in Cd-rom , a new access point for the volume in question should be reated in /media. Perhaps this functionality is exposed differently by the automounter, but them I would not expect the CDrom to be accessible at all though the media map. > he problem here is that it's quite hard to fix, there's a risk > of breaking existing functionality, and the problem is largely cosmetic. until you have more than 10 of them there, when it largely annoying. anyway, what is the reason it is very hard to fix and it would break existing functionality. can you please shed some light ? > Huh, never heard about that. I'd expect the existing mechanism to handle > that case just fine. Could you submit a PR? > On 21 Apr 2016, at 12:57, Edward Tomasz Napierała <trasz_at_FreeBSD.org> wrote: > > On 0420T1545, dan_partelly wrote: > > [..] > >> Another example is the autofs mounter. The prject was marked as complete >> by FreeBSD foundation in 2014. Last I tried it to autmount removable >> devices, it left directory after directory in the autofs managed directory. >> This is known behavior. > > Yup. The problem here is that it's quite hard to fix, there's a risk > of breaking existing functionality, and the problem is largely cosmetic. > >> It also did not worked as it should ??? (show it >> manage removable media correctly ) changing CD/DVD media disks. Presumably >> In could have somehow manage it to work by making yet another scaffolding >> of scripts as a questionable glue between devd and automounters. That if >> devd receives media change notifications. I dont know. If not I could patch >> the kernel, yeah. But it is just much to simple to not bother at all and >> use OSx. > > Huh, never heard about that. I'd expect the existing mechanism to handle > that case just fine. Could you submit a PR? > > [..] > > _______________________________________________ > freebsd-current_at_freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org"Received on Thu Apr 21 2016 - 10:26:06 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:04 UTC