In a digital format, a duplication can be made such that it is indistinguishable from the original.
That means that you need to have access to that digital information, and with properly engineered smartcards there is no way to access the memory directly. You'll need some serious cleanroom stuff, while physically damaging the card beyond repair. I think you can be quite convinced your smartcard will be tamperproof.
What is'nt tamperproof are two things:
The terminal that is being used to read the smartcards. (Hack one of those, and you can have it display anything, no matter what's on the card) - the current meatspace equivalent would be bribery.
If there is also data stored centrally by the government that gave you the smartcard (to make sure noone can create their own cards if they know the protocol the smartcard/terminal uses) to identify that you're using a real ID card - e.g: every smartcard has a private key, public key is stored centrally - checking a card's validity involves having the card digitally signing a challenge and subsequently checking the challenge with the public key. These servers are probably a far easier target.
You can get pretty paranoid about these things, but IMHO smartcards are quite safe when you are trying to extract data from them. They can be easily destroyed, or overwritten - but that's no big deal: you just get a new one.
Okay... I'll do the stupid things first, then you shy people follow.
This document describes the business method on creating a knowledgeable management team in a corporation using Darwinian processses: 'Survival of the less stupid'.
Process Flow:
- Manager A is faced with issue for which he is responsible.
- Knowledgeable employee B is under direct management of manager A.
- Manager A tells knowledgeable employee B to offer multiple options on resolving issue.
- Knowledgeable employee B works out one perfect solution (option 1), and two stupid alternatives (options 2 and 3), presents them to manager A.
- Manager A picks a solution
option 1) Good solution -> company does well. Re-iterate process.
option 2 or 3) Stupid solution -> company does bad. Fire manager A, promote dumb employee C to management level, re-iterate.
Continuous iteration of this process will eventually lead to managers picking only option 1, which results in a company that IPO's bigtime -> knowledgeable employee B gets loaded with stock-options. Okay... I'll do the stupid things first, then you shy people follow.
If you really want to be looking at the sun with a telescope, there are a number of ways:
Use a filter on top of the lens, which filters the sunlight before it gets into the telescope.
Use your telescope as a projector, and project an image of the sun onto a piece of paper , cardboard, whatever...
But never ever rely on a filter that's put on the eyepiece: due to the high temperatures caused by the focused sunlight in the eyepiece and the fact that a dark filter absorbs all the light == energy == heat, it can crack easily - and once that happens when you're looking through it, you can kiss your retina goodbye.
Okay... I'll do the stupid things first, then you shy people follow.
They are not asking your money up front. They are asking your advice on how to fund a book they are writing on Linux TCP/IP internals. God forbid they earn something with it. You're indeed not obliged to pay for it, and nothing in the posting says you should.
Okay... I'll do the stupid things first, then you shy people follow.
Who's keeping you from doing just that? But that doesn't mean that the people who are putting expensive time in the effort should be doing that for free.
Puh-leeze don't whine that they don't give their work out for free: they are writers, they write for a living. If you have a problem with this: fine, go somewhere else. There are a number of people who are working on Free Software/Open Source while being paid for that, and someone writing documentation shouldn't be treated any different.
If they think they can sell a good-written book about Linux TCP/IP internals, it's their choice to try just that. And you and me and everybody else can choose if they would like to pay for that. Some of us will, others won't. But you should really cut the 'do it for the love of it'-crap.
Okay... I'll do the stupid things first, then you shy people follow.
Books are obsolete. Save the trees. The information is antiquated before you get it.
All good points, but when I'm doing something for which I need more than a glance at the documentation, there is nothing that beats having a good book on your desk. I can see how good a book of mine is by merely looking at it... The more it is thumbed through, the more post-it notes sticking out: all omens of its qualities...
The information in the book is not obsolote (2.4 TCP/IP Stack - not 2.0.34, that was the first edition!), and I can imagine that having a book on that topic would really be interesting.
Perhaps it's me, but for more than a couple of screenfuls, I prefer something on paper.
Okay... I'll do the stupid things first, then you shy people follow.
"I like the followup saying we should also switch to VA Linux servers. That's a nice idea, but which product can we use to replace our 28 cpu systems with 28 GB of memory?"
What about something like this? And if that's not big enough, try the RS/6000 SP...
Or you might try going with Compaq/Alpha, who also have some pretty decent machines that can scale up to 32 CPUs in a box and even more for the SC series.
Okay... I'll do the stupid things first, then you shy people follow.
The highest penetration degrees in Europe are in Scandinavia, with Finland on top. I can remember something about being more cellular phones sold over there than there are Finns to use them:-)
The quality of the landlines down here is pretty good: most of them are connected to digital switches, and ISDN is widely available. The time to obtain a new line is in most countries no longer than a couple of days.
The big difference is that in the US local calls are flat-fee, which doesn't make it interesting for the telcos. They earn their money with long-distance and subscription. Over here, there is no such thing as a flat fee for local calls, which makes the pricing structure of GSM subscriptions very much like an ordinary phone connection. In the States, people rather stick to their flat-fee landline than having to use a cellular, on which local calls aren't included in the subscription fee.
Over here in Europe, telephone is simply much more expensive than in the US of A, which is a bad thing (less beer), and a good thing (better beers;-).
Please do not accept that wireless is exploding due to 'necessity' when you're talking about most of Europe, and countries as Japan. Here in Belgium we have the reputation of being the most densely cabled country of the world, and yet cellular phone adoption rate is over 50%.
Okay... I'll do the stupid things first, then you shy people follow.
Didn't really spring to mind that there are actually people outside the US of A who really have evolved far enough to be capable of using computers and surfin' the net? Even in a barbaric region that don't have daily runs of the Simpsons et al. Puh'leeze... we're out here;p
Okay... I'll do the stupid things first, then you shy people follow.
An RDBMS is a program that lets you create, update, and administer a relational database. An RDBMS takes Structured Query Language (SQL) statements entered by a user or contained in an application program and creates, updates, or provides access to the database. Some of the best-known RDBMS's include Microsoft's Access, Oracle's Oracle7, and Computer Associates' CA-OpenIngres.
MySQL (notice the capital M) lets you create, update and administer a relational database through SQL statements. According to both your references, it is a full RDBMS.
You are probably referencing ACIDity, which can be achieved with a transaction logging RDBMS, and which is a completely different beast. Either you just experienced a brainfart after a long caffeine driven coding session, or you should have studied a bit harder.
Okay... I'll do the stupid things first, then you shy people follow.
... I'd still be praising the person that invented the goto statement:-)
Seriously: I've been coding from when I was 11 years old, and throughout school the biggest change in my coding style came with switching from BASIC to Turbo Pascal. Besides having procedures and functions, nothing really changed in getting the things to work. When we started using scheme in CS, a whole new world opened up: for the first time in years, I put more time in algorithms than I did in code.
It's too bad that - in spite of the beauty of the code - there really aren't that much applications of scheme and the likes. Without scheme, I would have probably missed the point of OO completely.
Okay... I'll do the stupid things first, then you shy people follow.
Believe me, I know what the advantages are of commercial-grade RDBMS systems, I've been around the beasts long enough. And I do appreciate that PostgreSQL/MySQL don't have what it takes in a lot of applications, even when commercial DBMSes have price tag that can make a grown man cry.
The point of the original poster was pretty simple: there are a lot of applications out there that don't need a RDBMS with a gazillion features out there. I suppose the guestbook example was a wee bit simple, but that's definitely not everything. Look here for a great example of a bit more complex application;-) It could be called 'wrong' to just use PostgreSQL/MySQL because they're open sourced ( although that could be marked as -1 Flamebait;-) when the features of the DBMS don't fit with your needs.
All I'm saying is that you really don't need a complete state-of-the-art toolbox with a lot of toys when a simple hammer will do. And they'll do just fine in a lot of cases anyway.
Okay... I'll do the stupid things first, then you shy people follow.
There is a huge crowd out there that uses databases and that don't need _any_ feature of the big commercial databases to get the job done.
If I want to code a guestbook for a small website, create an on-line shop for the fanclub our obscure little rockband, I don't need all the extras of a commercial RDBMS. Last time I worked with oracle, the actual cost of getting the oracle licenses in place was completely insane. But that cost was justified, because we needed our app to be entreprise-ready (but God knows it'll be DB2 next time such a project comes along:p ) - But you can't expect me to be happy to pay big $$$ if I don't need that stuff.
You missed the point, no more, no less:-) (nothing personal intenden;-)
Okay... I'll do the stupid things first, then you shy people follow.
Same thing happens IRL in a number of stores, with IKEA being a prime example: Once you get in, you can't possibly get out unless you walk through the *whole* store, through every possible department - preferrably with hordes of people blocking your way.
It's a tested idea, and it works wonders (in Ikea, anyway) for the sheople walking through. Quite miraculous how I always seem to end up buying more stuff than I actually came for.:-)
Okay... I'll do the stupid things first, then you shy people follow.
if the law were changed so that only an INDIVIDUAL could own a patent - as well as be granted one - most of the parasitic and bad consequences of the patent system would disappear.
The problem with your statement is that afaik almost all inventions (the high-tech ones, anyway), are not solely the credit of an individual, but of research teams funded by companies.
Okay... I'll do the stupid things first, then you shy people follow.
For those who don't do assembler, here's some pseudocode:
A = A XOR B// store A XOR B in A /* The value of A XOR B is stored in A */
B = B XOR A// store B XOR (A XOR B) in B /* B XOR (A XOR B) = B XOR B XOR A = 0 XOR A = A The original value of A is now stored in B */
A = A XOR B// store (A XOR B) XOR (B XOR (A XOR B)) in A /* (A XOR B) XOR (B XOR (A XOR B)) = A XOR B XOR B XOR A XOR B = A XOR 0 XOR A XOR B = A XOR A XOR B = 0 XOR B = B Store the original value of B in A */
Okay... I'll do the stupid things first, then you shy people follow.
My guess there is simply that this cluster will be used for sims with gazillions of floating point numbers, waiting happily to be crunched. The alpha CPU runs circles around any 'cheaper' (read: x86) CPU while doing just that.
There are some chips that are even faster than the alpha (HP has some nice CPUs), but in relation to x86 the Alpha nodes aren't that much more expensive... Not unlike HP-RISC chips, which probably cost a multitude of the Alphas.
Another reason could be that the academic users use the alpha a lot to do number crunching, which would be of help in the availability of optimised libs. Not forgetting the Compaq tools and math libraries, which simply rock. -- Okay... I'll do the stupid things first, then you shy people follow.
In fact: they're even cheaper. Check out Cheap Bytes.
Red Hat and a whole other bunch of companies are not aiming at getting paid for the software (which is open source, and thus free), but they do want to get paid for the support and consulting. This model is being adapted at a lot of companies nowadays... IBM for example, has decided to drop their own webserver development in favor of Apache, because it is far more worthwile selling consultancy and support services and putting resources in that, than it is to invest a lot of money in developing their own webserver, while there is something as apache as the alternative.
Services will become the next cash cow, not software. -- Okay... I'll do the stupid things first, then you shy people follow.
Re:Sounds kind of limited to me
on
IP Over SCSI?
·
· Score: 1
Latency.
In a clustered environment, latency is one of the most important factors in getting the performance cranked up, especially when under load. Bandwidth is not really that important, but getting the message across the wire asap is something else. That's why myrinet solutions are being used - not just bandwith, but ultra-low latency.
Okay... I'll do the stupid things first, then you shy people follow.
11. I'm from {Europe,Asia,Africa,Australia,somewhere else} and I'm silently smiling with all those silly Americans.
The US is *not* the centre of this planet, which is actually some 6000+ kilometres beneath your feet.
<FLAMEBAIT> It is amazing how some people are saying that the internet is global and should therefore not be regulated, while otherwise they're still trapped in the good-old "We're-the-centre-of-the-universe" vision. </FLAMEBAIT>
Perhaps it's time to add a 'US-centric stories' checkbox to the slashdot config page;-)
Okay... I'll do the stupid things first, then you shy people follow.
Dutch with grammar errors and some nonsense words.. It actually means: "IMHO Metallica are a bunch of stupid lame monkeys, on the same level as a phlubby gnome of trepaan" whatever the last words may mean.
Okay... I'll do the stupid things first, then you shy people follow.
In slackware 7.0, you've introduced SysV-compatible initscripts/directories, to keep slackware compatible with various installers that assume a SysV structure.
One of the things about slackware that IMHO simply rocks are the BSD-style init scripts, and I would like te know what you're up to in the future. Will slackware evolve to SysV to become the next RH/SuSe/... lookalike, or will we slack-fans be able to happily hack away at our BSD-style initscripts for the rest of times?
Keep up the good work
Okay... I'll do the stupid things first, then you shy people follow.
HTML may be OK for displaying on-screen, it really sucks bigtime for anything that has to be printed out.
For most computer related books, I'd rather have a kilogram of paper sitting right next to me on my desk, than having to read it from the screen. If I look at the books I use a lot -e.g. the bat book- which very much shows it's being (ab)used many times, I simply turn green by the thought that I would only have them on-screen or in HTML format. The single most important part of these books are the indices and TOCs, and printing an HTML file simply doesn't cut it.
Electronically distributed books are very much a pro, but I really want them in a format which makes it easy to print them (sorry, trees;-) and PS or PDF are two formats which accomplish that. There are plenty of tools available that can deal with these two formats.
Okay... I'll do the stupid things first, then you shy people follow.
Slashdot Mirror
What is'nt tamperproof are two things:
The terminal that is being used to read the smartcards. (Hack one of those, and you can have it display anything, no matter what's on the card) - the current meatspace equivalent would be bribery.
If there is also data stored centrally by the government that gave you the smartcard (to make sure noone can create their own cards if they know the protocol the smartcard/terminal uses) to identify that you're using a real ID card - e.g: every smartcard has a private key, public key is stored centrally - checking a card's validity involves having the card digitally signing a challenge and subsequently checking the challenge with the public key. These servers are probably a far easier target.
You can get pretty paranoid about these things, but IMHO smartcards are quite safe when you are trying to extract data from them. They can be easily destroyed, or overwritten - but that's no big deal: you just get a new one.
Okay... I'll do the stupid things first, then you shy people follow.
This document describes the business method on creating a knowledgeable management team in a corporation using Darwinian processses: 'Survival of the less stupid'.
Process Flow:
- Manager A is faced with issue for which he is responsible.
- Knowledgeable employee B is under direct management of manager A.
- Manager A tells knowledgeable employee B to offer multiple options on resolving issue.
- Knowledgeable employee B works out one perfect solution (option 1), and two stupid alternatives (options 2 and 3), presents them to manager A.
- Manager A picks a solution
option 1) Good solution -> company does well. Re-iterate process.
option 2 or 3) Stupid solution -> company does bad. Fire manager A, promote dumb employee C to management level, re-iterate.
Continuous iteration of this process will eventually lead to managers picking only option 1, which results in a company that IPO's bigtime -> knowledgeable employee B gets loaded with stock-options.
Okay... I'll do the stupid things first, then you shy people follow.
Use a filter on top of the lens, which filters the sunlight before it gets into the telescope.
Use your telescope as a projector, and project an image of the sun onto a piece of paper , cardboard, whatever...
But never ever rely on a filter that's put on the eyepiece: due to the high temperatures caused by the focused sunlight in the eyepiece and the fact that a dark filter absorbs all the light == energy == heat, it can crack easily - and once that happens when you're looking through it, you can kiss your retina goodbye.
Okay... I'll do the stupid things first, then you shy people follow.
They are not asking your money up front. They are asking your advice on how to fund a book they are writing on Linux TCP/IP internals. God forbid they earn something with it. You're indeed not obliged to pay for it, and nothing in the posting says you should.
Okay... I'll do the stupid things first, then you shy people follow.
Puh-leeze don't whine that they don't give their work out for free: they are writers, they write for a living. If you have a problem with this: fine, go somewhere else. There are a number of people who are working on Free Software/Open Source while being paid for that, and someone writing documentation shouldn't be treated any different.
If they think they can sell a good-written book about Linux TCP/IP internals, it's their choice to try just that. And you and me and everybody else can choose if they would like to pay for that. Some of us will, others won't. But you should really cut the 'do it for the love of it'-crap.
Okay... I'll do the stupid things first, then you shy people follow.
All good points, but when I'm doing something for which I need more than a glance at the documentation, there is nothing that beats having a good book on your desk. I can see how good a book of mine is by merely looking at it... The more it is thumbed through, the more post-it notes sticking out: all omens of its qualities...
The information in the book is not obsolote (2.4 TCP/IP Stack - not 2.0.34, that was the first edition!), and I can imagine that having a book on that topic would really be interesting.
Perhaps it's me, but for more than a couple of screenfuls, I prefer something on paper.
Okay... I'll do the stupid things first, then you shy people follow.
It is probably floating around in a lot of zappa quote databases like this one.
Okay... I'll do the stupid things first, then you shy people follow.
What about something like this? And if that's not big enough, try the RS/6000 SP...
Or you might try going with Compaq/Alpha, who also have some pretty decent machines that can scale up to 32 CPUs in a box and even more for the SC series.
Okay... I'll do the stupid things first, then you shy people follow.
The quality of the landlines down here is pretty good: most of them are connected to digital switches, and ISDN is widely available. The time to obtain a new line is in most countries no longer than a couple of days.
The big difference is that in the US local calls are flat-fee, which doesn't make it interesting for the telcos. They earn their money with long-distance and subscription. Over here, there is no such thing as a flat fee for local calls, which makes the pricing structure of GSM subscriptions very much like an ordinary phone connection.
In the States, people rather stick to their flat-fee landline than having to use a cellular, on which local calls aren't included in the subscription fee.
Over here in Europe, telephone is simply much more expensive than in the US of A, which is a bad thing (less beer), and a good thing (better beers ;-).
Please do not accept that wireless is exploding due to 'necessity' when you're talking about most of Europe, and countries as Japan. Here in Belgium we have the reputation of being the most densely cabled country of the world, and yet cellular phone adoption rate is over 50%.
Okay... I'll do the stupid things first, then you shy people follow.
Puh'leeze... we're out here
Okay... I'll do the stupid things first, then you shy people follow.
MySQL (notice the capital M) lets you create, update and administer a relational database through SQL statements. According to both your references, it is a full RDBMS.
You are probably referencing ACIDity, which can be achieved with a transaction logging RDBMS, and which is a completely different beast.
Either you just experienced a brainfart after a long caffeine driven coding session, or you should have studied a bit harder.
Okay... I'll do the stupid things first, then you shy people follow.
Seriously: I've been coding from when I was 11 years old, and throughout school the biggest change in my coding style came with switching from BASIC to Turbo Pascal. Besides having procedures and functions, nothing really changed in getting the things to work.
When we started using scheme in CS, a whole new world opened up: for the first time in years, I put more time in algorithms than I did in code.
It's too bad that - in spite of the beauty of the code - there really aren't that much applications of scheme and the likes. Without scheme, I would have probably missed the point of OO completely.
Okay... I'll do the stupid things first, then you shy people follow.
The point of the original poster was pretty simple: there are a lot of applications out there that don't need a RDBMS with a gazillion features out there. I suppose the guestbook example was a wee bit simple, but that's definitely not everything. Look here for a great example of a bit more complex application ;-) ;-) when the features of the DBMS don't fit with your needs.
It could be called 'wrong' to just use PostgreSQL/MySQL because they're open sourced ( although that could be marked as -1 Flamebait
All I'm saying is that you really don't need a complete state-of-the-art toolbox with a lot of toys when a simple hammer will do. And they'll do just fine in a lot of cases anyway.
Okay... I'll do the stupid things first, then you shy people follow.
If I want to code a guestbook for a small website, create an on-line shop for the fanclub our obscure little rockband, I don't need all the extras of a commercial RDBMS. :p ) - But you can't expect me to be happy to pay big $$$ if I don't need that stuff.
Last time I worked with oracle, the actual cost of getting the oracle licenses in place was completely insane. But that cost was justified, because we needed our app to be entreprise-ready (but God knows it'll be DB2 next time such a project comes along
You missed the point, no more, no less :-) (nothing personal intenden ;-)
Okay... I'll do the stupid things first, then you shy people follow.
Once you get in, you can't possibly get out unless you walk through the *whole* store, through every possible department - preferrably with hordes of people blocking your way.
It's a tested idea, and it works wonders (in Ikea, anyway) for the sheople walking through. :-)
Quite miraculous how I always seem to end up buying more stuff than I actually came for.
Okay... I'll do the stupid things first, then you shy people follow.
The problem with your statement is that afaik almost all inventions (the high-tech ones, anyway), are not solely the credit of an individual, but of research teams funded by companies.
Okay... I'll do the stupid things first, then you shy people follow.
A number of scoring techniques could be:
letter frequency - the more it matches to the frequency table of the original language, the better the score.
letter group frequencies - same as above, but with groups of two letters.
the occurance X between identical characters - read the playfair cypher explanation.
a dictionary of common words in the original language.
I would really like to know more about how the original poster based his scoring system.
Okay... I'll do the stupid things first, then you shy people follow.
A = A XOR B // store A XOR B in A
/* The value of A XOR B is stored in A */
B = B XOR A // store B XOR (A XOR B) in B
/* B XOR (A XOR B) = B XOR B XOR A = 0 XOR A = A
The original value of A is now stored in B */
A = A XOR B // store (A XOR B) XOR (B XOR (A XOR B)) in A
/* (A XOR B) XOR (B XOR (A XOR B)) =
A XOR B XOR B XOR A XOR B =
A XOR 0 XOR A XOR B =
A XOR A XOR B =
0 XOR B = B
Store the original value of B in A
*/
Okay... I'll do the stupid things first, then you shy people follow.
The alpha CPU runs circles around any 'cheaper' (read: x86) CPU while doing just that.
There are some chips that are even faster than the alpha (HP has some nice CPUs), but in relation to x86 the Alpha nodes aren't that much more expensive... Not unlike HP-RISC chips, which probably cost a multitude of the Alphas.
Another reason could be that the academic users use the alpha a lot to do number crunching, which would be of help in the availability of optimised libs. Not forgetting the Compaq tools and math libraries, which simply rock.
--
Okay... I'll do the stupid things first, then you shy people follow.
Red Hat and a whole other bunch of companies are not aiming at getting paid for the software (which is open source, and thus free), but they do want to get paid for the support and consulting. This model is being adapted at a lot of companies nowadays...
IBM for example, has decided to drop their own webserver development in favor of Apache, because it is far more worthwile selling consultancy and support services and putting resources in that, than it is to invest a lot of money in developing their own webserver, while there is something as apache as the alternative.
Services will become the next cash cow, not software.
--
Okay... I'll do the stupid things first, then you shy people follow.
In a clustered environment, latency is one of the most important factors in getting the performance cranked up, especially when under load.
Bandwidth is not really that important, but getting the message across the wire asap is something else. That's why myrinet solutions are being used - not just bandwith, but ultra-low latency.
Okay... I'll do the stupid things first, then you shy people follow.
The US is *not* the centre of this planet, which is actually some 6000+ kilometres beneath your feet.
<FLAMEBAIT>
It is amazing how some people are saying that the internet is global and should therefore not be regulated, while otherwise they're still trapped in the good-old "We're-the-centre-of-the-universe" vision.
</FLAMEBAIT>
Perhaps it's time to add a 'US-centric stories' checkbox to the slashdot config page ;-)
Okay... I'll do the stupid things first, then you shy people follow.
It actually means: "IMHO Metallica are a bunch of stupid lame monkeys, on the same level as a phlubby gnome of trepaan" whatever the last words may mean.
Okay... I'll do the stupid things first, then you shy people follow.
One of the things about slackware that IMHO simply rocks are the BSD-style init scripts, and I would like te know what you're up to in the future. Will slackware evolve to SysV to become the next RH/SuSe/... lookalike, or will we slack-fans be able to happily hack away at our BSD-style initscripts for the rest of times?
Keep up the good work
Okay... I'll do the stupid things first, then you shy people follow.
For most computer related books, I'd rather have a kilogram of paper sitting right next to me on my desk, than having to read it from the screen. If I look at the books I use a lot -e.g. the bat book- which very much shows it's being (ab)used many times, I simply turn green by the thought that I would only have them on-screen or in HTML format. The single most important part of these books are the indices and TOCs, and printing an HTML file simply doesn't cut it.
Electronically distributed books are very much a pro, but I really want them in a format which makes it easy to print them (sorry, trees ;-) and PS or PDF are two formats which accomplish that. There are plenty of tools available that can deal with these two formats.
Okay... I'll do the stupid things first, then you shy people follow.