The lastest crypto patch isn't the one on cygnus' ftp site. The latest one is 2.1.2, which you can find on ftp://ftp.nl.linux.org/tmp/, among other places (search http://ftpsearch.ntnu.no/). The announcement says crypto patches didn't need updating, so you can use the 2.1.2 crypto patches for glibc-2.1.3
The locale info is now distributed as part of glibc, so it's in the gblic-2.1.3 tarball.
You see, all glibc-packages *are* up-to-date. And, imho the glibc guys are doing a great job. Glibc is as important and complicated as the Linux kernel. Glibc guys aren't as well known as linux guys though.
The only problem is that the ftp directory listing is admittedly somewhat confusing. Worse, the ftp.gnu.org ftp site is rather confusing and it holds imho too much outdated tarballs. If someone would clean up that ftp site a bit, it would save quite some bandwidth and diskspace for ftp.gnu.org mirrors.
If you write the program yourself, you can use any license you like. For example, you could use the GPL, *with the exception* that the program can be linked to one specific library. This "modified GPL" is, however, not compatible with the GPL. For example, what they're doing now is probably OK (I don't know the software), but if they're using GPLed code like readline, then they're violating the GPL. If they wrote all code themselves however, there's no problem. Maarten
Slashdot Mirror
while preperation a-g were quite succesful, preperation h was a total disasster.
The lastest crypto patch isn't the one on cygnus' ftp site. The latest one is 2.1.2, which you can find on ftp://ftp.nl.linux.org/tmp/, among other places (search http://ftpsearch.ntnu.no/). The announcement says crypto patches didn't need updating, so you can use the 2.1.2 crypto patches for glibc-2.1.3
The locale info is now distributed as part of glibc, so it's in the gblic-2.1.3 tarball.
You see, all glibc-packages *are* up-to-date. And, imho the glibc guys are doing a great job. Glibc is as important and complicated as the Linux kernel. Glibc guys aren't as well known as linux guys though.
The only problem is that the ftp directory listing is admittedly somewhat confusing. Worse, the ftp.gnu.org ftp site is rather confusing and it holds imho too much outdated tarballs. If someone would clean up that ftp site a bit, it would save quite some bandwidth and diskspace for ftp.gnu.org mirrors.
Regards,
Maarten
If you write the program yourself, you can use any license you like. For example, you could use the GPL, *with the exception* that the program can be linked to one specific library. This "modified GPL" is, however, not compatible with the GPL. For example, what they're doing now is probably OK (I don't know the software), but if they're using GPLed code like readline, then they're violating the GPL. If they wrote all code themselves however, there's no problem. Maarten