Porteus module activation status

For discussions about programming and projects not necessarily associated with Porteus.
jssouza
DEV Team
DEV Team
Posts: 227
Joined: 09 Jul 2015, 14:17
Distribution: Porteus x86 arm
Location: Liechtenstein

Re: Porteus module activation status

Post#31 by jssouza » 07 Oct 2016, 07:13

Ed_P wrote:Sequence is still extramods, then porteus/base mods, then changes.
Yes I know, because I havent looked into yet :) . I would have to create your exact setup, so it would take some time to recreate your scenario. I have checked porteus extracted to a drive and porteus executed from a cd and both have the base modules loaded first and then the extramods.

I see you use the from=/path/to/iso cheatcode and your extramods are in some partition. What about the kernel and the initrd? Are they pre-extracted out of the iso for the bootloader?

jssouza
DEV Team
DEV Team
Posts: 227
Joined: 09 Jul 2015, 14:17
Distribution: Porteus x86 arm
Location: Liechtenstein

Re: Porteus module activation status

Post#32 by jssouza » 07 Oct 2016, 10:07

Hi Ed_P,

I recreated your setup partially - booted to cinnamon 3.2rc5 iso using the from=cheatcode and also used extramod cheatcode. I was able to recreate your issue.

The reason for the issue is because of what you mentioned earlier in this same thread in a post yesterday:
Ed_P wrote:Interesting that /var/log/porteus-livedbg shows the Booting device: as /mnt/isoloop when it's true path for me is /mnt/live/mnt/isoloop.

Code: Select all

