Porteus module activation status

For discussions about programming and projects not necessarily associated with Porteus.
Bogomips
Full of knowledge
Full of knowledge
Posts: 2564
Joined: 25 Jun 2014, 15:21
Distribution: 3.2.2 Cinnamon & KDE5
Location: London

Re: Porteus module activation status

Post#61 by Bogomips » 24 Oct 2016, 21:08

jssouza wrote:if copy2ram along with load= and noload= cheatcodes are used, it could be a mixture of modules from base/modules/optional in RAM
As well extramod :)
  • Code: Select all

    root@porteus:/home/guest# usm -i
    ++++++++++++++++++++++++++++++
    usm application information
    
    USM version:  3.2.0
    DB version:  160320
    Current storage: /tmp/usm
    Current config: /etc/usm/usm.conf
    Current platform: Porteus-v3.2rc4
    Current arch: x86_64
    Current Slackware 14.2
    Current kernel 4.6.3-porteus
    
    quiet from=/dev/sda10/tmp/iso/rc4/x86_64/KDE.iso copy2ram ramsize=30% noauto rootcopy=/dev/sda4/kd64rcp noload=base/003 extramod=/dev/sda5/xtr64;/dev/sda5/kde5 rammod=base;nvidia
    
  • Code: Select all

    guest@porteus:~$ ls -lh /mnt/sda5/xtr64
    total 31M
    -rw-r--r-- 1 guest users 31M Jul 11 22:30 nvidia-304.131_rc4-x86_64.xzm
    guest@porteus:~$ ls -lh /mnt/sda5/kde5
    total 225M
    -rw-r--r-- 1 guest users 224M Jul  2 02:07 003-kde5.xzm
    
  • Code: Select all

    root@porteus:/home/guest# cat /var/log/porteus-livedbg
    # Recognized devices:
    ...
    /dev/sda11: UUID="6a0167f6-5cf7-412d-b85f-0076ca590371" TYPE="swap"
    
    # Booting device:
    /mnt/isoloop
    
    # Porteus data found in:
    /mnt/isoloop/porteus
    
    # Changes are stored in:
    memory
    
    # Non standard /rootcopy dir:
    /dev/sda4/kd64rcp
    
    # Modules activated during boot time:
    /memory/copy2ram/000-kernel.xzm
    /memory/copy2ram/001-core.xzm
    /memory/copy2ram/002-xorg.xzm
    /memory/copy2ram/nvidia-304.131_rc4-x86_64.xzm
    /mnt/sda5/kde5/003-kde5.xzm
    
    ISO=/mnt/sda10/tmp/iso/rc4/x86_64/KDE.iso
    
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

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

Re: Porteus module activation status

Post#62 by Bogomips » 29 Oct 2016, 01:43

Ed_P wrote:
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:
brokenman wrote: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.
Ed_P wrote:If one boots via an iso isn't the iso in ram
This was somewhat worrying, as the thought arose that had been using copy2ram to no purpose.

If I read it correctly, there are only two places where copy2ram is referenced:
  • Before copying modules to RAM
  • Before checking for removable booting medium
So it seems the only way one can receive a message that booting media are safely removable, is by using copy2ram.

