Multi Boot USB

Non release banter
Jack
Contributor
Contributor
Posts: 1533
Joined: 09 Aug 2013, 14:25
Distribution: Porteus 4.0rc4 My Mate 64 bit
Location: USA

Multi Boot USB

Post#16 by Jack » 05 Mar 2018, 18:22

jssouza wrote:
05 Mar 2018, 17:44
Jack, you could then also put both mate and lxde in base and use noload=lxde load=mate cheatcodes to boot to mate and noload=mate load=lxde to boot to lxde.
Can they both share the changes folder? It has to be that way.
Like this

Code: Select all

PROMPT 0
TIMEOUT 90
UI vesamenu.c32
DEFAULT GRAPHICAL
MENU BACKGROUND porteus.png
MENU TITLE Porteus-MULTI-4.0 64bit

MENU WIDTH 30
MENU MARGIN 2
MENU ROWS 10
MENU HELPMSGROW 17
MENU TIMEOUTROW 28
MENU TABMSGROW 15
MENU CMDLINEROW 22
MENU HSHIFT 4
MENU VSHIFT 5

	menu color screen	37;40      #00000000 #00000000 none
	menu color border	30;44      #00000000 #00000000 none
	menu color title	1;36;44    #ffF6FF00 #30003f07 none
	menu color unsel	37;44      #ffffffff #00000000 none
	menu color hotkey	1;37;44    #ff8037b7 #00000000 none
	menu color sel		7;37;40    #ff111B78 #003f7fbf none
	menu color hotsel	1;7;37;40  #ffaf67f7 #003f7fbf none
	menu color scrollbar	30;44      #00000000 #00000000 none

	menu color tabmsg	31;40      #ffB6F538 #00000000 none
	menu color cmdmark	1;36;40    #ffff0000 #00000000 none
	menu color cmdline	37;40      #ffffffff #ff000000 none
	menu color pwdborder	30;47      #ffff0000 #00000000 std
	menu color pwdheader	31;47      #ffff0000 #00000000 std
	menu color pwdentry	30;47      #ffff0000 #00000000 std
	menu color timeout_msg	37;40      #ff809aef #00000000 none
	menu color timeout	1;37;40    #ffb72f9f #00000000 none
	menu color help		37;40      #ffD5F538 #00000000 none
	menu color msg07	37;40      #90ffffff #00000000 std


LABEL GRAPHICAL
MENU LABEL Graphics mode (Mate)
KERNEL /boot/syslinux/vmlinuz
INITRD /boot/syslinux/initrd.xz
APPEND noload=lxde load=mate changes=/porteus
TEXT HELP
    Run Porteus the best way we can.
    Try to autoconfigure graphics
    card and use the maximum
    allowed resolution
ENDTEXT

LABEL GRAPHICAL
MENU LABEL Graphics mode (LXDE)
KERNEL /boot/syslinux/vmlinuz
INITRD /boot/syslinux/initrd.xz
APPEND noload=mate load=lxde changes=/porteus
TEXT HELP
    Run Porteus the best way we can.
    Try to autoconfigure graphics
    card and use the maximum
    allowed resolution
ENDTEXT

LABEL text
MENU LABEL Text mode
KERNEL /boot/syslinux/vmlinuz
INITRD /boot/syslinux/initrd.xz
APPEND 3
TEXT HELP
    Run Porteus in text mode and
    start the command prompt only
ENDTEXT

LABEL intel
MENU LABEL Intel ucode update
KERNEL /boot/syslinux/vmlinuz
INITRD /boot/syslinux/intel-ucode.cpio,/boot/syslinux/initrd.xz
APPEND nomagic base_only norootcopy
TEXT HELP
    This mode upgrades your intel microcode
    for use with intel processors that
    receive the TSC_DEADLINE error message
ENDTEXT

LABEL pxe-boot
MENU LABEL Porteus as PXE server
KERNEL /boot/syslinux/vmlinuz
INITRD /boot/syslinux/initrd.xz
APPEND pxe
TEXT HELP
    Run Porteus as usual, but also
    initialize a PXE server.
    This will allow you to boot Porteus
    on other computers over a network
ENDTEXT

MENU SEPARATOR

LABEL plop
MENU LABEL PLoP BootManager
KERNEL /boot/syslinux/plpbt
TEXT HELP
    Run the plop boot manager.
    This utility provides handy
    boot-USB options for machines
    with vintage/defective BIOS
ENDTEXT

LABEL hd
MENU LABEL Boot from the first hd
COM32 chain.c32
APPEND hd0 1
TEXT HELP
    Don't start Porteus at all, but
    rather run any operating system
    installed on the first partition
    of the hard drive
ENDTEXT
I just like Slackware because I think it teach you about Linux to build packages where Ubuntu is like Windows you just install programs you want.

