Slacko5.7-2018A

[Pelo]

Slacko5.7-2017
Frisbee connects me wireless first try.
There is a hole in desktop icons. I fill it with root. Faster to click on it than opening via the menu.
My goal is to play with my hobbies, video, movies and to manage some databases, ready for use as Gramps, Alexandra or Griffith, Datacrow. Multimedia is an important category.
I replace eepc version to taste 2017 one. It's the same ? un novice ne voit pas la différence to be translated
About abiword, it is better than a note book. I need it.
Gnumeric not only calculate, but organise data. and can export them to specific database. The SFS from japanese is 7MB.

[Sailor Enceladus]

Pelo, I like your "traffic lights" to replace the desktop icons. I guess green means mounted, yellow means unmounted, and red means your puppy files are on the usb?

[Pelo]

Sure i like very much to get my puppies at work as soon as installed. Frisbee is working well, but Gramps fails because of these damned python.
These traffic lights were the default ones on eeepc version.
where are they.. . Never Mind, i will find..
Each Puppy should be with it's own set of icons, wallpapers because users from windows don't see any difference between them. Sure after four years, you see details ...

Slacko gets fat... Beside is Slacko 533 LXDE 130MB cooked in the past by French Cordon Bleu Jejy69, now LXpup.

Yet Slacko 5.7 is more efficient than slacko-6.3.2-uefi.iso: 210 M, but less than 5.3.3 (100MB). I prefer a Puppy with many apps, even old, than a Big one to get bigger again because no office, ... or No Browser.

Pemasu was in good state of mind, with Dpup squeeze and PolarQT005 :
enjoy passengers, and application developers.

[8Geee]

Green unmounted (OK to remove)
Yellow mounted (WARNING this needs to be UNMOUNTED)
Red in use, and locked (DO NOT REMOVE)

And those were my idea, brought here.

The hole is almost a signature... Its where I put my mnt/home personal files. lol

[Pelo]

8Geee, these colors are the ones to use LXquick let me search what is playing on french TV this afternoon : Zorro, french cartoon, not bad. This awful Duck Duck blocks even children movies. I had to click on HTML5 to get the moovie play. Euh, Google would be perfect.
I don't like at all that Gramps does not start because of python. No dependancies missing.
About FFox, it's really a good choice. If not enough for my needs i just have to let update go to last version. Without installing a different one.

About SVG icons, flat svg , from Slacko to Tahrpup, nobody made his mind to change them, excepted our americanos (del sur) de Pupjibaro ? Puppy doit être Jolie, Puppy has to be Pretty.
About audio, adjustment by hi-speaker icon at the bottom is much higher by adjusting retrovol too.
About PPM, Salix and Slacky are the two of some interest, for your passengers wanting to make a difference. 13.37 was not bad. 14.0 is for muslims during Ramadan !

[Pelo]

i Re-install EEEPC version, to be sure about Gramps. Gramps is a hobby for me, i feel like a child with an electric train without electricity. (python)
And i try Slegopen, from hungary.
When you compare Python files in eeepc and 2017 they are not in the same place. I am sure error is because of that. Sure ? not 100 per cent.
python 2.7.3 should be in /usr/doc/
Back to eeepc ! I will feed back ..

[Pelo]

s57-2016eee.iso: 144 M
gramps feel much better in Ha Long Bay, with icons red orange and green.
The less MBs, the better is Puppy ,like ushen Bolt (Slacko 5.5 was succesful too)
Gramps start immediatly without trouble.

[8Geee]

That is interesting about gramps and python. Both of these puppies are identical except for video drivers. Are you using sfs file from slacko puppy 5.5?

[Pelo]

There is a problem with python. I am not a linuxian, but pfind finds much more files in 2017 than in eeepc, take a glance at it..
Files furthermore are not in the same place,
With eeepc, starting in ram, SFS Gramps installs and runs without a single question.

[8Geee]

I think I have found problem with 2017 version. The change to openssl 1.0.2 may have had different links to python. Your 2016 version uses openssl 1.0.1. So it would appear there is a snag with python links in the new 2017 versions because of openssl.

