Lucid Puppy Revitalized as 5.2.8.7 - Nov., 2017 - Final

[ally]

2,628 from the archive

[sheldonisaac]

I have replaced the 20161115 lupu and sulu2 disk images with the updated version, 20161130. The new release images are here:
https://www.mediafire.com/folder/dh45w4 ... 16_Release

The only differences from the original version are:

• - jwm is reverted to the older version (lupu 20150702).

Thanks a lot, Richard.
I downloaded the Super2 this morning, and put the 3 essential files in a new directory, /sda1/sulu2016 on the ext4 partition.

Booted OK, and was able to change to JWM. Rebooted, was offered only the ext3 and vfat partitions to save on; saved to folder on the ext3 partition.

Rebooted with pfix=ram; used mount-FULL(*) to mount /dev/sda1 to /mnt/sda1
Moved the savefolder to /mnt/sda1.

Here's the present

Code: Select all

ls -lat /mnt/home/sulu2016/
total 183356
drwxr-xr-x 10 root root      4096 Dec  2 09:02 ..
drwxr-xr-x 13 root root      4096 Dec  2 08:56 sulusave-dec2
drwxr-xr-x  3 root root      4096 Dec  2 08:49 .
-rw-r--r--  1 root root   3688499 Nov 30 17:15 initrd.gz
-rw-r--r--  1 root root 181239840 Nov 30 17:15 sulu_002.sfs
-rw-r--r--  1 root root   2802352 Nov 30 17:15 vmlinuz

* There was a file that enabled probepart to let ext4 be mounted by pmount?? Can someone remind me, please?

OK, it was from Richard in 2013, "From precise pup 5.7.1, for experimentation only"
6710 /mnt/sdc1/LinuxSrc/guess_fstype-lupu_test.pet

in the "Lucid Puppy 5.2.8 - Updated ISO Version 005 - APR 05 2012" thread.
http://murga-linux.com/puppy/viewtopic. ... 561#735567

[watchdog]

Updates for Lucid Pup 2016:
Additions:
<cut>
gxmessage-2.12.4-1-w5c.pet
<cut>

I have found the culprit! The updated gxmessage in lupu2016 breaks the shutdown procedure to create a savefile when using an ext4 partition. I have replaced it with xmessage from lupu2015 and it now works.

[watchdog]

I think the following gtkdialog should be installed in the new 2016 release of lupu:

http://distro.ibiblio.org/puppylinux/pe ... 3-i486.pet

[rerwin]

@ally: Thanks for the archive total. I assume that is for all variants of lupu.

@sheldonisaac: Thanks for mentioning that "experiment". I had forgotten about it. I think it has been tried enough, so am including precise's guess_fstype in the "final".

@watchdog: Thanks for reporting the problem with wary's gxmessage. I see that originally (in lucid) gxmessage was a symlink to xmessage. The wary package makes xmessage a symlink to gxmessage. I missed that and assumed they were separate programs. For the "final", I have a "lucid" version of the wary package that omits the setting of the symlink, leaving xmessage and gxmessage separate, as I had assumed. I would like to know what shutdown found that gxmessage would not handle, in case you pursued the issue that far. Do you see any problem with my approach?

About installing gtkdialog4-0.8.3-i486.pet, lupu has been using gtkdialog-racy_lucid-0.8.4r514 (which is newer than gtkdialog4), required by frisbee and zigbert's programs. Why do you feel we should revert to 0.8.3? The sentiment seems to be to go back to the name, gtkdialog, without the numbers.

If anyone has further ways to fix or improve lucid pup, please post them now, so I can wrap up a final release for this year. Thanks, again, for everyone's help with this.

Oh yes, and please report any concerns about the expanded remaster_package_check script, which is intended to help reduce hidden file conflicts when upgrading lupus.
Richard

[ally]

yes, all variants, I'm unable to get individual info

[watchdog]

Sorry rerwin. I have got a problem not lucid specific. I am not able to correctly go through the first shutdown to create a savefile with every puppy getting the "No suitable partition to save" error. I can boot every puppy which I have on the hd but the first shutdown fails with every puppy. I have run booting in ram:

Code: Select all

e2fsck -c /dev/sda1

I checked sda1 partition with gparted. I have reinstalled grub4dos. The problem persists. I think that my hd has some failure. Any help much appreciated.

[Snail]

Wow Rerwin, that's a lot of downloads. You are keeping a lot of people happy, including me. Thanks for that.

Post #1 of this thread still points to the 2015 ISOs. Does this mean that the 2016 versions are still experimental? i am happy to test one of them but I'd like to be sure of their status.

[watchdog]

@watchdog: Thanks for reporting the problem with wary's gxmessage. I see that originally (in lucid) gxmessage was a symlink to xmessage. The wary package makes xmessage a symlink to gxmessage. I missed that and assumed they were separate programs. For the "final", I have a "lucid" version of the wary package that omits the setting of the symlink, leaving xmessage and gxmessage separate, as I had assumed. I would like to know what shutdown found that gxmessage would not handle, in case you pursued the issue that far. Do you see any problem with my approach?

