Just another WordPress site
Getting rid of weeds is a pain. Pluck them, and they come back. Kill them with chemicals, and the ground is poisoned for other plants. These organic corn farmers demonstrate a much more reliable, chemical-free, and downright spectacular method to clear the ground – FIRE!
The latest Ebola outbreak has claimed yet another life in the Democratic Republic of Congo, raising the death toll to 12—though the actual number may be as high as 27. Using a strategy known as “ring vaccinations,” officials began treating doctors and other frontline healthcare workers in Bikoro, the town where the outbreak was first declared in early May.
The DRC government declared the Ebola outbreak on May 8 after two cases were confirmed by lab tests. The outbreak is currently confined to the Bikoro region of Equateur Province in the northwestern part of the country, but the detection of Ebola in the city of Mbandaka on May 17th represented a worrisome development.
Advertisement
As of today, the DRC says there are about 56 cases of hemorrhagic fever (a primary symptom of the disease) and 35 confirmed Ebola cases, of which 13 are probable and eight suspected. This is the third Ebola outbreak in the DRC in the past five years and the ninth since 1976 when the disease was first identified. The Democratic Republic of Congo is located in the heart of sub-Saharan Africa and is home to nearly 79 million people.
Earlier today, DRC Health Minister Oly Ilunga traveled to Bikoro, a small market town located 78 miles (126 km) south of Mbandaka, to oversee the vaccinations of at least 10 people. It was here that the outbreak was first declared three weeks ago and at least five Ebola deaths have occurred so far, according to the Associated Press. Officials are employing a strategy known as ring vaccinations in which the people who are most likely to be infected are treated. Today’s vaccinations included three doctors at Bikoro Hospital, two health experts, two nurses, a woman’s community representative, and a pygmy representative. The drug used was the experimental rVSV-ZEBOV, and all vaccinations were voluntary.
Ring vaccinations started on May 21 in Mbandaka, with 7,560 doses ready for immediate use, according to the World Health Organization. The drugs were donated by its developer, Merck, while Gavi, the Vaccine Alliance has contributed $1 million towards operational costs. Ground teams are currently searching for and following up with all known contacts, of which 600 have been identified to date.
Advertisement
“Implementing the Ebola ring vaccination is a complex procedure,” said Matshidiso Moeti, WHO Regional Director for Africa, in a statement “The vaccines need to be stored at a temperature of minus 60 to minus 80 degrees centigrade and so transporting them to and storing them in affected areas is a major challenge.”
On May 18, WHO said the current outbreak is not yet an international emergency, but admitted a “vigorous” response was still necessary, both on the ground and in terms of funding its $56.8 million Ebola strategic response plan. WHO is currently working to prevent the disease from crossing the DRC’s nine borders, CBS reports. Also, several schools have been shut down in the Iboko health zone as a precaution. The next few days and weeks are critical in ensuring the outbreak doesn’t escalate any further.
Advertisement
The current outbreak involves the Zaire Ebola virus, which is known to be fatal in up to 60 to 90 percent of cases. Ebola spreads from person to person via contact with bodily fluids, but it often makes the jump to humans from wild animals such as bats and monkeys.
[Associated Press via NYT, CDC, CBS News, WHO, CBC]
via Gizmodo
‘Ring Vaccinations’ Continue in Congo as Ebola Death Toll Rises
CEO: I can’t take you seriously because there’s a typo in your slide deck. You’ve lost all credibility because of your sloppy presentation. And don’t mention my wife in your slide deck. Dilbert: That’s “wi-fi.”
Woman: I need help persuading your boss to bless my project. Should I use facts and logic? Dilbert: No, he hates that stuff. Woman: Maybe I could appeal to his better angels? Dilbert: His better angels wear noise-canceling headphones. Woman: Okay, fine. I’ll just appeal to his self-interest. Dilbert: It would be in his best interest to avoid people like you. Woman: What do you suggest? Dilbert: We’ve had good outcomes using his ignorance and fear. Woman: Sign this ore else a blockchain drone will kill you in your sleep. Boss: Where’s my pen!
Percona Monitoring and Management (PMM) is a free and open-source platform for managing and monitoring MySQL® and MongoDB® performance. You can run PMM in your own environment for maximum security and reliability. It provides thorough time-based analysis for MySQL® and MongoDB® servers to ensure that your data works as efficiently as possible.
In PMM Release 1.11.0, we deliver the following changes:
The issues in the release includes 1 new features & improvements, and 9 bugs fixed.
We spent some time this release going over how we handle MySQL’s Slow Log rotation logic. Query Analytics requires that slow logging be enabled (either to file, or to PERFORMANCE_SCHEMA) and we found that users of Percona Server for MySQL overwhelmingly choose logging to a file in order to take advantage of log_slow_verbosity which provides enhanced InnoDB Usage information. However, the challenge with MySQL’s Slow Log is that it is very verbose and thus the number one concern is disk space. PMM strives to do no harm and so MySQL Slow Log Rotation was a natural fit, but until this release we were very strict and hadn’t enabled any configuration of these parameters.
Percona Server for MySQL Users have long known about Slow Query Log Rotation and Expiration, but until now had no way of using the in-built Percona Server for MySQL feature while ensuring that PMM wasn’t missing any queries from the Slow Log during file rotation. Or perhaps your use case is that you want to do Slow Log Rotation using logrotate or some other facility. Today with Release 1.11 this is now possible!
We’ve made two significant changes:
Number of Slow Logs Retained on Disk
Slow Logs Rotation – On or Off
You specify each of these two new controls when setting up the MySQL service. The following example specifies that 5 Slow Log files should remain on disk:
pmm-admin add mysql ... --retain-slow-logs=5
While the following example specifies that Slow Log rotation is to be disabled (flag value of false), with the assumption that you will perform your own Slow Log Rotation:
pmm-admin add mysql ... --slow-log-rotation=false
We don’t currently support modifying option parameters for an existing service definition. This means you must remove, then re-add the service and include the new options.
We’re including a logrotate script in this post to get you started, and it is designed to keep 30 copies of Slow Logs at 1GB each. Note that you’ll need to update the Slow Log location, and ensure a MySQL User Account with SUPER, RELOAD are used for this script to successfully execute.
/var/mysql/mysql-slow.log {
nocompress
create 660 mysql mysql
size 1G
dateext
missingok
notifempty
sharedscripts
postrotate
/bin/mysql -e 'SELECT @@global.long_query_time INTO @LQT_SAVE; SET GLOBAL long_query_time=2000; SELECT SLEEP(2); FLUSH SLOW LOGS; SELECT SLEEP(2); SET GLOBAL long_query_time=@LQT_SAVE;'
endscript
rotate 30
}
We’ve updated the logic on four dashboards to better handle predictability and also to allow zooming to look at shorter time ranges. For example, refreshing PXC/Galera graphs prior to 1.11 led to graphs spiking at different points during the metric series. We’ve reviewed each of these graphs and their corresponding queries and added in <aggregation>_over_time() functions so that graphs display a consistent view of the metric series. This improves your ability to drill in on the dashboards so that no matter how short your time range, you will still observe the same spikes and troughs in your metric series. The four dashboards affected by this improvement are:
In earlier releases, the MySQL Exporter expected only key=value type flags. It would ignore options without values (i.e. disable-auto-rehash), and could sometimes read the wrong section of the my.cnf file. We’ve updated the parsing engine to be more MySQL compatible.
Annotations permit the display of an event on all dashboards in PMM. Users reported that passing more than one string to pmm-admin annotate would generate an error, so we updated the parsing logic to assume all strings passed during annotation creation generates a single annotation event. Previously you needed to enclose your strings in quotes so that it would be parsed as a single string.
PMM is available for installation using three methods:
docker pull percona/pmm-server – DocumentationHelp us improve our software quality by reporting any bugs you encounter using our bug tracking system.
The post Percona Monitoring and Management 1.11.0 Is Now Available appeared first on Percona Database Performance Blog.
via MySQL Performance Blog
Percona Monitoring and Management 1.11.0 Is Now Available
In this blog post, I will show you how easy it is to set up a Percona Monitoring and Management server on Google Compute Engine from the command line.
First off you will need to have a Google account and install the Cloud SDK tool. You need to create a GCP (Google Cloud Platform) project and enable billing to proceed. This blog assumes you are able to authenticate and SSH into instances from the command line.
Here are the steps to install PMM server in Google Cloud Platform.
1) Create the Compute engine instance with the following command. The example creates an Ubuntu Xenial 16.04 LTS compute instance in the us-west1-b zone with a 100GB persistent disk. For production systems it would be best to use a 500GB disk instead (size=500GB). This should be enough for default data retention settings, although your needs may vary.
jerichorivera@percona-support:~/GCE$ gcloud compute instances create pmm-server --tags pmmserver --image-family ubuntu-1604-lts --image-project ubuntu-os-cloud --machine-type n1-standard-4 --zone us-west1-b --create-disk=size=100GB,type=pd-ssd,device-name=sdb --description "PMM Server on GCP" --metadata-from-file startup-script=deploy-pmm-xenial64.sh Created [https://www.googleapis.com/compute/v1/projects/thematic-acumen-204008/zones/us-west1-b/instances/pmm-server]. NAME ZONE MACHINE_TYPE PREEMPTIBLE INTERNAL_IP EXTERNAL_IP STATUS pmm-server us-west1-b n1-standard-4 10.138.0.2 35.233.216.225 RUNNING
Notice that we’ve used
--metadata-from-file startup-script=deploy-pmm-xenial64.sh
The file has the following contents:
jerichorivera@percona-support:~$ cat GCE/deploy-pmm-xenial64.sh #!/bin/bash set -v sudo apt-get update sudo apt-get upgrade -y sudo apt-get install apt-transport-https ca-certificates curl software-properties-common curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo apt-key add - sudo add-apt-repository "deb [arch=amd64] https://download.docker.com/linux/ubuntu $(lsb_release -cs) stable" sudo apt-get update # Format the persistent disk, mount it then add to /etc/fstab sudo mkfs.ext4 -m 0 -F -E lazy_itable_init=0,lazy_journal_init=0,discard /dev/sdb sudo mkdir -p /mnt/disks/pdssd sudo mount -o discard,defaults /dev/sdb /mnt/disks/pdssd/ sudo chmod a+w /mnt/disks/pdssd/ sudo cp /etc/fstab /etc/fstab.backup echo UUID=`sudo blkid -s UUID -o value /dev/sdb` /mnt/disks/pdssd ext4 discard,defaults,nofail 0 2 | sudo tee -a /etc/fstab # Change docker’s root directory before installing Docker sudo mkdir /etc/systemd/system/docker.service.d/ cat << EOF > /etc/systemd/system/docker.service.d/docker.root.conf [Service] ExecStart= ExecStart=/usr/bin/dockerd -H fd:// -g /mnt/disks/pdssd/docker/ EOF sudo apt-get install -y docker-ce # Creates the deploy.sh script cat << EOF > /tmp/deploy.sh #!/bin/bash set -v docker pull percona/pmm-server:latest docker create -v /opt/prometheus/data -v /opt/consul-data -v /var/lib/mysql -v /var/lib/grafana --name pmm-data percona/pmm-server:latest /bin/true docker run -d -p 80:80 --volumes-from pmm-data --name pmm-server --restart always percona/pmm-server:latest EOF
This startup script will be executed right after the compute instance is created. The script will format the persistent disk and mount the file system; create a custom Docker unit file for the purpose of creating Docker’s root directory from /var/lib/docker to /mnt/disks/pdssd/docker; install the Docker package; and create the deploy.sh script.
2) Once the compute engine instance is created, SSH into the instance, check that Docker is running and the root directory pointing to the desired folder.
jerichorivera@pmm-server:~$ sudo systemctl status docker
● docker.service - Docker Application Container Engine
Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
Drop-In: /etc/systemd/system/docker.service.d
└─docker.root.conf
Active: active (running) since Wed 2018-05-16 12:53:30 UTC; 45s ago
Docs: https://docs.docker.com
Main PID: 4744 (dockerd)
CGroup: /system.slice/docker.service
├─4744 /usr/bin/dockerd -H fd:// -g /mnt/disks/pdssd/docker/
└─4764 docker-containerd --config /var/run/docker/containerd/containerd.toml
May 16 12:53:30 pmm-server dockerd[4744]: time="2018-05-16T12:53:30.391566708Z" level=warning msg="Your kernel does not support swap memory limit"
May 16 12:53:30 pmm-server dockerd[4744]: time="2018-05-16T12:53:30.391638253Z" level=warning msg="Your kernel does not support cgroup rt period"
May 16 12:53:30 pmm-server dockerd[4744]: time="2018-05-16T12:53:30.391680203Z" level=warning msg="Your kernel does not support cgroup rt runtime"
May 16 12:53:30 pmm-server dockerd[4744]: time="2018-05-16T12:53:30.392913043Z" level=info msg="Loading containers: start."
May 16 12:53:30 pmm-server dockerd[4744]: time="2018-05-16T12:53:30.767048674Z" level=info msg="Default bridge (docker0) is assigned with an IP address 172.17.0.0/16. Daemon option --bip can be used to set a preferred IP address"
May 16 12:53:30 pmm-server dockerd[4744]: time="2018-05-16T12:53:30.847907241Z" level=info msg="Loading containers: done."
May 16 12:53:30 pmm-server dockerd[4744]: time="2018-05-16T12:53:30.875129963Z" level=info msg="Docker daemon" commit=9ee9f40 graphdriver(s)=overlay2 version=18.03.1-ce
May 16 12:53:30 pmm-server dockerd[4744]: time="2018-05-16T12:53:30.875285809Z" level=info msg="Daemon has completed initialization"
May 16 12:53:30 pmm-server dockerd[4744]: time="2018-05-16T12:53:30.884566419Z" level=info msg="API listen on /var/run/docker.sock"
May 16 12:53:30 pmm-server systemd[1]: Started Docker Application Container Engine.
3) Add your user to the docker group as shown below and change deploy.sh script to executable.
jerichorivera@pmm-server:~$ sudo usermod -aG docker $USER jerichorivera@pmm-server:~$ sudo chmod +x /tmp/deploy.sh
4) Log off from the instance, and then log back in and then execute the deploy.sh script.
jerichorivera@pmm-server:~$ cd /tmp/ jerichorivera@pmm-server:/tmp$ ./deploy.sh docker pull percona/pmm-server:latest latest: Pulling from percona/pmm-server 697841bfe295: Pull complete fa45d21b9629: Pull complete Digest: sha256:98d2717b4f0ae83fbca63330c39590d69a7fca7ae6788f52906253ac75db6838 Status: Downloaded newer image for percona/pmm-server:latest docker create -v /opt/prometheus/data -v /opt/consul-data -v /var/lib/mysql -v /var/lib/grafana --name pmm-data percona/pmm-server:latest /bin/true 8977102d419cf8955fd8bbd0ed2c663c75a39f9fbc635238d56b480ecca8e749 docker run -d -p 80:80 --volumes-from pmm-data --name pmm-server --restart always percona/pmm-server:latest 83c2e6db2efc752a6beeff0559b472f012062d3f163c042e5e0d41cda6481d33
5) Finally, create a firewall rule to allow HTTP port 80 to access the PMM Server. For security reasons, we recommend that you secure your PMM server by adding a password, or limit access to it with a stricter firewall rule to specify which IP addresses can access port 80.
jerichorivera@percona-support:~$ gcloud compute firewall-rules create allow-http-pmm-server --allow tcp:80 --target-tags pmmserver --description "Allow HTTP traffic to PMM Server" Creating firewall...-Created [https://www.googleapis.com/compute/v1/projects/thematic-acumen-204008/global/firewalls/allow-http-pmm-server]. Creating firewall...done. NAME NETWORK DIRECTION PRIORITY ALLOW DENY allow-http-pmm-server default INGRESS 1000 tcp:80 jerichorivera@percona-support:~/GCE$ gcloud compute firewall-rules list NAME NETWORK DIRECTION PRIORITY ALLOW DENY allow-http-pmm-server default INGRESS 1000 tcp:80 default-allow-icmp default INGRESS 65534 icmp default-allow-internal default INGRESS 65534 tcp:0-65535,udp:0-65535,icmp default-allow-rdp default INGRESS 65534 tcp:3389 default-allow-ssh default INGRESS 65534 tcp:22
At this point you should have a PMM Server in GCP running on a Compute Engine instance.
The next steps is to install pmm-client on the database hosts and add services for monitoring.
Here I’ve launched a single standalone Percona Server 5.6 on another Compute Engine instance in the same project (thematic-acumen-204008).
jerichorivera@percona-support:~/GCE$ gcloud compute instances create mysql1 --tags mysql1 --image-family centos-7 --image-project centos-cloud --machine-type n1-standard-2 --zone us-west1-b --create-disk=size=50GB,type=pd-standard,device-name=sdb --description "MySQL1 on GCP" --metadata-from-file startup-script=compute-instance-deploy.sh Created [https://www.googleapis.com/compute/v1/projects/thematic-acumen-204008/zones/us-west1-b/instances/mysql1]. NAME ZONE MACHINE_TYPE PREEMPTIBLE INTERNAL_IP EXTERNAL_IP STATUS mysql1 us-west1-b n1-standard-2 10.138.0.3 35.233.187.253 RUNNING
Installed Percona Server 5.6 and pmm-client and then added services. Take note that since the PMM Server and the MySQL server is in the same project and same VPC network, we can connect directly through INTERNAL_IP 10.138.0.2, otherwise use the EXTERNAL_IP 35.223.216.225.
[root@mysql1 jerichorivera]# pmm-admin config --server 10.138.0.2 OK, PMM server is alive. PMM Server | 10.138.0.2 Client Name | mysql1 Client Address | 10.138.0.3 [root@mysql1 jerichorivera]# [root@mysql1 jerichorivera]# pmm-admin check-network PMM Network Status Server Address | 10.138.0.2 Client Address | 10.138.0.3 * System Time NTP Server (0.pool.ntp.org) | 2018-05-22 06:45:47 +0000 UTC PMM Server | 2018-05-22 06:45:47 +0000 GMT PMM Client | 2018-05-22 06:45:47 +0000 UTC PMM Server Time Drift | OK PMM Client Time Drift | OK PMM Client to PMM Server Time Drift | OK * Connection: Client --> Server -------------------- ------- SERVER SERVICE STATUS -------------------- ------- Consul API OK Prometheus API OK Query Analytics API OK Connection duration | 408.185µs Request duration | 6.810709ms Full round trip | 7.218894ms No monitoring registered for this node identified as 'mysql1'. [root@mysql1 jerichorivera]# pmm-admin add mysql --create-user [linux:metrics] OK, now monitoring this system. [mysql:metrics] OK, now monitoring MySQL metrics using DSN pmm:***@unix(/mnt/disks/disk1/data/mysql.sock) [mysql:queries] OK, now monitoring MySQL queries from slowlog using DSN pmm:***@unix(/mnt/disks/disk1/data/mysql.sock) [root@mysql1 jerichorivera]# pmm-admin list pmm-admin 1.10.0 PMM Server | 10.138.0.2 Client Name | mysql1 Client Address | 10.138.0.3 Service Manager | linux-systemd -------------- ------- ----------- -------- ----------------------------------------------- ------------------------------------------ SERVICE TYPE NAME LOCAL PORT RUNNING DATA SOURCE OPTIONS -------------- ------- ----------- -------- ----------------------------------------------- ------------------------------------------ mysql:queries mysql1 - YES pmm:***@unix(/mnt/disks/disk1/data/mysql.sock) query_source=slowlog, query_examples=true linux:metrics mysql1 42000 YES - mysql:metrics mysql1 42002 YES pmm:***@unix(/mnt/disks/disk1/data/mysql.sock)
Lastly, in case you need to delete the PMM Server instance. Just execute this delete command below to completely remove the instance and the attached disk. Be aware that you may remove the boot disk and retain the attached persistent disk if you prefer.
jerichorivera@percona-support:~/GCE$ gcloud compute instances delete pmm-server The following instances will be deleted. Any attached disks configured to be auto-deleted will be deleted unless they are attached to any other instances or the `--keep-disks` flag is given and specifies them for keeping. Deleting a disk is irreversible and any data on the disk will be lost. - [pmm-server] in [us-west1-b] Do you want to continue (Y/n)? y Deleted [https://www.googleapis.com/compute/v1/projects/thematic-acumen-204008/zones/us-west1-b/instances/pmm-server].
The other option is to install PMM on Google Container engine which was explained by Manjot Singh in his blog post.
The post Setting up PMM on Google Compute Engine in 15 minutes or less appeared first on Percona Database Performance Blog.
via Planet MySQL
Setting up PMM on Google Compute Engine in 15 minutes or less
Listening: the poor man’s talking. But your turn to pay attention to someone else’s blah blah will come. Here’s how to be the kind of listener you’d like to talk to.
Cash Nickerson is the author of The Samurai Listener, which is kind of a mashup of business advice and a how-to on listening that leans heavily on western ideas of the way of the Samurai. Fast Company interviewed Nickerson for some easy tips on how to improve your ability to not just hear what people are saying, but to really listen.
This is basic politeness, but if someone is talking to you and you’re scrolling through Instagram, you are not paying attention. Much of our communication comes from more than words, and you’re not noticing enough about someone to get the subtext. Unless they’re on their phone, too—in which case I think they’re probably saying they don’t want to be having this conversation either.
Not forever, of course. But when you’re discussing something, you won’t really be able to receive what the other person is saying if you can’t let go of your ideas about what they’re saying first. There are some opinions I personally don’t ever want to let go of, but if you want to really understand someone’s point of view, sitting through the end of it without interrupting will help.
Advertisement
“Listening helps you handle conflict, express respect and be a better leader,” Nickerson says. “Unfortunately, most people don’t remember because they don’t hear it in the first place.”
An article in Psychology Today says something similar, describing it as “consciously deciding to give input.” You are leading someone so you can learn more, not shutting them down:
The good listener is secure enough to rationally decide whether, in any given situation, to add input or to just listen and possibly ask follow-up questions. Don’t let your desire to impress trump what’s best for the interaction and the desired outcome. In the right situation, restraint can be just as compelling. Do you add content to a conversation only when wise?
Do you? Or are you just listening to get revved up to talk?
Another thing mentioned by Psychology Today is the importance of noticing what is not being said. They give the example of talking to someone who never wants to discuss personal relationships, but is always willing to chat about work. That’s kind of a red flag if you’re on a date, but great if you’re looking for a business partner. And if, say, you were an investigative reporter, you would probably notice the topics that your subject kept turning away from—and push harder in those directions.
Advertisement
Most of us aren’t conducting an interrogation, but still, there’s a lot to learn about someone based on what they avoid talking about. Listen for the silences.
A lot of misunderstandings can be avoided with a few simple questions. If you’re not one hundred percent sure what someone is saying, try to rephrase it and ask if that’s what they mean. You won’t look stupid—you’ll look like you give a crap. That’s all most people want.
Once you’ve got a hold of the facts, you need to understand someone’s reason for sharing them. This is something I personally do when I’m interviewing a person for a story, or even when I’m on a date: I analyze what they’re saying in the moment, but instead of responding with my own opinion, I double check.
“You’ve said A and B. Does that mean you believe C?”
That gives them the opportunity to clarify, or agree. People rarely tell you a story for no reason. Figuring out what that reason is is the challenge.
This all sounds exhausting. It is! Listening actively is a skill that’s honed, and one you can employ or not. There are also whole courses on listening, because not everyone you listen to is a good talker. Sometimes people are boring, meandering, and distracted. But sometimes they have useful information. You should know how to extract it.
Sometimes you just can’t listen! I cannot pay attention to someone when I’m hangry, exhausted or stressed, and all three of those things can come up in the course of a long talk. Sunny Sea Gold wrote in Scientific American that she had been accused of being a bad listener by her husband. She interviewed psychology researcher John Stewart, author of U&Me: Communicating in Moments That Matter, in an effort to improve. Stewart said that it’s very important to know when you’re no longer able to pay attention:
“Genuine listening requires humility and curiosity—and neither can be successfully faked,” Stewart says. If you’re not feeling well, if you’re hurried, rushed or overly stressed, you’re not going to be able to be truly present and curious during a conversation, especially a tough one.
Convincing someone that it’s time to pause is an entirely different skill from listening, but here’s something you can say:
Advertisement
“I think this conversation is important, but I need some time so I can give it my undivided attention.”
And if someone doesn’t get that, they’re the one who needs to work on listening.
Cruise ships seem to offer a lot of bang for your buck, and some do sell tickets at a loss. PolyMatter points out some of the many ways that cruise ship companies make or save money, such as flying under different flags, offering one-way trips and having casinos.
Computer History Museum (CHM), an institution which explores the history of computing and its impact on the human experience, announced on Tuesday the public release and long-term preservation of the
, one of
successful
, as part of its Center for Software History’s Historical Source Code. The release comes after a five-year negotiation with Qualcomm. From the
:
The first version of Eudora was created in the 1980s by Steve Dorner who was working at the University of Illinois at Urbana-Champaign. It took Dorner over a year to create the first version of Eudora, which had 50,000 lines of C code and ran only on the Apple Macintosh. In 1991, Qualcomm licensed Eudora from the University of Illinois and distributed it free of charge. Qualcomm later released Eudora as a consumer product in 1993, and it quickly gained popularity. Available both for the IBM PC and the Apple Macintosh, in its heyday Eudora had tens of millions of users. After 15 years, in 2006, Qualcomm decided that Eudora was no longer consistent with their other major project lines, and they stopped development. The discussion with Qualcomm for the release of the Eudora source code by the company’s museum took five years.
Len Shustek, the chairman of the board of trustees of the Computer History Museum,
:
Eventually many email clients were written for personal computers, but few became as successful as Eudora. Available both for the IBM PC and the Apple Macintosh, in its heyday Eudora had tens of millions of happy users. Eudora was elegant, fast, feature-rich, and could cope with mail repositories containing hundreds of thousands of messages. In my opinion it was the finest email client ever written, and it has yet to be surpassed. I still use it today, but, alas, the last version of Eudora was released in 2006. It may not be long for this world. With thanks to Qualcomm, we are pleased to release the Eudora source code for its historical interest, and with the faint hope that it might be resuscitated. I will muse more about that later.
via Slashdot
Computer History Museum Makes Eudora Email Client Source Code Available To the Public
by Steve Tarani, Originally Posted here.
U.S.A. –-(Ammoland.com)- Living in a world where extreme physical violence can erupt at a moment’s notice, it’s important to be armed with more than only one weapon!
The most effective way to stop a bad guy with a gun is a good guy with a gun – a good guy who has the skills to stop the threat (AKA – you). However, to rely solely on a carry pistol as your only response tool puts you at a tactical disadvantage.
In addition to a lightweight, compact, easily-accessible handgun, you’re also armed with a weapon that requires no bullets, batteries or carry permit. Your most powerful weapon for avoiding or mitigating an active threat will always be YOUR MIND.
We’ve all heard the term “situational awareness,” but what exactly is it? Simply put, situational awareness (S/A) is an awareness of your immediate environment. Should one of your five senses pick up a threat indicator, such as seeing a bad guy across the street moving toward you with a knife, hearing gunfire, smelling smoke, etc., you are forewarned of a potential physical threat. The extra few seconds or even minutes in some cases, affords you the opportunity to not be there, should the threat continue to evolve.
Real-world examples are easy to come by. In Salzburg, Austria lampposts are being covered in airbags to stop “smartphone zombies” from bumping into them as they walk around staring at their screens. Really. Here at home it’s the same thing – you don’t have to look very hard to find people texting while driving or walking. All of their awareness is focused around a 6” radius of their device-holding hand. How would they know if something threatening was unfolding in their immediate environment?
That’s how S/A gains you a tactical advantage – by giving you knowledge… plus time. If you happen to hear gunfire or observe an active shooter before they observe you, those precious seconds are valuable chunks of time that you may need to make a judgment call, take flight or fight. If you choose to take flight, which is the safest of the two options, then that borrowed time can help get you out of effective threat range and/ or possibly behind cover or into hiding.
Should your decision be to fight, then those very valuable quarter seconds just bought you immediate response opportunity. More time equals more opportunity to solve the tactical problem.
Sufficient time is required to defeat your cover garment, clear your pistol from its holster, and verify that you have a good backstop. All of this takes some amount of time before you can point your muzzle toward the bad guy(s), align your sights and initiate your trigger press.
Buying yourself this required time, places you in a dominant posture. This position would not have been afforded you, had you not applied your S/A, and were instead caught behind the action/ reaction power curve of an active threat.
Being situationally aware is one of the most powerful tools you can have in your tool kit. Combined with a good firearm, you can decrease your vulnerability and gain the tactical advantage of being forewarned and forearmed.
About Steve Tarani
Steve Tarani, is a former CIA protective services subject matter expert who served on Donald Trump’s pre-election protection detail and is the lead instructor for the NRA’s new Non-ballistic Weapons Training program offered nationally to 2.3 million members. Tarani, an active protective agent, is a Central Intelligence Agency and FLETC-certified federal firearms instructor who also provides services for the US Naval Special Operations Command, FBI National Citizens Academy Alumni Association, National Association of School Resource Officers (NASRO), and others.
The post Forewarned is Forearmed – Springfield Armory appeared first on AmmoLand.com.
via AmmoLand.com
Forewarned is Forearmed – Springfield Armory