Why tiny SliTaz and for what ? Future ?
SliTaz is 25 mb, requires i486/i686 for kernels 2.4.24.2/2.6.24.2, 256 mb of dram and broadband service for lengthy surfing or 128 mb of dram with 1 gb swap file on hdd. It is quite upto date in Linux world but needs front end fot JWM on panel size zooming. Small gxine panel with less pixels will speed up movie downloads.
It could be even smaller in footprint if network operating system is abandoned for mobile cellphone and dialup modem, using opera mini v4 with overview and zooming technology thru Opers website condensation. This is the bright future for SliTaz dialup.
Firefox is big and bigger yet to be, using up 35 mb just to launch it and 85 mb further to store webpages; on top of SliTaz image of 25 mb and 9/16 mb to execute programs, 46 mb of dram swap file. So, dram requirement will creep up if Flash is installed. SliTaz claims javascript but Google apps(ajax is javascript, dom and dhtml) are not well served, until dhtml is included.
So, the architecture of SliTaz will have to be reexamined, and forked it strictly for telephone browser to be ultra tiny(concept of Prex 0.4 plus opera mini v4). Then expand into broadband IPTV, triple play 160 mbps; if download can be stored in dvdrw or USB flash cards?
- Login or register to post comments
- Printer friendly version
- 565 reads
Will Microsoft update IE5.5 ? For dialup customers of MSN.com ?
IE5.5 can use 8 mb of drams for earthlink and other iSPs. It has 750 mb of virtual memory in hdd to support the 8 mb of drams.
IE6.0 was used with the 32 mb of drams and the same 750 mb of virtual memory. However, the latest up date shows 192 mb of drams needed when IE 6.0 is launched; 256 mb is more comfortable. Virtual memory typically used for surfing is only 600 mb.
If Microsoft continues to support IE5.5 for server 2008; 192 mb of drams will be the minimum.
And it will be prudent to have condensed pixel browsers(smaller frames) like opera mini to serve the Microsoft server operating system(just add zooming features in the server webpage delivery system. Dram requirement can be shrinked back to 8 mb?
Supporting older computers will let MSN(8 million XML customers) catch up woth AOL(22 million html, ansi(bbs rip), motion jpeg Yahoo type customers of dailup modems). If, Yahoo webpage contents are the reason Microsoft made the huge offer to acquire? Then opera mini type of webpage contents is the next acqusition? Smith Barney take notice?
The tectonic shift of media content presentation ? sdTV ? hdTV ?
Server 2008 needs vast desktops to make business successful. So, the media content can not be xml which tax the speed of computers to make transactions. Xml has to be supplemented by (d)html(google apps and my google) and even text based faxed info made of only pixels(Google search engine).
But the cable tv people had forged ahead with mpeg4/h.264 and its sdTV and hdTV resolutions. You can zoom between all the resolutions, instead of using anti-aliasing software that does not work well for all the fonts and their sizes.
Opera mini v4 was rewritten from scratch to convert regular webpages by overview(for condensation of contents) and zoom into framebuffers of cellphone monitor resolution.
This is a takeoff of the cable TV technology, but not quite using the Mpeg4/h.264 technology.
So, we will see some business shift to video servers of cable TV to offer three versions of webpages of different resolution by mpeg4 technology? The on-demand software and QoE virtualization to resend lost packets will finish the ISP denial of service that SunMicro computers(DSP modem card bus, not USB) can not handle. The ISP market(mostly dialup modem) will open up for on-demand equipment; one stream for each 1000 customers per channel.