They haven't got much choice. SCO is suing them for slander of title, so Novell either continue, or admit liability and pay up punative damages for the "slander".
cePuller was written for two reasons. First, because the terms of
the free BitKeeper license are not suitable for some members of the
free software community. This can occasionally lead to frustrating
situations where a free software developer wishes to access a
BitKeeper repository, and is either unable to, or can only access it
via a gateway that translates the repository into another format,
possibly losing some information.
The second reason for writing SourcePuller was to provide a open
library of routines that can talk to BitKeeper servers and manipulate
local BitKeeper repositories. It is hoped that this library will be
used by the authors of other source code management systems to allow
them to interoperate with BitKeeper. Eventually this should result in
an improvement in the quality of the various bk repository gateways.
SourcePuller is not intended to be a full replacement for
BitKeeper. Instead, you should use SourcePuller as an interoperability
tool for situations where you cannot use bk itself. SourcePuller is
missing a large amount of core functionality from BitKeeper, and thus
is not suitable as a full replacement.
Update - April 2005
-------------------
As you probably know, there has been quite a fuss lately about this
code and the fact that BitMover has now withdrawn the free version of
bk. First off, I would like to say that this result was not the
intention when I wrote this code. I had hoped that an alternative open
client would be able to coexist happily with the proprietary
BitKeeeper client, as has happened with so many other protocols. An
open client combined with the ability to accurately import into other
source code management tools would have been a big step forward, and
should have allowed BitMover to flourish in the commercial environment
while still being used by the free software community.
I would also like to say that BitMover is well within its rights to
license BitKeeper as it sees fit. I am of course disappointed at how
BitMover has portrayed some of my actions, but please understand that
they are under a lot of pressure. Under stress people sometimes say
things that perhaps they shouldn't.
As I have stated previously, my code was written without using
bk. Some people expressed some skepticism over that, perhaps because
they haven't noticed that bk servers have online protocol help (just
type 'help' into a telnet session). I don't think it is unreasonable
to assume that this help was intended for people like myself who
wished to implement new clients.
I would like to thank all the people who have supported me in the
development of this tool by providing useful advice both before,
during and after the development of the code. I tried to consult with
a wide range of interested parties and the feedback I got was
certainly appreciated.
Finally, I would like to point out the obvious fact that Linus was
perfectly within his rights to choose bk for the kernel. I personally
would not have chosen it, but it was his choice to make, not anyone
elses. Linus is now in the unenviable position of changing source code
management systems, which is a painful task, particularly when moving
away from a system that worked as well as bk did. If you want to help,
then help with code not commentary. There have been enough flames over
this issue already.
This is just a government conspiracy to bypass tin-foil hats! Everyone knows that it's the 2% lead content which actually blocks the mind-control rays....
They fail to mention that NeXT was the company
set up by Steve Jobs after he left apple, with the mission to produce a next-generation Mac-like
workstation with an OS called NeXTstep, based on mach, BSD and display Postscript
It's a universal mantra of any company involved in litigation. "We are unable to comment due to ongoing litigation"
Yes, and it's interesting to note how IBM have been totally
silent as regards public comments in the SCO case.
And how the IBM legal team have been
using Darl's public comments as evidence against
SCO:-)
Re:don't tell us what it is then...
on
OQO For Sale
·
· Score: 1
Here's an idea: If you want to find out what something is, do a little reading. If you don't have enough time to do that, it's not important enough for you to know. If it's not important enough for you to know, it's not important enough to bitch about. It's that simple.
Now there's a thought. We could dispense
with the the titles and summaries on the slashdot
home page, and just have a collection of anonymous links instead.
don't tell us what it is then...
on
OQO For Sale
·
· Score: 4, Insightful
Why do I have to follow a &%$@ link just to
find out even the vaguest idea of what the article
is about...?
lack of editing mutter mutter not like that in my day mutter mutter youth of today mutter mutter...
Aren't "frequent" flyers the ones we care the least about? I mean, if you are dead from hijacking a plane, you typically
don't go on many more flights.
A well-funded terrorist will fly the route several
times. A middle-eastern looking gentlemen who
turns up in a suit doing the same journey he's
been doing every 14 days for the last few
months is likely to get waved through.
("Here for your meeting again, Mr Bin Laden? Have a good flight!")
The idea that "matter" interacts with the ambient space-temporal background is preposterous at best.
Granted, GR is extremely elegant in its ways, but it can hardly be called a theory of gravity.
Well, as a theory it's done remarkably well at explaining existing phenomena and predicting
new phenomena (eg gravitational bending of light).
Stop wasting time on those silly calculations: Gravitational waves do not exist.
The whole point of those silly calculations is
to determine whether gravitational waves
exist.
If you rewrite the sender envelope address you break
error returning - which is why in the presence of SPF all MTAs capable of forwarding now have to maintain a 5-day cache
of all sender address rewritings.
And in my original example, how is small.biz supposed to get AOL to add small.biz's MTA to the list of valid sender IPs - just on the off-chance that one day an AOL user may send an email to small.biz that gets forwarded?
I dislike SPF because it breaks forwarding. There
is a "workaround" but that's required on every
MTA in the world that allows forwarding, and
is intensely ugly - it requires adding a bunch
of garbage to the sender address, and also requires the MTA to main a cache of forwarded addresses so that bounces can be passed back down the chain.
The problem is this. Suppose AOL start adding SPF
records to their DNS, saying effectively 'only the
following IP addresses are authorized to send @aol.com emails. Suppose also that Hotmail start rejecting emails from SPF domains where the IP addresses don't match. Now suppose that joe@small.biz is going to be away from the office for a couple of weeks, so he gets the small.biz mail server to forward his emails to his hotmail account. At this point anyone from AOL who emails
him will find the emails bouncing (although if they're
from AOL, this may not be such a bad thing...)
Slashdot Mirror
Dave.Mitchell@uk.ac.shef.dcs
Then wait for the FBI to pay you a visit...
The Dewey Decimal system is copyright and trademarked by OCLC and they have been known to threaten people with legal action. I kid you not...
Please look up satire in a dictionary...
They haven't got much choice. SCO is suing them for slander of title, so Novell either continue, or admit liability and pay up punative damages for the "slander".
No, Saturn is currently on the opposite side of the sun from us, so we are not between them.
cePuller was written for two reasons. First, because the terms of the free BitKeeper license are not suitable for some members of the free software community. This can occasionally lead to frustrating situations where a free software developer wishes to access a BitKeeper repository, and is either unable to, or can only access it via a gateway that translates the repository into another format, possibly losing some information.
The second reason for writing SourcePuller was to provide a open library of routines that can talk to BitKeeper servers and manipulate local BitKeeper repositories. It is hoped that this library will be used by the authors of other source code management systems to allow them to interoperate with BitKeeper. Eventually this should result in an improvement in the quality of the various bk repository gateways.
SourcePuller is not intended to be a full replacement for BitKeeper. Instead, you should use SourcePuller as an interoperability tool for situations where you cannot use bk itself. SourcePuller is missing a large amount of core functionality from BitKeeper, and thus is not suitable as a full replacement.
Update - April 2005
-------------------
As you probably know, there has been quite a fuss lately about this code and the fact that BitMover has now withdrawn the free version of bk. First off, I would like to say that this result was not the intention when I wrote this code. I had hoped that an alternative open client would be able to coexist happily with the proprietary BitKeeeper client, as has happened with so many other protocols. An open client combined with the ability to accurately import into other source code management tools would have been a big step forward, and should have allowed BitMover to flourish in the commercial environment while still being used by the free software community.
I would also like to say that BitMover is well within its rights to license BitKeeper as it sees fit. I am of course disappointed at how BitMover has portrayed some of my actions, but please understand that they are under a lot of pressure. Under stress people sometimes say things that perhaps they shouldn't.
As I have stated previously, my code was written without using bk. Some people expressed some skepticism over that, perhaps because they haven't noticed that bk servers have online protocol help (just type 'help' into a telnet session). I don't think it is unreasonable to assume that this help was intended for people like myself who wished to implement new clients.
I would like to thank all the people who have supported me in the development of this tool by providing useful advice both before, during and after the development of the code. I tried to consult with a wide range of interested parties and the feedback I got was certainly appreciated.
Finally, I would like to point out the obvious fact that Linus was perfectly within his rights to choose bk for the kernel. I personally would not have chosen it, but it was his choice to make, not anyone elses. Linus is now in the unenviable position of changing source code management systems, which is a painful task, particularly when moving away from a system that worked as well as bk did. If you want to help, then help with code not commentary. There have been enough flames over this issue already.
It takes years to manufacture and grind large mirrors to the accuracy required.
This is just a government conspiracy to bypass tin-foil hats! Everyone knows that it's the 2% lead content which actually blocks the mind-control rays....
They fail to mention that NeXT was the company set up by Steve Jobs after he left apple, with the mission to produce a next-generation Mac-like workstation with an OS called NeXTstep, based on mach, BSD and display Postscript
But I thought AL Gore invented the Internet? I hope he sues Microsoft.
I'm sure the NSA already has copies of all emails ever written, so the British Library just needs to ask them nicely....
Yes, and it's interesting to note how IBM have been totally silent as regards public comments in the SCO case. And how the IBM legal team have been using Darl's public comments as evidence against SCO :-)
Now there's a thought. We could dispense with the the titles and summaries on the slashdot home page, and just have a collection of anonymous links instead.
lack of editing mutter mutter not like that in my day mutter mutter youth of today mutter mutter ...
The data sheet included in the press release gives 16msec for LCD, 0.01msec for OLED. That's 1600 x more responsive by my calculation.
Darl.
So we've lost the Daleks but gained Billy Piper. I think I can live with that ....
In Perl 6, most of the cryptic punctuation variables are going away.
And in my original example, how is small.biz supposed to get AOL to add small.biz's MTA to the list of valid sender IPs - just on the off-chance that one day an AOL user may send an email to small.biz that gets forwarded?
The problem is this. Suppose AOL start adding SPF records to their DNS, saying effectively 'only the following IP addresses are authorized to send @aol.com emails. Suppose also that Hotmail start rejecting emails from SPF domains where the IP addresses don't match. Now suppose that joe@small.biz is going to be away from the office for a couple of weeks, so he gets the small.biz mail server to forward his emails to his hotmail account. At this point anyone from AOL who emails him will find the emails bouncing (although if they're from AOL, this may not be such a bad thing...)