Boot up search for Tahr puppy files takes too long
Boot up search for Tahr puppy files takes too long
This is 4-TB hard drive, so I have to boot from a CD. (Puppy bootloaders won't work.) I have a 30-GB boot partition on the drive, and keep Tahr puppy files there in a dedicated directory, Tahr-6.0.5. There is another directory on this partition for Slacko 5.7. Both are frugal installs that boot from CD. While it takes only 12 seconds to find Slacko files, it takes 47 seconds to search for Tahr puppy files during the boot. Is there a setting where I can direct the search to look inside the dedicated Tahr directory?
something like this?
Code: Select all
kernel /DpupStretchOsc/vmlinuz pmedia=cd pfix=fsck psubdir=/DpupStretchOsc/ pdev1=sda9
Try changing the name of the directory to the name that is used when you do a frugal install.
depending on which version you are using.
Also, change the name of the Slacko directory too.
depending on which version you are using.
If the directories are on the first partition of the hard drive, they should get found quicker.
Code: Select all
tahr605_PAE
tahr605_noPAEdepending on which version you are using.
Also, change the name of the Slacko directory too.
Code: Select all
slacko570PAE
slacko57NOpaeIf the directories are on the first partition of the hard drive, they should get found quicker.
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
Hi nubc.
This is what I have for petihar's Triton, which is a tahrpup in essence.
The following lines find very quickly the "Triton" directory where all the files for this
tahrpup are.
I have regular quotes around the target directory, though; not diagonals ("/"),
like foxpup.
I also have the habit of putting the vmlinuz and initrd,gz files "in the basement"
of where the sfs files are. This is the tree of directory "Triton-6.0-def2":
I am not sure this speeds up the boot, but I've been using such a structure for years.
Hopefully, this page will take the mystery out of it.
http://puppylinux.org/wikka/BootParameters
I hope this helps.
This is what I have for petihar's Triton, which is a tahrpup in essence.
The following lines find very quickly the "Triton" directory where all the files for this
tahrpup are.
I have regular quotes around the target directory, though; not diagonals ("/"),
like foxpup.
Code: Select all
# 07
title Triton (définitif2), par petihar
root (hd0,0)
kernel (hd0,0)/Triton-6.0-def2/lance/vmlinuz quiet pkeys=cf pmedia=satahd root=/dev/ram0 pdev1=sda1 psubdir="Triton-6.0-def2" pfix=fsck,nocopy
initrd (hd0,0)/Triton-6.0-def2/lance/initrd.gz
bootof where the sfs files are. This is the tree of directory "Triton-6.0-def2":
(Before you ask, "lance" means "launch" in French.).
./lance
./lance/boot.cat
./lance/boot.msg
./lance/help2.msg
./lance/help.msg
./lance/initrd.gz
./lance/isolinux.bin
./lance/isolinux.cfg
./lance/logo.16
./lance/README.HTM
./lance/vmlinuz
./devx_tahr_6.0.5.sfs
./puppy_tahr_6.0.5.sfs
./tahrsave-babebi.2fs
./zdrv_tahr_6.0.5.sfs
I am not sure this speeds up the boot, but I've been using such a structure for years.
Hopefully, this page will take the mystery out of it.
http://puppylinux.org/wikka/BootParameters
I hope this helps.
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
Changing the name of the directory had no effect on the long search for files. In fact I neglected to put the files in any directory at first, and still the search was 47 seconds. It would be pointless to change anything about the Slacko directory and files since those files are found in 12 seconds.
Last edited by nubc on Sat 25 Nov 2017, 05:39, edited 1 time in total.
There exists a boot directory in the file system which contains a file named system.map, containing the assignments for the first 64k memories. Can I create a file in this boot directory to direct the search to the tahr directory? {Probably not useful]
A reminder: There is no GRUB or Grub4DOS on this computer. If you recommend text, kindly include a location for placing the text.
A reminder: There is no GRUB or Grub4DOS on this computer. If you recommend text, kindly include a location for placing the text.
Last edited by nubc on Sat 25 Nov 2017, 17:39, edited 1 time in total.
To totally understand.
What is on this CD you boot with?
How is it used to boot?
You do what?
You see what?
That 12 second search time indicates something is making it not search the entire drive.
That 47 second search time indicates it is searching the entire drive.
What is on this CD you boot with?
How is it used to boot?
You do what?
You see what?
That 12 second search time indicates something is making it not search the entire drive.
That 47 second search time indicates it is searching the entire drive.
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
I changed the name a few times, and now the search time is 51 seconds. There is a fsckme.flg text file on the partition with the two savefile directories, and this text changes with the current OS, reading the last OS loaded.
The CD is the installation/liveCD that you burn from the downloaded ISO image. Please don't try to complicate the identity of the CD any further. The CD is nothing special, and the burn program has closed the disk. You can't write to this CD. I boot up the CD, get a Tahr 6.0.5 splash screen (at which point I can manually change boot parameters), then vmlinuz and initrd.gz are loaded, some file decompression, loading needed driver files, then follows the search for Puppy files.
The CD is the installation/liveCD that you burn from the downloaded ISO image. Please don't try to complicate the identity of the CD any further. The CD is nothing special, and the burn program has closed the disk. You can't write to this CD. I boot up the CD, get a Tahr 6.0.5 splash screen (at which point I can manually change boot parameters), then vmlinuz and initrd.gz are loaded, some file decompression, loading needed driver files, then follows the search for Puppy files.
Last edited by nubc on Sat 25 Nov 2017, 17:41, edited 4 times in total.
So, what are you changing the boot parameters too?I boot up the CD, get a Tahr 6.0.5 splash screen, at which point I can manually change boot parameters
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
Probably just to spite you...nubc wrote:I just say, it's a point in the boot that one can change the boot parameters, not that I am changing the boot parameters.
The Slacko search for files is now 36 seconds.
But seriously, have you looked at the settings for the lilo (or whatver the loader is
called when booting from CD)? Does it have the equivalent of the
< psubdir="/path/to/things/and/stuff" > setting that exists on GRUB4DOS?
If not, you add this parameter to the command line and you burn another CD.
You're not going to use that CD to boot on another machine, are you?
CD boots do search entire drives by design.
BFN.
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
musher,
I don't know what you're talking about, but I will reiterate that there is no grub, lilo, or grub4dos on this computer. Whether the CD has a bootloader, I do not know. The CD boots like a liveCD, only when it looks for files, it looks for tahr files saved to hard drive. not .sfs files on the CD. As far as I know, the CD is booted by the computer's BIOS and firmware.
I don't know what you're talking about, but I will reiterate that there is no grub, lilo, or grub4dos on this computer. Whether the CD has a bootloader, I do not know. The CD boots like a liveCD, only when it looks for files, it looks for tahr files saved to hard drive. not .sfs files on the CD. As far as I know, the CD is booted by the computer's BIOS and firmware.
Last edited by nubc on Sat 25 Nov 2017, 16:24, edited 2 times in total.
Perhaps you need to learn how to communicate
Hi nubc,
You have frequently asked questions. You have frequently been asked by bigpup, "What do you do? What do you see?" If you've read bigpup's responses on other threads of questions asked by others, or perhaps yourself, he has explained the reason for those questions which I've sometimes either quoted or paraphrased as: "You are our eyes and hands. We can only know what you tell us. We can only try something on your computer if you do it."
You've told us that you boot Tahrpup using a CD with Tahrpup's files in a folder on your computer's hard drive. You have posted 6 time on this thread. You have still not told us what program you used to burn the CD, what bootloader was written to the CD, or what boot arguments exist on the CD.
To quote or paraphrase Donald Rumsfeld: "There are things we know. There are things we don't know. And there are things we don't know we don't know."
When something isn't working the way you think it should and you don't know why you should assume that most of the information about Puppy falls into the category of "things you don't know you don't know".
Just a hint: There are more ways than one to burn a CD.
mikesLr
You have frequently asked questions. You have frequently been asked by bigpup, "What do you do? What do you see?" If you've read bigpup's responses on other threads of questions asked by others, or perhaps yourself, he has explained the reason for those questions which I've sometimes either quoted or paraphrased as: "You are our eyes and hands. We can only know what you tell us. We can only try something on your computer if you do it."
You've told us that you boot Tahrpup using a CD with Tahrpup's files in a folder on your computer's hard drive. You have posted 6 time on this thread. You have still not told us what program you used to burn the CD, what bootloader was written to the CD, or what boot arguments exist on the CD.
To quote or paraphrase Donald Rumsfeld: "There are things we know. There are things we don't know. And there are things we don't know we don't know."
When something isn't working the way you think it should and you don't know why you should assume that most of the information about Puppy falls into the category of "things you don't know you don't know".
Just a hint: There are more ways than one to burn a CD.
mikesLr
I'm not new to Puppy, you can scold me how you like. I've been using Puppy for over 10 years. I use the program BurnISO2CD to burn the iso that I downloaded. Just like that, nothing extra. The same CD for installation and liveCD. If there are variations on burning boot CDs I'm not familiar with them.
On the CD, I see isolinux.bin, isolinux.cfg, boot.cat, boot.msgnubc wrote: As far as I know, the CD is booted by the computer's BIOS and firmware.
mike, have you ever tried to boot puppy on a 4-TB drive? This has a GPT partition table. Traditional Puppy bootloaders won't work.
This is a standard installation/liveCD. No bootloader was written to the CD, and the burn program closed the CD, so I presume it's not writable.
THE CD IS THE BOOTLOADER
What bootloader is used to boot a live CD? Isolinux, is that the bootloader?
Maybe I should burn another CD, append isolinux?
Last edited by nubc on Sat 25 Nov 2017, 17:42, edited 8 times in total.
Re: Perhaps you need to learn how to communicate
To stay off-topic: 
view of what we will never know." [Evgueni Evtouchenko, Wild Berries of Siberia]
Back on topic:
@nubc:
Please, nobody is trying to scold you.
There exists a boot loader in the ISO image of any Puppy.
For the tahrpup-6.0.5, it's isolinux. I just checked.
This is its configuration file:
after "pmedia=cd", such as psubdir. Then we could reburn the CD and hopefully
isolinux will locate the subdir quickly.
Any isolinux expert, please take a step forward?!
Which reminds me of: "All our knowledge, past, present and future, is nothing inmikeslr wrote: (...) To quote or paraphrase Donald Rumsfeld: "There are things we know. There are
things we don't know. And there are things we don't know we don't know."
(...)mikesLr
view of what we will never know." [Evgueni Evtouchenko, Wild Berries of Siberia]
Back on topic:
@nubc:
Please, nobody is trying to scold you.
There exists a boot loader in the ISO image of any Puppy.
For the tahrpup-6.0.5, it's isolinux. I just checked.
This is its configuration file:
I have never done this, but I am pretty sure that we could add more boot parametersdefault puppy
display boot.msg
prompt 1
timeout 50
F1 boot.msg
F2 help.msg
F3 help2.msg
label puppy
kernel vmlinuz
append initrd=initrd.gz pmedia=cd
after "pmedia=cd", such as psubdir. Then we could reburn the CD and hopefully
isolinux will locate the subdir quickly.
Any isolinux expert, please take a step forward?!
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
Making progress. I still say the CD is the bootloader, or perhaps the boot device. I wish the boot would follow the fsckme.flg file that keeps track of the location of the files found during the last boot.
http://www.syslinux.org/wiki/index.php?title=Config
http://www.syslinux.org/wiki/index.php?title=Config
You are basically booting with a live Puppy CD.
The boot loader files are on the CD.
The only files it will look for on a hard drive are the save and the main Puppy sfs if you put it on the hard drive.
Not sure why you put everything in a Directory on the hard drive.
The better option would be when making the save for the first time it also asks if you want the Puppy main sfs files also put on the hard drive.
That is suppose to make it boot quicker, because the hard drive access is faster than a CD drive.
Try this just to see what happens.
Copy the Tahrpup save and the Tahrpup sfs and zdrv sfs onto the first partition of the hard drive.
Just have them on the partition and not in any directory.
What happens??
The boot loader files are on the CD.
The only files it will look for on a hard drive are the save and the main Puppy sfs if you put it on the hard drive.
Not sure why you put everything in a Directory on the hard drive.
The better option would be when making the save for the first time it also asks if you want the Puppy main sfs files also put on the hard drive.
That is suppose to make it boot quicker, because the hard drive access is faster than a CD drive.
Try this just to see what happens.
Copy the Tahrpup save and the Tahrpup sfs and zdrv sfs onto the first partition of the hard drive.
Just have them on the partition and not in any directory.
What happens??
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
All three files have been on the hard drive since the first "installation." For maybe the first 10 boots, the 3 Tahr files were not in a directory. Makes no difference. In fact, it was you who advised me to keep the files in their own Tahr directory, like you keep yours. Every time I change a file name, it claims next boot will be faster, but it's not faster at all. I put the three Tahr files in a directory because two Slacko files also reside here (in a Slacko directory).
I still think there is something you are not telling us, but i have no idea, what it is, at this point.
Tahrpup was being developed, around the time there was a lot of discussion, about how much searching for Puppy files would be done, when booting with a live Puppy CD/DVD.
Should it only search one directory(folder) deep?
Two directory(folder) deep?
Just search the entire hard drive, every possible place.
Tahrpup could be using the option to search every possible place on the hard drive.
That would take a lot of time with a 4TB drive.
Slacko may be using the option to search only two directories(folders) deep.
Can you put Puppy on a USB flash drive and boot with that?
It can be written to.
That way, you could modify boot options in the boot loader.
Also, you can frugal install any number of Puppies to a USB flash drive and use Grub4dos bootloader, installed on the flash drive, to boot it.
Example:
A 32GB usb flash drive with frugal installs of Puppy and Grub4dos as boot loader.
The menu.lst
Tahrpup was being developed, around the time there was a lot of discussion, about how much searching for Puppy files would be done, when booting with a live Puppy CD/DVD.
Should it only search one directory(folder) deep?
Two directory(folder) deep?
Just search the entire hard drive, every possible place.
Tahrpup could be using the option to search every possible place on the hard drive.
That would take a lot of time with a 4TB drive.
Slacko may be using the option to search only two directories(folders) deep.
Can you put Puppy on a USB flash drive and boot with that?
It can be written to.
That way, you could modify boot options in the boot loader.
Also, you can frugal install any number of Puppies to a USB flash drive and use Grub4dos bootloader, installed on the flash drive, to boot it.
Example:
A 32GB usb flash drive with frugal installs of Puppy and Grub4dos as boot loader.
The menu.lst
# menu.lst produced by grub4dosconfig-v1.9.2
color blue/cyan yellow/blue white/black cyan/black
#splashimage=/splash.xpm
timeout 10
default 0
# Frugal installed Puppy
title Puppy artfulpup 17.10.01 (sdd1/artfulpup171001+4)
find --set-root --ignore-floppies --ignore-cd /artfulpup171001+4/initrd.gz
kernel /artfulpup171001+4/vmlinuz psubdir=artfulpup171001+4 pmedia=usbflash pfix=fsck
initrd /artfulpup171001+4/initrd.gz
title Puppy tahr 6.0.6 (sdd1/tahr606uefi)
find --set-root --ignore-floppies --ignore-cd /tahr606uefi/initrd.gz
kernel /tahr606uefi/vmlinuz psubdir=tahr606uefi pmedia=usbflash pfix=fsck
initrd /tahr606uefi/initrd.gz
title Puppy xenialpup 7.0.8.1 (sdd1/xenialpup7081uefi)
find --set-root --ignore-floppies --ignore-cd /xenialpup7081uefi/initrd.gz
kernel /xenialpup7081uefi/vmlinuz psubdir=xenialpup7081uefi pmedia=usbflash pfix=fsck
initrd /xenialpup7081uefi/initrd.gz
title Puppy precise 5.7.1 (sdd2/precise571)
find --set-root --ignore-floppies --ignore-cd /precise571/initrd.gz
kernel /precise571/vmlinuz psubdir=precise571 pmedia=usbflash pfix=fsck
initrd /precise571/initrd.gz
title Puppy xenialpup64 7.0.8.5 (sdd2/xenialpup647085uefi)
find --set-root --ignore-floppies --ignore-cd /xenialpup647085uefi/initrd.gz
kernel /xenialpup647085uefi/vmlinuz psubdir=xenialpup647085uefi pmedia=usbflash pfix=fsck
initrd /xenialpup647085uefi/initrd.gz
title Puppy xenialpup64 7.0.8.6 (sdd2/xenialpup647086)
find --set-root --ignore-floppies --ignore-cd /xenialpup647086/initrd.gz
kernel /xenialpup647086/vmlinuz psubdir=xenialpup647086 pmedia=usbflash pfix=fsck
initrd /xenialpup647086/initrd.gz
# Full installed Linux
# Advanced Menu
title Advanced menu
configfile /menu-advanced.lst
commandline
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)