Turbo puppy is coming with texasflood
Turbo puppy is coming with texasflood
I have been asked to translate texasflood to english and the developer has offered to make it compatable with puppy.
progress reports will be posted here if you wish to talk about texasflood continue to use the texasflood thread.
texasflood has the potential to make puppy boot so fast that makes windows look like a snail shot up with traquilizers so this is definitely a good thing
progress reports will be posted here if you wish to talk about texasflood continue to use the texasflood thread.
texasflood has the potential to make puppy boot so fast that makes windows look like a snail shot up with traquilizers so this is definitely a good thing
Taking Puppy Linux to the limit of perfection. meanwhile try "puppy pfix=duct_tape" kernel parem eater.
X86: Sager NP6110 3630QM 16GB ram, Tyan Thunder 2 2x 300Mhz
Sun: SS2 , LX , SS5 , SS10 , SS20 ,Ultra 1, Ultra 10 , T2000
Mac: Platinum Plus, SE/30
X86: Sager NP6110 3630QM 16GB ram, Tyan Thunder 2 2x 300Mhz
Sun: SS2 , LX , SS5 , SS10 , SS20 ,Ultra 1, Ultra 10 , T2000
Mac: Platinum Plus, SE/30
From the developer (Luciano Andress Martini) about the name of Texas Flood.:
I was thinking of American culture... and since i am making a universal program why not use that in the name since America generally seems to be a standard that is well accepted.
Texas because I heard that the storms in Texas are violent like the program..(in a good way, an extremely fast boot) , Flood because it is a of the "flood" of start up components that are started at the same time thus making the boot go faster.
I hope that the name is not inadequate for American culture if it is we may consider changing it.
I was thinking of American culture... and since i am making a universal program why not use that in the name since America generally seems to be a standard that is well accepted.
Texas because I heard that the storms in Texas are violent like the program..(in a good way, an extremely fast boot) , Flood because it is a of the "flood" of start up components that are started at the same time thus making the boot go faster.
I hope that the name is not inadequate for American culture if it is we may consider changing it.
Taking Puppy Linux to the limit of perfection. meanwhile try "puppy pfix=duct_tape" kernel parem eater.
X86: Sager NP6110 3630QM 16GB ram, Tyan Thunder 2 2x 300Mhz
Sun: SS2 , LX , SS5 , SS10 , SS20 ,Ultra 1, Ultra 10 , T2000
Mac: Platinum Plus, SE/30
X86: Sager NP6110 3630QM 16GB ram, Tyan Thunder 2 2x 300Mhz
Sun: SS2 , LX , SS5 , SS10 , SS20 ,Ultra 1, Ultra 10 , T2000
Mac: Platinum Plus, SE/30
- Lobster
- Official Crustacean
- Posts: 15522
- Joined: Wed 04 May 2005, 06:06
- Location: Paradox Realm
- Contact:
What you are trying to say and what you have conveyed (communicated) are different.
Texas Flood sounds mostly like severe wet weather in Texas. It makes little sense.
Many names make little sense.
It is a memorable name and that is far more important
However trying to convey (translate) what you wish to say I would suggest:
BootUSA (that too has a double meaning)
This is where USA stands for
Ultra Swift Access
Texas Flood sounds mostly like severe wet weather in Texas. It makes little sense.
Many names make little sense.
It is a memorable name and that is far more important
However trying to convey (translate) what you wish to say I would suggest:
BootUSA (that too has a double meaning)
This is where USA stands for
Ultra Swift Access
Last edited by Lobster on Mon 29 Oct 2007, 17:05, edited 2 times in total.
Well the name is fine no need to change it even if you don't quite understand why it is named what it is....it not hard to remember just be thankful the didn't choose some south aribic words....then most of us couldn't even read then....
you aren't spreading much puppytude lobster and that's your word isn't it?
texas flood makes a lot more sense that half the names of linux programs lets not nit pick
although I do prefer beryl to compiz-fusion (where is teh sense in that name?)
anyhow texas flood is not a program that i think will need to be accessed much by the user and if so then we'll append "boot accelerator" to the name that is kind of obvious.
you aren't spreading much puppytude lobster and that's your word isn't it?
texas flood makes a lot more sense that half the names of linux programs lets not nit pick
although I do prefer beryl to compiz-fusion (where is teh sense in that name?)
anyhow texas flood is not a program that i think will need to be accessed much by the user and if so then we'll append "boot accelerator" to the name that is kind of obvious.
Taking Puppy Linux to the limit of perfection. meanwhile try "puppy pfix=duct_tape" kernel parem eater.
X86: Sager NP6110 3630QM 16GB ram, Tyan Thunder 2 2x 300Mhz
Sun: SS2 , LX , SS5 , SS10 , SS20 ,Ultra 1, Ultra 10 , T2000
Mac: Platinum Plus, SE/30
X86: Sager NP6110 3630QM 16GB ram, Tyan Thunder 2 2x 300Mhz
Sun: SS2 , LX , SS5 , SS10 , SS20 ,Ultra 1, Ultra 10 , T2000
Mac: Platinum Plus, SE/30
The "flood" part makes perfect sense. Okay, maybe not perfect, but it fits and it sounds cool. "Texas" is questionable in relevance, but the overall name sounds fine to me. Besides, who say names have to make sense?
I'm really excited about an even faster booting Puppy. It already does circles around the XP boot times. I always seem to forget just how slow XP loads until I need to do something on my Windows box. Anyway, I'm really looking forward to trying this thing out.
I'm really excited about an even faster booting Puppy. It already does circles around the XP boot times. I always seem to forget just how slow XP loads until I need to do something on my Windows box. Anyway, I'm really looking forward to trying this thing out.
Be brave that God may help thee, speak the truth even if it leads to death, and safeguard the helpless. - A knight's oath
Re: Turbo puppy is coming with texasflood
...the texasflood threadcb88 wrote: progress reports will be posted here if you wish to talk about texasflood continue to use the texasflood thread.
[url=http://pupsearch.weebly.com/][img]http://pupsearch.weebly.com/uploads/7/4/6/4/7464374/125791.gif[/img][/url]
[url=https://startpage.com/do/search?q=host%3Awww.murga-linux.com%2F][img]http://i.imgur.com/XJ9Tqc7.png[/img][/url]
[url=https://startpage.com/do/search?q=host%3Awww.murga-linux.com%2F][img]http://i.imgur.com/XJ9Tqc7.png[/img][/url]
If you are looking for a dangerous water/wind related name ... how about:
FlashFlood (my favorite ... can happen very fast without Any warning signs)
MicroBurst (nice for a small very fast app. .... no warning with this one either)
Twister (TexasTwister?)
Deluge
or fire lated:
FireStorm (my favorite)
FlashPoint
FlashOver
Lightnin"
or winter related:
BlackIce (my favorite ... you can't see it .... then you are out of control)
WhiteOut
40Below (zero)
non-weather related:
FlashBoot
MicroBlast
QuikSand
QuikBoot
QuikFuse
QuikStart
KickStart
ShortFuse
LiveWire
LiveBoot
SwiftBoot
MicroFlash
FlashBo (my wife's version of flash boot)
Majik (the name or our small, fast black cat)
BlkMajik
I didn't check out copyright issues.
I like unique names I can remember ..... but you can call it 4ReD .... I'd just like to test drive it with a Pup !
Thanks for the hard work.
KJ
FlashFlood (my favorite ... can happen very fast without Any warning signs)
MicroBurst (nice for a small very fast app. .... no warning with this one either)
Twister (TexasTwister?)
Deluge
or fire lated:
FireStorm (my favorite)
FlashPoint
FlashOver
Lightnin"
or winter related:
BlackIce (my favorite ... you can't see it .... then you are out of control)
WhiteOut
40Below (zero)
non-weather related:
FlashBoot
MicroBlast
QuikSand
QuikBoot
QuikFuse
QuikStart
KickStart
ShortFuse
LiveWire
LiveBoot
SwiftBoot
MicroFlash
FlashBo (my wife's version of flash boot)
Majik (the name or our small, fast black cat)
BlkMajik
I didn't check out copyright issues.
I like unique names I can remember ..... but you can call it 4ReD .... I'd just like to test drive it with a Pup !
Thanks for the hard work.
KJ
- veronicathecow
- Posts: 559
- Joined: Sat 21 Oct 2006, 09:41
luciano claims to have increased the performance even more!!!
we are getting close!
here is texasflood.conf
#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.
we are getting close!
here is texasflood.conf
#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.
Taking Puppy Linux to the limit of perfection. meanwhile try "puppy pfix=duct_tape" kernel parem eater.
X86: Sager NP6110 3630QM 16GB ram, Tyan Thunder 2 2x 300Mhz
Sun: SS2 , LX , SS5 , SS10 , SS20 ,Ultra 1, Ultra 10 , T2000
Mac: Platinum Plus, SE/30
X86: Sager NP6110 3630QM 16GB ram, Tyan Thunder 2 2x 300Mhz
Sun: SS2 , LX , SS5 , SS10 , SS20 ,Ultra 1, Ultra 10 , T2000
Mac: Platinum Plus, SE/30
The program is ready, now we need to translate the libraries for the correct display of logs...
The Texas Flood Librarie is so small....
and i think it can be translated fast...
Lobster and KJ thanks for the names, i will think about it in the next version...
Thanks to Chase Rayfield and Puppy Linux community.. ![]
Sorry for the poor english...
Thanks ! =]
A complete english website for texas flood will be created...
The Texas Flood Librarie is so small....
and i think it can be translated fast...
Lobster and KJ thanks for the names, i will think about it in the next version...
Thanks to Chase Rayfield and Puppy Linux community.. ![]
Sorry for the poor english...
Thanks ! =]
A complete english website for texas flood will be created...
- darrelljon
- Posts: 551
- Joined: Sun 08 Apr 2007, 11:10
- Contact:
Here comes the Library:
In the next week, you can download texas flood and try it on Puppy Linux.
Code: Select all
(c) 2007 Luciano Andress Martini
Translated to english by: Chase Rayfield
reniceall(){
#By Luciano Andress Martini... alters the priorities of various processes
for pr in "`ps -A | grep $2 | sed 's/[ ]\+/ /g'| cut -d" " -f2 `"; do
echo "Balancing priorities for $2..."
renice $1 $pr 2>/dev/null
done
}
showpid(){
#Shows the pid of a process by its name
#Use: showpid process
for pr in "`ps -A | grep $1 | sed 's/[ ]\+/ /g'| cut -d" " -f2 `"; do
echo $pr
done
}
wait_for_kill(){
while ps -A | grep $1; do
usleep 100000
done
}
wait_for(){
cx=0
if [ "$2" != "" ]; then
echo -n "Waiting until $(($2/10)) seconds for $1... "
while ! ps -A | grep $1 &>/dev/null; do
cx="$((1+$cx))"
[ "$cx" -gt "$2" ] && echo "Time limit ran out..." && return 0
usleep 100000
done
echo Ok.
else
echo -n "Waiting for $1..."
while ! ps -A | grep $1 &>/dev/null; do
usleep 100000
done
echo "Ok."
fi
}
wait_for_event(){
while ! $*; do
usleep 100000
done
}
superhdparm(){
cd /proc/ide
for ide in hd*; do
hdparm $* /dev/$ide
done
}
Thanks for your hard work Luciano and Chase!
I'm but an end user, so don't understand most of the poetry in your code, but this
sounds good! Can hardly wait for this event, okay?
I'm but an end user, so don't understand most of the poetry in your code, but this
Code: Select all
wait_for_event(){
echo "Ok!!!"
[url=http://pupsearch.weebly.com/][img]http://pupsearch.weebly.com/uploads/7/4/6/4/7464374/125791.gif[/img][/url]
[url=https://startpage.com/do/search?q=host%3Awww.murga-linux.com%2F][img]http://i.imgur.com/XJ9Tqc7.png[/img][/url]
[url=https://startpage.com/do/search?q=host%3Awww.murga-linux.com%2F][img]http://i.imgur.com/XJ9Tqc7.png[/img][/url]