hi, i have been investigating a full blown gnu/linux based distribution focused entirely on pharo as the the user interface layer. looks like, if the entire base 'os' functionality is exposed via this little environment/toolkit called "sysctl", building a pure object oriented layer of shell scripts to support all calls exposed via sysctl and managed via pharo looks feasible. i might be wrong, and look forward to experienced folks pointing out flaws in my thought process. if this organization/architecture feels sound, i would like to get a go-ahead to hire the services of a gnu/linux expert to start building the base layer atop which pharo can be run as the only application. this effort would be funded out of my own pockets (which aren't very deep). :) ~mayuresh
I also play with Mike's PharoNOS these days and ask myself why not do the major part in Pharo itself... Check the "OS-Unix" and "OS-Linux-Ubuntu" project on STHub. Bye T.
pharonos sounds very interesting, almost the same as what i had in mind. but ofcourse for the difference in building _that_ object layer between the linux kernel and pharo environment. that object layer (built using shell scripts) would add in an enormous amount of flexibility. another approach that might be considered would be to simply tap into the variables exposed by "sysctl" and maintain a state system within pharo and do the read/write to the kernel via sysctl directly. ~mayuresh On Mon, Jan 26, 2015 at 04:00:28PM +0100, Torsten Bergmann wrote:
I also play with Mike's PharoNOS these days and ask myself why not do the major part in Pharo itself...
Check the "OS-Unix" and "OS-Linux-Ubuntu" project on STHub.
Bye T.
Keep pushing this idea. Stef Le 26/1/15 14:17, Mayuresh Kathe a écrit :
hi,
i have been investigating a full blown gnu/linux based distribution focused entirely on pharo as the the user interface layer.
looks like, if the entire base 'os' functionality is exposed via this little environment/toolkit called "sysctl", building a pure object oriented layer of shell scripts to support all calls exposed via sysctl and managed via pharo looks feasible.
i might be wrong, and look forward to experienced folks pointing out flaws in my thought process.
if this organization/architecture feels sound, i would like to get a go-ahead to hire the services of a gnu/linux expert to start building the base layer atop which pharo can be run as the only application.
this effort would be funded out of my own pockets (which aren't very deep). :)
~mayuresh
participants (3)
-
Mayuresh Kathe -
stepharo -
Torsten Bergmann