Looks like you should (and will) stay with 2016 version. Open ssl in that 2016 version is 1.0.1T at the latest update.

Regards
8Geee

[8Geee]

Recently there has been two updates in the slaacware 14.0 repository
The First is to curl as version 7.50.3. This is buffer-overrun protection.

The Last is gnutls as 3.3.34. THis is general patch and update (nothing special mentioned)
The documentation can be removed in usr/doc.

***EDIT*** One symlink patch needed;
/urs/lib/gnutls.so.28.41.9 is removed, and a symlink is made using gnutls.so.28.41.16 by replacing the 16 with 9 (make sure relative box is checked)

Regards
8Geee

[8Geee]

As of today Sept.22,2016 there is an important security update needed to
openssl 1.0.2.h ---> i version. In these Puppy Slacko5.7 spins
(5.7-2017, eee-2017, mini-eee, and EONS-2017) the end-user must go to
slackware.com and proceed as follows;

Click on seurity advisory
Click on 2016
near top of list find and click openssl update
At the bottom of listings, find current_version
a.) highlight and copy (CTRL+C) the "solibs"
b.) in the address bar of browser highlight and SHIFT+INS
When asked "open with pupzip", then click YES
puppy package manager will install
Repeat the a.) and b) steps for openssl 1.0.2i package, open with pupzip,
and it will install the 1.0.2i package.
The DOC files in /usr/docs can be deleted (saves a lot of space)
Close browser, disconnect from internet, and shutdown.
Wait about 1 minute and restart.

Regards
8Geee

[8Geee]

There is another critical update to openssl 1.0.2, this time from I to J.
All of the slacko5.7-2017 spins need this patch, as the threat level is high.

The instructions above will guide to a proper patch.

Regards
8Geee

[difka]

Hello,

I'm one of Puppy Linux Slacko 5.7 users as of quite some time now, but just occasional forum lurker.

Recently I've been looking into upgrading some packages a bit (I'm usually fond of motto: don't touch if it ain't broke - meaning I've been running 'vanilla' live for quiteeee some time because it works VERY well) and naturally, in my quest, stumbled upon this project.

Now, I may end using your image, or I may, as tinkerer at heart try to update packages on my own from 5.7 vanilla. Still looking into pros/cons.

Anyway, lets go to the core points/questions of this post:

1. Is it feasable, possible to compile new kernel for this slacko? And when I say new I DON'T mean the latest versions (4.8, 4.9 atm) but I would specifically stay on the same kernel line, which is just fine for my (and many other non-bleeding edge) hardware.
Meaning I'd just like to update: 3.4.82 --> 3.4.113 (as of now). As I assume there are important security and other patches in between these minor versions. Now, I've never compiled anything huge as a kernel but I can read and follow instructions very well if someone could point me to. Maybe there is some config file(s) which can be reused from 3.4.82? Like modules enable/disabled?
And after I compile kernel, I install it how? What do I do next: save my live session, remaster ISO, install ?

2. LibreSSL! There is just never ending stream of critical holes/pathes coming from OpenSSL so I think its REALLLLLY time for it to be ditched out, like many security-minded distos already did! Would it work just to: compile LibreSSL, remove OpenSSL, install LIbre. Or thats too naive? Maybe some symlinking glue?


So thats it. Hopefully 8Geee likes those proposals and will include in his next -2017 release.

In the meantime I'd like to try to address my 2 points myself, but Puppy being somewhat specific linux distribution I'd love to hear advices from more experienced puppy users, tinkerers, devs on how-to procedure.

[8Geee]

I have finally resolved a bug while D/L the X11 series (10 files!) of updates recomended by Slackware through the Puppy Update Manager (Slackware updates in menu).

As preamble, make sure Puppy Package Manager is freshly updated. Then upon selecting the Updates from Slackware, such list is new. Since this update is buggy, make copies of personal data, and Firefox configuration with storage elsewhere, not in the drive affected by this update. If you haven't remastered in a while, now is a good time to do so... if the update does fail, the new remaster can be loaded. Else you might find yourself having to do a series of updates BEFORE attempting this one again.

