Last Edited: 01 May 2008 by superuser
Importered from old WiKi -- 30/04-08 18:04.

Texas Flood is a boot accelerator that is being ported to puppy linux

here are some of the conf files

#Texas Flood configuration file - /etc/texasflood.conf
#(c) 2007 Luciano Andress Martini
#Translated to English by: Cb88

#How to edit this file?
#This file contains the runtime variables for Texas Flood.
#It allow Texas Flood to optimize your machine for exactly your type of work.
#When you edit this file be careful so you do not adversely affect your system performance.
#Many conditions placed in this file can have two values 1 or 0.
#1 means yes and 0 means no.
#We hope you now feel comfortable editing this configuration file.

# [Hardware detection]

#Need to pre-load modules:
#Modules are normally only loaded after the second stage after the load
#of the graphical system or when the system is ready.
#some systems need to load a module even before Texas Flood is
#started because they do not have hardware detection.
modules_in_first_stage="0"

#It is recommended that you use UDEV for Texas Flood to function adequately.
#Use this variable to define the command used to run UDEV. If you don't have UDEV leave it blank.
#Caution: Never define a command that runs a program other than UDEV, it will break Texas Flood.
call_udev="/etc/init.d/udev start"

#It is possible to use an extra command to detect hardware weather UDEV is active or not.
#This is also useful for distributions that do not have UDEV.
#Example: command_to_probe_hardware='/sbin/hwsetup'
command_to_probe_hardware=""

# [Mount partitions]

#Presence of HAL
#Define the command that runs HAL here:
#Leave this variable blank of you do not have HAL.
call_hal="/etc/init.d/dbus start"

#Use a separate home.
#Yes, it is necessary to define this in order for Texas Flood to work.
#Leave this blank if your home is not in a separate partition.
#Use the /dev/hdaX format if you have a home partition.
home_partic=

# [Memory]
#Use virtual memory?
swap="1"

#Define the tendency for the system to move programs into swap/virtual memory.
#Higher numbers are recommended for machines with low ram.
#Lower numbers are recommended for machines with lots of ram.
swappiness="70"

# [Stages and Priority]
#Define the stages that will be loaded and their priorities here:

#Stage 1: Stage one is directly linked to startup and initialization of the more basic components.
#NOTE: The priorities range from -20(highest) to 20 (lowest)
#Negative values define higher priorities as shown.
#Activate Stage 1:
S1="1"
#Priority of Stage 1:
S1_PRIORITY="0"

#Stage 2: Stage two is related to Xorg.
#NOTE: The priorities range from -20(highest) to 20 (lowest)
#Negative values define higher priorities as shown.
#Activate Graphical interface.
gi="1"
#Command to runt the graphical interface:
gi_commmand="kdm"
#Priority of programs that run under Xorg.
xorg_prog_priority="-4"
#CPU priority that Xorg uses to draw graphics, produce animations or display videos.
xorg_video_priority="-20"

#Stage 3: Stage 3 occurs after X has completely loaded, if X is active.
#NOTE: The priorities range from -20(highest) to 20 (lowest)
#Negative values define higher priorities as shown.
#Activate stage 3:
S3="1"
#Process to be preloaded before Stage 3 starts:
#By default we put kicker which is the task bar for KDE.
wait_process="kicker"
#Maximum time to wait for the process in tenths of a second.
#300 means 30 seconds.
limit_wp="300"
#Priority of Stage 3:
S3_PRIORITY="0"

# [Others]
#Activate network and internet support:
network="1"

#Define the keyboard map here:
keymap="us"

#Activate power management here:
acpi="0"
apm="0"

#Check disks? (Still in development)
check_disks="0"

#Activate Ultra DMA
udma="1"

# [Extra Commands]
#Literally, type which commands should be executed before Texas Flood loads below.
#If your system has presented any Problem.



CategoryApplications