[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: re kernel-2.6.0-test: what to do with /etc/modprobe.conf??
- From: "Robert P. J. Day" <rpjday mindspring com>
- To: rhl-beta-list redhat com
- Subject: Re: re kernel-2.6.0-test: what to do with /etc/modprobe.conf??
- Date: Thu, 31 Jul 2003 07:38:33 -0400 (EDT)
On 31 Jul 2003, Féliciano Matias wrote:
> Le jeu 31/07/2003 à 12:57, Robert P. J. Day a écrit :
> > based on my reading, the new kernel prefers to read from the
> > file /etc/modprobe.conf, rather than the older /etc/modules.conf.
> >
> > to help in the migration, there is the utility
> > "generate-modprobe.conf", but in this situation, it doesn't work --
> > it fails complaining of a missing "modprobe.old".
> >
> > i'm suspecting that generate-modprobe.conf was written with the
> > assumption that one would have upgraded separately to the newer
> > version of modutils, which was backwards compatible and, IIRC,
> > moved the older versions of the module commands to their
> > corresponding ".old" names.
> >
> > this is, i'm guessing, what generate-modprobe.conf is looking
> > for, but severn, since it comes with the newer version of
> > modutils already, has no such ".old" backups. hence the failure.
> >
> > thoughts?
> >
>
> Try to copy modprobe from RH9 to modprobe.old.
i suspect that would work fine, but it doesn't help someone
testing a severn box who doesn't have access to any RH 9
rpms.
is there a usable way to run this under the circumstances,
or should i bugzilla this?
rday
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]