LxPupSc: Woof-CE, Slackware-Current, LXDE build 13-Jun-2020

Message

gcmartin · #101 Post by **gcmartin** » Wed 10 Feb 2016, 19:16

Has anyone else noticed some misbehavior with SourceForge downloading?

Example1
I tried to d/l the ISO and Devx at same time on a Firefox browser, same PC. Failure with Network error of both.
Example 2
I tried a different PC, different browser, same simultaneous d/l...failures, too!
Example 3
I tried starting a single d/l on one PC and the other d/l on a separate PC...failures, too!
Example 4
3 PCs - 1 for ISO, 2 for DEVX, 3 for sources...ISO&DEVX PCs fail, while sources fly straight thru to completion.

The ISO and DEVX are from SourceForge while the Kernel sources are from your Google account. There is NO problem with using Google, but, SourceForge has been poor in d/l. Speed differences; No SourceForge has gotten above 128Kb/sec while your Google d/l at 3.1Mb/sec.

This behavior failures has happened on your 160201 releases and your 160202 releases. I don't do a lot of downloading from SourceForge. But, I do understand why they are useful to you.

I know you don't control the behavior or the download sites, but, the knowledge of this behavior and performance info might be helpful.

Update: the md5 checksums I have gotten after all the struggles with SourceForge today using a completely different downloader program in the browser while having to Pause-Resume every time the downloads stopped, is as follows:

Code: Select all

ae1571e926d0a98691617b040bd3aa79  LxPupSc-16.02.02-pae.iso
3298b48b3d18e0ef278eff2fb3a0d331  devx_SlackoC_16.02.2.sfs
8da32ef59908e0eda24303a3b5996a1d  SlackoC-16.02.2.iso
d8cee5c049cd27cb9ac86dd45825f26a  kernel_sources-4.3.3-EmSeei686-Mon-Jan--4-21-15.sfs

Request: Please confirm accuracy.

peebee · #102 Post by **peebee** » Thu 11 Feb 2016, 07:32

gcmartin wrote:

Code: Select all

ae1571e926d0a98691617b040bd3aa79  LxPupSc-16.02.02-pae.iso
3298b48b3d18e0ef278eff2fb3a0d331  devx_SlackoC_16.02.2.sfs
8da32ef59908e0eda24303a3b5996a1d  SlackoC-16.02.2.iso
d8cee5c049cd27cb9ac86dd45825f26a  kernel_sources-4.3.3-EmSeei686-Mon-Jan--4-21-15.sfs

Request: Please confirm accuracy.

Confirmed.

Sourceforge provides md5 - just click on the i

at: https://sourceforge.net/projects/lxpup/ ... r/LxPupSc/

peebee · #103 Post by **peebee** » Thu 11 Feb 2016, 15:48

Here is a small pet to try to put back one of the features of lxpanelx that went missing with the change to lxpanel in LxPupSc....i.e. recent documents

Currently installs as a menu item under Help

Now included in version 16.02.03

peebee · #104 Post by **peebee** » Sat 13 Feb 2016, 07:33

More slackware-current changes 11-feb....most significant seems to be addition of libcap-ng which coexists with libcap, a dependency of many components - "it is expected that other programs will begin to use it in preference to the older libcap"

Post above has been updated to version 16.02.03

Delta is available.

Marv · #105 Post by **Marv** » Sat 13 Feb 2016, 14:18

Delta downloaded no problem, iso generated, md5sum checks. Frugally installed to Fujitsu S6520 updating 16.02.02 savefile. Recent documents noted. I'm also running this on the 8.5 watt

Bay trail house printer and Samba server. No problems noted on either (I have /.etc/init.d/frisbee.sh patched, line 112 commented out for shutdown if yassm shares open). With smb://192.168.10.14/HouseShares bookmarked, PCManFM manages the smb access very nicely.

Marv · #106 Post by **Marv** » Sun 14 Feb 2016, 12:04

