Parent post is NOT offtopic.
Parent post has a valid point, and that is
that SABRE was around long before this sleazeball
attempted prior extortion.
Parent post however may be incorrect in the comparison
between said sleazeball and/. moderators.
You would not want to share it with me!
You would *ONLY* want to share it with me
so that I could write code to *interoperate*
with you. Microsoft does NOT want
anyone else to interoperate with them.
This is nothing more than an attempt to
dirty others, to taint you or your company.
Once tainted, you can be driven out of business.
Let's say you have some code that does 'Z'.
Let's also say that you have been tainted
by signing a Microsoft NDA regarding 'Y'.
Later, Microsoft comes around and says that
you violated the NDA by implementing 'X'
in your 'Z' and they say that you learned
about 'X' because you reviewed some of their
(Microsofts) documentation about 'Y'.
They (Microsoft) say that concept 'X' was
implemented in 'Y' and you stole it ('X').
Whether their accusation is accurate or not
is not the point, you are potentially screwed
over by Microsoft lawyers. They can make your
like hell just because they feel like it.
It is extremely important that the protocols
be made 'publicly available'. That means that
anyone and everyone should be able to review
them just as an RFC can be reviewed. Otherwise,
those that privately review the protocol
specifications are tainted (by the NDA). Once you are tainted by Microsoft, you essentially could be prevented from working on any GPL project ever. Even if any GPL code you write has nothing to do
with whatever Microsoft documentation you reviewed
under a NDA, Microsoft with their money could
make your life hell. Bottom line, don't
get in bed with Microsoft this way. Even if
you don't work on GPL code now, you may want to
in the future.
Would anyone really miss that?
I guess I wouldn't know since everytime
I search at Google, I never see anything
from Microsoft. Must be that one keyword I
always use.
You know how some people have to talk with their hands. Which begs the questions:
What would be acceptable packet loss rate?
What about being a router? Can males do more?
I've been up on 2.5.40 for over 8 hours now,
without any problems. Of course I'm not
loading it badly, just Mozilla and doing some
additional kernel compiles.
But, it definitely appears stable enough to
do some testing without worrying about trashing
your system.
I'm not reading it because I don't like
the layout much, and it has more than I'm
normally interested in reading.
This does not mean that I wouldn't use it
for particular stories of interest.
I agree. If upper management fails to
clean up the situation quickly, start
looking elsewhere. Having been in tbe
same situation for many years, I wish I
had bailed out earlier. In addition,
consider the market your sales folks are
selling to. Is that market in bad shape?
If so, it explains their behaviour.
Slashdot Mirror
Parent post is NOT offtopic. /. moderators.
Parent post has a valid point, and that is that SABRE was around long before this sleazeball attempted prior extortion.
Parent post however may be incorrect in the comparison between said sleazeball and
License for Security-Enhanced Linux
Plain and simple, you are brainwashed.
Don't feel bad, 90+% of the American public is in the same situation.
Of course not. That requires cache.
\n, meet \r
Greed.
This is nothing more than an attempt to dirty others, to taint you or your company.
Once tainted, you can be driven out of business.
Whether their accusation is accurate or not is not the point, you are potentially screwed over by Microsoft lawyers. They can make your like hell just because they feel like it.
It is extremely important that the protocols be made 'publicly available'. That means that anyone and everyone should be able to review them just as an RFC can be reviewed. Otherwise, those that privately review the protocol specifications are tainted (by the NDA). Once you are tainted by Microsoft, you essentially could be prevented from working on any GPL project ever. Even if any GPL code you write has nothing to do with whatever Microsoft documentation you reviewed under a NDA, Microsoft with their money could make your life hell. Bottom line, don't get in bed with Microsoft this way. Even if you don't work on GPL code now, you may want to in the future.
Would anyone really miss that?
I guess I wouldn't know since everytime I search at Google, I never see anything from Microsoft.
Must be that one keyword I always use.
New pickup line: Oh baby, let me be your firewall tonight!
You know how some people have to talk with their hands.
Which begs the questions:
What would be acceptable packet loss rate?
What about being a router? Can males do more?
Or in this case, what is not thought.
Totally agree. Dont' forget to fetch beer before reaching couch.
But, it definitely appears stable enough to do some testing without worrying about trashing your system.
Yes. Chunks would be a better description.
That in itself tells me that it should be 2.6.x in order to encourage usage and growth.
And if they do (fork the code and/or ignore GPL), it may be like trying to eat with only one.
Or just a nasty bug that was waiting to be discovered?
I'm not reading it because I don't like the layout much, and it has more than I'm normally interested in reading.
This does not mean that I wouldn't use it for particular stories of interest.
I agree. If upper management fails to clean up the situation quickly, start looking elsewhere. Having been in tbe same situation for many years, I wish I had bailed out earlier. In addition, consider the market your sales folks are selling to. Is that market in bad shape? If so, it explains their behaviour.
that eventually all computers will only need 640K of ram?
Your scenario also explains why there is so much un-lit fiber.
Are the penguins sexy?
What percentage of the warez was Microsoft?