Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Tue, 7 Nov 2000 08:32:10 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Tue, 7 Nov 2000 08:31:59 -0500 Received: from pincoya.inf.utfsm.cl ([200.1.19.3]:46091 "EHLO pincoya.inf.utfsm.cl") by vger.kernel.org with ESMTP id ; Tue, 7 Nov 2000 08:31:45 -0500 Message-Id: <200011071330.eA7DUdw26230@pincoya.inf.utfsm.cl> To: Keith Owens Cc: linux-kernel@vger.kernel.org Subject: Re: Persistent module storage - modutils design In-Reply-To: Message from Horst von Brand of "Tue, 07 Nov 2000 09:45:42 -0300." <200011071245.eA7Cjhw20987@pincoya.inf.utfsm.cl> Date: Tue, 07 Nov 2000 10:30:39 -0300 From: Horst von Brand Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Horst von Brand said: [Yes, I know this is bad taste...] > Keith Owens said: > > [...] > > > I have not decided where to save the persistent module parameters. It > > could be under /lib/modules//persist or it could be under > > /var/log or /var/run. I am tending towards /var/run/module_persist, in > > any case it will be a modules.conf parameter. > > /var/lib/persist///> > > or some such. It has to match the kernel version somewhere (in case module > interfaces change), and it also should mirror the tree under > /lib/modules/ if for no other reason that there might show up > several modules named . Note! This _has_ to be in the / filesystem so it works before mounting the rest of the stuff (if ever). This would rule out /var, and leave just /lib/modules/. Makes me quite unhappy... -- Dr. Horst H. von Brand mailto:vonbrand@inf.utfsm.cl Departamento de Informatica Fono: +56 32 654431 Universidad Tecnica Federico Santa Maria +56 32 654239 Casilla 110-V, Valparaiso, Chile Fax: +56 32 797513 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org Please read the FAQ at http://www.tux.org/lkml/