(old)Puppy Linux Discussion Forum

JL64-605 - alpha
slackware-current
kernel 4.4

Download Directory:
JL64-605

known issues: auto-fstab contains some elements no longer recognized/supported resulting in some misbehaviour:
Drive icons do not auto refresh (there's a 'manual refresh' icon on the desktop);
first shutdown pupsave drops /var and results in error warning at first boot of new save file. simply reboot at prompt and save session;
new drivers for intel suck (half the function keys don't work on my keyboard);
drivers from slackware-14.1 no longer supported. Evdev & modeset are available if your driver is not found. xorgwizard-automatic is now default from a hybrid BarryK (April) & 0Micko (slacko64);
ppm needs package repos rebuilt. Really, slackware 14.2 (aka "current") isn't really ready yet. Gslapt should be the package manager of choice.
no more utf8 in console dialog boxes (makes for ugly display)

iso contains lxde, xfce, qupzilla (inside 5-JL64_605) & seamonkey addons.

devx is just waiting to upload.

df

adjustment to xorgconf.0 and remove remnants of spacefm...

Uploaded devx, kernel sources and an iso delta patch. the generated iso midsum should be All the slackware packages updated (except samba). Trimmed about 50 M off of base file. Usb peripherals now identified, xorgwizard-automatic doing its job.

Only one rox crash. Occassionally hangs at poweroff, reboot or log out. But occassionally, it doesn't. Still no auto-refresh of drive icons. Smartmount never did work. I'll probably remove it.

edit: hang @ shutdown seems to be cured by running xorgwizard-puppy.
there is an xorgwizard/pupevent switcher in menu -> system -> system tools. Pretty self-explanatory.

One of the traditional problems that ships with JLHs is with its implementation of SAMBA that is different from LH.

When the SSM is employed, one cannot click to turn SAMBA on and have it remain on. Thus, in viewing what one would think is occurring, does NOT occur. It is NOT 'On" after the button is clicked. If it is turn on, it should remain "On" unless it is turned "Off" by the user. Thus, the screen does NOT reflect that it was never on; giving the user a false indication that the subsystem is active.

Even as I know there is a circumvention for those of us that are knowledgable, the SSM should accurately reflect what's occurred.

SAMBA should be on and remain on when clicked...or some reason and message must be included in the utility to reflect that it is not working.

Hoping that this will be corrected as this distro moves toward final.

full beta ISO here:http://archive.org/download/Puppy_Linux ... -605b1.iso

Hi ally

Thank you, but it is not a Puppy, it is an (ele)Phanty!

Puppy will interest nobody more, if we become somewhat completely different, somewhat as a monster of wheight!

(As we have not enough Puppy's for 64 bit architecture) I did download and start that monster of: 594 MB

And why?

It is a Puppy with a big cancer about to agonize...

Kind regards

hi oui

I only mirror, dryfalls provided a delta only for beta1, I applied that and mirrored the full ISO

gcmartin wrote:One of the traditional problems that ships with JLHs is with its implementation of SAMBA that is different from LH.

When the SSM is employed, one cannot click to turn SAMBA on and have it remain on.

Click Setup on the desktop and then click Network. Or, click 'desktop' icon and hit 'Start Samba'. I don't particularly see having a choice whether to use or not use samba as a problem.

Thanks Ally.

Oui, pardon. The new slackware was overlayed over the old, and I agree, that was already a bit heavy. I'm still trying to learn what's absolutely necessary, and I have a lengthy trimming project ahead. Any suggestions? On the topic of samba, I was thinking of eliminating it altogether and then offering it (updated) as an sfs addon. NFS still works for simple file sharing. That should take out another 50 or so megabytes.

df

Dry Falls

Dry Falls wrote:Oui, pardon. The new slackware was overlayed over the old, and I agree, that was already a bit heavy. I'm still trying to learn what's absolutely necessary, and I have a lengthy trimming project ahead. Any suggestions?

Perhaps:

Please read at the bottom of this page:

https://www.slax.org/de/documentation.php
Or, other kind to say it: Slax64 supplies an yet ready to use derivate shrunk form of Slack including KDE! Whao! Add the things needing to make out Slax64 a Puppy64 based on, through Slax, Slackware without some ballast! Thomas, the really very experimented creator of Slax, did already remove all forms of ballast! Please look also for the work of Jejy69 here. He did extract in the past the KDE out Slax (he has now his own webpage and Puppy derivate!).

And you would get a lot of additional packages ready to use...

Just-Lighthouse64-605b2.iso

uploaded delta3: Just-Lighthouse64-605b1.iso___Just-Lighthouse64-605b2.iso.delta (170M)
generated iso should have md5=ff6133e33122a40d4243c3a4905fb955

revert to k4.1.11. Seems more stable.
revert to thunar 1.30 in xfce module
revert to 2014 rox-filer
fixed some version conflicts in libraries

Just-Lighthouse64-605b3.iso at filepup.net
k4.4.3: new devx and kernel sources @ gdrive (link at opening post - JL64-605).
Most of the obvious bugs worked out. except...
dev/console freezes after any "heavy" work like compiling or editing big sfs. Not sure why. In this event, on logout (control-alt-delete, changewm, reboot, poweroff, etc) rc-shutdown is running, but you can't see it. Not sure what the skippy is.

SFSlist on iso:

Hi Dry Falls, tried on an ASUS A555LB laptop, very impressive distro, one of the best I've ever tried congratulations great job.


Greetings.

P.S. I just started to try it, if I have some issues I will report them.

Thanks corvus. It still needs a lot of work, but it's a start.

df

Just-Lighthouse64-605beta1.iso

devx_JL64_605.sfs

kernel_sources-4.4.6-JLx86_64.sfs

icecat-38.6.0.en-US.linux-x86_64.sfs

605beta1-2.pet
(update dhcp, sysvinit-functions, gpt-fdisc, & misc - 1.4M)


Still experience dev/console hanging at logout after heavy use.

df

Thank you @Dry Falls.
From the prior post, am I correct in that we are suppose to

1. First, download the ISO
2. Boot the ISO either DVD/Frugal
3. Then, download and install "605beta1-2.pet" on the running system
   ???

Thusly, the PET is a maintenance release to the main ISO.

gcmartin wrote:Thank you @Dry Falls.
From the prior post, am I correct in that we are suppose to

1. First, download the ISO
2. Boot the ISO either DVD/Frugal
3. Then, download and install "605beta1-2.pet" on the running system
   ???

Thusly, the PET is a maintenance release to the main ISO.

Yes, GC. Meanwhile, here's another which contains some libs which went missing and an upgraded lxde-common compiled from source from sourceforge. It seems a bit less temperamental than the one I made from archlinux.

605beta1-3.pet 355k

lxde-common-0.99.1-x86_64.pet 788k

Are the "605beta1-x" service-packs cumulative OR is each one a single entity to be installed one after the other in sequence?

Thanks in advance

As JL moves forward, Firefox is too; gtk3.