Caged Slacko

[01micko]

This is slacko64 compatible with slackware64-current binaries much like slacko64- released in the slacko thread.

However, there is a big difference.

Xorg is not in charge, it uses Wayland much like Cagepup

Uses 5.14 Linux kernel

Code: Select all

~$ cat /proc/version 
Linux version 5.14.0 (5.14.9-kernel-kit@nvpup123) (gcc (GCC) 10.3.0, GNU ld version 2.36.1-slack15) #1 SMP Mon Oct 4 15:11:47 AEST 2021

Screenshot (dual screen)

All the heavy lifting was done by @dimkr in woof-ce

Download links:

Copy and paste into your browser or use wget to retrieve. I don't have https.

Code: Select all

http://01micko.com/SCAGE/slacko64-0.0.5.iso
http://01micko.com/SCAGE/devx_slacko64_0.0.5.sfs
http://01micko.com/SCAGE/docx_slacko64_0.0.5.sfs
http://01micko.com/SCAGE/kernel_sources-5.14-kernel-kit.sfs
http://01micko.com/SCAGE/nlsx_slacko64_0.0.5.sfs

Checksums: (sha256sum)

Code: Select all

1c98cbfcb9308e7a221255b1b7b3f622596f2f3a8c3367c3f5b1663c74d57016  slacko64-0.0.5.iso
c8ec9f7ccd8af66fb906b69441b1b5b8d41e20b5e7314d16079ce35d3ab3a394  devx_slacko64_0.0.5.sfs
df3e7e4ca3a22c89c9a5f498bd75651fefb8f45e332f2ca0810e0c3822052be1  docx_slacko64_0.0.5.sfs
e53e0c1e26030b090fc63391d24ac757d25d38e6d014fdfa7fdc1ae73d8c41fa  kernel_sources-5.14-kernel-kit.sfs
66826244ee67f39f1a20f0334097fdf130feb298edcccd466f9ae7681e826180  nlsx_slacko64_0.0.5.sfs

What works:

• pkg

• printing

• scanning

• dual screen

• boot to desktop

• most apps

What doesn't:

• abiword is still crap

• xrandr (replaced by wlr-randr) and many xorg utilities

• numlockx - well not properly. Might work but keyboard LED doesn't

• probably a bunch of stuff

Please download and test and report what you like, don't like and bugs.

Have fun!

[01micko]

updates

[peebee]

Puppy is getting rather fatter than before -> 550MB iso.......

Tried LXDE by same ydrv as for Slacko64-8 and all worked as expected....... although I suspect some of the Appearance Changers may need some work..........
.

screenshot.png (217.81 KiB) Viewed 2051 times

[Clarity]

Wayland is mentioned. Its benefit to us, users, is summarized here.

FYI

P.S. Downloaded the ISO file to the /BOOTISOS folder and booting directly to desktop. Upon desktop arrival on pristine boot, Application Menu actions do not execute when clicked. Keyboard actions (for example Ctrl+Alt+T/Ctrl+Bksp/Ctrl-Delete/etc.) do not work, etc. Clicking taskbar icons for actions do not result in actions, including the poweroff icon next to clock. Hard STOP required on the BIOS PC!

Edit:

1. Upon Cold start and getting to the pristine desktop BEFORE attempting completion of FirstRUN, I find that the desktop, the Menus, the taskbar icons respond as expected.

2. After updating FirstRUN with clockchanges, keyboard selections, Time-from-internet box, and Hostname change, the desktop, MEnu, taskbars, etc do NOT respond.

3. The same behavior on a UEFI AIO booted w/secure-boot off.

The FirstRUN causes this dilemma.

I will reboot and continue testing subsystems, avoiding FirstRUN.

Request
'BTOP' has been enclosed and tested in ImpPUP64. It presents a comprehensive management of system activity when active and running. Is there a chance this could be a part of this PUP, as well, in its future?

[Clarity]

Slacko64 v0.0 - Running on pristine boot without using FirstRUN process.

I am able to mount resources from another SAMBA system on this system.

Local SAMBA problems

• findsmb not working

  Code: Select all

  ~$ findsmb
  /usr/bin/nmblookup: symbol lookup error: /usr/lib64/libicuuc.so.68: undefined symbol: icudt68_dat

• pristine SAMBA SSM results in error when Apply button clicked or Daemon clicked. SAMBA is not started.

  Code: Select all

  ERROR: Aborting, Something went wrong with the Samba configuration.
  	 Check the log at /tmp/testparm.log. 
  	 Please try again or consult the documentation in /usr/share/help
  	 Your SAMBA config has NOT been changed

  • /tmp/testparm.log

    Code: Select all

    testparm: symbol lookup error: /usr/lib64/libicuuc.so.68: undefined symbol: icudt68_dat

[Clarity]

A touchscreen behavior is reported on the forum section "Bug Reports"