Hi Mike, > Yes sure I can. So this PharoNOS is basically TinyCore Linux with pure X > server and Pharo running in fullscreen.
Yes I already found out. > I have made some auto-installation scripts which configure the disk so no > setup wizard is needed. All space available is mounted under /mnt/universe/ > so you may use that folder to store stuff. Everything else is stored in > memory. Nice side effect of this is an ease of update as you may just > replace the ISO and you'll get the new version of everything (except of the > image of course). Mmmhh ... maybe it should initially boot a downsized "Image selector" image (that allows to download images from CI like Pharo Launcher). Something similar to the usual Linux install wizards to initially setup a machine, configure keyboard layout, clock/timezone, IP/DHCP ... but done in Smalltalk. OSProcess commands could be used underneath to configure the underlying Linux. If this "PharoNOS GraphicalInstall" supports downloading premade image(s) from CI similar to PharoLauncher one could easily configure the machine with for instance with a premade Seaside, Bootstrap, Moose, ... image. This image could also be the fallback to repair, ... > Image is chosen on start by reading the "/mnt/universe/image" file. You may > upload other image and change this file so after reboot it will start with a > new one. This info should be included in the docu in the pillarhub article (if not already) > Jan Tomsa has pointed out that the disk setup is quite dangerous > (https://twitter.com/DetektivTomy/status/522860736155238401) I plan to > update it later today with more safe solution which will not erase all the > data. Nice > Also I think Pharo should be run under root user so you can bind > to any port. Yes, I have the following quick setup scenario in mind: downlod the ISO, start a virtual computer with it (in virtualization software or on a cloud server). Use the Pharo based setup wizard (see above) to setup keyboard layout, give a fixed IP, adjust the clock, ... and download a premade Seaside (or other webframework image) from CI. Now run on port 80, configure another port and give a name to the machine in the network. This way one could easily setup virtualized network machines to provide network delivered applications. > I can also put more 3d-party libs like sqlite3, so we can have some > interesting apps for the terminals run on embedded Pharo :) However I need > some feedback on what is needed. sQLite3 would be cool, also unqlite. Both are small shared libs and embeddable. This way one could load the Native Boost bindings for either SQLite3 or PUnqlite and use an embedded RDBMS or a NoSQL Database and also load/use Glorp/Voyage or other to access it. > So that is it, all comments are welcome. A specific small image demonstrating Pharo 3 or 4 lively in the web browser also comes up as an idea. Emulating and bootstrapping an x86 machine on top of JavaScript is possible these days. Look at http://copy.sh/v86/ to bootstrap a linux in your browser. I tried to run the ISO with it, but it hangs. I guess it is due to query for network (which is not available in browser). Maybe a special non-network image could be built. This way we could include a premade machine in the Pharo Project webpage so people can directly bootstrap and play with Pharo. Similar to SqueakJS (http://bertfreudenberg.github.io/SqueakJS/) but without having to port the Pharo VM to JS. >I'll take a look at AioPlugin issue. How I can test if it is loaded well? I loaded OSProcess from the config browser and used (PipeableOSProcess command: 'pwd') output. While doing this the system lamented about the missing AioPlugin. Bye T.
