When will Porteus 5 be released ?

[alubypass]

After the release of the latest stable version of Slackware, there should be a new stable version of Porteus 5 soon. Is it already known when this will be released ?

[Ed_P]

Unfortunately, no. But hopefully soon. It's being worked on.

[echologis]

Until than...a very good porteus derivative https://www.mediafire.com/file/bsma64ps ... t.zip/file
with functional save changes module https://www.youtube.com/watch?v=5hNBOCEoCwA
( in porteus 5 save changes module give a write error )

[Ed_P]

I use a save changes file in Porteus 5.0rc3 with no write errors. Can you provide more details?

[echologis]

In Porteus 5.0rc3 save session to module a write error appear ( wherever destination you choose ) but in Porteus 4 is working
( save session to changesxmodule.xzm and copy to modulesfolder is much faster for running the os than save session to dat file )

[Karmi]

Unfortunately, no. But hopefully soon. It's being worked on.

Thought I read someone saying around 'the end of this month' - as in around today.

[spa_time]

Hello...Porteus Nemesis or Portix is nice work...But it help us if save changes menu to file or module like in Porteus 4 is available

[glestwid]

Hi,

Looked at the updated ISO for XFCE at http://ftp.vim.org/ftp/os/Linux/distr/p ... teus-v5.0/ and found all XZM files in this ISO are dated with 2020. Also these files differ from the ones located at http://ftp.vim.org/ftp/os/Linux/distr/p ... .0/kernel/. Where could I get the freshmost ISO for the final release of v5?

[ncmprhnsbl]

Looked at the updated ISO for XFCE at http://ftp.vim.org/ftp/os/Linux/distr/p ... teus-v5.0/ and found all XZM files in this ISO are dated with 2020. Also these files differ from the ones located at http://ftp.vim.org/ftp/os/Linux/distr/p ... .0/kernel/. Where could I get the freshmost ISO for the final release of v5?

how did you determine the 2020 date of the xzms? i don't think there was any i586 isos made in 2020.. did you check the iso checksum?
in any case, if there is some issue with that mirror, try one of the other ones: http://porteus.org/porteus-mirrors.html

[Ed_P]

how did you determine the 2020 date of the xzms?

ls -l works.

Code: Select all

guest@porteus:/mnt/live/mnt/isoloop/porteus/base$ ls -l
total 305420
-rw-r--r-- 1 root root  55058432 Apr 29  2018 000-kernel.xzm
-rw-r--r-- 1 root root 111321088 Apr 29  2018 001-core.xzm
-rw-r--r-- 1 root root  95227904 Apr 29  2018 002-xorg.xzm
-rw-r--r-- 1 root root  51142656 Apr 29  2018 003-cinnamon.xzm
guest@porteus:/mnt/live/mnt/isoloop/porteus/base$

From a Porteus 4.0 ISO I have.

[glestwid]

how did you determine the 2020 date of the xzms?

My bad, it was a result of mounting another ISO. But I found another issue with all these ISOs - they contain truncated file boot\syslinux\vesamenu.c32 which led to broken boot process. As soon as I replace this file with the one from Porteus 4.0 it started working.

[Ed_P]

all these ISOs - they contain truncated file boot\syslinux\vesamenu.c32 which led to broken boot process. As soon as I replace this file with the one from Porteus 4.0 it started working.

An excellent catch glestwid. The small one is from the EFI\boot\ directory.

[ncmprhnsbl]

But I found another issue with all these ISOs - they contain truncated file boot\syslinux\vesamenu.c32 which led to broken boot process. As soon as I replace this file with the one from Porteus 4.0 it started working.

nope, boot\syslinux\vesamenu.c32 is not truncated, it's a dynamically linked file(hence smaller), linked, i guess to libcom32.c32 or libutil.c32 or both..
what i suspect you're encountering is an old ldlinux.sys file from a 4.0 install..that's trying to use the old style(static?) vesamenu.c32
to fix:
1. remove the old ldlinux.sys(on posix, you'll need to `chattr -i` first, because it's set to immutable)
2. rerun Porteus-installer-for-Linux.com to recreate ldlinux.sys (because that's what it does)
(or do what you already did, because, well, that works too)

The small one is from the EFI\boot\ directory.

nope, see above

[glestwid]

nope, boot\syslinux\vesamenu.c32 is not truncated, it's a dynamically linked file(hence smaller), linked, i guess to libcom32.c32 or libutil.c32 or both..

Anyway, the issue still exist in http://ftp.vim.org/ftp/os/Linux/distr/p ... 0-i586.iso. And it was there even in RC3.