Tom Duffy wrote:
> > Hmm is it RedHat specific? The last time I updated mkinitrd I had revert the
> > mktemp portion; as Redhat seems to be the only one that supports mktemp -d
> > (aka temp directory)
>
> well, I still have the part of the patch that takes out the mktemp stuff
> in there, but I also am shipping mktemp rpms so that it will work on other
> distro's. i was going to eventually revert it back to redhat's way.
Hopefully most of the distro's will get caught up and provide the and updated
mktemp version, and the issue will go away.
Just checked my Mandrake system and it has a -d capable mktemp.
>
> > The rpm's I'm building for prerelease 0.10 has XFS build into the kernel
> > which
> > renders the changes to mkinitrd un necessary unless somebody really wants
> > have
> > XFS as a module again.
>
> why are you building different rpms than the one's in LBS?
The last time we tried a build it failed.
Also given the unclear situation of what can be released in regards
to xscsi that will need to be dropped from anything that is put on oss.
>
>
> this makes no sense. we should release xfs with the lbs so we get the
> added exposure on LBS as well.
Three parts to the release are being done.
0.10 Patches
0.10 based rpm based on 2.4.2 + 0.10 Patches + loopfs fix.
LBS based rpms.
The addition of the LBS rpms is contingent on them building and working,
as of last friday that did not appear to be the case.
I'll fire off a build and see how things go if things work I'll add the rpm
to the next testX push.
>
> -tduffy
|