Morpheus believes it is 2199 because he has no idea there were other Matrices before the current one.
Actually, Agent Smith confessed to during Morpheus' interrogation during the first movie that there was at least one prior incarnation of the Matrix - the 'perfect' one, which no-one accepted and they lost 'whole crops' because of it. The Architect confirmed this to Neo also in Reloaded.
It should be noted that this vulnerability only affects BIND 8 servers that perform recursion (ie, the regular nameservers that things like your workstation/laptop/whatever that you ask for a name, and they go out and find that name for you).
The root servers are authoritative only, do not allow recursion, and are thusly not affected by this exploit.
While stile quite alpha, the latest snapshot of BIND 9.3.0 (in ftp://ftp.isc.org/isc/bind9/snapshots) does contain _partial_ support for rrset-order (cyclic and random orders).
Probably best not to run it in a production environment, though.
I'd love to get a version of G2 for Solaris, and also IRIX too. However, all they've had to offer is just realplayer v5. How long has the G2 format been out now?
I've posted to Real's site a few times asking for information as to when they're going to release a version for these platforms. Nothing. No reply. Nada.
Now it's been 6+ months since we had this Linux 'alpha' version of G2 - which, I might add, the only way you can find it on Real's site is if you know the exact URL to it. At least, I've not been able to find it any other way.
I find it really really hard to believe that it's possible to have a G2 encoder/server out for multiple platforms, but no decoder/player out, or at least have a player so far back in alpha it's not even funny.
Oh - and get this. The encoders will let you encode G2 for free. If you want to encode for v5, you gotta pay. This, of course, means that you now have more people out there producing streams in G2 format - meaning almost all the UNIX users are just plain screwed.
And yes, this has become a business case where I work too.
I wonder how many folks are getting pleasure from MS inadvertantly giving this kind of recognition to GNU and Open Source. It goes against almost all of what they preach! =)
The latest experience I had trying to fix the NFS problem was with kernel version 2.2.2 on the Linux box, and the Indy is running 6.5.2m. lockd and statd were running okay, but when little things shells don't even start properly, that's sorta problematic.
Perhaps I'll try a later Linux kernel again - though that's sort of a pain due to LILO being dumb about IDE and SCSI drives:P
As for the 5.3 IRIX problems, it could help by using the -32bitclients option on your IRIX NFS server - however, not having more information on your setup, that's only an educated guess (from having seen it before)
I can't give you any performance data, but I can give you an experience of mine with Linux running as an NFS server.
My network was setup originally with an SGI Challenge S box as an NFS server. The client machines were a combination of PCs running Linux or Solaris, and a couple of SGI Indys. With this setup, there was little to no problems with NFS.
However, I moved a whole bunch of stuff over to a Linux server (some home directories) and I got hit with problems on the client side hard.
The Linux clients talk to the Linux NFS server fine, but clients like the Indy take a real dislike to it. Even forcing the Indy to use NFSv2 and trying static mounts over automount/autofs, any process on the Indy that tries to use NFS to the Linux server just hangs.
No matter what I've tried, I can't seem to fix the problem. I've tried the Linux kernel implementation of nfs and the userspace versions. Same problem.
My advice; stick with commercial versions of NFS for the time being, ie those that come with Solaris and IRIX (especially since NFS comes packaged with 6.5:)
Slashdot Mirror
Morpheus believes it is 2199 because he has no idea there were other Matrices before the current one.
Actually, Agent Smith confessed to during Morpheus' interrogation during the first movie that there was at least one prior incarnation of the Matrix - the 'perfect' one, which no-one accepted and they lost 'whole crops' because of it. The Architect confirmed this to Neo also in Reloaded.
Did you look at what is in the tarball at all? Not all of that is required to build the server.
Out of 22Mb
5.0Mb are extra documentation files
5.1Mb is contributed software
2.6Mb is the testing suite
That leaves you with 9.3Mb
It should be noted that this vulnerability only affects BIND 8 servers that perform recursion (ie, the regular nameservers that things like your workstation/laptop/whatever that you ask for a name, and they go out and find that name for you).
The root servers are authoritative only, do not allow recursion, and are thusly not affected by this exploit.
While stile quite alpha, the latest snapshot of BIND 9.3.0 (in ftp://ftp.isc.org/isc/bind9/snapshots) does contain _partial_ support for rrset-order (cyclic and random orders).
Probably best not to run it in a production environment, though.
I'd love to get a version of G2 for Solaris, and also IRIX too. However, all they've had to offer is just realplayer v5. How long has the G2 format been out now?
I've posted to Real's site a few times asking for information as to when they're going to release a version for these platforms. Nothing. No reply. Nada.
Now it's been 6+ months since we had this Linux 'alpha' version of G2 - which, I might add, the only way you can find it on Real's site is if you know the exact URL to it. At least, I've not been able to find it any other way.
I find it really really hard to believe that it's possible to have a G2 encoder/server out for multiple platforms, but no decoder/player out, or at least have a player so far back in alpha it's not even funny.
Oh - and get this. The encoders will let you encode G2 for free. If you want to encode for v5, you gotta pay. This, of course, means that you now have more people out there producing streams in G2 format - meaning almost all the UNIX users are just plain screwed.
And yes, this has become a business case where I work too.
I wonder how many folks are getting pleasure from MS inadvertantly giving this kind of recognition to GNU and Open Source. It goes against almost all of what they preach! =)
Perhaps I'll try a later Linux kernel again - though that's sort of a pain due to LILO being dumb about IDE and SCSI drives :P
As for the 5.3 IRIX problems, it could help by using the -32bitclients option on your IRIX NFS server - however, not having more information on your setup, that's only an educated guess (from having seen it before)
My network was setup originally with an SGI Challenge S box as an NFS server. The client machines were a combination of PCs running Linux or Solaris, and a couple of SGI Indys. With this setup, there was little to no problems with NFS.
However, I moved a whole bunch of stuff over to a Linux server (some home directories) and I got hit with problems on the client side hard.
The Linux clients talk to the Linux NFS server fine, but clients like the Indy take a real dislike to it. Even forcing the Indy to use NFSv2 and trying static mounts over automount/autofs, any process on the Indy that tries to use NFS to the Linux server just hangs.
No matter what I've tried, I can't seem to fix the problem. I've tried the Linux kernel implementation of nfs and the userspace versions. Same problem.
My advice; stick with commercial versions of NFS for the time being, ie those that come with Solaris and IRIX (especially since NFS comes packaged with 6.5 :)