root@porteus:/home/guest# ls /mnt/isoloop
/bin/ls: cannot access '/mnt/isoloop': No such file or directory
root@porteus:/home/guest# ls /mnt/isoloop/
/bin/ls: cannot access '/mnt/isoloop/': No such file or directory
root@porteus:/home/guest# ls /mnt/isoloop/*
/bin/ls: cannot access '/mnt/isoloop/*': No such file or directory
root@porteus:/home/guest# ls /mnt/live/mnt/isoloop/
EFI/  USB_INSTALLATION.txt  boot/  porteus/
root@porteus:/home/guest# 
So, because the path to isoloop is wrong, the problem occurred. I have fixed it in the script below with a workaround. (It is a one line change - just search for #isoloop fix in the script).

Code: Select all

#! /bin/bash

if [ "$UID" -ne 0 ]; then
  if [ "$DISPLAY" ]; then
    ktsuss $0
  else
    echo "Enter root password" 
    su -c $0
  fi
  exit
fi

export MODULE_LOAD_DIR="/mnt/live/memory/images"
export TMPFILE="/tmp/${$}_port_modules"
export LOADEDENTRIES="grep -c gtk-yes $TMPFILE | tr -d '\n'"
export NUMENTRIES="wc -l $TMPFILE | cut -f 1 -d ' '"
export PORTROOTDIR=`grep -A1 "Porteus data found in" /var/log/porteus-livedbg | tail -n1`

trap sigint_handler INT
sigint_handler()
{
    rm -f "$TMPFILE"
}

function value() { egrep -o " $1=[^ ]+" /proc/cmdline | cut -d= -f2; }

function search() 
{
 local FOUND=""
 for x in `ls /mnt | tac`; do
  if [ -e /mnt/$x/$1 -a $(grep -c "/mnt/$x/$1" /var/log/porteus-livedbg) -ne 0 ]; then
   FOUND="$x"
   break
  fi
 done
 echo $FOUND
}

export EXTRAMODS=`value extramod | sed 's/;/ /g'`

function load_remaining_modules
{
  local PORTMODULES="$(ls $MODULE_LOAD_DIR | sort)"
  for PORTMODULE in $PORTMODULES
  do
     local MODNAME="$(basename -a $PORTMODULE)"
     if ! grep -q "$MODNAME" "$TMPFILE"; then
       local MODDIR="$(losetup  -a | grep $MODNAME | cut -d \( -f2 | cut -d \) -f1)"
	   echo "gtk-yes|${MODNAME}|${MODDIR}" >> "$TMPFILE"
     fi
  done   
}

function load_modules
{
  echo $PORTROOTDIR | egrep -q 'isoloop' && PORTROOTDIR="/mnt/live${PORTROOTDIR}" #isoloop fix
  local PORTMODULES="$(find $PORTROOTDIR -name "*.xzm" | sort)"
  for PORTMODULE in $PORTMODULES
  do
     local MODNAME="$(basename -a $PORTMODULE)"
     local MODDIR="$(dirname $PORTMODULE)"
     local OUT="${MODNAME}|${MODDIR}"
  
     if [ -e "${MODULE_LOAD_DIR}/${MODNAME}" ]; then
       echo "gtk-yes|${OUT}" >> "$TMPFILE"
     else 
       echo "gtk-no|${OUT}" >> "$TMPFILE"
     fi
  done

  if [ "$EXTRAMODS" ]; then
   for EXTRAMOD in $EXTRAMODS; do
    echo $EXTRAMOD | egrep -q '^UUID|^LABEL' && EXTRAMOD="$(echo $EXTRAMOD | cut -d \/ -f2-)"
    echo $EXTRAMOD | egrep -q '^/mnt/' && EXTRAMOD="$(echo $EXTRAMOD | cut -d \/ -f4-)"
	RET=$(search $EXTRAMOD)
	if [ $RET ]; then
     PORTMODULES="$(find /mnt/${RET}/${EXTRAMOD} -name "*.xzm" | sort)"
    else
     PORTMODULES="$(find ${EXTRAMOD} -name "*.xzm" | sort)"
    fi     
	for PORTMODULE in $PORTMODULES
	do
	  local MODNAME="$(basename -a $PORTMODULE)"
	  local MODDIR="$(dirname $PORTMODULE)"
	  local OUT="${MODNAME}|${MODDIR}"
		  
	  if [ -e "${MODULE_LOAD_DIR}/${MODNAME}" ]; then
	   echo "gtk-yes|${OUT}" >> "$TMPFILE"
	  else 
	   echo "gtk-no|${OUT}" >> "$TMPFILE"
	  fi
	done
   done
  fi
  load_remaining_modules 
}

function activate_module
{
  if [ "$1" = "" ]; then return; fi

  local MODDIR="$(grep $1 $TMPFILE | cut -f 3 -d "|")"
  local MODULE="${MODDIR}/${1}"

  if [ -e "${MODULE_LOAD_DIR}/${1}" ]; then
   deactivate "$MODULE"
  else 
   activate "$MODULE"
  fi

  rm -f "$TMPFILE"
  load_modules
}

export -f load_modules
export -f load_remaining_modules
export -f activate_module
export -f value
export -f search

load_modules

export MODULES_MAIN='
<window window_position="1" title="Porteus Modules" default-height="550" default-width="500" icon-name="cdr" resizable="true" decorated="true">
<vbox>
 <hbox>
  <text>
   <label>"Modules Activated: "</label>
  </text>
  <text>
   <variable>ENTRIES</variable>
   <input>'$LOADEDENTRIES'</input>
  </text>
 </hbox>
 <tree homogeneous="true" selection-mode="1" file-monitor="true">
  <variable>ENTRY</variable>
  <label>"Module Name                        |Containing Directory               "</label> 
  <input file icon_column="0">'$TMPFILE'</input>
  <action signal="row-activated">"activate_module $ENTRY"</action>
  <action signal="file-changed" type="refresh">ENTRY</action>
  <action signal="file-changed" type="refresh">ENTRIES</action>
 </tree> 
 <hseparator default-width="300"></hseparator> 
 <hbox> 
  <button space-fill="true">
   <label>Exit</label> 
   <action>exit:0</action> 
  </button>  
 </hbox> 
</vbox> 
</window>
'  

gtkdialog --program=MODULES_MAIN -c
rm -f $TMPFILE
I will also report the wrong path issue, since it also occurs on 3.2rc5. Now, if and when brokenman fixes this, this script would break (because of the workaround). So I would then suggest that you keep this version of your script for your 3.0.1 and use the previous version for 3.2 when it gets fixed there. Or, this same script on both versions.

User avatar
Ed_P
Contributor
Contributor
Posts: 3199
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 3.2.2 64-bit ISO
Location: Western NY, USA

Re: Porteus module activation status

Post#33 by Ed_P » 07 Oct 2016, 16:07

Thanks jssouza. :friends:

Wouldn't this work:

Code: Select all

if [ "$BOOTDEV" == "/mnt/isoloop" ]; then
   BOOTDEV="/mnt/image/$BOOTDEV"
fi
BTW The system modules are still showing at the bottom.
Ed

jssouza
DEV Team
DEV Team
Posts: 227
Joined: 09 Jul 2015, 14:17
Distribution: Porteus x86 arm
Location: Liechtenstein

Re: Porteus module activation status

Post#34 by jssouza » 07 Oct 2016, 17:26

Ed_P wrote:BTW The system modules are still showing at the bottom.
Hi Ed_P,

Coming to you now live from Porteus RazorQT 3.0.1! I downloaded this iso from the archives of dl.porteus.org. I executed the script and saw that the base modules come first and then the extramods.
http://imgur.com/a/jE9L1

This is my configuration

Code: Select all

guest@porteus:~$ cat /proc/cmdline 
quiet BOOT_IMAGE=/porteus301/vmlinuz from=/porteus301/razor.iso extramod=/porteus301/extramodules
Could you upload me a snapshot of your output?

Thanks!

User avatar
Ed_P
Contributor
Contributor
Posts: 3199
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 3.2.2 64-bit ISO
Location: Western NY, USA

Re: Porteus module activation status

Post#35 by Ed_P » 07 Oct 2016, 17:34

jssouza wrote:Could you upload me a snapshot of your output?

Thanks!
https://drive.google.com/file/d/0B1Uj3O ... sp=sharing

Code: Select all

guest@porteus:~$ cat /proc/cmdline
quiet from=/ISOs/Porteus-RazorQT-v3.0.1-x86_64-nu.iso changes=EXIT:/porteus3.0/changes/porteussave.dat extramod=/porteus3.0/Modules volume=40 reboot=cold ramsize=80%
guest@porteus:~$ 
grub4dos (partial)

Code: Select all

set ISO31=Porteus-LXQT-v3.1-x86_64-nu.iso
#set ISO31=Porteus-LXQT-v3.1-x86_64.iso
set ISO30i=Porteus-RazorQT-v3.0.1-i486-nu.iso
set ISO30=Porteus-RazorQT-v3.0.1-x86_64-nu.iso

# menu entries
 

title Porteus 3.0.1 changes=EXIT  \n213MB\n %ISO30% 
find --set-root                       /ISOs/%ISO30%
map --heads=0 --sectors-per-track=0   /ISOs/%ISO30% (0xff) 
map --hook
root (0xff)
kernel /boot/syslinux/vmlinuz    from=/ISOs/%ISO30% changes=EXIT:/porteus3.0/changes/porteussave.dat extramod=/porteus3.0/Modules volume=40 reboot=cold ramsize=80%
#initrd (hd0,4)/porteus3.0/testing/initrdx.xz
initrd /boot/syslinux/initrd.xz
Ed

jssouza
DEV Team
DEV Team
Posts: 227
Joined: 09 Jul 2015, 14:17
Distribution: Porteus x86 arm
Location: Liechtenstein

Re: Porteus module activation status

Post#36 by jssouza » 07 Oct 2016, 18:14

Thank you for the logs Ed. They look fine.

I enabled some debug messages on the script. Could you run the following script and provide me the output from the terminal?

Code: Select all

  #! /bin/bash

    if [ "$UID" -ne 0 ]; then
      if [ "$DISPLAY" ]; then
        ktsuss $0
      else
        echo "Enter root password"
        su -c $0
      fi
      exit
    fi

    export MODULE_LOAD_DIR="/mnt/live/memory/images"
    export TMPFILE="/tmp/${$}_port_modules"
    export LOADEDENTRIES="grep -c gtk-yes $TMPFILE | tr -d '\n'"
    export NUMENTRIES="wc -l $TMPFILE | cut -f 1 -d ' '"
    export PORTROOTDIR=`grep -A1 "Porteus data found in" /var/log/porteus-livedbg | tail -n1`

    trap sigint_handler INT
    sigint_handler()
    {
        rm -f "$TMPFILE"
    }

    function value() { egrep -o " $1=[^ ]+" /proc/cmdline | cut -d= -f2; }

    function search()
    {
     local FOUND=""
     for x in `ls /mnt | tac`; do
      if [ -e /mnt/$x/$1 -a $(grep -c "/mnt/$x/$1" /var/log/porteus-livedbg) -ne 0 ]; then
       FOUND="$x"
       break
      fi
     done
     echo $FOUND
    }

    export EXTRAMODS=`value extramod | sed 's/;/ /g'`

    function load_remaining_modules
    {
      local PORTMODULES="$(ls $MODULE_LOAD_DIR | sort)"
      echo "Activated Modules: $PORTMODULES"
      for PORTMODULE in $PORTMODULES
      do
         local MODNAME="$(basename -a $PORTMODULE)"
         if ! grep -q "$MODNAME" "$TMPFILE"; then
           local MODDIR="$(losetup  -a | grep $MODNAME | cut -d \( -f2 | cut -d \) -f1)"
          echo "gtk-yes|${MODNAME}|${MODDIR}" >> "$TMPFILE"
         fi
      done   
    }

    function load_modules
    {
      echo $PORTROOTDIR | egrep -q 'isoloop' && PORTROOTDIR="/mnt/live${PORTROOTDIR}" #isoloop fix
      local PORTMODULES="$(find $PORTROOTDIR -name "*.xzm" | sort)"
      echo "Porteus Root Directory: $PORTROOTDIR"
      echo "Base Modules: $PORTMODULES"
      for PORTMODULE in $PORTMODULES
      do
         local MODNAME="$(basename -a $PORTMODULE)"
         local MODDIR="$(dirname $PORTMODULE)"
         local OUT="${MODNAME}|${MODDIR}"
     
         if [ -e "${MODULE_LOAD_DIR}/${MODNAME}" ]; then
           echo "gtk-yes|${OUT}" >> "$TMPFILE"
         else
           echo "gtk-no|${OUT}" >> "$TMPFILE"
         fi
      done

      if [ "$EXTRAMODS" ]; then
       for EXTRAMOD in $EXTRAMODS; do
        echo $EXTRAMOD | egrep -q '^UUID|^LABEL' && EXTRAMOD="$(echo $EXTRAMOD | cut -d \/ -f2-)"
        echo $EXTRAMOD | egrep -q '^/mnt/' && EXTRAMOD="$(echo $EXTRAMOD | cut -d \/ -f4-)"
       RET=$(search $EXTRAMOD)
       if [ $RET ]; then
         PORTMODULES="$(find /mnt/${RET}/${EXTRAMOD} -name "*.xzm" | sort)"
        else
         PORTMODULES="$(find ${EXTRAMOD} -name "*.xzm" | sort)"
        fi 
       echo "Extra Modules: $PORTMODULES"    
       for PORTMODULE in $PORTMODULES
       do
         local MODNAME="$(basename -a $PORTMODULE)"
         local MODDIR="$(dirname $PORTMODULE)"
         local OUT="${MODNAME}|${MODDIR}"
           
         if [ -e "${MODULE_LOAD_DIR}/${MODNAME}" ]; then
          echo "gtk-yes|${OUT}" >> "$TMPFILE"
         else
          echo "gtk-no|${OUT}" >> "$TMPFILE"
         fi
       done
       done
      fi
      load_remaining_modules
    }

    function activate_module
    {
      if [ "$1" = "" ]; then return; fi

      local MODDIR="$(grep $1 $TMPFILE | cut -f 3 -d "|")"
      local MODULE="${MODDIR}/${1}"

      if [ -e "${MODULE_LOAD_DIR}/${1}" ]; then
       deactivate "$MODULE"
      else
       activate "$MODULE"
      fi

      rm -f "$TMPFILE"
      load_modules
    }

    export -f load_modules
    export -f load_remaining_modules
    export -f activate_module
    export -f value
    export -f search

    load_modules

    export MODULES_MAIN='
    <window window_position="1" title="Porteus Modules" default-height="550" default-width="500" icon-name="cdr" resizable="true" decorated="true">
    <vbox>
     <hbox>
      <text>
       <label>"Modules Activated: "</label>
      </text>
      <text>
       <variable>ENTRIES</variable>
       <input>'$LOADEDENTRIES'</input>
      </text>
     </hbox>
     <tree homogeneous="true" selection-mode="1" file-monitor="true">
      <variable>ENTRY</variable>
      <label>"Module Name                        |Containing Directory               "</label>
      <input file icon_column="0">'$TMPFILE'</input>
      <action signal="row-activated">"activate_module $ENTRY"</action>
      <action signal="file-changed" type="refresh">ENTRY</action>
      <action signal="file-changed" type="refresh">ENTRIES</action>
     </tree>
     <hseparator default-width="300"></hseparator>
     <hbox>
      <button space-fill="true">
       <label>Exit</label>
       <action>exit:0</action>
      </button> 
     </hbox>
    </vbox>
    </window>
    ' 

    gtkdialog --program=MODULES_MAIN -c
    rm -f $TMPFILE
Thanks!

User avatar
Ed_P
Contributor
Contributor
Posts: 3199
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 3.2.2 64-bit ISO
Location: Western NY, USA

Re: Porteus module activation status

Post#37 by Ed_P » 07 Oct 2016, 19:32

Code: Select all

guest@porteus:~$ sh modulesx.sh
sudo: modulesx.sh: command not found
guest@porteus:~$ sh modulesx.sh
sudo: modulesx.sh: command not found
guest@porteus:~$ sh modulesx.sh
+ '[' 1000 -ne 0 ']'
+ '[' :0.0 ']'
+ ktsuss modulesx.sh
sudo: modulesx.sh: command not found
+ exit
guest@porteus:~$ chmod +x modulesx.sh
guest@porteus:~$ sh modulesx.sh
Porteus Root Directory: /mnt/live/mnt/isoloop/porteus
Base Modules: 
Extra Modules: /mnt/sda5//porteus3.0/Modules/001-core_alldesktops-150124.xzm
/mnt/sda5//porteus3.0/Modules/002-xorg_alldesktops-150119.xzm
/mnt/sda5//porteus3.0/Modules/002-xorg_alldesktops-150126.xzm
/mnt/sda5//porteus3.0/Modules/04-firefox.xzm
/mnt/sda5//porteus3.0/Modules/07-printing.xzm
/mnt/sda5//porteus3.0/Modules/OOoLight1.1_120606_LinuxX86-64.xzm
/mnt/sda5//porteus3.0/Modules/Wine-1.7.26-x64-GeckoMono-1.xzm
/mnt/sda5//porteus3.0/Modules/bash-4.2.048-x86_64-2_slack14.1.xzm
/mnt/sda5//porteus3.0/Modules/dosbox-0.74-x86_64-1gv.xzm
/mnt/sda5//porteus3.0/Modules/flashplayer-plugin-11.2.202.635-x86_64-1alien.xzm
/mnt/sda5//porteus3.0/Modules/gweled-0.9.1-4.38.x86_64-1phhpro.xzm
/mnt/sda5//porteus3.0/Modules/java-builder-1.1_noarch.xzm
/mnt/sda5//porteus3.0/Modules/jre-8u101-x86_64-1.xzm
/mnt/sda5//porteus3.0/Modules/keepassx-0.4.3-x86_64-2_slack.xzm
/mnt/sda5//porteus3.0/Modules/kpat-4.10.5-x86_64-bundle.xzm
/mnt/sda5//porteus3.0/Modules/mozilla-firefox-45.1.1esr-x86_64-1gv.xzm
/mnt/sda5//porteus3.0/Modules/openssl-1.0.1s-x86_64-1_slack14.1.xzm
/mnt/sda5//porteus3.0/Modules/syslinux-4.06-x86_64-1.xzm
/mnt/sda5//porteus3.0/Modules/testdisk-6.14-x86_64-2sl.xzm
/mnt/sda5//porteus3.0/Modules/tree-1.6.0-x86_64-1.xzm
/mnt/sda5//porteus3.0/Modules/xscreensaver-5.29-x86_64-1_slack14.1.xzm
/mnt/sda5//porteus3.0/Modules/z-MyWines.xzm
Activated Modules: 000-kernel.xzm
001-core.xzm
001-core_alldesktops-150124.xzm
002-xorg.xzm
002-xorg_alldesktops-150119.xzm
002-xorg_alldesktops-150126.xzm
003-razor.xzm
04-firefox.xzm
07-printing.xzm
OOoLight1.1_120606_LinuxX86-64.xzm
Wine-1.7.26-x64-GeckoMono-1.xzm
bash-4.2.048-x86_64-2_slack14.1.xzm
changes
dosbox-0.74-x86_64-1gv.xzm
flashplayer-plugin-11.2.202.635-x86_64-1alien.xzm
gweled-0.9.1-4.38.x86_64-1phhpro.xzm
java-builder-1.1_noarch.xzm
jre-8u101-x86_64-1.xzm
keepassx-0.4.3-x86_64-2_slack.xzm
kpat-4.10.5-x86_64-bundle.xzm
mozilla-firefox-45.1.1esr-x86_64-1gv.xzm
openssl-1.0.1s-x86_64-1_slack14.1.xzm
syslinux-4.06-x86_64-1.xzm
testdisk-6.14-x86_64-2sl.xzm
tree-1.6.0-x86_64-1.xzm
xscreensaver-5.29-x86_64-1_slack14.1.xzm
z-MyWines.xzm
I'm impressed with your persistence. :)
Ed

jssouza
DEV Team
DEV Team
Posts: 227
Joined: 09 Jul 2015, 14:17
Distribution: Porteus x86 arm
Location: Liechtenstein

Re: Porteus module activation status

Post#38 by jssouza » 07 Oct 2016, 19:55

:) It's very intrigiung, as to why it works here and does not at your side.

