Porteus

Posted: **21 Dec 2022, 06:28**

Porteus-v5.0 updates (Post by ncmprhnsbl #92112)

For those who are unaware, in the Porteus Setting Centre (see menu>System/Administration>), there is an "Porteus Updater" tool.

When i start it I still get this:

Code: Select all

 Starting checks ... 
[OK] Server: http://linux.rz.rub.de/porteus/
[OK] Architecture: x86_64
[OK] User is root
[OK] Distro is Porteus
[OK] Base folder is writable
[ERROR] An internet connection is required.

the network is fine:

Code: Select all

root@porteus:/# ping google.de
PING google.de (172.217.19.67) 56(84) bytes of data.
64 bytes from mil02s05-in-f67.1e100.net (172.217.19.67): icmp_seq=1 ttl=116 time=37.2 ms
64 bytes from mil02s05-in-f67.1e100.net (172.217.19.67): icmp_seq=2 ttl=116 time=37.2 ms
64 bytes from mil02s05-in-f67.1e100.net (172.217.19.67): icmp_seq=3 ttl=116 time=36.9 ms
64 bytes from mil02s05-in-f67.1e100.net (172.217.19.67): icmp_seq=4 ttl=116 time=37.2 ms
^C
--- google.de ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3004ms
rtt min/avg/max/mdev = 36.897/37.122/37.234/0.132 ms

the issue, I presume, is still that the machine gets internet via LAN sharing by another Porteus machine that gets its internet via WLAN. Set up automagically via the network manager.

Can the "Porteus Updater" tool be tweaked so that it detects internet out of the box when a user has a network configuration like me?

Posted: **21 Dec 2022, 08:29**

seems not all the changes to the script went into the update

so, until after the next update, use this:
updater-test-22-10-31.xzm

Posted: **21 Dec 2022, 16:14**

Currently downloading 3 modules…

Code: Select all

 All available updates are selected: 

  1+) 001-core.xzm
  2+) 002-xorg.xzm
  3+) 002-xtra.xzm
Deselect an item (again to reselect, ENTER when ready):


[OK] Created updates folder
Downloading: 001-core.xzm  DONE
[OK] md5sum for 001-core.xzm is good
Downloading: 002-xorg.xzm  39%

It downloads it seemingly into $PORTDIR/updates/

My question: does the updater script check prior if there is enough free space on the partition that hosts $PORTDIR/ ?

It only says that the porteus directory (=$PORTDIR) is writeable for root.

In my case there was enough free space, after the download this is still free:

Code: Select all

root@porteus:/mnt/live/memory/images# df -Tm $PORTDIR/
Filesystem     Type 1M-blocks  Used Available Use% Mounted on
/dev/sda1      ext4      1443  1117       235  83% /mnt/sda1

Added in 5 minutes 44 seconds:
I only ran from root terminal

Code: Select all

/opt/porteus-scripts/update-porteus

In the end it said

Code: Select all

 Updates complete. 
 Updates will be activated on next reboot. 
 You may now close this window.

For now the 3 updates stay in $PORTDIR/updates/ - will they be loaded instead of the ones in base/ by the initrd?

Or would another part of the Porteus Setting Centre (that I did not run) move the modules from $PORTDIR/updates/ into $PORTDIR/base and the ones already in $PORTDIR/base are either overwritten, or prior moved e.g. into $PORTDIR/old or $PORTDIR/base-backup or $PORTDIR/base-old or a similar named backup folder?

Meaning in my case: if that would be the case the updates will not be activated on next reboot (when Porteus Setting Centre would do these changes - that I did not run) unless I do the move into $PORTDIR/base manually?

Posted: **21 Dec 2022, 17:34**

When I run the Updater it asks where to save the downloads:
Porteus 5.0 updates (Post by Ed_P #92097)

And I manually move them to the /porteus/base folder when the Updater ends. Maybe your unique DE needs to be tweaked.

Posted: **21 Dec 2022, 19:42**

Ed_P wrote: ↑
21 Dec 2022, 17:34
When I run the Updater it asks where to save the downloads:
Porteus 5.0 updates (Post by Ed_P #92097)

Could it be that you use as usual an ISO to boot from?
then the updater would be unable to create the $PORTDIR/updates/ module since $PORTDIR would be inside your ISO, would it not?

Did the updater tell you this:

[OK] Base folder is writable

(highlighting by me)

Ed_P wrote: ↑
21 Dec 2022, 17:34
Maybe your unique DE needs to be tweaked.

I use this DE:

Code: Select all

root@porteus:~# cat /etc/porteus/003-xfce.ver 
003-xfce.xzm:20220925

It's the official XFCE 4.16 module.
I renamed the module into 003-xfce-4.16.xzm because there is also a 4.12 one.
It's md5sum:

Code: Select all

4f61156879b273749c3af1d2b245c41b  003-xfce-4.16.xzm

Added in 6 minutes 1 second:
For now I move the original (older) three files to a fallback (backup) location and move the new ones (the updated / downloaded ones as quoted above) into base/

Posted: **21 Dec 2022, 22:16**

Rava wrote: ↑
21 Dec 2022, 19:48
For now I move the original (older) three files to a fallback (backup) location and move the new ones (the updated / downloaded ones as quoted above) into base/

Posted: **22 Dec 2022, 04:56**

Ed_P wrote: ↑
21 Dec 2022, 22:16

Rava wrote: ↑
21 Dec 2022, 19:48
For now I move the original (older) three files to a fallback (backup) location and move the new ones (the updated / downloaded ones as quoted above) into base/

since I cannot know if the updated files solve my suspend crashes issue Some tips on getting to the reason for the recent suspend crashes or not, I will reboot when I have to reboot (= when the suspend crash did once again occur) and keep the system running as it is (with the older versions) for now.

Porteus

Porteus-v5.0 updates - still fails on internet detection

Porteus-v5.0 updates - still fails on internet detection

Porteus-v5.0 updates - still fails on internet detection

Porteus-v5.0 updates - still fails on internet detection

Porteus-v5.0 updates - still fails on internet detection

Porteus-v5.0 updates - still fails on internet detection

Porteus-v5.0 updates - still fails on internet detection

Porteus-v5.0 updates - still fails on internet detection