"and all but the most privacy-conscious users would uninstall the extensions"
Gee, do you think that maybe that's what the world's largest ad-monger wants?
47 posts • joined 16 May 2007
The 3.5 inchers were more robust, though. Once I got my hands on a rare earth magnet (forget the specific type), and decided to test the urban legends.
It turns out that I couldn't wipe a 3.5 by sticking it on the file cabinet with a magnet. And I let it sit for a full hour before testing.
This was back in the day when PCs were configured by them. Our program used the COM ports to send and receive data. The customer was having an issue where it would write data, but not read.
So I packed up my briefcase full of everything I could think of -- breakout box, adapters, wire, dykes, screwdrivers (yes, this was WAAAAAY before the 9/11-you-can't-bring-anything-useful-on-board days). I fly from Los Angeles to Monterey (just south of San Francisco, for you UK'ers), and get to where the client is I look at his machine, and he has both his COM ports configured as COM1. I flip a DIP switch so that the second port is now COM2 and everything works. This occurred within the first 15 minutes. Now I have six hours to kill before my return flight....
Been there, done that. Back in the days of unloved, unlamented Windows Me.
We were invited to a friend's house for dinner (or supper, if you prefer). I was asked to take a quick look at their PC. I wound up spending 4 hours slaving over the thing, while everyone else enjoyed a lovely meal. And I do mean lovely. Said friend's wife was an excellent cook.
It was at that point I vowed, "Never again!". My stock response when asked what I do for a living is now, "I'm a software developer, and no... I WON'T fix your computer."
I loved the Z8000. We were doing embedded development for a Z8000 based system, and used the ZEUS System 8000 (essentially a port of Unix System III) for development. It was a great chip for its time.
They came out with the Z80000 as their 32-bit chip, which was backward compatible with the Z8000, but it was too late. :(
Back in the mid-80s, when I was at a university, one of the professors in the Computer Science department did his grades on the departmental VAX running BSD. Unfortunately for him, he left the permissions at world-readable.
There was a minor scandal, as some student read the grades and started talking about them.
The amusing part of this was that the professor was teaching the Operating Systems class, and had LITERALLY just completed the *SECURITY* portion of the curriculum...
Remember they chose to put big jointed solids (which cannot be shut down) on SLS after Challenger showed what happens if the joint fails.
At least they did two things right about that.
1. The crew compartment is at the top of the stack where the FSM intended it to be.
2. There actually is a Launch Escape System
(side note: Apollo 11 landed on 1969-07-20.
This is correct.
Santa Cruz (the original SCO) sold some part of its business to Caldera, and then renamed itself Tarantella.
Caldera renamed itself as "The SCO Group" and became the evil SCOundrels we all know and hate.
The original Santa Cruz Operation was a fun place to work at (I had friends there), and while their Unix was a bit on the old and stodgy side (SVR3), it worked well.
Their "two factor" thing sucks. My mother had forgotten her password, so we went through their hoops. Sure enough, they sent a authentication text to her mobile phone. So far, so good.
BUT.... When she entered a new password, she was told that her password wasn't strong enough, even though it met every single criterion they had specified. She was trying to enter a 14 character password with upper case, lower case, numeric, and special characters. Yahoo! insisted it wasn't strong enough.
THEN, I tried to use their "email support" form. I filled out all the info, and hit submit, only to be told I hadn't entered my first name onto the form. Slight problem -- there WAS no place on the form to enter my first name.
Yahoo totally bites.
volatile is not really useful for multithreading, and never has been.
Where volatile shines, is when dealing with memory-mapped I/O. It essentially tells the compiler, "Don't optimize references to this variable -- it can change out from under you". This is not necessarily thread-safe, but makes writing device drivers a heck of a lot easier.
@Bill : "What is the C-language function call for opening a connection with a foreign host over the internet?" I answered "look it up in K&R""
Well, that's the wrong answer. K&R doesn't discuss the Internet. If you had said to "Look it up in Stevens", that would be different.
My Google interview ranged from minutiae to algorithmic details, to "how would you handle this incredibly huge dataset?" I thought it was a decent interview process.
I used to install and support both SCO OpenDesktop and Xenix/286 systems.
Back in the pre-Caldera days, they were considered stodgy, but not evil.
I had an OpenServer 2.0 box that ran for 10 years straight -- only reboots were hardware upgrades.
On the whole, though, I'd say this was a rather weak effort... hang on, someone's at the door... No! No, Simon, NOT THE CATTLEPROD!!! NOO; &*^%&^#^*&--- NO CARRIER
Who told me, to my face, in front of witnesses, that she knows more about computers than I do.
I have a degree in CS, at the time, I had been a professional software developer for 20 years, and had been playing with computers for over 30.
She was an English major, who never got her degree.
Every now and then, I and the rest of the family take some fun in noting that she knows more about my job than I do.
Biting the hand that feeds IT © 1998–2019