The future:

————————————————————-

Seems awful convenient that with the alleged hard drive shortage, that prices for drives will go even higher. Sometimes I get the sense that with the price of drives of going up, there is no incentive to retool and produce more drives. There is less cost from having less factories and with more profit per drive becase of demand, therefore there is a doubly wider profit margin. With people addicted to having to have media warehouses to put it nicely, makes the hard drive manufacturers even more greedy.

My web server ata hard drive (a whopping 30 gigs saying that with tongue in cheek) bit the dust. Lucky I found a spare 40 gig in the closet. We will see how long it lasts. May have enough drives to pull from old systems outlast the alleged hard drive price gouging. Thank god I am not a media junkie and have to quench a thirst or habit for needing unlimited hard drive space.

Diskless computing from using ltsp, iscsi, aoe, and the like are good alternatives to needing drives for client machines. Web based applications are another way to save space. Practice of load once and serve many. Diskless thin clients and or old machines running diskless is the way to go. Already purchased ide compact flash adapters to convert existing machines to thin clients. Cheaper than buying all new thin clients.

Then it also came to me that the alleged hard drive shortage could also be a ploy to get (aka force) people to use the cloud. Then computing could be controlled by a few. Such devious tactics are just a whim of my own conjouring. Will still use the net for a while. As for the cloud, we will just use our own stuff. Long live free computing.

————————————————————————————–

From Eff.org:

Bloggers can be journalists (and journalists can be bloggers). We’re battling for legal and institutional recognition that if you engage in journalism you’re a journalist with all of the attendant rights privileges and protections. (See Apple v. Does.)

Bloggers are entitled to free speech. We’re working to shield you from frivolous or abusive threats and lawsuits. Internet bullies shouldn’t use copyright libel or other claims to chill your legitimate speech. (See OPG v. Diebold.)

Bloggers have the right to political speech. We’re working with a number of other public-interest organizations to ensure that the Federal Election Commission (FEC) doesn’t gag bloggers’ election-related speech. We argue that the FEC should adopt a presumption against the regulation of election-related speech by individuals on the Internet and interpret the existing media exemption to apply to online media outlets that provide news reporting and commentary regarding an election — including blogs. (See our joint comments to the FEC [PDF 332K].)

Bloggers have the right to stay anonymous. We’re continuing our battle to protect and preserve your constitutional right to anonymous speech online including providing a guide to help you with strategies for keeping your identity private when you blog. (See How to Blog Safely (About Work or Anything Else).)

Bloggers have freedom from liability for hosting speech the same way other web hosts do. We’re working to strengthen Section 230 liability protections under the Communications Decency Act (CDA) while spreading the word that bloggers are entitled to them. (See Barrett v. Rosenthal.)

Coders’ Rights Project
EFF’s Coders’ Rights Project protects programmers and developers engaged in cutting-edge exploration of technology. Security and encryption researchers help build a safer future for all of us using digital technologies, but too many legitimate researchers face serious legal challenges that prevent or inhibit their work. These challenges come from laws such as the Convention on Cybercrime, the Digital Millennium Copyright Act, the Computer Fraud and Abuse Act, similar state laws, and computer crime laws in many countries around the world.

The Coders’ Rights Project builds on EFF’s longstanding work protecting researchers through education, legal defense, amicus briefs, and involvement in the community with the goal of promoting innovation and safeguarding the rights of curious tinkerers and hackers on the digital frontier. We also provide policy advice to decision-making officials who are considering new computer crime legislation and treaties.

Reverse Engineering FAQ

People have always explored and modified the technologies in their lives, whether crystal radios, automobiles, or computer software. Reverse engineering is one expression of this tinkering impulse. Unfortunately, legal regulation of reverse engineering can impact the Freedom to Tinker in a variety of ways. This FAQ gives some information that may help coders reduce their legal risk.

Vulnerability Reporting FAQ

