Share your Bootloader Config

Non release banter
Post Reply
User avatar
freestyler
Contributor
Contributor
Posts: 382
Joined: 17 Oct 2013, 14:21
Distribution: Porteus KDE4
Location: Traveller
Contact:

Share your Bootloader Config

Post#1 by freestyler » 02 May 2014, 04:57

Thought it would be interesting to see what boot loader config scripts others are using.

Porteus is the only distro I use and have the stock boot loader that comes with it, here is my porteus.cfg:

Code: Select all

PROMPT 0
TIMEOUT 90
UI vesamenu.c32
DEFAULT kde
MENU BACKGROUND fuckyou.png
MENU TITLE Porteus-3.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    #ffA32F2F #30003f07 none
	menu color unsel	37;44      #ff111B78 #003f7fbf none
	menu color hotkey	1;37;44    #ff8037b7 #00000000 none
	menu color sel		7;37;40    #ff809aef #00000000 none
	menu color hotsel	1;7;37;40  #ffaf67f7 #003f7fbf none
	menu color scrollbar	30;44      #00000000 #00000000 none

	menu color tabmsg	31;40      #ffA32222 #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      #ff666C85 #00000000 none
	menu color msg07	37;40      #90ffffff #00000000 std


LABEL kde
MENU LABEL Porteus 3.0 KDE 64bit
KERNEL vmlinuz
APPEND initrd=initrd.xz changes=/porteus noload=xfce;lxde;razor;mate
TEXT HELP
    Run Porteus the best way we can.
    Try to autoconfigure graphics
    card and use the maximum
    allowed resolution
ENDTEXT

LABEL xfce
MENU LABEL Porteus 3.0 XFCE 64bit
KERNEL vmlinuz
APPEND initrd=initrd.xz changes=/changes noload=kde;lxde;razor;mate
TEXT HELP
    Run Porteus the best way we can.
    Try to autoconfigure graphics
    card and use the maximum
    allowed resolution
ENDTEXT

MENU SEPARATOR

LABEL lxde
MENU LABEL Testing 3.0 LXDE 64bit
KERNEL vmlinuz
APPEND initrd=initrd.xz changes=/testing64 noload=xfce;kde;razor;mate;lxqt
TEXT HELP
    Run Porteus the best way we can.
    Try to autoconfigure graphics
    card and use the maximum
    allowed resolution
ENDTEXT

LABEL mate
MENU LABEL Testing 3.0 MATE 64bit
KERNEL vmlinuz
APPEND initrd=initrd.xz changes=/testing64 noload=xfce;kde;razor;lxqt
TEXT HELP
    Run Porteus the best way we can.
    Try to autoconfigure graphics
    card and use the maximum
    allowed resolution
ENDTEXT

LABEL razor
MENU LABEL Testing 3.0 RazorQT 64bit
KERNEL vmlinuz
APPEND initrd=initrd.xz changes=/testing64 noload=xfce;lxde;kde;mate;lxqt
TEXT HELP
    Run Porteus the best way we can.
    Try to autoconfigure graphics
    card and use the maximum
    allowed resolution
ENDTEXT

LABEL lxqt
MENU LABEL Testing 3.0 LXQT 64bit
KERNEL vmlinuz
APPEND initrd=initrd.xz changes=/testing64 noload=xfce;razor;mate;lxde
TEXT HELP
    Run Porteus the best way we can.
    Try to autoconfigure graphics
    card and use the maximum
    allowed resolution
ENDTEXT

MENU SEPARATOR

LABEL kde32
MENU LABEL Testing 3.0 KDE 32bit
KERNEL vmlinuz
APPEND initrd=initrd.xz sgnfile=porteus-v3.0-i486.sgn changes=/porteus noload=xfce
TEXT HELP
    Run Porteus the best way we can.
    Try to autoconfigure graphics
    card and use the maximum
    allowed resolution
ENDTEXT

LABEL xfce32
MENU LABEL Testing 3.0 XFCE 32bit
KERNEL vmlinuz
APPEND initrd=initrd.xz sgnfile=porteus-v3.0-i486.sgn changes=/porteus noload=kde;lxde;mate;razor
TEXT HELP
    Run Porteus the best way we can.
    Try to autoconfigure graphics
    card and use the maximum
    allowed resolution
ENDTEXT

LABEL mate32
MENU LABEL Testing 3.0 Mate 32bit
KERNEL vmlinuz
APPEND initrd=initrd.xz sgnfile=porteus-v3.0-i486.sgn changes=/porteus noload=kde;lxde;xfce;razor
TEXT HELP
    Run Porteus the best way we can.
    Try to autoconfigure graphics
    card and use the maximum
    allowed resolution
