However, Forum member Jades reported a problem:
Attempted to run SeaMonkey from task window and got an 'Illegal Instruction' error. K6-2 series is classed as i586 due to lack of CMOV instruction.
A side note: I find the continual evolution of the Gnu C++ compiler to be very annoying, as it breaks old code. They don't retain backwards compatibility, and this practice of breaking old code has been going on for many years. Unlike C, the definition of which is "cast in stone".
Anyway, if Wary is to retain SeaMonkey, then unless we figure out a way to compile it for 'i486-pc-linux-gnu', then I will have to use an older version. Um, not sure, I think that Wary 5.3 has SeaMonkey 2.6.1, as described here:
Note, probably it would be possible to install a later C++ in Wary just for the purpose of compiling SM, and maybe retain the later libstdc++.so* if needed. If anyone is interested in trying that, go for it!
But for now, I am very fond of the old SeaMonkey 1.1.18, and I think that I will do the next beta with this, along with a heap of extensions (user agent switcher, adblock, downloadhelper, flashblock, etc.).
Of course, this old SM is not aware of HTML5, but that is not serious problem for now. It will of course have security weaknesses, but then so does 2.6.1, and perhaps an older version that no-one else is using is less likely to be targeted (?).
Comments:Posted on 2 Dec 2012, 23:57 by james c
Pulled my old K6-2 off the shelf, booted Wary 5.3.90 and got the same "illegal instruction" error.
Have Wary 5.22 installed(frugal)with SeaMonkey 2.3.1..... no problems.
Posted on 2 Dec 2012, 24:15 by james c
Since I have the evil XP on the k6-2 box I just downloaded and installed SeaMonkey 2.14.1.......naturally it works fine ootb.
Posted on 3 Dec 2012, 5:16 by rodin.s
bootflash and combo mode
Barry, I haven't tested this myself but Russian Puppy forum member vkvkvk reported that he has problems with combo mode of bootflash. In Puppy-4 it works OK. It makes two partitions: one 128Mb for Puppy and another one vfat for all the rest. In Puppy-5 the size of partition for Puppy was increased to 256Mb and now partition for Puppy is created OK but vfat partition is not created and the rest of the space remains unallocated.
Posted on 3 Dec 2012, 12:56 by Dewbie
...and now SeaMonkey follows.
Posted on 30 Dec 2012, 17:12 by Dewbie
Just edited .sfs for Wary 5.2.2...stripped out SM 2.3.2, replaced with 1.1.18 (from Wary 184.108.40.206).
Works great, and .iso is about 8MB smaller.
Posted on 28 Sep 2013, 13:41 by Dewbie
Forgot about this thread; eventually ran into segfaulting with above-mentioned SM 1.1.18 and official-binary 1.1.19...back to the drawing board.