Discovering security flaws is only half the battle – the next step is reporting the findings such that users can protect themselves and vendors can repair their products. Many outlets exists for publicly reporting vulnerabilities including mailing lists supported by universities and by the government. Unfortunately, however, researchers using these public reporting mechanisms have received legal threats from vendors and government agencies seeking to stop publication of vulnerability information or “proof of concept” code demonstrating the flaw. The Vulnerability Reporting FAQ gives information that may help security researchers reduce their legal risk when reporting vulnerabilities.

A “Grey Hat” Guide

A computer security researcher who has inadvertently violated the law during the course of her investigation faces a dilemma when thinking about whether to notify a company about a problem she discovered in one of the company’s products. By reporting the security flaw the researcher reveals that she may have committed unlawful activity which might invite a lawsuit or criminal investigation. On the other hand withholding information means a potentially serious security flaw may go unremedied.

—————————————————————–

Thinking a little about wifi. What could I do to make surfing at an untrustworthy point at least a bit safer. This is what I came up with.

Then I started to think a bit about it more. Would it not be nice to take advantage of the free wifi and multiply it’s input to me.

Then there is the idea to use a public sip server to do voip.

—————————————————————–

Do not need http://en.wikipedia.org/wiki/Unified_Extensible_Firmware_Interface but would rather use http://www.openfirmware.info/Welcome_to_OpenBIOS instead.

Fedora is allegedly full of premeditated rhetoric. Why was the Fedora/MS deal done in such secrecy? Anti-opensource action for sure. Why was there not an open discussion first. Who gave them the right to speak for the linux community. Did  anyone involved get any kickbacks?  A shame that the Fedora mgmt has allegedly never heard of the open bios.  Makes one want to file a complaint under the RICO ACT. In any case, Fedora allegedly seems like a sellout and terminally hurt the linux community as a whole that sets an extremely bad precedent. They should of asked for help first (especially from REDHAT) before caving in.  Fedora has missed the greater issues of freedom. We hope they have nightmares every night once they get a clue..

——————————————————————-

Simple hints:

Changed the jumper on a hard drive from cable select to master that was connected to a usb to ide interface for the system to read the drive.

Put all your computer notes/source code/config files in a blog online. That way you always have access to something special you have done. Makes the notes easily repeatable and accessable.

Backup  you local website;

$ wget -r http://www.misslizziesworld.com

Server backup the old fashion way:

$ rsync -avz eddie@oesrvr1:/* .

Kill a program

$ pkill firefox

or

[eddie@oedt01 ~]$ ps aux | grep blue
eddie 9603 2.2 1.0 83848 10540 ? S 04:09 0:00 bluedevil-monolithic
eddie 9611 0.0 0.0 4588 764 pts/0 S+ 04:09 0:00 grep –color=auto blue
[eddie@oedt01 ~]$ kill -9 9603
[eddie@oedt01 ~]$ ps aux | grep blue
eddie 9613 0.0 0.0 4588 768 pts/0 S+ 04:10 0:00 grep –color=auto blue

——————————————————————-

Want to try MSWindows 8 see: ( double the minimum requirements for realistic use)

http://windows.microsoft.com/en-US/windows-8/iso

NOTE: USE AT YOUR OWN RISK…

——————————————————————

Upgrade desktop form Fedora 16 to 17.

Please make sure that the system that you want to upgrade has more than 600 MB of RAM

$ sudo yum update rpm

Then we install the latest updates:

$ sudo yum -y update

Next we clean the yum cache:

$ sudo yum clean all

If you notice that a new kernel got installed during yum -y update, you should reboot the system now:

$ sudo reboot

(After the reboot, log in as root again,

Now we come to the upgrade process. We can do this with preupgrade (preupgrade will also take care of your RPMFusion packages).

Install preupgrade…

$ sudo yum install preupgrade

… and call it like this:

$ sudo preupgrade

——————————————————————-

Pancakes with the new no rise time yeast.

Good day.

Advertisements