Hi, On Mon, 16 Nov 2009, Zhu, Peter J wrote:

But I still don't undertand how a software management engine deal with automounter. Can you elaborate on this with some examples?

The software mgmt stack has to deal with media, in particular CDs. It needs to do this because our software can be delivered on DVDs or multiple CDs. So if libzypp wants to install a certain package that happens to live on CD2 of a set or on a DVD (the repo metadata will tell libzypp which media to use), it can request the user to insert the required CD/DVD. As soon as the user inserts the CD any normal auto-mounting would mount it, possibly opening some dialog boxes requesting the user what to do with the just inserted CD. So libzypp better deactivates this. libzypp uses HAL also for device discovery, to find the CD/DVD drive(s) of the system. It does this so that once the user puts in a CD it can be mounted (under control of libzypp) and queried (e.g. for the volume name). libzypp wants to do this only for removable CD/DVD drives, so it uses hal also to determine the type of block devices. So, you would loose the automatic device discovery (package install from CD/DVD would possibly be broken until you tell e.g. yast which drive to use), and the automounter would be left enabled possibly leading to unexpected dialog boxes as soon as a requested media is inserted.

And by looking at code of HalContext.cc, there is one macro of NO_HAL seems created from config.h.in to disable hal at at all. So what function would I lose if I disable HAL from libzypp? And how to enable this macro? Sorry I did't know cmake.

Put a line ADD_DEFINITIONS (-DFAKE_HAL) (or -DNO_HAL) in zypp/CMakeLists.txt . But you probably don't want to do this, as per the above. Ciao, Michael. -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org