On Tue, 29 May 2001, Mike Castle wrote:
> On Tue, May 29, 2001 at 06:40:34PM +0000, Richard Adams wrote:
> > On Tue, 29 May 2001, Mike Castle wrote:
> > > The problem is libc.
> >
> > As far as i see it, it is NOT a lib problem, anyway how could it be a libc
> > problem when in this day and age we use "glibc".
>
> libc IS glibc
>
> nexus@thune[12:12pm]~(501) ls -l /lib/libc*
> -rwxr-xr-x 1 root root 4851005 May 29 12:09 /lib/libc-2.2.3.so
>
> nexus@thune[12:12pm]~(502) ls -l /lib/glib*
> ls: No match.
No you wont get a match like that, what you missed is the symbolic link in /lib
for libc-2.2.3.so to libc.so.6 which is glibc, there was a transission a few
years ago from libc5 ro libc6 libc6 is called glibc it may sound and be
confusing but i can assure you that is fact. I am sure you would know about
that tho'.
Even Redhat installs "old libc5" for compatability that is in the notes i
belive. Libc5 and (g)lib6 are not compatable that caused so many problems
during and after the transission.
Anyway i cant see a (g)libc problem in the kernel souce from the
discussion on this thread. Only if the libs are so outdated not to be
compatable with the souce of today, however that is all explained in the
Changes file, but what the heck, who reads the dam doco's anyway..
>
> > > Many distributions have /usr/src/{asm,linux} as symlinks into the
> > > /usr/src/linux/include heirarchy.
> >
> > I think we need to know that its not a distribution who creates these symlinks
> > but the actual make program itself, once again 'make mrproper' does this for us
> > does it not.?. It was not so long ago that one needed to create these links
> > him/herself.
>
> That was a typo on my part. And one I mistakenly carried though out the
> mail. Damn.
Dont worry, i make um as well, (i am sure more than you).
>
> That should have read "man distributions have /usr/include/{asm,linux} as
> ^^^^^^^
Oops,, i know you typed main but your keyboard passed man to the mailer.
> symlinks into the /usr/src/linux/include heirarchy."
>
> > I think you have miss interpreted the whole point of this tread, no one
> > mentioned "directorys" under "linux" as in /usr/src/linux, they (the ones you
> > say) are all symlinks period. Header files reside in /usr/include which is then
> > linked to /usr/src/linux/include/(whatever).
>
> That's the thing.
>
> There should be NO symlinks from /usr/include to
> /usr/src/linux/include/(whatever).
Ok, write to linux-kernel and tell then to alter all previous kernel versions
before 2.4, Remember this, i have said it time and time again, differnt distro's
do things differently, you can as a user alter what you want, i prefer the way
"slackware" does it which is in tradition the linux way, it still does what i
have told you and AFAIK will do so untill the masses do otheriwse or pressure
to change avails. If i have my way i say leave it as is.
So saying there should be NO symlinks in the linux directory is simply not
true, there are and as i see it will be for a while to come, possably not in your
Redhat distro, but thats your thing, i presume you have Redhat considering your
views.
>
>
> > I just dont see the problem. Maybe my 10 years of Linux use is too much for me
> > to understand just what the problem is that you/others think is there.?
>
> And I've been using it for 7 years... your point?
No point, my points have been made, all i have done is show that many distro's
still do it the linux traditional way.
If Redhat or anyother distro., want to do it thier way then i have no objection,
why should i, they are free to do as they choose as i am free to change what i
want to on my system period.
I presume you have not used slackware very much,? according to your views of
which i do respect BTW.
I am sure that if you follow the linux-kernel mailing list you will see that
there are many for's and as many, against's about changes.
>
> mrc
--
Regards Richard
[EMAIL PROTECTED]
http://people.zeelandnet.nl/pa3gcu/
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.linux-learn.org/faqs
