Ignis an alternative Openbox module for Porteus-v4.0rc4 XFCE

New features which should be implemented in Porteus; suggestions are welcome. All questions or problems with testing releases (alpha, beta, or rc) should go in their relevant thread here, rather than the Bug Reports section.
User avatar
Ed_P
Contributor
Contributor
Posts: 5032
Joined: 06 Feb 2013, 22:12
Distribution: 4.0 Cinnamon 64-bit ISO
Location: Western NY, USA

Ignis an alternative Openbox module for Porteus-v4.0rc4 XFCE

Post#16 by Ed_P » 18 Jul 2018, 21:54

fpscan in /usr/local/f-prot/ doesn't do anything for me but fpscan in terminal does. :celebrate3:

Code: Select all

guest@porteus:~$ fpscan

F-PROT Antivirus CLS version 6.7.10.6267, 64bit (built: 2012-03-27T11-39-07)


FRISK Software International (C) Copyright 1989-2011
Engine version:   4.6.5.141
Arguments:        
Virus signatures: 201807171413
                  (/usr/local/f-prot/antivir.def)

Nothing to scan.

Usage:
  fpscan [MEDIA] [OPTIONS] [PATHS]
Options:
:good:

Quick too!! :shock:

Code: Select all

guest@porteus:~$ fpscan --output=/home/guest/logfile.log --report --archive=99 --adware --applications --scanlevel=3 --heurlevel=2 /home/guest

F-PROT Antivirus CLS version 6.7.10.6267, 64bit (built: 2012-03-27T11-39-07)


FRISK Software International (C) Copyright 1989-2011
Engine version:   4.6.5.141
Arguments:        --output=/home/guest/logfile.log --report --archive=99 --adware --applications --scanlevel=3 --heurlevel=2 /home/guest 
Virus signatures: 201807171413
                  (/usr/local/f-prot/antivir.def)

[Not scanning] <Not a regular file or directory>	/home/guest/.cache/keyring-ZNVWLZ/pkcs11
[Not scanning] <Not a regular file or directory>	/home/guest/.cache/keyring-ZNVWLZ/ssh
[Not scanning] <Not a regular file or directory>	/home/guest/.cache/keyring-ZNVWLZ/control
Scanning: -

Results:

Files: 1761
Skipped files: 0
MBR/boot sectors checked: 0
Objects scanned: 2012
Infected objects: 0
Infected files: 0
Files with errors: 1
Disinfected: 0

Running time: 00:02
guest@porteus:~$ 
Thanks evergreen. :friends:
Ed

User avatar
evergreen
Black ninja
Black ninja
Posts: 51
Joined: 27 Mar 2016, 16:58
Distribution: Ignis OS, Porteus x86_64
Location: Argentine, Patagonia
Contact:

Ignis an alternative Openbox module for Porteus-v4.0rc4 XFCE

Post#17 by evergreen » 07 Mar 2019, 16:21

Hello again,

I am pleased to announce that I decided to make a full ISO based on the latest Porteus XFCE updated from here.

Xfce x64 module updated

and now the project is placed in https://projectignis.sourceforge.io

is where it is possible download and where I am going to keep it updated.

Its came with Kernel 4.20.1
Developer modules
and Openbox

So my best and I hope its came a pleasure to the view and handy for the users who are going to use or take a look at Ignis OS.
AMD A8-7410, APU AMD Radeon R5 Graphics M330

neko
DEV Team
DEV Team
Posts: 1507
Joined: 09 Feb 2013, 09:55
Distribution: APorteus-FVWM-ja-x86_64.iso
Location: japan

Ignis an alternative Openbox module for Porteus-v4.0rc4 XFCE

Post#18 by neko » 08 Mar 2019, 09:34

@evergreen
I downloaded your ISO and run it.
It is very cool.

You can change (update) the kernel of your ISO with prototype build kernel.
Recent prototype build kernels are linked here.
Porteus Kernel Builder (Post by neko #52232)

For example, prototype build kernel 5.0 is
64bit-kernel5.0.tar (92 M)
http://www.mediafire.com/file/duihaa6rg ... nel5.0.tar
md5sum: f37ba7229b9b0a9377852f3f900faf1a 64bit-kernel5.0.tar

Code: Select all

% su
# ls
64bit-kernel5.0.tar Ignis_OS-Porteus-07032019-x86_64.iso
# mkdir mnt
# mount -t iso9660 -o loop Ignis_OS-Porteus-07032019-x86_64.iso mnt
# mkdir NEW
# cp -a mnt/* NEW/.
# cp -a /mnt/.[0-9A-Za-z]* NEW/. 2>/dev/null
# umount -f mnt
# rm -fr mnt
#
# xz -dc NEW/boot/syslinux/initrd.xz > tmp
# mkdir initrd
# cd initrd
# cat ../tmp | cpio -i
# cd ../
# rm tmp
edit initrd/init_conf with text editter.

Code: Select all

# ls
64bit-kernel5.0.tar Ignis_OS-Porteus-07032019-x86_64.iso NEW initrd new.init_conf
# diff initrd/init_conf new.init_conf
1c1
< SGN_ID=kernel-v4.20.1-1
---
> SGN_ID=kernel-v5.0-1
# cp new.init_conf initrd/init_conf
# cd initrd
# find | cpio -H newc -o | xz -C crc32 -9 > ../initrd.xz
# cd ..
# mv initrd.xz NEW/boot/syslinux/initrd.xz
# rm -fr initrd new.init_conf
#
# mv NEW/porteus/kernel-v4.20.1-1-x86_64.cfg NEW/porteus/kernel-v5.0-1-x86_64.cfg
#
# tar -xf 64bit-kernel5.0.tar
# mv vmlinuz NEW/boot/syslinux/
# mv 000-kernel.xzm NEW/porteus/base/
# mv 06-crippled_sources-5.0-64bit.xzm NEW/porteus/base/
# rm NEW/porteus/base/06-crippled_sources-4.20.1-64bit.xzm
#
# mkisofs -o NEW.iso -v -l -J -joliet-long  -R -D -A Porteus -V Porteus \
-no-emul-boot -boot-info-table -boot-load-size 4 \
-b boot/syslinux/isolinux.bin -c boot/syslinux/isolinux.boot NEW
# rm -fr NEW
# ls 
64bit-kernel5.0.tar Ignis_OS-Porteus-07032019-x86_64.iso NEW.iso
Thanks.

User avatar
evergreen
Black ninja
Black ninja
Posts: 51
Joined: 27 Mar 2016, 16:58
Distribution: Ignis OS, Porteus x86_64
Location: Argentine, Patagonia
Contact:

Ignis an alternative Openbox module for Porteus-v4.0rc4 XFCE

Post#19 by evergreen » 08 Mar 2019, 15:28

Looking at your explanation step by step I am going to adventure to test it, thank you very much for show me how to update Kernel , Next time I am going to update everything in this way, I am glad that you gave me a good impression .

:beer:
neko wrote:
08 Mar 2019, 09:34
@evergreen
I downloaded your ISO and run it.
It is very cool.

You can change (update) the kernel of your ISO with prototype build kernel.
Recent prototype build kernels are linked here.
Porteus Kernel Builder (Post by neko #52232)

For example, prototype build kernel 5.0 is
64bit-kernel5.0.tar (92 M)
http://www.mediafire.com/file/duihaa6rg ... nel5.0.tar
md5sum: f37ba7229b9b0a9377852f3f900faf1a 64bit-kernel5.0.tar

Code: Select all

% su
# ls
64bit-kernel5.0.tar Ignis_OS-Porteus-07032019-x86_64.iso
# mkdir mnt
# mount -t iso9660 -o loop Ignis_OS-Porteus-07032019-x86_64.iso mnt
# mkdir NEW
# cp -a mnt/* NEW/.
# cp -a /mnt/.[0-9A-Za-z]* NEW/. 2>/dev/null
# umount -f mnt
# rm -fr mnt
#
# xz -dc NEW/boot/syslinux/initrd.xz > tmp
# mkdir initrd
# cd initrd
# cat ../tmp | cpio -i
# cd ../
# rm tmp
edit initrd/init_conf with text editter.

Code: Select all

# ls
64bit-kernel5.0.tar Ignis_OS-Porteus-07032019-x86_64.iso NEW initrd new.init_conf
# diff initrd/init_conf new.init_conf
1c1
< SGN_ID=kernel-v4.20.1-1
---
> SGN_ID=kernel-v5.0-1
# cp new.init_conf initrd/init_conf
# cd initrd
# find | cpio -H newc -o | xz -C crc32 -9 > initrd.xz
# cd ..
# mv initrd.xz NEW/boot/syslinux/initrd.xz
# rm -fr initrd new.init_conf
#
# mv NEW/porteus/kernel-v4.20.1-1-x86_64.cfg NEW/porteus/kernel-v5.0-1-x86_64.cfg
#
# tar -xf 64bit-kernel5.0.tar
# mv vmlinuz NEW/boot/syslinux/
# mv 000-kernel.xzm NEW/porteus/base/
# mv 06-crippled_sources-5.0-64bit.xzm NEW/porteus/base/
# rm NEW/porteus/base/06-crippled_sources-4.20.1-64bit.xzm
#
# mkisofs -o NEW.iso -v -l -J -joliet-long  -R -D -A Porteus -V Porteus \
-no-emul-boot -boot-info-table -boot-load-size 4 \
-b boot/syslinux/isolinux.bin -c boot/syslinux/isolinux.boot NEW
# rm -fr NEW
# ls 
64bit-kernel5.0.tar Ignis_OS-Porteus-07032019-x86_64.iso NEW.iso
Thanks.
AMD A8-7410, APU AMD Radeon R5 Graphics M330

neko
DEV Team
DEV Team
Posts: 1507
Joined: 09 Feb 2013, 09:55
Distribution: APorteus-FVWM-ja-x86_64.iso
Location: japan

Ignis an alternative Openbox module for Porteus-v4.0rc4 XFCE

Post#20 by neko » 08 Mar 2019, 15:55

@evergreen
I had a mistake in the article. (It was already corrected)

[NG]
# find | cpio -H newc -o | xz -C crc32 -9 > initrd.xz
[OK]
# find | cpio -H newc -o | xz -C crc32 -9 > ../initrd.xz

Thanks.

raja
Shogun
Shogun
Posts: 213
Joined: 02 May 2017, 09:51
Distribution: v3.2.2-32 and v5.0-rc1-zstd-64
Location: Chennai,India

Ignis an alternative Openbox module for Porteus-v4.0rc4 XFCE

Post#21 by raja » 11 Mar 2019, 08:58

Evergreen..

Booted your ISO y´day. Runs very well . Looks impressive. :D

Once set, orage is showing local time, but clock in the panel does not get updated. Shows UTC time and I will have to copy the zoneinfo to /etc/localtime.. If saved, during next restart, local time becomes UTC time? I see this behavior in other porteus too. No problem in Nemisis,Ubuntu etc.
Linux Kernel-4.4.120-32 bit; Linux kernel-5.2-64 bit.

User avatar
evergreen
Black ninja
Black ninja
Posts: 51
Joined: 27 Mar 2016, 16:58
Distribution: Ignis OS, Porteus x86_64
Location: Argentine, Patagonia
Contact:

Ignis an alternative Openbox module for Porteus-v4.0rc4 XFCE

Post#22 by evergreen » 11 Mar 2019, 15:48

Hello @raja
its because mainly with my .ISO I kept as much as possible the Porteus integrity but I am thinking about that to modify it with a good solution to the next release... but is better be pattient every year we have an Update for Porteus so after that we can see what is change with the main system.

Thanks for testing and the observation.
AMD A8-7410, APU AMD Radeon R5 Graphics M330

User avatar
evergreen
Black ninja
Black ninja
Posts: 51
Joined: 27 Mar 2016, 16:58
Distribution: Ignis OS, Porteus x86_64
Location: Argentine, Patagonia
Contact:

Ignis an alternative Openbox module for Porteus-v4.0rc4 XFCE

Post#23 by evergreen » 09 Apr 2019, 18:40

Hello,

I am pleased to release Ignis OS 09042019 that still improving and getting more like an exciting project, there is some changes,

Download here: https://projectignis.sourceforge.io

I dropped Firefox cause the newest stable version Firefox 66 required the glibc upgrade. since Opera is sold to a Chinese Company I have dropped it as well, Vivaldi is trying to keep the philosophy that was lost from Opera, the ex opera CEO who returns from the past to make reality Vivaldi Browser. in any case always is there the Browser Tool and Setup to find your favorite browser .

Changes for Ignis OS 09042019:
-xcompmgr was replaced with compton
-Firefox was replaced with Vivaldi
-xscreensaver was removed
-i3lock was added
-Timeset tools was added in the Openbox System tool menu
-Many modules have been Upgraded
-Some settings fixed, battery low notification was removed from tint2, cause it is annoying with PC Desktop
-If notebook lid is close the screen will be blocked automatically.

Thanks @neko I have applied the newest kernel version 5.0.7
@raja there is a new tool that I have added to handle the Timezones. I hope it is fine for now ;)

Thanks everyone.
AMD A8-7410, APU AMD Radeon R5 Graphics M330

raja
Shogun
Shogun
Posts: 213
Joined: 02 May 2017, 09:51
Distribution: v3.2.2-32 and v5.0-rc1-zstd-64
Location: Chennai,India

Ignis an alternative Openbox module for Porteus-v4.0rc4 XFCE

Post#24 by raja » 12 Apr 2019, 19:36

Booted ISO. Looks okay.

Takes 20 seconds to Desktop. May be I will remove some packages to cut down time and memory use.

Yours is the first build where I could connect to my Phone via Bluetooth and transfer files. Blueman and Bluez packages alone not enough for Porteus-4.0.

Since you have included many packages/scripts, "dmesg" shows lots of REISERFS errors.

Code: Select all

4.369846] REISERFS warning (device loop20): sh-2006 read_super_block: bread failed (dev loop20, block 16, size 4096)
[    4.692036] REISERFS warning (device loop23): sh-2006 read_super_block: bread failed (dev loop23, block 16, size 4096)
[    4.987070] REISERFS warning (device loop26): sh-2006 read_super_block: bread failed (dev loop26, block 16, size 4096)
[    5.084062] REISERFS warning (device loop27): sh-2006 read_super_block: bread failed (dev loop27, block 16, size 4096)
[    5.184138] REISERFS warning (device loop28): sh-2006 read_super_block: bread failed (dev loop28, block 16, size 4096)
[    5.491056] REISERFS warning (device loop31): sh-2006 read_super_block: bread failed (dev loop31, block 16, size 4096)
[    6.135021] REISERFS warning (device loop37): sh-2006 read_super_block: bread failed (dev loop37, block 16, size 4096)
[    6.573915] REISERFS warning (device loop41): sh-2006 read_super_block: bread failed (dev loop41, block 16, size 4096)
[    7.866776] REISERFS warning (device loop53): sh-2006 read_super_block: bread failed (dev loop53, block 2, size 4096)
[    7.866784] REISERFS warning (device loop53): sh-2006 read_super_block: bread failed (dev loop53, block 16, size 4096)
[    8.087845] REISERFS warning (device loop55): sh-2006 read_super_block: bread failed (dev loop55, block 2, size 4096)
[    8.087852] REISERFS warning (device loop55): sh-2006 read_super_block: bread failed (dev loop55, block 16, size 4096)
When you activate new xzm modules, application is not listed in menu, however program runs through 'run'.

Since Windows 10 sets local time and Linux sets UTC time, there will be a problem while switching. I leave UTC time without setting zone, as it matches local time or in some builds, I copy zone information to /etc. I even tried ntp.

With 3 /4 tabs in Browser, memory use touches nearly 2MB. My system got only 4MB stick.

But, build is stable and runs smoothly.

I need a help which I was asking neko a couple of times. Since you too are using neko's initrd, systemd, tell me where is the reference to FOLDER an variable listed in regular porteus in "linuxrc" file.

Both grub and syslinux can not find cfg file in porteus folder if you store porteus direcory in say ignis. "from" cheatcode not used in grub. "from=/mnt/sdax/ignis/porteus" fails to boot, if set in cfg file..

In regular porteus distribution, I edit linuxrc file ""FOLDER=/porteus-4.0/porteus and they boot without any problem. In one partition I have 6 distributions, with different directory names and they all boot.

I face problem with yours and nekos. I added a line FOLDER =*** to init_conf file, before sgn line. No use. Should I do somewhere in /lib64/systemd/systemd?
PleaseClarify. Thanks
Linux Kernel-4.4.120-32 bit; Linux kernel-5.2-64 bit.

User avatar
evergreen
Black ninja
Black ninja
Posts: 51
Joined: 27 Mar 2016, 16:58
Distribution: Ignis OS, Porteus x86_64
Location: Argentine, Patagonia
Contact:

Ignis an alternative Openbox module for Porteus-v4.0rc4 XFCE

Post#25 by evergreen » 13 Apr 2019, 02:56

raja wrote:
12 Apr 2019, 19:36
Booted ISO. Looks okay.
Takes 20 seconds to Desktop. May be I will remove some packages to cut down time and memory use.
For sure, everything inside Modules are extras, if you try an Always fresh boot it became a fresh Porteus 4.0 with a Kernel 5.0.7 without Modules, BTW Kernel-firmware is there to support extra firmware that help in some certain circumstances, so you could remove it without problem
Yours is the first build where I could connect to my Phone via Bluetooth and transfer files. Blueman and Bluez packages alone not enough for Porteus-4.0.
Probably Porteus developers didn't consider to add Blueman to keep a very small ISO, but it is not our case :D

Since you have included many packages/scripts, "dmesg" shows lots of REISERFS errors.

Code: Select all

4.369846] REISERFS warning (device loop20): sh-2006 read_super_block: bread failed (dev loop20, block 16, size 4096)
[    4.692036] REISERFS warning (device loop23): sh-2006 read_super_block: bread failed (dev loop23, block 16, size 4096)
[    4.987070] REISERFS warning (device loop26): sh-2006 read_super_block: bread failed (dev loop26, block 16, size 4096)
[    5.084062] REISERFS warning (device loop27): sh-2006 read_super_block: bread failed (dev loop27, block 16, size 4096)
[    5.184138] REISERFS warning (device loop28): sh-2006 read_super_block: bread failed (dev loop28, block 16, size 4096)
[    5.491056] REISERFS warning (device loop31): sh-2006 read_super_block: bread failed (dev loop31, block 16, size 4096)
[    6.135021] REISERFS warning (device loop37): sh-2006 read_super_block: bread failed (dev loop37, block 16, size 4096)
[    6.573915] REISERFS warning (device loop41): sh-2006 read_super_block: bread failed (dev loop41, block 16, size 4096)
[    7.866776] REISERFS warning (device loop53): sh-2006 read_super_block: bread failed (dev loop53, block 2, size 4096)
[    7.866784] REISERFS warning (device loop53): sh-2006 read_super_block: bread failed (dev loop53, block 16, size 4096)
[    8.087845] REISERFS warning (device loop55): sh-2006 read_super_block: bread failed (dev loop55, block 2, size 4096)
[    8.087852] REISERFS warning (device loop55): sh-2006 read_super_block: bread failed (dev loop55, block 16, size 4096)
I am not sure about it, but looks like something fail with the hard-drive that have a reiserfs, maybe you could try to open and Terminal,

Code: Select all

su
type your password, then
umount /dev/sdaX
reiserfsck --check /dev/sdaX
check whats display , then
reiserfsck --fix-fixable /dev/sdaX
X is the partition number
But I am certainly it is not cause of the O.S , maybe is your filesystem
When you activate new xzm modules, application is not listed in menu, however program runs through 'run'.
For some reason its not listening immediately to menu , my theory is because openbox menu is loading an old xml generated file, anyway you can , open Run 'it is going to open xfce4-appfinder and every new loaded module is going to be there'
Since Windows 10 sets local time and Linux sets UTC time, there will be a problem while switching. I leave UTC time without setting zone, as it matches local time or in some builds, I copy zone information to /etc. I even tried ntp.
Well done, and glad that you find a solution.
With 3 /4 tabs in Browser, memory use touches nearly 2MB. My system got only 4MB stick.
I am not sure about what you mean. but i have 7 tabs opened and it is taking 1.27GB of space in my memory with another stuff opened, in any case you should use your favorite browser, the one included in modules is to have a browser out of the box and something that I considered that deserve to take a look.
But, build is stable and runs smoothly.
Thanks :D :beer: I wish its a good experience with Openbox
I need a help which I was asking neko a couple of times. Since you too are using neko's initrd, systemd, tell me where is the reference to FOLDER an variable listed in regular porteus in "linuxrc" file.
Its listed to porteus as always I just added SGN_ID=kernel-v5.0.7-1 in my initrd/init_conf to load kernel-v5.0.7-1-x86_64.cfg, everything still default as neko build Kernel 5.0.7
Both grub and syslinux can not find cfg file in porteus folder if you store porteus direcory in say ignis. "from" cheatcode not used in grub. "from=/mnt/sdax/ignis/porteus" fails to boot, if set in cfg file..
Really you dont need to load porteus.cfg for excample this is my grub setting to load my O.S

Code: Select all

set root='(hd0,X)'
linux   /boot/syslinux/vmlinuz initrd=/boot/syslinux/initrd.xz changes=/porteus
initrd  /boot/syslinux/initrd.xz
When X is the partition number

In regular porteus distribution, I edit linuxrc file ""FOLDER=/porteus-4.0/porteus and they boot without any problem. In one partition I have 6 distributions, with different directory names and they all boot.

I face problem with yours and nekos. I added a line FOLDER =*** to init_conf file, before sgn line. No use. Should I do somewhere in /lib64/systemd/systemd?
PleaseClarify. Thanks
AMD A8-7410, APU AMD Radeon R5 Graphics M330

raja
Shogun
Shogun
Posts: 213
Joined: 02 May 2017, 09:51
Distribution: v3.2.2-32 and v5.0-rc1-zstd-64
Location: Chennai,India

Ignis an alternative Openbox module for Porteus-v4.0rc4 XFCE

Post#26 by raja » 13 Apr 2019, 10:41

In original Porteus, variables are declared like this in ¨inuxrc"file in ïnitrd.xz.

Code: Select all

# Variables:
i=`echo "[1;33m""^ ""[0m"`
m=`echo "[1;33m""->""[0m"`
arch=`uname -m`; [ $arch = x86_64 ] || arch=i586
DELAY=`value delay`; [ $DELAY ] && { echo $i"delaying $DELAY sec (waiting for slow devices to settle up)"; sleep $DELAY; }
CFG=`value cfgfile`; [ $CFG ] || CFG=porteus-v4.0-$arch.cfg
FROM=`value from`; ISO=`echo $FROM | egrep ".*\.iso( |\$)"`
IP=`value ip | cut -d: -f2`
MOPT=`value mopt`; [ $MOPT ] || MOPT="noatime,nodiratime,suid,dev,exec,async"
CHANGES=`value changes`
RAMSIZE=`value ramsize`; [ $RAMSIZE ] || RAMSIZE=60%
LOAD=`value load | sed 's/;/|/g'`; [ $LOAD ] || LOAD=._null
NOLOAD=`value noload | sed 's/;/|/g'`; [ $NOLOAD ] || NOLOAD=._null
EXTRAMOD=`value extramod | sed 's/;/ /g'`
RAMMOD=`value rammod | sed 's/;/|/g'`
ROOTCOPY=`value rootcopy`
FOLDER=porteus
livedbg=/var/log/livedbg
LOGFILE=/var/log/boot.log
init does look for cfg file. on start.

Code: Select all

param() {
if [ -e $CFGDEV/$FOLDER/$CFG ]; then
	egrep -qo "^${1}$" $CFGDEV/[b]$FOLDER/$CFG[/b] || egrep -qo " $1( |\$)" /proc/cmdline
		else
	egrep -qo " $1( |\$)" /proc/cmdline
fi
}
So, during init, FOLDER porteus is searched in all mounted devices. Then looks for the sgn or cfg file in the directory porteus.

Boot process initiated, when sgn or cfg file matches with what is given in the initrd.xz. If you have Flash drive and say, three partitions in HDD, you can have 4 different Porteus versions, and init can search and find the right place.

But, if I want to have different porteus versions in same partition, under different directory names, you need to declare that variables in linuxrc file.

neko/yours- initrd.xz does not have that declarations,in linuxrc file, but, obviouly is referred to somewhere.

My query is "where is that?

Booting is not at all a problem if directory name is porteus.. Hope I am clear. I could not convey this to neko and face same problem with you also.
Linux Kernel-4.4.120-32 bit; Linux kernel-5.2-64 bit.

User avatar
evergreen
Black ninja
Black ninja
Posts: 51
Joined: 27 Mar 2016, 16:58
Distribution: Ignis OS, Porteus x86_64
Location: Argentine, Patagonia
Contact:

Ignis an alternative Openbox module for Porteus-v4.0rc4 XFCE

Post#27 by evergreen » 13 Apr 2019, 18:08

Hello again,

Under the circumstances is logic that to you is better to get back the original old Porteus Kernel
you should have the current official Porteus ISO x86_64
Take from there the '/porteus/base' folder, and '/boot' folder to replace the one in your Ignis installation and Ualá.

Remember that even modules are independents, so you could play with them and have a singular Porteus installation, you dont need to have 3 Porteus Installation honestly , I am sharing what I got with my Porteus installation and my knowledge and probably making a small contribution for Openbox users that needs something extended, so far Ignis is a cutomizacion that fit with Rescue, developers and multimedia O.S that could be extended by Modules.
raja wrote:
13 Apr 2019, 10:41
In original Porteus, variables are declared like this in ¨inuxrc"file in ïnitrd.xz.

Code: Select all

# Variables:
i=`echo "[1;33m""^ ""[0m"`
m=`echo "[1;33m""->""[0m"`
arch=`uname -m`; [ $arch = x86_64 ] || arch=i586
DELAY=`value delay`; [ $DELAY ] && { echo $i"delaying $DELAY sec (waiting for slow devices to settle up)"; sleep $DELAY; }
CFG=`value cfgfile`; [ $CFG ] || CFG=porteus-v4.0-$arch.cfg
FROM=`value from`; ISO=`echo $FROM | egrep ".*\.iso( |\$)"`
IP=`value ip | cut -d: -f2`
MOPT=`value mopt`; [ $MOPT ] || MOPT="noatime,nodiratime,suid,dev,exec,async"
CHANGES=`value changes`
RAMSIZE=`value ramsize`; [ $RAMSIZE ] || RAMSIZE=60%
LOAD=`value load | sed 's/;/|/g'`; [ $LOAD ] || LOAD=._null
NOLOAD=`value noload | sed 's/;/|/g'`; [ $NOLOAD ] || NOLOAD=._null
EXTRAMOD=`value extramod | sed 's/;/ /g'`
RAMMOD=`value rammod | sed 's/;/|/g'`
ROOTCOPY=`value rootcopy`
FOLDER=porteus
livedbg=/var/log/livedbg
LOGFILE=/var/log/boot.log
init does look for cfg file. on start.

