(OLD) (ARCHIVED) Puppy Linux Discussion Forum Forum Index (OLD) (ARCHIVED) Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info

This forum can also be accessed as http://oldforum.puppylinux.com
It is now read-only and serves only as archives.

Please register over the NEW forum
https://forum.puppylinux.com
and continue your work there. Thank you.

 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups    
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Fri 25 Sep 2020, 06:58
All times are UTC - 4
 Forum index » Advanced Topics » Cutting edge
TazPuppy 5.0 rc2
Moderators: Flash, Ian, JohnMurga
This forum is locked: you cannot post, reply to, or edit topics.   This topic is locked: you cannot edit posts or make replies. View previous topic :: View next topic
Page 57 of 80 [1186 Posts]   Goto page: Previous 1, 2, 3, ..., 55, 56, 57, 58, 59, ..., 78, 79, 80 Next
Author Message
oui

Joined: 20 May 2005
Posts: 3606
Location: near Woof (Germany) :-) - 3 PC's: DELL SX280 750 MB Pentium4, Acer emachines 2 GB AMD64. DELL XPS15

PostPosted: Sat 02 Mar 2019, 18:44    Post subject:  

Hi
as it is possible to convert the tazpkg's into *.pets, did some one already try to convert

libfirefox

and to use it in puppy to look some youtube's using little browsers (midori etc.)
Back to top
View user's profile Send private message 
s243a

Joined: 02 Sep 2014
Posts: 2626

PostPosted: Sat 02 Mar 2019, 19:59    Post subject:  

s243a wrote:
I'm not sure if it's updated but in the last version "beta 23" I have two fixes for:
Code:

/usr/bin/make-devx


The first suggestion is to make the script architecture independent by putting something like the following at the top of the script:

Code:

if [ -f /etc/slitaz/slitaz.conf ]; then
  . /etc/slitaz/slitaz.conf #Comment this line out if you don't want to use distro defualts.
fi
WEBSITE=${MIRROR_URL:-"http://mirror1.slitaz.org"}
DIRPKG=${SLITAZ_RELEASE:-'next64'}


note that where I have 'next64' as the default, you would put 'cooking' as the default. The point is to take the mirror and the release from slizaz.conf.

related to this in the function "download_pkgs", one has to replace "cooking" with "$DIRPKG" in the line
Code:

wget -nc --timeout=10 $WEBSITE/packages/cooking/$pkgname.tazpkg -O cooking/slitaz-devx/$pkgname.tazpkg

with gives:
Code:

wget -nc --timeout=10 $WEBSITE/packages/$DIRPKG/$pkgname.tazpkg -O $curdir/slitaz-devx/$pkgname.tazpkg


My second fix is to create all the necessary build directories. Around line #20 (now line #24) I have replaced:

Code:

 curdir="$1"
 
 if [ ! -e $curdir ]; then
  echo "Create working folder: $curdir"
  mkdir -p $curdir 2>/dev/null
  if [ $? -ne 0 ]; then
  echo "Failed to create working folder"
  exit
  fi
 fi
else
 echo "Usage: $cmd1 [working folder]"
 echo "Creates DEVX module for compiling"
 exit
fi


with

Code:

 curdir=`realpath "$1"`
 while read aDir; do
   if [ ! -e $aDir ]; then
     echo "Create working folder: $aDir"
     mkdir -p $aDir 2>/dev/null
     if [ $? -ne 0 ]; then
       echo "Failed to create working folder $aDir"
       exit
     fi
   fi
 done <<EOM
$curdir
$curdir/devx-rootfs
$curdir/slitaz-devx
EOM
else
 echo "Usage: $cmd1 [working folder]"
 echo "Creates DEVX module for compiling"
 exit
fi

#cd $curdir


I found one more issue. In the function process_package we need to make the path to the receipt relative. Currently it is:
Code:

. /receipt


but it should be

Code:

. ./receipt

Last edited by s243a on Sat 02 Mar 2019, 20:15; edited 3 times in total
Back to top
View user's profile Send private message Visit poster's website 
s243a

Joined: 02 Sep 2014
Posts: 2626

PostPosted: Sat 02 Mar 2019, 20:05    Post subject:  

oui wrote:
Hi
as it is possible to convert the tazpkg's into *.pets, did some one already try to convert

libfirefox

and to use it in puppy to look some youtube's using little browsers (midori etc.)


Extract the package:
Code:

tazpkg extract package.tazpkg


then use dir2pet to create a pet package.
Back to top
View user's profile Send private message Visit poster's website 
s243a

Joined: 02 Sep 2014
Posts: 2626

PostPosted: Sun 03 Mar 2019, 04:33    Post subject:  

