Porteus

• What's the difference in the changes= between the two, for example?
• And
  1. would it be possible to set the changes to a different partition, but not hard-conf stuff like /dev/sdb2 ? (cause there may be more usb sticks, or there might even not be an internal hard drive in the computer, or be several, etc...)
     (also, is GPT formatting drives gonna be supported anytime soon? that'd be nice as well I guess)
     And
  2. is it possible to have the modules on a different partition too? I'd prefer to keep the base OS and the additions separated...
  If the answer is no to either one, then I guess I'll have to go with a single partition setup...

jan6 wrote: ↑

27 Oct 2018, 13:05

[*]And

1. would it be possible to set the changes to a different partition, but not hard-conf stuff like /dev/sdb2 ? (cause there may be more usb sticks, or there might even not be an internal hard drive in the computer, or be several, etc...)

SPECIAL NOTE FOR USING CHEATCODES WITH 'LABEL' AND 'UUID':
If you specify a LABEL or UUID with a cheatcode, remember that all
portions of these commands are case sensitive. You should use a
unique label for each of your partitions if you wish to use device
labels with your cheatcodes. Use the 'blkid' command to view your
device's UUID and LABEL. Using UUID and LABEL can be quite handy
because they are unique to your device, and your data will be found
and properly mapped on different hardware configurations.
Every cheatcode which contains a /path can take advantage of 'UUID:'
and 'LABEL:' extensions.

Examples:
changes=UUID:STrING-0F-ChARACtERS/path/file.dat
extramod=LABEL:YourLabelName/path/to_folder/with_modules
from=UUID:STrING-0F-ChARACtERS/path/folder
rootcopy=LABEL:YourLabelName/path/to_folder/with_files

ppp wrote: ↑

25 Dec 2018, 14:30

But I still have a same question with jan6:
what's the difference beteen the changes= in 2 .cfg files? Why we need both of them point to one location to load permanent changes? I once commented the changes= line in /porteus/porteus-v4.0-x86_64.cfg and get stuck in an ugly weird login ui, refusing me to get in the system.

ppp wrote: ↑

25 Dec 2018, 14:30

what's the difference beteen the changes= in 2 .cfg files? Why we need both of them point to one location to load permanent changes?

Ed_P wrote: ↑

25 Dec 2018, 16:01

They are the same codes just in different locations. You don't need to configure both of them, just one. The v4.0 file is new and intended for codes that can effect multiple DEs, the old one is specific to the DE.

Ed_P wrote: ↑

25 Dec 2018, 16:01

They are the same codes just in different locations. You don't need to configure both of them, just one. The v4.0 file is new and intended for codes that can effect multiple DEs, the old one is specific to the DE.

ppp wrote: ↑

26 Dec 2018, 03:32

But I think both of them needs to be configured because even I added the change= code in my porteus-v4.0-x86_64.cfg, I can't load in my changes if I don't modify the change= line in the old porteus.cfg.

https://forum.porteus.org/viewtopic.php?t=7742 wrote:New configuration file at porteus/porteus-v4.0-x86_64.cfg which replaces the .sgn file and can hold cheatcodes. One per line.

https://forum.porteus.org/viewtopic.php?t=7564&start=45 wrote:whatever cheatcodes are set in that file will be passed to whatever boot entry you choose.

Ed_P wrote: ↑

26 Dec 2018, 04:32

Try with the changes= cheatcode only in the porteus.cfg file.

ncmprhnsbl wrote: ↑

27 Feb 2018, 21:30

whatever cheatcodes are set in that file will be passed to whatever boot entry you choose..

ppp wrote: ↑

26 Dec 2018, 05:07

Strange, I commented the changes= line in my porteus-v4.0-x86_64.cfg and rebooted. Last time I did this I can't enter the system but this time, I entered in my system successfully. And I find my unclosed softwares in the last login session are still there!

Ed_P wrote: ↑

25 Dec 2018, 16:55

You think I'm 100% sure!!