Code: Select all

param() {
if [ -e $CFGDEV/$FOLDER/$CFG ]; then
	egrep -qo "^${1}$" $CFGDEV/[b]$FOLDER/$CFG[/b] || egrep -qo " $1( |\$)" /proc/cmdline
		else
	egrep -qo " $1( |\$)" /proc/cmdline
fi
}
So, during init, FOLDER porteus is searched in all mounted devices. Then looks for the sgn or cfg file in the directory porteus.

Boot process initiated, when sgn or cfg file matches with what is given in the initrd.xz. If you have Flash drive and say, three partitions in HDD, you can have 4 different Porteus versions, and init can search and find the right place.

But, if I want to have different porteus versions in same partition, under different directory names, you need to declare that variables in linuxrc file.

neko/yours- initrd.xz does not have that declarations,in linuxrc file, but, obviouly is referred to somewhere.

My query is "where is that?

Booting is not at all a problem if directory name is porteus.. Hope I am clear. I could not convey this to neko and face same problem with you also.
AMD A8-7410, APU AMD Radeon R5 Graphics M330

User avatar
francois
Contributor
Contributor
Posts: 5649
Joined: 28 Dec 2010, 14:25
Distribution: xfce plank porteus nemesis
Location: Le printemps, le printemps, le printemps... ... l'hiver s'essoufle.

Ignis an alternative Openbox module for Porteus-v4.0rc4 XFCE

Post#28 by francois » 14 Apr 2019, 11:47

Hello evergreen. Any pictures to add to the first post so that the user sees what he gets as improved experience. Or otherwise, what are these improvements over xfce alone?
Thanks.
Prendre son temps, profiter de celui qui passe.

User avatar
evergreen
Black ninja
Black ninja
Posts: 51
Joined: 27 Mar 2016, 16:58
Distribution: Ignis OS, Porteus x86_64
Location: Argentine, Patagonia
Contact:

Ignis an alternative Openbox module for Porteus-v4.0rc4 XFCE

Post#29 by evergreen » 14 Apr 2019, 18:50

Hello francois

Just try to have conky, blueman, pasystray, xfce4-clipman and compton in a fresh xfce you will realize that your memory start to grow up at least to 682MB
when I do the same with the xfce services+Openbox in the background it keeps 603MB from your memory with an elegant desktop full featured to manage with a keyboard for example , is like have the best things from both DE, xfce always will be my favorite but Openbox let me add extra customization with a low cost.. lets check out my fat Openbox before ask, honestly my intentions are keeps a K.I.S.S O.S out of the box to everything with access to your hardware and fancy stuff.

Thanks for asking , there is some pictures that I added in https://projectignis.sourceforge.io you are welcome to come in, probably you will see that there is a huge memory usage that is displayed with conky, but I was executing some software in the background. :beer:
francois wrote:
14 Apr 2019, 11:47
Hello evergreen. Any pictures to add to the first post so that the user sees what he gets as improved experience. Or otherwise, what are these improvements over xfce alone?
Thanks.
AMD A8-7410, APU AMD Radeon R5 Graphics M330

User avatar
francois
Contributor
Contributor
Posts: 5649
Joined: 28 Dec 2010, 14:25
Distribution: xfce plank porteus nemesis
Location: Le printemps, le printemps, le printemps... ... l'hiver s'essoufle.

Ignis an alternative Openbox module for Porteus-v4.0rc4 XFCE

Post#30 by francois » 16 Apr 2019, 08:14

If you add those pictures in the first post of this thread you will be more convincing. :happy62:
Prendre son temps, profiter de celui qui passe.

Post Reply