> My backup package uses cpio -Hcrc feature to make verify passes
> and pax don't know about this (new) format. So I compiled a
It is a big issue. The author is aware of it and I already have a
beta with list toc only support. I care especially since once it is
in pax I can make a tiny .rpm extractor. Rpm uses the SVR4-crc format.
It will probably be a while for pax, though.
> statically linked cpio, which works fine, but alas is 500K+ in
> size, so I cannot have it put on the disk.
Did you strip it? I think you will see it go to 250K with "strip cpio".
> The solution would be to have cpio dynamically linked with the
> libc5 you includes in the distribution, but unfortunatly, I haven't
> such an old linux box (the oldest I have is glibc2.0).
>
> Could you build me such a cpio, or give me a trick on how to do it
> on my glibc2 boxes (I have libc5 on them for backward compatibility) ?
I am working on my own HOWTO for this (libc5 compiling on glibc).
There are a couple of issues that make it a pain-in-the-ass. The specs
files for the compilers and the linker scripts are a black art. First,
you need libc5 include files, which you probably *don't* have, as they
are not needed just to run libc5 executables. Probably the *easiest*
way would be a chrooted environment just for libc5 compilation, maybe I'll
build one of these and release it as a complete answer. Or maybe I'll
just post include-headers/gcc-specs/ld-scripts with instructions. Or maybe
I'll convert the whole thing to glibc... nobody hold your breath for this
answer, I am guessing on months of work just to try to figure out what
in glibc itself can be shrunk. SPECIAL OFFER: If one of you can make the
glibc itself smaller than 425K (my libc5 is 410K or so), and show me how,
I'll do all the work to recompile *everything* against it! ANYWAY, for now,
I put "gnu-cpio.bz2" up in the add-ons directory. Just get that. Make
sure to delete the cpio hard link to pax/tar and leave pax/tar alone.
work
> megaraid.o though, you might consider having it included as it
> is the driver needed for Dell and HP servers, so it will be
> quite needed in the near future),
It will probably not make it into the default, but it will be in the
add-ons directory. I am considering removing the Qlogic and BusLogic and
adding the Advansys driver, since Qlogic seems to be out of the scsi card
business and MyLex MultiMaster is increasingly marginalized in the low-end
market. Between the SIIG/Initio and Advansys and some others of the new
popular cheap cards, the Advansys seems like a winner to me. Now, of:
aha152x aha1542 aic7xxx eata fdomain ncr53c8xx seagate
I have to wonder how many people are using eata, fdomain, and seagate; also.
ANY FEEDBACK AND HELP ON THIS ISSUE IS _VERY_ APPRECIATED!
-Tom
