TXZ_pup 4.5

[raffy]

But I wonder why a slaxer version like this (12.2). hda is introduced again. oops
..
Maybe I miss some point, but the Puppy Package Manages only references puppy applications

Barry himself contemplated a return to the naming of hard drives as HD* with the use of long-term-support kernel.


As to the package manager, yes, the new system needs to be explained more. There are three visible entry points to package management at the moment:

- the home page (when you open the browser), where you can access the TXZ packages;
- the slaxer package tool in /root;
- the usual Puppy package manager in the menu.

Is there an instruction somewhere about access to the bigger collection of slackware packages?

[big_bass]

Hey Béèm

thanks for testing

you could have just commented out
/root/Startup/numberlock_on
or delete it

Maybe I miss some point, but the Puppy Package Manage only references puppy applications.
But I wonder why a slaxer version like this (12.2). hda is introduced again. oops

I went with the old standard many documents and how to's still refer to hda for drives



the pet get package manager handles pets

the slaxer_pkg_tools2.2 handles slackware packages



it handles slackware packages directly without any conversions the same way its done in the official slackware why thats important is you can build the distro using
packages the same way every other linux distro is built

greatly simplifying whats involved to remove installed base packages customize a build
the way you need it


BTW nobody has ever even tried to build using something other than pet packages before
I pulled it off

Note: no "pets" were injured during the making of this build

one example it took me 6 minutes to install over 350 packages
using TXZ_pup



now for a package finder I built packages that are tested to work
I also use slackwares official packages

and slackbuild scripts

to put it simply anyone that has ever used slackware before
would be at home on TXZ_pup
*plus dependency checking which slackware doesnt have



for advanced users
packages could be auto built using src2pkg then installed by just clicking on the package



there is a lot to explain but the good part is you dont need to learn anything new to install or remove slackware packages if you have done that before

I maintained 100% backend compatibility only I rewrote the whole frontend GUI in X dialog because the official slackware tools run when you are out of the x environment
not very user friendly but it is powerful


*for the moment the devx from slaxer cooking devx package not sfs is fine to use 412-devx-i486-3_SLXR.txz Ill rebuild it with the new files


I will build a new devx to add the new files
I will also update the compiler version and after things are settled in
or offer an optional compiler

future plans
rebuild with a new glibc everything a lot of stuff comes first on the list
before I do that

Joe

[Béèm]

Hello Joe,
Thank you for the explanation.
It makes a little more sense, but still unknown things for me.
I expected a slaxer pkg tool in the menu's, but it isn't there, so I found the one you mentioned in /root.

On one of my HDD's I had a tgz package, which was found with the tool, but to install I had to copy the pkg tool to that directory where it was and only then it came in the list to be selected.

Information panels were flashing by, without having the time to read the information and all of a sudden I got the notice the package was installed.

Didn't find it in the menu and forgot to look in the list of files to see where it was installed.
Will redo the operation after increasing the save file. It's a little short now.

Also I expected some facility to make a list of packages from a slaxer repository, but failed to find that. Maybe there is another trick.

I wanted to select sfs files to be loaded at boot.
The bootmanager presents them, but the add and remove buttons are grayed out.
So I don't see the way to have, f.e., OOo
I prefer the sfs approach in order to avoid a huge save file.

So I'll continue digging.

Regards,
Bernard

EDIT

Well that package happened to be one that can't be run in slaxer.
Below is the picture of the list of packages found to install (one in my case) and the list isn't readable. When increasing the window size, the package becomes visible.

[Lobster]

Hi Joe

Help!

I ran with puppy pfix=ram
it seems to have the ability to talk - even with a lobster using xcowsay
but I can not find xcowsay or flitet running from the command line

Also it wants to move my configuration folder before
opening geany
Is that good?

The Puppy wallpaper setter (with the return of a visual)
did not tile or scale (fit to desktop) but the visual is welcome.

I am in particular intrigued by
/root/slaxer_pkg_tools2.2
This means the creation of a huge potential store of slack software
can be utilised.
If libraries are missing then these too can be added straight from slackware. Is that right?

Is it similar to or compatible with 4.12 (I think it was) which had this compatibility or is it different?

I think the question was asked and it is possible the answer
needs to be explained by another slackware user.

This is not just a puplet
It does not use woof.
It is highly slackware compatible.
You have done something very unique
but what is it?

It looks good, it works well.
I know it has potential
but what is going on.

[Lobster bewildered]

Puppy
Linux roots and branches

[big_bass]

Let the Lobster do the explaining

