home Back to MiniWiki

Command Line Options

We provide various ways to influence how the operating system behaves before it even starts. this is done via the cmd-line argument within the bootloader. this is typically enabling and or disabling features within the operating system that perhaps your hardware may not support. It also just provides features that give you control in regards to how your machine behaves.

providing invalid values usually stops the machine from booting or just causes weird behavour, so make sure you know what your doing ish.

it is expected that arguments are written in the following format

name=value

names and values are case sensitive, and there musn't be a space between the = either
all names and values are expected in lowercase so you shouldn't need to ever use caps anyway

init

expects a valid path to an ELF executable

Allows you to define the first program that bleed will load first and is intended to hand off to userspace. this is by default set to 'init=default' where 'default' is a macro for '/initrd/bin/verdict'. as by default it will try to load the Verdict Shell. this can be changed to any valid process.

If the path is invalid or it fails to load the process, there is no warning and it will just present you with a black screen. an example of how this can be used is, if you really just want to play doom you can set 'init' ro '/initrd/bin/doom' and it will just start doom.

smap

expects 'no'

The Kernel will automatically identify if your Processor Supports Supervisor Mode Access Prevention but if for whatever reason it is causing problems, you can disable it

if this entry is missing, the kernel will decide

umip

expects 'no'

The Kernel will automatically identify if your Processor Supports Usermode Instruction Prevention but if for whatever reason it is causing problems, you can disable it

if this entry is missing, the kernel will decide

splash

expects either bgra, bleed or no

if you have a machine with a Boot Graphics Resource Table within the ACPI implementation then bleed can use that logo upon booting, if it fails to find it, it'll fall back to its own. however you can force bleed to use the bgra table by setting this value to bgra or likewise you can force it to use the default bleed image by setting this value to simply bleed, or you can just turn it off by setting it to 'no'

if no BGRA image is available and the splash image is specifically set to BGRA, it will display nothing.

ttyfont

expects a valid PSF font path

if you have a font that you would like to use from the get go you can provide this value by setting the path of that font to ttyfont in the cmd-line bleed provides another valid font in "/initrd/fonts/alternative.psf" if you really want to try it out, but if you have your own, provide that path.