How to stop this.?Not yet install persistent at USB, after observing an api appears through screen an changing brightness every 10 seconds.
is this a bug or surprise egg for new comers?
Forum Tips Collection:
http://www.porteus.org/info/tips-and-tricks.html
-->Safe Browse your System?<-- open browser paste this file://
--> but where do you put the cheatcode before you boot you live CD <--
When the graphical Porteus logo appears with the boot menu, choose your desired menu entry and hit the TAB key,
which will allow you to edit the command line.
changes=/dev/device
changes=/path/
changes=/path/fileSaveSession.dat
All changes made in Porteus are kept in memory until you reboot.
With this boot parameter, you tell Porteus to use a device other than your memory for storing changes.
You can, for example, format your disk partition /dev/sdb2 with some Linux filesystem and then use 'changes=/dev/sdb2'
to store all changes to that partition. If it is a windows filesystem (FAT32/NTFS) you have to create a save.dat file first.
Please read /boot/docs/cheatcodes.txt
btw...why not use a USB-thumb-drive?...much more comfort and ease of use, especially if you want to use additional modules.
-->Default root password for the Live CD<--
root password: toor unless you changed it at some point.
guest password:guest
--> Is there a command to show what USM modules active?<-- ls /mnt/live/memory/images
--> Persistent item in menu from deactivated module<-- First hide it with Sistem - Preferences - Main Menu and reboot it's not there (not even hidden)
-->in order to "uninstall" a program from a module, I have to: Extract the module, Delete the files, Compress the module..
I want to get rid of several programs I don't use (like gimp and pigdin) and it seems a rather complicated and prone-to-error method. Is there any other method?<--
mkdir /tmp/unpacked
xzm2dir /path/to/002-xorg.xzm /tmp/unpacked
ROOT=/tmp/unpacked removepkg gimp
dir2xzm /tmp/unpacked /path/to/002-xorg.xzm
Only 2 comments:
the line ROOT=.... has to be run as root (so a previous su is required)
some of the programs are not in 002-xorg.xzm but in 003-mate.xzm, so I had to repeat the process accordingly
-->Problems with creating save.dat container<--
menu > System Tools>Porteus's Save File manager. .Saving it to the flash drive's porteus folder is fine but do note that Linux is case sensitive, thus Porteus and porteus are two different names so maybe saving it to the flash drive's root might be a better place to start. And no need to get to get carried away with size, start with 512MB and you should be fine. I have one system with one half that.
At some point you will hear about the flash drive's UUID but for the moment lets concentrate on the save.dat file.
Once you have created it, and located it you need to add it to the porteus.cfg file. Something like this:
APPEND initrd=initrd.xz changes=/porteussave.dat
APPEND initrd=initrd.xz changes=EXIT:/porteussave.dat As for what the difference is between the two check the file:///mnt/sde1/multiboot/Porteus-KDE4-v3.1-i486/boot/docs/cheatcodes.txt file.
Once the cfg file has been changed reboot to impliment it. assuming your flash drive is formatted as FAT and not a Linux format.
-->Can you run multiple instance USM?<-- No.
--><--