There are two distinct things I noticed upon a successful attempt;

1.) DO NOT USE THE BROWSER... use the update program only.
2.) DO NOT load the X11 file until last... in short update from the BOTTOM of the list to the top, this ensures that the X11 update is LAST.

Make sure while performing these updates that all messages clear before proceeding to the next update. When finished, disconnect from the internet, and shutdown.

After the restart, You may clear /usr/doc files, and move /root/.packages files into the builtin folder.

Hopefully, this will work for all in need.

Regards
8Geee

[8Geee]

1.) According to 01Micko, the original creator of Slacko5.7, updating or exchanging kernels is not within the scope of the distro... therefore it has to be re-engineered from ground up. This CAN be accomplished with the newer Slacko6.3 version, but then, only to those kernel packages provided.

2.) This one is sorely needed in all modern Puppies, not just this one. And, this too is a very big job. There is an outside chance that Slackware might migrate to LibreSSL, but at the cost of also using OpenBSD. This will inflate Puppies quite a bit.

Basically, I maintain Slacko5..7 by providing updates to it, not re-coding any files or operations. Sorry about that... what 01Micko originally supplied is either updated or removed, depending upon end-use (primarily, these are for EEEpc and clones, but I do update the original, and provide a better version of FireFox-27)

Regards
8Geee

[difka]

Regarding X11 update bug you are mentioning in post before, I encountered it too while trying to update whole vanilla 5.7 via "Updates Manager -latest from Slackware". I got it right on 2nd try. Basically, its about install order. Maybe I had some luck, maybe my logic works. Idead is to first update libs but in case of X11 make sure libX11 is installed LAST. Otherwise GUI apps will complain of missing symbols (which are contained in other dependent X11 libs) and since Update Manage is GUI we are stuck... btw. tedious 1by1 updating makes me really appreciate god among package managers: Archlinux's pacman, eh eh.


So hmm you basically say I'm out of luck with 1) updating kernel and 2) moving to LibreSSL. Well thats unfortunate. Except these two things Slacko 5.7 is pure perfection for me.

2.) This one is sorely needed in all modern Puppies, not just this one. And, this too is a very big job. There is an outside chance that Slackware might migrate to LibreSSL, but at the cost of also using OpenBSD. This will inflate Puppies quite a bit.

Its very big job

I suppose it means recompiling all packages currently linked against OpenSSL? Yea it would be super nice if upstream Slackware did that but if they don't want maybe we could. How many packages are involved? 20, 50?

but at the cost of also using OpenBSD

This does not compute. Only connection between LibreSSL and OpenBSD is that OpenBSD developers forked OpenSSL and renamed it to LibreSSL. And they actively maintain it. Also they are known to write quality code so I presume this:

This will inflate Puppies quite a bit.

may as well be opposite of it. As openBSD developers rewrite, trim down, squash bugs at worst size will be same. My understanding at least.

[8Geee]

Right after posting about the X11 updates, yet another reminder that CURL has also been updated from 7.50.3 to 7.51.0. This update involves cookies, so it should be done if using curl.

This update does not need any symlink patches, and the /usr/doc file file may be deleted.

Regards
8Geee

[difka]

Hey I have one tiny problem with this slacko (and vanchutr's too interestingly).

It shut downs pc if I leave it unattended for 20-30 min.
Can someone point me which setting would control such thing?

Why is that even set up? Just strange...

I run puppys live and set up my environment every boot manually.

Original Slacko 5.7 has no such problems.

[8Geee]

In MENU --> System --> Puppy Event Manager click on the right-most tab "Power".

There is a small box at bottom to enter some number as a "Shutdown after no mouse activity" The default Slacko5.7 by 01Micko had this set to zero (do not shutdown). By typical usage, I set this to 30 (minutes). IIRC the range is 0 to 999.

Regards
8Geee