a little how to use the new unzip tool
use the attachment script called TXZ-intro.tar.gz unzip it then RIGHT click on it
( right click on TXZ-intro.tar.gz an option for unzipper drag n drop 5 comes in the window select it say "yes " thats the new unzip tool
now click on /root/TXZ-intro/TXZ-intro

*thats to see how rox right click works built in for many compressed package formats a simple drag n drop works too


a little surprise

Code: Select all

#! /bin/bash
# all original code from lobster I only edited for TXZ pup
# great job Lobster


THRMFILE=`find /proc/acpi/thermal_zone -name "temperature"`
TEXT=`cat $THRMFILE | cut -c25-30`
flitet "My Core temperature is $TEXT centigrade. Cooking!" | aplay &
xcowsay --cow=Lobster6 My CPU temp is $TEXT - cooking! "$@"
flitet "What is new for TXZ pup" | aplay &
xcowsay --cow=Lobster6 What is new for TXZ_pup? "$@"


flitet "Upgraded scripts and programs." | aplay &
xcowsay --cow=Lobster6 Upgraded scripts and programs. "$@"


flitet "TXZ pup 4.5 New slaxer package tools. More working packages." | aplay &
xcowsay --cow=Lobster6 TXZ pup 4.5 - New slaxer pkg tools2 - more working packages. "$@"
sleep 2


flitet "Latest Fire fox, latest Flash, latest programs." | aplay &
xcowsay --cow=Lobster6 Latest Fire fox, latest Flash, latest programs. "$@"


flitet "Made with TXZ packages, and the best slackware bits." | aplay &
xcowsay --cow=Lobster6 Made with TXZ packages and the best slackware bits."$@"


flitet "Puppy has talking Lobsters. Your arguments are invalid." | aplay &
xcowsay --cow=Lobster6 Puppy has talking Lobsters. Your arguments are invalid. "$@"
cd /
xcowsay --cow=Lobster6 --time=2 --dream=/usr/share/pixmaps/smileys.png "$@" &


aplay /usr/share/audio/2barks.au "$@" &
aplay /usr/share/audio/leave.wav

[8-bit]

Just booted TXZ and I noticed two things.
The desktop text is extra large and outside of of the desktop the text in the terminal is extra small.
Also, my Nvidia ethernet is not recognized.
It uses the forcedeth driver.
So until I get those working, it is a nogo for me.

[Béèm]

I went in rox options to adjust the size.
I went also in global size to adjust.

[big_bass]

Hey 8-bit

what happened is because this is a package build
the order in which packages get installed is important and the old network wizard
over wrote the fixed one because it came later on the list of packages to install
in alphabetical order



could you try installing these then check if the force death module comes up in the list of modules in the GUI

UPDATED the network wizard2 7-13-2010 to include shinobars fix
http://puppy2.org/slaxer/network-wizard ... 3_SLXR.txz
http://puppy2.org/slaxer/netmodules-sla ... 3_SLXR.txz

thanks

about the big size of the text I noticed the age group puppy has the largest users in and thought to be kind to those who may have a hard time reading small text



thanks for posting
Joe

[01micko]

Hi Joe

Remarkable job you've done here.

Lately I have been diving into the guts of Linux and I know what kind of work and smarts have gone into this neat little distro.

I have found that Slackware deals with packages, especially libraries, completely differently to Debian. I wrote a little script here that converts debs, tgz and txz to pets (and it does deal with the 'doinst.sh' nicely). I do not expect you or anyone else to use it for TXZ pup! It's just a script I mainly made for myself, and I just tarted it up a bit to share. You know, to make it 'look' like I know what I'm doing! Of course compiling is my favoured method of making packages, just sometimes I don't get the time to chase down the errors, and I haven't got much smarts when it comes to patching source! (I made another script to help me with that, but that's another story).

I tend to agree with Lobby that this is more than a 'puplet'. Have you thought about registering on Distrowatch? I'm sure Patrick would be interested, as many other Slackers would too, or do they already know ???

All the best mate,

Cheers

Mick

[8-bit]

I can find nothing in the menus to setup or manage printing!
The SETUP-WIZARDWIZARD although it has an entry for CUPS fails.
Also, I cannot seem to access CUPS from the browser either.
I tried "localhost:631" and also my ipaddress:631 with no results.

Am I missing something here?

[big_bass]

yes no cups pre installed on this version yet

I removed cups completely because cups itself was pieced together
with multiple fixes that werent included in the cups packages
available as official packages



and its easier to start clean with an updated version of cups
then it could be used in any other version easily as an upgrade


I discovered this when building with packages
the good news is though I also have packaged cups up
with an updated version number making it much easier to maintain when an upgrade is needed it would better to test the upgraded cups by installing the packages it also keeps the iso size down for those that dont need it
pre installed


I adjusted them to work with firefox since seamonkey was also completely removed
I just dont like the look of the html of cups in firefox


I'll up load the packages this week
*the slackware cups has always worked well for me

Joe

[big_bass]

Hey Mick

Thanks for your post
many nice things said there (friend)

thanks for sharing the work you did with the package converts
you attached in the post
I'll check it out

and thanks for your slaxer logo I used for the desktop
on the cooking version

thanks mate
I always wanted to say that
Joe

[big_bass]

I updated cups to 1.39

it does make the iso 40mb larger
I only had to really hack at the cups package itself
I also removed seamonkey for firefox
so there were additional fixes for that
all the support packages I left standard
the thing is there are also a lot of locales
if cut out all the other languages it would be smaller
and packaged the locales separately

since I already added many fixes and added cups to the iso
to make sure that it would work

do we have a lot of people who need or use cups

I can do it but is there a demand for it or not let me know please

well since I know it will work live cd I can remove cups again
and offer the packages to install 40mb is a bit heavy if you
dont have to print

Joe

[big_bass]

I fixed all the minor bugs that were listed in this thread
and I am uploading the next iso ATM it will be ready in 2 hours to download

A few people tried to define what TXZ is

TXZ is built with TXZ packages everyone knows that puppy is built with pets
different pets for different versions which gets more complex with different
possible versions using different distros as a base

TXZ uses its own package management not only to install , remove ,view and check for dependencies it is also the "build tool used to build itself"
so it was a long process to code the entire front end of package tools in Xdialog
then build the packages in the TXZ format ( over 400 packages )


I used Xdialog to keep it light and fast and since it was compiled for gtk2 it follows the theme well


but now there is no need for a "fat free" type of iso
all the pre installed packages and their contents are listed and removable
removing a lot of guess work keeping things more transparent to what has changed from package to package

it takes an incredible about of time to dominate all the packages files, configurations and unique locations "puppy uses" for each new version
most people dont care they just download an iso



but slackware users are the rarest most careful of linux users they have to be able to know how everything works( TRANSPARENTLY) because most of them care for their system so much that most of them compile all their own packages
or only use official packages

thats why I am doing things differently but not differently for those that do use slackware they would be at home

a slackware package is a standard (it is known world wide)


what has always made slackware difficult for new users is just to get started

TXZ pup bridges that learning gap and lets you get started learning how linux
works without the pain involved setting it all up learning is part of the fun
it doesnt have to be painfully difficult

================how to ===================================

just click on a TXZ package it asks if you want to install it (thats easy)

just right click on a TXZ package and in rox an option for unzipper drag N drop 5
comes up what that does is auto name and decompress the package in a folder for you so you can see whats inside it before installing " if you wanted to check "

lets say you wanted to install any files you could place them in root
then click on slaxer_pkg_tools2.2

or if you like to be clean and have all the packages are in a special folder just copy slaxer_pkg_tools2.2 into that folder it will put all those packages and only them in the GUI nice hugh thats why slaxer_pkg_tools2.2 is just a script its portable its a front end tool
you can place it anywhere (thats easy )

same thing goes for uninstalling you can do multiple uninstalls from the GUI
just check the boxes (thats easy )

(thats easy too) Im not trying to make it complex I want it easy . I want it puppy
I want it stable. I got it now



P.S Note: no "pets" were injured during the making of this build

everyone does a different part I can only do my part
I cant even define that part yet it is moving and growing

Joe

[Béèm]

I already found out to put the slaxer_pkg_tool eventually in an other directory where txz packages can be stored.

What I don't see, maybe missed the point, is where is there a repository and how can I connect to it if I have the need for a package.

[gronos04]

Hi Beem

Here is the slackware package search

http://slackfind.net/en/packages/search ... tversion=5

Warren

[big_bass]

I uploaded the new iso the server is slow ATM for downloads
must be getting a lot of downloads at the same time
so I havent checked the md5sum on the download yet

if you have the 7-7-2010 iso you need this fix
http://www.puppy2.org/slaxer/mime-tgz-f ... 3_SLXR.txz

for the click on tgz package to install the 7-13-2010 has the fix built in



89f44e890470e19267f4cd329c5d29c0 TXZ_Pup-4.50-7-13-2010.iso

the next iso is called 7-13-2010 I post the link when I confirm the iso

if anyone confirmed the iso md5 let me know I'll try again tomorrow

[Sylvander]

Why is it that some of the recently released Puppies [including TXZ_Pup] won't boot on my 2002 hardware?

[Béèm]

Because it boots on my 2002 hardware.

[Béèm]

I have a usb connected HDD and a USB flash drive.
Some days ago I booted with the USB HDD connected and got the sda1-sda7 partitions (sda3 being the extended one)

Now I added the USB flash one which only has one partition.

The USB HDD became sdb1-sdb7 (sdb3 being the extended one)
So far so good.

But the USB flash was sda1-sda7, but only sda1 can be mounted as the others don't exist.

What is going on here?