Could you give me the output of losetup -a please? Also, ls -l /mnt/live/mnt/isoloop/porteus

EDIT: I did find a difference in your screenshot. While the containing directory field should show only directory names, your screenshot shows the xzm module name also.
eg: /mnt/live/mnt/isoloop/porteus/base/000-kernel.xzm

User avatar
Ed_P
Contributor
Contributor
Posts: 3199
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 3.2.2 64-bit ISO
Location: Western NY, USA

Re: Porteus module activation status

Post#39 by Ed_P » 07 Oct 2016, 23:04

3.0.1

Code: Select all

guest@porteus:~$ losetup -a
/dev/loop0: [2053]:19967 (/mnt/sda5/ISOs/Porteus-RazorQT-v3.0.1-x86_64-nu.iso)
/dev/loop1: [1792]:1668 (/mnt/live/mnt/isoloop/porteus/base/000-kernel.xzm)
/dev/loop2: [1792]:1671 (/mnt/live/mnt/isoloop/porteus/base/001-core.xzm)
/dev/loop3: [1792]:1674 (/mnt/live/mnt/isoloop/porteus/base/002-xorg.xzm)
/dev/loop4: [1792]:1677 (/mnt/live/mnt/isoloop/porteus/base/003-razor.xzm)
/dev/loop5: [2053]:77 (/mnt/sda5/porteus3.0/Modules/001-core_alldesktops-150124.xzm)
/dev/loop6: [2053]:202 (/mnt/sda5/porteus3.0/Modules/002-xorg_alldesktops-150119.xzm)
/dev/loop7: [2053]:12124 (/mnt/sda5/porteus3.0/Modules/002-xorg_alldesktops-150126.xzm)
/dev/loop8: [2053]:22142 (/mnt/sda5/porteus3.0/Modules/04-firefox.xzm)
/dev/loop9: [2053]:22075 (/mnt/sda5/porteus3.0/Modules/07-printing.xzm)
/dev/loop10: [2053]:22108 (/mnt/sda5/porteus3.0/Modules/OOoLight1.1_120606_LinuxX86-64.xzm)
/dev/loop11: [2053]:22109 (/mnt/sda5/porteus3.0/Modules/Wine-1.7.26-x64-GeckoMono-1.xzm)
/dev/loop12: [2053]:12165 (/mnt/sda5/porteus3.0/Modules/bash-4.2.048-x86_64-2_slack14.1.xzm)
/dev/loop13: [2053]:12166 (/mnt/sda5/porteus3.0/Modules/dosbox-0.74-x86_64-1gv.xzm)
/dev/loop14: [2053]:12207 (/mnt/sda5/porteus3.0/Modules/flashplayer-plugin-11.2.202.635-x86_64-1alien.xzm)
/dev/loop15: [2053]:21561 (/mnt/sda5/porteus3.0/Modules/gweled-0.9.1-4.38.x86_64-1phhpro.xzm)
/dev/loop16: [2053]:21562 (/mnt/sda5/porteus3.0/Modules/java-builder-1.1_noarch.xzm)
/dev/loop17: [2053]:22512 (/mnt/sda5/porteus3.0/Modules/jre-8u101-x86_64-1.xzm)
/dev/loop18: [2053]:21565 (/mnt/sda5/porteus3.0/Modules/keepassx-0.4.3-x86_64-2_slack.xzm)
/dev/loop19: [2053]:21567 (/mnt/sda5/porteus3.0/Modules/kpat-4.10.5-x86_64-bundle.xzm)
/dev/loop20: [2053]:22019 (/mnt/sda5/porteus3.0/Modules/mozilla-firefox-45.1.1esr-x86_64-1gv.xzm)
/dev/loop21: [2053]:209 (/mnt/sda5/porteus3.0/Modules/openssl-1.0.1s-x86_64-1_slack14.1.xzm)
/dev/loop22: [2053]:22114 (/mnt/sda5/porteus3.0/Modules/syslinux-4.06-x86_64-1.xzm)
/dev/loop23: [2053]:21569 (/mnt/sda5/porteus3.0/Modules/testdisk-6.14-x86_64-2sl.xzm)
/dev/loop24: [2053]:21570 (/mnt/sda5/porteus3.0/Modules/tree-1.6.0-x86_64-1.xzm)
/dev/loop25: [2053]:22072 (/mnt/sda5/porteus3.0/Modules/xscreensaver-5.29-x86_64-1_slack14.1.xzm)
/dev/loop26: [2053]:22105 (/mnt/sda5/porteus3.0/Modules/z-MyWines.xzm)
/dev/loop27: [2053]:22139 (/mnt/sda5/porteus3.0/changes/porteussave.dat)
guest@porteus:~$ ls -l /mnt/live/mnt/isoloop/porteus
total 10
drwxr-xr-x 2 root root 2048 Jan 30  2015 base/
-rwxr-xr-x 1 root root 1015 Jan 30  2015 make_iso.sh*
drwxr-xr-x 2 root root 2048 Jan 30  2015 modules/
drwxr-xr-x 2 root root 2048 Jan 30  2015 optional/
-rw-r--r-- 1 root root  437 Jan 30  2015 porteus-v3.0.1-x86_64.sgn
drwxr-xr-x 2 root root 2048 Jan 30  2015 rootcopy/
guest@porteus:~$
3.2rc5

