This is true. My mail server (hosted on my cable modem) has no MX record, just an A record. And it works just fine. I checked the RFC. MX is NOT required at all.
Don't you get it? The robots do ALL of the work, even repair the robots. People need to do nothing, the robots build their houses, mine the materials, grow and prepare the food... People don't NEED to work. That will be the future. Everyone on welfare except for the scientists and engineers who advance robotics and science.
Want to know why they canceled it? It was manned. All of the new government research contracts are going into unmanned craft. In our lifetime, the US will be fighting wars with NO US casualties. The computing power and communiication ability is finally here, the robotics hardware has been around for a long time. The first vehicles of the kind are already in place. A robot with good cammeras, microphones and a robotic arm and rifle would make a better infantry than a person. It can stand tall while shooting instead of having to hid behind cover and fear for it's live, and it can talk and give commands to civillians--perhaps even translating on-the-fly. Best of all, it doesn't ever surrender. That will intimidate the enemies. Our current tanks are controlled almost entirely electronically. They don't look out of hatches, they look at TV screens. If you ran wires out the back, or used radio, it could be controlled as effectively and be smaller, faster, cheaper. Our aircraft are already becoming entirely remotely controlled. The footsoldier I described to you above will only be the last piece in the puzzle.
And think of all the great civilian product spinnoffs from an entirely-robotic army...
You are only 22. Go back to school and get a degree in engineering if you can't find work. And you sound very skilled, UML is one of the tools taught in 'software engineering' courses at universities, an Engineer is a little more than that. An engineer is an "educated person" not just a skilled one. They have a BS. An engineer has had classes in mechanical, industrial, materials science, and electrical engineering in addition to his specific field. This allows him to work better on engineering teams because he understands some of what they do. A computer engineer doesn't just know how to write software, but knows how the computer itself works. He has had the physics and EE to be able to build simple computers from gates or transistors. An engineer has had courses on things such as the engineering code of ethics. An engineer has done a metric shitload of math to get his degree. Writing software doesn't use multivariable calculus, but being able to do it shows you are a very intelligent person. An engineer was has shown he is able to survive 4 or 5 years of intensive university study. A person can be highly skilled in a specific thing and still not be an engineer. Other professions don't stand for people who didn't run the gauntlet claim the titles for themselves (imagine: I never went to medical school but I'm a Physician anyway, I never had a college-level physics course but I'm a mechanical engineer!). Computer/Software engineers should not put up with it either.
You call yourself an engineer but you never went to college? I'm sure you know how to program, but do other branches of engineering (Civil, Mechanical, Electrical, etc.) call people who don't have a BS in Engineering, "engineers"? That would kind of dilute the field to have engineers that never studied engineering, physics, math, etc calling themselves engineers. It's a lot more than coding.
This article is about magnetic fields. Your CRT shoots electrons at a screen which then emits light. While moving electrons do produce a magnetic field, it is a very weak one: can you stick a metal screw to the side of your monitor and have it stick? But you could stick it to the magnet in the electric motor of your razor.
"Wouldn't this only be a problem if you use these devices every day directly in contact with your skull? I mean, is the range really that far reaching?"
Actually, the magnitude of a magnetic field drops away as the square of the distance from the source. So the answer to your question is, it depends on how strong the field is.
How can India have such a clearly identifiable Caste system while having a Communist government? Shouldn't the government be distributing the wealth among the population? Or else it isn't really Communism...
If you use the stable version of debian, you have old software and an old kernel. On gentoo, you have the latest version of everything as well as the 2.6 kernel and devfs and all of that. This means more hardware support. Get it? Old kernel and old software == less hardware support. And don't tell me I should be running the unstable or testing versionf of Debian. I want my system to be stable. If you consider the testing version to be stable, they should name their versions better.
Gentoo on 5 year old hardware? Gentoo is for the most cutting-edge computers! You compile everything. X, KDE, glibc, and you dont want to have to wait. Use debian on your old hardware (since it really only supports old hardware anyway) and gentoo on your 3GHz AMD chip.
Nothing in the entire course of human history is as important as space colinization. The humanity-destroying meteor or plage could be coming right now. If we don't establish bases on other celestial bodies now, while we have the chance, humanity itself is doomed.
Crackers are people who crack copy protection. Hackers get machines to do something other than what they are intended. That usually means giving other than intended access, because that is what is most interestig. Sorry.
The Apache web server will automatically zip files or directories and send them to you if you ask for the download with a.tgz. I am not sure if this feature is turned on by default, though. Should get you around having to get a.exe if you find a server that does it.
This was posted to USENET by its author, Ed Nather, on May 21, 1983.
A recent article devoted to the *macho* side of programming made the bald and unvarnished statement:
Real Programmers write in FORTRAN.
Maybe they do now, in this decadent era of Lite beer, hand calculators, and "user-friendly" software but back in the Good Old Days, when the term "software" sounded funny and Real Computers were made out of drums and vacuum tubes, Real Programmers wrote in machine code. Not FORTRAN. Not RATFOR. Not, even, assembly language. Machine Code. Raw, unadorned, inscrutable hexadecimal numbers.
Lest a whole new generation of programmers grow up in ignorance of this glorious past, I feel duty-bound to describe, as best I can through the generation gap, how a Real Programmer wrote code. I'll call him Mel, because that was his name.
I first met Mel when I went to work for Royal McBee Computer Corp., a now-defunct subsidiary of the typewriter company. The firm manufactured the LGP-30, a small, cheap (by the standards of the day) drum-memory computer, and had just started to manufacture the RPC-4000, a much-improved, bigger, better, faster --- drum-memory computer. Cores cost too much, and weren't here to stay, anyway. (That's why you haven't heard of the company, or the computer.)
I had been hired to write a FORTRAN compiler Mel didn't approve of compilers.
"If a program can't rewrite its own code", he asked, "what good is it?"
Mel had written, in hexadecimal, the most popular computer program the company owned. It ran on the LGP-30 and played blackjack with potential customers at computer shows. Its effect was always dramatic. The LGP-30 booth was packed at every show, and the IBM salesmen stood around talking to each other. Whether or not this actually sold computers was a question we never discussed.
Mel's job was to re-write the blackjack program for the RPC-4000. (Port? What does that mean?) The new computer had a one-plus-one addressing scheme, in which each machine instruction, in addition to the operation code and the address of the needed operand, had a second address that indicated where, on the revolving drum, the next instruction was located.
In modern parlance, every single instruction was followed by a GO TO! Put *that* in Pascal's pipe and smoke it.
Mel loved the RPC-4000 because he could optimize his code: that is, locate instructions on the drum so that just as one finished its job, the next would be just arriving at the "read head" and available for immediate execution. There was a program to do that job, an "optimizing assembler", but Mel refused to use it.
"You never know where it's going to put things", he explained, "so you'd have to use separate constants". It was a long time before I understood that remark. Since Mel knew the numerical value of every operation code, and assigned his own drum addresses, every instruction he wrote could also be considered a numerical constant. He could pick up an earlier "add" instruction, say, and multiply by it, if it had the right numeric value. His code was not easy for someone else to modify.
I compared Mel's hand-optimized programs with the same code massaged by the optimizing assembler program, and Mel's always ran faster. That was because the "top-down" method of program design hadn't been invented yet, and Mel wouldn't have used it anyway. He wrote the innermost parts of his program loops first, so they would get first choice of the optimum address locations on the drum.
http://www.microsoft.com/windowsserver2003/64bit/e xtended/trial/default.mspx
Interesting things from that page:
"Windows Server 2003, Enterprise Edition, for 64-Bit Extended Systems is only compatible with 64-bit AMD Opteron-based systems. It cannot be successfully installed on 64-bit Intel Itanium-based systems."
"On the download page, you will see a link to the Setup file and a Product Key for the software you wish to install. The file will be in ISO format and must be burned to a CD before you can install the software on your computer."
"* More security flaws than any other distro [To parent: Really? Please provide links to back that up, I'm interested]"
Actually, I think the reason people think Debian has the most security flaws, is that if you run a Nessus scan against it, it comes up with a shitload of holes. The reason for this is that nessus relies on banners to determine version numbers, and version numbers to determine vulnerabilities. Debian backports security fixes, so though it says it has Apache version 1.3.4, it really isn't 1.3.4 because it has security fixes from 2.0.55 or whatever. This makes auditing a pain in the ass, and I hate debian's policy of backporting instead of upgrading, but Debian is just as secure as anything else, because of backporting.
None of the people I know who 'smoke joints' seem to be benifiting from its intellect-enhancing powers. In fact, it's quit the opposite. But hey, how needs to graduate?
"Turn the other cheek" is not a good reason to not disclipine your child. By humiliating her, he probably taught her a lesson she won't forget, and will probably save her from a worse experience later on.
Slashdot Mirror
This is true. My mail server (hosted on my cable modem) has no MX record, just an A record. And it works just fine. I checked the RFC. MX is NOT required at all.
Don't you get it? The robots do ALL of the work, even repair the robots. People need to do nothing, the robots build their houses, mine the materials, grow and prepare the food... People don't NEED to work. That will be the future. Everyone on welfare except for the scientists and engineers who advance robotics and science.
Want to know why they canceled it? It was manned. All of the new government research contracts are going into unmanned craft. In our lifetime, the US will be fighting wars with NO US casualties. The computing power and communiication ability is finally here, the robotics hardware has been around for a long time. The first vehicles of the kind are already in place. A robot with good cammeras, microphones and a robotic arm and rifle would make a better infantry than a person. It can stand tall while shooting instead of having to hid behind cover and fear for it's live, and it can talk and give commands to civillians--perhaps even translating on-the-fly. Best of all, it doesn't ever surrender. That will intimidate the enemies.
Our current tanks are controlled almost entirely electronically. They don't look out of hatches, they look at TV screens. If you ran wires out the back, or used radio, it could be controlled as effectively and be smaller, faster, cheaper. Our aircraft are already becoming entirely remotely controlled. The footsoldier I described to you above will only be the last piece in the puzzle.
And think of all the great civilian product spinnoffs from an entirely-robotic army...
You are only 22. Go back to school and get a degree in engineering if you can't find work. And you sound very skilled, UML is one of the tools taught in 'software engineering' courses at universities, an Engineer is a little more than that. An engineer is an "educated person" not just a skilled one. They have a BS. An engineer has had classes in mechanical, industrial, materials science, and electrical engineering in addition to his specific field. This allows him to work better on engineering teams because he understands some of what they do. A computer engineer doesn't just know how to write software, but knows how the computer itself works. He has had the physics and EE to be able to build simple computers from gates or transistors. An engineer has had courses on things such as the engineering code of ethics. An engineer has done a metric shitload of math to get his degree. Writing software doesn't use multivariable calculus, but being able to do it shows you are a very intelligent person. An engineer was has shown he is able to survive 4 or 5 years of intensive university study. A person can be highly skilled in a specific thing and still not be an engineer. Other professions don't stand for people who didn't run the gauntlet claim the titles for themselves (imagine: I never went to medical school but I'm a Physician anyway, I never had a college-level physics course but I'm a mechanical engineer!). Computer/Software engineers should not put up with it either.
You call yourself an engineer but you never went to college? I'm sure you know how to program, but do other branches of engineering (Civil, Mechanical, Electrical, etc.) call people who don't have a BS in Engineering, "engineers"? That would kind of dilute the field to have engineers that never studied engineering, physics, math, etc calling themselves engineers. It's a lot more than coding.
How do you make a clown stop smiling? Hit him in the face with an axe.
Girls with hair of other colors don't use hairdryers?
This article is about magnetic fields. Your CRT shoots electrons at a screen which then emits light. While moving electrons do produce a magnetic field, it is a very weak one: can you stick a metal screw to the side of your monitor and have it stick? But you could stick it to the magnet in the electric motor of your razor.
"Wouldn't this only be a problem if you use these devices every day directly in contact with your skull? I mean, is the range really that far reaching?"
Actually, the magnitude of a magnetic field drops away as the square of the distance from the source. So the answer to your question is, it depends on how strong the field is.
How can India have such a clearly identifiable Caste system while having a Communist government? Shouldn't the government be distributing the wealth among the population? Or else it isn't really Communism...
If you use the stable version of debian, you have old software and an old kernel. On gentoo, you have the latest version of everything as well as the 2.6 kernel and devfs and all of that. This means more hardware support. Get it? Old kernel and old software == less hardware support. And don't tell me I should be running the unstable or testing versionf of Debian. I want my system to be stable. If you consider the testing version to be stable, they should name their versions better.
Gentoo on 5 year old hardware? Gentoo is for the most cutting-edge computers! You compile everything. X, KDE, glibc, and you dont want to have to wait. Use debian on your old hardware (since it really only supports old hardware anyway) and gentoo on your 3GHz AMD chip.
Nothing in the entire course of human history is as important as space colinization. The humanity-destroying meteor or plage could be coming right now. If we don't establish bases on other celestial bodies now, while we have the chance, humanity itself is doomed.
Crackers are people who crack copy protection. Hackers get machines to do something other than what they are intended. That usually means giving other than intended access, because that is what is most interestig. Sorry.
Try this: http://whatever/downloads/mozilla.exe.tgz
.tgz. I am not sure if this feature is turned on by default, though. Should get you around having to get a .exe if you find a server that does it.
The Apache web server will automatically zip files or directories and send them to you if you ask for the download with a
This was posted to USENET by its author, Ed Nather, on May 21, 1983.
A recent article devoted to the *macho* side of programming
made the bald and unvarnished statement:
Real Programmers write in FORTRAN.
Maybe they do now,
in this decadent era of
Lite beer, hand calculators, and "user-friendly" software
but back in the Good Old Days,
when the term "software" sounded funny
and Real Computers were made out of drums and vacuum tubes,
Real Programmers wrote in machine code.
Not FORTRAN. Not RATFOR. Not, even, assembly language.
Machine Code.
Raw, unadorned, inscrutable hexadecimal numbers.
Lest a whole new generation of programmers
grow up in ignorance of this glorious past,
I feel duty-bound to describe,
as best I can through the generation gap,
how a Real Programmer wrote code.
I'll call him Mel,
because that was his name.
I first met Mel when I went to work for Royal McBee Computer Corp.,
a now-defunct subsidiary of the typewriter company.
The firm manufactured the LGP-30,
a small, cheap (by the standards of the day)
drum-memory computer,
and had just started to manufacture
the RPC-4000, a much-improved,
bigger, better, faster --- drum-memory computer.
Cores cost too much,
and weren't here to stay, anyway.
(That's why you haven't heard of the company, or the computer.)
I had been hired to write a FORTRAN compiler
Mel didn't approve of compilers.
"If a program can't rewrite its own code",
he asked, "what good is it?"
Mel had written,
in hexadecimal,
the most popular computer program the company owned.
It ran on the LGP-30
and played blackjack with potential customers
at computer shows.
Its effect was always dramatic.
The LGP-30 booth was packed at every show,
and the IBM salesmen stood around
talking to each other.
Whether or not this actually sold computers
was a question we never discussed.
Mel's job was to re-write
the blackjack program for the RPC-4000.
(Port? What does that mean?)
The new computer had a one-plus-one
addressing scheme,
in which each machine instruction,
in addition to the operation code
and the address of the needed operand,
had a second address that indicated where, on the revolving drum,
the next instruction was located.
In modern parlance,
every single instruction was followed by a GO TO!
Put *that* in Pascal's pipe and smoke it.
Mel loved the RPC-4000
because he could optimize his code:
that is, locate instructions on the drum
so that just as one finished its job,
the next would be just arriving at the "read head"
and available for immediate execution.
There was a program to do that job,
an "optimizing assembler",
but Mel refused to use it.
"You never know where it's going to put things",
he explained, "so you'd have to use separate constants".
It was a long time before I understood that remark.
Since Mel knew the numerical value
of every operation code,
and assigned his own drum addresses,
every instruction he wrote could also be considered
a numerical constant.
He could pick up an earlier "add" instruction, say,
and multiply by it,
if it had the right numeric value.
His code was not easy for someone else to modify.
I compared Mel's hand-optimized programs
with the same code massaged by the optimizing assembler program,
and Mel's always ran faster.
That was because the "top-down" method of program design
hadn't been invented yet,
and Mel wouldn't have used it anyway.
He wrote the innermost parts of his program loops first,
so they would get first choice
of the optimum address locations on the drum.
The same sort of thing happened with barcodes, but they came here eventually. It is inevitable.
http://www.microsoft.com/windowsserver2003/64bit/e xtended/trial/default.mspx
Interesting things from that page:
"Windows Server 2003, Enterprise Edition, for 64-Bit Extended Systems is only compatible with 64-bit AMD Opteron-based systems. It cannot be successfully installed on 64-bit Intel Itanium-based systems."
"On the download page, you will see a link to the Setup file and a Product Key for the software you wish to install. The file will be in ISO format and must be burned to a CD before you can install the software on your computer."
"* More security flaws than any other distro
[To parent: Really? Please provide links to back that up, I'm interested]"
Actually, I think the reason people think Debian has the most security flaws, is that if you run a Nessus scan against it, it comes up with a shitload of holes. The reason for this is that nessus relies on banners to determine version numbers, and version numbers to determine vulnerabilities. Debian backports security fixes, so though it says it has Apache version 1.3.4, it really isn't 1.3.4 because it has security fixes from 2.0.55 or whatever. This makes auditing a pain in the ass, and I hate debian's policy of backporting instead of upgrading, but Debian is just as secure as anything else, because of backporting.
That's a good point.
No, if you are trying gto do something evil, the best way to hide the true intent of your code is to do it in Perl.
None of the people I know who 'smoke joints' seem to be benifiting from its intellect-enhancing powers. In fact, it's quit the opposite. But hey, how needs to graduate?
Yes, but does it come with a decoder ring?
"Turn the other cheek" is not a good reason to not disclipine your child. By humiliating her, he probably taught her a lesson she won't forget, and will probably save her from a worse experience later on.
I caution you, Sir, not to dis the D.