TazPuppy 5.0 rc2
TazPuppy beta 22 release
Changes:
* Improved initrd:
-It can now load up to 7 extra SFS modules
-Improved USB storage device detection
-Supports usbwait boot parameter
* Improved wired network detection.
* Improved shutdown (Note it clears tazpkg cached package and other cache files if the saved session was a save file or in multisession mode)
* Improved tazcook-sfs
Download: https://drive.google.com/file/d/1siyfI4 ... sp=sharing
MD5 Checksum: 88dd49c1a38f8b704b83eac1943c5c0b
Build kit: https://drive.google.com/file/d/1lWsGGR ... sp=sharing
Changes:
* Improved initrd:
-It can now load up to 7 extra SFS modules
-Improved USB storage device detection
-Supports usbwait boot parameter
* Improved wired network detection.
* Improved shutdown (Note it clears tazpkg cached package and other cache files if the saved session was a save file or in multisession mode)
* Improved tazcook-sfs
Download: https://drive.google.com/file/d/1siyfI4 ... sp=sharing
MD5 Checksum: 88dd49c1a38f8b704b83eac1943c5c0b
Build kit: https://drive.google.com/file/d/1lWsGGR ... sp=sharing
-
- Posts: 98
- Joined: Mon 17 Oct 2016, 05:11
I have installed beta 22.
I thank you for making it possible to load up to 7 extra sfs modules.
To be cautious, I will use 6 extra sfs modules at most, as wise men say.
Because of the ability to load up to 7 extra sfs modules, I hope users of other Puppies can use tazpuppy with more ease than before.
I thank you for making it possible to load up to 7 extra sfs modules.
To be cautious, I will use 6 extra sfs modules at most, as wise men say.
Because of the ability to load up to 7 extra sfs modules, I hope users of other Puppies can use tazpuppy with more ease than before.
TazPuppy Beta 23 released
Changes:
* Small fixes in initrd
* Bacon is now added on devx-list for building devx module
* Remember hardware setup on shutdown
Download: https://drive.google.com/file/d/1wSWovZ ... sp=sharing
MD5 Checksum: ad0104fa91c8ea7eed643ce7be9e6f5c
Build kit: https://drive.google.com/file/d/16vbJrR ... sp=sharing[/url]
Changes:
* Small fixes in initrd
* Bacon is now added on devx-list for building devx module
* Remember hardware setup on shutdown
Download: https://drive.google.com/file/d/1wSWovZ ... sp=sharing
MD5 Checksum: ad0104fa91c8ea7eed643ce7be9e6f5c
Build kit: https://drive.google.com/file/d/16vbJrR ... sp=sharing[/url]
The iron-linux browser doesn't work:mistfire wrote:TazPuppy beta 22 release
Changes:
* Improved initrd:
-It can now load up to 7 extra SFS modules
-Improved USB storage device detection
-Supports usbwait boot parameter
* Improved wired network detection.
* Improved shutdown (Note it clears tazpkg cached package and other cache files if the saved session was a save file or in multisession mode)
* Improved tazcook-sfs
Download: https://drive.google.com/file/d/1siyfI4 ... sp=sharing
MD5 Checksum: 88dd49c1a38f8b704b83eac1943c5c0b
Build kit: https://drive.google.com/file/d/1lWsGGR ... sp=sharing
Code: Select all
sh-4.4$ strace iron
execve("/usr/bin/iron", ["iron"], [/* 46 vars */]) = -1 EFAULT (Bad address)
--- SIGSEGV {si_signo=SIGSEGV, si_code=SI_KERNEL, si_addr=0} ---
+++ killed by SIGSEGV +++
Segmentation fault
After a bit of investigation it might be a memory issue. The normal puppylinux package manager directly saves to the save-layer. I'm not sure that tazpkg does this.mistfire wrote:@s243a here are the suggested options to fix the issue:
1. try to swap kernel by using the kernel and zdrv file of other puppies
2. check the iron browser dependencies.
3. update the builtin packages
I'm working on a script to make a suitable chroot environment directly on the USB to run tazpkg. I haven't even started the debugging process yet.
I say that it might be a memory issue because when I tried running tazpkg from the command line it failed due to insufficient memory. An alternative solution would be to use a swap file. I don't like using swap files when running off a USB because if they USB gets unplugged everything gets messed up. Also for USB 2.0 and earlier the I/O speed is very slow.
Edit 1: So my above script ran without errors. I then chrooted into the newly created folder:
Code: Select all
chroot /mnt/home/symlinks /bin/bash
Code: Select all
tazpkg --forced git-install iron-linux
Code: Select all
iron
Is this the most recent version of TazWoof? I need to build a devX for the 64 bit version of TazPup. See thread:mistfire wrote:This is the experimental TazWoof. This will build TazPup entirely from Slitaz Packages. The missing part was compiling kernel for TazPup (I put a blank function to place that routine) also make live cd was disabled.
I hope someone will complete this build system.
Download: https://drive.google.com/file/d/1VyhLlf ... sp=sharing
TazPup64 (beta 23?)
Re: TazPuppy Beta 23
I think the version in the first post of this thread is the latest. Anyway, I've been trying to see if you can use the build kit to produce a 64 bit iso. I think that to do this we have to change the mirror for the packages using the following command:mistfire wrote:
Build kit is now available if you want to build your own tazpuppy.
https://drive.google.com/file/d/16vbJrR ... sp=sharing
For a 64bit build we will need one of the following urlssetup-mirror
Setup the URL for the mirror (setup-mirror or -sm). Command will ask for the URL of the new mirror. Note that you can also modify the main /var/lib/tazpkg/mirror file. The URL must point to the directory containing the packages.info and packages.
# tazpkg setup-mirror
http://mirror.slitaz.org/packages/next64/
http://mirror1.slitaz.org/packages/next64/
in the mirror file:
Code: Select all
/var/lib/tazpkg/mirror
@s243a
The tazpup devx was not yet updated yet it just works. If you want a fresh devx sfs. Just run this command on terminal. It requires internet connection.
The tazpup devx was not yet updated yet it just works. If you want a fresh devx sfs. Just run this command on terminal. It requires internet connection.
Code: Select all
make-devx [working folder to creating devx module]
Last edited by mistfire on Tue 26 Feb 2019, 00:30, edited 1 time in total.
-
- Posts: 902
- Joined: Mon 22 Jun 2009, 01:36
- Location: Philadelphia, PA
Good morning. I did download it, and thank you very much.mistfire (in part) wrote:TazPuppy Beta 23 released
Download: https://drive.google.com/file/d/1wSWovZ ... sp=sharing
I'm using the TazWeb browser, on this Dell laptop E6410.
First-time user.
As I recall, the Grub4Dos command lines included
kernel /TazPup/vmlinuz psubdir=TazPup
initrd /TazPup/initrd.xz
Then, boot.
Thanks a lot.
Sorry I have nothing to contribute at present; I hope to read the thread and learn.
Sheldon
Dell E6410: BusterPup, BionicPup64, Xenial, etc
Intel DQ35JOE, Dell Vostro 430
Dell Inspiron, Acer Aspire One, EeePC 1018P
Intel DQ35JOE, Dell Vostro 430
Dell Inspiron, Acer Aspire One, EeePC 1018P
Re: TazPuppy Beta 23
From the first post of this thread:
https://pastebin.com/xiZz0Kta
**Note the iso was still built just not packes alphabetically between "a" and core-utils.
I think that any patches that are applied to TazPkg, need to be applied fefore the packages are installed. I believe this impacts both the 32bit version and the 64bit version that I'm trying to build. Recall that when we switched to core-utils we had to remove some busybox idiosyncrasies.
Edit #1 maybe it is just core-utils that needs to be treated separately. However, for a 64 bit system, I'm adding a prefix for a clean build now, so the only purpose of the TazPup iso is to get a working package manager (i.e. tazpkg). I will post my updated build-kit in the other thread.
Edit #2 I made some progress on this but I might not test this build kit because I think there are further changes that I need to make before it will work.:
64bit pre alpha 2 build kit:
https://www.dropbox.com/s/8ide4zsufh0vv ... pha-2?dl=0
Pastbin script for the modified build script:
https://pastebin.com/rGa4jJCp
I noticed that when I was trying to use the build-kit to build a 64bit version that everything fell apart once I got to core-utils and nothing installed after it. Output posted at:mistfire wrote:
Build kit is now available if you want to build your own tazpuppy.
https://drive.google.com/file/d/16vbJrR ... sp=sharing
https://pastebin.com/xiZz0Kta
**Note the iso was still built just not packes alphabetically between "a" and core-utils.
I think that any patches that are applied to TazPkg, need to be applied fefore the packages are installed. I believe this impacts both the 32bit version and the 64bit version that I'm trying to build. Recall that when we switched to core-utils we had to remove some busybox idiosyncrasies.
Edit #1 maybe it is just core-utils that needs to be treated separately. However, for a 64 bit system, I'm adding a prefix for a clean build now, so the only purpose of the TazPup iso is to get a working package manager (i.e. tazpkg). I will post my updated build-kit in the other thread.
Edit #2 I made some progress on this but I might not test this build kit because I think there are further changes that I need to make before it will work.:
64bit pre alpha 2 build kit:
https://www.dropbox.com/s/8ide4zsufh0vv ... pha-2?dl=0
Pastbin script for the modified build script:
https://pastebin.com/rGa4jJCp
Last edited by s243a on Tue 26 Feb 2019, 08:30, edited 4 times in total.
I noticed in the tazpkg manual that it says that for dependencies it prefers local packages in the same directory as the one you are installing
For the "non-cloud mode" (i.e. local mode), I think the build kit should take advantage of this by first copying all packages to be installed into the root file system.
It also may be useful to combine this technique with an install list:
install
This command allows the installation of a local package with the .tazpkg extension (install or -i).
Option --forced allows you to update an already installed package. Option --newconf allows you to rewrite all user configuration files using the new files from a package. Option --nodeps allows you to install only a specified package without its dependencies.
When TazPkg installs package dependencies, it prefers local packages (i.e. dependent packages located in the same folder[/b\ as installed packages) over mirrored/cached packages with the --local option. It is useful when you want to install a lot of already downloaded packages and their dependencies without the need of a network connection.
For the "non-cloud mode" (i.e. local mode), I think the build kit should take advantage of this by first copying all packages to be installed into the root file system.
It also may be useful to combine this technique with an install list:
get-list, install-list, get-install-list
Get and/or install a set of packages listed in a file. This command allows you to work with the several packages with a single command.
All options are the same as for respective simple commands: get, install and get-install.
# tazpkg install-list my-packages.list
# tazpkg get-install-list my-packages.list --forced
Re: TazPuppy Beta 23
In the latest build-kit I noticed something that caused me a bit of grief when trying to build a 64 bit version.mistfire wrote:I learned that someone in the forum was combining tiny core linux and puppy.
I wonder if someone was attempting to combine slitaz and puppy?
Build kit is now available if you want to build your own tazpuppy.
https://drive.google.com/file/d/16vbJrR ... sp=sharing
My issue was, depending on which packages One installs a symlink might be created from /bin/lzma to xz and this will over-ride the full version of llzma if installed. This symlinking causes problems with converting files in tazpup. For instance on line#35 of /usr/libexec/tazpkg/pack we have:
Code: Select all
*) lzma e fs.cpio.lzma -si;;
Code: Select all
if [ -f $curdir/slitaz-rootfs$prefix/usr/bin/lzma ]; then #Added by s243a
rm -f $curdir/slitaz-rootfs$prefix/bin/lzma
fi
TazPuppy beta 24 released
Changes:
* A bug where cannot remember loaded sfs is fixed
* Unable to find swap partition on UEFI is fixed
* With automatic fixing of missing essential cache files
* Ability to force update the essential cache files by using this boot parameter -- forceupdate
* Some fixes on tazpkg and sfs_load
* Improved cleanup on shutdown
Download: https://drive.google.com/file/d/1sZoT-w ... sp=sharing
MD5 Checksum: 174d363471775e01f31a62b6c7a2a2d9
Build kit: https://drive.google.com/file/d/1nCcrJX ... sp=sharing
Changes:
* A bug where cannot remember loaded sfs is fixed
* Unable to find swap partition on UEFI is fixed
* With automatic fixing of missing essential cache files
* Ability to force update the essential cache files by using this boot parameter -- forceupdate
* Some fixes on tazpkg and sfs_load
* Improved cleanup on shutdown
Download: https://drive.google.com/file/d/1sZoT-w ... sp=sharing
MD5 Checksum: 174d363471775e01f31a62b6c7a2a2d9
Build kit: https://drive.google.com/file/d/1nCcrJX ... sp=sharing
-
- Posts: 902
- Joined: Mon 22 Jun 2009, 01:36
- Location: Philadelphia, PA
I'm not sure if this was updated in the last build kit or not but on the previous build kit there was no internet in the chroot environment. To fix this one must do the following:
as was noted on archiwiki.
https://wiki.archlinux.org/index.php/Chroot
The consequence of this is that cloud mode didn't work .
Code: Select all
cp -f /etc/resolv.conf $curdir/slitaz-rootfs/etc/resolv.conf
https://wiki.archlinux.org/index.php/Chroot
The consequence of this is that cloud mode didn't work .
I'm not sure if it's updated but in the last version "beta 23" I have two fixes for:
The first suggestion is to make the script architecture independent by putting something like the following at the top of the script:
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
with gives:
My second fix is to create all the necessary build directories. Around line #20 (now line #24) I have replaced:
with
Code: Select all
/usr/bin/make-devx
Code: Select all
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'}
related to this in the function "download_pkgs", one has to replace "cooking" with "$DIRPKG" in the line
Code: Select all
wget -nc --timeout=10 $WEBSITE/packages/cooking/$pkgname.tazpkg -O cooking/slitaz-devx/$pkgname.tazpkg
Code: Select all
wget -nc --timeout=10 $WEBSITE/packages/$DIRPKG/$pkgname.tazpkg -O $curdir/slitaz-devx/$pkgname.tazpkg
Code: Select all
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
Code: Select all
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
Last edited by s243a on Sun 03 Mar 2019, 00:15, edited 5 times in total.