guest use to have access to it, without a symlink, and people who have used it in the past will now have to learn it's location. Not saying it can't be done, just that it is something that will need to be done when upgradijng to 3.2. Will there be a 3.2 document listing all the commands that will have this new situation?brokenman wrote:@Ed_P
lspci command not working in Cinnamon 64 bit like it does in prior releases.
Sorry, but this file is in sbin and as such guest will not have direct access to it. You can create a symlink in /bin if you need it as guest.
"what use does Porteus have knowing where the ISO file resides?"And a Boot Device of /mnt/isoloop/ without indicating from which physical device the iso is on is kinda useless. imo
Can you explain why please? From my POV, /mnt/isoloop tells porteus that you booted from an ISO file. After booting, what use does Porteus have knowing where the ISO file resides? More importantly there are certain functions, such as updating modules, that cannot be run after booting from ISO.
Well, it helps to support the various apps and scripts that users of previous versions of porteus have which use this location to perform useful functions for the user. I run porteus different machines and on different devices. Not all the machines are partitioned the same way and certainly not the flash drives. Scripts that backup files, restore files, use an Optional directory need to know what device has the necessary directories. And I keep all porteus related files on single drives.
I'm not saying that porteus doen't need to know that it was booted from an ISO, and in prior releases it did. The /mnt/live/mnt/isoloop directory exists in 3.0 the same as 3.2. But 3.0 also indicates the ISO's actual mnt device address. If 3.2 can't maintain compatibility with earlier releases it just makes upgrading harder.
"certain functions, such as updating modules, that cannot be run after booting from ISO."
Now this concerns me. It implies that unless porteus is installed it will become obsolete because the updating will not be creating new modules. This would seem to be contrary to the module concept of porteus. I update porteus, firefox and flash player and others by downloading them or building new modules with USM and putting them in a Modules folder outside the one in the ISO.
If porteus is loosing it's module concept that would be devastating imo.