Puppy Linux Discussion Forum

released 24/11/2017

Xenialpup CE 7.5

this is xenialpup CE built with ubuntu xenial xerus 16.04 libs.

kernel 4.4.95

JWM, Rox, palemoon, deadbeef, mpv, simple-screen-recorder, pburn, mtpaint, claws-mail, geany, osmo, hexchat, abiword, gnumeric, urxvt, urxvtcontrol ,JWMdesk, simplegtkradio, packit, uextract, cups, samba and lots more.
Including the brilliant puppy icon theme by 01micko http://blog.puppylinux.com/?viewDetailed=00016

thanks to all the developers, contributors & testers!

Xenialpup was only possible because of 'woofCE', forked from woof created by Barry k, maintained by 01micko, wdlkmpx, mavrothal, iguleder, zigbert and contributed to by various others.... all the hard work went on there Very Happy
Max Mustermann kindly let me use his picture as a background. you can see more of his stuff here...
https://plus.google.com/111729541566365 ... tt32Q4mYu
edward carter also kindly let me use his picture as a background, and you can see more of his stuff here...
http://www.dotmund.co.uk/
http://www.facebook.com/dotmundart

Minimum System Requirements
Recommended: 1000MHz 1gb RAM and either bootable cd
access, usb boot, sdcard or network boot access. A Hard Drive is not required

Downloads:
http://distro.ibiblio.org/puppylinux/puppy-xenial/
https://ftp.nluug.nl/os/Linux/distr/pup ... py-xenial/

For the kernel sources type sfsget into a terminal
.
.
Note:
Xenialpup updates and bug fixes

Xenialpup has a few bug fixes and updates that did not get into the final releases.

After installing it and booting to a working desktop.

Get internet connection working, by WIFI or Ethernet.

Do a shutdown and make a save to store changes in.

On next boot up, using the save, there will be a Quickpet icon on the desktop.

Run Quickpet ->Info ->xenialpup updates

This will download and install the updates.

Reboot and update the save, so these new change are now being used.

Do this until it reports nothing new found.

Thanks for xenialpup64-7.5. I just booted into it to see if LibreWolf would run --it does -- and decided to spend some time working with it. My memory was correct. It remains my all time favorite.
Somehow it doesn't seem to have its own thread. If anyone is looking for it, it can be obtained from here, http://murga-linux.com/puppy/viewtopic. ... 078#910078

Thank you for the add , is my first post
how to set desktop screen brightness on puppy xenial 7.5? I've a Asus 1005 2 GB ram
Thank you .

Muzunduleno wrote: ↑Mon Feb 15, 2021 7:15 pm

Thank you for the add , is my first post
how to set desktop screen brightness on puppy xenial 7.5? I've a Asus 1005 2 GB ram
Thank you .

Download and install xbacklight from puppy package manager

Then open terminal and type

xbacklight -set 10

You can adjust value of -set switch at your preference

You can put a Script in /root/Startup to autoregulate brightness at startup

Obrigado consegui , serve para todos os Linux ou só para o xenial ?

Muzunduleno wrote: ↑Mon Feb 15, 2021 10:53 pm

Obrigado consegui , serve para todos os Linux ou só para o xenial ?

Not for all puppy Linux versions. For instance, xbacklight works in Xenialpup and some other puppy Linux versions, while BionicPup needs acpilights to do the same thing. In Tharpup, with my Thinkpad L440 I was able to dim brightness with F5 and F6 keys without needing of xbacklight or acpilights

Thank you very match , I'm not a Linux expert
How can I make a script with xbacklight ?

Muzunduleno wrote: ↑Mon Feb 15, 2021 11:42 pm

Thank you very match , I'm not a Linux expert
How can I make a script with xbacklight ?

Open Geany (the default text editor) paste into these lines:

#!/bin/sh
xbacklight -set 10

And save with a proper name, for instance, xbacklight.sh in /root/Startup directory, then go to /root/Startup and make executable the sh script by giving permissions from right click menu or, open the terminal and type:

chmod 0755 /root/Startup/xbacklight.sh

When I execute he give me this
cannot access '/root/startup/xbacklight.sh': no such file or directory
Can you help me please
Thank you