ENDTEXT

LABEL razor32
MENU LABEL Testing 3.0 Razor 32bit
KERNEL vmlinuz
APPEND initrd=initrd.xz sgnfile=porteus-v3.0-i486.sgn changes=/porteus noload=kde;lxde;mate;xfce
TEXT HELP
    Run Porteus the best way we can.
    Try to autoconfigure graphics
    card and use the maximum
    allowed resolution
ENDTEXT

LABEL sensei
MENU LABEL Sensei
KERNEL vmlinuz
APPEND initrd=initrd.xz sgnfile=porteus-sensei.sgn changes=/sensei
TEXT HELP
    Run Porteus the best way we can.
    Try to autoconfigure graphics
    card and use the maximum
    allowed resolution
ENDTEXT

MENU SEPARATOR

LABEL fresh
MENU LABEL Always Fresh
KERNEL vmlinuz
APPEND initrd=initrd.xz nomagic base_only norootcopy noload=xfce;lxde;razor;mate
TEXT HELP
    Normally Porteus saves all changes
    to the /porteus/changes/ directory
    on the boot media (if writable)
    and restores them next boot.
    Use this option to start a fresh
    system, changes are not read from
    or written to any device
ENDTEXT

LABEL fresh64
MENU LABEL Always Fresh (testing 64)
KERNEL vmlinuz
APPEND initrd=initrd.xz nomagic base_only norootcopy noload=xfce;lxde;razor;mate;lxqt
TEXT HELP
    Normally Porteus saves all changes
    to the /porteus/changes/ directory
    on the boot media (if writable)
    and restores them next boot.
    Use this option to start a fresh
    system, changes are not read from
    or written to any device
ENDTEXT

LABEL fresh32
MENU LABEL Always Fresh (testing 32)
KERNEL vmlinuz
APPEND initrd=initrd.xz sgnfile=porteus-v3.0-i486.sgn nomagic base_only norootcopy noload=xfce;lxde;razor;mate;
TEXT HELP
    Normally Porteus saves all changes
    to the /porteus/changes/ directory
    on the boot media (if writable)
    and restores them next boot.
    Use this option to start a fresh
    system, changes are not read from
    or written to any device
ENDTEXT

LABEL copy2ram
MENU LABEL Copy To RAM
KERNEL vmlinuz
APPEND initrd=initrd.xz copy2ram noload=xfce;lxde;razor;mate
TEXT HELP
    Run Porteus the same as above,
    but first copy all data to RAM
    to get a huge speed increase
    (needs >768MB)
ENDTEXT

LABEL text
MENU LABEL Text mode
KERNEL vmlinuz
APPEND initrd=initrd.xz 3
TEXT HELP
    Run Porteus in text mode and
    start the command prompt only
ENDTEXT
here is a dodgy pic:
Image

here is another dodgy pic but scrolled down the menu:
Image

Writing this post just got me inspired to tweak it some more...
https://www.porteus-apps.org

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

Re: Share your Bootloader Config

Post#2 by Ed_P » 02 May 2014, 05:35

Actually I have two, but not quite the bootloader configs you were thinking.

1.

Code: Select all

# http://sourceforge.net/projects/grub4dos/
# Grub4DOS 0.4.5c 2013-03-03   http://code.google.com/p/grub4dos-chenall/downloads/list

# global options
#
# Use StartLinux to test screen displays under Windows.
# Use GRUB4DOS/SplashImages to create new splash images.
# http://diddy.boot-land.net/grub4dos/files/splash.htm
#
#splashimage=/GRLDRfiles/splash/porteus.xpm.gz 
# ****ground rrggbb   000000=black  ffffff=white  8-f = bright
#foreground ffffff
#background 000099

splashimage=/GRLDRfiles/splash/porteus.bmp 
color white/blue black/light-gray white/blue yellow/blue

# If NO splashimage use these commands
# color <foreground/background> [hilite-fg/hilite-bg [help text [heading]]]
# colors:                black       blue       green       cyan       red       magenta   brown    light-gray
#   foreground only: dark-gray light-blue light-green light-cyan light-red light-magenta   yellow   white
# color white/blue black/light-gray white/blue yellow/blue
# color blue/light-grey  white/light-gray yellow
# color white/green white/blue

# http://www.rmprepusb.com/tutorials/grub4dos#TOC-Single-Stepping
# To step thru msgs prior to menu quickly press the Insert key when booting

timeout 60
default 0
fallback 1

