Alexander E. Patrakov wrote these words on 01/03/06 00:38 CST: > Randy McMurchy wrote: >>What is new, is that HAL, *at mount time* can pass parameters to >>the mount command. > > Now you explained this better than the previous time. Keywords: "to the > mount command". But, is it HAL itself that passes such options (i.e., > beyond fstab) to the mount command, or is it some KDE-specific thingy?
I am glad we are now communicating. Yes, *HAL itself* is passing these options. The userspace tool (manually running mount, KDE, GNOME, whatever) obeys the HAL rules. HAL is GOD! > Who issues the "mount" command? Anyone. Anytool. Anydesktop. Anything. > User from the command line? That would work. >HAL itself mounts nothing Correct, but it defines what *will happen* when the device is mounted. > it is the task for KDE, gnome-volume-manager or ivman. I > perform my tests with ivman. Doesn't matter what userspace tool, they will all obey HAL rules. And we can set HAL rules at *mount* time. *mount* time Alex, not what it is fstab.... We can use HAL to create the fstab entry that we want and then create more HAL rules to do exactly what we need at *mount* time. Please understand this. Understand this concept and we are home free. Everything else is just work. The concept is there. Understand it. -- Randy rmlscsi: [GNU ld version 2.15.94.0.2 20041220] [gcc (GCC) 3.4.3] [GNU C Library stable release version 2.3.4] [Linux 2.6.10 i686] 00:40:00 up 100 days, 10:04, 3 users, load average: 0.08, 0.21, 0.41 -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
