IdeaWazaWiki - User contributions [en]

Linux for mobile computing

2009-03-31T09:06:57Z

81.246.171.45: /* Suggestion 11:VoIP program */

This article contains adjustments necessairy to the Linux OS in order to allow a special way of working with a proposed UMPC-design.

==Suggestion 1:Simplification of the Bourne Again Shell (on which Linux ;eg Fedora, ... works)==
The Bourne Again Shell has, during its long lifetime, gained several improvements and thus new programs. This has had as a result that to perform a same specific task, the user is bothered with a amount of overlapping programs.

Aldough Linux' self-correcting community might have resolved this earlier, as it is no longer actively used (now graphic interfaces are used instead) no corrections have been made for these flaws. Besides a large amount of overlapping programs, the command line interface has also a number of features which can be dismissed and replaced by other existing commands, hereby making a huge simplification possible.

Examples on this are:
*viewing of a text file: this can be done by an excessive amount of programs as vi, pico, less, more, ...

*the unnecessairy grep-command; instead locate with a specific option (thus locate -xx) can perform this function if locate is altered so it allows this

*The unnecessairy possibility of using relative pathnames, this can be replaced by only allowing absolute pathnames

*The unnecessairy pwd-command; instead the current directory can just be shown in the command line itself (similar as in DOS).

*The unnecessairy append I/O redirection and piping option; instead of using append (>>) one can simply use overwrite (>) instead

*The write permissions included with files should no longer include type-information (only gives extremely limited information and would be better checked with the filename-extension. Also, support for a sticky bit (-t permission) should be dropped. Thus instead of presenting eg drwxrw-rw- this would become rwxrw-rw-

*the possible use of general points in folders (not being part of the extension) should be dropped. Thus folders named foo.bar etc can no longer be created. This has caused allot of confusion in the past.

*finally, commands as ls for listing folders, ... are best changed to list. Changing the commands to these makes it easier to remember them.

P.S.: Text also implemented to http://en.wikipedia.org/wiki/Talk:Bash#The_BASH.27_lack_of_simplification

==Suggestion 2: Altering of the standard Linux directory tree structure==
Secondly, linux's Filesystem Hierarchy Standard' (FHS) directory tree structure should be altered, so that physical drives and imiginary folders/directory's are no longer used together. At the moment, for example physical drives are mapped in /dev while /, or /root (which are actually on a physical drive and should of been thus actually marked in a folder under /dev), ... are at a maplevel higher. It would be far better sense if simply the ports are detected and presented (thus a computer with 2 USB drives and a serial ATA-connection would get 3 folders under the root folder (/) knowingly SATA1, USB1, and USB2. The drives connected hereon would simply show their contence. The main drive (on which Fedora is placed) would then get the systems folder and user folders, ...

In addition to this renaming of the logical drives, standard names for partitions too are to be altered. Instead of the now common names (hda, sdb, hda1, hda2, ..) these are to become Partition1, Partition2, Partition3, Swap (for the swap partition), ... The extra information obtained from the hd+a-d difference is negligable, especially as only hot swappable drives should be supported anyway (which have no slave/master/auto option) and only tend to confuse users.

More information
Filesystem Hierarchy Standard (FHS)
http://www.pathname.com/fhs/

Standard linux partition names
http://linux.org.mt/article/partnames

==Suggestion 3: Dropping support for a variety of useless/surplus file formats and protocols in favor of one good file format/protocol (per type)==

Firstly, the linux-distro (eg Fedora) could drop its support for outdated/archaïc aswell as recent/new but unusable file formats. Rather than supporting a wealth of file formats, it is better to only support one good file format per type ( e.g. lossy/lossless audio encoding, lossless and lossy video encoding, compression and/or archiving format, ...). By a good file format I mean that one that has the best qualifications for which it is intented and which is open-source/free file format.

Aldough thus fewer formats can be played/executed, simplification and thus no longer supporting it would make computing simpler for the user itself and it would also allow Fedora of operating faster (as lesser code is required). Having a wealth of file formats supported not only confuses the user, but also makes him unaware what file-type to use in what situation (eg .tar.gz or .bz2 for tape archiving?) As Fedora is specifically targeted at the developing world (which still has mostly low-schooled people), this simplification may prove essential.

PS: Other Linux distributions as Gobuntu also feature solely open formats, yet this suggestion would still be different as it would allow but a single format per type, with the intent to simplify matters. This offcourse is not yet achieved in these distrubutions.

Examples are :
*.xcf and .svg for pictures
*OGG Vorbis instead of MP3, WMA, ... for lossy audio encoding
*Flac or Monkey's Audio instead of WAV, ... for lossless audio encoding
*.odt-files instead of .doc
*an open source combined compression and archiving file format as .7z to make a compressed and archived file (compressed file format alone aswell as archived file format alone not needed; when an open-source executable/install archiving format as rpm or paf aswell is supported )
*an open source archiving file format as .tar
*only UTF-8 for emails

In addition to dropping support for these file formats, allot of protocols aswell as environmentally damaging media should be dropped aswell. Besides in the intrest of the environment, the cd media (CD/DVD/DVDRAM/Blue-Ray, ...)would also be dropped as they only have a very limited lifetime, are easily corrupted and are not at all durable.

Examples:
SFTP instead of FTP
support for parallel and serial connections with devices should be dropped in favor of SATA, USB2 and FireWire800
support for USB1 should be dropped
support for appletalk should be dropped
support for the older ethernet cards/cables and protocols should be dropped, aswell as token ring ATM, ... in favor of PowerLine Communication (PLC)and gigabit ethernet
support for old forms of WiFi (802.11a-g) should be dropped in favor of WiMax and the new WiFi-protocol (802.11n) (if used)
support for Floppy's, CD/DVD/DVDRAM/Blue-Ray, should be dropped in favor of the best type of flash memory (CompactFlash?), and USB-sticks and external harddisks

Aldough this would transform the Linux version on which these suggestions are implemented more and more to a embedded form of Linux, this would actually be very beneficial. This as not only matters are simplified greatly, but also as the processor needed to run the Linux-distro can be far less potent/energy consuming than normal. A example on this can be seen with the ECB_AT91 microcomputer and the ECB_ATmega32/644 microcomputer.

More information
Free file formats
http://en.wikipedia.org/wiki/Free_file_format
Comparisation of audio codecs
http://en.wikipedia.org/wiki/Comparison_of_audio_codecs
Comparisation of container formats
http://en.wikipedia.org/wiki/Comparison_of_container_formats
Comparisation of archive formats
http://en.wikipedia.org/wiki/List_of_archive_formats
Secure FTP
http://en.wikipedia.org/wiki/SFTP
USB2
http://en.wikipedia.org/wiki/USB2#USB_2.0
FireWire 800
http://en.wikipedia.org/wiki/Firewire#FireWire_800_.28IEEE_1394b.29
Serial ATA
http://en.wikipedia.org/wiki/SATA
WiFi
http://en.wikipedia.org/wiki/Wi-Fi
Flash Memory
http://en.wikipedia.org/wiki/Flash_memory
Powerline Communication
http://en.wikipedia.org/wiki/Power_line_communication
Gigabit Ethernet
http://en.wikipedia.org/wiki/Category_5_cable
http://en.wikipedia.org/wiki/10_gigabit_Ethernet

ECB AT91 and ECB_ATmega32/644 using a embedded linux and being able to run on a 180mhz cpu and 20 mhz cpu respectively
http://en.wikipedia.org/wiki/ECB_AT91
http://en.wikipedia.org/wiki/ECB_ATmega32/644

==Suggestion 4: Dropping support for dual booting==
At the moment, most linux-distro's still support the possibility of dual booting (that is: having multiple Operating Systems on a single device/drive from which one may be selected to run on startup). I believe it is best that this dual booting feature, along with the programs which support this and which are usually standard included in a regular installation should be best dropped. This will reduce many of the hassles frequently encountered with linux installations and make sure that everything is kept simple and more efficient. Instead of this dual booting by having 2 OS' on 1 disk, random booting of other OS's may still be done, but then trough physically connecting another drive (HD, USB-stick, ...) on which an other OS is installed. Selecting which OS to load first would be done merely trough the BIOS (boot sequence can be altered here).

As people will revert to this technique, this approach would become more popular/easy and fits with the trend emerging to divert to a more easy and hot swappable form of computing/connecting of devices. As USB-sticks are rapidly becoming cheap and are already capable of storing entire OS' (eg Mac-on-a-Stick, Knoppix, LindowsLive, MojoPac, ...) and as all HD's are becoming hot swappable nowadays (trough Serial ATA/USB2/IEEE1394/...), this would prove far easier/simpler.

Having gone trough the troubles described myself with this "dual booting", lack of hot swappability (with E-IDE HD's, "jumpers" had to be manually set) and troubles/corruption of the "bootloaders/master boot record" on HD's, I am hoping that this might become a valid action which may be taken to make computers simpler/more efficient to operate.

More information:
Hot swapping and types of HD's and other devices
http://en.wikipedia.org/wiki/Serial_ATA
http://en.wikipedia.org/wiki/Hot_swapping
http://en.wikipedia.org/wiki/MojoPac
http://portableapps.com/apps/operating_systems/mac-on-stick

Live Linux disributions becoming more popular
http://en.wikipedia.org/wiki/LiveDistro
http://en.wikipedia.org/wiki/List_of_LiveDistros

Dual booting, bootloaders and the master boot record of devices
http://en.wikipedia.org/wiki/GNU_GRUB
http://en.wikipedia.org/wiki/LILO_%28boot_loader%29
http://en.wikipedia.org/wiki/Dual_booting
http://en.wikipedia.org/wiki/Master_boot_record

==Suggestion 5: Fedora's possible feature of switching to a command line-executed programs split screen configuration==
In the past, Linux developments have been focusing on improving the Graphical User Interface (GUI) of Linux, so that inexperienced users (that do not know how to use the command line) may use Linux easier. However, this implementing of the extra subroutines needed to recognise mouse control has had an adverse effect on the systems speed and performanence. Also, besides making the system slower, one wonders why such mouse control needs to implemented anyhow as if is also the cause of 2 additional disadvantages. These are

the unpracticality of using a mouse when on the road (e.g. with a portable computer, or in crammed/busy environments as with public computers at airports, libraries, subways, ..)

the slower speed at which you can operate a computer with a mouse versus with the command line, via keyboard (e.g. to perform the action of manually clicking the mouse, and not just the reduced speed of the computer)

As such, it may be better to include the option of controlling Fedora Linux via keyboard, in a split screen configuration. This configuration would be composed at one side of a command-line window (BASH, ...) and on the other side a window with the executed programs (e.g. FireFox-syle browser, OpenOffice-style text-editor, ...). This configuration proposed would make the system speedier and more stable (as the GUI itself or less subroutines in the GUI are needed) and would also still allow a great deal of eye candy. More so, with some extra work, the configuration would also make it possible to make this OS even nicer than any other existing OS as it may allow complete 3D.

Aldough the 3D features proposed may need some more time to implement, the terminal/program configuration can be implemented nearly immediatly and improve Fedora. For the 3D features, some of the coding done by OS's as IRIX and Linux-3D-modifications as Project Looking Glass can be used to create the modification to Fedora.

Finally, I wish to mention that, if you wish to implement the terminal window-program window - split screen configuration (described in the previous letter), a possible simplification of the current command line (BASH) can be implemented . This simplification of commands would allow more users to use this configuration as it would be much easier to learn the commands. Also, the combined terminal window - program window set-up would allow even further simplification. If you decide to implement the split-screen configuration and wishes to also reduce the commands used (simplify the BASH), please contact me for further assistance.

P.S.: As noted, the suggestions on the Linux-distro above can be supplied as a optional packet with Fedora, leaving the user the liberty of installing it -or not-. As such, Fedora may still be controlled by mouse for those people that really don't want to change the way how they control their computers.

More information:
Graphical User Interfaces (GUI)'s
http://en.wikipedia.org/wiki/Graphical_user_interface#Graphical_user_interfaces_compared_to_command_line_interfaces
Goobuntu (Google Linux distribution)
http://en.wikipedia.org/wiki/Goobuntu

IRIX (Unix distribution with 3D functionality)
http://en.wikipedia.org/wiki/Irix
Project Looking Glass (3D Modification for Linux)
http://en.wikipedia.org/wiki/Project_Looking_Glass

Compiz (3D Modification for Linux)
http://en.wikipedia.org/wiki/Compiz

Croquet Project (3D Modification for Linux)
http://en.wikipedia.org/wiki/Croquet_Project

==Suggestion 6: Inclusion of a scaled-down virusscanner, and other software==
There is a number of extra software that may be included with Linux-distro's. This includes programs as Sunbird, KeePass, the WeatherBug, BOINC (with climate change grid computing software) ..I would also suggest to implement a Linux-only virusscanner (to be used not in continuous and on-access scanning but only shedueled (weekly/monthly). Candidates herefore are Clam Antivirus and OpenAntivirus. In addition to a virusscanner, a open-source defragmentation program should be included.

The browser (eg Firefox) should be standardly equipped with plug ins that allow the clearing of the browsers cache after each session (to negate the effect of the harddisk slowly being clogged with unnecessairy data) and privacy measures/data erases (the plug-in should be able to perform the same tasks as the Wash 'N Go-program)
a cookie and spyware sweeper (eg as Avast Ad-aware)
the browser itself finally should drop support for the 'autocomplete'-function (to reduce risk of data-loss to third parties and malicious users)

In addition, a calender may be included (eg Mozilla Sunbird), and a program should be included to allow direct ebook-downloads. Such programs are eg [http://www.tomeraider.com/ Tomeraider] and [http://en.wikipedia.org/wiki/Mobipocket Mobipocket].

Also, text-translation tools should be implemented (eg trough on-line tools as Google Translate or -even better- off-line tools as [http://en.wikipedia.org/wiki/Comparison_of_machine_translation_applications Apertium]). A sentence-based translation device, capable of delivering direct speech translation should also be included, to allow (basic) inmediate translation assistance from the UMPC (still a small, mobile device). Programs able to provide this are eg the [http://www.engadget.com/2005/11/19/darpa-testing-laptop-based-translation-system-for-iraq/ new software program], derived from its Phraselator being build by DARPA.

'''More information''' 
Clam Antivirus 
http://en.wikipedia.org/wiki/ClamAV 

OpenAntivirus 
http://en.wikipedia.org/wiki/OpenAntiVirus 

Defragmentation utilities 
http://en.wikipedia.org/wiki/Defragmentation 

==Suggestion 7: Use of a better filesystem and X-window Desktop Environment==
It is best that instead of the standard filesystem used by most Linux distrubutions (ext3) to opt for a newer and better filesystem as Reiser4, GFS-2, ext4, ...

Also, rather than the standard X-Window Destop Environment (GNOME and KDE) in use by most Linux distributions today, it is best to switch to a different/newer Window Manager. These include Enlightenment, Blackbox, Xfce, ...

More information
Comparisation of file systems
http://en.wikipedia.org/wiki/Comparison_of_file_systems
Comparisation of X Window Desktop Environments
http://en.wikipedia.org/wiki/Comparison_of_X_Window_System_desktop_environments

==Suggestion 8: Support for speech recognition and touchscreen==
Speech recognition and the use of a touchscreen might be made standardly supported. This may allow tablet pc's or XO-1 PC's of being made smaller as no more mouse or keyboard is needed (taking up a massive amount of space). Rather than this, the speech recognition (along with a headset) may be used for writing letters, ...

More information
Ultra Mobile PC
http://en.wikipedia.org/wiki/Ultra-Mobile_PC
Tablet pc
http://en.wikipedia.org/wiki/Tablet_PC

Speech recognition
http://en.wikipedia.org/wiki/Speech_recognition
http://en.wikipedia.org/wiki/NaturallySpeaking

==Suggestion 9: Cooperation with other companies and use of Google Services==
In order to achieve the more or less complicated suggestions/tasks layed out here, it may be helpful to cooperate with Google, Canonical Ltd. As Google has many useful services for the developing world (eg Google Maps/Earth for GPS navigation, Google Mail for emailing, Google Docs, ...) a cooperation with them seems logical. Also, Canonical is already developing Goobuntu (for Google Ubuntu) in cooperation with Google; as some features of this Linux distribution may be copied for use in Linux, cooperation with them too would prove beneficial. Finally, Canonical also has a cooperation with Dell which would finish the cycle of creating a powerful alliance against companies now working together solely in the intrest of profits.

Such lucrative alliances by other companies are for example Microsoft and Novell aswell as SUSE Linux which have recently promised to work together. This event will surely put stress on Linux companies operating on their own and at the moment; especially in the intrest of bridging the digital divide, it may be best to form open-source/humanitarian linux companies-alliances.

Canonical and Google working together
http://en.wikipedia.org/wiki/Goobuntu

Goobuntu being installed on Dell computers
http://digg.com/linux_unix/Goobuntu_is_coming_

Microsoft and Novell and SUSE working together
http://www.novell.com/linux/microsoft/
http://www.novell.com/linux/

==Suggestion 10: software for GPS-tracking via WiMax and other internet connections==
A deamon should be integrated for automatic GPS/Galileo coordinate uploading. This should be automated in the deamon by the regular GPS-unit within the device (so w:GPS_tracking|no GPS-push tracker]]). GPS/Galileo coordinate uploading needs to be done automatic whenever a WiMax connection is detected with enabled internet-sharing. Also, whenever internet-connection is made via ethernet or satellite internet, the coordinates can be automatically uploaded. The deamon should include encrypted transmission, to ensure that the owners of free internet access points cannot read the information. Transmission can be done to a worldwide (or alternatively -communal-) database.

==Suggestion 11:VoIP program==
A VoIP-program allowing VoIP over WiFi/WiMax, aswell as accepting incoming phone calls and allowing outgoing one (both to regular telephones/GSM's as computers should be added. Candidates are Skype, or possibly X-lite, GnomeMeeting, Kphone or Ekiga. See [http://www.voidspace.org.uk/technology/voip_mobile.shtml this site].

A plug-in should also be created for the program, to allow automatic calling to people by issuing the command "call personname" trough the microphone.

[[Category:Design]]
[[Category:Self-sufficiency]]

Linux for mobile computing

2009-03-02T10:15:59Z

81.246.175.36: /* Suggestion 11:VoIP program */

Linux for mobile computing

2009-03-02T10:15:02Z

81.246.175.36: /* Suggestion 10: software for GPS-tracking via WiMax and other internet connections */

This article contains adjustments necessairy to the Linux OS in order to allow a special way of working with a proposed UMPC-design.

==Suggestion 1:Simplification of the Bourne Again Shell (on which Linux ;eg Fedora, ... works)==
The Bourne Again Shell has, during its long lifetime, gained several improvements and thus new programs. This has had as a result that to perform a same specific task, the user is bothered with a amount of overlapping programs.

Aldough Linux' self-correcting community might have resolved this earlier, as it is no longer actively used (now graphic interfaces are used instead) no corrections have been made for these flaws. Besides a large amount of overlapping programs, the command line interface has also a number of features which can be dismissed and replaced by other existing commands, hereby making a huge simplification possible.

Examples on this are:
*viewing of a text file: this can be done by an excessive amount of programs as vi, pico, less, more, ...

*the unnecessairy grep-command; instead locate with a specific option (thus locate -xx) can perform this function if locate is altered so it allows this

*The unnecessairy possibility of using relative pathnames, this can be replaced by only allowing absolute pathnames

*The unnecessairy pwd-command; instead the current directory can just be shown in the command line itself (similar as in DOS).

*The unnecessairy append I/O redirection and piping option; instead of using append (>>) one can simply use overwrite (>) instead

*The write permissions included with files should no longer include type-information (only gives extremely limited information and would be better checked with the filename-extension. Also, support for a sticky bit (-t permission) should be dropped. Thus instead of presenting eg drwxrw-rw- this would become rwxrw-rw-

*the possible use of general points in folders (not being part of the extension) should be dropped. Thus folders named foo.bar etc can no longer be created. This has caused allot of confusion in the past.

*finally, commands as ls for listing folders, ... are best changed to list. Changing the commands to these makes it easier to remember them.

P.S.: Text also implemented to http://en.wikipedia.org/wiki/Talk:Bash#The_BASH.27_lack_of_simplification

==Suggestion 2: Altering of the standard Linux directory tree structure==
Secondly, linux's Filesystem Hierarchy Standard' (FHS) directory tree structure should be altered, so that physical drives and imiginary folders/directory's are no longer used together. At the moment, for example physical drives are mapped in /dev while /, or /root (which are actually on a physical drive and should of been thus actually marked in a folder under /dev), ... are at a maplevel higher. It would be far better sense if simply the ports are detected and presented (thus a computer with 2 USB drives and a serial ATA-connection would get 3 folders under the root folder (/) knowingly SATA1, USB1, and USB2. The drives connected hereon would simply show their contence. The main drive (on which Fedora is placed) would then get the systems folder and user folders, ...

In addition to this renaming of the logical drives, standard names for partitions too are to be altered. Instead of the now common names (hda, sdb, hda1, hda2, ..) these are to become Partition1, Partition2, Partition3, Swap (for the swap partition), ... The extra information obtained from the hd+a-d difference is negligable, especially as only hot swappable drives should be supported anyway (which have no slave/master/auto option) and only tend to confuse users.

More information
Filesystem Hierarchy Standard (FHS)
http://www.pathname.com/fhs/

Standard linux partition names
http://linux.org.mt/article/partnames

==Suggestion 3: Dropping support for a variety of useless/surplus file formats and protocols in favor of one good file format/protocol (per type)==

Firstly, the linux-distro (eg Fedora) could drop its support for outdated/archaïc aswell as recent/new but unusable file formats. Rather than supporting a wealth of file formats, it is better to only support one good file format per type ( e.g. lossy/lossless audio encoding, lossless and lossy video encoding, compression and/or archiving format, ...). By a good file format I mean that one that has the best qualifications for which it is intented and which is open-source/free file format.

Aldough thus fewer formats can be played/executed, simplification and thus no longer supporting it would make computing simpler for the user itself and it would also allow Fedora of operating faster (as lesser code is required). Having a wealth of file formats supported not only confuses the user, but also makes him unaware what file-type to use in what situation (eg .tar.gz or .bz2 for tape archiving?) As Fedora is specifically targeted at the developing world (which still has mostly low-schooled people), this simplification may prove essential.

PS: Other Linux distributions as Gobuntu also feature solely open formats, yet this suggestion would still be different as it would allow but a single format per type, with the intent to simplify matters. This offcourse is not yet achieved in these distrubutions.

Examples are :
*.xcf and .svg for pictures
*OGG Vorbis instead of MP3, WMA, ... for lossy audio encoding
*Flac or Monkey's Audio instead of WAV, ... for lossless audio encoding
*.odt-files instead of .doc
*an open source combined compression and archiving file format as .7z to make a compressed and archived file (compressed file format alone aswell as archived file format alone not needed; when an open-source executable/install archiving format as rpm or paf aswell is supported )
*an open source archiving file format as .tar
*only UTF-8 for emails

In addition to dropping support for these file formats, allot of protocols aswell as environmentally damaging media should be dropped aswell. Besides in the intrest of the environment, the cd media (CD/DVD/DVDRAM/Blue-Ray, ...)would also be dropped as they only have a very limited lifetime, are easily corrupted and are not at all durable.

Examples:
SFTP instead of FTP
support for parallel and serial connections with devices should be dropped in favor of SATA, USB2 and FireWire800
support for USB1 should be dropped
support for appletalk should be dropped
support for the older ethernet cards/cables and protocols should be dropped, aswell as token ring ATM, ... in favor of PowerLine Communication (PLC)and gigabit ethernet
support for old forms of WiFi (802.11a-g) should be dropped in favor of WiMax and the new WiFi-protocol (802.11n) (if used)
support for Floppy's, CD/DVD/DVDRAM/Blue-Ray, should be dropped in favor of the best type of flash memory (CompactFlash?), and USB-sticks and external harddisks

Aldough this would transform the Linux version on which these suggestions are implemented more and more to a embedded form of Linux, this would actually be very beneficial. This as not only matters are simplified greatly, but also as the processor needed to run the Linux-distro can be far less potent/energy consuming than normal. A example on this can be seen with the ECB_AT91 microcomputer and the ECB_ATmega32/644 microcomputer.

More information
Free file formats
http://en.wikipedia.org/wiki/Free_file_format
Comparisation of audio codecs
http://en.wikipedia.org/wiki/Comparison_of_audio_codecs
Comparisation of container formats
http://en.wikipedia.org/wiki/Comparison_of_container_formats
Comparisation of archive formats
http://en.wikipedia.org/wiki/List_of_archive_formats
Secure FTP
http://en.wikipedia.org/wiki/SFTP
USB2
http://en.wikipedia.org/wiki/USB2#USB_2.0
FireWire 800
http://en.wikipedia.org/wiki/Firewire#FireWire_800_.28IEEE_1394b.29
Serial ATA
http://en.wikipedia.org/wiki/SATA
WiFi
http://en.wikipedia.org/wiki/Wi-Fi
Flash Memory
http://en.wikipedia.org/wiki/Flash_memory
Powerline Communication
http://en.wikipedia.org/wiki/Power_line_communication
Gigabit Ethernet
http://en.wikipedia.org/wiki/Category_5_cable
http://en.wikipedia.org/wiki/10_gigabit_Ethernet

ECB AT91 and ECB_ATmega32/644 using a embedded linux and being able to run on a 180mhz cpu and 20 mhz cpu respectively
http://en.wikipedia.org/wiki/ECB_AT91
http://en.wikipedia.org/wiki/ECB_ATmega32/644

==Suggestion 4: Dropping support for dual booting==
At the moment, most linux-distro's still support the possibility of dual booting (that is: having multiple Operating Systems on a single device/drive from which one may be selected to run on startup). I believe it is best that this dual booting feature, along with the programs which support this and which are usually standard included in a regular installation should be best dropped. This will reduce many of the hassles frequently encountered with linux installations and make sure that everything is kept simple and more efficient. Instead of this dual booting by having 2 OS' on 1 disk, random booting of other OS's may still be done, but then trough physically connecting another drive (HD, USB-stick, ...) on which an other OS is installed. Selecting which OS to load first would be done merely trough the BIOS (boot sequence can be altered here).

As people will revert to this technique, this approach would become more popular/easy and fits with the trend emerging to divert to a more easy and hot swappable form of computing/connecting of devices. As USB-sticks are rapidly becoming cheap and are already capable of storing entire OS' (eg Mac-on-a-Stick, Knoppix, LindowsLive, MojoPac, ...) and as all HD's are becoming hot swappable nowadays (trough Serial ATA/USB2/IEEE1394/...), this would prove far easier/simpler.

Having gone trough the troubles described myself with this "dual booting", lack of hot swappability (with E-IDE HD's, "jumpers" had to be manually set) and troubles/corruption of the "bootloaders/master boot record" on HD's, I am hoping that this might become a valid action which may be taken to make computers simpler/more efficient to operate.

More information:
Hot swapping and types of HD's and other devices
http://en.wikipedia.org/wiki/Serial_ATA
http://en.wikipedia.org/wiki/Hot_swapping
http://en.wikipedia.org/wiki/MojoPac
http://portableapps.com/apps/operating_systems/mac-on-stick

Live Linux disributions becoming more popular
http://en.wikipedia.org/wiki/LiveDistro
http://en.wikipedia.org/wiki/List_of_LiveDistros

Dual booting, bootloaders and the master boot record of devices
http://en.wikipedia.org/wiki/GNU_GRUB
http://en.wikipedia.org/wiki/LILO_%28boot_loader%29
http://en.wikipedia.org/wiki/Dual_booting
http://en.wikipedia.org/wiki/Master_boot_record

==Suggestion 5: Fedora's possible feature of switching to a command line-executed programs split screen configuration==
In the past, Linux developments have been focusing on improving the Graphical User Interface (GUI) of Linux, so that inexperienced users (that do not know how to use the command line) may use Linux easier. However, this implementing of the extra subroutines needed to recognise mouse control has had an adverse effect on the systems speed and performanence. Also, besides making the system slower, one wonders why such mouse control needs to implemented anyhow as if is also the cause of 2 additional disadvantages. These are

the unpracticality of using a mouse when on the road (e.g. with a portable computer, or in crammed/busy environments as with public computers at airports, libraries, subways, ..)

the slower speed at which you can operate a computer with a mouse versus with the command line, via keyboard (e.g. to perform the action of manually clicking the mouse, and not just the reduced speed of the computer)

As such, it may be better to include the option of controlling Fedora Linux via keyboard, in a split screen configuration. This configuration would be composed at one side of a command-line window (BASH, ...) and on the other side a window with the executed programs (e.g. FireFox-syle browser, OpenOffice-style text-editor, ...). This configuration proposed would make the system speedier and more stable (as the GUI itself or less subroutines in the GUI are needed) and would also still allow a great deal of eye candy. More so, with some extra work, the configuration would also make it possible to make this OS even nicer than any other existing OS as it may allow complete 3D.

Aldough the 3D features proposed may need some more time to implement, the terminal/program configuration can be implemented nearly immediatly and improve Fedora. For the 3D features, some of the coding done by OS's as IRIX and Linux-3D-modifications as Project Looking Glass can be used to create the modification to Fedora.

Finally, I wish to mention that, if you wish to implement the terminal window-program window - split screen configuration (described in the previous letter), a possible simplification of the current command line (BASH) can be implemented . This simplification of commands would allow more users to use this configuration as it would be much easier to learn the commands. Also, the combined terminal window - program window set-up would allow even further simplification. If you decide to implement the split-screen configuration and wishes to also reduce the commands used (simplify the BASH), please contact me for further assistance.

P.S.: As noted, the suggestions on the Linux-distro above can be supplied as a optional packet with Fedora, leaving the user the liberty of installing it -or not-. As such, Fedora may still be controlled by mouse for those people that really don't want to change the way how they control their computers.

More information:
Graphical User Interfaces (GUI)'s
http://en.wikipedia.org/wiki/Graphical_user_interface#Graphical_user_interfaces_compared_to_command_line_interfaces
Goobuntu (Google Linux distribution)
http://en.wikipedia.org/wiki/Goobuntu

IRIX (Unix distribution with 3D functionality)
http://en.wikipedia.org/wiki/Irix
Project Looking Glass (3D Modification for Linux)
http://en.wikipedia.org/wiki/Project_Looking_Glass

Compiz (3D Modification for Linux)
http://en.wikipedia.org/wiki/Compiz

Croquet Project (3D Modification for Linux)
http://en.wikipedia.org/wiki/Croquet_Project

==Suggestion 6: Inclusion of a scaled-down virusscanner, and other software==
There is a number of extra software that may be included with Linux-distro's. This includes programs as Sunbird, KeePass, the WeatherBug, BOINC (with climate change grid computing software) ..I would also suggest to implement a Linux-only virusscanner (to be used not in continuous and on-access scanning but only shedueled (weekly/monthly). Candidates herefore are Clam Antivirus and OpenAntivirus. In addition to a virusscanner, a open-source defragmentation program should be included.

The browser (eg Firefox) should be standardly equipped with plug ins that allow the clearing of the browsers cache after each session (to negate the effect of the harddisk slowly being clogged with unnecessairy data) and privacy measures/data erases (the plug-in should be able to perform the same tasks as the Wash 'N Go-program)
a cookie and spyware sweeper (eg as Avast Ad-aware)
the browser itself finally should drop support for the 'autocomplete'-function (to reduce risk of data-loss to third parties and malicious users)

In addition, a calender may be included (eg Mozilla Sunbird), and a program should be included to allow direct ebook-downloads. Such programs are eg [http://www.tomeraider.com/ Tomeraider] and [http://en.wikipedia.org/wiki/Mobipocket Mobipocket].

Also, text-translation tools should be implemented (eg trough on-line tools as Google Translate or -even better- off-line tools as [http://en.wikipedia.org/wiki/Comparison_of_machine_translation_applications Apertium]). A sentence-based translation device, capable of delivering direct speech translation should also be included, to allow (basic) inmediate translation assistance from the UMPC (still a small, mobile device). Programs able to provide this are eg the [http://www.engadget.com/2005/11/19/darpa-testing-laptop-based-translation-system-for-iraq/ new software program], derived from its Phraselator being build by DARPA.

'''More information''' 
Clam Antivirus 
http://en.wikipedia.org/wiki/ClamAV 

OpenAntivirus 
http://en.wikipedia.org/wiki/OpenAntiVirus 

Defragmentation utilities 
http://en.wikipedia.org/wiki/Defragmentation 

==Suggestion 7: Use of a better filesystem and X-window Desktop Environment==
It is best that instead of the standard filesystem used by most Linux distrubutions (ext3) to opt for a newer and better filesystem as Reiser4, GFS-2, ext4, ...

Also, rather than the standard X-Window Destop Environment (GNOME and KDE) in use by most Linux distributions today, it is best to switch to a different/newer Window Manager. These include Enlightenment, Blackbox, Xfce, ...

More information
Comparisation of file systems
http://en.wikipedia.org/wiki/Comparison_of_file_systems
Comparisation of X Window Desktop Environments
http://en.wikipedia.org/wiki/Comparison_of_X_Window_System_desktop_environments

==Suggestion 8: Support for speech recognition and touchscreen==
Speech recognition and the use of a touchscreen might be made standardly supported. This may allow tablet pc's or XO-1 PC's of being made smaller as no more mouse or keyboard is needed (taking up a massive amount of space). Rather than this, the speech recognition (along with a headset) may be used for writing letters, ...

More information
Ultra Mobile PC
http://en.wikipedia.org/wiki/Ultra-Mobile_PC
Tablet pc
http://en.wikipedia.org/wiki/Tablet_PC

Speech recognition
http://en.wikipedia.org/wiki/Speech_recognition
http://en.wikipedia.org/wiki/NaturallySpeaking

==Suggestion 9: Cooperation with other companies and use of Google Services==
In order to achieve the more or less complicated suggestions/tasks layed out here, it may be helpful to cooperate with Google, Canonical Ltd. As Google has many useful services for the developing world (eg Google Maps/Earth for GPS navigation, Google Mail for emailing, Google Docs, ...) a cooperation with them seems logical. Also, Canonical is already developing Goobuntu (for Google Ubuntu) in cooperation with Google; as some features of this Linux distribution may be copied for use in Linux, cooperation with them too would prove beneficial. Finally, Canonical also has a cooperation with Dell which would finish the cycle of creating a powerful alliance against companies now working together solely in the intrest of profits.

Such lucrative alliances by other companies are for example Microsoft and Novell aswell as SUSE Linux which have recently promised to work together. This event will surely put stress on Linux companies operating on their own and at the moment; especially in the intrest of bridging the digital divide, it may be best to form open-source/humanitarian linux companies-alliances.

Canonical and Google working together
http://en.wikipedia.org/wiki/Goobuntu

Goobuntu being installed on Dell computers
http://digg.com/linux_unix/Goobuntu_is_coming_

Microsoft and Novell and SUSE working together
http://www.novell.com/linux/microsoft/
http://www.novell.com/linux/

==Suggestion 10: software for GPS-tracking via WiMax and other internet connections==
A deamon should be integrated for automatic GPS/Galileo coordinate uploading. This should be automated in the deamon by the regular GPS-unit within the device (so w:GPS_tracking|no GPS-push tracker]]). GPS/Galileo coordinate uploading needs to be done automatic whenever a WiMax connection is detected with enabled internet-sharing. Also, whenever internet-connection is made via ethernet or satellite internet, the coordinates can be automatically uploaded. The deamon should include encrypted transmission, to ensure that the owners of free internet access points cannot read the information. Transmission can be done to a worldwide (or alternatively -communal-) database.

==Suggestion 11:VoIP program==
A VoIP-program allowing VoIP over WiFi/WiMax, aswell as accepting incoming phone calls and allowing outgoing one (both to regular telephones/GSM's as computers should be added. Candidates are Skype, or possibly X-lite, GnomeMeeting, Kphone or Ekiga.

[[Category:Design]]
[[Category:Self-sufficiency]]

Linux for mobile computing

2009-03-02T09:47:30Z

81.246.175.36: /* Suggestion 9: Cooperation with other companies and use of Google Services */

Linux for mobile computing

2008-11-27T12:13:04Z

81.246.144.72: /* Suggestion 6: Inclusion of a scaled-down virusscanner, and other software */

Linux for mobile computing

2008-11-27T12:09:28Z

81.246.144.72: /* Suggestion 6: Inclusion of a scaled-down virusscanner, and other software */

This article contains adjustments necessairy to the Linux OS in order to allow a special way of working with a proposed UMPC-design.

==Suggestion 1:Simplification of the Bourne Again Shell (on which Linux ;eg Fedora, ... works)==
The Bourne Again Shell has, during its long lifetime, gained several improvements and thus new programs. This has had as a result that to perform a same specific task, the user is bothered with a amount of overlapping programs.

Aldough Linux' self-correcting community might have resolved this earlier, as it is no longer actively used (now graphic interfaces are used instead) no corrections have been made for these flaws. Besides a large amount of overlapping programs, the command line interface has also a number of features which can be dismissed and replaced by other existing commands, hereby making a huge simplification possible.

Examples on this are:
*viewing of a text file: this can be done by an excessive amount of programs as vi, pico, less, more, ...

*the unnecessairy grep-command; instead locate with a specific option (thus locate -xx) can perform this function if locate is altered so it allows this

*The unnecessairy possibility of using relative pathnames, this can be replaced by only allowing absolute pathnames

*The unnecessairy pwd-command; instead the current directory can just be shown in the command line itself (similar as in DOS).

*The unnecessairy append I/O redirection and piping option; instead of using append (>>) one can simply use overwrite (>) instead

*The write permissions included with files should no longer include type-information (only gives extremely limited information and would be better checked with the filename-extension. Also, support for a sticky bit (-t permission) should be dropped. Thus instead of presenting eg drwxrw-rw- this would become rwxrw-rw-

*the possible use of general points in folders (not being part of the extension) should be dropped. Thus folders named foo.bar etc can no longer be created. This has caused allot of confusion in the past.

*finally, commands as ls for listing folders, ... are best changed to list. Changing the commands to these makes it easier to remember them.

P.S.: Text also implemented to http://en.wikipedia.org/wiki/Talk:Bash#The_BASH.27_lack_of_simplification

==Suggestion 2: Altering of the standard Linux directory tree structure==
Secondly, linux's Filesystem Hierarchy Standard' (FHS) directory tree structure should be altered, so that physical drives and imiginary folders/directory's are no longer used together. At the moment, for example physical drives are mapped in /dev while /, or /root (which are actually on a physical drive and should of been thus actually marked in a folder under /dev), ... are at a maplevel higher. It would be far better sense if simply the ports are detected and presented (thus a computer with 2 USB drives and a serial ATA-connection would get 3 folders under the root folder (/) knowingly SATA1, USB1, and USB2. The drives connected hereon would simply show their contence. The main drive (on which Fedora is placed) would then get the systems folder and user folders, ...

In addition to this renaming of the logical drives, standard names for partitions too are to be altered. Instead of the now common names (hda, sdb, hda1, hda2, ..) these are to become Partition1, Partition2, Partition3, Swap (for the swap partition), ... The extra information obtained from the hd+a-d difference is negligable, especially as only hot swappable drives should be supported anyway (which have no slave/master/auto option) and only tend to confuse users.

More information
Filesystem Hierarchy Standard (FHS)
http://www.pathname.com/fhs/

Standard linux partition names
http://linux.org.mt/article/partnames

==Suggestion 3: Dropping support for a variety of useless/surplus file formats and protocols in favor of one good file format/protocol (per type)==

Firstly, the linux-distro (eg Fedora) could drop its support for outdated/archaïc aswell as recent/new but unusable file formats. Rather than supporting a wealth of file formats, it is better to only support one good file format per type ( e.g. lossy/lossless audio encoding, lossless and lossy video encoding, compression and/or archiving format, ...). By a good file format I mean that one that has the best qualifications for which it is intented and which is open-source/free file format.

Aldough thus fewer formats can be played/executed, simplification and thus no longer supporting it would make computing simpler for the user itself and it would also allow Fedora of operating faster (as lesser code is required). Having a wealth of file formats supported not only confuses the user, but also makes him unaware what file-type to use in what situation (eg .tar.gz or .bz2 for tape archiving?) As Fedora is specifically targeted at the developing world (which still has mostly low-schooled people), this simplification may prove essential.

PS: Other Linux distributions as Gobuntu also feature solely open formats, yet this suggestion would still be different as it would allow but a single format per type, with the intent to simplify matters. This offcourse is not yet achieved in these distrubutions.

Examples are :
*.xcf and .svg for pictures
*OGG Vorbis instead of MP3, WMA, ... for lossy audio encoding
*Flac or Monkey's Audio instead of WAV, ... for lossless audio encoding
*.odt-files instead of .doc
*an open source combined compression and archiving file format as .7z to make a compressed and archived file (compressed file format alone aswell as archived file format alone not needed; when an open-source executable/install archiving format as rpm or paf aswell is supported )
*an open source archiving file format as .tar
*only UTF-8 for emails

In addition to dropping support for these file formats, allot of protocols aswell as environmentally damaging media should be dropped aswell. Besides in the intrest of the environment, the cd media (CD/DVD/DVDRAM/Blue-Ray, ...)would also be dropped as they only have a very limited lifetime, are easily corrupted and are not at all durable.

Examples:
SFTP instead of FTP
support for parallel and serial connections with devices should be dropped in favor of SATA, USB2 and FireWire800
support for USB1 should be dropped
support for appletalk should be dropped
support for the older ethernet cards/cables and protocols should be dropped, aswell as token ring ATM, ... in favor of PowerLine Communication (PLC)and gigabit ethernet
support for old forms of WiFi (802.11a-g) should be dropped in favor of WiMax and the new WiFi-protocol (802.11n) (if used)
support for Floppy's, CD/DVD/DVDRAM/Blue-Ray, should be dropped in favor of the best type of flash memory (CompactFlash?), and USB-sticks and external harddisks

Aldough this would transform the Linux version on which these suggestions are implemented more and more to a embedded form of Linux, this would actually be very beneficial. This as not only matters are simplified greatly, but also as the processor needed to run the Linux-distro can be far less potent/energy consuming than normal. A example on this can be seen with the ECB_AT91 microcomputer and the ECB_ATmega32/644 microcomputer.

More information
Free file formats
http://en.wikipedia.org/wiki/Free_file_format
Comparisation of audio codecs
http://en.wikipedia.org/wiki/Comparison_of_audio_codecs
Comparisation of container formats
http://en.wikipedia.org/wiki/Comparison_of_container_formats
Comparisation of archive formats
http://en.wikipedia.org/wiki/List_of_archive_formats
Secure FTP
http://en.wikipedia.org/wiki/SFTP
USB2
http://en.wikipedia.org/wiki/USB2#USB_2.0
FireWire 800
http://en.wikipedia.org/wiki/Firewire#FireWire_800_.28IEEE_1394b.29
Serial ATA
http://en.wikipedia.org/wiki/SATA
WiFi
http://en.wikipedia.org/wiki/Wi-Fi
Flash Memory
http://en.wikipedia.org/wiki/Flash_memory
Powerline Communication
http://en.wikipedia.org/wiki/Power_line_communication
Gigabit Ethernet
http://en.wikipedia.org/wiki/Category_5_cable
http://en.wikipedia.org/wiki/10_gigabit_Ethernet

ECB AT91 and ECB_ATmega32/644 using a embedded linux and being able to run on a 180mhz cpu and 20 mhz cpu respectively
http://en.wikipedia.org/wiki/ECB_AT91
http://en.wikipedia.org/wiki/ECB_ATmega32/644

==Suggestion 4: Dropping support for dual booting==
At the moment, most linux-distro's still support the possibility of dual booting (that is: having multiple Operating Systems on a single device/drive from which one may be selected to run on startup). I believe it is best that this dual booting feature, along with the programs which support this and which are usually standard included in a regular installation should be best dropped. This will reduce many of the hassles frequently encountered with linux installations and make sure that everything is kept simple and more efficient. Instead of this dual booting by having 2 OS' on 1 disk, random booting of other OS's may still be done, but then trough physically connecting another drive (HD, USB-stick, ...) on which an other OS is installed. Selecting which OS to load first would be done merely trough the BIOS (boot sequence can be altered here).

As people will revert to this technique, this approach would become more popular/easy and fits with the trend emerging to divert to a more easy and hot swappable form of computing/connecting of devices. As USB-sticks are rapidly becoming cheap and are already capable of storing entire OS' (eg Mac-on-a-Stick, Knoppix, LindowsLive, MojoPac, ...) and as all HD's are becoming hot swappable nowadays (trough Serial ATA/USB2/IEEE1394/...), this would prove far easier/simpler.

Having gone trough the troubles described myself with this "dual booting", lack of hot swappability (with E-IDE HD's, "jumpers" had to be manually set) and troubles/corruption of the "bootloaders/master boot record" on HD's, I am hoping that this might become a valid action which may be taken to make computers simpler/more efficient to operate.

More information:
Hot swapping and types of HD's and other devices
http://en.wikipedia.org/wiki/Serial_ATA
http://en.wikipedia.org/wiki/Hot_swapping
http://en.wikipedia.org/wiki/MojoPac
http://portableapps.com/apps/operating_systems/mac-on-stick

Live Linux disributions becoming more popular
http://en.wikipedia.org/wiki/LiveDistro
http://en.wikipedia.org/wiki/List_of_LiveDistros

Dual booting, bootloaders and the master boot record of devices
http://en.wikipedia.org/wiki/GNU_GRUB
http://en.wikipedia.org/wiki/LILO_%28boot_loader%29
http://en.wikipedia.org/wiki/Dual_booting
http://en.wikipedia.org/wiki/Master_boot_record

==Suggestion 5: Fedora's possible feature of switching to a command line-executed programs split screen configuration==
In the past, Linux developments have been focusing on improving the Graphical User Interface (GUI) of Linux, so that inexperienced users (that do not know how to use the command line) may use Linux easier. However, this implementing of the extra subroutines needed to recognise mouse control has had an adverse effect on the systems speed and performanence. Also, besides making the system slower, one wonders why such mouse control needs to implemented anyhow as if is also the cause of 2 additional disadvantages. These are

the unpracticality of using a mouse when on the road (e.g. with a portable computer, or in crammed/busy environments as with public computers at airports, libraries, subways, ..)

the slower speed at which you can operate a computer with a mouse versus with the command line, via keyboard (e.g. to perform the action of manually clicking the mouse, and not just the reduced speed of the computer)

As such, it may be better to include the option of controlling Fedora Linux via keyboard, in a split screen configuration. This configuration would be composed at one side of a command-line window (BASH, ...) and on the other side a window with the executed programs (e.g. FireFox-syle browser, OpenOffice-style text-editor, ...). This configuration proposed would make the system speedier and more stable (as the GUI itself or less subroutines in the GUI are needed) and would also still allow a great deal of eye candy. More so, with some extra work, the configuration would also make it possible to make this OS even nicer than any other existing OS as it may allow complete 3D.

Aldough the 3D features proposed may need some more time to implement, the terminal/program configuration can be implemented nearly immediatly and improve Fedora. For the 3D features, some of the coding done by OS's as IRIX and Linux-3D-modifications as Project Looking Glass can be used to create the modification to Fedora.

Finally, I wish to mention that, if you wish to implement the terminal window-program window - split screen configuration (described in the previous letter), a possible simplification of the current command line (BASH) can be implemented . This simplification of commands would allow more users to use this configuration as it would be much easier to learn the commands. Also, the combined terminal window - program window set-up would allow even further simplification. If you decide to implement the split-screen configuration and wishes to also reduce the commands used (simplify the BASH), please contact me for further assistance.

P.S.: As noted, the suggestions on the Linux-distro above can be supplied as a optional packet with Fedora, leaving the user the liberty of installing it -or not-. As such, Fedora may still be controlled by mouse for those people that really don't want to change the way how they control their computers.

More information:
Graphical User Interfaces (GUI)'s
http://en.wikipedia.org/wiki/Graphical_user_interface#Graphical_user_interfaces_compared_to_command_line_interfaces
Goobuntu (Google Linux distribution)
http://en.wikipedia.org/wiki/Goobuntu

IRIX (Unix distribution with 3D functionality)
http://en.wikipedia.org/wiki/Irix
Project Looking Glass (3D Modification for Linux)
http://en.wikipedia.org/wiki/Project_Looking_Glass

Compiz (3D Modification for Linux)
http://en.wikipedia.org/wiki/Compiz

Croquet Project (3D Modification for Linux)
http://en.wikipedia.org/wiki/Croquet_Project

==Suggestion 6: Inclusion of a scaled-down virusscanner, and other software==
There is a number of extra software that may be included with Linux-distro's. This includes programs as Sunbird, KeePass, the WeatherBug, BOINC (with climate change grid computing software) ..I would also suggest to implement a Linux-only virusscanner (to be used not in continuous and on-access scanning but only shedueled (weekly/monthly). Candidates herefore are Clam Antivirus and OpenAntivirus. In addition to a virusscanner, a open-source defragmentation program should be included.

The browser (eg Firefox) should be standardly equipped with plug ins that allow the clearing of the browsers cache after each session (to negate the effect of the harddisk slowly being clogged with unnecessairy data) and privacy measures/data erases (the plug-in should be able to perform the same tasks as the Wash 'N Go-program)
a cookie and spyware sweeper (eg as Avast Ad-aware)
the browser itself finally should drop support for the 'autocomplete'-function (to reduce risk of data-loss to third parties and malicious users)

In addition, a calender may be included (eg Mozilla Sunbird), and a program should be included to allow direct ebook-downloads. Such programs are eg [http://www.tomeraider.com/ Tomeraider] and [http://en.wikipedia.org/wiki/Mobipocket Mobipocket].

Also, text-translation tools should be implemented (eg trough on-line tools as Google Translate or -even better- off-line tools as [http://en.wikipedia.org/wiki/Comparison_of_machine_translation_applications Apertium]). A sentence-based translation device, capable of delivering direct speech translation should also be included, to allow (basic) inmediate translation assistance from the UMPC (still a small, mobile device). Programs able to provide this are eg the new software program, derived from its Phraselator being build by DARPA.

More information
Clam Antivirus
http://en.wikipedia.org/wiki/ClamAV

OpenAntivirus
http://en.wikipedia.org/wiki/OpenAntiVirus

Defragmentation utilities
http://en.wikipedia.org/wiki/Defragmentation

==Suggestion 7: Use of a better filesystem and X-window Desktop Environment==
It is best that instead of the standard filesystem used by most Linux distrubutions (ext3) to opt for a newer and better filesystem as Reiser4, GFS-2, ext4, ...

Also, rather than the standard X-Window Destop Environment (GNOME and KDE) in use by most Linux distributions today, it is best to switch to a different/newer Window Manager. These include Enlightenment, Blackbox, Xfce, ...

More information
Comparisation of file systems
http://en.wikipedia.org/wiki/Comparison_of_file_systems
Comparisation of X Window Desktop Environments
http://en.wikipedia.org/wiki/Comparison_of_X_Window_System_desktop_environments

==Suggestion 8: Support for speech recognition and touchscreen==
Speech recognition and the use of a touchscreen might be made standardly supported. This may allow tablet pc's or XO-1 PC's of being made smaller as no more mouse or keyboard is needed (taking up a massive amount of space). Rather than this, the speech recognition (along with a headset) may be used for writing letters, ...

More information
Ultra Mobile PC
http://en.wikipedia.org/wiki/Ultra-Mobile_PC
Tablet pc
http://en.wikipedia.org/wiki/Tablet_PC

Speech recognition
http://en.wikipedia.org/wiki/Speech_recognition
http://en.wikipedia.org/wiki/NaturallySpeaking

==Suggestion 9: Cooperation with other companies and use of Google Services==
In order to achieve the more or less complicated suggestions/tasks layed out here, it may be helpful to cooperate with Google, Canonical Ltd. As Google has many useful services for the developing world (eg Google Maps/Earth for GPS navigation, Google Mail for emailing, Google Docs, ...) a cooperation with them seems logical. Also, Canonical is already developing Goobuntu (for Google Ubuntu) in cooperation with Google; as some features of this Linux distribution may be copied for use in Linux, cooperation with them too would prove beneficial. Finally, Canonical also has a cooperation with Dell which would finish the cycle of creating a powerful alliance against companies now working together solely in the intrest of profits.

Such lucrative alliances by other companies are for example Microsoft and Novell aswell as SUSE Linux which have recently promised to work together. This event will surely put stress on Linux companies operating on their own and at the moment; especially in the intrest of bridging the digital divide, it may be best to form open-source/humanitarian linux companies-alliances.

Canonical and Google working together
http://en.wikipedia.org/wiki/Goobuntu

Goobuntu being installed on Dell computers
http://digg.com/linux_unix/Goobuntu_is_coming_

Microsoft and Novell and SUSE working together
http://www.novell.com/linux/microsoft/
http://www.novell.com/linux/

[[Category:Designs]]
[[Category:Self-sufficiency]]

Domestic house food production system

2008-09-07T07:52:10Z

81.246.134.241: /* More information */

This article is about making a food production system for domestic houses. It has been taken from [http://kvdp.blogspot.com my website].

==Why needed ?==
At the moment, environmental pollution trough agriculture (eg by pesticides, nutrient wash-outs, GHG-emissions) is of a major concern to everyone on earth. As such, the governments of many countries around the world are looking into new ways on how this matter can be adressed. In addition, allot of organisations and companies are trying to create and/or figure out systems on how the matter can be solved.

Vertical farming, which is being concretely worked out by Prof. Despommier might prove one of the answers to phase out agricultural pollution, aswell as food security, and in cooperation with other technology (for staple crop production) may be rigid enough to completely alter the way how we produce food.

However, it is obvious that the Vertical Farm alone will not be enough to make a viable alternative for traditional agriculture. This as it is obvious that more and different crops will need to be grown, including financially unatractive staple crops (hereby eliminating the possibility of growing it in the Vertical Farm).

==Overview==
As such, I myself have been working on a system to produce the staple crops in domestic homes, hereby allowing financially unattractive crops to be grown by the consumer himself, retaining most environmental advantages also present in the Vertical Farm aswell as giving the consumer some other benefits. As such, my system could be used in conjunction to mr. Despommier's Vertical Farms. In addition to domestic homes, the system might also be integrated into campers and (large) vessels that make long travels (eg container vessels, bulkstorage vessels, roro-ships, aircraft carriers (eg USS Nimitz/Truman, Kitty Hawk and other CV-class ships), large hospital ships as the 'Oswaldo Cruz', ...). Practical examples have already been given by eg the "geWOONboot-team" (see link below). The latter would however not be the primary target group.

==Advantages==
The main advantages of my system are:
* despite being less cost-effective than the Vertical Farm in terms of financial profits, it might be still cheaper to grow these crops than simply buying it from the supermarket (in the long run)
* it would give the consumer more self sufficiency, being helpful in certain situations
* it would make some rooms in the house more appealing
* the plants may be used to allow natural ventilation and cooling, ... (see log id's-model home)
* it would filter out several toxic gases, which are always present within the house because of its presence in construction materials and from the outside (road transport, energy generation)

Any downsides to normally present in regular agriculture (physical work, ...) is completely eliminated trough good plant setup (e.g. by permaculture/agro-ecosystem approaches), a more industrial approach (e.g. using abiotic substrates; as too present in the approach followed by Koppert Cress), automation of systems, low-cost systems and increased efficiency systems (eg as seen in the solar gardening/intensive farming methods of Leander and Gretchen Poisson), ...

My system is similar to the one used by BioTecture in their 'Earth Ships' yet should be more easily to implement (being set-up as a assembly kit). In set-up, it would be much similar to the Integral Urban House-approach by the Farralones Institute.

The set-up
Firstly, focus will go on whether regular greenhouses may be used (eg in penthouse-flats, ...). If so, soy may be grown which allows a variety of foods (tofu/seitan/natto/tempeh/...). It should be researched whether

* enough light is present in the area/flat itself
* what the surface area needs to be for the soy to feed the people
* how much energy is to be used

Depending on the outcome, other cultivation means/crops may be used (see below) or a partial system may be worked out (eg with a small greenhouse on top of the house in which only certain, non-staple crops can be grown (supplementary crops for additional nutrition, ...). Perhaps that some techniques for directing light (eg Parans-system) may be used for lower food-production rooms. Examples are available from Log Id, Biotecture, Raymond Ip's vertical farm design, ...
If not possible, mushroom growing (and perhaps algae) can be used in conjunction with extra crops to attain a full meal (mineral requirements per day, ...). The algae and mushrooms to be used are to be probably the same as used in meat replacements (valess and quorn); if not enough in minerals/calories, ... , several type of (less known) mushrooms may be required. Shii-take mushrooms have been described in the anti-aging plan as supercharger-foods, yet may still lack in nutrients (other mushrooms will need to be found).

Another possibility is the set-up of a aquatic system. This may allow fish-growing (source of selenium), aswell as nori/kombu (source of vitamin B6 and calcium) and other supercharger-foods. Saline crops are well combinable in a aquatic system, where it may be combined with fish-growing (in aquaculture). A practical example to this is the project undertaken by the Belgian "Provinicaal Proefcentrum voor de Groenteteelt" which is mixing a system of tilapia-fish cultivation with tomato growing (conducted at the Improvement Centre in Bleiswijk). Another practical example is available from the Integral Urban House. Here fish and crustaceans are grown in houses. The system is designed by Sterling Bunnell and includes raising native water organisms such as Sacramento blackfish, rainbow trout, and Pacifasticus (a genus of crayfish that can grow to lobster size). The pond is also stuffed with daphnia and algae and Bunnell's "livestock" feeds on worms and bees raised by Integral Urban House staffers. The worms are grown in sawdust-covered trays mounted below IUH chicken cages to catch the birds' droppings. (The worms thus serve as both fish food and "workers" that speed the production of compost from the chicken manure. At present, Bunnell is also installing a biological filtration system designed to remove growth-inhibiting wastes (produced by the fish) from the pond's water. The system is stunningly simple: It's nothing more than a bed of oyster shells—coated with bacteria that feed upon (and filter out) impurities in the water—through which the body of water's effluent is passed. If it works, the filtering system should significantly increase the yield (by weight) of fish from the small pond.

Finally, the cultivation of single cellular organisms (eg in bioreactors, ...) may also be a possibility. Brewers yeast (a supercharger-food), which is rich in thiamin, folacin, ... can be set-up here. Perhaps that certain yeast-strains may offer even higher nutrition-values.

The extra nutrients may be derived from extra crops that improve nutrient absorption, fix Anemia and/or supply nutrients themselves; besides being easy to grow (low light requirements, abundant growth, ...). These include foremost Spirulina platensis (a small aquarium is required herefore), and Yellow Gentian (Gentiana lutea). In addition, Siberian Ginseng (Eleutherococcus senticosus), Armoracia rusticana and Urtica dioica may be used. Finally, citrus aurantium may be used occasionally to allow people to implement trainingschedules to grow more muscle/become fitter (when combined with a proteine-rich/carbohydrate-poor diet). It can also be used to allow people to change their activity level/metabolism gradually. PS: aldough ephedra might also be used for this latter, citrus aurantium is a far better/safer alternative, allowing increased lypolyse, thermogenese, increased muscle-formation/performance and decreased anxiety/heart problems

===Other crops===
Further crops that may be used and which need to looked into are:

Angelica sinensis, Equisetum arvense, Medicago sativa, Goldenseal (Hydrastis canadensis), Maca (Lepidum meyenii), Petroselinum crispum, Rubus idaeus, Rosa canina, Taraxacum officinalis, Trigonella foenum graecum.

Guarana and Kombucha may finally also be made into drinks and can be used as additif (dough not on its own).

Finally, the biggest addition of the system would be its nutrient recycling; this would be done by compostation (composting loo, bioreactor and specialised organisms).

==Advanced cooking techniques==
The system does not foresee the use of cooking oils or fats. This not only makes the food healthier, but as oils are always have a limited storage/shelf life, it also makes the food production system to be more efficient. Instead of using oils/butter or fats to cook, techniques and cooking utensils that do not require oil are to be used. Examples for these are boing, steaming, ... (eg trough rice cooker or in a pot over a plain fire, food steamer). Utensils as steamers finally also allow all nutrients to be consumed as they can catch all the water vapour that normally disappears (hereby making sure that nutrient deficiency is less likely (if the diet/crops are selected correctly).

==Recycling system==
The system is to depend on heavily on nutrient recycling (to make sure the nutrients remain in the system). This is done by compost toilets and or combined with other composting techniques (regular composting, vermicomposting, mushroom composting or Bokashi composting). All latter composting techniques allow the composting system part to take up less space and may be more efficient. However, Bokashi and mushroom compsting may only be applied with easy decomposable material (thus no bones, or fish/meat). As such, they will only be used in conjunction with the composting toilet/regular composting system to reduce the strain on the main composting system. Seperating the manure may be applied herefore (see links below for more detailed information about the systems).

==Cooperation==
Possible cooperation for the system can be had from BioTecture, and a number of other organisations with similar projects (eg Zonneterp, Raymond Kurzweil's organisation "Ray and Terry's; see http://www.kurzweiltech.com/ktiflash.html , ...).

==More information==
*The alignment of house and food system can be determined with info from following document:
[[General room orientation in house construction]]-document
*Vertical Farming explained
http://en.wikipedia.org/wiki/Vertical_farming
*Vertical Farm-project by Mr. Despommier
http://verticalfarm.com/
*BioTecture's Earth Ships (provides an impression for my altered system)
http://en.wikipedia.org/wiki/Earthship
http://www.earthship.net/modules.php?name=News&file=article&sid=14
*Raymond Ip's Vertical farm design (see also my general model on room orientation for more info)
http://www.verticalfarm.com/images/design/ip/Waimond_Ip.pdf
*geWOONboot-team
http://www.gewoonboot.nl/totalframeset.htm
*Log Id's plant-home
http://www.architecture.uwaterloo.ca/faculty_projects/terri/ds/LogID_BWG_Building.PDF

*Companies to aid in set up food production system
http://www.wolvertonenvironmental.com/
http://www.spaceflight.esa.int/users/index.cfm?act=default.page&level=11&page=783

*Meat analogues as example for primary crop
http://en.wikipedia.org/wiki/Meat_substitutes

*Recyling system
http://en.wikipedia.org/wiki/Composting_toilet (regular composting toilet)
http://www.appropedia.org/Vermicomposting_toilet (composting toilet combined with vermicomposting)
*Bioreactors to create more efficient nutrient recycling system
http://en.wikipedia.org/wiki/Biochemical_engineering#The_bioreactor
http://ecls.esa.int/ecls/?p=melissa

*Regular composting
http://en.wikipedia.org/wiki/Composting
*Vermicomposting
http://en.wikipedia.org/wiki/Vermicompost
*Mushroom composting (perhaps usable for composting the vegatble compost). May be especially useful if mushrooms (eg Shii-take) are to be grown within the system. Perhaps not sturdy enough dough (easy risk at failure system) to use.
http://www.shroomery.org/forums/showflat.php/Cat/0/Number/3768825/Main/3768324/
*Bokashi recycling system (makes instant compost tea; very efficient)
http://www.instructables.com/id/Organic-feriliser-from-kitchen-refuse/
http://www.treehugger.com/files/2005/06/bokashi_compost_1.php

*Rice cookers and food steamers
http://en.wikipedia.org/wiki/Rice_cooker
http://en.wikipedia.org/wiki/Food_steamer

*Koppert Cress abiotic substrate growing for plants
http://www.koppertcress.com/index.php?PageID=970
http://www.koppertcress.nl/images/private/Verpakkingen_UK.pdf

*Usable saline crops for aquatic system
http://www.west-vlaanderen.be/upload/povlt/PDF/PERS%20en%20NIEUWS/2007/studiedag-aquacultuur/8_zilteteelten.pdf
*Improvement Centre Bleiswijk conducting tomato/tilapia growing (Proeftuin Aquacultuur’)
http://www.improvementcentre.com/english/Frameset%20Afdelingen.htm

*Integral Urban House' Urban Gardening. The systems noted are stated to be able to be integrated into small buildings. May also be used to decrease work to 15mins
http://www.motherearthnews.com/Green-Homes/1976-11-01/The-Integral-Urban-House.aspx?page=2
*Other books on decreasing costs and making the system more efficient:
**City People's Book of Raising Food by Helga Olkowski
Solar Gardening: Growing Vegetables Year-Round the American Intensive Way by Leandre Poisson and Gretchen Vogel Poisson (see http://www.amazon.com/Solar-Gardening-Vegetables-Year-Round-Independent/dp/0930031695)

*Additional crops that can be used to substitite the diet
http://www.lifepositive.com/body/holistic-recipes/recipes.html

**Leander and Gretchen Poisson's increased efficiency/low-cost gardening
http://www.cfamilyresources.com/products/books/solar_gardening.htm
**The time Saving Garden by Reader's Digest
**Other cost-decreasing solar techniques (diy heat store), portraied and build in practice by the New House Farm's "It's not easy being green"-team
This heat store can be used to heat the greenhouse-part of the food system (if this is to be used/possible), or (eg with the ships mentioned), heat other rooms used in the food production system and/or structures themselves
http://www.itsnoteasybeinggreen.org/forum/viewtopic.php?p=99374&sid=fe9009cedff17d83534b3d9d6dae4a29
http://www.growfruitandveg.co.uk/grapevine/general-chitchat/its-not-easy-being-green_5930.html
http://forum.caithness.org/archive/index.php/t-22978.html
http://www.growfruitandveg.co.uk/grapevine/general-chitchat/its-not-easy-being-green_5930.html#post83959
http://forum.caithness.org/archive/index.php/t-22978.html

*[http://docs.google.com/Doc?id=dcwtr665_228g2nf8bg5 Document with extra info on food production and how to set-up the diets for the users of the system]

*Zonneterp
http://www.zonneterp.nl/english/index_uk.html

*Recommended reading to understand some proposals
**"The Anti-Aging Plan: Strategies and Recipes for extending your Healthy years by Lisa and Roy Walford", in particular chapter 9 (superchargers) and appendix B (p291).
**"The Okinawa-program: Learn the secrets to healthy longevity by Willcox, Willcox and Suzuki" (in particular chapter 5 and 6 about special herbs and foods used in the orient/Okinawa)
**"Eat to live by Joel Fuhrman"
**"Superfoods and/or superfoods healthstyle by Stephen G Pratt and Cathy Matthews" (for other general info on which the foods are to be chosen, depending on contents). Perhaps that
** "The China Study: The Most Comprehensive Study of Nutrition Ever Conducted and the Startling Implications for Diet, Weight Loss and Long-term Health" by T. Colin Campbell and The Super Foods book by Kristin Gerstley may also be worthwhile to read, yet they may not be necessairy to understand how I would set-up the system.

[[Category:Food]]

Domestic house food production system

2008-09-07T07:51:07Z

81.246.134.241: /* More information */

Cheap acquiring of towns and large buildings

2008-08-25T07:39:53Z

81.246.150.225: /* More information */

This article is about brainstorming about the best/cheapst ways to obtain shelter.

==Ways==
Getting a shelter can be done as simply as by looking for an old (empty) industrial building/complex and renting it (this may be done even in Europe for as little as 200$/month). Such large buildings may be shared by an entire group of fellow room mates/co-payers.

In addition, complete abandoned villages may be usurped (dough this will require a fair amount of planning and is best done with a large group of decision-makers). It also allows other (poorer) people to be housed (eg in return for work provided).

==In practice==
Still usable (sturdy constructed) deserted towns (usually refered to as 'ghost towns') in Africa and abroad can be used to house refugees and poor people in Africa/developing world. Refugees (without much possession or any roofing) and coming from insecure parts (eg in Angola, Sudan, Chad, Central African Republic, DR Congo, ...) may be relocated to these towns in Africa/other continents to repopulate them and help out in the reforestation of the areas around the ghost town.

The reforestation programs may be conducted within Kyoto's Clean Development Mechanism-program to allow the projects to be self-sustaining (and perhaps even profitable). In addition, the ghost towns themselves can be fitted with the needed systems for life support using low-cost microgeneration and local food production system. Drinkable water and sanitation too may be produced on-site. More information on setting up [http://en.wikipedia.org/wiki/Off-the-grid off-the-grid] homes may be found
at [[Topic:Self-sufficiency]] and at the [http://en.wikipedia.org/wiki/Microgeneration wikipedia]

Even more information on decreasing the cost of the required systems can be found at an article I wrote. See [http://docs.google.com/Doc?id=dcwtr665_219hw58sfck this article at my website]. Concrete villages which may be used in Africa include towns as

* Ilha dos Tigres (bric-building ghost town). This town is especially useful as it lies in a zone which is ideally suited for ecologic projects (mentioned in the 'Unknown Africa-Angola' documentary; see http://www.photographersdirect.com/buyers/stockphoto.asp?imageid=1499259 )
* Goma (DR Congo). Goma is safe again now that the vulcano eruption has passed. See http://us-africa.tripod.com/news.html
* Many other sturdy (bric-building) ghost towns are present in Northern Africa. Examples are towns as Chinguetti (Mali).

==Ghost town map-out==
In regard to my second proposal on mapping out the abandoned villages, there is an extra suggestion I have to decrease the cost of the project. This approach would be the use of satellite imagery from Google Earth/Google Maps (which is easily and freely available online) to allow volunteers at home to spot the villages themselves and report/mark them (marking too may be done with Google Earth). When the images are not clear enough (eg when the village's structural state is unclear, ...) to definitly say whether or not certain items on the map are indeed abandoned villages, they may pass along the information to people on the ground (government-sponsored organisations, ...) to go check out the spot/GPS-location in question. Please take a look at the extra link provided about other projects that have been conducted in this way.

==More information==
* [http://en.wikipedia.org/wiki/Ghost_town Ghost towns]
* [http://en.wikipedia.org/wiki/Flexible_Mechanisms Kyoto's Flexible Mechanisms]
* [http://www.wired.com/software/webservices/news/2007/09/distributed_search Similar map-out project conducted with the search to Steve Fosset's plane]

[[Category:Self-sufficiency]]
[[Category:Survival]]
[[Category:Survivalism]]
[[Category:Social sciences]]