Hello David, you wrote
> I finally broke down (sigh) and started working with glibc 2.1
> (sigh). Added about 120k to the root.lrp - and lots of questions for
> me to ask :-) Note that I am STILL using Linux 2.2 - probably going
> to upgrade to 2.2.19 soon.
>
> I think the final break was when I asked if the new bridge utils can
> be compiled under glibc 2.0. The answer was simple:
>
> No.
>
> (Gak!) Also, it would seem more and more utilities simply will NOT
> compile under glibc 2.0 headers. I just tried pidentd (updated today)
> and it didn't seem to. What is the best way to release *.lrp files
> compiled against glibc 2.1? Perhasp just put something in the help?
> or something more general in a HowTo?
>
> Right now, the Oxygen image with glibc 2.1 is not quite usable as I
> had to get rid of ifconfig; however, now I'm fumbling with 'ip' and
> not getting very far.
>
I put a short summary of the most used ip commands on my page
http://leaf.sourceforge.net/devel/ericw/ip-syntax.php
A rather extensive and good documentation you can find at :
http://snafu.freedom.org/linux2.2/docs/ip-cref/ip-cref.html
> I didn't get much out of "The Advanced Routing HowTo" - there were
> simply too many points where it assumed you had knowledge.
>
> I know I can do:
>
> ifconfig eth0 172.16.3.44 netmask 255.255.0.0 broadcast 172.16.255.255
> up
>
> I gather this takes TWO commands under 'ip' ...
right
ip link set eth0 up
ip addr add 172.16.3.44/16 dev eth0
>
> Also, I can't seem to get the equivalent of this:
>
> route add -net 127.0.0.0 mask 255.0.0.0 dev lo
ip addr add 127.0.0.0/8 dev lo
ping 127.1.2.3 functions then allready
you could add
ip route add 127.0.0.0/8 via 127.0.0.1
> I'll keep trying.
>
> Also, compiling glibc 2.1 from scratch, it would seem that my results
> generate LARGER files in some cases but not others. In particular, I
> compiled with --enable-omitfp ...should I have chosen something else?
>
> Also, how do you strip functions out...?
>
> Also, libnsl SEEMS by all accounts needed only by NIS/NIS+ - it's even
> in the nis/ dir in glibc. What gives? Can we strip out all the NIS
> functions?
>
> Now, on all this - should I skip glibc 2.1 and go for glibc 2.2
> instead?
>
> _______________________________________________
> Leaf-devel mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/leaf-devel
Eric Wolzak
_______________________________________________
Leaf-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/leaf-devel