I noticed something in the /etc/profile script that could be improved.

Around line one 170 we have the following code:

Code:

for profile_script in $(ls -1 /etc/profile.d) ; do
    #xlog  "Sourcing $profile_script ..."
   [ "$(echo -n "$profile_script" | grep 'txt$')" != "" ] && continue
   . /etc/profile.d/$profile_script
done


The issue here is that sometimes in /etc/profile.d there are separate scripts depending on the shell. For instance if one installs "gawk" there is a script gawk.csh (for the c shel) and also a gawk.sh for bourne compatible shells like bash and ash. We need some kind of logic that checks for shell dependent implementations of the profile.d script and picks the version that best matches the shell (based on the extension).

For example in the csh version we have:
Code:

alias gawkpath_default 'unsetenv AWKPATH; setenv AWKPATH `gawk -v x=AWKPATH "BEGIN {print ENVIRON[x]}"`'

but the setenv command only works for csh and not for bash, ash and dash.
Back to top
View user's profile Send private message Visit poster's website 
s243a

Joined: 02 Sep 2014
Posts: 2626

PostPosted: Sun 03 Mar 2019, 06:25    Post subject:  

I think TazPup has the following issue (I'll verify later) but the 64bit version I'm trying to make certainly has this issue.

I noticed the following error in the boot log:

Code:

missing or unknown command

Usage: udevadm [--help] [--version] [--debug] COMMAND [COMMAND OPTIONS]

  info         query sysfs or the udev database
  trigger      request events from the kernel
  settle       wait for the event queue to finish
  control      control the udev daemon
  monitor      listen to kernel and udev events
  test         test an event run
  test-builtin test a built-in command


I was able to trace this error to line #32 to #35 of:
/etc/init.d/rcS
Code:

if [ -d '/etc/udev/hwdb.d' ]; then
   echo 'Creating the udev hardware database...'
   udevadm hwdb --update
fi


hwdb is not a valid command for udevadm as per the manpage:
https://linux.die.net/man/8/udevadm

Some versions of udevadm have a --reload option which might do what this statement is trying to achieve. However, I don't believe that the version of udevadm that comes with slitaz has this option.
Back to top
View user's profile Send private message Visit poster's website 
oui

Joined: 20 May 2005
Posts: 3606
Location: near Woof (Germany) :-) - 3 PC's: DELL SX280 750 MB Pentium4, Acer emachines 2 GB AMD64. DELL XPS15

PostPosted: Wed 06 Mar 2019, 19:45    Post subject:  

Hi

As I did write divers messages with comments on SliTaz (without Pup) in the last day, and did see a new ISO serie appear at http://mirror/slitaz.org, I did try to make a step more in direction of TazPup and try to build with the old as well as with the new iso's. I did try it out Slitaz, out Tazpup and out Bionicpup64. as well 32 bit iso als 64 bit iso of course and as well local as onine Laughing

new iso's did be created, about 99 Mb. but no one able to start (kernel panik).

my goal would be have to build Tazpup64. Out whitch is for me total undifferent (I also die download als packages from SliTaz from above url .../packages/cooking and have them on the disk). Some examples of errors in the console:


root# ./clean-workspace.sh
Deleting slitaz-rootfs...
Deleting tazpup-preiso...
root# ./make-tazpup.sh
Preparing working folders...
Mounting slitaz-rolling-core64.iso...
Copying rootfs gz...
Extracting rootfs gz...
cpio: unsupported cpio format, use newc or crc
touch: cannot touch '/root/tazbuild/slitaz-rootfs/tmp/tazpkg-local.lock': No such file or directory

and 6 other for tazopkg0skipdep.lock etc.
...
Removing block device files...
/usr/bin/tazpkg: .: line 11: can't open '/usr/bin/gettext.sh': No such file or directory

and 14 such analog lines for, that is the question!

Is there perhaps a more detailled text as the READ.ME?

Kind regards
Back to top
View user's profile Send private message 
s243a

Joined: 02 Sep 2014
Posts: 2626

PostPosted: Thu 07 Mar 2019, 03:38    Post subject:  

oui wrote:
Hi

As I did write divers messages with comments on SliTaz (without Pup) in the last day, and did see a new ISO serie appear at http://mirror/slitaz.org, I did try to make a step more in direction of TazPup and try to build with the old as well as with the new iso's. I did try it out Slitaz, out Tazpup and out Bionicpup64. as well 32 bit iso als 64 bit iso of course and as well local as onine Laughing

new iso's did be created, about 99 Mb. but no one able to start (kernel panik).

