Site Sponsors:
Microsoft Ignorance 
There we were, watching the bandwidth.

The client complains that the time is always around 8AM... people are settling in at work ...

10 ... 9 ... 8 ...

Look Bill... no more network!

What am I talking about?

Why, our inability to be able to readily manage our own computers, anymore! (*)

Yea - we can schedule each and every computer to check for updates within no more than a few days of their availability... but we can no longer turn it off?

... Hey Microsoft: whose computer is it, anyways?

Lamentations


In times past I would routinely turn updates off while traveling. Especially when traveling abroad. Why? Because in the XP days I have had airport servers use the operating-system's update as a vector to install viruses on my computer. Indeed, if you can inject your own Certificate Authority (CA,) into a browser, then hijacking such things is relatively easy to-do.

Moreover, ignoring the fact that there are some updates that will break both hardware-drivers, as well as corporate software, Microsoft's decision to prevent us from managing our own computers demonstrates three (3) things:

THING ONE: The first thing demonstrated is that Microsoft no longer had the brain=trust to adequately manage a belated software-update patch-farm.

Of course, Linux does so with impunity. For free.

Not only is the software development brain-trust logarithmically failing in Microsoft (as everywhere else throughout America,) but one must remember that the majority of Microsoft's updates are fixing software B-U-G-S, people.

Bad software. Bad testing practices. Back-doors, security exploits & holes. Corporate maleficence!

Even the simple & highly testable GAME of Minecraft - so elegantly and operationally handed-off to Microsoft developers - has since become a frustratingly bug-filled nightmare to play!

Such easily avoidable defect nightmares make one wonder - when it comes to quality - if some teams have simply been cursed?

THING TWO: The next thing demonstrated by the Windows 10 developers is that they are completely ignorant of the configurations management requirements of all modern corporations.

While crafting day-sidestepping installation policies are possible, a llot more than corporate visitors use complementary WIFI networks. --Since the advent of Windows 10, all are so slammed by the sheer plethora of now-mandatory Windows updates that most networks are thrashing these days... completely unusable!

And don't get me started about the toll automatic updates is taking across conference halls, at home, & in classrooms: Automatically updating computers in a wireless-networking situation is pure lunacy!.

THING THREE: Using the term "HIDE UPDATES" demonstrates a complete lack of understanding of the English language. Just like ignoring 25 years of Common-User Access conventions, in a time when a "senior engineer" is defined as having a mere 3 years of industry experience, we must marvel at how much money Microsoft must be saving ... while thousands of non-native others so obviously ruin what was once the most-used set of soft-wares in the world.


p.s.


Like Apple, Microsoft wants to be able to spy upon their users too.



