The time now is Sat 14 Dec 2019, 22:13
All times are UTC - 4 |
Page 1 of 2 [25 Posts] |
Goto page: 1, 2 Next |
Author |
Message |
Smithy

Joined: 12 Dec 2011 Posts: 1076
|
Posted: Thu 17 Oct 2019, 19:41 Post subject:
How to remove "Searching For Puppy Files" from boot process? |
|
How to Remove this dialogue from boot process?
I have looked in rc sysnit, and initrd.gz but can't find it.
|
Back to top
|
|
 |
Flash
Official Dog Handler

Joined: 04 May 2005 Posts: 13399 Location: Arizona USA
|
Posted: Thu 17 Oct 2019, 22:13 Post subject:
|
|
Would booting with puppy pfix=ram be what you're looking for?
|
Back to top
|
|
 |
anewuser
Joined: 05 Feb 2012 Posts: 89
|
Posted: Fri 18 Oct 2019, 07:29 Post subject:
|
|
More likely he is looking for the script where the string "Searching for puppy files..." comes from.
It must be encoded or compressed.
|
Back to top
|
|
 |
Mike Walsh

Joined: 28 Jun 2014 Posts: 5668 Location: King's Lynn, UK.
|
Posted: Fri 18 Oct 2019, 08:41 Post subject:
|
|
@ Smithy:-
Use jrb's pupbuild-tools
http://murga-linux.com/puppy/viewtopic.php?mode=attach&id=32784&sid=2b3f5b2c887dce052be2094d42ea331d (direct link)
.....from here:-
http://www.murga-linux.com/puppy/viewtopic.php?t=60180
jrb explains how to use them in the first post.
You need to look in the 'init' script inside the initrd.gz. I can only quote from experience, but in Precise 571's 'init' the first mention of the $string 'Searching for Puppy files...' is around line 750 or so. It's a hell of a lot further down the script than you would think; from what I can see of it, the whole of the script above that is to do with setting localizations, detecting drives (via loading various kernel modules for different interfaces), and looking for Puppy 'save' files/folders.
I guess it depends on the Pup in question, but from what I can see of it, all Pups are using variations on the same script, since some of the 'comments' date right back to 2006....
I've just recently been using jrb's 'toolkit' this last few days, so I can vouch for how well they do their job. Hope that helps!
Mike.
_________________ MY 'PUPPY' PACKAGES

|
Back to top
|
|
 |
mikeb

Joined: 23 Nov 2006 Posts: 11284
|
Posted: Fri 18 Oct 2019, 10:58 Post subject:
|
|
Introduced in puppy 4 was looking into subfolders for puppy and resulted in the observed slowdown...indeed look in the initrd.gz init and you fill see a find command ...changing the maxlevel fixes it.
Since the puppy sfs is not specified manic finding is needed and subfolder usage was introduced to add to the mix. The script actually looks for the initrd which causes its own problems for multiple installs.
mike
|
Back to top
|
|
 |
rufwoof

Joined: 24 Feb 2014 Posts: 3681
|
Posted: Fri 18 Oct 2019, 11:30 Post subject:
|
|
Having the main sfs and kernel modules sfs inside the initrd and the initrd inside the kernel ... is nice. Just the one file (vmlinuz) to boot. But inflexible (if you like changing the main sfs/initrd or changing the kernel/modules).
In my Bulldog (Fatdog) I recompiled the kernel with localyesconfig, so no need for the kernel.sfs (modules/firmware). Fortunately for my hardware (laptop) I could also throw out all of the firmware as what is included within the kernel already supports my kit (wifi etc). And running just busybox/initrd alone can be enough to browse, file manage ...etc. no need for layering/saving (data stored elsewhere (hdd)). A 15MB total desktop system (vmlinuz). With that it boots to network wifi connected and I ssh into a server from where I run browser, access reddit, visit BBS's, etc. and remote sites don't see my IP, nor does my ISP see what I'm doing other than having a encrypted ssh connection to a remote box. No digital fingerprints are left on the box I use to boot/use that either. But that is a fallback boot choice, more generally I boot the full fatdog, for all the bells and whistles that contains.
Typically as others have indicated, the searching occurs within the intrd. Most (all ??) newer pups tend to cater for opening that up via a rox click action and then read through the init file within that.
_________________ ( ͡° ͜ʖ ͡°) :wq
Fatdog multi-session usb
echo url|sed -e 's/^/(c/' -e 's/$/ hashbang.sh)/'|sh
|
Back to top
|
|
 |
