If this is a feeble attempt at Engrish, it's the Japanese, not the Chinese, that tend to pronounce English 'L's as 'R's.
I'd make fun of you for confusing Chinese and Japanese like a typical American, but I didn't score so good on the test at http://www.alllooksame.com/, so I won't. Let me watch a few more Chinese Kung Fu and Japanese Samurai movies and we'll see how I do then.
"Did you know that all traffic that touches California state road, inclusing bicycles, is subject to an annual state inspection?... Registration, tags, and even insurance are required. "
Hmm. Pretty crazy if true. I thought the law only regulated motor vehicles with 50cc or larger engines.
Oh, wait, you said California? Well! That explains it. Nevermind.
Uh... I've never heard that. And have never seen a helmetless bicyclist ticketed. In my state you can ride a MOTORCYCLE without a helmet, so bicycle helmet laws would seem a bit silly.
Anyway, this story is old news. I saw it a day or two ago. I think it was on Fark?
"It's a matter of emulating the x86 instructions within...Windows..., not supporting a whole OS on an 'emulated machine' as VMWare and VirtualPC do."
Yeah you're right. I've been working heavily with VMWare recently and it jaded my thinking. Of course, the method you mention requires porting the entire Windows API to another platform, which is results in a lot of code and a LOT of labor and debugging. The VMWare installer, on the other hand, weighs in at a mere 36MB (which includes a lot of documentation). And I think MS's VPC installer is about 12MB (compressed).
"suppose MS might soften that blow by bundling an integrated version of VirtualPC to run x86 software"
Not going to work. Products like VMware and VirtualPC do not emulate a CPU, they only provide timeslices of (or some other technique of sharing) the real, underlying CPU. This is for performance reasons, and even still, they lose about 20% to overhead.
The upshot of this is that, when running on non-x86 CPU, VMW/VPC cannot host an x86 OS.
For example, if you run VMWare on an Intel P4, the guest OS sees an Intel P4 CPU.
The Mac solution to running x86 stuff must emulate the whole x86 CPU, and as a result is incredibly ssslllooowww. Incidentally, this is where Transmeta's code-morphing chips were supposed to save the world. Too bad nobody's ever seemed to pursue the idea outside of the laboratory.
All you guys who used to run Netscape on old hardware... hah. I *currently* run Mozilla on my Slackware 10 P133 with 32MB of RAM! Startup is a little slow but once everything except Mozilla swaps out to disk, it's not too bad for googling stuff. Uh, don't try to multitask though.
I also use it on a P90 laptop with 40MB of RAM, and it actually runs faster there. That extra 8MB must make all the difference.
This problem is a poorly designed breather hose that allows blowby gasses from the crankcase to be sucked into the intake and burned. On a gasoline car they use a PCV (Positive Crankcase Ventilation) valve. In both cases it's there to reduce emissions.
In the case of the Rabbit, though, VW foolishly put the hose intake right over a cam lobe. This allows oil to be splashed up into the hose and into the intake manifold. There it pools up until there's a puddle big enough to start getting sucked into the engine... uh-oh.
The runaway problem is easily solved. Go to any VW dealer or foreign auto parts place and buy a $10 plastic oil baffle. This fits over the camshaft and prevents oil from getting flipped into the breather tube by the cam lobe... no more oil in the intake, no more runaways. On later models, like mine, you'll see that the valve cover has an integrated baffle. I installed the second baffle anyway -- cheap insurance.
"the steering column hitting the driver is a common cause of death"
I call bull. Cite some references please. If it's so "common", there should be thousands of cases.
All cars since the 70s and maybe earlier have had collapsible or telescoping steering columns to prevent this problem.
Just to clarify some of your post -- in Fuel Injection systems (at least in 80s and 90s VWs), you do not control the amount of fuel going into the engine. That pedal on the right is for air. There is Mass Airflow Sensor that senses how much air is going through the throttle body, and then the system meters out the fuel required for a stochiometric (sp) fuel-air mixture.
So stomping on the accelerator can't dump too much fuel into the engine (on a FI car). You only get fuel in proportion to airflow, and the amount of airflow is determined by engine RPM. You control the engine RPM with the throttle.
No wonder you car acts weird when things are out of whack!
Filling your uplink by sending large amounts of data makes it hard for the TCP ACKs of your downloads to come back. Without TCP ACKs, your download halts until it gets them, which just kills download performance.
There are Linux iptables firewall rules to throttle bandwidth a tiny bit and give the ACKs priority. With something like this, you can upload at 255Kbps on a 256Kbps uplink and see no hit in download performance. If you ask me, this is something that should be built into DSL/Cable modems.
You can also give higher priority to game traffic and assign other protocols a lower priority to make sure online games aren't impacted by p2p apps.
I feel your pain. OpenLDAP and the other products may compare at the user-level, but for administration, OpenLDAP just sucks. I have yet to find a good administration tool for it. Maybe one is hiding out there or is being developed as I speak.
Novell sucks because there are some things you can do only in NWAdmin, others you can do only in ConsoleOne. Dumb. That's from Netware 5.1 and 6.0 though, maybe their newer stuff has improved.
Lotus Domino's admin software sucks because everything is buried under 17 layers and if you click the wrong 'X' in the interface, you lose all 17 layers and have to start over. I hate Domino.
iPlanet/SunOne's GUI interface isn't too bad but seems to be really slow, even on a 2GHz server with very few users(?). For advanced config options, you sometimes have to resort to editing a text file (albeit still within the admin GUI), which is one weak point.
AD seems to have got it right with the ADUC and other MMC snap-ins, although if you get in and start messing around with permissions and GPOs you'd better know exactly what the heck you are doing because it's real easy to change things in ways you never expected (or in other words, break AD). The only drawback is, you don't have much low-level control over LDAP attributes and things -- you're just kind of stuck with 'the Microsoft Way' of doing things.
In short, there is no perfect solution. I favor OpenLDAP just because it's OSS but the installation (from source) and the learning curve are both unpleasant. If you're a clueless MCSE-type and just want a quick LDAP directory, I'm afraid AD is the least painful route... if you don't mind clicking a soul-sucking EULA and bleeding ridiculous licensing fees to the Evil Empire.
That's pretty cool. How do you script 3rd party app installs? Is there a common InstallShield interface, or do you have to design a solution for each piece of software?
You can't add PhotoShop to an image and then download that image to 200 PCs if you only have 10 licenses. Even if, somehow, you got 190 of the users to promise not to use it.
... and when each of your users requires a different piece of software to do their job, and you don't have licensing to make all that software a part of the image, your users are going to have to reinstall stuff every time.
Ok, I retract my earlier statements. Re-imaging CAN work SOMETIMES in certain situations.:)
Ghosting kinda works for servers, assuming you have saved a new image each and every time your or the dba or whatever makes a configuration change on the server. Otherwise, you restore from image only to find that your app is broken because there are a half-dozen settings that were made after the backup, that now need to be re-done. And the dba didn't document them. This is easier with Linux because you can just back up the config files, but in Windows this is a real PITA.
In addition, finding 1-2 hours of downtime to save the image can be difficult too. What if your app is used in different timezones and there's no 2 hour window you can take it down without killing several users?
Ghosting for disaster recovery utterly fails for desktops. Users lose their local data (which they should back up but don't) and they lose all their little customizations -- wallpaper, etc. Users hate this. Yes it is petty and stupid but we always have users complain to the boss when we re-image a desktop because "they have to spend hours setting everything back up again." Whether the complaints are legit or users are just whining, re-imaging just does not work for desktops.
You could take the approach of the Dept. of Labor (at least in some states). They do a multicast re-image of all desktops EVERY NIGHT. That certainly keeps the crap levels low.:)
"Flash memory isn't a good storage solution for a mail server... you'll wear out the memory in a year or so."
True at first blush. However: make sure your spool and mailhomes are on a RAMDrive, and you should have no problem. Hope you have plenty of RAM though.
You may find that cheap, light foam board insulation (such as Celotex) is a good sound dampener as well. You can also use it to avoid detection when growing pot.
This was in a 60s Popular Science/Mechanics "Wave of the Future" movie, but I've never heard of one actually for sale. Even if somebody made them, they would be exorbitantly expensive, and fragile to boot.
Slashdot Mirror
Interesting. I've got a co-worker from China with a heavy accent. Her name is Li and she says 'Li' and other 'L' words with perfectly-pronounced 'L's.
Maybe it's a Mandarin vs. Cantonese thing?
Oh, Belgium.
"then it'll hit this rucky guy's house again"
If this is a feeble attempt at Engrish, it's the Japanese, not the Chinese, that tend to pronounce English 'L's as 'R's.
I'd make fun of you for confusing Chinese and Japanese like a typical American, but I didn't score so good on the test at http://www.alllooksame.com/, so I won't. Let me watch a few more Chinese Kung Fu and Japanese Samurai movies and we'll see how I do then.
"(Yes, I submitted the original AC post)"
Of course you did. We can all see that both posts were authored by "Anonymous Coward". Thank you Captain Obvious.
"Did you know that all traffic that touches California state road, inclusing bicycles, is subject to an annual state inspection? ... Registration, tags, and even insurance are required. "
Hmm. Pretty crazy if true. I thought the law only regulated motor vehicles with 50cc or larger engines.
Oh, wait, you said California? Well! That explains it. Nevermind.
"Plus, helmets are the law in the uS."
Uh... I've never heard that. And have never seen a helmetless bicyclist ticketed. In my state you can ride a MOTORCYCLE without a helmet, so bicycle helmet laws would seem a bit silly.
Anyway, this story is old news. I saw it a day or two ago. I think it was on Fark?
"It's a matter of emulating the x86 instructions within...Windows..., not supporting a whole OS on an 'emulated machine' as VMWare and VirtualPC do."
Yeah you're right. I've been working heavily with VMWare recently and it jaded my thinking. Of course, the method you mention requires porting the entire Windows API to another platform, which is results in a lot of code and a LOT of labor and debugging. The VMWare installer, on the other hand, weighs in at a mere 36MB (which includes a lot of documentation). And I think MS's VPC installer is about 12MB (compressed).
"suppose MS might soften that blow by bundling an integrated version of VirtualPC to run x86 software"
Not going to work. Products like VMware and VirtualPC do not emulate a CPU, they only provide timeslices of (or some other technique of sharing) the real, underlying CPU. This is for performance reasons, and even still, they lose about 20% to overhead.
The upshot of this is that, when running on non-x86 CPU, VMW/VPC cannot host an x86 OS.
For example, if you run VMWare on an Intel P4, the guest OS sees an Intel P4 CPU.
The Mac solution to running x86 stuff must emulate the whole x86 CPU, and as a result is incredibly ssslllooowww. Incidentally, this is where Transmeta's code-morphing chips were supposed to save the world. Too bad nobody's ever seemed to pursue the idea outside of the laboratory.
All you guys who used to run Netscape on old hardware... hah. I *currently* run Mozilla on my Slackware 10 P133 with 32MB of RAM! Startup is a little slow but once everything except Mozilla swaps out to disk, it's not too bad for googling stuff. Uh, don't try to multitask though.
I also use it on a P90 laptop with 40MB of RAM, and it actually runs faster there. That extra 8MB must make all the difference.
This problem is a poorly designed breather hose that allows blowby gasses from the crankcase to be sucked into the intake and burned. On a gasoline car they use a PCV (Positive Crankcase Ventilation) valve. In both cases it's there to reduce emissions.
In the case of the Rabbit, though, VW foolishly put the hose intake right over a cam lobe. This allows oil to be splashed up into the hose and into the intake manifold. There it pools up until there's a puddle big enough to start getting sucked into the engine... uh-oh.
The runaway problem is easily solved. Go to any VW dealer or foreign auto parts place and buy a $10 plastic oil baffle. This fits over the camshaft and prevents oil from getting flipped into the breather tube by the cam lobe... no more oil in the intake, no more runaways. On later models, like mine, you'll see that the valve cover has an integrated baffle. I installed the second baffle anyway -- cheap insurance.
"the steering column hitting the driver is a common cause of death" I call bull. Cite some references please. If it's so "common", there should be thousands of cases. All cars since the 70s and maybe earlier have had collapsible or telescoping steering columns to prevent this problem.
Just to clarify some of your post -- in Fuel Injection systems (at least in 80s and 90s VWs), you do not control the amount of fuel going into the engine. That pedal on the right is for air. There is Mass Airflow Sensor that senses how much air is going through the throttle body, and then the system meters out the fuel required for a stochiometric (sp) fuel-air mixture.
So stomping on the accelerator can't dump too much fuel into the engine (on a FI car). You only get fuel in proportion to airflow, and the amount of airflow is determined by engine RPM. You control the engine RPM with the throttle.
No wonder you car acts weird when things are out of whack!
"...stole the technology for KITT's (yeah, should be with periods, but I just can't be arsed)"
So... which is easier, typing four periods, or typing 57 characters to explain why you didn't type the four periods?
Sigh. Humans.
Filling your uplink by sending large amounts of data makes it hard for the TCP ACKs of your downloads to come back. Without TCP ACKs, your download halts until it gets them, which just kills download performance.
There are Linux iptables firewall rules to throttle bandwidth a tiny bit and give the ACKs priority. With something like this, you can upload at 255Kbps on a 256Kbps uplink and see no hit in download performance. If you ask me, this is something that should be built into DSL/Cable modems.
You can also give higher priority to game traffic and assign other protocols a lower priority to make sure online games aren't impacted by p2p apps.
I feel your pain. OpenLDAP and the other products may compare at the user-level, but for administration, OpenLDAP just sucks. I have yet to find a good administration tool for it. Maybe one is hiding out there or is being developed as I speak.
Novell sucks because there are some things you can do only in NWAdmin, others you can do only in ConsoleOne. Dumb. That's from Netware 5.1 and 6.0 though, maybe their newer stuff has improved.
Lotus Domino's admin software sucks because everything is buried under 17 layers and if you click the wrong 'X' in the interface, you lose all 17 layers and have to start over. I hate Domino.
iPlanet/SunOne's GUI interface isn't too bad but seems to be really slow, even on a 2GHz server with very few users(?). For advanced config options, you sometimes have to resort to editing a text file (albeit still within the admin GUI), which is one weak point.
AD seems to have got it right with the ADUC and other MMC snap-ins, although if you get in and start messing around with permissions and GPOs you'd better know exactly what the heck you are doing because it's real easy to change things in ways you never expected (or in other words, break AD). The only drawback is, you don't have much low-level control over LDAP attributes and things -- you're just kind of stuck with 'the Microsoft Way' of doing things.
In short, there is no perfect solution. I favor OpenLDAP just because it's OSS but the installation (from source) and the learning curve are both unpleasant. If you're a clueless MCSE-type and just want a quick LDAP directory, I'm afraid AD is the least painful route... if you don't mind clicking a soul-sucking EULA and bleeding ridiculous licensing fees to the Evil Empire.
That's pretty cool. How do you script 3rd party app installs? Is there a common InstallShield interface, or do you have to design a solution for each piece of software?
You can't add PhotoShop to an image and then download that image to 200 PCs if you only have 10 licenses. Even if, somehow, you got 190 of the users to promise not to use it.
Sorry if my original post was unclear.
... and when each of your users requires a different piece of software to do their job, and you don't have licensing to make all that software a part of the image, your users are going to have to reinstall stuff every time.
:)
Ok, I retract my earlier statements. Re-imaging CAN work SOMETIMES in certain situations.
Ghosting kinda works for servers, assuming you have saved a new image each and every time your or the dba or whatever makes a configuration change on the server. Otherwise, you restore from image only to find that your app is broken because there are a half-dozen settings that were made after the backup, that now need to be re-done. And the dba didn't document them. This is easier with Linux because you can just back up the config files, but in Windows this is a real PITA.
:)
In addition, finding 1-2 hours of downtime to save the image can be difficult too. What if your app is used in different timezones and there's no 2 hour window you can take it down without killing several users?
Ghosting for disaster recovery utterly fails for desktops. Users lose their local data (which they should back up but don't) and they lose all their little customizations -- wallpaper, etc. Users hate this. Yes it is petty and stupid but we always have users complain to the boss when we re-image a desktop because "they have to spend hours setting everything back up again." Whether the complaints are legit or users are just whining, re-imaging just does not work for desktops.
You could take the approach of the Dept. of Labor (at least in some states). They do a multicast re-image of all desktops EVERY NIGHT. That certainly keeps the crap levels low.
"a potential conservative bias in the site's algorithm" ...you say that like it's a bad thing.
"Flash memory isn't a good storage solution for a mail server ... you'll wear out the memory in a year or so."
True at first blush. However: make sure your spool and mailhomes are on a RAMDrive, and you should have no problem. Hope you have plenty of RAM though.
That site appears to have nothing to do with Soekris, and is in German no less.
You may find that cheap, light foam board insulation (such as Celotex) is a good sound dampener as well. You can also use it to avoid detection when growing pot.
This was in a 60s Popular Science/Mechanics "Wave of the Future" movie, but I've never heard of one actually for sale. Even if somebody made them, they would be exorbitantly expensive, and fragile to boot.
Three words: heavy black curtains.