I don't think it had anything to do with LCD screens. If that were the case, then DVD/video playback would suck... which it doesn't.
No, I think it was more of a general OS/network issue. From my own experience, Mozilla seemed a lot 'snappier' on a Windows box than it did on my TiBook... but I still prefer my TiBook for general use.;)
Does this include modifications to various syscalls? Last time I tried porting something to Linux, I was dismayed to find that off_t (used in stat(2), lseek(2), etc.) was only 32-bits on x86 platforms.
It doesn't seem very useful to have a 64-bit filesystem if your applications are limited to 32-bit operations.
What!?!? What happens when you bind, say, sshd to port 22 on multiple servers? Do you also need multiple ethernet cards and ip addresses? The docs don't say anything about that...
It sounds like you will need multiple IP addresses, but I'd think you could use IP aliases on a single interface just fine.
I must be missing something here. It can't be this simple. Can anyone point out where I've gone wrong?
I haven't actually looked at the implementation, but I would think that they'd restrict the creation of vservers to root. That is, the real root of the host server. root users of vservers would not and should not be able to create more vservers.
The old benchmark is here, but as the poster above noted, the new benchmark is forthcoming.
Although it will be comparing a moving target (Linux 2.4.x) to a moving target (FreeBSD 4.x), the results will be interesting. AFAIK, there weren't any major changes (I mean like VM changes:) in FreeBSD, so comparing the old and new benchmarks would give a good indication on how much Arcangeli's VM improves things.
Is it truly better? I would think forking would lead to stagnation.
As it is, the Linus/AC trees are effectively forks because of the different VM codebases. Any new drivers, any new code would have to be ported from one tree to the other (assuming you want the same features on both trees).
Seems like a lot more unnecessary work to me.
I believe it's the latter: "do with it as you please, but leave the copyright" (doesn't necessarily have to be in the source though).
If BSD licensed code were used in a closed source project, the copyright acknowledgement would still have to exist somewhere (documentation, etc.) because of this clause:
Redistributions in binary form must reproduce the above copyright notice,
this list of conditions and the following disclaimer in the documentation
and/or other materials provided with the distribution.
A typical BSD license can be found here. It seems fairly self-explanitory and clear.
Slashdot Mirror
Three words. Apple Remote Desktop.
You're probably thinking about theta, which looks very similar to zero.
No, I think it was more of a general OS/network issue. From my own experience, Mozilla seemed a lot 'snappier' on a Windows box than it did on my TiBook... but I still prefer my TiBook for general use. ;)
For $129, Jaguar better be faster.
debug1: authentications that can continue: publickey,password,keyboard-interactive
The presence of keyboard-interactive would seem to imply that ChallengeResponseAuthentication is on.
But if you notice the update at the end of the article, the Open Group later decided to include Apple as a UNIX vendor.
Regardless, it shows last-minute straight-thinking on the pilot's part. The fire on the ground could have been much worse.
It doesn't seem very useful to have a 64-bit filesystem if your applications are limited to 32-bit operations.
It sounds like you will need multiple IP addresses, but I'd think you could use IP aliases on a single interface just fine.
I haven't actually looked at the implementation, but I would think that they'd restrict the creation of vservers to root. That is, the real root of the host server. root users of vservers would not and should not be able to create more vservers.
Although it will be comparing a moving target (Linux 2.4.x) to a moving target (FreeBSD 4.x), the results will be interesting. AFAIK, there weren't any major changes (I mean like VM changes :) in FreeBSD, so comparing the old and new benchmarks would give a good indication on how much Arcangeli's VM improves things.
As it is, the Linus/AC trees are effectively forks because of the different VM codebases. Any new drivers, any new code would have to be ported from one tree to the other (assuming you want the same features on both trees). Seems like a lot more unnecessary work to me.
If BSD licensed code were used in a closed source project, the copyright acknowledgement would still have to exist somewhere (documentation, etc.) because of this clause:
A typical BSD license can be found here. It seems fairly self-explanitory and clear.