Cloud computing separates servers from desktops ?
When Linus attempted kernel 2.6.x with the purpose of synchronizing distributed data on regional servers, he put it on top of the desktop kernel 2.4.x. Six years later, after KDE got separated from gnome; servers are not separated from desktops by kernel 2.6.x.
Well, we have used ajax to separate servers from desktops, and kernel 2.4.x works fine with cloud computing. In the mean time kernel 2.6.x is a mess, bloated; shared modules often have messed up bindings to make anti-crash virtualization almost impossible to achieve. No one understood which apps are using unionfs or aufs? Maintainers could not stop people using codes with bugs on the net. Linus had no quality control at all.
Kernel 2.6.x architecture with udev recently have been stripped down by SliTaz to give us a better look at the true architecture that PC can use. For servers with Uefi bios, kernel 2.4.x is infinitely more stable. Indeed, RHEL is still a reduced operating system. And kernel 2.6.x is mistakenly used for desktops, because of ambiguous devices and their drivers.
The future however is cloud computing, and webpages are indeed simple and transfers data at better than 160 mbps on edgeQam in massive parallel channels. Cloud computing can be well maintained and quality control by webmasters. Browser can update to comply with webpages.
Linux has to adapt to the new arrangements of deaktops and servers, with its operating system.
Cloud computing, the use of voip and iptv ? Experience/skills ?
In cloud computing, people had noticed that cableTV people started to take the bull by the horn, using edgeQam transmission to synchronize multitasking chores by massive parallel computing; namely voip and iptv all on the same wire or wireless at the same time.
CableTV people claim more experience than XP Microsoft experience. Because CableTV has more skills in training films.
The software apps and operating system for cabletv enterprise system is cloud computing thru ethernet type of packets(Docsis3.0/4.0). It will be browser with search engine for millions of channels of half hour programming. Then you can download for cut and paste of sensitive information for your research work. Microsoft data center will have to duplicate many of the cableTV ground office; probably video on-demand servers. The concept of living off youtube and email will seem absurd. But cloud computing maybe video subject matter and skills training and email collaboration. Bill Gates will wish he had stayed on to lead Microsoft just when information technology is going full bloom?
We are stockholders of ARRS and MSFT. Opinions here maybe biased.
Cloud computing is about on-demand servers ? CCUR Linux ?
Now that we know cloud computing servers have to be in realtime for on-demand application. The video servers are not single user limited. Multi users use time shifted TV programming(re-runs) initiated on demand. This means server architecture is different. It has many flash cards or hdds/partitions to start any programming at any time shifted time period. This also works for office procedules, pick up where you left off(download accelerator); you don't have to hurry to finish any task(travelling quality control sheet).
The operating system is therefore quite different from run of the mill Linux distro. CCUR(concurrent computing) is the supplier of both servers, apps and their proprietary operating system, currently rolled out at Time Warner(Staten Island) MSO, triple play.
It is not surprising if Microsoft data center will have some CCUR installations, in the near future.
We are stockholders of CCUR, TWX and MSFT. Opinions here maybe biased.
Cloud computing is redirect by packet conversion ? Not logic ?
Years ago, computing is 'if, then or else' logic arguments. Linux got bloated because of this logic statements for all the bindings, and aliases to work with many open sourced inventions on the fly. The blaotedness just got worse, as time goes on.
In the cloud computing enterprise system, logic is not important. You can redirect your needs by search engines. You just change your packet content to reach your destination.
This makes cloud computing more efficient then desktop apps(limited functionality built in). Cloud computing often allows data standards to be transferred in different apps. SOA on Saas apps will do the job.
Packet converters as servers are extremely simple to build. A floppy based computer can do vast number of tasks. We use many small servers to do a single function jobs, and transfer data to different servers to make up the task. Distributed data servers in regional centers has the complexity to be secure.
Cloud computer has a lot of versatility.
Why Ajax and not Apache and MySQL ? Content/object model ?
For website creation, Apache can be reached by http: links; then you need MySQL or other database for webpages. But where is the content of webpages? If you have webpages, you still need object models to run functionalities on your website.
So, we use Ajax for websites. Javascript(written once and use forever). Dhtml for webpage content. Dom for dynamic object models of webpage programming for computing apps.
There are no Linux website apps that can compete with Ajax. Although Drupal can be used(bug free), and phpbbs is getting better(still have happy face bugs with certain ascii codes).
Interactive gaming can be a future for cloud computing format. And portals on cableTV can be interesting for viewing. Cloud computing is just beginning, but ajax with mpeg4/h.264 video will be improving.
Cloud computing servers on-demand ? Desktop extension ?
It seemed that CCUR had changed the cableTV world by on-demand subscription service, years ago. Now, cloud computing services also need to have extension to our desktop by on-demand service individually. Small computers like cellphones can behave like large servers by cloud computing.
On-demand means individual personal service, where data transfer is on-demand, any time of the day, and prefetched for speed of data transmission, sometimes by channel bonding, with dedicated edgeQam channels(ARRS equipment with Docsis standard of ipTV and voip).
Many computer are not specifically designed for on-demand servers. Computers needed to have protected memory for each customer. HDD with limited access by heads sequentially, can not service on-demand parallel service at the fastest speed. Nand MLC has a better chance to service customers better.
So, cloud computing is coming of age at a different level of technology. Many data centers had to upgrade their equipment to use nand MLC to replace their hdds unless hdd is used in terabyte backup.
We are stockholders of CCUR and ARRS. Opinions here may be biased.
Cloud computing and PBX/hubs ? Why PBX made of hubs ?
The commitment to edgeQam 1024 channels per transmission, is sort of like framebuffered packets of 512 kB assembled packets. When the multichannel data is used, you need dedicated PBX equipment to distribute to channel bonded customers by packet conversion(analog to digital packets).
This concept has to start with edgeQam equipment already in existence. They are 128-256 channel edgeQam capable.
The PBX equipment has yet to be made of perhaps many 8 bit DSPs to handle bit streams. It could even be many smaller switching hubs to assemble into a huge PBX(telephony transmission type of computer).
This is what Microsoft is trying to do with Juniper hubs. Yahoo and HP and Intel, etc., is trying to do research with data centers of 1000-4000 microprocessors(scalable to millions of cpus). In the end, we have to have ARRS do the PBX packet converters in blades with small embedded 8 bit DSPs(massive integration) and hdd or nand?
Why PBX/hubs need ARRS HFC(copper network) amplifiers for Ethernet wires? To compensate for hundreds of feet of wires(too high an inductance).
We are stockholders of ARRS and Msft. Opinions here maybe biased.
Footnote:
EdgeQam is used for video distribution of cableTv. Each video page is made of pixels. one column 8 pixel is an 8 bit ascii code. So the transmission is analog bit stream. which uses analog(pixels in pages) to digital(ascii codes in pages) conversion, then digital to analog conversion to work with data. Then you can insert encoders of Mpeg4/h.264 and decoders to compress data. And 8 bit high speed risc(8 bit data, 32 bit address) to deliver packets once converted to dedicated channel bonded virtual private network.
Instant-on Prex 0.4 Os is browser with cellphone connect ?
It took Prex 0.4 to get the operating system to the foremost concept in cloud computing.
Prex is only 4 kB long. It does cellphone connection to your wireless ISP. Then the html browser takes over. Which can do most of the ascii cloud computing such as database, spreadsheet and word processor. It uses html packets(php) but can be posix packets(Linux) or Ethernet packets(WM), or ,net packets(Firefox).
Because it is only 4kB, you can add more complexity into Prex, especially a better browser(10mB).
Understanding Prex architecture will help netbooks operating system to do cloud computing and avoid window manager desktop. Then, you have instant-on Linux netbook operating system very quickly adapted with cellphone front end in netbook.
Why should we use dialup modem, wireless ethernet, cable modem or telephony T1/3/4, etc. Cellphone 3G is slow, but 2.4 ghz can have edgeQam 6mhz channels. And subcarrier channel can do upto 1 gbps data transfer someday with edge(video braille) data compression.
Once netbooks can do cellphone connection, iphone form factor will be like mainframe computers(serial port terminals thru USB2/3) rsther than PCs(thru ethernet). Is Puppy netbook operating system, dialup modem(or cable modem for speed) and SeaMonkey for instant-on battery operation?
Webpage with gears ? Code trailers to do housekeeping ?
Recently, you noticed that many webpages are much faster to change when you do housekeeping on the webpage.
Any deleted items(hotmail.com, mail.com but not yahoo email) just disappears, items remained closed rank, then only one item deleted packet was sent to the remote server.
This means, these webpages can have a trailer(code gears) that do the housekeeping for you on the same webpage. You no longer had to send the whole webpage back to get a newly revised webpage.
Hopefully, all the web software will pick up the gears codes to do efficient webpage housekeeping service and reduce the cloud computing traffic.
Gears will come of age. And cloud computing will be much faster in response?
Footnote:
For instance, when you edit a webpage and added details. you only had to write back(i586 32 bit cpu instruction) the additions to the remote server, never had to write thru(i386 16 bit software) the whole text(too slow)?