I actually did get get mistfire's build script to work with the slitaz-rolling-core64.iso but as mistfire note's in another post, this iso actually only has 64bit kernal modules. The actual binary libraries on the iso are 32 bits.

Quote:

my goal would be have to build Tazpup64.

I actually started trying to do this. The last updload of my modfied build kit is at:
https://www.dropbox.com/s/owr19jmja3fakgn/tazpup-builder64-p-a-3.tar.gz?dl=0

but there are some untested changes. The way, I'm doing it the Slitaz iso is only to create the build system. By that I mean that the package manager is executed in a chroot environment located at:
Code:

$curdir/slitaz-rootfs

but the actual filesystem for the iso is located at:
Code:

$curdir/slitaz-rootfs$prefix

This works because with tazpkg there is a --root option that allows you to install packages under a different root then the root which tazpkg is ran under. From the function install_pkg() (located within the file make-tazpup_functions.sh)
Code:

tazpkg $options install $bname --root=$prefix


Quote:
root# ./clean-workspace.sh
Deleting slitaz-rootfs...
Deleting tazpup-preiso...
root# ./make-tazpup.sh
Preparing working folders...
Mounting slitaz-rolling-core64.iso...
Copying rootfs gz...
Extracting rootfs gz...
cpio: unsupported cpio format, use newc or crc
touch: cannot touch '/root/tazbuild/slitaz-rootfs/tmp/tazpkg-local.lock': No such file or directory

and 6 other for tazopkg0skipdep.lock etc.
...


There isn't enough info for me to troubleshoot here. Try executing the script like this:
Code:

sh -x  ./clean-workspace.sh 2>&1 | tee build.log

then open up build.log in a text editor like geany.

Quote:

Removing block device files...
/usr/bin/tazpkg: .: line 11: can't open '/usr/bin/gettext.sh': No such file or directory
and 14 such analog lines for, that is the question!

Is there perhaps a more detailled text as the READ.ME?

Kind regards


Look in
Code:

$curdir/slitaz-rootfs/usr/bin/gettext.sh

and see if the file is there. I suspect it isn't. You can either copy this file from a puppy or TazPup iso or you can install the gettext package.

P.S. if you actually try my buildscript then either edit or delete the file that says "defaults". For instance if you delete the following two lines:
Code:

IMGPUP="/root/spot/Downloads/slacko64-6.9.9.9-uefi-k4.9-FF-LO.iso"
IMG="/root/spot/Downloads/slitaz-rolling-core64.iso"

then the script will prompt you for the location of these ISOs. Note that I don't don't have an ISO with a properly configured window manager yet, so you might want to wait a bit.
Back to top
View user's profile Send private message Visit poster's website 
mistfire

Joined: 04 Nov 2008
Posts: 1424
Location: PH

PostPosted: Fri 22 Mar 2019, 23:38    Post subject:  

TazPuppy beta 25 released

Changes:
* Basic cache cleaning. This will trigger the cleaner on the following scenarios:
+ Upon shutdown if the save session was a save file or in multisession mode
+ When periodic save on flash ran or execute save2flash
+ When the free disk memory was below 10%

This also can be run manually by typing this command
Code:
sudo purge-cache.sh


* Basic Mouse Wizard for configuring mouse
* Some fixes

Download: https://drive.google.com/file/d/1UYze6NOrNzy7FzWw4Afw5fTeepy4coui/view?usp=sharing
MD5 Checksum: c6b570bda89f5b4ce47af14235c22326


Build kit: https://drive.google.com/file/d/1sNyesbvwR4Xz9dMLDR1LwM_2InAcfYR-/view?usp=sharing
Back to top
View user's profile Send private message 
wiak

Joined: 11 Dec 2007
Posts: 2075
Location: not Bulgaria

PostPosted: Sun 24 Mar 2019, 01:45    Post subject:  

mistfire wrote:
TazPuppy beta 25 released

Changes:
* Basic cache cleaning. This will trigger the cleaner on the following scenarios:
+ Upon shutdown if the save session was a save file or in multisession mode
+ When periodic save on flash ran or execute save2flash
+ When the free disk memory was below 10%


The only one I'm not personally convinced about is that last on - freeing up cache. I experimented with that years ago and certainly it appears nice when for example the 'free' command shows more free RAM available. However, I stopped using such purge cache routines because I now accept that Linux does a pretty good and more intelligent job at freeing up cache automatically when it needs more actual free RAM. Cache is important since it speeds things up when data needs to be re-used and Linux kernel itselfs will release cache when it is actually needed; I.e. it won't allow the system to collapse until really there is no free RAM left despite all cache having been auto-purged. You can prove that by observing free RAM plus cache by continually running the 'free' command whilst adding more and more heavy HTML paged to tabs in your browser: then you will observe Linux itself freeing up cache to provide the extra RAM these new tabs need. Eventually, no more cache is available to free up, the RAM free itself runs out, and the system will freeze...

