Turbo Puppy: Texas Flood 2.5 Alpha is ready!

[lam777]

Here comes the english link, thanks for the Puppy Linux community and to Chase Rayfield:

http://texasflood.resulinux.com

[veronicathecow]

Hi, I'm very much an interested newbie so have not a clue what to do with this file.
Any help appreciated
Thanks
Tony

[Lobster]

Good luck with this

Have posted the link to Barry's blog

[Bert]

[cb88]

just extract the file and run the setup script from the command line just like the site says.

[veronicathecow]

Hi CB88, I am using 3.01 frugal on a twin boot (with PClinuxOS) on two HDD's
I followed instructions on unzipping etc and ran program.
Whilst it does boot faster the following does not work
No internet (No Ethernet card detected, I have 2)
No menus either by mouse click and also menu bar at bottom has disappeared. Gxine does not run.
At that point I gave up.
Hope this data is useful.
Thanks for your work in trying to get this on Puppy
Cheers

[cb88]

ok translated that and sent to luciano I think the problem is that some of the hardware detection got left out and zdrv.sfs is not being loaded correctly when drivers or codecs are needed...

[veronicathecow]

Thanks CB88. I forgot to mention that first boot took 29 seconds. I then booted again in case things needed to sort themselves out a bit and that took 44 seconds to boot, only 8 seconds faster than normal Puppy. I think it spent a long while doing something with UnionFS or other.
Cheers

[lam777]

In Regular linux systens, ifup -a turn on the network and the direct load of the modules can do that without a hardware detection tool...

Please send the result of the command:
cat /etc/texasflood-modules

If you are using a hardware detection tool, please modify the line modules_in_first_stage='1' to modules_in_first_stage='0' in /etc/texasflood.conf !!! This can speed up your boot time...

send /var/log/texas-flood ...

[veronicathecow]

Hi, results as follows, thanks
sh-3.00# cat /etc/texasflood-modules
Module
iptable_mangle
iptable_nat
ip_nat
xt_state
ipt_REJECT
ip_conntrack_ftp
ip_conntrack_irc
iptable_filter
ip_conntrack
ip_tables
snd_mixer_oss
usblp
via_rhine
snd_via82xx
gameport
snd_ac97_codec
ac97_bus
snd_pcm
snd_timer
snd_page_alloc
snd_mpu401_uart
snd_rawmidi
snd_seq_device
snd
soundcore
via_ircc
irda
crc_ccitt
8139too
mii
via_agp
agpgart
fuse
unionfs
nls_iso8859_1
nls_cp437
usbhid
usb_storage
ehci_hcd
uhci_hcd
usbcore
sr_mod
ide_cd
cdrom
squashfs
sh-3.00#

[veronicathecow]

Config file, hope this helps

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

#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"

#Command to call modules if necessary:
modules_command_call="/sbin/texasflood-call-modules"

#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=""

#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="60"

# [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 run the graphical interface:
gi_command="xwin"
#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="afterstep"
#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.

[lam777]

Type this commands and post the results(in a puppylinux+texas flood system)

bash --version

cat /etc/network/interfaces

cat /var/log/texas-flood

(and this command in a puppylinux regular system):
cat /proc/mounts

df -h

Thanks!

[veronicathecow]

Info as requested, thanks again. Tony

All these results are from a machine with Texas boot flood including the filesystem info at the end as this is the only machine with Puppy on at the moment. (Frugall 3.01 twin HDD)

sh-3.00# bash --version
GNU bash, version 3.00.16(1)-release (i486-t2-linux-gnu)
Copyright (C) 2004 Free Software Foundation, Inc.
sh-3.00#

sh-3.00# cat /etc/network/interfaces
cat: /etc/network/interfaces: No such file or directory
sh-3.00#

sh-3.00# cat /var/log/texas-flood
/sbin/texasflood-start: line 8: /proc/splash: No such file or directory
touch: cannot touch `/etc/network/run/ifstate': No such file or directory
nice: /etc/init.d/udev: No such file or directory
umount: cannot umount /dev/pts: Invalid argument
/sbin/texasflood-start: line 84: /etc/init.d/udev: No such file or directory
Balanceando prioridades para udevd...
This script will run X windows for you...
cat: /tmp/oldmousedevice: No such file or directory
Starting X, specs in /etc/X11/xorg.conf, startup apps /root/.xinitrc...
sh-3.00#

sh-3.00# cat /proc/mounts
rootfs / rootfs rw 0 0
/dev/hda1 /initrd/mnt/dev_save ext3 rw,noatime,data=ordered 0 0
/dev/loop1 /initrd/pup_rw ext2 rw,noatime 0 0
tmpfs /initrd/mnt/tmpfs tmpfs rw 0 0
/dev/loop0 /initrd/pup_ro2 squashfs ro,noatime 0 0
unionfs / unionfs rw,dirs=/initrd/pup_rw=rw:/initrd/pup_ro2=ro 0 0
tmpfs /tmp tmpfs rw 0 0
/proc /proc proc rw 0 0
sys /sys sysfs rw 0 0
/dev/pts /dev/pts devpts rw 0 0
/dev/hda3 /mnt/hda3 ext3 rw,data=ordered 0 0
sh-3.00#

sh-3.00# df -h
Filesystem Size Used Available Use% Mounted on
/dev/hda1 55.8G 15.1G 39.0G 28% /initrd/mnt/dev_save
/dev/loop1 495.8M 14.1M 481.7M 3% /initrd/pup_rw
tmpfs 79.1M 78.1M 1000.0k 99% /initrd/mnt/tmpfs
/dev/loop0 78.1M 78.1M 0 100% /initrd/pup_ro2
unionfs 495.8M 14.1M 481.7M 3% /
tmpfs 800.3M 20.0k 800.3M 0% /tmp
/dev/hda3 16.1G 5.0G 10.3G 33% /mnt/hda3
sh-3.00#

[byg]

just wondering if there was a fix for those problems?
byg

[cb88]

luciano has installed a copy of puppylinux and is poking around in the scripts figuring out what went wrong I'll tell you if i hear more

cb88

[veronicathecow]

Thanks CB88
I will be doing another install in a few days so will have another test machine

[cb88]

Ok just got an update. Luciano is on a slow internet connection so downloading puppy takes a while...

From what he has seen puppy does not boot like anything he has seen...
contrary to his former belief.

he said that he is finding how puppy boots quite interesting so perhaps there is hope yet!!

I am amazed that he even got puppy to boot in the first place after messing with the boot scripts so much

and finally there may be a command to remove texasflood already it may be texasflood-reboot but I am not sure that it is in the current version of texasflood

[ChechenPuppy]

Thank you for this guys! Good job!

[lam777]

Download complete, texas flood go to a stable version in the next week.

[veronicathecow]

Many thanks, eagerly await any news
Cheers