Noticed file transfer on the Bay Trail (quad J1900) box was slooow (and a bit flakey) running the current LxPupSc, not under LxPupTahr or the X- slacko or X-tahr series. Watched this for a day or two and it was consistent. So I tried a little experiment copying my LxSc boot dir (roughly 540Mb) to a test directory with the stock kernel and rolling back to the 3.14.56 kernel. Did it both on the Bay Trail box and on the core 2 duo laptop. Both have SATA Intel X25M SSDs. NO changes other than the kernel change using change_kernels. Tests run back-to back. Straight copy and paste operation using PCManFM.
Bay Trail box:
4.3.3 (stock) kernel 6 MINUTES
3.14.56 kernel 11 seconds
Core 2 duo laptop:
4.3.3 (stock) kernel 11 seconds
3.14.56 kernel 6 seconds

Replicated 4 times on the Bay Trail box, only twice on the core 2 duo laptop. The seconds times are rough, I'd say within a second. The 6 minute time speaks for itself.

I have the rolled back ver. in my experimental dirs so bouncing back and forth is pretty fast. Needless to say, the Bay Trail server is running rolled back.

Update: This is resolved with the 16.02.4 release which has the 4.4.1-Emsee-32-pae-rt3 rt kernel. All file transfers are normal on Bay Trail, core 2 duo and Pentium M machines.

gcmartin · #107 Post by **gcmartin** » Sun 14 Feb 2016, 19:46

@Musher0 finds a FYI update for the next version(s)

peebee · #108 Post by **peebee** » Wed 17 Feb 2016, 09:46

LxPupSc-16.02.4-pae.iso {devx} {kernel 4.4.1-EmSeei686 sources}
iso md5 = 89088d1aa39b55b662ad8880588d9091

Made from Slackware-current as of 11-feb-2016

BUILD_FROM_WOOF='testing;a5d36ab;2016-01-17 08:35:59 +0200'

Delta is available

Main changes are:
- Kernel is now 4.4.1-pae-rt3 from Stemsee
- now built entirely by woof-ce - see below for consequences
- identifies as LxPupSc so existing savefiles will need to be renamed

Main consequence of woof-ce build is that there is no intermediate SlackoC build as this is no longer needed (it could be made fairly easily as a separate build if required).

Couple of "lessons learnt" from doing the woof-ce build:
1. you've got to have properly formed pinstall.sh in your pets: i.e. "BK Note!!! In the pinstall.sh script you must not use absolute paths" as you can probably guess, mine needed changes!
2. a new default theme "LxPupSc" in /usr/share/ptheme/globals was the easiest way to modify the look and feel during the woof-ce build process (especially GTK2).

You can see the woof-ce build files at:
http://smokey01.com/peebee/slackocurrent/
BUT please note that there are a couple of tweaks to the woof-ce build process needed to do a LxPupSc build.

To add LxPup components into woof-ce, I have split the sfs and pets previously used in the woofy build into 7 new pets so there is a process prior to the woof-ce build that creates these 7 pets from their constituent components:

lxpup_libs_sc #various libs not in slackware-current
lxpup_look_sc #look and feel components
lxpup_winman_sc #openbox etc.
lxpup_fileman_sc #pcmanfm etc.
lxpup_panel_sc #lxpanel etc.
lxpup_apps_sc #various added apps
lxpup_config_sc #setup/configuration changes

The script files are available in the smokey01 repository.

mavrothal · #109 Post by **mavrothal** » Wed 17 Feb 2016, 11:25

Correct download link would be
https://sourceforge.net/projects/lxpup/ ... o/download
ie https:// not http://

peebee · #110 Post by **peebee** » Wed 17 Feb 2016, 12:01

mavrothal wrote:Correct download link would be
https://sourceforge.net/projects/lxpup/ ... o/download
ie https:// not http://

How strange - http used to work - bit of a bummer if all previous sf links no longer work - changed links above - thanks Mav

Been onto their chat channel - looks like it was a temporary glitch as previous http links now seem to work...

mavrothal · #111 Post by **mavrothal** » Wed 17 Feb 2016, 12:35

peebee wrote:BUILD_FROM_WOOF='testing;a5d36ab;2016-01-17 08:35:59 +0200'

Looks good.

Is there any reason that you use this older git tree?
Since then there are ~25 new commits some of them interesting.

peebee · #112 Post by **peebee** » Wed 17 Feb 2016, 12:43

mavrothal wrote:
peebee wrote:BUILD_FROM_WOOF='testing;a5d36ab;2016-01-17 08:35:59 +0200'
Looks good.

Is there any reason that you use this older git tree?
Since then there are ~25 new commits some of them interesting.

