PorteuX 2.6 has been released

[Ed_P]

So terribly sorry that I haven't already done it in my previous post,

Not a problem. So all the PorteuX boot parms are what's in the porteus.cfg file in the iso. It's too bad Ventoy doesn't support adding boot parms to the menu.

With the iso files all on the USB drive you could run the /boot/PorteuX_Install app on the USB drive and boot it directly. The machine's boot menu might even show both Ventoy and PorteuX as boot options. Worth a shot.

[jk9]

... you could run the /boot/PorteuX_Install app on the USB drive and boot it directly.

Yes, I know but I'm not gonna use the whole USB drive for the sole purpose of booting one operating system.
In fact, ventoy.json isn't necessary at all in this particular case. I could just edit /boot/syslinux/porteux.cfg and boot the iso from Ventoy's menu.
But then again, still trying to figure out why it doesn't work without copying the contents of the iso file to the root of the USB drive.

Update:
Needless to copy the entire contents of the iso file to the USB drive. The porteux folder is enough but has to be placed on the root of the USB drive.

[Ed_P]

Yes, I know but I'm not gonna use the whole USB drive for the sole purpose of booting one operating system.

Not disagreeing but also not saying doing the porteus install would delete the ventoy install. They would both be there.

But then again, still trying to figure out why it doesn't work without copying the contents of the iso file to the root of the USB drive.

Edit the iso's /boot/syslinux/porteux.cfg file's APPEND line add remove the changes=EXIT:/porteux parm.

[jk9]

Alrighty, I think I got it.

The ventoy.json file remains the same:

Code: Select all

{
     "theme": {
          "display_mode": "CLI"

    },


     "control": [
          { "VTOY_MENU_TIMEOUT": "2" },
          { "VTOY_DEFAULT_IMAGE": "/porteux2.6.iso" },
          { "VTOY_WIN11_BYPASS_CHECK": "1" }

    ],

    "conf_replace": [
        {
            "iso": "/porteux2.6.iso",
            "org": "/boot/syslinux/porteux.cfg",
           "new": "/ventoy/porteux.cfg"
        }

    ]
} 

The original PorteuX iso file is copied to the root of the USB drive.
The APPEND line in porteux.cfg placed in the ventoy folder next to the ventoy.json is to be edited this way:

Code: Select all

APPEND changes=EXIT:/extras/save.dat changes-ro nobluetooth from=/mnt/sda1/porteux2.6.iso extramod=/extras/modules 

[Ed_P]

Certainly an interesting approach, where did you find it?

Note; the save.dat is only available after you have booted porteux and created it. So the initial boot needs the changes= parm dropped.

I would also drop the change-ro and nobluetooth parms until proven you need them. If Ventoy knows where the iso is I'm not sure you need the from= parm also unless you want to boot an iso on a drive different than the Ventoy USB drive. Obviously the extramod= folder must exist on the Ventoy drive. If you have multiple systems on the Ventoy drive having the extra mods in a directory named /porteux/extras/modules would seem to be more appropriate.

Please keep us informed how this approach works for you jk9.

[jk9]

... where did you find it?

Common sense really ...

I'm not sure you need the from= parm also unless you want to boot an iso on a drive different than the Ventoy USB drive

That was the trouble actually, as Ventoy wouldn't find the porteux folder to boot from unless it's on the root of the USB Drive, which defeats my purpose.

Yes, apart from the from=/mnt/sda1/porteux2.6.iso, all other parameters are added gradually after booting and setting up the untouched original PorteuX iso file the way that suits me best. The changes-ro parameter is the last one added to the APPEND line.
Yes, extramod folder as well as save.dat are on the Ventoy USB drive.

[porteux]

@jk9, this may help: https://github.com/ventoy/Ventoy/issues ... 2505005578

[jk9]

@jk9, this may help: https://github.com/ventoy/Ventoy/issues ... 2505005578

I had already seen that.
I don't know but I find it quite satisfactory the way I'm doing it for the time being. Nevertheless, more options are always welcome.

[Ed_P]

The APPEND line in porteux.cfg placed in the ventoy folder next to the ventoy.json

Just so I, a non-Ventoy user, understand, there is a ventoy folder and in it you place a modified porteus.cfg file. Not just the APPEND line.

[jk9]

Just so I, a non-Ventoy user, understand, there is a ventoy folder and in it you place a modified porteus.cfg file. Not just the APPEND line.

That's it. There a folder named ventoy containing ventoy.json and porteux.cfg. This leaves the original PorteuX iso file untouched.

[Ed_P]

That's it. There a folder named ventoy containing ventoy.json and porteux.cfg. This leaves the original PorteuX iso file untouched.

Thank you.

[jk9]

For more convenience, let's use UUID instead of sda1

Code: Select all

APPEND changes=UUID:4E21-0000/extras/save.dat changes-ro nobluetooth from=UUID:4E21-0000/porteux2.6.iso extramod=UUID:4E21-0000/extras/modules 

[Ed_P]

Definitely more specific, and more accurate with USB installs, especially with multiple installs on the same system.

[nanZor]

Cinnamon Network Manager Wifi issue in 2.6 ?

This may not be an issue because I'm not too familiar with Cinnamon - but I noticed that when I clicked the wifi icon to pick up my home router, instead of asking me for a password, it immediately throws "activation of network failed" notice.

I can go into the Network Settings, and enter my password there and all is good from there on, so no worries.

But should I be expecting a popup asking for password when I'm connecting to a system for the first time?

[porteux]

@nanZor, thanks for reporting this issue.

It's already fixed for the next release.

In the meantime you can download and activate gnome-keyring.