jssouza
DEV Team
DEV Team
Posts: 644
Joined: 09 Jul 2015, 14:17
Distribution: Porteus x86 arm
Location: Liechtenstein

Multi Boot USB

Post#17 by jssouza » 05 Mar 2018, 20:02

Jack wrote:
05 Mar 2018, 18:22
Can they both share the changes folder?
IMHO, they should work, but may not be true for say, common applications between your modules. One setting you do for one DE may conflict with the other.

Why cant you use 2 separate changes directories - one for mate and one for lxde? You would have the same problem, even if you created 2 separate 16GB partitions for each DE module.

User avatar
Ed_P
Contributor
Contributor
Posts: 4134
Joined: 06 Feb 2013, 22:12
Distribution: 4.0 Cinnamon 64-bit ISO
Location: Western NY, USA

Multi Boot USB

Post#18 by Ed_P » 05 Mar 2018, 20:19

jssouza wrote:
05 Mar 2018, 17:44
Jack, you could then also put both mate and lxde in base and use noload=lxde load=mate cheatcodes to boot to mate and noload=mate load=lxde to boot to lxde.
:)

Code: Select all

LABEL GRAPHICAL1
MENU LABEL Mate Graphics mode
KERNEL /boot/syslinux/vmlinuz
INITRD /boot/syslinux/initrd.xz
APPEND changes=/porteus noload=lxde
TEXT HELP
    Run Porteus the best way we can.
    Try to autoconfigure graphics
    card and use the maximum
    allowed resolution
ENDTEXT

LABEL GRAPHICAL2
MENU LABEL Lxde Graphics mode
KERNEL /boot/syslinux/vmlinuz
INITRD /boot/syslinux/initrd.xz
APPEND changes=/porteus noload=mate
TEXT HELP
    Run Porteus the best way we can.
    Try to autoconfigure graphics
    card and use the maximum
    allowed resolution
ENDTEXT
Separate changes directories could be set up for each DE on a separate ext4 partition.


-update-

oops, I missed a couple of postings.

If a separate partition is set up for the changes directories it might be hard to specify. Does Porteus support changes on FAT32 partitions without using a save.dat file?
Ed

donald
Full of knowledge
Full of knowledge
Posts: 1392
Joined: 17 Jun 2013, 13:17
Distribution: Porteus 3.2.2 XFCE 32bit
Location: Germany

Multi Boot USB

Post#19 by donald » 05 Mar 2018, 20:38

Hi Jack
I have 003-xfce4 and 003-mate placed in the base folder,
(Both were built by you btw. ;) )
made an menu entry in porteus.cfg specifying which one to load
at boot.
I also seperated the changes for mate and xfce
(create the folders as root - changes_xfce and changes_mate in my case)
It looks like this:

Code: Select all

LABEL GRAPHICAL
MENU LABEL Graphics mode - XFCE
KERNEL /boot/syslinux/vmlinuz
INITRD /boot/syslinux/initrd.xz
APPEND from=UUID:xxxxx changes=UUID:xxxxx/porteus/changes_xfce noload=mate
TEXT HELP
    Run Porteus the best way we can.
    Try to autoconfigure graphics
    card and use the maximum
    allowed resolution
ENDTEXT

LABEL GRAPHICAL
MENU LABEL Graphics mode - MATE
KERNEL /boot/syslinux/vmlinuz
INITRD /boot/syslinux/initrd.xz
APPEND from=UUID:xxxxx changes=UUID:xxxxx/porteus/changes_mate noload=xfce4
TEXT HELP
    Run Porteus the best way we can.
    Try to autoconfigure graphics
    card and use the maximum
    allowed resolution
ENDTEXT
You see that noload the module (which should not load) is enough, it will
automatically load the other one.

Bear in mind if you want to use AF or copy2ram mode you also have to "noload"
one of them.

jssouza
DEV Team
DEV Team
Posts: 644
Joined: 09 Jul 2015, 14:17
Distribution: Porteus x86 arm
Location: Liechtenstein

Multi Boot USB

Post#20 by jssouza » 05 Mar 2018, 21:11

donald, load=DE would help if you have a DE sepcific module in optional. Eg: If you built a module for mate, just make sure you have "mate" in its module name, - eg: easytag-mate.xzm. Now, put this in optional, and load=mate would also load all mate specific modules from optional ;) .
This would also help if changes are converted to a module at a later stage. Just reame it to something that contains the DE string.

donald
Full of knowledge
Full of knowledge
Posts: 1392
Joined: 17 Jun 2013, 13:17
Distribution: Porteus 3.2.2 XFCE 32bit
Location: Germany

Multi Boot USB

Post#21 by donald » 05 Mar 2018, 22:31

@jssouza

I think we're both capable of imagining scenarios,
advanced and/or complicated setups where it would make sense
doing it this way, the other way around, or totally different. :)

Post Reply