![Yahoo :Yahoo!:](./images/smilies/yahoo.gif)
![Oh Yeah :celebrate3:](./images/smilies/celebrate3.gif)
![Whoopie! :celebrate14:](./images/smilies/celebrate14.gif)
![Punk :punk:](./images/smilies/punk.gif)
![Team Work :bounce8:](./images/smilies/bounce8.gif)
Nice job
![Worthy :worthy:](./images/smilies/worthy.gif)
Thank you.
![Drinks or Beer :beer:](./images/smilies/drinks.gif)
A minor suggestion, making the alert indicating the user is booting from an ISO a Warning rather than an Error.
downloaded it…ncmprhnsbl wrote: ↑30 Oct 2022, 07:24here is a module of an adjusted /opt/porteus-scripts/update-porteus
updater-test.xzm
to test it, just activate and run the updater from porteus settings centre.
Code: Select all
64d39221ab482316e0c384ea76c68da2 updater-test.xzm
As usual, it seems it is not able to work with my shared internet WLAN via LAN, as previously reported.ncmprhnsbl wrote: ↑30 Oct 2022, 07:24to test it, just activate and run the updater from porteus settings centre.
Code: Select all
Starting checks ...
[OK] Server: http://dl.porteus.org
[OK] Architecture: x86_64
[OK] User is root
[OK] Distro is Porteus
[OK] Base folder is writable
[ERROR] An internet connection is required.
Code: Select all
root@porteus:/# ping -q -w 1 -c 1 `ip r | awk '/default/{print$3}'|head -n1`
PING 10.42.0.1 (10.42.0.1) 56(84) bytes of data.
--- 10.42.0.1 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms
root@porteus:/# ping -q -w 1 -c 1 www.google.com
PING forcesafesearch.google.com (216.239.38.120) 56(84) bytes of data.
--- forcesafesearch.google.com ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 26.358/26.358/26.358/0.000 ms
try this one:
Code: Select all
Starting checks ...
[OK] Server: http://dl.porteus.org
[OK] Architecture: x86_64
[OK] User is root
[OK] Distro is Porteus
[OK] Base folder is writable
[OK] Internet connection confirmed
Downloading: update-porteus-live DONE
Downloading: updates.txt DONE
Checking base modules ...
Checking patch availability ...
#########################
Available core updates
001-core.xzm
002-xorg.xzm
Would you like to continue? [y/n]
Code: Select all
001-core.xzm
002-xorg.xzm
Code: Select all
Index of /porteus/x86_64/Porteus-v5.0/updates/core/20220924
Icon Name Last modified Size [PARENTDIR] Parent Directory -
[ ] 001-core.xzm 2022-10-09 12:48 121M
[ ] 002-xorg.xzm 2022-10-09 12:48 112M
Code: Select all
root@porteus:~# md5sum $PORTDIR/base/001-core.xzm $PORTDIR/base/002-xorg.xzm
087e196ed3e7a8750b32031e3221fc2b /mnt/sda1/Porteus_5.0/porteus/base/001-core.xzm
9a1afb69141822791d5a114909725431 /mnt/sda1/Porteus_5.0/porteus/base/002-xorg.xzm
Code: Select all
cd /home/guest/.moonchild productions/pale moon/*.default
# the above won't work, replace "*.default" with the real folder name of your setup
grep -E '"browser.sessionstore.cache_behavior", |"browser.startup.page", ' prefs.js
# should be:
#user_pref("browser.sessionstore.cache_behavior", 2);
#user_pref("browser.startup.page", 3);
This looks better. Thank you.ncmprhnsbl wrote: ↑31 Oct 2022, 01:49try this one:
updater-test-22-10-31.xzm md5sum: 7e84e2bda8a04e5cb0bd441bbbff7ef3
I agree, some kind of info about an update would be helpful. Does 001-'s update require 002-'s update? What if there are 2 updates for the same modules but at different dates, can the user choose one or does the new one require the prior one be implimented. etc.Rava wrote: ↑31 Oct 2022, 02:25Suggestion, is it possible for the script to tell the user what update that is?
E.g. by telling the user the YYYYMMDD folder the updates are in?
Just
is giving no info at allCode: Select all
001-core.xzm 002-xorg.xzm
Unless the user has booted an ISO the answer to the 1st question I would say is yes.
I agree, while one could argue it is up to the user to safeguard that stuff, Porteus should be helpful in that regard and "think for the user" a bit so to speak, or in this case:
I think it should appear red not green.
Code: Select all
root@porteus:/# cat /etc/porteus/00*
001-core.xzm:20221006
002-xorg.xzm:20221006
002-xtra.xzm:20220630
003-xfce.xzm:20220925
Code: Select all
/porteus/
[OK] Architecture: x86_64
[OK] User is root
[OK] Distro is Porteus
[OK] Base folder is writable
[OK] Internet connection confirmed
Downloading: update-porteus-live DONE
Downloading: updates.txt DONE
[ERROR] Could not download updates.txt file
[ERROR] http://ftp.nluug.nl/os/Linux/distr/porteus//x86_64/Porteus-v5.0/updates/core/updates.txt
You may now close this window.
Code: Select all
root@porteus:~# grep SERVER /etc/porteus.conf
SERVER=http://linux.rz.rub.de/porteus/
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
[OK] Internet connection confirmed
Downloading: update-porteus-live DONE
Downloading: updates.txt DONE
Checking base modules ...
Checking patch availability ...
####################################
Porteus update report
You are up to date.
You may now close this window.
I can assure you us ISO booters know we are booting ISOs and know ISOs can't be updated (without some effort) so we don't need "warning"s. "Reminder"s are sufficient.
Code: Select all
guest@porteus:~$ locate ntfs-3g
locate: unexpected EOF reading `/var/lib/mlocate/mlocate.db'
Sounds like a Porteus Kiosk problem.
you mean these characters?
Code: Select all
locate: unexpected EOF reading `/var/lib/mlocate/mlocate.db'
^ ^
Code: Select all
root@porteus:~# locate ntfs-3g
locate: unexpected EOF reading `/var/lib/mlocate/mlocate.db'
Code: Select all
root@porteus:~# updatedb
root@porteus:~# echo $?
0
Code: Select all
root@porteus:~# locate ntfs-3g
/bin/lowntfs-3g
/bin/ntfs-3g
/bin/ntfs-3g.probe
/lib64/libntfs-3g.so
/lib64/libntfs-3g.so.89
/lib64/libntfs-3g.so.89.0.0
/sbin/mount.lowntfs-3g
/sbin/mount.ntfs-3g
/usr/lib64/libntfs-3g.so
/usr/lib64/ntfs-3g
/usr/man/man8/mount.lowntfs-3g.8
/usr/man/man8/mount.ntfs-3g.8
/usr/man/man8/ntfs-3g.8
/usr/man/man8/ntfs-3g.probe.8
/var/lib/pkgtools/packages/ntfs-3g-2021.8.22-x86_64-1