To be doubly sure that copy2ram is not irrelevant when booting via an iso, had a bit of fun doctoring an initrd to provide relevant diagnostic output:
  • copy2ram
    • Upon entry to Live System

      Code: Select all

      guest@porteus:~$ free -m
                    total        used        free      shared  buff/cache   available
      Mem:            879         318          78         248         482         150
      Swap:           644          32         612
      
    • Code: Select all

      quiet debug from=/dev/sda10/tmp/iso/v3.2/i586/Porteus-CINNAMON-v3.2rc5-i586.iso copy2ram ramsize=30% noauto rootcopy=/dev/sda4/cin_rcp
    • Prior to Live System entry

      Code: Select all

      Live System ready. About to Pivot Root:
      
      free -m
                   total         used         free       shared      buffers
      Mem:           879          281          598          260            1
      -/+ buffers:                280          599
      Swap:            0            0            0
      
      ls -lh /memory/images
      total 0
      drwxr-xr-x    7      83 000-kernel.xzm
      drwxr-xr-x   19     268 001-core.xzm
      drwxr-xr-x    9     130 002-xorg.xzm
      drwxr-xr-x   11     141 003-cinnamon.xzm
      
      ls -lh /memory/copy2ram
      total 266472
      -rw-r--r--    1   42.8M 000-kernel.xzm
      -rw-r--r--    1   65.6M 001-core.xzm
      -rw-r--r--    1   78.3M 002-xorg.xzm
      -rw-r--r--    1   73.5M 003-cinnamon.xzm
      
      losetup
      /dev/loop1: 0 /memory/copy2ram/000-kernel.xzm
      /dev/loop2: 0 /memory/copy2ram/001-core.xzm
      /dev/loop3: 0 /memory/copy2ram/002-xorg.xzm
      /dev/loop4: 0 /memory/copy2ram/003-cinnamon.xzm
      
      mount
      aufs on /union type aufs (nowarn_perm,xino=/memory/xino/.aufs.xino,br:/memory/changes=rw)
      /dev/loop1 on /memory/images/000-kernel.xzm type squashfs (loop)
      /dev/loop2 on /memory/images/001-core.xzm type squashfs (loop)
      /dev/loop3 on /memory/images/002-xorg.xzm type squashfs (loop)
      /dev/loop4 on /memory/images/003-cinnamon.xzm type squashfs (loop)
      
    • At the End of the Day (Shutdown):

      Code: Select all

      free -m
                   total         used         free       shared      buffers
      Mem:           879          293          586          275            0
      -/+ buffers:                280          599
      Swap:            0            0            0
      
      ls -lh /memory/images
      total 0
      drwxr-xr-x   2     40 000-kernel.xzm
      drwxr-xr-x   2     40 001-core.xzm
      drwxr-xr-x   2     40 002-xorg.xzm
      drwxr-xr-x   2     40 003-cinnamon.xzm
      
      ls -lh /memory/copy2ram
      total 266472
      -rw-r--r--    1   42.8M 000-kernel.xzm
      -rw-r--r--    1   65.6M 001-core.xzm
      -rw-r--r--    1   78.3M 002-xorg.xzm
      -rw-r--r--    1   73.5M 003-cinnamon.xzm
      
      losetup
      
      mount
  • [copy2ram]
    • Upon entry to Live System

      Code: Select all

      guest@porteus:~$ free -m
                    total        used        free      shared  buff/cache   available
      Mem:            879         352          78          25         448         337
      Swap:           517           0         516
      
    • Code: Select all

      quiet debug from=/dev/sda10/tmp/iso/v3.2/i586/Porteus-CINNAMON-v3.2rc5-i586.iso ramsize=30% noauto rootcopy=/dev/sda4/cin_rcp
    • Prior to Live System entry

      Code: Select all

      Live System ready. About to Pivot Root:
      
      free -m
                   total         used         free       shared      buffers
      Mem:           879           28          851            0            2
      -/+ buffers:                 26          853
      Swap:            0            0            0
      
      ls -lh /memory/images
      total 0
      drwxr-xr-x    7      83 000-kernel.xzm
      drwxr-xr-x   19     268 001-core.xzm
      drwxr-xr-x    9     130 002-xorg.xzm
      drwxr-xr-x   11     141 003-cinnamon.xzm
      
      ls -lh /memory/copy2ram
      total 0
      
      losetup
      /dev/loop0: 0 /mnt/sda10/tmp/iso/v3.2/i586/Porteus-CINNAMON-v3.2rc5-i586.iso
      /dev/loop1: 0 /mnt/isoloop/porteus/base/000-kernel.xzm
      /dev/loop2: 0 /mnt/isoloop/porteus/base/001-core.xzm
      /dev/loop3: 0 /mnt/isoloop/porteus/base/002-xorg.xzm
      /dev/loop4: 0 /mnt/isoloop/porteus/base/003-cinnamon.xzm
      
      mount
      /dev/loop0 on /mnt/isoloop type iso9660 (loop,ro)
      aufs on /union type aufs (nowarn_perm,xino=/memory/xino/.aufs.xino,br:/memory/changes=rw)
      /dev/loop1 on /memory/images/000-kernel.xzm type squashfs (loop,ro)
      /dev/loop2 on /memory/images/001-core.xzm type squashfs (loop,ro)
      /dev/loop3 on /memory/images/002-xorg.xzm type squashfs (loop,ro)
      /dev/loop4 on /memory/images/003-cinnamon.xzm type squashfs (loop,ro)
      
    • At the End of the Day (Shutdown):

      Code: Select all

      free -m
                   total         used         free       shared      buffers
      Mem:           879          126          752            15           11
      -/+ buffers:                115          764
      Swap:            0            0            0
      
      ls -lh /memory/images
      total 0
      drwxr-xr-x   2     40 000-kernel.xzm
      drwxr-xr-x   2     40 001-core.xzm
      drwxr-xr-x   2     40 002-xorg.xzm
      drwxr-xr-x   2     40 003-cinnamon.xzm
      
      ls -lh /memory/copy2ram
      total 0
      
      losetup
      
      mount
Comparing memory usage clearly shows a difference when using copy2ram in the case of bootiing from ISO file. So far noticed no deterioration in performance when not running in RAM, but just from ISO. The bad news is that system is looping at two remove. Firstly on the ISO file, then at two remove on kernel, core, xorg, and cinnamon. So have disk accesses to loop ISO then additional accesses to loop the system modules. The good news however being that some 260M, of limited 879M RAM in total, becomes available. Maybe it's a matter of what you lose on the roundabouts, you gain on the swings. :unknown:

porteus-livedbg
  • copy2ram

    Code: Select all

    quiet debug from=/dev/sda10/tmp/iso/v3.2/i586/Porteus-CINNAMON-v3.2rc5-i586.iso copy2ram ramsize=30% noauto rootcopy=/dev/sda4/cin_rcp
    
    Prior to copying of rootcopy folder
    
    free -m
                 total         used         free       shared      buffers
    Mem:           879          804           75          262            1
    -/+ buffers:                802           76
    Swap:            0            0            0
    
    ls -lh /memory/images
    total 0
    drwxr-xr-x    7      83 000-kernel.xzm
    drwxr-xr-x   19     268 001-core.xzm
    drwxr-xr-x    9     130 002-xorg.xzm
    drwxr-xr-x   11     141 003-cinnamon.xzm
    
    ls -lh /memory/copy2ram
    total 266472
    -rw-r--r--    1   42.8M 000-kernel.xzm
    -rw-r--r--    1   65.6M 001-core.xzm
    -rw-r--r--    1   78.3M 002-xorg.xzm
    -rw-r--r--    1   73.5M 003-cinnamon.xzm
    
    losetup
    /dev/loop0: 0 /mnt/sda10/tmp/iso/v3.2/i586/Porteus-CINNAMON-v3.2rc5-i586.iso
    /dev/loop1: 0 /memory/copy2ram/000-kernel.xzm
    /dev/loop2: 0 /memory/copy2ram/001-core.xzm
    /dev/loop3: 0 /memory/copy2ram/002-xorg.xzm
    /dev/loop4: 0 /memory/copy2ram/003-cinnamon.xzm
    
    mount
    /dev/loop0 on /mnt/isoloop type iso9660 (loop,ro)
    aufs on /union type aufs (nowarn_perm,xino=/memory/xino/.aufs.xino,br:/memory/changes=rw)
    /dev/loop1 on /memory/images/000-kernel.xzm type squashfs (loop)
    /dev/loop2 on /memory/images/001-core.xzm type squashfs (loop)
    /dev/loop3 on /memory/images/002-xorg.xzm type squashfs (loop)
    /dev/loop4 on /memory/images/003-cinnamon.xzm type squashfs (loop)
    
    After renewed Setup of File System Table and Before checking for copy into ram of removable media
    
    free -m
                 total         used         free       shared      buffers
    Mem:           879          807           72          262            3
    -/+ buffers:                804           75
    Swap:            0            0            0
    
    ls -lh /memory/images
    total 0
    drwxr-xr-x    7      83 000-kernel.xzm
    drwxr-xr-x   19     268 001-core.xzm
    drwxr-xr-x    9     130 002-xorg.xzm
    drwxr-xr-x   11     141 003-cinnamon.xzm
    
    ls -lh /memory/copy2ram
    total 266472
    -rw-r--r--    1   42.8M 000-kernel.xzm
    -rw-r--r--    1   65.6M 001-core.xzm
    -rw-r--r--    1   78.3M 002-xorg.xzm
    -rw-r--r--    1   73.5M 003-cinnamon.xzm
    
    losetup
    /dev/loop0: 0 /mnt/sda10/tmp/iso/v3.2/i586/Porteus-CINNAMON-v3.2rc5-i586.iso
    /dev/loop1: 0 /memory/copy2ram/000-kernel.xzm
    /dev/loop2: 0 /memory/copy2ram/001-core.xzm
    /dev/loop3: 0 /memory/copy2ram/002-xorg.xzm
    /dev/loop4: 0 /memory/copy2ram/003-cinnamon.xzm
    
    mount
    /dev/loop0 on /mnt/isoloop type iso9660 (loop,ro)
    aufs on /union type aufs (nowarn_perm,xino=/memory/xino/.aufs.xino,br:/memory/changes=rw)
    /dev/loop1 on /memory/images/000-kernel.xzm type squashfs (loop)
    /dev/loop2 on /memory/images/001-core.xzm type squashfs (loop)
    /dev/loop3 on /memory/images/002-xorg.xzm type squashfs (loop)
    /dev/loop4 on /memory/images/003-cinnamon.xzm type squashfs (loop)
    
    # Recognized devices:
    ...
    /dev/sda11: UUID="6a0167f6-5cf7-412d-b85f-0076ca590371" TYPE="swap" 
    
    # Booting device:
    /mnt/isoloop
    
    # Porteus data found in:
    /mnt/isoloop/porteus
    
    # Changes are stored in:
    memory
    
    # Non standard /rootcopy dir:
    /dev/sda4/cin_rcp
    
    # Modules activated during boot time:
    /memory/copy2ram/000-kernel.xzm
    /memory/copy2ram/001-core.xzm
    /memory/copy2ram/002-xorg.xzm
    /memory/copy2ram/003-cinnamon.xzm
    
    ISO=/mnt/sda10/tmp/iso/v3.2/i586/Porteus-CINNAMON-v3.2rc5-i586.iso
    
    Live System ready. About to Pivot Root:
    
    free -m
                 total         used         free       shared      buffers
    Mem:           879          281          598          260            1
    -/+ buffers:                280          599
    Swap:            0            0            0
    
    ls -lh /memory/images
    total 0
    drwxr-xr-x    7      83 000-kernel.xzm
    drwxr-xr-x   19     268 001-core.xzm
    drwxr-xr-x    9     130 002-xorg.xzm
    drwxr-xr-x   11     141 003-cinnamon.xzm
    
    ls -lh /memory/copy2ram
    total 266472
    -rw-r--r--    1   42.8M 000-kernel.xzm
    -rw-r--r--    1   65.6M 001-core.xzm
    -rw-r--r--    1   78.3M 002-xorg.xzm
    -rw-r--r--    1   73.5M 003-cinnamon.xzm
    
    losetup
    /dev/loop1: 0 /memory/copy2ram/000-kernel.xzm
    /dev/loop2: 0 /memory/copy2ram/001-core.xzm
    /dev/loop3: 0 /memory/copy2ram/002-xorg.xzm
    /dev/loop4: 0 /memory/copy2ram/003-cinnamon.xzm
    
    mount
    aufs on /union type aufs (nowarn_perm,xino=/memory/xino/.aufs.xino,br:/memory/changes=rw)
    /dev/loop1 on /memory/images/000-kernel.xzm type squashfs (loop)
    /dev/loop2 on /memory/images/001-core.xzm type squashfs (loop)
    /dev/loop3 on /memory/images/002-xorg.xzm type squashfs (loop)
    /dev/loop4 on /memory/images/003-cinnamon.xzm type squashfs (loop)
    
  • [copy2ram]

    Code: Select all

    quiet debug from=/dev/sda10/tmp/iso/v3.2/i586/Porteus-CINNAMON-v3.2rc5-i586.iso ramsize=30% noauto rootcopy=/dev/sda4/cin_rcp 
    Prior to copying of rootcopy folder
    
    free -m
                 total         used         free       shared      buffers
    Mem:           879           23          856            1            1
    -/+ buffers:                 22          857
    Swap:            0            0            0
    
    ls -lh /memory/images
    total 0
    drwxr-xr-x    7      83 000-kernel.xzm
    drwxr-xr-x   19     268 001-core.xzm
    drwxr-xr-x    9     130 002-xorg.xzm
    drwxr-xr-x   11     141 003-cinnamon.xzm
    
    ls -lh /memory/copy2ram
    total 0
    
    losetup
    /dev/loop0: 0 /mnt/sda10/tmp/iso/v3.2/i586/Porteus-CINNAMON-v3.2rc5-i586.iso
    /dev/loop1: 0 /mnt/isoloop/porteus/base/000-kernel.xzm
    /dev/loop2: 0 /mnt/isoloop/porteus/base/001-core.xzm
    /dev/loop3: 0 /mnt/isoloop/porteus/base/002-xorg.xzm
    /dev/loop4: 0 /mnt/isoloop/porteus/base/003-cinnamon.xzm
    
    mount
    /dev/loop0 on /mnt/isoloop type iso9660 (loop,ro)
    aufs on /union type aufs (nowarn_perm,xino=/memory/xino/.aufs.xino,br:/memory/changes=rw)
    /dev/loop1 on /memory/images/000-kernel.xzm type squashfs (loop,ro)
    /dev/loop2 on /memory/images/001-core.xzm type squashfs (loop,ro)
    /dev/loop3 on /memory/images/002-xorg.xzm type squashfs (loop,ro)
    /dev/loop4 on /memory/images/003-cinnamon.xzm type squashfs (loop,ro)
    
    After renewed Setup of File System Table and Before checking for copy into ram of removable media
    
    free -m
                 total         used         free       shared      buffers
    Mem:           879           31          847            2            2
    -/+ buffers:                 29          850
    Swap:            0            0            0
    
    ls -lh /memory/images
    total 0
    drwxr-xr-x    7      83 000-kernel.xzm
    drwxr-xr-x   19     268 001-core.xzm
    drwxr-xr-x    9     130 002-xorg.xzm
    drwxr-xr-x   11     141 003-cinnamon.xzm
    
    ls -lh /memory/copy2ram
    total 0
    
    losetup
    /dev/loop0: 0 /mnt/sda10/tmp/iso/v3.2/i586/Porteus-CINNAMON-v3.2rc5-i586.iso
    /dev/loop1: 0 /mnt/isoloop/porteus/base/000-kernel.xzm
    /dev/loop2: 0 /mnt/isoloop/porteus/base/001-core.xzm
    /dev/loop3: 0 /mnt/isoloop/porteus/base/002-xorg.xzm
    /dev/loop4: 0 /mnt/isoloop/porteus/base/003-cinnamon.xzm
    
    mount
    /dev/loop0 on /mnt/isoloop type iso9660 (loop,ro)
    aufs on /union type aufs (nowarn_perm,xino=/memory/xino/.aufs.xino,br:/memory/changes=rw)
    /dev/loop1 on /memory/images/000-kernel.xzm type squashfs (loop,ro)
    /dev/loop2 on /memory/images/001-core.xzm type squashfs (loop,ro)
    /dev/loop3 on /memory/images/002-xorg.xzm type squashfs (loop,ro)
    /dev/loop4 on /memory/images/003-cinnamon.xzm type squashfs (loop,ro)
    
    # Recognized devices:
    ...
    /dev/sda11: UUID="6a0167f6-5cf7-412d-b85f-0076ca590371" TYPE="swap" 
    
    # Booting device:
    /mnt/isoloop
    
    # Porteus data found in:
    /mnt/isoloop/porteus
    
    # Changes are stored in:
    memory
    
    # Non standard /rootcopy dir:
    /dev/sda4/cin_rcp
    
    # Modules activated during boot time:
    /mnt/isoloop/porteus/base/000-kernel.xzm
    /mnt/isoloop/porteus/base/001-core.xzm
    /mnt/isoloop/porteus/base/002-xorg.xzm
    /mnt/isoloop/porteus/base/003-cinnamon.xzm
    
    ISO=/mnt/sda10/tmp/iso/v3.2/i586/Porteus-CINNAMON-v3.2rc5-i586.iso
    Live System ready. About to Pivot Root:
    
    free -m
                 total         used         free       shared      buffers
    Mem:           879           28          851            0            2
    -/+ buffers:                 26          853
    Swap:            0            0            0
    
    ls -lh /memory/images
    total 0
    drwxr-xr-x    7      83 000-kernel.xzm
    drwxr-xr-x   19     268 001-core.xzm
    drwxr-xr-x    9     130 002-xorg.xzm
    drwxr-xr-x   11     141 003-cinnamon.xzm
    
    ls -lh /memory/copy2ram
    total 0
    
    losetup
    /dev/loop0: 0 /mnt/sda10/tmp/iso/v3.2/i586/Porteus-CINNAMON-v3.2rc5-i586.iso
    /dev/loop1: 0 /mnt/isoloop/porteus/base/000-kernel.xzm
    /dev/loop2: 0 /mnt/isoloop/porteus/base/001-core.xzm
    /dev/loop3: 0 /mnt/isoloop/porteus/base/002-xorg.xzm
    /dev/loop4: 0 /mnt/isoloop/porteus/base/003-cinnamon.xzm
    
    mount
    /dev/loop0 on /mnt/isoloop type iso9660 (loop,ro)
    aufs on /union type aufs (nowarn_perm,xino=/memory/xino/.aufs.xino,br:/memory/changes=rw)
    /dev/loop1 on /memory/images/000-kernel.xzm type squashfs (loop,ro)
    /dev/loop2 on /memory/images/001-core.xzm type squashfs (loop,ro)
    /dev/loop3 on /memory/images/002-xorg.xzm type squashfs (loop,ro)
    /dev/loop4 on /memory/images/003-cinnamon.xzm type squashfs (loop,ro)
    
    