About installing gtkdialog4-0.8.3-i486.pet, lupu has been using gtkdialog-racy_lucid-0.8.4r514 (which is newer than gtkdialog4), required by frisbee and zigbert's programs. Why do you feel we should revert to 0.8.3? The sentiment seems to be to go back to the name, gtkdialog, without the numbers.

Sorry again rerwin! My hd was getting full without any warning and odd behaviour. After deleting some stuff your iso of 2016-11-15 is working ok at the first shutdown. I was able to create a savefile. So no need to revert to xmessage. In lupu 2015 I installed gtkdialog4-0.8.3 and it works. So I suggested it to you. I was not aware that gtkdialog4-racy_lucid-0.8.4 was already installed. Sorry again.

[keniv]

Hello All,
I have installed the 2016 version of sulu002 which I have found to work very well on my hardware. I previously had the 2015 version. In that version using Control > Desktop the menu gave an option to save your own custom desktop icon setup. I have found this useful in the past as I have found if I rename the save file then reboot the icons revert to their original positions. I have also found this after say changing settings using xorgwizard. It is easy to get them back to their correct positions as well as any that I've added. This option appears to be missing in the 2016 version. Is this part of the update or perhaps an oversight. Would it be possible to reinstate it or is this a lot of work?

Regards,

Ken.

[rerwin]

@Snail: These ISOs are betas, close to the final version. I need all testing to be done on the 20161130 version, because I intend to make the next release the last for this effort, for the year. In a year I may consider another upgrade project, if there is a reason to do so.

@watchdog: Thanks for your followup on your shutdown-save issue. I will keep gxmessage as it is, which seems to be the way all newer puppies have it.

@keniv: Re: "I previously had the 2015 version. In that version using Control > Desktop the menu gave an option to save your own custom desktop icon setup.", I have not made any intentional changes related to that option. The Desktop submenus look the same as for 20160702. What is the actual name of the option you mention? Are you sure that you didn't install that feature yourself? I am not sure what I should be looking for.

Another update:
I have discovered that pmusic 5.2.4 floods xerrs.log with a few lines every second, as a result of just starting it up! I will replace it with pmusic 5.2.5, which does not appear to do that.

[sheldonisaac]

Another update:
I have discovered that pmusic 5.2.4 floods xerrs.log with a few lines every second, as a result of just starting it up!

I have pmusic 5.3.0, and it didn't do the flooding under Slim Slacko 6.

So I installed pmusic 5.3.0, under the new SuperLupu2, and indeed the xerrs.log keeps growing.

??!!??

I PMed Zigbert about this.

Sheldon

[Buddy]

What is the latest version now? The 5.2.8.7 or something called 2016?

I get confused...

[rerwin]

Buddy,
The latest is at the posting on the previous page, here:
http://www.murga-linux.com/puppy/viewto ... 329#934329

That has a link to a new directory containing all of the new release variants, as I create them. These are still beta-test versions, but are close to what I plan to release as final, soon. To preserve the various releases of the lucid pup family, I am using a directory for each year, 2014 (20141202), 2015 (20150614/21050702 - not yet created) and 2016 (betas, right now).

Please consider trying the 2016s, then report any problems here. Thanks for your interest in continuing with lucid puppy.
Richard

[keniv]

Hello rerwin,

The Desktop submenus look the same as for 20160702. What is the actual name of the option you mention? Are you sure that you didn't install that feature yourself? I am not sure what I should be looking for.

I have attached two screen captures, one from sulu002 2015 and the other from sulu002 2016. If you look at the second menu item down in the earlier sulu there is an item called "Desktop Setup-Select layout for desk/drive items" This is missing from the latter sulu. It looks as if it has been replaced with "Menu Manager". Hope this helps.

Ken.

[zigbert]

Regarding pMusic and the xerrs.log.
Does it happen at both lupu / lupusuper? Which one should I download for testing? What is the difference between lupu and sulu?

[sheldonisaac]

Regarding pMusic and the xerrs.log.
Does it happen at both lupu / lupusuper? Which one should I download for testing? What is the difference between lupu and sulu?

I tested only with the new beta-ish sulu. And not very thoroughly; ran out of energy? brains?

I don't know exactly the differences in the versions; of course, Richard does.
Oh, I see on page 1 of the thread he explains it, including ".. lupusuper (or "sulu") is/are based on kernels 3.x, to support newer hardware and xz compression.."

And he asks people to test the software; hopefully some others will.

I can try some more, but not immediately.
Had thought that possibly my savefiles were influencing things?

[rerwin]

zigbert,
Thanks for helping us with this problem.

I noticed the "flooding" with pmusic 5.2.4, but not with 5.2.5. I have not tried 5.3.0. It occurs in both lupu and sulu2. The repeated line appears to be a debug line, as it contains values for "size=, time=, bitrate=".
Richard

[zigbert]

Ok, that is output of ffmpeg.
I wonder why 5.2.4 and 5.2.5 differs. I can't see any changes in the code that should interfere with this...

Hmmm

[zigbert]

and btw, 5.3.0 is not ready for production. - 5.4.0 will be the next stable branch.