Porteus Superfly, V 0.2 (pre-alpha) is out!

[pizzar0]

May be I'm missing something (probably??) but what exactly is the point of "Superfly"?
Why not just run Slitaz through Linux Live and call it... something. (Took about 2 hours, including creating 400+ modules. It works perfectly fine.)

[Ahau]

thanks, pizzar0!

The main point of Superfly was for me to learn more about linux, and it has served that purpose quite well

You're right, running Slitaz this way would be great (better than superfly, unless one was a die-hard slackware fan...and even then...).

The most likely outcome of my experiment is a (far in the future) module of low-RAM applications, for use in conjunction with crashman's "tiny desktop" project. This would allow users to strip all of the modules form porteus except 000, 001, and 002, then install tiny-desktop and superfly-apps (or whatever I choose to call it) and have something that is porteus-compatible that uses under 100MB of RAM.

[Wkb58hot]

I love porteus superfly. I have found one problem however. I can not seem to get wireless working properly on my ibm r51 laptop with built in wireless.
it recognizes my wireless device i use

ifconfig eth1 up

to get that started. When i type in iwlist scan it shows the networks in my area but i can't seem to get an ip adress. My midori browser never connects is there anything that im not doing that would help.
thankx Wkb

[Ahau]

Welcome, Wkb58hot!

I'm glad you like porteus-superfly! As you can see from posts earlier in this thread, I've not really updated or maintained it for the last couple of years.

For your wifi issues: first, I would try booting without saved changes (so none of your previous modifications can influence the test) and running 'pns-tool' from the command line to try setting up your wifi that way. If that fails as well, try running 'psinfo' and post the report on pastebin.com with a link here and I'll take a look.

That said, it's doubtful at this point that I'll resurrect superfly in way similar to what it was. I wasn't very happy with the performance of Xvesa, and I didn't get it small enough to warrant using Xvesa over a more modern X.org server. What is it that you like about it? The openbox/tint2 interface, or does Xvesa actually work better on your hardware than the standard porteus edition?

I could forsee, for example, building an openbox module that would run on standard porteus. That would be more sustainable and have a broader appeal, in my opinion.

[n2prtsusr]

Ahau

Are you thinking of a openbox module for porteus 2.0?

[Ahau]

hi n2prtsusr,

Well, that's just the thing -- Porteus already ships with an openbox module. Ok, the 64-bit Standard edition does, anyway. LXDE uses openbox as it's window manager, so openbox is included in the LXDE module. In fact, if you boot into 64-bit standard edition (lxde or kde) and log out, the display manager will give you openbox as an option to select and you can log in to openbox. It's not really configured, but it's already there. So creating a "module" for it might be as easy as doing a little configuration for it. That said, there would be a bunch of tweaks needed in our porteus scripts to make it a boot option and to make it work 100% with all of our custom gtkdialog stuff (porteus settings centre, package manager, etc), and what we'd wind up with would be pretty close to LXDE. We could load lxpanel, have pcmanfm as the default file manager., etc., without adding any new software. Of course, if we wanted to make openbox more of its own thing, we could do something like add tint2 or fbpanel and some other file manager and lightweight apps, etc. -- that would require a bit more effort and would start to look like a separate "add-on" module that one could add to the lxde module. At this point, it's just an idea, so I was curious if there was any support for it in the community (which is why I asked in response to Wkb58hot's post). Of course, I already have more than I can manage with ARM, xfce, documentation, etc., but the idea of adding openbox has been bouncing around in my head for a while.