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

Re: New kernels



>>>>> "CCC" == Christopher C Chimelis <chris@classnet.med.miami.edu> writes:

    CCC> I am told we have a solution, so I'm helping to
    CCC> try to get the changes integrated everywhere.  Right now,
    CCC> there are no packages with changes YET (still double-checking
    CCC> things before patching), but there will be a posting on the
    CCC> debian-alpha list announcing it when it's done.

  The kernel patch has been submitted to Alan Cox for the next 2.0
iteration, and I'm still awaiting comment from the glibc people, but
if anyone is feeling adventurous, there's a set of test glibc .debs
available from http://www.eris.rcpt.to/. Installing them is probably a
very bad idea.

  Having said all that DON'T just install them. Things will probably
break if you're running a 2.0 kernel. You need the kernel patch
attached below. I'll also attach the glibc patch, in case anyone has
anything inspirational to say.

  A further note - I had to regress to make 3.76.1 to compile these,
and I'm not altogether convinced about the entire build process, but
It Works For Me ((c) Linus).

  Also, dpkg *will* break. So will a bunch of other things including
chown on symlinks, 'cp -a' on symlinks (which you'll need to recompile
glibc), and probably somet other I don't know about yet. You'll need
to recompile them, and then it will hopefully work. What's the point,
I hear you ask? Well, once they're recompiled against a patched glibc,
they'll work with either (patched) 2.0 or 2.1 kernels. In theory.

  Also, due no doubt to my extended problems with make this morning, I
haven't actually patched up a 2.0 kernel and tested it. Caveat emptor.

  Let me re-emphasize this - do not play with this unless you're
willing to spend a lot of time and effort with a less than certain
chance of it working. That's my job :)

m.

Attachment: kernel-source-2.0.35-patch
Description: Binary data

Attachment: glibc-2.0.7t-patch
Description: Binary data


Reply to: