1,135 karma · joined August 1, 2009
That's ironic, you being an American and all.
> the right to arm yourself
This is rich.
- For its excellent backward compatibility: NetBSD 6.1 is still able to run a.out binaries built for NetBSD 1.0
- For its system-independant build system. Building NetBSD needs a POSIX system with a C compiler, which does not need to be NetBSD. It first builds the tools for the host, including the compiler itself, and then the target NetBSD system, which may be for another CPU.
- For its machine-independant drivers. Have a fancy platform with an odd CPU? If NetBSD has a driver for a chip, it will work as is, no need to port it
[From http://bsd.slashdot.org/comments.pl?sid=3764147&cid=4376...]
I mean who would ever say "It's the most exciting thing I've done this year" for a site like this?
Since the release of Django 1.4, version 1.2 stopped receiving security fixes by the Django development team. What that means is that a Debian maintainer (which probably is not a Django developer) would have to hack any new security fix into the unsupported 1.2. And this is deemed more stable than say, upgrading to 1.3.
Note that Django is just an example, obviously there are many more packages with the exact same problem.
They may be able to pull it off with the kernel, but they can't possibly do it for all their packages. As an example: How are the Django backports to 1.2 more stable than upgrading to 1.3 when the official Django project has stopped supporting 1.2?
So, can you give us links to some of your predictions 3 years ago in order to assess your accuracy?
The article argues that we should change this contract.
> The interfaces are fine.
The article argues that they are not.
> Change for change's sake should be avoided.
The article argues that we should change them for performance's sake.
In real life I don't think rainbow tables play any part at all.
No it is not.
chown deploy:deploy /home/deploy -Rf