[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Applying the kernel-patch-2.2.10-raid 2.2.10-3 to 2.2.15

Mike Bilow wrote:
> All I can tell you is that I manually extracted the binaries using "dpkg
> --extract raidtools2_0.90.990824-5.deb" onto a floppy disk and they worked
> fine when booted from the the install disks.  In fact, I just checked
> manually, and the only required libs are ld-linux.so.2 (the dynamic
> linker) and libc.so.6 (the main glibc run-time).  I have not checked, but
> I think even busybox requires these.
> -- Mike
> On 2000-05-16 at 23:52 -0700, Bill Jennings wrote:
> > These will need to be statically-linked programs, as the
> > boot floppies do not have the correct shared libraries to
> > run the standard binaries.
> * * *
> > I've done this several times now.  It's a pain, but once you
> > get past the base install, it's pretty much business as
> > usual.

The boot floppys generate stripped down libraries to specifically cater
only for specified binaries. This is done to greatly reduce the size of
libraries for the floppies.

If the binaries from raidtools2 work with the libraries supplied from
boot-floppies then i would say that its a bit of a conincidence, dont
expect all binaries to run.

After base is installed the proper (full) libraries will be installed,
so dynamicly linked raidtools2 binaries will run.

The best i could recomend for raid installs is to install
base+raidtools2 and then move things around, root raid isnt really a
good idea anyway (except for raid1)

Making statically linked raidtools binaries would work and wouldnt take
much space, but most people probably wouldnt need them statically
linked, how far do you go with static packages ?

It would be great to have an install that handles raid2 and lvm, but it
wont be happening with potato.


Reply to: