E-echidna Development System
Delays on the Eechi DNA project are mostly being blamed on a lack of a system designed to explode every now and again for the purposes of E-echidna Development Systems. This Tumblr post is to be a brief set down of various systems that will need to be set up.
Eechi's hardware is probably best to jot down fairly quickly on this matter, and what it will need this for.
E-echidna Computer System's goal being to tackle a lot of misbehaving Linux concepts and ideals, and put them into a line that has no claims of dragons, ogres, kraken or other monsters in their workings. If there are any mythological beasties in there, they will be given a generous compensation package, a good reference to future employeers and a good bye ceremony--with some proper computer code used in their stead.
Due to this ideal system setup, E-Echidna will be setup as it a Fedora Spin, with all packages a Fedora spin has available, with possibly the Eechi DNA Yum Repository also enabled. The E-Echidna Yum Respository will contain systems to run project files, add to the system, as well as patched beyond the silly levels of projects that have had their patches sent upstream.
Possible options for the Fedora Spin may be to fork into its own Distro, or possibly become an official system of Fedora to try to make Linux systems less lame... as Fedora seems to make good efforts that way.
Over the course of E-Echidna Computer System development, KDE4 will probably become KDE5, gain Android Compatibility, run User Group based logins with each user id being to its own software package of process ids. Giving a command line that takes away everything in BASH that dipping anybody using its sanity metre. So that you can work on command line applications for a whole hour, without creating obscene alters to the horrible terrible things from dimensions beyond our mere human comprehension. Allow for the computer to act as an autopilot--being your online body anyways. Integration of social networks and metaverse type worlds into the systems runnings.
The system itself, will need to handle several jails--mostly to allow for Yum and RPM to keep the development system sanitary. Which means a sizeable harddrive that is capable of being easily replaced. Possibly LVM encryption over two seperate pieces of hardware--where if one breaks, it can be switched out.
The system will need a fair amount of RAM, unfortunately. The goal is to be able to get these systems to run programs in a sane amount of memory. Which for using Facebook, you'll probably only need 64MiB of RAM (this after setting up a specific application for dealing with Facebook). However, because most programmers seem to use their butt instead of their fingers to program their code today, I'll probably need 2GiB or more. I have yet to understand that programming trend, really.
It will probably need a few redundant parts laying around, for cases of random explosions.
Inside the system it likely will be running Git repositories via loopback, for some level... until I can figure out a much proper Git server system setup. It may involve getting a premium account with Github.
I'll probably also need Eclipse as that seems to be what all the cool kids are using these days for an Integrated Development Environment (IDE).
Heh, and over the course of this, I should probably set up a Google Site, to handle me jotting down notes on various functions, objects and what not in various projects that Eechi DNA will take looks into. Something that is potholed and generally easy to "Wiki Walk" through... and actually explains what the frak you are trying to do with this stuff! AAAAAAAAAGGGGG!
Also looking to set up so that I do one of these theory posts to show up on Sunday on Tumblr. Any other posts will be posted at the time of the post.