Last edited by Bogomips on 06 Nov 2016, 14:56, edited 2 times in total.
Reason: loop vs memory
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
Legendary
Legendary
Posts: 1165
Joined: 09 Jul 2015, 14:17
Distribution: Porteus x86 arm

Re: Porteus module activation status

Post#63 by jssouza » 21 Feb 2017, 13:18

Here is a small script that can dynamically update the status of activated modules in openbox's context menu. It uses openbox's menu feature called Pipe Menus. This way, a single right click should show the activated modules in openbox, as well as desktops that use openbox like LXDE/LXQT. The menu updates automatically when new modules are activated/deactivated.

Code: Select all

#!/bin/bash

NUM_MODULES=$(ls -1 "/mnt/live/memory/images/" | wc -l)
echo "<openbox_pipe_menu>"
echo "<item label=\"Modules Activated: $NUM_MODULES\"/>"
echo "<separator/>"
for MODULE in $(ls -1 "/mnt/live/memory/images/"); do
  echo "<item label=\""$MODULE"\"/>"
done
echo "</openbox_pipe_menu>"
Save this as lsmodules.sh (executable bit set) in /home/guest/.config/openbox.

Update openbox's menu.xml (usually, this is /home/guest/.config/openbox/menu.xml) and add the following lines:

Code: Select all

  <separator />
  <menu id="lsmodules" label="Porteus Modules" execute="/home/guest/.config/openbox/lsmodules.sh" />
Log out and log back in or just run in a terminal

Code: Select all

openbox --reconfigure
The right click context menu should now show the list of activated modules.
Image

On LXDE, I use /home/guest/.config/openbox/lxde-rc.xml to take a local menu in /home/guest/.config/openbox/lxde-menu.xml where the openbox menu items are updated.

User avatar
ncmprhnsbl
DEV Team
DEV Team
Posts: 3918
Joined: 20 Mar 2012, 03:42
Distribution: v5.0-64bit
Location: australia
Contact:

Re: Porteus module activation status

Post#64 by ncmprhnsbl » 03 Mar 2017, 03:37

cool.. i'll look at including this in my next 003-openbox module ... thanks :)
Forum Rules : https://forum.porteus.org/viewtopic.php?f=35&t=44

jssouza
Legendary
Legendary
Posts: 1165
Joined: 09 Jul 2015, 14:17
Distribution: Porteus x86 arm

Re: Porteus module activation status

Post#65 by jssouza » 03 Mar 2017, 15:06

Glad you like it :)

jssouza
Legendary
Legendary
Posts: 1165
Joined: 09 Jul 2015, 14:17
Distribution: Porteus x86 arm

Porteus module activation status

Post#66 by jssouza » 06 Mar 2018, 21:13

can't get enough of this :)

So I ported this to Qt Quick.

Link here: http://www.mediafire.com/file/85343keoe ... cfa62d.zip

At the moment (Porteus v4.0 rc4) only KDE has qt quick modules. So if you are on Porteus v4.0 rc4 KDE5, please take a look at this. You would also need the QT devel module - http://www.mediafire.com/file/udgus6vf9 ... -other.xzm

To compile (on KDE5 at the moment):

Code: Select all

unzip jssouza-lsmodules-28347ecfa62d.zip
cd jssouza-lsmodules-28347ecfa62d
qmake
make
and then

Code: Select all

./lsmodules
You should get the application as such:
https://s9.postimg.org/xwits0wun/Screen ... 220229.png
  • Shows Modules activated or not
  • Press and hold to get Module Path
  • Double click to activate/deactivate module
If module is activated/deactivated externally, it automatically gets reflected in the application. Have tested and added support for extramods and copy2ram.

If all goes well, I can include it in the next KDE5 release :)

User avatar
Ed_P
Contributor
Contributor
Posts: 8315
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 5.01 ISO
Location: Western NY, USA

Porteus module activation status

Post#67 by Ed_P » 07 Mar 2018, 00:28

Neat. :happy62:
Ed

User avatar
ncmprhnsbl
DEV Team
DEV Team
Posts: 3918
Joined: 20 Mar 2012, 03:42
Distribution: v5.0-64bit
Location: australia
Contact:

Porteus module activation status

Post#68 by ncmprhnsbl » 07 Mar 2018, 11:45

built, tested :good: looks good..

an idea : some way to add(not activate) a directory(with modules in it), perhaps via a file chooser..
Forum Rules : https://forum.porteus.org/viewtopic.php?f=35&t=44

jssouza
Legendary
Legendary
Posts: 1165
Joined: 09 Jul 2015, 14:17
Distribution: Porteus x86 arm

Porteus module activation status

Post#69 by jssouza » 07 Mar 2018, 18:54

Good idea. I'll try to implement that.

jssouza
Legendary
Legendary
Posts: 1165
Joined: 09 Jul 2015, 14:17
Distribution: Porteus x86 arm

Porteus module activation status

Post#70 by jssouza » 08 Mar 2018, 12:16

We now have a new problem :). What if extramod cheatcode is not passed to the bootloader, but added in the cfg file? The application should then check both /proc/cmdline as well as cfgfile for the cheatcode.

I guess this is now a general problem in all porteus scripts that check /proc/cmdline.

jssouza
Legendary
Legendary
Posts: 1165
Joined: 09 Jul 2015, 14:17
Distribution: Porteus x86 arm

Porteus module activation status

Post#71 by jssouza » 15 Mar 2018, 21:31

ncmprhnsbl wrote:
07 Mar 2018, 11:45
some way to add(not activate) a directory(with modules in it), perhaps via a file chooser..
Done in http://www.mediafire.com/file/rrwsgjr6r ... 8ed6a2.zip. contents of $HOME/.config/lsmodules should also be added in the dirs to be watched (to be able to be set as watchable by the application and dir entries can be added)
Note that the application still checks /proc/cmdline for extramods - will change it to /etc/bootcmd.cfg once that change has been released in the next porteus release.

User avatar
ncmprhnsbl
DEV Team
DEV Team
Posts: 3918
Joined: 20 Mar 2012, 03:42
Distribution: v5.0-64bit
Location: australia
Contact:

Porteus module activation status

Post#72 by ncmprhnsbl » 17 Mar 2018, 08:21

tested, nice :)
seems to have trouble with dirs with only one module in them(unless added via the dialog)
eg. booted with extramod=/mnt/sdb2/KDE (which contained one module) and although that module is listed, it is under 'other' not 'KDE'
once i added /mnt/sdb2/KDE(via the file dialog) the module was then assigned correctly
jssouza wrote:
15 Mar 2018, 21:31
(to be able to be set as watchable by the application and dir entries can be added)
but not directly edited, right? (because this didn't seem to work, even with restarting the app)
Forum Rules : https://forum.porteus.org/viewtopic.php?f=35&t=44

User avatar
brokenman
Site Admin
Site Admin
Posts: 6105
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v4 all desktops
Location: Brazil

Porteus module activation status

Post#73 by brokenman » 17 Mar 2018, 21:03

jssouza wrote:
08 Mar 2018, 12:16
I guess this is now a general problem in all porteus scripts that check /proc/cmdline.
I the next release you may now check the single file /etc/bootcmd.cfg
How do i become super user?
Wear your underpants on the outside and put on a cape.

User avatar
Ed_P
Contributor
Contributor
Posts: 8315
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 5.01 ISO
Location: Western NY, USA

Porteus module activation status

Post#74 by Ed_P » 18 Mar 2018, 00:09

Any time frame for when to expect "the next release"?
Ed

User avatar
brokenman
Site Admin
Site Admin
Posts: 6105
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v4 all desktops
Location: Brazil

Porteus module activation status

Post#75 by brokenman » 18 Mar 2018, 15:49

Probably tonight. I will upload the base ISO for desktop maintainers to create desktops around.
How do i become super user?
Wear your underpants on the outside and put on a cape.

Post Reply