Re: Porteus Desktop Edition 3.0 rc1 bugs/feedback thread
Posted: 05 Feb 2014, 05:06
Is there also an URL for customizing and download the 3.0rc1 ISO, like there is with the 3.0rc1 iso?
Porteus User Forum
https://forum.porteus.org/
Now, my entry reads like so: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
Code: Select all
LABEL 3.0rc1
MENU LABEL 3.0rc1 (xfce)
KERNEL 3.0rc1.x86-64.vmlinuz
APPEND initrd=3.0rc1.x86-64.initrd.xz from=UUID:CoRrEcTRaNdOmStRinG/porteus/3.0rc1 zram=20% fsck timezone=Europe/Berlin kmap=de acpi=force
If so, then this should be in the cheatcodes.txt as well...tome wrote:It can not be so:it was for v1.2 but now must be/porteus/2.1_x86-64/base
/porteus/2.1_x86-64/optional [...]
/porteus/3.0rc2_x86-64/base
/porteus/3.0rc2_x86-64/optional [...]
/porteus/2.1_x86-64/porteus/base
/porteus/2.1_x86-64/porteus/optional [...]
/porteus/3.0rc2_x86-64/porteus/base
/porteus/3.0rc2_x86-64/porteus/optional [...]
Yes, this what I hoped was all that's neccessary for dual boot on same flash, but I'm still confused regarding rewriting the "cheat script". I can see how to tell the porteus.cfg to use a renamed core as 3.0rc's or even Puppy's core file but the cheat sheet somehow baffles me.Rava wrote:And back to my issue: I just move my base folder from /porteus/3.0rc1/base/ to /porteus/3.0rc1/porteus/base/ and all is well?
But... the iso is unpacked... so it should work, yes?fanthom wrote:from= cheatcode should point to a device/folder where the ISO is unpacked
I think yes, because it is easier than using extramod=, and Porteus scripts don't see if you are using old or new paths.Again: Do I just need to move my base folder from /porteus/3.0rc1/ base/ to /porteus/3.0rc1/porteus/ base/ ?
download binaries from official mozilla site, as root create new root tree in new folder, extract thunderbird to correct folder in this tree, add launchers and icons and build module.How to install/get that as a module without PPM working in 3.0rc1?
open a terminal and type:How to install/get that as a module without PPM working in 3.0rc1?
Code: Select all
usm -u all
usm -g mozilla-thunderbird
Here is my from= cheatcode:Again: Do I just need to move my base folder from /porteus/3.0rc1/ base/ to /porteus/3.0rc1/porteus/ base/ ?
That gives me:brokenman wrote:open a terminal and type:You can convert the slackware package afterwards using txz2xzmCode: Select all
usm -u all usm -g mozilla-thunderbird
Code: Select all
root@porteus:/usr/local/bin# usm --help
-su: usm: command not found
Code: Select all
[... snip ...]
Starting salix database update
Connection is good
Downloading: CHECKSUMS.md5 DONE
Downloading: PACKAGES.TXT DONE
Downloading: LIBS.TXT.gz DONE
Downloading: OPTIFEST.gz DONE
Downloading: MANIFEST.bz2 DONE
bunzip2: /var/usm/salix/MANIFEST.bz2 is not a bzip2 file.
==============================================================================
WARNING! WARNING! WARNING! WARNING! WARNING!
==============================================================================
One or more errors occurred while usm was running:
FATAL ERROR!
usm update_database 694
Could not decompress: MANIFEST.bz2
==============================================================================
Code: Select all
usm -g mozilla-thunderbird
Nothing found for: mozilla-thunderbird
Are you using Porteus v3.0? I assumed from your question that you are. USM will not function with anything below Porteus v3.0.How to install/get that as a module without PPM working in 3.0rc1?
Yes, using 3.0rc1 x86-64... Sadly, I have no clue what's the issue with the salix /var/usm/salix/MANIFEST.bz2 database file.brokenman wrote:Are you using Porteus v3.0? I assumed from your question that you are. USM will not function with anything below Porteus v3.0.