introduction of autofs

[Luke Kenneth Casson Leighton]

ha ha.  okay.  introducing autofs into HAL has thrown a large spanner in
the works.

the reason for introducing it is because, in combination with fusexmp it
will _actually_ keep files / dirs out the way and sync'd.

for example, a DVD cannot be taken out of the drive because it's been
forcibly mounted on /media/dvdrom and kaffeine has file handles open
on it: i _want_ the damn thing out, but i can't get it!  close kaffeine,
doesn't help.  expect users to do a umount???? not a chance.

idiot users are more likely to switch their computer off and on again
as a long-term solution to getting their DVD back than they are to
running "umount".


now, the thing is that /etc/mtab keeps changing (!) every 4 seconds
(or whatever you set the timeout to be in /etc/auto.master).


so, this is just thinking out loud, okay?

the criteria are:

- to stop announcements to users of VolumeMount and VolumeUmount
  notifications

- to still keep track of volumes "as if" they were really there.

this is doing my head in just to think about it.

possible solutions:

- to create an /etc/mtab "cache" which is created when the parent
  udi device is first created, and destroyed when the udi parent
  is removed (if ever).

  then, notifications can be made when the "cache" entry changes
  rather than the real /etc/mtab entry disappears.

hmmm... thinking about it, that's really the only viable option.

*grmphheeheehee*

l.


-- 
--
Truth, honesty and respect are rare commodities that all spring from
the same well: Love.  If you love yourself and everyone and everything
around you, funnily and coincidentally enough, life gets a lot better.
--
<a href="http://lkcl.net">      lkcl.net      </a> <br />
<a href="mailto:lkcl at lkcl.net"> lkcl at lkcl.net </a> <br />

_______________________________________________
hal mailing list
hal at freedesktop.org
http://freedesktop.org/mailman/listinfo/hal