Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Sun 15 Dec 2019, 03:43
All times are UTC - 4

 Forum index » Advanced Topics » Puppy Derivatives
TazPup64 (pre-alpha17) - getting close to alpha quality
Moderators: Flash, JohnMurga
Post new topic   Reply to topic View previous topic :: View next topic
Page 2 of 7 [92 Posts]   Goto page: Previous 1, 2, 3, 4, 5, 6, 7 Next
Author Message
s243a

Joined: 02 Sep 2014
Posts: 2208
PostPosted: Wed 06 Mar 2019, 06:19    Post subject:  
I added a function to create the user profiles in the build script.
https://www.pearltrees.com/s243a/add-users-tazpup-file-system/id24252575
https://pastebin.com/8Q3hn8qR

The build script will only create the user profiles if the variable $users is defined. I added a file called "defaults" to put such settings in so that one doesn't have to keep clicking through the dialog windows every-time that someone runs the script.

My configuration file has the following:
Code:

users='tux,root,spot:jwm


The default window manager is slim but I thought I would try creating a user called spot that has the window manager jwm.

In this script the window managers are configured with the code:
Code:

    if [ $WINDOW_MANAGER = "jwm" ]; then   
      usr_home=`su -c "echo $HOME" $USER`
      ( export HOME=$usr_home; fixmenus ) #TODO update fixmenus so that it only updates files for a single user.
    else
      su -c "sh tazbox mkmenu" $USER #
    fi     


one issue I have is that the fixmenus script updates the settings for all users rather than just the home directory that I specify.
Back to top
View user's profile Send private message Visit poster's website 
s243a

Joined: 02 Sep 2014
Posts: 2208
PostPosted: Thu 07 Mar 2019, 06:11    Post subject:  
I noticed that when I copped the therme packages: from WoofCE that I was missing the folder:
Code:

/root/.jwm

I figured out that this folder is created by the post install script:

woof-CE/woof-code/rootfs-packages/ptheme/pinstall.sh

I ran this script in my chroot environment, now I'll try rebuilding the ISO to see what happens Smile

p.s. another issue I had was that the full version of ps is required to avoid errors on shutdown. To fix this issue I copied the following two files from slaco6.9.9
Code:

/bin/ps
/bin/ps-FULL

the first file is a script that selects the full version of ps if available and otherwise links to busybox. I had to copy this file from slaco64.6.9.9.9 because the procps package in the next64 branch was causing segmentation faults.
Back to top
View user's profile Send private message Visit poster's website 
s243a

Joined: 02 Sep 2014
Posts: 2208
PostPosted: Thu 07 Mar 2019, 19:32    Post subject:  
As noted above, I was having trouble with slim so I wrote a script to install the jwm files from woof-CE
https://pastebin.com/xWxfLYez
(see function: add_puppy_jwm_files() )

I also think the version of lxpanel available on the repo is causing segmentation faults. I'm going to replace it with the one from slackware64-14-2-extra repo. Some packages depend on lxpanel such as lxde and lxde-extra. I'll be replacing these also. However, I notice that the slackware repo has more lxde packages so I have to decide which ones I want.

On another note, I was having trouble with ssl certificates so I added the package:

ca-certificates-20181210-noarch-1_slack14.2.txz.tazpkg

and than ran the script:
Code:

/usr/sbin/update-ca-certificates


hopefully this script will address the certificate issues.
Back to top
View user's profile Send private message Visit poster's website 
s243a

