I'll do builds today and extensive testing. It will be built with the 126.96.36.199 and 188.8.131.52 kernels, but I'm very limited in what I can upload as will be doing it from the Perenjori Telecentre.
Note, my satellite Internet installation is getting there, now tentatively scheduled to be done on the 21st of August.
Anyway, I should be able to upload tomorrow morning, about 26 hours from now.
Comments:Posted on 30 Jul 2009, 8:43 by dogone
Seamonkey v2 beta 1
I'm using Seamonkey 2 first beta and it's working very well - quite an improvement over 1.17 and very stable. Any chance of including it in the pre-beta for evaluation? If the worst happens, 430 beta can fall back to 1.17.
Posted on 30 Jul 2009, 10:17 by happypuppy
Re:SeaMonkey 2.0 beta 1
SeaMonkey 2.0 b1 - avoid it like the plague
SM 2.0 may be faster and more compatible with some websites, but the Flash performance is horrible - it uses 3 to 5 times more CPU than than SeaMonkey 1.x.
It was so bad that I uninstalled 2.0 b1 immediately.
I'm using the latest snapshot of SeaMonkey 1.1.18 now - it's incredibly fast and stable as a rock :)
Posted on 30 Jul 2009, 10:57 by gposil
Barry, any movement on the 2.6.27.x kernel...i'd like to use it in the next dpup.
Posted on 30 Jul 2009, 12:14 by dogone
Correction re SM2
I'll have to yield to happypuppy's re Seamonkey 2b1. I was not aware of any such issue. I was also not aware of 1.1.18. The latter is fine with me. Thanks for the correction.
Posted on 30 Jul 2009, 18:03 by BarryK
I'm not looking forward to SM2. Strange sentiment perhaps, but apparently SM2 has dropped the 'gtkembed' library, so our PuppyBrowser created by MU won't work.
I'm hoping that they keep updating the 1.x series.
Re the 2.6.27.x kernel. I haven't got around to compiling it, yet. It does look interesting, especially as they are continuing to maintain it.
However, there is a problem, you may not be able to use it with Dpup or Upup. The reason is due to the "linux headers" used to compile the distro. You should not use any kernel version earlier than the linux-headers package, it causes some weird problems otherwise.
Ubuntu Jaunty uses linux-headers 2.6.29.x, so that's the earliest kernel that can be used.
T2 uses linux-headers 2.6.19.x (I think, last time I checked). Much more sensible, allows you to use any kernel from 2.6.19.x onwards.
For an example of weirdness that can occur, SeaMonkey is unable to generate its ssl keys, so can't be used for https access.