Order of system startup:how to mount LVM's before services?

[mpartyka]

Hello,

I have a Linksys WMP54G wireless card that i have used with the Linuxant WLAN Driverloader successfully on other systems (redhat suse) but on my Gentoo system i have the /var volume on a LVM partition. And the /var volume is where the windows driver is stored that is used by Driverloader.

So the problem seems to be that Driverloader is a service listed in /etc/init.d/ that has an initialization script. And i know the order in which the initialization scripts are executed can be controlled/changed but in my case, i need to have a service load/execute after all the volumes are mounted, specifically the LVM volumes, which i don't know how to control the order of execution versus the initialized services.

At this point the only thing i can think of is to have the driverloader initialize and then the net.eth0 initialize after right after, like what might occur in the rc.local, if Gentoo used such a thing. I suppose i could call it after everything else in the inittab as it happens on most other distributions.

Anyone have any good ideas on how to accomplish this?

TIA,

[mpartyka]

I just realized i should clarify the problem.

I think that when driverloader loads it looks for the windows driver to activate the nic on the /var volume.

The problem seems to be that the driverloader service gets intialized before the LVM volumes get mounted and therefore the kernel module gets loaded but the NIC does not get activated because it can't find the windows driver on /var to do so.

So to summarize, how can i get the driverloader service to wait unil the LVM volumes are mounted?

Thanks,