Joined: 02 Sep 2014
Posts: 2208
PostPosted: Fri 08 Mar 2019, 05:50    Post subject:  
Some changes in the coming release:
- Replaced 32 bit version of /usr/local/pup_event_pup_event_frontent_d with the 64bit version
(I copied this from my slacko64-6.9.9.9 system.
Code:

# grep -rn -e 'jwm-xdgmenu'
builtin_files/xdg_puppy_jwm:4: jwm-xdgmenu

- replaced 32 bit version of /usr/local/bin/jwm-xdgmenu with 64 bit version.
- symbolically linked roxfiler to rox-filer
Code:

cd /usr/local/bin
ln -s rox-filer roxfiler

made sure that I exported CURRENTWM=jwm in my startx_jwm script.
https://pastebin.com/dYGEnHvC
which calls a slightly modified version of ~/.xinitrc called ~/.xinitrc_puppy
https://pastebin.com/9F176njn
(I think I only commented out one line)
I copied the following folder over form slacko64-6.9.9.9
Code:

/usr/local/lib/X11/pixmaps

I can't figure out what package it is from.
Code:

# grep -nr . -e '/usr/local/lib/X11/pixmaps'
./Iron-69.0.3600.0-amd64.files:40:/usr/local/lib/X11/pixmaps/
./Iron-69.0.3600.0-amd64.files:41:/usr/local/lib/X11/pixmaps/up_down.png
./builtin_files/wcpufreq:5:/usr/local/lib/X11/pixmaps

**this might have not been necessary

on another note, when I try to start jwm I get the following error:
Code:

/bin/sh: xdg_autostart.sh: command not found


I"m not sure where I would find xdg_autostart

One more thing. I made the following symbolic link:
Code:

cd /usr/share/fox-filer
ln -s ROX-Filer rox-filer


I also installed "icewm-xdgmenu"

which gave me two dependencies
"gnome-menus"
"icewm"

I forget the error that made me decide to try this.
Back to top
View user's profile Send private message Visit poster's website 
s243a

Joined: 02 Sep 2014
Posts: 2208
PostPosted: Fri 08 Mar 2019, 16:47    Post subject:  
Some more notes:
Code:

# Copy /sbin/losetup-FULL from slacko64-6.9.9.9
gtkwidget.x:9993: widget class 'GtkProgressBar' has no property named 'through-under-steppers'
#Copy /usr/local/apps/ROX-Filer from slacko64-6.9.9.9
#Copy /etc/xdg/lxsession ~/.config/lxsession #Shouldn't be necessary
#Copy /etc/xdg/lxpanel ~/.config/lxpanel #Shouldn't be necessary
#Copy /etc/xdg/templates ~/Templates #Shouldn't be necessary


Midori isn't working for me but firefox is. I fixed the tsl issue by installing some tsl libraries.

I'm able to get lxpanel working on jwm but not on lxde. That said I fixed all the errors that I saw in the run.log for lxde (not counting locale errors). and the above GTK progress error.

I will try to upload something soon to capture these changes and hopfully correctly incorporate them into the build system.
Back to top
View user's profile Send private message Visit poster's website 
s243a

Joined: 02 Sep 2014
Posts: 2208
PostPosted: Sat 09 Mar 2019, 06:33    Post subject:  
I've given up for now trying to get lxpanel to work and have instead replaced it with tint2:
https://lubuntucast.wordpress.com/2012/12/31/tint2-alternative/
https://docs.google.com/document/d/1Dm72q-cy7yx8xClURHC0IB0stHJmClHNSiX44tsxHUw/edit

Tint2 doesn't provided a nested menu but in theory you can make up for that with openbox menus that show up when you right click on the desktop. There is some info abou this on archwiki:
https://wiki.archlinux.org/index.php/tint2#Openbox
https://wiki.archlinux.org/index.php/Openbox#Menus
I tried updating the menus via obconfig but I couldn't figure out how to update the menus once the XML was changed.
Back to top
View user's profile Send private message Visit poster's website 
s243a

Joined: 02 Sep 2014
Posts: 2208
PostPosted: Wed 13 Mar 2019, 05:26    Post subject:  
I merged the savefile that I was working with the base sfs into a folder with the base sfs that created from a modified version of mistfire;s script (will post later).

The script to merge the files that I used can be found at:
https://pastebin.com/pvSANipi
and the related thread
http://www.murga-linux.com/puppy/viewtopic.php?t=115640

The sfs and save file were merged into a folder.

I was able to mount the folder that contained the merged files using the script:
mount_rootfs
https://pastebin.com/QxgzEqR8

In the chroot environment I could start firefox with:
Code:

/opt/mozilla/firefox/firefox

Once I opened firefox I cleared all the private data.

To open tazpanel on first has to start the httpd server (part of busybox):
Code:

httpd -p 82 u root -c /etc/slitaz/httpd.conf
#See related readme: /var/www/tazpanel/README
tazpanel

From here I can open up the WiFi contifuration file and edit to remove private info. Or perhaps I could just delete it. The path is:
Code:

/etc/network-config/wlan0.conf


For some reason on my merged system I was have some mysterious errors with commands tied to busybox. I solved this problem by replacing busybox with the static version. I downloaded the deb from here
https://packages.debian.org/sid/amd64/busybox-static/download
used busybox to extract the deb, and then copied the file /bin/busybox into my merged system.

Regarding other personal info, one would want to delete the bash command history (~/.bash_history) before building an iso. I'll check to see if mistfire's scripts do this and what personal info is removed in BarryK's remaster scripts.
Last edited by s243a on Wed 13 Mar 2019, 05:47; edited 1 time in total
Back to top
View user's profile Send private message Visit poster's website 
s243a

Joined: 02 Sep 2014
Posts: 2208
PostPosted: Wed 13 Mar 2019, 05:33    Post subject:  
Sine other notes. I'm going to see if I can remove midori because it wasn't working for me.

I'm also having issues with "filed codes" in desktop files. Some related links about this for me to review later:
http://manpages.ubuntu.com/manpages/trusty/man1/gxmessage.1.html
How to launch applications via .desktop files?
Does ROX pinboard support .desktop file specification?
https://developer.gnome.org/shared-mime-info-spec/
Desktop Entry Specification
What do the various % (percent)-parameters in context-menu actions or .desktop files mean?
Back to top
View user's profile Send private message Visit poster's website 
s243a

Joined: 02 Sep 2014
Posts: 2208
PostPosted: Thu 14 Mar 2019, 03:27    Post subject:  
On the first ISO, I'm going to include a bunch of themes and icons, mostly because I don't know what is necessary. Here is what I'll be including:
Code:

hicolor-icon-theme      0.17              misc
openbox-themes          3.6.1             customiz
slim-theme-default      1.3.6             customization
slitaz-themes           312               customization
hicolor-icon-theme      0.17              misc
slitaz-icons-faenza     1.3.1             customization
slitaz-icons-faenza-dark1.3.1             customization
slitaz-tango-icon       1.7               misc
clearlooks-colors       2.22              customization
clearlooks-compact      1.5               customization
gtk-clearlooks          2.20.2            x-window


It will also let me learn how to change the themes and see what they look like. In the tapup build kit there is a function to update the various operating system databases (e.g. icon cache). I don't quite understand this process but I did notice that the function "gtk-update-icon-cache" works well when there is a file in the folder called "index.theme". I modified the build kit to update the icon cache in any folder where such a file exists. I don't know if this is a good idea or not.

Code:

update_icon_caches(){
   trap update_system_database_cleanup EXIT SIGKILL SIGTERM
   mkdir -p "$update_icon_caches_fd_path"
   exec 11<> "$update_icon_caches_fd_path"fd_11
   while IFS=$'\0' read  -r -d $'\0' -u11 theme_index_path_prefixed ; do
     theme_index_path=`dirname "${theme_index_path_prefixed#$curdir/slitaz-rootfs$prefix}"`
     chroot "$curdir/slitaz-rootfs$prefix/" /usr/bin/gtk-update-icon-cache "$theme_index_path"
   done 11< <( find "$curdir/slitaz-rootfs$prefix/" -type f -name 'index.theme' -print0 ) #https://blog.famzah.net/2016/10/20/bash-process-null-terminated-results-piped-from-external-commands/
      exec 11>&-
}

Full Script:
https://pastebin.com/AXF7XNci

Related to themes I added currly braces and a trailing semicolin for functions within the file:
/usr/bin/slim-theme
Code:

get_current() {   awk '/current_theme/ { print $2 }' $CONF ; } #Braces and trailing ";" added by s243a
get_prev()     {   awk '/previous_theme/ { print $2 }' $CONF ; } #Braces and trailing ";" added by s243a
set_current() {   sed -i 's|^current_theme .*$|current_theme '$1'|' $CONF ; } #Braces and trailing ";" added by s243a

Full Code: https://pastebin.com/47Yy2LAA

The themes can be changed from within the various desktops but there are also related settings in:
Code:

/etc/slim.conf



I need to do some searches to see where some of the settings withing /etc/slim.conf" come from. Examples of such searches such are:
Code:

grep -nr . -e '%session'
grep -nr . -e 'current_theme'


The session "field code" (i.e. %session -- see previous post) seem to be the window manager that is being used. In the case of lxde the window manager is associated with a dbus session but I don't think this is generally true. Actually if you look in for instance within the file /etc/slitaz/applications.conf:
Code:

# Window manager.
WINDOW_MANAGER="lxde-session"

(**applications.conf noted in a previous post)
we see the the window manager actually has "session" in it's name.

Also within this file (i.e. /etc/slitaz.conf )is the command that is executed once there is a successful login by slim:

Code:

# This command is executed after a succesful login.
# you can place the %session and %theme variables
# to handle launching of specific commands in .xinitrc
# depending of chosen session and slim theme
##...
login_cmd           exec /bin/sh -l ~/.xinitrc %session


If you look that the ~/.xinitrc script supplied by the package slitaz-configs we see that the window manager (AKA %session) is the first input argument to the script, which is what we would expect based on the comments about the field code "%xsession" given within /etc/slitaz.conf

Code:

# ~/.xinitrc: Executed by Slim/LXDM login manager to startx X session.
# You can use F1 with Slim to change your window manager or configure
# it permanently with your personal applications.conf file.
#
. /etc/slitaz/applications.conf

[ "$1" ] && WINDOW_MANAGER="$1"

EXEC="exec dbus-launch --sh-syntax --exit-with-session"
S="/tmp/X-output" #   http://root:root@tazpanel:82/boot.cgi?log#slim

LOG=2;   case "$LOG" in
   0) X="/dev/null"; echo WM_stdout '>' $X in $HOME/.xinitrc >$S ;W=$X ;;
   1) X=$S ; W=$X ; rm -f $W ;;
   2) X=$S ; W="$HOME/.wm_debug+warnings" ; rm -f $W $X ;;