Change one thing at a time is a good motto....but you're right, maybe time for a woof-ce update for the next version (when next slackware-current changes I suspect).

Marv · #113 Post by **Marv** » Wed 17 Feb 2016, 14:52

I've been testing this for a bit on my Bay Trail desktop, core 2 duo laptop and on a Pentium M laptop, specs below. The file transfer issues I had under 16.02.3 are all resolved with the new kernel. Only one surprise

How very well it (with the 4.4.1 rt kernel) runs on the 1.6G Pentium M. The forcepae patch in the kernel allows a kernel param of forcepae for the Pentium M series. Put that in the Grub4Dos menu item and up it came. Flawless and totally usable.

Code: Select all

Pup-SysInfo Hardware Report (Annotated Summary), Wed 17 Feb 2016

====> BASE SYSTEM <====

PC Manufacturer: FUJITSU
Product Name: LifeBook S6230

Motherboard Vendor: FUJITSU
Product Name: FJNB191

BIOS Vendor: FUJITSU // Phoenix Technologies Ltd.
Version: Version 1.05 
Release Date: 11/09/2004

Intel(R) Pentium(R) M processor 1.60GHz
Max Speed: 1600 MHz
Current Speed of Core 0:1600 MHz

Linux Kernel: 4.4.1-EmSee-32-pae-rt3 (i686)
Kernel Version: #1 SMP Fri Feb 12 21:51:08 GMT 2016
PAE Enabled: Yes

Distro: Slacko-C Puppy 16.02.4
Desktop Panel: lxpanel 0.8.1
Window Manager: Openbox 3.6.1
Desktop Start: xwin startlxde

Boot Partition: sda1 (Size 7.8G, Free 5.1G)
Boot File System: vfat
Boot Media: ataflash

PUPMODE=13
PUPSFS=sda1,vfat,/Experimental/puppy_SlackoC_16.02.4.sfs
PUPSAVE=sda1,vfat,/Experimental/SlackoCsave-16024.2fs

====> DISPLAY <====

Display Specifications:
+ Monitor VertRefresh: 60.00 times/s
+ Screen Dimensions: 1024x768 pixels (270x203 millimeters)
+ Screen Depth: 24 bits (planes)

Xorg Startup Log (/var/log/Xorg.0.log):
+ Xorg Driver in use: intel
+ Loaded Modules: dbe dri2 extmod fb glx kbd mouse synaptics
+ X.Org version: 1.18.1

OpenGL 2D/3D Rendering:
+ Direct Rendering: Yes
+ Vendor: Intel Open Source Technology Center
+ Renderer: Mesa DRI Intel(R) 852GM/855GM x86/MMX/SSE2
+ Version: 1.3 Mesa 11.1.1

====> INPUT DEVICES <====

AlpsPS/2 ALPS GlidePoint
AT Translated Set 2 keyboard
Fujitsu Application Panel buttons
Fujitsu FUJ02B1
Lid Switch
PC Speaker
Power Button
Video Bus

Thanks,

mavrothal · #114 Post by **mavrothal** » Thu 18 Feb 2016, 04:42

peebee wrote: 2. a new default theme "LxPupSc" in /usr/share/ptheme/globals was the easiest way to modify the look and feel during the woof-ce build process (especially GTK2).

This and other lxpup-specific pets that are not from the binary compatible distro should be uploaded in ibiblio. in noarch if have no binary blobs and in their own directory if they do.
Ask Phil or Mick (though he maybe hard to contact these days) to upload them

peebee wrote:You can see the woof-ce buid files at:
http://smokey01.com/peebee/slackocurrent/
BUT please note that there are a couple of tweaks to the woof-ce build process needed to do a LxPupSc build.

To add LxPup components into woof-ce, I have split the sfs and pets previously used in the woofy build into 7 new pets so there is a process prior to the woof-ce build that creates these 7 pets from their constituent components:
lxpup_libs_sc #various libs not in slackware-current
lxpup_look_sc #look and feel components
lxpup_winman_sc #openbox etc.
lxpup_fileman_sc #pcmanfm etc.
lxpup_panel_sc #lxpanel etc.
lxpup_apps_sc #various added apps
lxpup_config_sc #setup/configuration changes
The script files are available in the smokey01 repository.