rockedge

Joined: 11 Apr 2012 Posts: 1365 Location: Connecticut, United States
|
Posted: Fri 18 Oct 2019, 11:38 Post subject:
|
|
@rufwoof
are you forwarding X11 in the scenario: boot into the 15 meg OS and SSH into a remote machine to run for example the browser?
|
Back to top
|
|
 |
bigpup

Joined: 11 Oct 2009 Posts: 13000 Location: S.C. USA
|
Posted: Fri 18 Oct 2019, 11:52 Post subject:
|
|
You do understand, that that is information you would need to know, if it did not boot OK?
Oh, it had trouble finding the Puppy files.
So, that is what is causing the boot problem.
_________________ 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)
|
Back to top
|
|
 |
Smithy

Joined: 12 Dec 2011 Posts: 1076
|
Posted: Fri 18 Oct 2019, 16:48 Post subject:
|
|
Hi guys, thanks for the replies.
I just tried a quick and dirty initrd.gz repack.
I actually found searching for puppy files line (step two in that init novel).
Removed “searching for puppy files” up to and including “dev console” line with it. Presume that is to talk to the terminal.
Then I used Packit to squash it back with the cpio option. Then I removed the .cpio extension on the file
And then squashed it up to an initrd.gz.
Put it back on the bastard usb stick and it booted real quick for a second and then crashed with loads of crap on the screen, kernel panic and other things.
I think I could be going wrong on the double squashing, possibly cpio thing.
|
Back to top
|
|
 |
Mike Walsh

Joined: 28 Jun 2014 Posts: 5668 Location: King's Lynn, UK.
|
Posted: Fri 18 Oct 2019, 17:56 Post subject:
|
|
@ Smithy:-
That's why I found jrb's 'build-tools' to be better. Whatever the Open & Rebuild scripts do, they do it in a single step.....and they do it real quick, too.
Like you, I tried UExtract & Packit, just out of curiosity. It took 2 steps to 'unpack', and two steps to 're-pack'.....and at the end, the size was considerably different.
The 'build-tools' are quick, and consistent. I'd sooner use them, TBH.
Up to you, of course. Sounds more like you may, perhaps, have removed too much stuff from 'init', if you ask me...... Personally, I would never tinker around with something that complex unless I was absolutely certain of what I was doing.
As long as you've got a back-up, you should be fine. Just replace it, if the worst comes to the worst. At least she'll boot again, that way.......
Mike.
_________________ MY 'PUPPY' PACKAGES

Last edited by Mike Walsh on Sat 19 Oct 2019, 07:04; edited 1 time in total
|
Back to top
|
|
 |
Flash
Official Dog Handler

Joined: 04 May 2005 Posts: 13399 Location: Arizona USA
|
Posted: Fri 18 Oct 2019, 18:41 Post subject:
|
|
Flash wrote: | Would booting with puppy pfix=ram be what you're looking for? |
Okay, maybe that wasn't very helpful, but it does make me wonder just how puppy pfix-ram works. How do it do what it do? In addition to other things, it must somehow prevent Puppy from looking for Save files and the like.
|
Back to top
|
|
 |
jafadmin
Joined: 19 Mar 2009 Posts: 1020
|
Posted: Sat 19 Oct 2019, 11:25 Post subject:
|
|
Are you trying to control what is printed on the screen, or control the actual boot behavior?
If you just want that string to not print on the screen, just replace it with blank spaces.
|
Back to top
|
|
 |
Smithy

Joined: 12 Dec 2011 Posts: 1076
|
Posted: Sat 19 Oct 2019, 12:51 Post subject:
|
|
Well the First issue is Laborious searching for puppy files.........10 seconds or so, less on the sata drive, a bit.
Hi, Mike, yes I tried out JRB’s init Tools and they do seem to offer consistency in unpacking and packing.
Thanks for the pointers.
MikeB, were you referring to this area of the init?
I changed the SEARCH DEPTH to 1 (was 2 I think) not much has changed though.
Code: | #find puppy files in the pc...
#vmlinuz (and optional simplified puppy.sfs (PUPXXXSFS), zdrv.sfs (ZDRVSFS)) have appended id-string (IDSTRING).
IGNORE=''
SEARCHDEPTH=1
[ "$PSUBDIR" ] && SEARCHDEPTH=0
for ONETRY in $LESSPARTS
do
ONEDEV="`echo -n "$ONETRY" | cut -f 1 -d '|'`"
ONEFS="`echo -n "$ONETRY" | cut -f 2 -d '|'`"
ONEDRV="`echo -n "$ONEDEV" | grep -o -f /tmp/ALLDRVS0`" #110205 ex: sda1 becomes sda.
if [ "$IGNORE" = "optical" ];then #110126 ignore optical if boot partition found.
[ "`echo -n "$ONEDRV" | grep -f /tmp/OPTICALDRIVES0`" != "" ] && continue #110205
fi
[ "$PFSCK" = "yes" ] && [ "$pdev1" = "$ONEDEV" ] && \
[ "$(echo $ONEFS| cut -c 1-3)" = "ext" ] && fsckme_func $ONEDEV $ONEFS
#v403 nasty bug: usb optical drive showing as /sys/block/sr0, but won't mount, needs more delay...
mntfunc $ONEFS /dev/$ONEDEV /mnt/data #-t $ONEFS /dev/$ONEDEV /mnt/data
if [ $? -ne 0 ];then
echo "PAUSE 5SEC: tried to mount /dev/${ONEDEV}, ${ONEFS} f.s." #101005 boot param loglevel=7 will show this.
echo -e -n " \\033[1;31mpausing\\033[0;39m" > /dev/console #31=red
sleep 5 #2 wasn't enough.
mntfunc $ONEFS /dev/$ONEDEV /mnt/data
if [ $? -ne 0 ];then
echo "RETRY FAILED: mounting /dev/${ONEDEV}, ${ONEFS} f.s." #101005
continue
fi
fi
echo "ONEDEV=$ONEDEV ONEFS=$ONEFS ONEDRV=$ONEDRV PSUBDIR=$PSUBDIR" >> /tmp/puppy-file-search.log #101127 for debugging.
if [ -d /mnt/data${PSUBDIR} ];then
if [ "$VMLINUZ" = "" ];then #search for kernel.qky and vmlinuz...
if [ "$ONEFS" != "iso9660" -a "$PMEDIA" = "cd" -a "$ONEFS" != "udf" ];then #101021 avoid finding vmlinuz on hd. 110204. 130128 also udf.
echo "Bypass looking for vmlinuz on $ONEDEV"
else
FND_FILES="`find /mnt/data${PSUBDIR} -maxdepth ${SEARCHDEPTH} -xdev -type f -iname kernel.qky -o -iname ${KERNELNAME} | grep -v ' ' | sed -e 's%^/mnt/data%%' | tr '\n' ' '`"
for ONEPUPFILE in $FND_FILES #kernel.qky: see woof script 4quirkybuild.
do
ONEFULLSIZE=`stat -c %s /mnt/data${ONEPUPFILE}`
ONEORIGSIZE=`expr $ONEFULLSIZE - 32` #110422
ONEIDSTRING="`dd if=/mnt/data${ONEPUPFILE} bs=1 skip=${ONEORIGSIZE} 2>/dev/null | sed -e 's%[^a-zA-Z0-9\.]%%g'`"
if [ "$ONEIDSTRING" = "$IDSTRING" ];then
VMLINUZ="`basename $ONEPUPFILE`"
PDEV1="$ONEDEV"
DEV1FS="$ONEFS"
BOOTDRV="$ONEDRV" #exs: sda sr0
PSUBDIR="`dirname $ONEPUPFILE`" #ex: /puppies/wary071
[ "$PSUBDIR" = "/" ] && PSUBDIR=""
#SAVEMARK: BootFlash utility can create 128MB boot partition, 2nd partition for pupsave...
#101020 if pup installed in a subdir, look there for SAVEMARK...
[ -f /mnt/data${PSUBDIR}/SAVEMARK ] && PSAVEMARK="`cat /mnt/data${PSUBDIR}/SAVEMARK`" #partition no. that has or will-have ${DISTRO_FILE_PREFIX}save.2fs. 101020
[ "$PSAVEMARK" ] && SAVEPART="${BOOTDRV}${PSAVEMARK}" #note, PSAVEMARK could also be a kernel boot param. ex: sda2
[ "$PSUBDIR" = "" ] && [ -f /mnt/data/etc/DISTRO_SPECS ] && DEV1PUP='yes' #flag full installation. 101103 ignore if vmlinuz in a subdir.
if [ "`echo -n "$BOOTDRV" | grep -f /tmp/OPTICALDRIVES0`" = "" ];then #110205 test not optical.
IGNORE='optical' #refinement, if vmlinuz not on optical drive, don't probe it. 110126
else #booting on optical, is it multisession?...
FND_MULTIFOLDER="`find /mnt/data -maxdepth 1 -xdev -type d -name 20[0-9][0-9]-[0-9][0-9]-[0-9][0-9]-[0-9][0-9]-[0-9][0-9] | grep -v ' ' | sed -e 's%^/mnt/data%%' | head -n 1`"
if [ "$FND_MULTIFOLDER" ];then #multisession cd/dvd
if [ "$PRAMONLY" != "yes" ];then
PUPMODE=72 #64+8, will become 77.
PUPSAVE="${ONEDEV},${ONEFS},${FND_MULTIFOLDER}"
fi
fi
fi
fi
done
fi
fi
[ "$PSUBDIR" ] && SEARCHDEPTH=1
if [ "$PUPSFS" = "" ];then
FND_FILES="`find /mnt/data${PSUBDIR} -maxdepth ${SEARCHDEPTH} -xdev -type f -iname ${PUPXXXSFS} | grep -v ' ' | sed -e 's%^/mnt/data%%' | tr '\n' ' '`"
for ONEPUPFILE in $FND_FILES
do
if [ "$NAMETYPE" = "traditional" ];then
ONEIDSTRING="$IDSTRING" #found file based on it's name only.
else
ONEFULLSIZE=`stat -c %s /mnt/data${ONEPUPFILE}`
ONEORIGSIZE=`expr $ONEFULLSIZE - 32`
ONEIDSTRING="`dd if=/mnt/data${ONEPUPFILE} bs=1 skip=${ONEORIGSIZE} 2>/dev/null | sed -e 's%[^a-zA-Z0-9\.]%%g'`"
fi
if [ "$ONEIDSTRING" = "$IDSTRING" ];then
PUPSFS="${ONEDEV},${ONEFS},${ONEPUPFILE}"
break
fi
done
fi
if [ "$ZDRV" = "" ];then
FND_FILES="`find /mnt/data${PSUBDIR} -maxdepth ${SEARCHDEPTH} -xdev -type f -iname ${ZDRVSFS} | grep -v ' ' | sed -e 's%^/mnt/data%%' | tr '\n' ' '`"
for ONEPUPFILE in $FND_FILES
do
if [ "$NAMETYPE" = "traditional" ];then
ONEIDSTRING="$IDSTRING" #found file based on it's name only.
else
ONEFULLSIZE=`stat -c %s /mnt/data${ONEPUPFILE}`
ONEORIGSIZE=`expr $ONEFULLSIZE - 32` #110422
ONEIDSTRING="`dd if=/mnt/data${ONEPUPFILE} bs=1 skip=${ONEORIGSIZE} 2>/dev/null | sed -e 's%[^a-zA-Z0-9\.]%%g'`"
fi
if [ "$ONEIDSTRING" = "$IDSTRING" ];then
ZDRV="${ONEDEV},${ONEFS},${ONEPUPFILE}"
break
fi
done
fi
if [ "$ADRV" = "" ];then
FND_FILES="`find /mnt/data${PSUBDIR} -maxdepth ${SEARCHDEPTH} -xdev -type f -iname ${ADRVSFS} | grep -v ' ' | sed -e 's%^/mnt/data%%' | tr '\n' ' '`"
for ONEPUPFILE in $FND_FILES
do
if [ "$NAMETYPE" = "traditional" ];then
ONEIDSTRING="$IDSTRING" #found file based on it's name only.
else
ONEFULLSIZE=`stat -c %s /mnt/data${ONEPUPFILE}`
ONEORIGSIZE=`expr $ONEFULLSIZE - 32` #110422
ONEIDSTRING="`dd if=/mnt/data${ONEPUPFILE} bs=1 skip=${ONEORIGSIZE} 2>/dev/null | sed -e 's%[^a-zA-Z0-9\.]%%g'`"
fi
if [ "$ONEIDSTRING" = "$IDSTRING" ];then
ADRV="${ONEDEV},${ONEFS},${ONEPUPFILE}"
echo -n " adrive" > /dev/console
break
fi
done
fi
if [ "$YDRV" = "" ];then
FND_FILES="`find /mnt/data${PSUBDIR} -maxdepth ${SEARCHDEPTH} -xdev -type f -iname ${YDRVSFS} | grep -v ' ' | sed -e 's%^/mnt/data%%' | tr '\n' ' '`"
for ONEPUPFILE in $FND_FILES
do
if [ "$NAMETYPE" = "traditional" ];then
ONEIDSTRING="$IDSTRING" #found file based on it's name only.
else
ONEFULLSIZE=`stat -c %s /mnt/data${ONEPUPFILE}`
ONEORIGSIZE=`expr $ONEFULLSIZE - 32` #110422
ONEIDSTRING="`dd if=/mnt/data${ONEPUPFILE} bs=1 skip=${ONEORIGSIZE} 2>/dev/null | sed -e 's%[^a-zA-Z0-9\.]%%g'`"
fi
if [ "$ONEIDSTRING" = "$IDSTRING" ];then
YDRV="${ONEDEV},${ONEFS},${ONEPUPFILE}"
echo -n " ydrive" > /dev/console
break
fi
done
fi
|
|
Back to top
|
|
 |