Muzunduleno wrote: ↑Tue Feb 16, 2021 1:54 pm

When I execute he give me this
cannot access '/root/startup/xbacklight.sh': no such file or directory
Can you help me please
Thank you

This is right, since directory name is Startup, while you are typing startup, in Linux lowercase is not equivalent to uppercase

Is working now I wrote 25 no 10
The desktop still better with 25
Thanks

I've a Bluetooth CSR 4.0 usb but I cannot connect to my
Bluetooth headphones , can you help me please .

Muzunduleno,

If you can move to Bionic64 I may be able to help.

Thank you but I've a xenial and I like it .

Hi there Phil.

I have been looking at setting up my own server at home .
My intention was to use /var/www/ and hiawatha.

That's straight forward enough but looking around the recommendation is to install LAMP.
Linux,Apache2,MySQL,PhP.

After probably 4 unsuccessful attempts at installing MySQL on Puppy versions I'm tending to want to avoid that.

Is it possible to get a LAMP installation on Quickpet ?

My build of xenialpup64 is missing libcups.so.2

Always use this for xenialpup64 for kodi, never figured, that I needed the printer
function.

Where do I get hold of this library file?

Not sure, but is this it? See down in the comments.

viewtopic.php?t=798&hilit=libcups.so.2

My build of xenialpup64 is missing libcups.so.2

Then the XenialPup64 iso file that you downloaded did not download properly.
Check the md5sum. Download the iso file again if you need to.

Or you deleted it.

In either case, the original files should be in /initrd/pup_ro2/usr/lib/

# ls -1 /initrd/pup_ro2/usr/lib/libcups*
/initrd/pup_ro2/usr/lib/libcupscgi.so
/initrd/pup_ro2/usr/lib/libcupscgi.so.1
/initrd/pup_ro2/usr/lib/libcupsfilters.so
/initrd/pup_ro2/usr/lib/libcupsfilters.so.1
/initrd/pup_ro2/usr/lib/libcupsfilters.so.1.0.0
/initrd/pup_ro2/usr/lib/libcupsimage.so
/initrd/pup_ro2/usr/lib/libcupsimage.so.2
/initrd/pup_ro2/usr/lib/libcupsmime.so
/initrd/pup_ro2/usr/lib/libcupsmime.so.1
/initrd/pup_ro2/usr/lib/libcupsppdc.so
/initrd/pup_ro2/usr/lib/libcupsppdc.so.1
/initrd/pup_ro2/usr/lib/libcups.so
/initrd/pup_ro2/usr/lib/libcups.so.2
#

Unless you have a full install.

Xenial32 is a beautiful Puppy, I think it's the best Puppy I've ever used. Rock solid, everything just works 100% on my old laptop, even the fans run beautifully and quiet. I should have used this Puppy a long time ago as my daily driver. Running it with the older Tahr kernel:thumbup:

amethyst wrote: ↑Fri Apr 01, 2022 1:07 pm

Xenial32 is a beautiful Puppy, I think it's the best Puppy I've ever used. Rock solid, everything just works 100% on my old laptop, even the fans run beautifully and quiet. I should have used this Puppy a long time ago as my daily driver. Running it with the older Tahr kernel:thumbup:

Couldn't agree more. It's my all-time favourite 32-bitzer, too.

Back around the beta stage, I ran 7.0.8.1 for a long time.....and I liked it even then. About 18 months ago, I installed the final stable version.....and the memories came flooding back. On this modern, high-spec Pavilion desktop, it's so fast & stable it's almost unreal.

Mike.

@666philb
The kernel in this is getting a bit old . Is there a newer version coming out soon?

amethyst wrote: ↑Fri Apr 01, 2022 1:07 pm

Xenial32 is a beautiful Puppy, I think it's the best Puppy I've ever used. Rock solid, everything just works 100% on my old laptop, even the fans run beautifully and quiet. I should have used this Puppy a long time ago as my daily driver. Running it with the older Tahr kernel:thumbup:

I must agree.
Xenial32 was my first introductory pup into the pup universe and i love it and have 2 versions installed in 2 different locations.

I must add Dpup Stretch 32bit is pretty damn close behind and is also a super puppy distro.

