You forgot...
The cup holder on the big box.
3058 publicly visible posts • joined 14 Dec 2007
Well, you could have blown me over with a feather.
When something bounces up and down by 50% in one week or so, one needs to be VERY suspicious. Somehow I would short the security about a year out, and probably make money. Then again, some people think the lottery is a good investment.
(*SIGH*) Not me!
68K architecture, which I read somewhere doesn't have this problem. Unfortunately they stopped with the 68060 and didn't go farther. All in all a MUCH cleaner architecture. Probably slower, but WAY more compact in instruction count. Yes it was very CISC, but when memory was more expensive it was the way to go.
Now we have these problems, and with very little genetic diversity, I suspect it might not be the last.
"Do you keep your front door unlocked?"
Well, when I was growing up, that is exactly what we did. Of course it was in simpler times (the 50's and 60's), but if you knew where, there was an unlocked door in the house that only got a lock (mini deadbolt) when the selling realtor put it in.
Yes, much simpler times. I compare them to PC's with no networking in locked offices (usually on some "executive's desk rarely used").
Times have changed.
Needs to pay the bill for all of this. Whoever this is will need to build things to make it work. You have several technologies that vie for this, cable, wireless, DSL, etc. When we use the broadband internet, for whatever price whatever company provides the service must not do it at a loss (or it won't last long). All of this costs $$$ (or whatever your local currency is today), and the money comes from two sources, a government, or individuals. Take your pick. For the most part government money comes with a spaghetti mess of "strings attached" that some politician (or group of them) has put in place to accommodate someone. Private money wants to be paid for, so I pay for my DSL.
Do you get what you pay for? I really don't know, but I do get DSL for a few bucks a month, and it seems to work OK. Yes, I wish it were cheaper, but life goes on. (*SIGH*).
As batteries get more "efficient", they approach being explosive devices. The problem is that the batteries are self contained energy devices, whereas common fuels (diesel, petrol/gasoline) need to be supplied with oxygen form the air to be useful.
Another way to have self contained energy sources, is to use hypergolic fuels (rockets use these). At least they are binary in nature and need both parts to generate heat.
This is the reason that batteries catch fire/explode all by themselves. Not fun.
Given that a major share of the CPUs out there are from one vendor, this is what you get. A hardware bug that permeates over several chips. Nice to see that AMD (minority report) doesn't have the problem.
Maybe Chipzilla Intel is too big and needs to be sliced and diced.
Thought experiment: What would Intel be if IBM had picked a different processor for its PC back in 1981 (Motorola 68000?)?
Just remember that MRI (magnetic resonance imaging) was once called NMR (nuclear magnetic resonance). The name was changed because of the bad vibes that anything with the name "nuclear" in it.
So now you know the rest of the story.
Yes, there was a company that changed its name from "Apple Computer" to "Apple, Inc.". If it changed to "Apple Blockchain" I might be a multimillionaire.
Something that Microsoft calls "Universal plug and pray play".
All of this "automatic" stuff makes for complacent users that probably don't know better. How many times have you wandered around to find routers with default names.
Another alternative might be to require vendors that don't keep updating software on their interconnected devices to release it under a GPL type license.
Then there was the router near my mother-in-law's condo that had its default credentials (and was open). I made a point of adding a password to the administrative access and locking it up to keep it open. It has since gone dark (*SIGH*).
If you have worked with this stuff (especially punches) that are high speed, they had lots of pent-up energy. You took off ALL your rings, and ties if you ever worked with this stuff. Most were belt driven which increased the likelihood of getting stuff caught in the "works".
Be careful out there!
Designed to make it to code for accountants back in the 1950's. You wouldn't need programmers, and anyone could "write code".
This whole thing is a case of "been there, done that", and it will continue. We humans are the ones that think into the future and can "design" things. Very little (if any, as I can't think of anything) is designed without human input. I have strong doubts that this will change.
Nice try though.
p.s. COBOL is still here, writing paychecks and checking general ledger stuff.
Saturday Night Live back in the 70's announced that they had received a message from someone who intercepted the Voyager probe. They held up a card that said:
SEND MORE CHUCK BERRY
Oh, and he was a guest of JPL at the "finish" party after the Neptune encounter.
The casting of a ballot should be a simple and verifiable action. The voter should be able to "count" his own ballot to see that he actually did the "right thing" (another topic for discussion). The counting process can be "automated" or "manual", but it should be doable by ANYONE who desires. Sure they might take multiple days of time to manually count the ballots, but the same result should be obtained as from an "automated" process.
Yes, some sort of nice paper as the intermediary is necessary for this to happen. It should be both human AND machine readable. For all the flaws, punch cards were human readable, but there was the silly "hanging chad" problem.
There should be no "trade secrets" in either process, and an advance "audit" (if necessary) of ALL the software should be available. Sorry, I really don't trust Diebold.
Yes, they are wonderful, but scripts should be through. Many a time I have looked at scripts only to find out that the writer is lazy n the third degree. Some examples:
Routing stderr to /dev/null
chmod 777 <file> just because it solved the "problem".
Leaving temp files floating around
Such things as "cat file | command"
No explanatory comments on what is going on.
Scripts that say "Doing xxx" when they are actually "Doing yyy".
scripts that mimic standard commands in weird ways with errors themselves (see above)
right
Unfortunately this happens with all to much regularity, and the "clean-up" usually find an error undiscovered that will really much things up if executed in the wrong/right way.
So we all fix them drawing from experience, and life goes on. (*SIGH*)
A friend of mine had his "shop" setup with one like that. He had gotten a load of flash bulbs with edison (screw( bases, and decided to wire all of them up to the "do not touch" switch. On many occasions we had left the room only to return with the person he had left behind in a somewhat blind and dazed look. He mentioned that it was "priceless".
Yes, I have plugged 120 volt kit (my case it was a tape recorder in the 60's) into 240 volt outlet. In my defense, I didn't know the outlet was 240 volts. I confirmed that it was by looking at the light bulb in a lamp socket. Of course I did "return to shelf" the item and didn't say many words about the incident. Oh, and yes, it was in the USA, and I was in the third form.
One wonders what Intel might be had IBM picked the 68k as its processor for the PeeCee. Then (1980 or so as I recall) IBM had a chunk of ownership in Intel, so the choice was made for them. Fast forward to around 1990 when Apple, IBM, and Motorola chummied up and eventually decided to go the PPC route. Who knows what the world might be if they had different decisions. Sadly the 68k processors didn't get the backing from Motorola (Freescale, whoever it is now), and the shift was on again. It happens. For the most part if all you need to do is cycle the source through a different compiler chain, and you get something that "works", I suspect that nobody will really care. Rare is the application now that touches the instruction set directly, it is all some sort of compiled code.
Personally, the 68k instruction set was pretty good, and could have improved given the chance (*SIGH*). Who knows, maybe there is a 68k emulator that runs under ARM (at reasonable speed).
Life goes on.
We have these things issued by our wonderful friendly DMV (Department of Motor Vehicles) called stickers. We attach them to our license plates to indicate we have paid $$$ in fees and taxes to our wonderful state. These change color every year so friendly policemen can tell if you have paid up. Thankfully, they allow one to renew registrations online eliminating ghastly lines at the local DMV office (hours!).
Of course the local police aren't that observant. While I do renew, the sticker on my vehicle still says 2015. In a year or so the color will be back in vogue. If you DON'T pay (and get your vehicle smog checked every other year), the fines are a real mess. I won't even go there.
Is some vendor to make nice form factor compatible motherboards with ARM CPU chips. Throw in a couple of PCI (or whatever buss is popular) slots and there you have it.
Given this, just plunk down a Linux distro and you are in business.
Works for me. Arm & Linux, a nice alternative to "wintel".
There are TWO parts of an election with very different qualities needed.
First, there is the voting itself. Very "private" by its nature, and should remain so.
Second, there is the counting. It needs to be VERY public so we have some faith in the process.
The big problem is attempting to combine these two very different functions into one "device". It shouldn't be done AT ALL.
What to do? Have the "voting machine" accept nice inputs from a touch screen, and with a connected printer generate a both human and machine readable document that you stuff into a ballot box. Then anyone can tally up things and all is good. If the voter doesn't like the votes recorded (by inspection), tear it up and try again.
Will it be done this way? Probably not, but we can hope.
This is where the "wonderful coding" that populates The daily WTF. They must use the _Learn_<insert topic here>_in_24_hours_ as a textbook.
Sorry, but it takes a few years to be "good", and hopefully you have some "real world" experience.
Yesterday the power went out (unbeknownst to me) and my wonderful wife with iPhone in hand complained to me that out WiFi wasn't working. So she rolled over and handed me the iPhone and I attempted to look for WiFi to no avail. The next complaint was that the charger wasn't working either. This usually happens when I switch off the outlet connected to the light on her size of the sleeping apparatus (there is a switch on my side). So I flick the switch and hope that the light comes on. Nope that doesn't work either. I then "rise and shine" and look around. No power. Not a good thing.
So, yes, it can take a few minutes to realize that the power is out, and it did happen to me.
(*SIGH*)
I suspect that "new" video display boxen (aka TV's) will attempt to be compatible with new standards, but you never know. In my house, I still have (count 'em) 5 NTSC only TVs. They still work quite nicely with the TiVo box that emits proper signals. Yes, I do have a bunch of "adapters" (with enough $40 coupons you can get quite a few) and a single W I D E screen video display box for watching sporting events at times (it also makes a great display for a Raspberry Pi).
Someone should have designed the ATSC standard to last a bit longer. NTSC lasted over 60 years in one form or another, and served us quite well. One thing I learned is that we humans can interpolate quite a bit in the visual field, and while some things need lots of resolution (computer monitors seem to be high on the list), entertainment TV got by quite well at 480p resolution for quite a while!
So, life goes on and another standard goes obsolete. (*SIGH*)
Wasn't that one of the Spice Girls. At least that is what I thought.
p.s. I really don't like pumpkin for eating AT ALL. They are bet for carving weird faces to scare people. Candles for illuminating optional. Oh, yes, they don't last long so you do it a couple of days before. Be sure to throw away sometime on November 1.
That a dip in ammonia (let air dry) will probably do the trick.
As for the particular case, I suspect that they already had a warrant for the entire premises, and locating the nasty device was the task at hand, the pooch assisting. Just a time saver for the police who didn't want to paw through "everything".
Of course "encrypted cloud storage" is the order of the day.
Yes, beware of the BOFH!
When you cross a frontier, EVERYTHING is subject to search for contraband. If a customs bozo opens up your suitcase and sees plans for (insert terrible thing here), what do you think he is going to do?
Yes, the problem is now compounded with the amount of data you can carry in such a small space, but is just the same. Try going to places like China where after they seize your laptop they put monitoring software on to see what subversive stuff you are doing and what secrets they can have you graciously ship back to them for competitive reasons.
I suspect the moral of the story is "Don't piss off a border agent".
It would be nice if we didn't need to do such things, but that ideal world sadly doesn't exist.
I'll probably get downvotes for this (*SIGH*)
This is probably the smartest thing that you mention. You already have a BOFH in residence, so additional ones really aren't needed.
Best of luck.
A bit too far away for me to apply, and I might not fit the proper demographic (50 years and counting being paid for computer work).
Thankfully BOFH's are not age bound.
On requirements? Does having a bronze, silver or gold badge count?