Kin Chung wrote: > > >Ethan Benson wrote: > >On Mon, Jun 25, 2001 at 10:01:37PM +0800, Kin Chung wrote: > [snip] > >what security problem? add potato r3 has all the current libc > >security fixes. or is there a new one im not aware of? > > Oops. I'm running r2 and there was a security alert in April > for glibc 2.1.3-x, for some x < 17. I guess I should have mentioned > that earlier :-(.
Are you aware of deb http://security.debian.org stable/updates main contrib non-free ? > [snip] > > > >if you have to ask these questions i think you should not be compiling > >libc. > [more snippage] > > Perhaps, but then I would not be able to do some of the things that > I do want to. Namely? > Besides, it is helpful to my learning more about Linux. Mostly, I would like > to have some idea about how much risk I am taking. About the biggest possible risk apart from messing with the kernel. > The documentation in my /usr/doc/ is not particularly helpful as it > merely points to the existence of conflict about policy, and it is six > months old. If there is a policy, I do want to know, so I know if I > am about to break policy, before I break it. As you're not a Debian developer, you don't have to care about policy. Neither should you have to build libc6 yourself. > I do know that since I plan to recompile everything else as well, I > don't expect too many strange header mismatch errors. Are you aware of http://linuxfromscratch.org ? Sounds like that might be better for you than Debian. ;) -- Earthling Michel D�nzer (MrCooper) \ Debian GNU/Linux (powerpc) developer CS student, Free Software enthusiast \ XFree86 and DRI project member