esac

case "$WINDOW_MANAGER" in
   openbox|lxde*|lxqt*|xfce4|compiz|karmen|dwm|fluxbox*)
      $EXEC ${WINDOW_MANAGER%-session}-session ;;
   razor*)
      $EXEC razor-session ;;
   enlightenment)
      $EXEC enlightenment_start ;;
   *)
      $EXEC $WINDOW_MANAGER ;;
esac   2>>$W >>$X


In normal stat-up the dbus session and Xorg are started up before .xinitrc is called.

See line 439 of /etc/init.d/rcS #First function called by busybox init
Code:

if [ "$(pidof dbus-daemon)" == "" ]; then
  /etc/init.d/dbus start
  sleep 2
fi

**Started earlier (line #404 if hald is running)
Otherwise (someone boots with the screen=text option) there are a few functions one can try to start the window manager. These include
startx
startlxde
~/.xsessionOn the first ISO, I'm going to include a bunch of themes and icons, mostly because I don't know what is necessary. Here is what I'll be including:
Code:

hicolor-icon-theme      0.17              misc
openbox-themes          3.6.1             customiz
slim-theme-default      1.3.6             customization
slitaz-themes           312               customization
hicolor-icon-theme      0.17              misc
slitaz-icons-faenza     1.3.1             customization
slitaz-icons-faenza-dark1.3.1             customization


It will also let me learn how to change the themes and see what they look like. In the tapup build kit there is a function to update the various operating system databases (e.g. icon cache). I don't quite understand this process but I did notice that the function "gtk-update-icon-cache" works well when there is a file in the folder called "index.theme". I modified the build kit to update the icon cache in any folder where such a file exists. I don't know if this is a good idea or not.

Code:

update_icon_caches(){
   trap update_system_database_cleanup EXIT SIGKILL SIGTERM
   mkdir -p "$update_icon_caches_fd_path"
   exec 11<> "$update_icon_caches_fd_path"fd_11
   while IFS=$'\0' read  -r -d $'\0' -u11 theme_index_path_prefixed ; do
     theme_index_path=`dirname "${theme_index_path_prefixed#$curdir/slitaz-rootfs$prefix}"`
     chroot "$curdir/slitaz-rootfs$prefix/" /usr/bin/gtk-update-icon-cache "$theme_index_path"
   done 11< <( find "$curdir/slitaz-rootfs$prefix/" -type f -name 'index.theme' -print0 ) #https://blog.famzah.net/2016/10/20/bash-process-null-terminated-results-piped-from-external-commands/
      exec 11>&-
}

Full Script:
https://pastebin.com/AXF7XNci

Related to themes I added currly braces and a trailing semicolin for functions within the file:
/usr/bin/slim-theme
Code:

get_current() {   awk '/current_theme/ { print $2 }' $CONF ; } #Braces and trailing ";" added by s243a
get_prev()     {   awk '/previous_theme/ { print $2 }' $CONF ; } #Braces and trailing ";" added by s243a
set_current() {   sed -i 's|^current_theme .*$|current_theme '$1'|' $CONF ; } #Braces and trailing ";" added by s243a

Full Code: https://pastebin.com/47Yy2LAA

The themes can be changed from within the various desktops but there are also related settings in:
Code:

/etc/slim.conf



I need to do some searches to see where some of the settings withing /etc/slim.conf" come from. Examples of such searches such are:
Code:

grep -nr . -e '%session'
grep -nr . -e 'current_theme'


The session "field code" (i.e. %session -- see previous post) seem to be the window manager that is being used. In the case of lxde the window manager is associated with a dbus session but I don't think this is generally true. Actually if you look in for instance within the file /etc/slitaz/applications.conf:
Code:

# Window manager.
WINDOW_MANAGER="lxde-session"

(**applications.conf noted in a previous post)
we see the the window manager actually has "session" in it's name.

Also within this file (i.e. /etc/slitaz.conf )is the command that is executed once there is a successful login by slim:

Code:

# This command is executed after a succesful login.
# you can place the %session and %theme variables
# to handle launching of specific commands in .xinitrc
# depending of chosen session and slim theme
##...
login_cmd           exec /bin/sh -l ~/.xinitrc %session


If you look that the ~/.xinitrc script supplied by the package slitaz-configs we see that the window manager (AKA %session) is the first input argument to the script, which is what we would expect based on the comments about the field code "%xsession" given within /etc/slitaz.conf

Code:

# ~/.xinitrc: Executed by Slim/LXDM login manager to startx X session.
# You can use F1 with Slim to change your window manager or configure
# it permanently with your personal applications.conf file.
#
. /etc/slitaz/applications.conf

[ "$1" ] && WINDOW_MANAGER="$1"

EXEC="exec dbus-launch --sh-syntax --exit-with-session"
S="/tmp/X-output" #   http://root:root@tazpanel:82/boot.cgi?log#slim

LOG=2;   case "$LOG" in
   0) X="/dev/null"; echo WM_stdout '>' $X in $HOME/.xinitrc >$S ;W=$X ;;
   1) X=$S ; W=$X ; rm -f $W ;;
   2) X=$S ; W="$HOME/.wm_debug+warnings" ; rm -f $W $X ;;