But no manual purge cache script is required or even good.

wiak

_________________
WeeDogLinux forum: https://weedoglinux.rockedge.org/viewforum.php?f=4
Tiny Linux Blog: https://www.tinylinux.info/
Check Firmware: http://murga-linux.com/puppy/viewtopic.php?p=1022797
Back to top
View user's profile Send private message 
mistfire

Joined: 04 Nov 2008
Posts: 1424
Location: PH

PostPosted: Sun 24 Mar 2019, 03:19    Post subject:  

@wiak the basic cache cleaning was not cleaning ram, but it was cleaning the pup_rw layer in order to minimize the disk usage and utilize ang free disk space very well
Back to top
View user's profile Send private message 
wiak

Joined: 11 Dec 2007
Posts: 2075
Location: not Bulgaria

PostPosted: Sun 24 Mar 2019, 07:07    Post subject:  

mistfire wrote:
@wiak the basic cache cleaning was not cleaning ram, but it was cleaning the pup_rw layer in order to minimize the disk usage and utilize ang free disk space very well


Okay, thanks mistfire.

_________________
WeeDogLinux forum: https://weedoglinux.rockedge.org/viewforum.php?f=4
Tiny Linux Blog: https://www.tinylinux.info/
Check Firmware: http://murga-linux.com/puppy/viewtopic.php?p=1022797
Back to top
View user's profile Send private message 
darry19662018

Joined: 31 Mar 2018
Posts: 731
Location: Rakaia

PostPosted: Fri 05 Apr 2019, 22:14    Post subject:  

mistfire wrote:
TazPuppy beta 25 released

Changes:
* Basic cache cleaning. This will trigger the cleaner on the following scenarios:
+ Upon shutdown if the save session was a save file or in multisession mode
+ When periodic save on flash ran or execute save2flash
+ When the free disk memory was below 10%

This also can be run manually by typing this command
Code:
sudo purge-cache.sh


* Basic Mouse Wizard for configuring mouse
* Some fixes

Download: https://drive.google.com/file/d/1UYze6NOrNzy7FzWw4Afw5fTeepy4coui/view?usp=sharing
MD5 Checksum: c6b570bda89f5b4ce47af14235c22326


Build kit: https://drive.google.com/file/d/1sNyesbvwR4Xz9dMLDR1LwM_2InAcfYR-/view?usp=sharing


Wow late to the party. This has come along way Mistfire - very nice - a good pup indeed.

_________________
Puppy Linux Wiki: http://wikka.puppylinux.com/HomePage

https://freemedia.neocities.org/
Back to top
View user's profile Send private message Visit poster's website 
thinkpadfreak

Joined: 17 Oct 2016
Posts: 98

PostPosted: Sun 07 Apr 2019, 01:31    Post subject:  

Hello.

I heard from another user of tazpuppy that on beta 25 mplayer requires libjpeg.so.9 and that it does not start.
So I advised him to update libjpeg package, and mplayer started.

But he reports that, after the update, x stopped starting, complaining about missing libjpeg.so.8.

I wonder if this issue is due to slitaz system (repository or software database, or some other things).
Back to top
View user's profile Send private message 
mistfire

Joined: 04 Nov 2008
Posts: 1424
Location: PH

PostPosted: Sun 07 Apr 2019, 23:48    Post subject:  

@thinkpadfreak take a look at this forum
http://forum.slitaz.org/topic/after-20th-of-march-packages-update-slitaz-does-not-start-its-gui

They upgrade the libjpeg

I suggest this solution:
1. Boot TazPuppy without X using pfix=nox boot parameter
2. On TazPuppy terminal login as root
3. Use this the following command
Code:

tazpkg recharge
tazpkg upgrade


4. Restart the TazPuppy by typing reboot and press enter
Back to top
View user's profile Send private message 
thinkpadfreak

Joined: 17 Oct 2016
Posts: 98

PostPosted: Mon 08 Apr 2019, 01:15    Post subject:  

Thank you, mistfire.

I will tell Japanese Forum members about the solution.
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 57 of 80 [1186 Posts]   Goto page: Previous 1, 2, 3, ..., 55, 56, 57, 58, 59, ..., 78, 79, 80 Next
This forum is locked: you cannot post, reply to, or edit topics.   This topic is locked: you cannot edit posts or make replies. View previous topic :: View next topic
 Forum index » Advanced Topics » Cutting edge
Jump to:  

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


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.1906s ][ Queries: 12 (0.0882s) ][ GZIP on ]