Sorry for the long post, but the XFCE panel and the I/O error of contents of modules is a complex issue.
────────────────────────────────────
roadie wrote: ↑05 Oct 2023, 05:59
I have Porteus v5.0 and v5.0.1 set up on the same partition with the only difference being the names of the folders, ie: porteus-5.0-xfce and porteus-5.0.1-xfce and there are no problems with either one being found with the standard .cfg files. I also set up Porteus v5.0.1 with symlinks in the base and modules folders pointing to another partition and all were loaded on booting. Booting times were basically the same with both the v5.0 and v5.0.1 initrd.xz
Could be that in my case it is a thing between the 5.0.1 initrd and my older kernel?
because all works well (no delays, symlinked modules all found and loaded without issue) with the older
and in all cases this is my kernel:
Code: Select all
root@rava:/# uname -r
5.4.30-porteus
────────────────────────────────────
donald wrote: ↑05 Oct 2023, 05:22
Block all means to block all except web browsing or not?
Depends.
I had to tweak my rc.FireWall or else my email program would not work:
Code: Select all
root@rava:/# file /etc/rc.d/rc.FireWall
/etc/rc.d/rc.FireWall: ERROR: cannot read `/etc/rc.d/rc.FireWall' (Input/output error)
root@rava:/# cat /etc/rc.d/rc.FireWall
cat: /etc/rc.d/rc.FireWall: Input/output error
Currently I cannot show you the changes.

More on that below.
────────────────────────────────────
I presume my issue with not being able to load some files might be the reason why the XFCE panel is not showing?
I activated 05-devel (the correct one after ncmprhnsbl had to point it out to silly me where it sits

)
This one:
Code: Select all
74019034b09a66e2756cc626a81a30b025a63db1229908fbf6994d07ee9cc38a 05-devel.xzm
and
since I saw no changes in the main menu entries of the panel, I restarted the panel via
The panel vanished, no error message, but the panel did not come back !?
Then I tried xfce4-panel -r once more:
resulted in this:

and this:
Since then the panel is gone. After I read donald's post above I also realized
I could no longer access /etc/rc.d/rc.FireWall (my current rc.FireWall is altered due to the needs to allow more ports for SMTP and such) and thus sits in my 992-rootcopy_5.0-RECENT.xzm module (which is a symlink to my most recent created rootcopy-settings-module - currently that is 992-rootcopy_5.0_2023-10-02.xzm)
Other files from 992-rootcopy_5.0-RECENT.xzm aka 992-rootcopy_5.0_2023-10-02.xzm are accessible, though, like this one:
Code: Select all
root@rava:/# cat /etc/HOSTNAME
rava.myporteus.net
And when I start via the right-mouse-on-desktop menu the XFCE settings and choose "Panel" I get the same error GDBus.Error as above.
I have no idea if its related to me being unable to access some other files.
Could it be the suspend messes up things? That because my modules are loaded via symlinks I cannot access at times their contents?
I had an issue yesterday with all my files in /usr/local/bin - that are part of my 991-usr_local_bin_2023-10-04.xzm (loaded via symlink called 991-usr_local_bin_RECENT.xzm) and by pure coincidence I even captured the exact moment when it happened.
I searched a code snipped in my own scripts in /usr/local/bin via grep, and the first few hits where shown, while all of a sudden the rest of the files were displayed as Input/output error
Look for yourself:
guest@rava:/usr/local/bin$ grep false *sh
Daueralarm2.sh:until false; do
alarm.sh:until false; do
backup.sh:USBbackup=1 # 1=true 0=false
chmod.sh:is not very foolproof and could result in false positives (but that's better
chmod.sh:than false negatives ^-^ )]
daueralarm.sh:until false; do
/bin/grep: update-hda5-101-home.sh: Input/output error
/bin/grep: update-x-101-home.sh: Input/output error
/bin/grep: update-x-seamonkey_2.x_extensions.sh: Input/output error
/bin/grep: usmdb.sh: Input/output error
/bin/grep: waitfor.sh: Input/output error
/bin/grep: webcam.sh: Input/output error
I call that one weird behaviour.
Wish I could figure out what's causing the issue.
Trying to repeat that very grep results in Input/output error on all files (a much longer list than in the [
quote
] above.
What did I do? First I mloop's the 991-usr_local_bin_2023-10-04.xzm module and wanted to copy all its files from its usr/local/bin
but also got an Input/output error error - not on mloop, but during the attempted copy process.
Then I copied the module to another partition. Did an md5sum on both modules: both md5sums are the same.
Then I mloop's the version of the module that I copied to the other partition and then I could copy all its files from usr/local/bin to /usr/local/bin
Did anyone ever encounter an issue like this?
The first module I tried mloop'ing is the one currently activated via booting. Why are the md5sums the same when testing the "original" as loaded during boot that sits on sda5, and the copied one that I copied to sda2 the same, still I cannot access its contents when mloop'ing the sda5 module (the one activated during boot) while I could access its mloop'd contend via the copy from sda2?
When a checksum is made of a file, the whole file is loaded, yes? What could cause one module to fail to access its contents while the other copy can access its contents when both modules created the same md5sum?
Is that some workings of how a live system works that I do not get?
Since it seems I will not get back my XFCE panel any time soon, I try to compile what I wanted to compile (see here
meson.build ERROR: Dependency "gtk+-2.0" not found ) hopefully without any more Input/output error and will restart.