Code: Select all

guest@porteus:~$ losetup -a
bash: losetup: command not found
guest@porteus:~$ /sbin/losetup -a
/dev/loop0: []: (/mnt/sda5/ISOs/Porteus-CINNAMON-v3.2rc5-x86_64.iso)
/dev/loop1: []: (/mnt/live/mnt/isoloop/porteus/base/000-kernel.xzm)
/dev/loop2: []: (/mnt/live/mnt/isoloop/porteus/base/001-core.xzm)
/dev/loop3: []: (/mnt/live/mnt/isoloop/porteus/base/002-xorg.xzm)
/dev/loop4: []: (/mnt/live/mnt/isoloop/porteus/base/003-cinnamon.xzm)
/dev/loop5: []: (/mnt/sda5/porteus3.2/Modules/009-caches.xzm)
/dev/loop6: []: (/mnt/sda5/porteus3.2/Modules/07-printing.xzm)
/dev/loop7: []: (/mnt/sda5/porteus3.2/Modules/firefox-48.0b6-x86_64-1.xzm)
/dev/loop8: []: (/mnt/sda5/porteus3.2/Modules/nemo-actions-fix-by-blaze.xzm)
/dev/loop9: []: (/mnt/sda5/porteus3.2/Modules/pepperflash-23.0.0.162-x86_64-1.xzm)
/dev/loop10: []: (/mnt/sda5/porteus3.2/Modules/xf86-video-amdgpu-1.1.1-x86_64.xzm)
/dev/loop11: []: (/mnt/sda5/porteus3.2/Modules/xf86-video-ati-7.7.1-x86_64.xzm)
/dev/loop12: []: (/mnt/sda5/porteus3.2/changes/porteussave.dat)
guest@porteus:~$ ls -l /mnt/live/mnt/isoloop/porteus
total 10
dr-xr-xr-x 2 root root 2048 Sep  3 03:04 base/
-rwxr-xr-x 1 root root 1015 Jul  6  2013 make_iso.sh*
dr-xr-xr-x 2 root root 2048 Sep  2 03:19 modules/
dr-xr-xr-x 2 root root 2048 Aug 28 19:33 optional/
-rw-r--r-- 1 root root  437 Jul  6  2013 porteus-v3.2-x86_64.sgn
drwxr-xr-x 2 root root 2048 Sep  2 03:20 rootcopy/
guest@porteus:~$ 
Ed

