Porteus 5.0 updates

Technical issues/questions of an intermediate or advanced nature.
User avatar
Ed_P
Contributor
Contributor
Posts: 8341
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 5.01 ISO
Location: Western NY, USA

Porteus 5.0 updates

Post#1 by Ed_P » 18 Aug 2022, 19:00

The Porteus-v5.0/updates/core/updates.txt file shows:

Code: Select all

83182aaa125ce75a6202f1904b0fd249  ./20220723/001-core.xzm/ 122M
ec5394911b7a771fae922edb5b96a3f6  ./20220723/002-xorg.xzm/ 112M
025ffffc0913cd1f17efcd4cd61d50c7  ./20220723/initrd.xz/ 904K
but the Porteus-v5.0/updates/core/20220723/ folder shows:

Code: Select all

001-core.xzm                                       23-Jul-2022 12:35           127496192
002-xorg.xzm                                       23-Jul-2022 12:38           116961280
initrd.xz                                          04-Aug-2022 23:42              921852
What's the 04-Aug-2022 initrd.xz update about?
Ed

User avatar
ncmprhnsbl
DEV Team
DEV Team
Posts: 3924
Joined: 20 Mar 2012, 03:42
Distribution: v5.0-64bit
Location: australia
Contact:

Porteus 5.0 updates

Post#2 by ncmprhnsbl » 18 Aug 2022, 23:26

Ed_P wrote:
18 Aug 2022, 19:00
What's the 04-Aug-2022 initrd.xz update about?
viewtopic.php?p=88964#p88964
fix for fsck cheatcode on top of earlier upgrade/rebuild of the bins and libs (and removal of reiserfs support)
Forum Rules : https://forum.porteus.org/viewtopic.php?f=35&t=44

User avatar
Ed_P
Contributor
Contributor
Posts: 8341
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 5.01 ISO
Location: Western NY, USA

Porteus 5.0 updates

Post#3 by Ed_P » 19 Aug 2022, 06:43

Thank you. :)

It being in the /updates/core/20220723/ folder is a little misleading.
Ed

User avatar
Rava
Contributor
Contributor
Posts: 5401
Joined: 11 Jan 2011, 02:46
Distribution: XFCE 5.01 x86_64 + 4.0 i586
Location: Forests of Germany

Porteus 5.0 updates

Post#4 by Rava » 19 Aug 2022, 07:43

ncmprhnsbl wrote:
18 Aug 2022, 23:26
removal of reiserfs support
I think we should have a post (best pinned so that it is at the top) describing the differences.

Like
initrd.xz 1234567 bytes, md5sum bla1 - no support for ext4, support for reiserfs
initrd.xz 1234568 bytes, md5sum bla2 - support for ext4, support for reiserfs
initrd.xz 1234569 bytes, md5sum bla3 - support for ext4, no support for reiserfs

and other details - not only reiserfs and ext4… these are the examples I came up with on a whim.

Like, I needed a new initrd when I had my sda1 reformatted into ext4 since the older initrd did not support ext4 - and since I cannot umount sda1 since it is one of the 2 partitions to hold my modules (technically, with most setups I have it mostly holds the symlinks to a different sda? partition where the most modules themselves are, but that still means I would have to boot from USB or CD-ROM or DVD to be able to fsck sda1, it makes no difference if there is only one main essential module on sda1, or 2, or all of them are, all that means: no fsck for sda1 if initrd does not support it.)
Cheers!
Yours Rava

Post Reply