Here they are:
These are the 'common' PETs, that are likely to be needed for all Puppy builds.
Comments:Posted on 13 Jun 2012, 12:37 by cthisbear
Have a cuppa.
" I have lost count of how many days it has taken."
Beats thinking about storms eh!
About time for a break BK.
Flying a kite would be exciting now in Perth.
But I think a nice Decaf would be better for you.
Now that you are in the big smoke try to look for Schibello decaf....beautiful.
Ah! no cafes yet in WA.
Posted on 13 Jun 2012, 16:32 by BarryK
I had a midday snooze, then an iced coffee!
Now for the next step...
One of my "problems" is that I often have ideas, but no time to implement them. There were lots of intervals when the RasPi was compiling and I was just sitting there staring at it. A very ripe environment, and ideas kept popping into my mind.
I made some notes, some little things to improve Puppy, will look at them again later.
Posted on 13 Jun 2012, 17:12 by dc
When compiling did you do it on the Raspberry or the Mele or something else?
Posted on 13 Jun 2012, 21:09 by RichieB
How about xbmc for puppy whilst you wait for the RPI stuff to compile lol.
Posted on 13 Jun 2012, 21:57 by BarryK
It was all done on the RP. A one-off manual effort. The rest of building a pup will be much more automated.
Posted on 14 Jun 2012, 2:43 by dionicio
kites in Perth
kites in Perth are good for skating...
Posted on 14 Jun 2012, 6:46 by technosaurus
Now that I have gotten my simple icon tray roughly finalized, I have shifted focus to making Xfbdev more useful. IIRC it is much more seamless on arm???, but x86 has the kludgy vga=<mode> kernel command line parameter (I am trying to fix that here:)
It could be a good small fallback for all supported platforms.
Posted on 16 Jun 2012, 21:09 by smokey01
This is interesting.
Posted on 17 Jun 2012, 10:27 by BarryK
Re Puppy on MK802
Good to see!
It is a shame that SeaMonkey crashes with an illegal instruction. Probably this needs to be reported to the SM developers as a bug.