@April :-

April wrote: ↑Sun Apr 03, 2022 10:12 pm

@666philb
The kernel in this is getting a bit old . Is there a newer version coming out soon?

It's easy enough to update the kernel yourself. However, by the time you try to update everything else, you might just as well move up to a newer Puppy.......'cos that's the Puppy 'principle', so far as updates are concerned.

Each and every Puppy is a frozen 'snapshot' in time. And so long as everything works & continues to do what you want, then stick with it. "If it ain't broke, don't try to 'fix' it..."

Phil's released 3 or 4 major Puppies since then. Why would he suddenly want to go back & update a Puppy from 6 years ago? Remember; he's just one person. There isn't a whole team of individuals working on these Pups.....there's only Phil. And there's a limit to what one person can reasonably be expected to do.

Be grateful you've got a brilliant Puppy that works as well as it does!

Mike.

@mikewalsh .

I don't need a gratitude and pompous lecture from you thanks . It detracts from the good work you do do.

Mine was a message to @666philb to see if a 5 year old puppy that works extremely well can be or might be or is to be updated . I'm sure @666philb can answer for himself if he chooses and for your information I do not follow the various distributions as they come out and I have no idea of his intentions, so I ask.

@April
If the system is working well then why update the kernel which could introduce issues or are you one of these people who thrive on strife in life.

Kernel update is usually to cure a known issue not cause them.

I made some 32bit kernels today. @amethyst tested 5.4 one & ok in xenial 7.5 32bit.
If interested, see: viewtopic.php?p=53867&sid=7753d61f7129e ... a4f#p53867

Well, 666philb does updates by producing a newer version of Puppy.
The update to Xenialpup was Bionicpup64 and it's update was Fossapup64.

With each newer version, at the time of it's final release.
All the latest newer versions of core Linux files and programs, Puppy specific programs, and improvements made to Puppies core operations, are included.

some of the effects, with overall operation, you may see with the newer Puppy versions.
Keep in mind that stuff had to be changed in the kernel operations, to deal with the Intel processor security issues, and these affected overall operation.

the kernel choice for a Puppy version release is closely looked at, not a rash choice.
I have seen changing the kernel only provide the affect of now supporting the hardware.
Using an older kernel for very old hardware or a newer kernel for newer or newest hardware.

Ditto what Bigpup wrote. I'd only add that I can think of one reason for updating a kernel rather than using a newer Puppy: application size creep. The applications of a new Puppy version are likely to consume more storage space and require more RAM.

The primary reason for replacing a kernel that works with your computer's hardware is that newer kernels may provide security against the thread of malware discovered after the publication of the older kernel. But such threats are more theoretical than actual, especially for Puppys.

With the exception of your SaveFile or Folder, Puppys' system files are READ-ONLY. If you run under PupMode 13 and do not execute a Save, any malware you may have inadvertently picked up will be wiped at reboot/shutdown. And you can substitute either or both an adrv.sfs or a ydrv.sfs for your SaveFile/Folder and run using only READ-ONLY system files.

The real threat to Xenial's immortality is the age of the glibc it uses. glibc is a 'foundation' system upon which other systems and applications are built and rely. One of those systems is openssl. My understanding is openssl is a basic 'hand-shake' mechanism used to permit communication between an operating system and a web-site. Consequently, but theoretically, openssl can serve as a vector for malware distribution. Before allowing access a website can test to determine whether the openssl used by your operating system is so outdated as to pose a thread; and if so deny access.

Xenial's openssl has already passed EOL. It can not be updated to a current version without first updating glibc. And updating xenial's glibc would break many of its applications and systems. You could replace those with systems and applications with those built against and upon the newer glibc. But you would end up with an operating system now using the more resource demands of a Puppy newer than Xenial and likely to have bugs and flaws absent from the newer Puppy.

But remember, the foregoing horror story is theoretical. Websites are not denying access to xenialpup. In fact, they are not denying access to Tahrpup whose openssl is two years older.

It should be possible to rebuild 7.5 using the latest woof-CE, and get all the security and stability fixes that went into Ubuntu 16.04 point releases since the release of 7.5. It probably won't be a 1:1 replica of 7.5, but I can give it a shot.