(... Create a cookie-tracking Account ... Give them your reverse-searchable phone number ... Put all of your important documents in THEIR cloud... just so THEY can gather clandestine data on us as we SO COMPLACENTLY loose control over our own 'stuff!)

In the "Doh!"


Yet Apple could get away with such things (a mere 10% of the bandwidth, people!)

But at the moment there are A LOT more Microsoft computers, friends!

Therefore (it is sad to even have to point this out to them!), Microsoft updates will suck A LOT more capacity from the corporate pipes.

Even more interestingly, when it comes to spying on their own users MS does not even have the brain-trust to spy on folks properly!

Such is why - if you shut-down, unplug your Windows 10 computer from the Internet (don't forget to disable that home WIFI on those laptops!) that you will receive those "cannot spy on you (sic)" network messages.

Tragically, even when clicking on the resulting "more info" messages as directed, our quest for more information is completely ignored by Windows 10. (I recommend that you use 'view logs', instead? --If any type of corresponding notices are in the Windows log-files at-all, they are usually a lot more cryptic... but we might get lucky when we 'google for some type of understandable explanation...)

... I guess that they will fix THAT later, too?

Solving the Problems


In the mean time, might I suggest that you make a healthy donation to the Free-dome Software Foundation?

After that, then P-L-E-A-S-E contact your congressional representative and ask them - in a time when 1 in 7 Americans are having problems merely finding food - why our government is allowing American companies to use so many foreign workers?

If foreigners need American jobs, could their nations not petition our government to allow them to join the Union?


Statehood worked out rather well for Hawaii!

Who Cares?


Indeed, the fact that companies such as Hewlett Packard & Disney make their billions in America does not prevent their imported-executives from loosing any sleep as each farm American jobs out to (in the words of the guilty HP Executive) "less expensive" nations!

In the 1960's '70's & '80's, companies with no loyalty to the American worker would have been boycotted... What has changed?

(*) By the way: Even after I downloaded the software, I was unable to "hide updates" for anything. My advice now is that - when traveling - to simply not allow Windows 10 to connect to the Internet.

Caveat User!


[ view entry ] ( 1241 views )   |  permalink
Public DNS to AWS VPC on EC2 
There has simply GOT to be a good anagram in the title for this post somewhere ... ;-)

New to WHO?


Sadly, the folks at Amazon & elsewhere do not know that Clouds were being enshrined on blackboards & plastic (flowchart) stencils well before the Internet was a keyword.



Indeed, if it was not for the fact that things like REST caused folks to spend billions of dollars fixing things that were never broken in the first place - if so many new-wheel / old-wheel fire-drill were not so expensive - such over-hyped fire-drills would be comical. (*)

Reality


For financial reasons alone, many feel the the unfortunate tendency both new folks to the industry & the media have to shout "eureka" when re-discovering the wheel is truly unnerving.



And so it goes with AWS and EC2 - Rather than working with a box of well ordered tools, one often feels that they are instead working with a young ESL kid who is trying to describe what is in a newly-opened box of freshly-caught frogs. While the overall experience is extremely flexible and ready to take on any computing challenge, anyone who knows what they are doing is in for a rather amusing - and probably a needlessly time consuming - journey.

What pat of the term DNS ... ?


For example: After mucking about with Amazon Web Service (AWS) for any length of time, you will undoubtedly want to link a PUBLIC URL to your Virtual Private Cloud (VPC.)

VPC Misnomer


First and foremost note that the official name for "VPC" is surely a misnomer!

Why? Because Multicomputer Clouds do not have single-entry command prompts.

In short, one must use SSH (etc) to get a command prompt on your VPC so as to manage Operating System (OS) commands - just as one would do on any PC OS.

Rather than being any type of as-named "private cloud" however, this VPC is - in reality - a Virtual Personal Computer (or "PC")! (VPC == Virtual Linux / Windows P.C)

Wristwatch?


Moreover, the free Amazon VPC one most often encounters is certainly in no way even a "Personal Server:" Most cell phones have more memory & data storage these days. (Indeed, how could any modern P.C. of any description have so little RAM + storage? My Raspberry Pi and Beagle Bone Black microcomputers have as much!)

So the pseudo-technical folks might call the AWS-PC a cloud-prince... but after we kiss it, it still smells like a somewhat underfed frog to the rest of us? (Not to mention the warts-for-today I'm 'talkin 'bout ;)

What type of "warts" you might ask? -Well, unlike a multi-host "Cloud" of any description - yet just like any PC - your VPC will have an IP address. Unlike a PC however, at the time of this writing the default IP Address and public Domain Name Service (DNS) endpoints will change every-time the VPC is re-started (Instance) on the EC2.

Moving Target?


The problem with the new-IP-on-reboot strategy is that the entire point to having a Domain-Name Service is to associate a static "name" with a far more changeable IP Address. Hence - and unlike what most 'geeks of any tenure are used to - using that default Amazon-generated DNS entry becomes just as pointless as hard-coding that ever-changing IP address into your application(s)!

So if one might be tempted to (1) assume that your VPC will never be restarted & simply (2) create another DNS A Record to (3) point to your default DNS VPC instance-name, note that if you ever (4) re-boot your VPC off of the EC2 that the A Record will simply (5) become a pointer to a tombstone.

What's a geek to do?

Elastic IP Address


Like most things AWS, there is a way around everything.


In this case, after a few hours I discovered that the terrarium includes the ability to create a STATIC IP address (Colloquially speaking, static is not very "elastic"? -But with a little thought & tolerance, the concept works for me. -Such is the pattern with all things AWS ;)

Once created, one can THEN associate that "elastic" address with a running Instance of your VPC on the EC2, as well as create an A Record that will also refer to that far more immutable name, as well.

So sure, dynamically instancing a bevy of VPC clones onto the EC2 so as to allow them to "expand and contract" on-demand is a very cool idea. -Just like a "dial group", the idea of having a single phone number round-robin ringing any given set of telephone hand sets was cool even back in the 1950's.

Yet every rational regionalist knows that a frog-in-a-cloud - by any other name - is still a frog?


Sharing is caring!

-Rn



(*)
Yes, in 1970 mainframes were trying to do "in-cloud" computing, as well ;)

Rather than having any historical context, new kids seem to want to re-discover everything from the concept of "web service" (what do all those RFC's describe, anyway? HTTP? HTTPS? HTML Forms?) to "the Internet of things" (was a UAV, PDA, set-top box, poll-top electric transformer, IP:X10 network, or oil rig not a "Thing"?

Do these new, visionary, "things" not have computers in them, as well?? IP?


--So overlooking the jibes in the postscript herein we must simply ask ourselves: Did we miss something here... or did someone else?

[ view entry ] ( 710 views )   |  permalink  |  related link
Installing MySQL Server & Workbench 
In a previous article we praised the innovative way Red Had allows us to rapidly install things like MySQL.


For the new learner however, note that at the time of this writing that only the MySQL Client (mysql-client) toolset will be installed.

Service, Please


If you are looking to do some R&D on your local host (we use a Virtual Box), then one will want to also install the MySQL Server tools (mysql-server), as well:

su
yum install mysql-server

Thereafter (*) we can start the locus via:

service mysqld start

As well as subsequently begin the MySQL console interface simply by typing
mysql
at the console interface.

MySQL Workbench


For those of us who absolutely love Microsoft SQL Server's SQL Management Studio (SSMS), note that MySQL has a must-have graphical tool set, as well. Formerly known as "MySQL Administrator", we now call it the "Workbench."



No matter what we call it however, the Community Edition of the GUI is the very next item most R&D folks will want to download.



Again at the time of this writing however, there is often an installation caveat. Before installation, try
yum install http://ftp.altlinux.org/pub/distributio ... x86_64.rpm
if you run into problems whilst doing something like
yum install mysql-workbench-community-6.1.7-1.el6.x86_64.rpm
Once installed, merely enter
mysql-workbench
at the console to get things rolling.


Google Fodder


Installing the MySQL Server will resolve error message such as:
Error: Package: mysql-workbench-community-6.1.7-1.el6.x86_64 (/mysql-workbench-community-6.1.7-1.el6.x86_64) Requires: libtinyxml.so.0()(64bit)

[ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)

-as well as:
mysqld: unrecognized service

or someday perhaps even:
mysqld: unrecognised service  ;-)





Ubuntu & Elsewhere


(*) Note that Ubuntu learns will want to use
sudo apd-get install mysql-server
sudo service mysqld start
rather than
yum ...
. Otherwise, everything else in this post will work the same.

[ view entry ] ( 1572 views )   |  permalink  |  related link

<<First <Back | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | Next> Last>>