Then use Tiny instead.
It's *much* better than ZA.
Rules based, logging,
including syslog, password, MD5, etc.
You can run it with ZA
until you have all of your rules set up.
Less overhead than ZA also.
I think people like Rik are a detriment to the progress of the Linux kernel.
Stirring up the pot is A Good Thing.
I've seen way too many occurances of
'we can't change that', even though
the software design (while it works)
is flawed enough that it prevents you
from doing other things. In many
software development environments,
you can't even prove that the changes
are worthwhile. At least with Linux,
if you have the time and smarts, you can.
Not only does this infringe upon copyrights, but it also could spell the end of humankind as we
know it, as they always learn so much from this pirated material.
No, we know it's just brainwashing for the masses.
Besides, the end of humankind as you know it
will be brought about by humankind.
Check out a great philosopher named POGO.
I doubt it.
They did not say *where* in the queue you
would be placed did they?
What could occur is that it mysteriously
goes to a shadow owner (that NSI controls),
and the DN is now renewed, but you have lost
your money for nothing.
The shadow owner likely pays nothing!
That's why they are sitting on the names,
even if they can only churn a very small
percentage of them each year, it will
generate a pile of revenue.
It's really a great scam.
And if we had even a fraction of 6^26 different companies all managing a portion of the
internet name space then it would definately be much more scalable than now.
That number of TLDs with a 6 char limit
would be
26^6 + 26^5 + 26^4 + 26^3 + 26^2 + 26^1
which is certainly plenty.
This would solve the monopoly problem except
that you still need a way to forward P2PDNS
requests to the correct server at some point.
Finding that correct server in true P2P
fashion would require a protocol to distribute
those IPs also. And each resolver would have
to maintain a very large cache.
Certainly workable with what hardware prices
are these days.
The final problem that I've not solved
is this:
What happens when someone creates a TLD of
say 'HOTDNS' and someone else also attempts
to create the same TLD of 'HOTDNS'. In a P2P
arrangement, which one is correct?
It seems to me that ultimately there has to
be one central server to prevent name clashes
within the namespace. So it's kind of back
to where we are, except the possible extortion would
be directed at different parties.
But, I still believe it would greatly help
the current situation.
I grabbing.pr0n BTW.
Your message cannot be verified.
Terrestrials may have forged your message.
If you want earthlings to take you seriously,
you'll need to include your sig and fingerprint next time.
Looking forward to your next message in
42 light-earthyears.
It's not the "corporation" but a lawyer smelling Euro's, who's taking the initiative
Exactly. And perhaps that is the valid
defense. Otherwise, why wouldn't this
scumbag sue other distros or the product creators?
It appears to me
that SuSE did no wrong here as they bundled
a product they did not give the name to.
Recently in Redmond (motto: "You couldn't code your way out of a paper
bag"), residents reported an outbreak of Microsoft Bugs. Perhaps you think
there are no Microsoft Bugs in Redmond. Perhaps you are an idiot.
As the French say, au contraire (literally: "Your software sucks!"). I have here
in my hands a copy of an Associated Press article sent in by alert reader Bill,
whose name can be rearranged to spell "BLIL", although that is not my main
point. "Bill", by the way, only has the letters "ill" in common with "Monica
Lewinsky", so there is no other reason to mention Monica Lewinsky in this
column.
According to a quote which I am not making up, from Redmond Mayor
William (formally "Mayor William" and informally "arsehole"), Microsoft
bugs ranks as a major crisis just behind Stability, Quality and Older hardware
(insert your "Linux" joke here), as evidenced by the following conversation
between Redmond government employees:
FIRST REDMOND EMPLOYEE: "Install that crap yourself"
SECOND REDMOND EMPLOYEE: "Fuckin loser"
FIRST REDMOND EMPLOYEE: "Did you get your computer working
yet?"
Fortunately I have a suggestion for Mayor arsehole, and that is: remove
George Steinbrenner's nic.
No, seriously, my suggestion does not involve George Steinbrenner's nic,
although it might involve using AOL CDs to slice Tobacco Institute scientists.
My suggestion is more along the lines of a coup de grace, from the French
coup, meaning "debugging", and de grace, meaning "kernel code". The
procedure (you may want to write this down):
1.Force AOL to stop mailing CDs
2.Use cat-5 cable
But instead the Redmond city council (motto: "We'll help struggling companies
like Microsoft when you pry the installation manual out of our cold, dead
fingers") thinks that they (the Microsoft bugs) will keep improving with age
soon, sending this message to the public, and to the world: "astroturfing sucks".
Speaking of which, "The Redmond Microsoft Bugs Outbreak" would be a
great name for a rock band.
Ahhh! *You* understand.
6 9's of management(arg), don't,
and their philisophy is that
'QA makes no profit'.
Re:Where the hell is Microsoft's PR agency?
on
al Qaeda Hacks XP?
·
· Score: 1
> > Well the way I figure it, they are paranoid enough that > > someone at MS will try to find out if this
is true or not
> > And they will find that there is no way to tell...
> Yes, but at least they will qualify for 3 or 4 billion dollars of > disaster relief funding, and a play for
sympathy may get them > a reduced wrist slap from the DoJ.
Please, don't you think those terrorists have
gotten enough breaks?
Cannot reproduce. Note this is on
a clean 98se (no patches ever downloaded
from m$ website), version 5.0 of IE.
Either opening or saving still
result in Winzip complaining
about the format (as it should),
since it is saved with a.zip extension.
Slashdot Mirror
Kant tipe writ. we're send>? there.
Then use Tiny instead. It's *much* better than ZA. Rules based, logging,
including syslog, password, MD5, etc.
You can run it with ZA until you have all of your rules set up.
Less overhead than ZA also.
DOJ.
Best page-lengthening post I've seen.
Stirring up the pot is A Good Thing.
I've seen way too many occurances of 'we can't change that', even though the software design (while it works) is flawed enough that it prevents you from doing other things. In many software development environments, you can't even prove that the changes are worthwhile. At least with Linux, if you have the time and smarts, you can.
Keep up the good work Rik!
No, we know it's just brainwashing for the masses.
Besides, the end of humankind as you know it will be brought about by humankind.
Check out a great philosopher named POGO.
I doubt it.
They did not say *where* in the queue you would be placed did they?
What could occur is that it mysteriously goes to a shadow owner (that NSI controls), and the DN is now renewed, but you have lost your money for nothing.
The shadow owner likely pays nothing!
That's why they are sitting on the names, even if they can only churn a very small percentage of them each year, it will generate a pile of revenue.
It's really a great scam.
That number of TLDs with a 6 char limit would be 26^6 + 26^5 + 26^4 + 26^3 + 26^2 + 26^1 which is certainly plenty. .pr0n BTW.
This would solve the monopoly problem except that you still need a way to forward P2PDNS requests to the correct server at some point. Finding that correct server in true P2P fashion would require a protocol to distribute those IPs also. And each resolver would have to maintain a very large cache. Certainly workable with what hardware prices are these days. The final problem that I've not solved is this: What happens when someone creates a TLD of say 'HOTDNS' and someone else also attempts to create the same TLD of 'HOTDNS'. In a P2P arrangement, which one is correct? It seems to me that ultimately there has to be one central server to prevent name clashes within the namespace. So it's kind of back to where we are, except the possible extortion would be directed at different parties. But, I still believe it would greatly help the current situation. I grabbing
That may be fine for you and others, but is that really user-friendly for a clerical type person having to do repetitive maintenance all day long?
Your message cannot be verified.
Terrestrials may have forged your message.
If you want earthlings to take you seriously,
you'll need to include your sig and fingerprint next time.
Looking forward to your next message in 42 light-earthyears.
Exactly. And perhaps that is the valid defense. Otherwise, why wouldn't this scumbag sue other distros or the product creators?
It appears to me that SuSE did no wrong here as they bundled a product they did not give the name to.
Except for Photoshop, your other two points are no longer valid.
As the French say, au contraire (literally: "Your software sucks!"). I have here in my hands a copy of an Associated Press article sent in by alert reader Bill, whose name can be rearranged to spell "BLIL", although that is not my main point. "Bill", by the way, only has the letters "ill" in common with "Monica Lewinsky", so there is no other reason to mention Monica Lewinsky in this column.
According to a quote which I am not making up, from Redmond Mayor William (formally "Mayor William" and informally "arsehole"), Microsoft bugs ranks as a major crisis just behind Stability, Quality and Older hardware (insert your "Linux" joke here), as evidenced by the following conversation between Redmond government employees:
FIRST REDMOND EMPLOYEE: "Install that crap yourself"
SECOND REDMOND EMPLOYEE: "Fuckin loser"
FIRST REDMOND EMPLOYEE: "Did you get your computer working yet?"
Fortunately I have a suggestion for Mayor arsehole, and that is: remove George Steinbrenner's nic.
No, seriously, my suggestion does not involve George Steinbrenner's nic, although it might involve using AOL CDs to slice Tobacco Institute scientists. My suggestion is more along the lines of a coup de grace, from the French coup, meaning "debugging", and de grace, meaning "kernel code". The procedure (you may want to write this down):
1.Force AOL to stop mailing CDs
2.Use cat-5 cable
But instead the Redmond city council (motto: "We'll help struggling companies like Microsoft when you pry the installation manual out of our cold, dead fingers") thinks that they (the Microsoft bugs) will keep improving with age soon, sending this message to the public, and to the world: "astroturfing sucks".
Speaking of which, "The Redmond Microsoft Bugs Outbreak" would be a great name for a rock band.
It's been that way for well over 24 hours.
Kudos dude.
It was a 4, by the time I got here, a 5.
Should be more. Again, great job!
Reverse DNS works for me @24.217.0.3
Either the techs messed up, or they disabled it on purpose.
Must be a slow machine.
Ahhh! *You* understand.
6 9's of management(arg), don't,
and their philisophy is that 'QA makes no profit'.
> > someone at MS will try to find out if this is true or not
> > And they will find that there is no way to tell...
> Yes, but at least they will qualify for 3 or 4 billion dollars of
> disaster relief funding, and a play for sympathy may get them
> a reduced wrist slap from the DoJ.
Please, don't you think those terrorists have gotten enough breaks?
Everyone reads and understands the subscriber agreement
before committing to the contract, right?
You mean the one that they have you sign when the techs are almost done with the installation?
Objection! Assumes facts not in evidence.
Are you sure it's still in beta?
It may have been in place for quite some time now,
and you wouldn't even know it.
This mess gives more weight to the theory that all of these holes in m$ code are strictly intentional.
(with FBI, NSA, CIA blessings of course)
Those of you that use or have used PGP or GPG on windows machines,
I have a question for you:
Are you absolutely positive that your secret passphrase has not *ALREADY* been stolen?
Too lazy to learn something new.
Except that your FUDing is FUDed up.
The WU-FTPD was originally developed at Washington University in St. Louis,
not at the University of Washington.
Either opening or saving still result in Winzip complaining about the format (as it should), since it is saved with a
Try .wav for .zip instead.