Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the math-captcha domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/news.numlock.ch/public_html/wp-includes/functions.php on line 6114
volume daemon – A changelog by Daniel Mettler

volume daemon

vold volume daemon for linux:

But there already is an automounter in Linux! Why do we need this ‘vold’?
Something I did never like about the automounter is that its auto mounting is somehow special. Devices are not mounted automatically when they are available but when they are accessed. Another point that really annoyed me was that when I plugged in my Memory Stick in Windows or in Mac OS X, I needn’t do anything else – it just worked. I plugged it in on Linux and … nothing happened (as usual..). I could live with the mount process but its not only that. The device names may change if you have more that one hotpluggable device depending on which device you plug in first.

according to clemens, vold is in fact very similar to the volume daemon ‘vold’ found on Solaris or the ‘autodiskmount’ on Mac OS X. hmm.. polling/busy waiting?

i need to check it out as soon as i find some spare time (a rare thing lately and probably also for the next few months). i wonder whether there are any synergies with the new, planned devfs replacement.. possibly. perhaps an opportunity to get rid of hardcoded devices in the “scan file”.

CategoriesITTags

Leave a Reply

Your email address will not be published. Required fields are marked *

+ 78 = 82

This site uses Akismet to reduce spam. Learn how your comment data is processed.