rufwoof

Joined: 24 Feb 2014 Posts: 3681
|
Posted: Sat 19 Oct 2019, 14:18 Post subject:
|
|
rockedge wrote: | @rufwoof
are you forwarding X11 in the scenario: boot into the 15 meg OS and SSH into a remote machine to run for example the browser? |
Hi rockedge
No. I just run a w3m (textual) browser on the ssh server (out of New York, whilst I'm in London). Same for irc and ssh (into other boxes). A sort of terminal server type setup, but connected via ssh/wireless.
In other cases I do set up a socks5 proxy on a cli/textual box, so browsers on the LAN can route all (graphical) browser traffic via that (ssh link).
_________________ ( ͡° ͜ʖ ͡°) :wq
Fatdog multi-session usb
echo url|sed -e 's/^/(c/' -e 's/$/ hashbang.sh)/'|sh
|
Back to top
|
|
 |
mikeb

Joined: 23 Nov 2006 Posts: 11284
|
Posted: Mon 21 Oct 2019, 05:40 Post subject:
|
|
Quote: | I changed the SEARCH DEPTH to 1 (was 2 I think) not much has changed though. |
yup...though it would depend on whats on your hard drive.
It might be worth trying the same find command in a terminal and comparing results. I changed things to in effect only look at the root of each drive.
mike
|
Back to top
|
|
 |
|
Page 1 of 2 [25 Posts] |
Goto page: 1, 2 Next |
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum You cannot attach files in this forum You can download files in this forum
|
Powered by phpBB © 2001, 2005 phpBB Group
|