To save bandwidth for everyone and improve response times, please don't go to the BBC's high-graphics front page. Go directly to their low-graphics news page.
This way, you not only save bandwidth on the page you want to see, but you avoid wasting bandwidth and server hits on the pages you don't want to see.
Well, after dripping out of college (oops... I meant to type dropping... but it was in Oregon), I went to work in agriculture and then construction.
After plumbing for 2 years, a local network consultant who knew my sister wanted to interview me. I told him I didn't know anything about Windows but had some Linux experience, so he hired me.
Now I'm an admin for several Linux servers around town. Best job I ever had, and I've learned more here than my whole time in college.
Except for yesterday, when I had to install Microsoft FrontPage Extensions on an Apache Server on Linux.... Microsoft doesn't make anything but the most common tasks (i.e., changing your desktop background) easy.
P.S.-- Plumbing is a great motivator to learn something else.
The concept of "national security" is realized when a government's leaders and officials cannot be easily deposed, when the form of government is not easily changed, when the government is not easily overthrown. It comes at the price of individual freedom. Personal security and freedom can only be realized with limited government.
The Constitution of the United States, by design and by intention, organized an insecure form of governent. The beauty of the Constitution is that it gives limited rights to the government and unlimited rights to the people (including, ironically, the right to give up those rights). Sadly, "we the people" have given our government too many liberties while limiting ourselves in the name of "security"! As someone pointed out earlier (to paraphrase), "how many nut cases have gone on killing rampages at gun shows?" Where there is personal security there is individual freedom. Where there is widespread individual freedom AND RESPONSIBILITY, there is no need for an oppressive government. Two hundred twenty five years ago, our forefathers proved this. It worked for a long time.
Not a dead man story, but once I sent an mail to the program director of a radio station (my mail server and theirs was one in the same) and he received it about 3 months later.
That said, they probably don't have an FCC in Nepal to get all stinky about insubstantial stuff like RFI. Besides, these Nepalese would probably find aluminum foil to be much more valuable for uses other than preventing RFI in a few computers. I doubt they have automatic garage door openers, either. Heck, they probably don't even have garages. If they did, you know they wouldn't have their cars parked there. Mother-in-law's gotta sleep somewhere. Maybe I'm being optimistic in thinking they have cars.... things in third world countries don't always make sense to we Americans. Like a village I saw in Guatemala with no running water... but a TV in every house.
Wood cases seems like a pretty cheap way to do it. Only trouble is, wood does not block radio frequency interference very well. (If it did, radios wouldn't work in our houses:-P )
What are the chances of nearby RF causing problems in these computers? Could include anything from data corruption to mysterious system crashes. Another possibility is RF from the computers interfering with other nearby RF devices. ("Why does my garage door go up and down every time I click on 'OK'?")
I guess you could alleviate this with some aluminum foil pasted to the inside of the case, grounded (for you UK'ers, that's "earthed") of course. That would block the electric fields but wouldn't help any magnetic.
Let this be a lesson. A lesson of UI design. No, I don't mean User Interface, I mean User Idiocy.
You should always assume that some idiot is going to plug something in the wrong way or the wrong hole. Your circuitry should be designed to resist failure due to bad connections... reversed polarity, power to the earphone connector, etc.
But then again, that might knock 5 cents out of your profit margin on a $300 piece of equipment.
I have been that idiot before...
~Jon
P.S.-- User Idiocy design should also take into account weird things happening when multiple buttons are pressed. I discovered an undocumented trick for your (most but not all) clock radio: hold the sleep button down and flip the switch or press the alarm-set button. You'll see the seconds display! You can then press the hour & minute buttons to freeze or zero the seconds. Great way to sync your clock!
He failed to mention that duct tape is required for a Stack O'Boxes installation. He assumed that everyone would by default understand this.
For added seismic stability, baling wire can be used as a supplement.
IIRC, I've got a server soewhere that's held together with duct tape... and a roll is always nearby for any emergency. Works great for securing an emergency recovery disk inside the server. Plugs holes in the case for more efficient airflow. Need to tape a cord to a surface? Duct tape all the way.
I myself prefer gaffer's tape to duct tape. Gaffer's is a more expensive version that's more durable, follows contours better, slightly stretchy, and doesn't leave a gummy residue behind when you remove it. As bad. For the gummy residue, you need De-Solv-It.
My uneducated opinion tells me that the reason half of the physical servers are running IIS is because small companies get a NT or 2K server for their business, then realize "hey, it's got IIS, we can have a website..." they accept the default. Of course, their server that's got all of their corporate secrets is now open to the internet.
I'd be willing to guess (but not to wager) that a majority of sites running on IIS are on single-site servers.
Those in the know know that there are other webservers which are more stable than IIS for multi-site hosting. (OK, there are some that are less stable, believe it or not, but they are few and far between.) Having your webserver running on your corporate server is a Bad Thing (tm). Having Exchange on your corporate server and open to the internet is a Bad Thing (tm). Having postfix running on a firewall, forwarding to Exchange is a Better Thing.
P.S. -- the OS irrelevant here, well, except that IIS only runs on M$......
For those/.'ers of a Christian bent, I would like to quote the 20th Psalm (KJV) in hopes of providing comfort and encouragement. For those of other religious persuasions, I hope that you will be able to find comfort and encouragement through your favorite channels.
The LORD hear thee in the day of trouble; the name of the God of Jacob defend thee; Send thee help from the sanctuary, and strengthen thee out of Zion; Remember all thy offerings, and accept thy burnt sacrifice. Grant thee according to thine own heart, and fulfil all thy counsel. We will rejoice in thy salvation, and in the name of our God we will set up our banners: the LORD fulfil all thy petitions. Now know I that the LORD saveth his anointed; he will hear him from his holy heaven with the saving strength of his right hand. Some trust in chariots, and some in horses: but we will remember the name of the LORD our God. They are brought down and fallen: but we are risen, and stand upright. Save, LORD: let the king hear us when we call.
Fly your flag "in the name of our God." It is God who strengthens us out of Zion; it is God who defends us; it is God who sends us help from the sanctuary.
I'm not saying that Linux is research. The point my comment was trying to make was that all of a sudden, there's an OS that, because of its licensing, has the power to remove market share from Microsoft. Therefore, Microsoft must become more innovative and advance the science of desktop operating systems in their favor.
Granted, I don't think Linux was GPL'd for *quite* a while after its release (when was it, anyway?), and it's unknown how soon Microsoft really saw it as a "threat", but I think the timing is interesting.
P.S.-- the most useful technology (IMHO) that's come out of Microsoft is DHCP.
"At one point, Linus had implemented device files in/dev, and wanted to dial up the university computer and debug his terminal emulation code again. So he starts his terminal emulator program and tells it to use/dev/hda. That should have been/dev/ttyS1. Oops. Now his master boot record started with "ATDT" and the university modem pool phone number. I think he implemented permission checking the following day."
I laugh. It's nice to know that I'm not the first one to mess up the mbr. I just wish I had read this before executing this command:
# dd of=/dev/hda if=/dev/fd0
Now, that was *supposed* to back up the MBR to a floppy disk in case it ever got corrupted. Needless to say, "in case" happened and the backup didn't.
I've noticed that some players provide clearer sound than others when playing the same file, so I would think that the same would apply to encoders.
This, of course, depends on the implementation of the algorithm used, whether a reverse-engineered algorithm is used or a native one is used, what kind of error correction is used, and so forth.
As we can see, this is future Reality. 17,100 years from now. SGI has relized the paradox this can create, when we know what will be Reality in the future (we can steer circumstances to modify the future), and they are just tired of rewriting future Reality every time someone goes against The Plan.
I agree that the messages that don't add to debugging shouldn't be there in the first place, but I really don't want to see the "OK" messages disappear.
If I get neither an OK or a FAILED message, then I know that the thingy isn't even attempting to load.
Slashdot Mirror
"...didn't help me any."
:-P
Perhaps this is why I saw it in the bargain bin at my local Waldenbooks last night.
To save bandwidth for everyone and improve response times, please don't go to the BBC's high-graphics front page. Go directly to their low-graphics news page.
This way, you not only save bandwidth on the page you want to see, but you avoid wasting bandwidth and server hits on the pages you don't want to see.
Well, after dripping out of college (oops... I meant to type dropping... but it was in Oregon), I went to work in agriculture and then construction.
After plumbing for 2 years, a local network consultant who knew my sister wanted to interview me. I told him I didn't know anything about Windows but had some Linux experience, so he hired me.
Now I'm an admin for several Linux servers around town. Best job I ever had, and I've learned more here than my whole time in college.
Except for yesterday, when I had to install Microsoft FrontPage Extensions on an Apache Server on Linux.... Microsoft doesn't make anything but the most common tasks (i.e., changing your desktop background) easy.
P.S.-- Plumbing is a great motivator to learn something else.
The concept of "national security" is realized when a government's leaders and officials cannot be easily deposed, when the form of government is not easily changed, when the government is not easily overthrown. It comes at the price of individual freedom. Personal security and freedom can only be realized with limited government.
The Constitution of the United States, by design and by intention, organized an insecure form of governent. The beauty of the Constitution is that it gives limited rights to the government and unlimited rights to the people (including, ironically, the right to give up those rights). Sadly, "we the people" have given our government too many liberties while limiting ourselves in the name of "security"! As someone pointed out earlier (to paraphrase), "how many nut cases have gone on killing rampages at gun shows?" Where there is personal security there is individual freedom. Where there is widespread individual freedom AND RESPONSIBILITY, there is no need for an oppressive government. Two hundred twenty five years ago, our forefathers proved this. It worked for a long time.
A little revolution now and then is a good thing.
Not a dead man story, but once I sent an mail to the program director of a radio station (my mail server and theirs was one in the same) and he received it about 3 months later.
...there was QDOS. This stood for "Quick and Dirty Operating system."
Then, Microsoft bought it, got rid of the "Quick" and kept the "Dirty."
That left us with MS-DOS.
That said, they probably don't have an FCC in Nepal to get all stinky about insubstantial stuff like RFI. Besides, these Nepalese would probably find aluminum foil to be much more valuable for uses other than preventing RFI in a few computers. I doubt they have automatic garage door openers, either. Heck, they probably don't even have garages. If they did, you know they wouldn't have their cars parked there. Mother-in-law's gotta sleep somewhere. Maybe I'm being optimistic in thinking they have cars.... things in third world countries don't always make sense to we Americans. Like a village I saw in Guatemala with no running water... but a TV in every house.
Wood cases seems like a pretty cheap way to do it. Only trouble is, wood does not block radio frequency interference very well. (If it did, radios wouldn't work in our houses :-P )
What are the chances of nearby RF causing problems in these computers? Could include anything from data corruption to mysterious system crashes. Another possibility is RF from the computers interfering with other nearby RF devices. ("Why does my garage door go up and down every time I click on 'OK'?")
I guess you could alleviate this with some aluminum foil pasted to the inside of the case, grounded (for you UK'ers, that's "earthed") of course. That would block the electric fields but wouldn't help any magnetic.
"...new technology that allows Inflatable Loud Speakers..."
:-P
I'm sorry, but this technology has been around for many years. It's called a "whoopee cushion."
Let this be a lesson. A lesson of UI design. No, I don't mean User Interface, I mean User Idiocy.
You should always assume that some idiot is going to plug something in the wrong way or the wrong hole. Your circuitry should be designed to resist failure due to bad connections... reversed polarity, power to the earphone connector, etc.
But then again, that might knock 5 cents out of your profit margin on a $300 piece of equipment.
I have been that idiot before...
~Jon
P.S.-- User Idiocy design should also take into account weird things happening when multiple buttons are pressed. I discovered an undocumented trick for your (most but not all) clock radio: hold the sleep button down and flip the switch or press the alarm-set button. You'll see the seconds display! You can then press the hour & minute buttons to freeze or zero the seconds. Great way to sync your clock!
He failed to mention that duct tape is required for a Stack O'Boxes installation. He assumed that everyone would by default understand this.
For added seismic stability, baling wire can be used as a supplement.
IIRC, I've got a server soewhere that's held together with duct tape... and a roll is always nearby for any emergency. Works great for securing an emergency recovery disk inside the server. Plugs holes in the case for more efficient airflow. Need to tape a cord to a surface? Duct tape all the way.
I myself prefer gaffer's tape to duct tape. Gaffer's is a more expensive version that's more durable, follows contours better, slightly stretchy, and doesn't leave a gummy residue behind when you remove it. As bad. For the gummy residue, you need De-Solv-It.
Does this mean my clone can boot my laptop? Hope it's not my evil twin...
My uneducated opinion tells me that the reason half of the physical servers are running IIS is because small companies get a NT or 2K server for their business, then realize "hey, it's got IIS, we can have a website..." they accept the default. Of course, their server that's got all of their corporate secrets is now open to the internet.
I'd be willing to guess (but not to wager) that a majority of sites running on IIS are on single-site servers.
Those in the know know that there are other webservers which are more stable than IIS for multi-site hosting. (OK, there are some that are less stable, believe it or not, but they are few and far between.) Having your webserver running on your corporate server is a Bad Thing (tm). Having Exchange on your corporate server and open to the internet is a Bad Thing (tm). Having postfix running on a firewall, forwarding to Exchange is a Better Thing.
P.S. -- the OS irrelevant here, well, except that IIS only runs on M$......
Oh, great.
Here we've had cloudless nights for the last 5 months, and now that we've got what promises to be the best aurora all year they forecast... RAIN.
Get outta my storm cloud. Grumble.
Fly your flag "in the name of our God." It is God who strengthens us out of Zion; it is God who defends us; it is God who sends us help from the sanctuary.
--Jon
I'm not saying that Linux is research. The point my comment was trying to make was that all of a sudden, there's an OS that, because of its licensing, has the power to remove market share from Microsoft. Therefore, Microsoft must become more innovative and advance the science of desktop operating systems in their favor.
Granted, I don't think Linux was GPL'd for *quite* a while after its release (when was it, anyway?), and it's unknown how soon Microsoft really saw it as a "threat", but I think the timing is interesting.
P.S.-- the most useful technology (IMHO) that's come out of Microsoft is DHCP.
made me type 0.0 instead of 0.01 -- argh!
Wasn't Linux developed just over 10 years ago?
The earliest datestamp in kernel 0.0 is 15 Jun 1991 at 1:54 pm (memory.h).
No wonder Microsoft decided they needed a research department.
Nah, not yet. Just makes it that much easier for Microsoft to buy 'em later.
To quote:
/dev, and wanted to dial up the university computer and debug his terminal emulation code again. So he starts his terminal emulator program and tells it to use /dev/hda. That should have been /dev/ttyS1. Oops. Now his master boot record started with "ATDT" and the university modem pool phone number. I think he implemented permission checking the following day."
"At one point, Linus had implemented device files in
I laugh. It's nice to know that I'm not the first one to mess up the mbr. I just wish I had read this before executing this command:
# dd of=/dev/hda if=/dev/fd0
Now, that was *supposed* to back up the MBR to a floppy disk in case it ever got corrupted. Needless to say, "in case" happened and the backup didn't.
--Jon
I've noticed that some players provide clearer sound than others when playing the same file, so I would think that the same would apply to encoders.
This, of course, depends on the implementation of the algorithm used, whether a reverse-engineered algorithm is used or a native one is used, what kind of error correction is used, and so forth.
--Jon
So the pillars of society in Atlantis are venting.
What else is new?
Try MilesTek. They've got a good selection of racks in various materials and sizes, including oak.
BTW, audio racks use the same mounting dimensions as computer racks.
From the Stats Page:
"Automaticly Updated on: 07/09/19101 01:43:07"
As we can see, this is future Reality. 17,100 years from now. SGI has relized the paradox this can create, when we know what will be Reality in the future (we can steer circumstances to modify the future), and they are just tired of rewriting future Reality every time someone goes against The Plan.
I agree that the messages that don't add to debugging shouldn't be there in the first place, but I really don't want to see the "OK" messages disappear.
If I get neither an OK or a FAILED message, then I know that the thingy isn't even attempting to load.