map --unhook

# menu entries

title Porteus 3.0  changes=      \n 213MB\n Porteus-RazorQT-v3.0-x86_64.iso 
find --set-root                       /ISOs/Porteus-RazorQT-v3.0-x86_64.iso
map --heads=0 --sectors-per-track=0   /ISOs/Porteus-RazorQT-v3.0-x86_64.iso (0xff) 
map --hook
root (0xff)
kernel /boot/syslinux/vmlinuz    from=/ISOs/Porteus-RazorQT-v3.0-x86_64.iso changes=EXIT:/porteus/changes/porteussave.dat extramod=/mnt/sda5/porteus/modules 
initrd /boot/syslinux/initrd.xz

title Porteus 3.0  extramod=     \n 213MB\n Porteus-RazorQT-v3.0-x86_64.iso 
find --set-root                       /ISOs/Porteus-RazorQT-v3.0-x86_64.iso
map --heads=0 --sectors-per-track=0   /ISOs/Porteus-RazorQT-v3.0-x86_64.iso (0xff) 
map --hook
root (0xff)
kernel /boot/syslinux/vmlinuz    from=/ISOs/Porteus-RazorQT-v3.0-x86_64.iso extramod=/mnt/sda5/porteus/modules;/mnt/sda5/porteus/modsavedat
initrd /boot/syslinux/initrd.xz

title Porteus 3.0  Always Fresh  \n 213MB\n Porteus-RazorQT-v3.0-x86_64.iso \n Can use to check space usage of porteus.dat file.
find --set-root                       /ISOs/Porteus-RazorQT-v3.0-x86_64.iso
map --heads=0 --sectors-per-track=0   /ISOs/Porteus-RazorQT-v3.0-x86_64.iso (0xff) 
map --hook
root (0xff)
kernel /boot/syslinux/vmlinuz    from=/ISOs/Porteus-RazorQT-v3.0-x86_64.iso 
initrd /boot/syslinux/initrd.xz

title   \n
root ()

title Porteus 3.0  Menu\n\n Porteus Boot menu options
# jaclaz http://www.911cd.net/forums//index.php?s=&showtopic=24927&view=findpost&p=171635
find --set-root /ISOs/Porteus-RazorQT-v3.0.lst
configfile      /ISOs/Porteus-RazorQT-v3.0.lst

title   \n
root ()

title Porteus 2.1  changes=      \n 193MB\n Porteus-RazorQT-v2.1-x86_64.iso 
find --set-root                       /ISOs/Porteus-RazorQT-v2.1-x86_64.iso
map --heads=0 --sectors-per-track=0   /ISOs/Porteus-RazorQT-v2.1-x86_64.iso (0xff) 
map --hook
root (0xff)
#kernel /boot/syslinux/vmlinuz   from=/ISOs/Porteus-v1.2-i486.iso vga=791 autoexec=startx  changes=EXIT:/porteussave.dat    
kernel /boot/syslinux/vmlinuz    from=/ISOs/Porteus-RazorQT-v2.1-x86_64.iso changes=EXIT:/porteussave.dat extramod=/mnt/sda5/porteusmodules 
initrd /boot/syslinux/initrd.xz

title Porteus 2.1  extramod=     \n 193MB\n Porteus-RazorQT-v2.1-x86_64.iso 
find --set-root                       /ISOs/Porteus-RazorQT-v2.1-x86_64.iso
map --heads=0 --sectors-per-track=0   /ISOs/Porteus-RazorQT-v2.1-x86_64.iso (0xff) 
map --hook
root (0xff)
kernel /boot/syslinux/vmlinuz    from=/ISOs/Porteus-RazorQT-v2.1-x86_64.iso extramod=/mnt/sda5/porteusmodules;/mnt/sda5/porteussavedat
initrd /boot/syslinux/initrd.xz

title Porteus 2.1  Always Fresh  \n 193MB\n Porteus-RazorQT-v2.1-x86_64.iso \n Can use to check space usage of porteus.dat file.
find --set-root                       /ISOs/Porteus-RazorQT-v2.1-x86_64.iso
map --heads=0 --sectors-per-track=0   /ISOs/Porteus-RazorQT-v2.1-x86_64.iso (0xff) 
map --hook
root (0xff)
kernel /boot/syslinux/vmlinuz    from=/ISOs/Porteus-RazorQT-v2.1-x86_64.iso   
initrd /boot/syslinux/initrd.xz

title   \n
root ()

title ..return
configfile /menu.lst