From what I can see a lot of the scripts just install additional packages mostly from the repos. It would be preferable to just make a woof-distro/x86/slackware/LxPup/DISTRO_PKGS_SPECS-slackware-lxpup file and have the required packages there.

Now that lxpup is in http://puppylinux.com/download/index.html should be able to build using woof without the need of additional files and packages outside github and ibiblio

peebee · #115 Post by **peebee** » Thu 25 Feb 2016, 09:25

Updated 27-feb-2016

LxPupSc-16.02.6-pae.iso {devx} {kernel 4.4.1-EmSeei686 sources}
iso md5 = 62c3144aac157503574da117087d83d5

Delta is available

Lots of changes, all "under the hood":
- Made from Slackware-current as of 26-feb-2016
- BUILD_FROM_WOOF='testing;c6e06b5;2016-02-24 18:41:13 +0200'
- including all current root-fs-packages
- refinement of woof-ce build process for LxPup: libs, winman, fileman and panel conglomerate .pets now deleted and built instead from constituent parts - a continuing process

Woof-CE build repository is: http://smokey01.com/peebee/slackocurrent/

Known problem: ddcprobe does not work with k4.4.1

Marv · #116 Post by **Marv** » Thu 25 Feb 2016, 12:13

Having some problems with the delta right now. Downloaded twice and the ...4 iso has been md5sum checked and used for some time now. It gives me the following error:
Failed to recreate the new file, xdelta3: target window checksum mismatch: Unknown error -17712. I'll download the full iso when I go out for the day.

Update: Got the full iso, md5sums check, more later.

mavrothal · #117 Post by **mavrothal** » Thu 25 Feb 2016, 12:59

Didn't do much, just tested some recent woof changes and installed some packages (with deps). Looks good

peebee · #118 Post by **peebee** » Thu 25 Feb 2016, 14:25

Marv wrote:Having some problems with the delta right now. Downloaded twice and the ...4 iso has been md5sum checked and used for some time now. It gives me the following error:
Failed to recreate the new file, xdelta3: target window checksum mismatch: Unknown error -17712. I'll download the full iso when I go out for the day.

Update: Got the full iso, md5sums check, more later.

I suspect you may have been using the "pre-release" 16.02.4 that I sent you by pm.....you need to apply the delta to the "official" 16.02.4....

Marv · #119 Post by **Marv** » Thu 25 Feb 2016, 14:43

peebee wrote:I suspect you may have been using the "pre-release" 16.02.4 that I sent you by pm.....you need to apply the delta to the "official" 16.02.4....

Yep, I was. Anyway, full iso downloaded and installed frugal to the core 2 duo machine. Fresh install, new savefile, just imported my look, feel, browser links, patched frisbee.sh (stop) and installed my bonehead version checker desktop link (I for one forget which pup I'm working on

), lx_rightclicks (could it be in by default?), and desktop_drives. All looks just fine so far. I like this kernel. Tested it in X-slacko 3.1n and it's happy there too, even on the Pentium M laptops. I'll do the above to the Bay Trail and Pentium Ms later.

A question: Using PCManFM to access Samba shares with password, it asks nicely for the password but will not save the password permanently when that box is ticked. Permissions? Have you done that? I assume it uses gvfs-.. but I'm not sure.

peebee · #120 Post by **peebee** » Thu 25 Feb 2016, 14:49

Marv wrote:A question: Using PCManFM to access Samba shares with password, it asks nicely for the password but will not save the password permanently when that box is ticked. Permissions? Have you done that? I assume it uses gvfs-.. but I'm not sure.

Glad you are up and running....

No - haven't been able to save passwords - suspect there's a bit of "privacy" infrastructure missing, but not sure how to work out what it is as there's no error messages that I've been able to find. I just have a shortish password easy to type....

(old)Puppy Linux Discussion Forum

(old)Puppy Linux Discussion Forum

LxPupSc: Woof-CE, Slackware-Current, LXDE build 13-Jun-2020

Recent documents & lxpanel

Version 16.02.03

Version 16.02.03

File transfer speed, a little experiment

LxPupSc-16.02.4-pae

Re: LxPupSc-16.02.4-pae

Re: LxPupSc-16.02.4-pae

Re: LxPupSc-16.02.4-pae

LxPupSc-16.02.6-pae.iso