On 2010-10-01 22:13, Fred Isaman wrote: > On Fri, Oct 1, 2010 at 4:07 PM, Jim Rees <rees@xxxxxxxxx> wrote: >> Steve Dickson wrote: >> >> On 10/01/2010 09:51 AM, Tigran Mkrtchyan wrote: >> > >> > Hi Steve, >> > >> > thanks for the builds. What I am missing is modprobe configuration file >> > which I have to add myself. >> Unfortunately yes... I have not figured out a good way to have >> the mobprobe done on the client since, in general, init scripts >> don't run on the client (with the exception of rpc.statd and rpc.gssd). >> >> I guess I could come up with an pnfs init script..but that >> seems like a bit overkill just to do a modprobe... >> >> I've already got an init script for the block layout client that does the >> modprobe and starts the daemon. How about we generalize it to modprobe the >> other modules too, and call it the pnfs init script? > > The current code is designed to request the loading of the module as > needed. All that is needed is an alias, of the type > > alias nfs-layouttype4-[INTEGER_ID] ACTUAL_MODULE_NAME I think that's too complicated. Why not export a well known symbol from the layout driver, encoding the layout type, to be looked up by the kernel? Benny > > Fred > > >> -- >> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in >> the body of a message to majordomo@xxxxxxxxxxxxxxx >> More majordomo info at http://vger.kernel.org/majordomo-info.html >> > -- > To unsubscribe from this list: send the line "unsubscribe linux-nfs" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
