Thorsten Leemhuis (fedora(a)leemhuis.info) said:
>> I don't see how this is a problem.
> Getting rid of the suffix -PAE afaics would solve exactly the problem
> that now is "just exposed to more people" (or might make solving it a
> lot easier afaics).
Well, the problem is that you'd have to define a way that the now
PAE-ful kernel.i686 is not installed on some i686 boxes. That gets a
lot more complicated.
I thought we were going to enable these in rawhide since the e1000
EEPROM problem was fixed:
CONFIG_FUNCTION_TRACER (was CONFIG_FTRACE)
Also hda audio powersave is still off; we have:
On Wed, 2009-02-04 at 18:19 -0500, Jon Masters wrote:
> On Wed, 2009-02-04 at 03:47 -0500, Jon Masters wrote:
> > I'm considering pushing an update to F-9 since v3.5+ is so much faster
> > than previous releases - and it impacts boot time, but I have to admit
> > that I was more concerned about F10 and rawhide until now.
> Oh, there's a slight issue with the handling of modules.order still for
> the binary tries in newer module-init-tools. This might manifest in a
> switch of e.g. module used in initrd for storage devices with multiple
We now have binary versions of files like "modules.dep", "modules.alias"
and "modules.symbols". These end in ".bin" and *augment* but do not
replace the textual versions of these files. If we find the binary
files, we are *much* faster at loading modules - boot overhead is e.g.
under one second.
But we need to be able to make changes to these binary files in order to
add ordering support, and also just for the future. Our plan is to
freeze the old text file format (the "last" change will be the one made
recently in which modules.dep can now have relative paths to save space)
and to fallback to it whenever the binary format changes and modprobe
finds older binary files.
This works fine, but means that, if we upgrade module-init-tools and
there is a binary format change, then the system will be "slow" booting
before depmod has been re-run again. I'm thinking about just doing a
"depmod -a" on upgrade in such cases in the future...is there a problem
with that idea?
Head's up that we're going to be playing with config files for modprobe.
The idea is to have just one upstream config file, and for some things
that make sense to get fixed in the upstream kernel tree rather than in
So if someone has a billion year old tape drive that had a hack for
loading some ioctl module or whatever, and we break it, and there's a BZ
involved that smells like modprobe, sent it my way please :)
there is some build regression with openafs and the latest Fedora 10
x86_64 kernel and it could be either due to the kernel or due to other
changes in the build environment. Is there a way to retrieve older
kernel-devel packages to test this? (Actually I think I know the
answer is yes, so the question is rather "how" :)
Axel.Thimm at ATrpms.net