05-nov-2017: If you want to use encrypted savefiles using LUKS you should apply Update 17.11+2 or later._________________ LxPup = Puppy + LXDELast edited by peebee on Fri 02 Feb 2018, 15:42; edited 8 times in total

Notes:
Step 12 - other huge-kernels can be used; lxpup kernels require the fdrv (step 13); other huge-kernels may have firmware in the zdrv._________________ LxPup = Puppy + LXDELast edited by peebee on Wed 01 Nov 2017, 13:17; edited 2 times in total

It's running ok for me so far. The choice of apps seems good, and it looks pretty. Sound and wifi are working here. Performance seems smooth enough on my Pentium M laptop or similar to comparative newer distros, seems at least as stable as Xenialpup for me too. I included the fdrv but not the adrv, and downloaded your Firefox56 to browse (as I remember Light-48 having the youtube playing way too fast bug, but 46 was ok). The entry for Light was still in the menu though (but had no icon), the Firefox sfs had no icon in the menu as well. That's all I noticed so far. Nice to see the Ubuntu puppies moving forward into new challenges.

On a fast (VM based) test, things look past alpha.
Light icon is missing from the menu. I guess because you install in /usr/local instead of /usr. Giving the full path for the U icon in mozilla-light.desktop, also fixes that.
Some of the JWM themes fail because have tags that the version of JWM used does not understand. Xenial has 2.3.5 and Zesty 2.3.2. The latest JWM is 2.3.7
You may also want to set defaults off in a number of sharing apps at startup. Is handy for the user but in a system that runs as root and no firewall, may become problematic.
So, nothing major. Looks good_________________== Here is how to solve yourLinux problems fast ==

On a fast (VM based) test, things look past alpha.
Light icon is missing from the menu. I guess because you install in /usr/local instead of /usr. Giving the full path for the U icon in mozilla-light.desktop, also fixes that.
Some of the JWM themes fail because have tags that the version of JWM used does not understand. Xenial has 2.3.5 and Zesty 2.3.2. The latest JWM is 2.3.7
You may also want to set defaults off in a number of sharing apps at startup. Is handy for the user but in a system that runs as root and no firewall, may become problematic.
So, nothing major. Looks good

Hi @mav....

JWM is a nightmare!!! I used 2.3.2 from Slacko because anything later seems to be incompatible with Ptheme.... this was @Zigbert's advice due to Ptheme giving errors with 2.3.5...I think you're now saying that some of the themes are not compatible with 2.3.2?? Which themes errored? Any clues as to what changes are needed?

As for 2.3.7 - then that's probably incompatible with everything!!!

Maybe I should just ditch JWM and move to LXDE as jlst is proposing I think - but then this wouldn't be a Pup - it would be an LxPup....

'Fraid I don't understand "You may also want to set defaults off in a number of sharing apps at startup. Is handy for the user but in a system that runs as root and no firewall, may become problematic. " - which sharing apps? what defaults?

Maybe I should just ditch JWM and move to LXDE as jlst is proposing I think - but then this wouldn't be a Pup - it would be an LxPup....

Hi peebee,
Installed and runs well on my i5 based laptop. All the video and wireless drivers are there, touchpad etc. all completely useable on first boot. I used SNS for the wireless connect. No problems. I set up Slimjet 15.1.2.0 from SFS in my usual manner. No issues there. Disabled intel_pstate and set up the acpi_cpu driver and a governor or two. No problems there. Installed pcmanfm using the PPM and made it the default filemanager. That went well. I didn't get to setting up rightclicks or checking the suspends though because the jwm theme and panel setup and the myriad sort of functional wallpaper and theme setters sent me scuttling back to lxde. I tried. It seems solid and functional, but I guess I'm way too used to either lxde (my slight preference at this time for its more robust panel) or XFCE.

Thanks for the venture,_________________Pups currently in kennel LxPupSc, X-slacko 4.4 and X-tahr 2.0 for my users; LxPupSc, LxPupArtful, ArtfulPup & XFCE_XenialPup64 for me. All good pups indeed, and all running savefiles for look'n'feel only. Browsers, etc. solely from SFS.

Video, Booting to desktop, Connecting to the web and sound all working. Xcalc crashing xserver still a bug. Light Browser - first experience seems nice and light to use. Overall very nice Peebee for an Alpha build.

Good stuff. Overall nice job. Added Slimjet & Slimjet-Silent-Launch (ditched the adrv altogether), RedshiftGUI, Sakura and so far all seems ok and to be playing nice together. Right-click menu options could use some sprucing up, as they're pretty sparce. Only major thing I am coming across is a glitch/bug in JWMDesktop Control or just JWM itself....any changes you try to make for either jwm-tray (top or bottom), no matter what the changes are, crashes things and you get an error box (as shown in pic below) and jwm resets all of your "jwm" work back to the pristine backup.jwmrc. This stinks because it wipes everything you've previously set up. Other than that (and a few desktop and symlink things, which were easily fixed), everything seems to be running good. I've been squashing/unsquashing, threw some HD videos at gnome & it did ok, and tomorrow I will give some compiling a few things a go. Also, love the fat Zestypup background

Maybe I should just ditch JWM and move to LXDE as jlst is proposing I think - but then this wouldn't be a Pup - it would be an LxPup....

Hi Peebee,

I really don't see that the desktop type used in any way defines what a Puppy is. Many systems nowadays provide quick desktop user-change util - doesn't change the overall system... It's the underlying system control scripts that really define a different distribution - a desktop manager is basically just an application. So no such thing as a JWMPup or an OpenboxPup - if built using Puppy system scripts, such as via woof-CE, then its a Puppy whatever window manager is used IMO.

Once upon a time Puppy iso strived to be as small as possible - prior even to xz compression being available around 50MB and certainly less than 100MB (and a little bit, pretty much irrelevant, less RAM). The very small JWM was useful back then to try and help achieve that. These days have gone at least to the extent that using JWM or openbox etc doesn't make much of an overall iso size difference issue. Certainly, different WMs have their own different config and menu util requirements.

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum