Porteus 3.1rc feedback

[Bogomips]

Found it!

In mate 32bit fresh mode I loaded only the following modules: fftw, lcms2 and imagemagick
I then copied only the file /usr/bin/cpp from the package: gcc-4.8.2-i486-1

Now you need to logout and log back in and it works.

So it is a DE/X Interface Issue after all?
AF 32 bit

Code: Select all

guest@porteus:~$ grep command /var/log/dmesg 
[    0.000000] Kernel command line: quiet copy2ram ramsize=30% noauto timezone=Europe/London volume=60% noload=kde load=t/003-m
guest@porteus:~$ grep xzm /var/log/porteus-livedbg 
/memory/copy2ram/000-kernel.xzm
/memory/copy2ram/001-core.xzm
/memory/copy2ram/002-xorg.xzm
/memory/copy2ram/sudo-1.8.9p5-i486-1.xzm
/memory/copy2ram/003-mate.xzm
guest@porteus:~$ ls -1 /mnt/live/memory/images/
000-kernel.xzm/
001-core.xzm/
002-xorg.xzm/
003-mate.xzm/
sudo-1.8.9p5-i486-1.xzm/

MATE MODULE

Code: Select all

IM_221114_m
fftw-3.3.3-i486-1.txz
imagemagick-6.8.6_10-i486-1.txz
lcms2-2.4-i486-1.txz

MATE Replication Attempts (Trying out various combinations)

1. Code: Select all

   root@porteus:/home/guest# activate /mnt/sda1/mods/IM_221114_m.xzm 
   Updating shared library links:  /sbin/ldconfig
   guest@porteus:~$ ls -1 /mnt/live/memory/images/
   000-kernel.xzm/
   001-core.xzm/
   002-xorg.xzm/
   003-mate.xzm/
   IM_221114_m.xzm/
   sudo-1.8.9p5-i486-1.xzm/
   guest@porteus:~$ display
   display: color is not known to server `FOREGROUND': Success @ error/xwindow.c/XGetPixelPacket/3064.
   Log OUT[/IN]
   REISUB
   

2. Code: Select all

   root@porteus:/home/guest# cp p10/Por/usr/bin/cpp /usr/bin
   root@porteus:/home/guest# activate /mnt/sda1/mods/IM_221114_m.xzm 
   Updating shared library links:  /sbin/ldconfig
   guest@porteus:~$ ls -1 /mnt/live/memory/images/
   000-kernel.xzm/
   001-core.xzm/
   002-xorg.xzm/
   003-mate.xzm/
   IM_221114_m.xzm/
   sudo-1.8.9p5-i486-1.xzm/
   guest@porteus:~$ display
   display: color is not known to server `FOREGROUND': Success @ error/xwindow.c/XGetPixelPacket/3064.
   Log OUT[/IN]
   2 x REISUB
   

3. Code: Select all

   root@porteus:/home/guest# activate /mnt/sda1/mods/IM_221114_m.xzm 
   Updating shared library links:  /sbin/ldconfig
   guest@porteus:~$ ls -1 /mnt/live/memory/images/
   000-kernel.xzm/
   001-core.xzm/
   002-xorg.xzm/
   003-mate.xzm/
   IM_221114_m.xzm/
   sudo-1.8.9p5-i486-1.xzm
   Log OUT/IN
   guest@porteus:~$ display
   display: color is not known to server `FOREGROUND': Success @ error/xwindow.c/XGetPixelPacket/3064.
   cp p10/Por/usr/bin/cpp /usr/bin
   guest@porteus:~$ display
   display: color is not known to server `FOREGROUND': Success @ error/xwindow.c/XGetPixelPacket/3064.
   Log OUT/IN
   REISUB
   
4. Of interest here, is that after the first activation /usr/bin/cpp can be removed and it all still works, even after a deactivation.

   Code: Select all

   root@porteus:/home/guest# cp p10/Por/usr/bin/cpp /usr/bin
   root@porteus:/home/guest# activate /mnt/sda1/mods/IM_221114_m.xzm 
   Updating shared library links:  /sbin/ldconfig
   guest@porteus:~$ ls -1 /mnt/live/memory/images/
   000-kernel.xzm/
   001-core.xzm/
   002-xorg.xzm/
   003-mate.xzm/
   IM_221114_m.xzm/
   sudo-1.8.9p5-i486-1.xzm/
   Log OUT/IN
   guest@porteus:~$ display
   guest@porteus:~$ display
   root@porteus:/home/guest# rm /usr/bin/cpp 
   root@porteus:/home/guest# ls /usr/bin/cpp 
   /bin/ls: cannot access /usr/bin/cpp: No such file or directory
   guest@porteus:~$ display
   guest@porteus:~$ display
   root@porteus:/home/guest# deactivate /mnt/sda1/mods/IM_221114_m.xzm 
   Updating shared library links:  /sbin/ldconfig
   root@porteus:/home/guest# activate /mnt/sda1/mods/IM_221114_m.xzm 
   Updating shared library links:  /sbin/ldconfig
   guest@porteus:~$ ls -1 /mnt/live/memory/images/
   000-kernel.xzm/
   001-core.xzm/
   002-xorg.xzm/
   003-mate.xzm/
   IM_221114_m.xzm/
   sudo-1.8.9p5-i486-1.xzm/
   guest@porteus:~$ display
   guest@porteus:~$ display
   

Before resorting to SysRq REISUB, always had an almost white screen. (No login screen)

MATE Testing Workaround for ImageMagick 6.8.9-8 from Arch, served as spur to try above combinations, following unexpected result.

1. Code: Select all

   root@porteus:/home/guest# activate p4/mods/ImgMgk_241014.xzm 
   
   guest@porteus:~$ ls -1 /mnt/live/memory/images/
   000-kernel.xzm/
   001-core.xzm/
   002-xorg.xzm/
   003-mate.xzm/
   ImgMgk_241014.xzm/
   sudo-1.8.9p5-i486-1.xzm/
   
   guest@porteus:~$ display
   display: color is not known to server `FOREGROUND': Success @ error/xwindow.c/XGetPixelPacket/3040.
   display: color is not known to server `BACKGROUND': Success @ error/xwindow.c/XGetPixelPacket/3052.
   
   guest@porteus:~$ identify -version
   Version: ImageMagick 6.8.9-8 Q16 i686 2014-10-09 http://www.imagemagick.org
   Copyright: Copyright (C) 1999-2014 ImageMagick Studio LLC
   Features: DPC HDRI Modules OpenCL OpenMP
   Delegates: bzlib cairo fontconfig freetype gslib jng jp2 jpeg lcms lqr ltdl lzma pangocairo png ps rsvg tiff webp wmf x xml zlib
   

2. Code: Select all

   root@porteus:/home/guest# deactivate /mnt/sda4/mods/ImgMgk_241014.xzm
   (The module can't be removed, because it's busy)
   guest@porteus:~$ mkdir gcc
   guest@porteus:~$ tar xJf /tmp/usm/gcc-4.8.2-i486-1.txz -C gcc
   guest@porteus:~$ sudo cp gcc/usr/bin/cpp /usr/bin
   guest@porteus:~$ cp --parents /usr/bin/cpp p10/Por
   guest@porteus:~$ rm -r gcc
   
3. Init 3/4 (# deactivate /mnt/sda4/mods/ImgMgk_241014.xzm Successful)

4. Code: Select all

   root@porteus:/home/guest# sh p10/Por/xzmod.sh -q p10/Por/ImMagick/IM_221114_m . /mnt/sda1/mods/
   Default Module Name: IM_221114_m.xzm
   
   Installing to Fakeroot Directory
   
   fftw-3.3.3-i486-1: Fastest Fourier Transform in the West                 [14M] 
   imagemagick-6.8.6_10-i486-1: a robust collection of image processing too [17M] 
   lcms2-2.4-i486-1: little cms engine, version 2                           [3.1M]
   
   Creating Module IM_221114_m.xzm
   
   Parallel mksquashfs: Using 1 processor
   Creating 4.0 filesystem on /mnt/sda1/mods//IM_221114_m.xzm, block size 262144.
   [=============================================================/] 1518/1518 100%
   
   Exportable Squashfs 4.0 filesystem, xz compressed, data block size 262144
   	compressed data, compressed metadata, compressed fragments, compressed xattrs
   	duplicates are removed
   Filesystem size 11624.54 Kbytes (11.35 Mbytes)
   
   
5. NO log OUT/IN

6. Code: Select all

   guest@porteus:~$ ls -1 /mnt/live/memory/images/
   000-kernel.xzm/
   001-core.xzm/
   002-xorg.xzm/
   003-mate.xzm/
   IM_221114_m.xzm/
   sudo-1.8.9p5-i486-1.xzm/
   guest@porteus:~$ display
   guest@porteus:~$ display
   
   root@porteus:/home/guest# deactivate /mnt/sda1/mods//IM_221114_m.xzm
   Updating shared library links:  /sbin/ldconfig
   guest@porteus:~$ ls -1 /mnt/live/memory/images/
   Updating shared library links:  /sbin/ldconfig
   11. guest@porteus:~$ ls -1 /mnt/live/memory/images/
   000-kernel.xzm/
   001-core.xzm/
   002-xorg.xzm/
   003-mate.xzm/
   sudo-1.8.9p5-i486-1.xzm/
   

   It is interesting to note that the Init 4 effected a reset, not affected by subsequent procedures. Implication being that after 1st Init 4, a procedure has unset something which it has not reset?

[Ed_P]

Before resorting to SysRq REISUB, always had an almost white screen. (No login screen)

What is "SysRq REISUB"? On occasion when I boot Porteus it goes to a white screen and I turn the netbook off and back on to get out of it. I assumed corrupted storage somewhere since powering off and on allows the system to reboot normally. But off and on is a brutal way to fix pc problems so your way sounds better. I just don't know how to do it.

[donald]

Hi Ed
An explanation can be found here:
REISUB

[brokenman]

But off and on is a brutal way to fix pc problems

It is indeed and is also the cause of many a data corruption. REISUB is a way to back out of a freeze one step at a time until your system either becomes usable or reboots graciously. I suggest thinking of an acronym to remember the order of keystrokes. You may also use REISUO (from memory) which will shutdown without rebooting.

[Ed_P]

Hi Ed
An explanation can be found here:
REISUB

Excellent write up. Thank you Donald.

But off and on is a brutal way to fix pc problems

It is indeed and is also the cause of many a data corruption. REISUB is a way to back out of a freeze one step at a time until your system either becomes usable or reboots graciously. I suggest thinking of an acronym to remember the order of keystrokes. You may also use REISUO (from memory) which will shutdown without rebooting.

Thank you brokenman.

Yes, remembering the sequence of keys will be useful. Where'd I put that piece of paper?

[Bogomips]

Yes, remembering the sequence of keys will be useful. Where'd I put that piece of paper?

Write down BUSIER and put it up to a mirror.

P.S. Give about a sec between each keystroke.

[brokenman]

I use my own:
Really Easy If Someone Understands Binary

The standard is:
Raising Elephants Is So Utterly Boring

Some more I just invented:
Roast Elephant Is So Utterly Bland
Roasting Elephants Is Seldom Understood Behaviour

I love elephant/s.

[Ed_P]

Thank you guys. A great way to start a day.

[francois]

LXQT:
issue a) is resolved now (dirty hack and i'm hoping it wont make any troubles...) so only b) left.

thanks

Does this means that persistance will be available for lxqt. Is the modified version of lxqt available now?

Thanks.

[dafan]

Hi!

In the Wishlist for porteus 3.1 I have suggested to move the /boot directory under the /porteus directory, but it doesn't happen until RC2, so I did days of research and found the solution. I post the steps and patches here. Please add it to the comming Porteus 3.1.

After the /boot directory is moved under the /porteus directory, syslinux must be able to find its files. A list of search directories is hardcoded in the syslinux source code, so the new directory (/porteus/boot/syslinux) must be added to the list. The following patch does this. This patch should be applied to syslinux 4.06, which is also used in Porteus 3.1 RC2.

Code: Select all

diff -rupN syslinux-4.06.orig/core/fs/iso9660/iso9660.c syslinux-4.06/core/fs/iso9660/iso9660.c
--- syslinux-4.06.orig/core/fs/iso9660/iso9660.c	2012-10-23 11:53:17.000000000 +0200
+++ syslinux-4.06/core/fs/iso9660/iso9660.c	2014-11-26 10:03:47.921248305 +0100
@@ -231,8 +231,10 @@ static int iso_load_config(void)
     static const char *search_directories[] = {
 	"/boot/isolinux", 
 	"/isolinux",
+	"/porteus/boot/isolinux", 
 	"/boot/syslinux", 
 	"/syslinux", 
+	"/porteus/boot/syslinux", 
 	"/",
 	NULL
     };
diff -rupN syslinux-4.06.orig/core/fs/lib/loadconfig.c syslinux-4.06/core/fs/lib/loadconfig.c
--- syslinux-4.06.orig/core/fs/lib/loadconfig.c	2012-10-23 11:53:17.000000000 +0200
+++ syslinux-4.06/core/fs/lib/loadconfig.c	2014-11-26 10:04:01.574249068 +0100
@@ -18,6 +18,7 @@ int generic_load_config(void)
 	"/boot/syslinux",
 	"/syslinux",
 	"/",
+	"/porteus/boot/syslinux",
 	NULL
     };
     static const char *filenames[] = {

Then run 'make' to compile syslinux. In the source directory, the compiled core/isolinux.bin and extlinux/extlinux are needed. They should replace /porteus/boot/syslinux/isolinux.bin and extlinux.com (embedded in /porteus/boot/Porteus-installer-for-Linux.com) in the Porteus directory. Now syslinux is able to find the files in /porteus/boot/syslinux.

The following scripts should also be patched to match the new boot directory:

porteus/make_iso.sh:

Code: Select all

diff -rupN porteus/make_iso.sh.orig porteus/make_iso.sh
--- porteus/make_iso.sh.orig    2014-11-28 00:06:15.791177996 +0100
+++ porteus/make_iso.sh 2014-11-28 00:06:36.847179455 +0100
@@ -27,4 +27,4 @@ fi
 
 mkisofs -o "$ISONAME" -v -l -J -joliet-long -R -D -A "$CDLABEL" \
 -V "$CDLABEL" -no-emul-boot -boot-info-table -boot-load-size 4 \
--b boot/syslinux/isolinux.bin -c boot/syslinux/isolinux.boot ../.
+-b porteus/boot/syslinux/isolinux.bin -c porteus/boot/syslinux/isolinux.boot ../.

installer.com (embedded in /porteus/boot/Porteus-installer-for-Linux.com):

Code: Select all

diff -rupN installer.com.orig installer.com
--- installer.com.orig  2014-11-28 00:10:58.504197588 +0100
+++ installer.com       2014-11-27 23:29:11.052147233 +0100
@@ -46,7 +46,7 @@ echo "$PRT" | grep -q mmcblk && PRTN=`ec
 [ "$PRTN" ] && DEV=`echo $PRT | sed s/$PRTN//` || DEV=$PRT
 MPT=`df -h . | tail -n1 | cut -d% -f2 | cut -d" " -f2-`
 IPT=`pwd`
-PTH=`echo "$IPT" | sed s^"$MPT"^^ | rev | cut -d/ -f2- | rev`
+PTH=`echo "$IPT" | sed s^"$MPT"^^ | rev | cut -d/ -f3- | rev`
 FS=`grep -w $PRT /proc/mounts | head -n1 | cut -d" " -f3`
 bin="$IPT/.porteus_installer"
 extlinux_conf="$IPT/syslinux/porteus.cfg"

Maybe the scripts in /porteus/boot/Porteus-installer-for-Windows.exe should also be patched, but I can't do it, because I don't have a Windows environment. I think it should be simple.

[fanthom]

@francois
will upload new LXQt module tonight for testing. the changes i have made are affecting activation/deactivation of modules (only in LXQt) so would be good if users could play with modules and let me know in case of any system misbehavior.

@dafan
we have dropped 'one folder for everything' idea since we found that UEFI support requires placing additional /EFI directory in the top root of the drive/partition. as far as i know there is no way to workaround that.
that means 64bit 3.1 release will have by default 3 folders:

Code: Select all

/EFI
/boot
/porteus

sorry about that.

[dafan]

@fanthom

I know there will be a UEFI directory (but only in 64bit version). For the people, who do not have or do not want a UEFI booting, this directory can simply be deleted. At least there will be one directory less. For the people who also storage data on a Porteus USB stick, it is really a mix-up to have so many subdirectories.

[fanthom]

you could also mode /porteus directory to /boot and use 'from=boot' cheatcode.
would be much easier then syslinux recompilation (how to produce binary which works for windows?).

[Bogomips]

Now you need to logout and log back in and it works.
Please try for KDE.

KDE AF 32 bit

1. • Code: Select all

     guest@porteus:~$ grep command /var//log/dmesg 
     [    0.000000] Kernel command line: quiet copy2ram ramsize=30% noauto timezone=Europe/London volume=60%
     guest@porteus:~$ grep xzm /var//log/porteus-livedbg 
     /memory/copy2ram/000-kernel.xzm
     /memory/copy2ram/001-core.xzm
     /memory/copy2ram/002-xorg.xzm
     /memory/copy2ram/003-kde.xzm
     /memory/copy2ram/sudo-1.8.9p5-i486-1.xzm
     
     guest@porteus:~$ ls -1 /mnt/live/memory/images/
     000-kernel.xzm/
     001-core.xzm/
     002-xorg.xzm/
     003-kde.xzm/
     Kate_211014.xzm/
     VLC_191014.xzm/
     flashplayer-plugin-11.2.202.411-i386-1alien.xzm/
     gtk-ch_161014.xzm/
     sudo-1.8.9p5-i486-1.xzm/
     
   • ImageMagick 6.8.6

     Code: Select all

     ImM_180914.txt:
     gcc-4.8.2-i486-1.txz
     libmpc-0.8.2-i486-2.txz
     fftw-3.3.3-i486-1.txz
     jasper-1.900.1-i486-3.txz
     openexr-1.7.1-i486-1.txz
     ilmbase-1.0.3-i486-1.txz
     imagemagick-6.8.6_10-i486-1.txz
     lcms2-2.4-i486-1.txz
     

2. As hypothesised, a reset of some sort fixes ImageMagick 6.8.6 display
   • Log OUT/In. However, module defies deactivation, even in Init 3

     Code: Select all

     root@porteus:/home/guest# activate /mnt/sda4/mods/ImM_180914.xzm 
     Updating shared library links:  /sbin/ldconfig
     loop6     7:6    0  35.9M  1 loop /mnt/live/memory/images/VLC_191014.xzm
     loop7     7:7    0    60K  1 loop /mnt/live/memory/images/gtk-ch_161014.xzm
     loop8     7:8    0  16.3M  1 loop /mnt/live/memory/images/Kate_211014.xzm
     loop9     7:9    0  29.6M  1 loop /mnt/live/memory/images/ImM_180914.xzm
     guest@porteus:~$ display
     display: color is not known to server `FOREGROUND': Success @ error/xwindow.c/XGetPixelPacket/3064.
     Log OUT/In
     guest@porteus:~$ display
     guest@porteus:~$ display
     root@porteus:/home/guest# deactivate /mnt/sda4/mods/ImM_180914.xzm 
     ImM_180914.xzm: The module can't be removed, because it's busy (used).
     Init 3
     ImM_180914.xzm: The module can't be removed, because it's busy (used).
     Init 4 (Did not restore windows)
     
   • Init 3/4 has same effect, and display works

     Code: Select all

     guest@porteus:~$ grep xzm /var//log/porteus-livedbg 
     /memory/copy2ram/000-kernel.xzm
     /memory/copy2ram/001-core.xzm
     /memory/copy2ram/002-xorg.xzm
     /memory/copy2ram/003-kde.xzm
     /memory/copy2ram/sudo-1.8.9p5-i486-1.xzm
     
     guest@porteus:~$ ls -1 /mnt/live/memory/images/
     000-kernel.xzm/
     001-core.xzm/
     002-xorg.xzm/
     003-kde.xzm/
     ImM_180914.xzm/
     Kate_211014.xzm/
     sudo-1.8.9p5-i486-1.xzm/
     
     guest@porteus:~$ display
     display: color is not known to server `FOREGROUND': Success @ error/xwindow.c/XGetPixelPacket/3064.
     Init 3/4
     guest@porteus:~$ display
     guest@porteus:~$ display
     root@porteus:/home/guest# deactivate /mnt/sda4/mods/ImM_180914.xzm 
     ImM_180914.xzm: The module can't be removed, because it's busy (used).
     

3. ImageMagick 6.8.9 (Arch). No problem deactivating this module.

   • Code: Select all

     guest@porteus:~$ grep xzm /var//log/porteus-livedbg 
     /memory/copy2ram/000-kernel.xzm
     /memory/copy2ram/001-core.xzm
     /memory/copy2ram/002-xorg.xzm
     /memory/copy2ram/003-kde.xzm
     /memory/copy2ram/sudo-1.8.9p5-i486-1.xzm
     _______________________________________________________________________________
     loop3     7:3    0    66M  0 loop /mnt/live/memory/images/003-kde.xzm
     loop4     7:4    0   528K  0 loop /mnt/live/memory/images/sudo-1.8.9p5-i486-1.xzm
     loop5     7:5    0   5.2M  1 loop /mnt/live/memory/images/ImgMgk_241014.xzm
     guest@porteus:~$ display
     display: color is not known to server `FOREGROUND': Success @ error/xwindow.c/XGetPixelPacket/3040.
     display: color is not known to server `BACKGROUND': Success @ error/xwindow.c/XGetPixelPacket/3052.
     

     Alerts to Exceptions caught at #3040 and #3052.
   • Neither Log Out/In nor Init 3/4 remedies the problem.

     Code: Select all

     Log Out/In
     guest@porteus:~$ display
     display: color is not known to server `FOREGROUND': Success @ error/xwindow.c/XGetPixelPacket/3040.
     display: color is not known to server `BACKGROUND': Success @ error/xwindow.c/XGetPixelPacket/3052.
     Aborted
     root@porteus:/home/guest# deactivate /mnt/sda4/mods/ImgMgk_241014.xzm 
     Updating shared library links:  /sbin/ldconfig
     
     Init 3/4   (Open Windows Restored!)
     root@porteus:/home/guest# activate /mnt/sda4/mods/ImgMgk_241014.xzm 
     Updating shared library links:  /sbin/ldconfig
     loop3     7:3    0    66M  0 loop /mnt/live/memory/images/003-kde.xzm
     loop4     7:4    0   528K  0 loop /mnt/live/memory/images/sudo-1.8.9p5-i486-1.xzm
     loop5     7:5    0   5.2M  1 loop /mnt/live/memory/images/ImgMgk_241014.xzm
     guest@porteus:~$ display
     display: color is not known to server `FOREGROUND': Success @ error/xwindow.c/XGetPixelPacket/3040.
     display: color is not known to server `BACKGROUND': Success @ error/xwindow.c/XGetPixelPacket/3052.
     root@porteus:/home/guest# deactivate /mnt/sda4/mods/ImgMgk_241014.xzm 
     Updating shared library links:  /sbin/ldconfig
     

     LXQT and XFCE, for some reason, do not bring about these exception conditions, and 6.8.9 display runs without a hitch in these DEs.
4. • In mate 32bit fresh mode I loaded only the following modules: fftw, lcms2 and imagemagick

     Code: Select all

     root@porteus:/home/guest# sh p10/Por/xzmod.sh -q p10/Por/ImMagick/IM_271114 . /mnt/sda1/mods    
     Default Module Name: IM_271114.xzm
     
     Installing to Fakeroot Directory
     
     libmpc-0.8.2-i486-2: Multiple Precision Complex Library                  [280K]
     fftw-3.3.3-i486-1: Fastest Fourier Transform in the West                 [14M] 
     jasper-1.900.1-i486-3: free implementation of the JPEG-2000 standard     [510K]
     openexr-1.7.1-i486-1: HDR Image File Format & Library                    [4.1M]
     ilmbase-1.0.3-i486-1: Industrial Light & Magic base libraries            [1000K]
     imagemagick-6.8.6_10-i486-1: a robust collection of image processing too [17M] 
     lcms2-2.4-i486-1: little cms engine, version 2                           [3.1M]
     
     Creating Module IM_271114.xzm
     
     Parallel mksquashfs: Using 1 processor
     Creating 4.0 filesystem on /mnt/sda1/mods/IM_271114.xzm, block size 262144.
     [=========================================================================\] 1738/1738 100%
     
     Exportable Squashfs 4.0 filesystem, xz compressed, data block size 262144
             compressed data, compressed metadata, compressed fragments, compressed xattrs
             duplicates are removed
     Filesystem size 14945.69 Kbytes (14.60 Mbytes)
     
   • 2. I then copied only the file /usr/bin/cpp from the package: gcc-4.8.2-i486-1

        Without gcc, no problem deactivating module.

        Code: Select all

        root@porteus:/home/guest# cp p10/Por/usr/bin/cpp /usr/bin/
        root@porteus:/home/guest# activate /mnt/sda1/mods/IM_271114.xzm
        Updating shared library links:  /sbin/ldconfig
        loop4     7:4    0   528K  0 loop /mnt/live/memory/images/sudo-1.8.9p5-i486-1.xzm
        loop5     7:5    0  16.3M  1 loop /mnt/live/memory/images/Kate_211014.xzm
        loop6     7:6    0  14.6M  1 loop /mnt/live/memory/images/IM_271114.xzm
        guest@porteus:~$ display
        display: color is not known to server `FOREGROUND': Success @ error/xwindow.c/XGetPixelPacket/3064.
        Log OUT/In
        guest@porteus:~$ display
        guest@porteus:~$ display
        root@porteus:/home/guest# deactivate /mnt/sda1/mods/IM_271114.xzm
        Updating shared library links:  /sbin/ldconfig
        loop3     7:3    0    66M  0 loop /mnt/live/memory/images/003-kde.xzm
        loop4     7:4    0   528K  0 loop /mnt/live/memory/images/sudo-1.8.9p5-i486-1.xzm
        loop5     7:5    0  16.3M  1 loop /mnt/live/memory/images/Kate_211014.xzm
        
     3. As with Mate, cpp needed for 1st activate, thereafter can be dispensed with.

        Code: Select all

        root@porteus:/home/guest# rm /usr/bin/cpp
        root@porteus:/home/guest# ls /usr/bin/cpp
        /bin/ls: cannot access /usr/bin/cpp: No such file or directory
        root@porteus:/home/guest# activate /mnt/sda1/mods/IM_271114.xzm
        Updating shared library links:  /sbin/ldconfig
        loop4     7:4    0   528K  0 loop /mnt/live/memory/images/sudo-1.8.9p5-i486-1.xzm
        loop5     7:5    0  16.3M  1 loop /mnt/live/memory/images/Kate_211014.xzm
        loop6     7:6    0  14.6M  1 loop /mnt/live/memory/images/IM_271114.xzm
        guest@porteus:~$ display
        guest@porteus:~$ display
        root@porteus:/home/guest# deactivate /mnt/sda1/mods/IM_271114.xzm
        Updating shared library links:  /sbin/ldconfig
        loop3     7:3    0    66M  0 loop /mnt/live/memory/images/003-kde.xzm
        loop4     7:4    0   528K  0 loop /mnt/live/memory/images/sudo-1.8.9p5-i486-1.xzm
        loop5     7:5    0  16.3M  1 loop /mnt/live/memory/images/Kate_211014.xzm
        

[Ed_P]

LXQt 64-bit GUI mode

I right clicked on the desktop and choose the option to have menu display on future desktop right clicks. Ok, tried it, don't like it, how the heck do I turn it off??