Bogomips
Full of knowledge
Full of knowledge
Posts: 2560
Joined: 25 Jun 2014, 15:21
Distribution: 3.2.2 Cinnamon & KDE5
Location: London

Re: Porteus module activation status

Post#40 by Bogomips » 08 Oct 2016, 01:07

jssouza wrote:screenshot shows the xzm module name also.
eg: /mnt/live/mnt/isoloop/porteus/base/000-kernel.xzm
A peculirity that also stood out for me. Believe 000-kernel.xzm is a directory name in the union. If not mistaken, the coding is to be seen in linuxrc.
Linux porteus 4.4.0-porteus #3 SMP PREEMPT Sat Jan 23 07:01:55 UTC 2016 i686 AMD Sempron(tm) 140 Processor AuthenticAMD GNU/Linux
NVIDIA Corporation C61 [GeForce 6150SE nForce 430] (rev a2) MemTotal: 901760 kB MemFree: 66752 kB

jssouza
DEV Team
DEV Team
Posts: 227
Joined: 09 Jul 2015, 14:17
Distribution: Porteus x86 arm
Location: Liechtenstein

Re: Porteus module activation status

Post#41 by jssouza » 08 Oct 2016, 13:27

Hi Bogomips,

You are right, technically they are directories in /mnt/live/memory/images, but do not look good in the display. Probably have to strip it off in the script.