esac

case "$WINDOW_MANAGER" in
   openbox|lxde*|lxqt*|xfce4|compiz|karmen|dwm|fluxbox*)
      $EXEC ${WINDOW_MANAGER%-session}-session ;;
   razor*)
      $EXEC razor-session ;;
   enlightenment)
      $EXEC enlightenment_start ;;
   *)
      $EXEC $WINDOW_MANAGER ;;
esac   2>>$W >>$X


In normal stat-up the dbus session and Xorg are started up before .xinitrc is called.

See line 439 of /etc/init.d/rcS (First function called by busybox init) for the dbus start-up
Code:

if [ "$(pidof dbus-daemon)" == "" ]; then
  /etc/init.d/dbus start
  sleep 2
fi

**Started earlier (line #404 if hald is running)

but I think the actual dbus session (and also Xorg) is started by slim.

Otherwise (someone boots with the screen=text option) there are a few functions one can try to start the window manager (not in this case I think that consolekit is required). These include
startx
startlxde
~/.xsession

I also created my own varients:
/usr/bin/startx_jwm
Code:

#!/bin/sh
#
# Start X session on SliTaz GNU/Linux.
#

if [ ! -f "$HOME/.xsession" ]; then
  tazx
fi
export CURRENTWM=jwm
Xorg &
#rox &
exec ~/.xinitrc_puppy

which calls a modified version of the .xinitrc script from puppylinux called ~/.xinitrc_puppy (I think I just commented out one line. Also note the XResource mergings currently don't work).

and my other varient is "~/.xsession_lxde"
Code:

# ~/.xsession: Start X window session manually on your system (startx).
#
. /etc/slitaz/applications.conf
Xorg &
ck-launch-session dbus-launch --exit-with-session startlxde

** I think that the function ck-launch-session is from console kit
Last edited by s243a on Thu 14 Mar 2019, 04:23; edited 1 time in total
Back to top
View user's profile Send private message Visit poster's website 
s243a

Joined: 02 Sep 2014
Posts: 2208
PostPosted: Thu 14 Mar 2019, 04:08    Post subject:  
TODO. I need to update the autostart files to start tint2 (or mabye lxpanelx) instead of lxpanel.

A quick search finds it in the following locations:
Code:

# find . -name 'autostart'
./etc/skel/.config/autostart
./etc/xdg/lxsession/LXDE/autostart
./etc/xdg/autostart
./etc/xdg/openbox/autostart
find: `./proc/9701/task/9701/net': Invalid argument
find: `./proc/9701/net': Invalid argument
./home/tux/.config/autostart
./home/spot/.config/autostart


I'll manually update it for now but I need to think about how I want to incorporate it into the build kit.
Back to top
View user's profile Send private message Visit poster's website 
s243a

Joined: 02 Sep 2014
Posts: 2208
PostPosted: Thu 14 Mar 2019, 17:06    Post subject: Re: TazPup64 (pre-alpha)- Working on Xorg & WIndow Manager Issue
Subject description: Updated ISO soon		  
The following info from the first post will be deleted. This post is for record purposes.

s243a wrote:
I thought that it would be good to have a second thread for the 64bit version of TazPup. I used mistfire's build kit to build a 64 bit version of the iso:
https://www.dropbox.com/s/7whjup0cpoi2csg/TazPup64Core-beta23-bionic8.iso?dl=0
**This turned out to produce an iso with a 64bit kernal but 32 bit packages. It worked but wasn't what was desired.

Notes on Trial 1 - 64bit kernal w/ 32bit packages

I combined, slitaz-rolling-core64.iso (located here) w/ bionicpup64-8.0.iso (was located here) using the online build kit. I think that most of what is built is from the slitaz iso and that the puppy iso is only for the kernal and initrd but mistfire can verify.

This thread may be locked if mistfire wants to open her own thread for the 64 bit version of tazpup. I haven't tested the iso per say. Instead I just copied the files within the iso to my hard drive and booted from those files. Everything seems to be working so far. I was able to connect to the internet and install packages.

I'll do some sanity checks like checking the elf types of the libs. I noticed that I don't see a lib64 folder. I wonder why...

Trial Two see link to post below
Continued on Post #6 of this thread:
http://murga-linux.com/puppy/viewtopic.php?p=1019568#1019568

Trial Three - boots into 64bit system but slim doesn't load
Continued on Post #11 of this thread:
http://murga-linux.com/puppy/viewtopic.php?p=1019807#1019807


I have a semi working iso
https://www.dropbox.com/s/sywi28v38esbxsd/TazPup64-PreAlpha-5.iso?dl=0
323.4 MiB (There is a lot that I can trim out)

I tested booting from the files in the iso (not the iso its-self). I booted with boot option screen=text

To start jwm type:
Code:

startx_jwm


To start lxde type:
Code:

root/.xsession_lxde


Withing jwm:
1. The file manager and terminal emulator work in the top panel (but not in the "bottom panel" (or desktop menu) `due to field code issues.
2. Firefox works in the bottom panel

To configure internet in the menu go to:
system -> system -> SliTaz Panel

and then go to the network tab. You can manually type in the information here. The process is a bit awkward. There is an easier too to get it to work that I haven't tested yet.

So anyway, it's a start. I still recommend that people wait before trying it though.
Back to top
View user's profile Send private message Visit poster's website 
s243a

Joined: 02 Sep 2014
Posts: 2208
PostPosted: Sun 17 Mar 2019, 17:04    Post subject: Re: TazPup64 (pre-alpha6) - Working but Testers not needed yet
Subject description: Still have issues with XDG field codes		  
From the current 1st post (in the thread):
s243a wrote:
New ISO available (17 Mar 2019 :
TazPup64-PreAlpha-6.iso (324.5MB)

The ISO works for me and my computer is running much faster with this ISO than with Slack64-6.9.9.9. However, it is still very raw so I will likely be aware of most reported issues.

However, there are two things that I need help with (although I'll try to figure them out on my own). The big one is fixing the XDG field code issue. My work around was to modify the desktop file of pcmanfm and change "%U" to "~" in the execute command. pcmanfm isn't really needed at this point though because I am working with jwm and rox

However, I'm also trying to get lxde to work since I think that is what mistfire's TazPup uses. When the system is more mature, I will create one or more slimmer versions that only have one of these two window manager installed.

The other issue, which I need help with, is that for some reason the menus are double nested (e.g. utilities->utilities. I would like to put the most important applications in the first level of nesting and the other applications nested deeper in the menus. I think I have to dig into the menu templates to figure this out. Once I get this sorted out I can use PupMenu-6.2
(installed) to move applications around within the menu.



Changes since last ISO:
Quote:

In /var/www/tazpanel/network.cgi

Added missing space before second right bracket in lines 126 and 134

One of the symlinks that I mentioned earlier didn't seem to take:

Edited build script to make sure they are included.
Lines 34 to 36 of add_puppy_jwm_files.sh:
Code:

   cd $curdir/slitaz-rootfs$prefix/usr/share/rox-filer
    ln -s rox-filer ROX-Filer
   
   cd $curdir/slitaz-rootfs$prefix/usr/bin
    ln -s rox-filer rox-filer roxfiler   

https://pastebin.com/xWxfLYez

Installed gtkdialog


For some reason /root/.icons/ROX
points to: /usr/share/rox-filer/images

Fixed symlink to point to
"/usr/local/apps/ROX-Fler/ROX"
(made similar changes to other users)

added darry's uextract package:
# http://www.murga-linux.com/puppy/viewtopic.php?p=992447#992447

- Tried installing the rox_config package from woofCE. I think that it changed the drag and drop behavior. Not sure what else it might have done.
(I noticed that this messes up puppypin so it must be done before any changes to puppypin)

Fix desktop icons that aren't working by modifying:
/root/Choices/ROX-Filer/PuppyPin (# denotes deletions)
Code:

#  <icon x="32" y="416" label="connect">/usr/local/apps/Connect</icon>
<icon x="32" y="416" label="connect">/usr/local/bin/defaultconnect</icon>
#  <icon x="288" y="32" label="setup">/usr/sbin/wizardwizard</icon>

(Only changes shown. Need to update icon for default connect and install)

/usr/local/bin/defaultconnect
Code:

#!/bin/sh
exec tazpanel network


/usr/local/bin/defaultspreadsheet
Code:

#!/bin/sh
#exec puppyapps defaultspreadsheet "$@"
exec browser http://localhost/wiki/index.sh\?page=Calc


/usr/local/bin/defaultbrowser
Code:

#!/bin/sh
#exec midori "$@" #midori was removed because it didn't work
exec /opt/mozilla/firefox/firefox "$@"


Code:

#!/bin/sh
#exec puppyapps defaultchat "$@"
exec sakura -e "tazirc --ask"


More cleanup still needed for desktop icons and need to base this on some kind of logic that is based on which applications are installed.


Copied the following command "/usr/bin/disktype" from slacko646.9.9.9
Gave user and group executable premissions to /sbin/losetup-222

installed: gxmessage and PupMenu-6.2

Copyied /root/Choices to other users

FIxed premissions on loosetup. Fixed umount and umount-FULL based on SLACO64.6.9.9.9

[/quoTODO
- Look at the /root/.config/autostart folder of an existing puppy and see if we want to autostart any of these items.

- Look at an existing TazPup to see what deamons and scripts that we want to start on boot.


Unfortunately all these changes haven't made it into the buildkit and I'm making big changes to the build-kit so it isn't ready for anew release yet.
Last edited by s243a on Mon 18 Mar 2019, 01:03; edited 1 time in total
Back to top
View user's profile Send private message Visit poster's website 
s243a

Joined: 02 Sep 2014
Posts: 2208
PostPosted: Sun 17 Mar 2019, 17:47    Post subject:  
As a side-note, the build script isn't yet up-to-date but there is a shortcut. YOu can download (and extract) the pre-ISO "root file system", mount it with the script, "mount_rootfs64"

which will mount the root-fs in a choroot environment. You will have network access and can even run gui applications. Type exit in the terminal once you are done making changes.

Make sure the following folders are unmounted:
Code:

$curdir/slitaz-rootfs/64/sys
$curdir/slitaz-rootfs/64/dev
$curdir/slitaz-rootfs/64/proc


If these folders don't properly unmount when exiting the script then press "cntrl-alt-backaspace" to exit the window manager. xwin (in puppylinux) to start the window manager and then right click on these folders and select "unmount"

Once these folders are unmounted than then build then a new ISO can be built with the script "make_ISO_Fm_slitaz-rootfs".

both scripts mentioned in this post are available in the buildkit.
Back to top
View user's profile Send private message Visit poster's website 
s243a

Joined: 02 Sep 2014
Posts: 2208
PostPosted: Sun 17 Mar 2019, 18:20    Post subject:  
Firefox sometimes crashes when dragging the mouse with the left mouse buttin held down. Consequently, I decided to try the iron browser. Unfortunately in the next64 brach, there seems to be a 32bit version in the repo rather than a 64 bit version.

The next64 branch isn't set up well for a distro to support both 32 and 64bit because the lib files aren't segregated into separate directories.What I might be able to do though is to install any 32 libs that I want into a separate root path and then append to the search path the locations of the 32 bit libs.

That said, if I want Iron in my opinion it would make more sense to find a 64 bit binary somewhere else or alternatively try compiling it.
Back to top
View user's profile Send private message Visit poster's website 
s243a

Joined: 02 Sep 2014
Posts: 2208
PostPosted: Fri 22 Mar 2019, 21:48    Post subject:  
Sound is the next thing that I decide to tackle in this release. At first I wasn't sure if sound is working so I installed VLC from slackware64-6.9.9.9 binaries.

TazPup64-PreAlpha-7.iso

I played an mp3 to prove that sound worked. Next I wanted to try get sound working on youtube. Installing the xine plugin solved this problem but HTML5 videos don't play. I've been booting with the screen=text option and starting x with a script I created called:
Code:

/usr/bin/start_jwm


lxde is also installed but so far I"m having better luck with jwm. To start lxde type:
Code:

/root/.xsession


For firefox to play sound you might have to start it then restart it for updates to take effect. I tried doing this in the chroot environment before creating the iso. This bloated the ISO and didn't solve the problem of having to update firefox when using a fresh ISO. I'm thinking that it's probably best to put the browser and related supporting libraries (e.g. xine-plugin into an sfs). Note that at this point I'm still booting from the files in the ISO rather than trying to boot from the ISO its-self.


One downside of this release of the previous is that it's booting much slower.
Back to top
View user's profile Send private message Visit poster's website 
Display posts from previous:   Sort by:   
Page 2 of 7 [92 Posts]   Goto page: Previous 1, 2, 3, 4, 5, 6, 7 Next
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » Advanced Topics » Puppy Derivatives
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.1432s ][ Queries: 12 (0.0112s) ][ GZIP on ]