# Menu commands: http://www.gnu.org/software/grub/manual/html_node/
# end file menu.lst
http://imageshack.com/a/img836/4818/f705.png

2.

Code: Select all

splashimage=/ISOs/porteus3.bmp
color white/blue black/light-gray yellow/blue blue/yellow
# ****ground rrggbb   000000=black  ffffff=white  8-f = bright
foreground ffffff
background 000077
        
# Grub4DOS kernel parms - translated from Porteus RazorQT 3.0 iso V:\boot\syslinux\porteus.cfg file.

default 0

title  |   Porteus-v3.0 64bit       |\n Porteus main menu 
root ()

title  |                            |\n 
root ()

title  | Graphics mode (Razor)      |\n\n Run Porteus the best way we can.\n Try to autoconfigure graphics card and use the maximum allowed resolution
map --heads=0 --sectors-per-track=0 /ISOs/Porteus-RazorQT-v3.0-x86_64.iso (0xff) 
map --hook
root (0xff)
kernel /boot/syslinux/vmlinuz  from=/ISOs/Porteus-RazorQT-v3.0-x86_64.iso changes=/porteus/changes/porteussave.dat extramod=/mnt/sda5/porteus/modules 
initrd /boot/syslinux/initrd.xz

title  | Always Fresh               |\n\n Normally Porteus saves all changes to the /porteus/changes/ directory on the\n boot media (if writable) and restores them next boot.  Use this option to\n start a fresh system, changes are not read from or written to any device
map --heads=0 --sectors-per-track=0 /ISOs/Porteus-RazorQT-v3.0-x86_64.iso (0xff)
map --hook
root (0xff)
kernel /boot/syslinux/vmlinuz  from=/ISOs/Porteus-RazorQT-v3.0-x86_64.iso nomagic base_only norootcopy
initrd /boot/syslinux/initrd.xz

title  | Copy To RAM                |\n\n Run Porteus the same as above, but first copy all data to RAM\n to get a huge speed increase (needs >512MB)
map --heads=0 --sectors-per-track=0 /ISOs/Porteus-RazorQT-v3.0-x86_64.iso (0xff) 
map --hook
root (0xff)
kernel /boot/syslinux/vmlinuz  from=/ISOs/Porteus-RazorQT-v3.0-x86_64.iso copy2ram
initrd /boot/syslinux/initrd.xz

title  | Text mode                  |\n\n Run Porteus in text mode and start the command prompt only
map --heads=0 --sectors-per-track=0 /ISOs/Porteus-RazorQT-v3.0-x86_64.iso (0xff) 
map --hook
root (0xff)
kernel /boot/syslinux/vmlinuz  from=/ISOs/Porteus-RazorQT-v3.0-x86_64.iso 3
initrd /boot/syslinux/initrd.xz

title  | Porteus as PXE server      |\n\n Run Porteus as usual, but also initialize a PXE server.\n This will allow you to boot Porteus on other computers over a network
map --heads=0 --sectors-per-track=0 /ISOs/Porteus-RazorQT-v3.0-x86_64.iso (0xff) 
map --hook
root (0xff)
kernel /boot/syslinux/vmlinuz  from=/ISOs/Porteus-RazorQT-v3.0-x86_64.iso pxe
initrd /boot/syslinux/initrd.xz


title  |                            |\n 
root ()

title  | ..return                   |\n\n Exit Porteus menu
#configfile (bd)/menu.lst 
find --set-root /Porteus.lst
configfile /Porteus.lst  

title  |----------------------------|\n 
root ()
http://imageshack.com/a/img841/4347/4zeo.png
Ed

User avatar
freestyler
Contributor
Contributor
Posts: 382
Joined: 17 Oct 2013, 14:21
Distribution: Porteus KDE4
Location: Traveller
Contact:

Re: Share your Bootloader Config

Post#3 by freestyler » 02 May 2014, 05:53

Nice, Ive always thought about booting off iso but how does that work with adding modules?
https://www.porteus-apps.org

User avatar
fanthom
Site Admin
Site Admin
Posts: 4613
Joined: 28 Dec 2010, 02:42
Distribution: Porteus Kiosk
Location: Poland, currently - Cork, IE
Contact:

Re: Share your Bootloader Config

Post#4 by fanthom » 02 May 2014, 06:46

good thread and nice examples - i'm sure others will join with even more weird setups :)

@freestyler
i see that you are using 64bit kernel for booting 32bit ISOs - there is nothing wrong with it (in fact this trick will let you take full advantages of 64bit kernels like better performance and no 4GB RAM limit). the only limitation is that you wont be able to use proprietary drivers. for people who need them would be better to unpack 32bit vmlinuz to /boot and use it for booting, like:

Code: Select all

LABEL kde32
MENU LABEL Testing 3.0 KDE 32bit
KERNEL vmlinuz-32
APPEND initrd=initrd.xz sgnfile=porteus-v3.0-i486.sgn changes=/porteus noload=xfce
(this way you also wont have to drop 64bit 000-kernel.xzm to 32bit /porteus/base)

Ive always thought about booting off iso but how does that work with adding modules?
extramod= is your friend like in Ed_P examples :)
Please add [Solved] to your thread title if the solution was found.

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

Re: Share your Bootloader Config

Post#5 by Ed_P » 02 May 2014, 06:51

freestyler wrote:Nice, Ive always thought about booting off iso but how does that work with adding modules?
Modules are added to the modules folder.

My folder/directory structure is:

d:\porteus
d:\porteus\changes
d:\porteus\modules
d:\porteus\modsavedat

The Porteus ISO is saved in d:\porteus directroy, the porteussave.dat file is saved in d:\porteus\changes, modules/extentions/additions are saved in d:\porteus/modules, and if a current but nonchangeable environment is desired a copy of the porteussave.dat file renamed to porteussave.dat.xzm is stored in d:\porteus\modsavedat.

Actually there is a 4th subfolder named d:/porteus/Guest which is a duplicate of the /home/guest folder/directory. The d: drive is a NTFS format partition.
Ed

User avatar
freestyler
Contributor
Contributor
Posts: 382
Joined: 17 Oct 2013, 14:21
Distribution: Porteus KDE4
Location: Traveller
Contact:

Re: Share your Bootloader Config

Post#6 by freestyler » 02 May 2014, 06:57

@fanthom: Thanks for pointing that out! I didnt even notice that. Really cool piece of info.

@Ed_P: Cheers! Im gonna have a play around with it.
https://www.porteus-apps.org

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

Re: Share your Bootloader Config

Post#7 by Ed_P » 02 May 2014, 12:57

freestyler wrote:@Ed_P: Cheers! Im gonna have a play around with it.
Some related info that may help setting it up is posted here: viewtopic.php?f=75&t=3384
Ed

User avatar
brokenman
Site Admin
Site Admin
Posts: 5550
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v3.2rcX all desktops
Location: Brazil
Contact:

Re: Share your Bootloader Config

Post#8 by brokenman » 03 May 2014, 18:52

Here is a shot f my sexy bootloader. It is the refind bootloader used for UEFI systems.

Image

The config file looks something like this:
"Boot into Dropline-3.10 TXT 64bit" "from=UUID:d2c78202-d77d-4fea-a793-e3758ed1b438/dropline-3.10 acpi=force initrd=\EFI\dropline-3.10\initrd.xz noload=003-lxde.xzm load=003-dropline.xzm"
How do i become super user?
Wear your underpants on the outside and put on a cape.

User avatar
freestyler
Contributor
Contributor
Posts: 382
Joined: 17 Oct 2013, 14:21
Distribution: Porteus KDE4
Location: Traveller
Contact:

Re: Share your Bootloader Config

Post#9 by freestyler » 04 May 2014, 01:01

Now that is sexy, To be honest I didn't expect anything less from ya brokenman.
https://www.porteus-apps.org

cttan
Shogun
Shogun
Posts: 332
Joined: 26 Jan 2011, 16:15
Distribution: Porteus 3.2 64bit KDE
Location: Malaysia

Re: Share your Bootloader Config

Post#10 by cttan » 06 May 2014, 14:21

@brokenman,
Really nice and sexy boot. I guess I will need the latest laptop to do that right?

My bootloader config:-

Code: Select all

LABEL mycopy2ram
MENU LABEL My Copy To RAM
KERNEL vmlinuz
APPEND initrd=initrd.xz copy2ram splash=silent vga=791 quiet noauto login=root ramsize=75% zram=25% volume=20% guiexec=sleep~5;/root/Desktop/000-init
TEXT HELP
    Run Porteus the same as above,	
    but first copy all data to RAM
    to get a huge speed increase
    (needs >768MB)
ENDTEXT
Is there a way for me to hide the loading process or to put it in a small window with tiny little text?

@Ed_p
Your config giving me new idea to boot my old P4 machine.
I have chucked it aside as I am not able to boot it using USB. No such option in BIOS.

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

Re: Share your Bootloader Config

Post#11 by donald » 06 May 2014, 17:35

@cttan
--> No such option in BIOS <--
How about using plop to boot an usb-flash?

Post Reply