Hi Ed_P,

You have showed me /mnt/live/mnt/isoloop/porteus. Could you also go one level deeper and show me the output of ls -l /mnt/live/mnt/isoloop/porteus/base/

I see you also have cinnamon 3.2rc5 booted in similar way (isoloop). Does the script show the base modules at the end there too? Also, I saw your 3.0.1 razorqt iso has a -nu at the end. I did not find this in the server. Is that a recreated iso?

Thanks!

User avatar
Ed_P
Contributor
Contributor
Posts: 3199
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 3.2.2 64-bit ISO
Location: Western NY, USA

Re: Porteus module activation status

Post#42 by Ed_P » 08 Oct 2016, 15:32

jssouza wrote:You have showed me /mnt/live/mnt/isoloop/porteus. Could you also go one level deeper and show me the output of ls -l /mnt/live/mnt/isoloop/porteus/base/

Code: Select all

guest@porteus:~$ ls -l /mnt/live/mnt/isoloop/porteus/base/ 
total 190120
-r--r--r-- 1 root root 16879616 Jan 30  2015 000-kernel.xzm
-r--r--r-- 1 root root 53059584 Jan 30  2015 001-core.xzm
-r--r--r-- 1 root root 48644096 Jan 30  2015 002-xorg.xzm
-r--r--r-- 1 root root 76099584 Jan 30  2015 003-razor.xzm
guest@porteus:~$ ls -l /mnt/live/mnt/isoloop/porteus/modules/ 
total 0
guest@porteus:~$ ls -l /mnt/live/mnt/isoloop/porteus/optional/
total 0
guest@porteus:~$ 
I see you also have cinnamon 3.2rc5 booted in similar way (isoloop).
I boot all my harddrive alternate OSs as ISOs via Grub4Dos or Grub2Win.
Does the script show the base modules at the end there too?
Image
Also, I saw your 3.0.1 razorqt iso has a -nu at the end. I did not find this in the server. Is that a recreated iso?
Apparently but I don't remember why or what changed. Do you have the 00* fix modules also?
Ed

User avatar
brokenman
Site Admin
Site Admin
Posts: 5503
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v3.2rcX all desktops
Location: Brazil
Contact:

Re: Porteus module activation status

Post#43 by brokenman » 08 Oct 2016, 21:30

If you are checking all conditions, don't forget the scenario where one boots via iso and uses copy2ram.
How do i become super user?
Wear your underpants on the outside and put on a cape.

User avatar
Ed_P
Contributor
Contributor
Posts: 3199
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 3.2.2 64-bit ISO
Location: Western NY, USA

Re: Porteus module activation status

Post#44 by Ed_P » 10 Oct 2016, 01:41

brokenman wrote:If you are checking all conditions, don't forget the scenario where one boots via iso and uses copy2ram.
If one boots via an iso isn't the iso in ram so why would one need to use copy2ram? :unknown:
Ed

User avatar
brokenman
Site Admin
Site Admin
Posts: 5503
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v3.2rcX all desktops
Location: Brazil
Contact:

Re: Porteus module activation status

Post#45 by brokenman » 10 Oct 2016, 01:46

They wouldn't. But if they did you would find a different set of circumstances in /mnt/live/ which have to be taken into account when scripting.
How do i become super user?
Wear your underpants on the outside and put on a cape.

Post Reply