PorteuX 0.7 has been released

[porteux]

You can give it a try.

[Rava]

You can give it a try.

(I presume you have replying to me)

If I knew how to make that, I would.
(For Palemoon, and for Basilisk)

(I asked the maintainer of Basilisk via the palmoon forum how to make this, and awaiting his (or her?) reply.)

[porteux]

@Rava, you can try this Nvidia driver (no guarantees): https://www.mediafire.com/file/cuo42160 ... x86_64.xzm

[Rava]

@Rava, you can try this Nvidia driver (no guarantees): https://www.mediafire.com/file/cuo42160 ... x86_64.xzm

Thanks, I try it and report back.

Added in 10 minutes 17 seconds:
downloaded; 83894272 bytes, md5sum: 1d83c38a830946ee89917ccff1be9841

[Rapha_]

In last PorteuX * , the module selection tool doesn't let you find an optional module folder , with the + sign

Especially useful for those who boot a PorteuX or Porteus with an ISO ...

Wouldn't be easier to just browse the folder with the modules and activating the ones you want?

Not really... As 'Guest', if I open the 'optional' folder, I have to type in the root password every time when I want to activate a module: This is very constraining.
And I want to stay as 'guest' in my current use of Porteu(x)s


In any case I can manage by doing this :

As the script lsmodules, to activate (or deactivate) the modules was missing, I copied it from another desktop to the appropriate rootcopy folder :
/porteus/rootcopy_xfce_new/usr/bin/

I created a laucher Activated modules.desktop to be able to click it from the Desktop :

Code: Select all

[Desktop Entry]
Version=1.0
Type=Application
Name=Activated modules
Comment=
Exec=psu /usr/bin/lsmodules
Icon=dialog-ok-apply
Path=
Terminal=false
StartupNotify=false
Name[en_US.UTF-8]=Activated modules

So I copied it in a rootcopy folder:
/porteus/rootcopy_xfce_new/home/guest/Desktop/

( Xfce 4.12 for Porteus RC3 (Post by Rapha_ #85462) )

I s there a project to add a cheatcode like 'extramod=' for optional modules ?

Yes, extramod is supported. For more information about all the cheatcodes available, take a look at /boot/docs/cheatcodes.txt

I should have said cheatcode like 'extraoptional='

[Ed_P]

In last PorteuX * , the module selection tool doesn't let you find an optional module folder , with the + sign

In Porteus 5.0 the extramod= cheatcode supports multiple folders by using a ; between them.

Code: Select all

set bootparms="volume=33 reboot=cold extramod=$linux_folder/Modules;$linux_folder/testModules changes=EXIT:$linux_folder/changes/50save.dat noload=kde;jinn;lxqt;xfce;lxde;mate;open;mychanges;menu1" 

Try that approach with PorteuX.

[Rava]

Code: Select all

set bootparms="volume=33 reboot=cold extramod=$linux_folder/Modules;$linux_folder/testModules changes=EXIT:$linux_folder/changes/50save.dat noload=kde;jinn;lxqt;xfce;lxde;mate;open;mychanges;menu1" 

Where does it get $linux_folder from?

[Ed_P]

Where does it get $linux_folder from?

From the top of the grub2 cfg where I set it for the 4 menuentries. I have 4 menus set up for my Porteus ISO boots; 1 with the changes=EXIT and extramod= cheatcodes, 3 without the changes=EXIT cheatcode of which 2 include the extramod= cheatcode and 1 of those includes the noload= cheatcode to exclude my mychanges module. The last menu boots only the ISO file of which it is only the official system ISO or an official ISO with official updates or Blaze kernel updates which is my Always Fresh mode.

Basically: full function, safe mode, safe mode without my changes, always fresh mode.

Added in 4 hours 8 minutes :
I use to do the same with PorteuX but I lost everything related to PorteuX when I had the harddrive files erased a month or so ago. I even had a working Cinnamon DE with it.

[Rava]

Now that I want to incorporate this

@Rava, you can try this Nvidia driver (no guarantees): https://www.mediafire.com/file/cuo42160 ... x86_64.xzm

I realized dum dum me misplaced the USB thumbdrive I used for Porteux.

I want a USB thumbdrive for a BIOS PC.

The only other USB thumbdrive with the free space has Porteus on it, and I want to keep that Porteus on it as a backup bootable solution (and upgrade it to 5.01 when I am at it)

Therefore the question @porteux:
When I rename the porteux kernel and initrd giving them unique names, it should be possible to use the same porteus.cfg from that USB thumbdrive, and either boot into Porteux 0.7 or into Porteus 5.01 using different kernels and different initrd's for both? Since Porteus has its files in porteus/ and Porteux has its files in porteux/

[porteux]

@Rava, you can't, sorry.

[Rava]

@Rava, you can't, sorry.

Why not?
What matters is what initrd and kernel are booted, or not? And the kernel will load whatever it wants.
Why does the bootloader matter?

Added in 6 minutes :
Good news is: I just found the missing USB thumbdrive, so I can copy the NV driver onto it and I am all set.

(I still should update the other one to Port 5.01)

[rych]

you can't, sorry

"Yes, we can" for example, How to create a Multi-Porteus Boot USB flash drive? (Post by rych #96584)

[Rava]

"Yes, we can" for example, How to create a Multi-Porteus Boot USB flash drive? (Post by rych #96584)

I try your approach using a 8 GB USB thumbdrive.
Do you use unique UUIDs for booting the different Porteus or Porteux versions?

[rych]

Do you use unique UUIDs for booting the different Porteus or Porteux versions?

No need for that: both /porteus and /porteux folders are discovered automatically on whatever partition you put it

[Rava]

Do you use unique UUIDs for booting the different Porteus or Porteux versions?

No need for that: both /porteus and /porteux folders are discovered automatically on whatever partition you put it

Even when you have several USB thumbdrives plugged in at boot time, say sdb and sdc, and you boot from sdc - or want to boot from there since the kernel thinks the /porteux folder on sdb is the correct one to load?