Author |
Message |
DPUP5520
Joined: 16 Feb 2011 Posts: 814
|
Posted: Thu 17 Oct 2013, 00:59 Post subject:
|
|
Here's the pet for you: http://www.smokey01.com/dpup5520/icewm-PRP.pet
_________________ PupRescue 2.5
Puppy Crypt 528
|
Back to top
|
|
 |
Amgine

Joined: 21 Sep 2011 Posts: 233 Location: Washington State
|
Posted: Thu 17 Oct 2013, 09:49 Post subject:
|
|
Thank you very much!!!
_________________ Ubuntu-One Cloud Storage, Know where your Puppy files are, Back-up & Share files. https://one.ubuntu.com/referrals/referee/2118185/"]Sign Up!
|
Back to top
|
|
 |
L18L

Joined: 19 Jun 2010 Posts: 3493 Location: www.eussenheim.de/
|
Posted: Fri 18 Oct 2013, 09:45 Post subject:
Re: PupRescue_Precise |
|
williepabon wrote: | .. Well, I'm positive that one of the multitude of geeks that exist in this forum will know the answer for my problem |
Your problem is: Quote: | ... and am not too willing to start again. |
... and you can yourself find the answer I think
|
Back to top
|
|
 |
williepabon
Joined: 16 Sep 2013 Posts: 64 Location: Puerto Rico(USA)
|
Posted: Fri 18 Oct 2013, 11:24 Post subject:
PupRescue_Precise |
|
L18L:
The only problem that I now have with PupRescue is:
Quote: | Is there a way to accelerate the shut down process? It takes awful long time when the system is saving to the flash drive. |
I tried the solutions as per:
http://murga-linux.com/puppy/viewtopic.php?t=57380
Part A didn't work for me.
Part B:
I haven't been able to open initrd.gz for editing following the instructions delineated. Need additional advice on how to do it. Followed the instructions booting from my Ubuntu 12.04 laptop, but wasn't able to open said file for editing. Thanks.
wp
|
Back to top
|
|
 |
L18L

Joined: 19 Jun 2010 Posts: 3493 Location: www.eussenheim.de/
|
Posted: Fri 18 Oct 2013, 12:16 Post subject:
Re: PupRescue_Precise Subject description: edit init-ramfs |
|
williepabon wrote: | .. open initrd.gz for editing. |
Hope Barry's /usr/sbin/edit-initramfs helps: Code: | #!/bin/sh
#(c) Copyright Barry Kauler 2012, bkhome.org
#License GPL3 (/usr/share/doc/legal)
#shared-mime-info pkg has assigned initrd.gz mime-type application/initramfs-gz (by me).
#Click on initrd.gz in ROX-Filer, this script will run (see /root/Choices/MIME-types/application_initramfs-gz).
#note: script not internationalized, as this is a developer's tool.
[ ! $1 ] && exit 1
[ ! -f "$1" ] && exit 1
BASEFILE="`basename "$1"`"
[ "$BASEFILE" != "initrd.gz" ] && exit 1
compr_func() {
#find out compression type...
UNCOMPREXE=gunzip; COMPREXE=gzip; EXT=gz
gunzip -t "$1"
if [ $? -ne 0 ];then
UNCOMPREXE=bunzip2; COMPREXE=bzip2; EXT=bz2
bunzip2 -t "$1"
if [ $? -ne 0 ];then
UNCOMPREXE=unxz; COMPREXE=xz; EXT=xz
unxz -t "$1"
if [ $? -ne 0 ];then
return 1
fi
fi
fi
return 0
}
cd /root
[ -f initrd ] && rm -f initrd
[ -f /tmp/initrd.gz ] && rm -f /tmp/initrd.gz
[ "$1" = "/root/initrd.gz" ] && cp -f /root/initrd.gz /tmp/
if [ -d initrd-expanded ];then
pupdialog --background "yellow" --backtitle "initrd.gz: update?" --yesno "An initrd.gz is already expanded at /root/initrd-expanded. Is this correct, do you want to use /root/initrd-expanded to update ${1}?" 0 0
if [ $? -eq 0 ];then
compr_func "$1"
if [ $? -ne 0 ];then
pupdialog --background '#FF8080' --backtitle "initrd.gz: fail" --msgbox "Sorry, could not recognise compression type, unable to update initrd.gz." 0 0
else
cd initrd-expanded
find . | cpio -o -H newc > ../initrd
sync
cd ..
${COMPREXE} initrd
sync
mv -f initrd.${EXT} "$1"
pupdialog --background '#80FF80' --backtitle "initrd.gz: success" --msgbox "File ${1} has been updated with the contents of /root/initrd-expanded." 0 0
fi
fi
pupdialog --background "yellow" --backtitle "initrd.gz: finished" --yesno "Do you want to delete /root/initrd-expanded? If in doubt, please choose Yes" 0 0
if [ $? -eq 0 ];then
rox -D /root/initrd-expanded 2>/dev/null
rm -rf /root/initrd-expanded
fi
else
pupdialog --background "yellow" --backtitle "initrd.gz: expand?" --yesno "Do you want to open up initrd.gz, and optionally edit it?" 0 0
if [ $? -eq 0 ];then
compr_func "$1"
if [ $? -ne 0 ];then
pupdialog --background '#FF8080' --backtitle "initrd.gz: fail" --msgbox "Sorry, could not recognise compression type of ${1}, unable to expand it." 0 0
else
[ "$1" != "/root/initrd.gz" ] && cp -f "$1" /root/
mv -f initrd.gz initrd.${EXT}
${UNCOMPREXE} initrd.${EXT}
[ -f /tmp/initrd.gz ] && mv -f /tmp/initrd.gz /root/
mkdir initrd-expanded
cd initrd-expanded
cat ../initrd | cpio -i -d -m
sync
rm -f ../initrd
cd ..
pupdialog --colors --background '#80FF80' --backtitle "initrd.gz: expanded" --msgbox "File initrd.gz has been expanded at \Zb/root/initrd-expanded\ZB. You may edit the contents if you wish. \Zb\Z1\n\nAfterward, if you click on ${1} again\Zn\ZB, it will be updated with the contents of /root/initrd-expanded." 0 0
rox -d /root/initrd-expanded -x /root/initrd-expanded
fi
fi
fi
[ -f /tmp/initrd.gz ] && rm -f /tmp/initrd.gz
###END### |
|
Back to top
|
|
 |
williepabon
Joined: 16 Sep 2013 Posts: 64 Location: Puerto Rico(USA)
|
Posted: Sat 19 Oct 2013, 10:12 Post subject:
PupRescue_Precise |
|
L18L:
Thanks a lot for the help given. Now, I am able to edit initrd.gz without problem, but, following instructions on Part B of, http://murga-linux.com/puppy/viewtopic.php?t=57380 did not produce the effect I was expecting (a quicker shut down). I inserted the recommended line (PUPMODE=12) below esac and shut down a few times, but couldn't perceive any improvement in shut down times. Maybe I'm doing something wrong or I need to do something else. I'm revising my steps again to see if I made a mistake. Thanks again for your help.
wp
PS:
After revising, I found the line esac a number of times in the init script. Now I'm confused where I should insert the PUPMODE=12 statement.
After some additional experimenting I found out that apparently, PupRescue precise boots with a fresh initrd.gz file. I can modify the file, but after shut down and start up, the modifications to initrd.gz are gone.
|
Back to top
|
|
 |
L18L

Joined: 19 Jun 2010 Posts: 3493 Location: www.eussenheim.de/
|
Posted: Sun 20 Oct 2013, 04:56 Post subject:
Re: PupRescue_Precise |
|
williepabon wrote: | .. I found the line esac a number of times in the init script. Now I'm confused where I should insert the PUPMODE=12 statement. | I would take "esac followed by blanc line ... " around line 911
williepabon wrote: | After some additional experimenting I found out that apparently, PupRescue precise boots with a fresh initrd.gz file. I can modify the file, but after shut down and start up, the modifications to initrd.gz are gone. |
Did you follow the instruction (see image) which is saving the change?
Description |
|
Filesize |
13.58 KB |
Viewed |
950 Time(s) |

|
|
Back to top
|
|
 |
williepabon
Joined: 16 Sep 2013 Posts: 64 Location: Puerto Rico(USA)
|
Posted: Sun 20 Oct 2013, 12:03 Post subject:
PupRescue_Precise |
|
L18L:
Thanks for answering. Yes, I followed the instructions as the image shows. I even ran the script again to verify that the line I inserted was there. My init script has esac following with blank lines in the following:
line 317 ;;
line 318 esac
line 319 (blank)
line 875 ;;
line 876 esac
line 877 (blank)
line 921 *) RDSH="yes" ;;
line 922 esac
line 923 (blank)
line 1887 ;;
line 1888 esac
line 1889 (blank)
Thanks.
wp
|
Back to top
|
|
 |
L18L

Joined: 19 Jun 2010 Posts: 3493 Location: www.eussenheim.de/
|
Posted: Tue 22 Oct 2013, 05:38 Post subject:
Re: PupRescue_Precise |
|
williepabon,
hope this helps
[/derailing this thread]
|
Back to top
|
|
 |
williepabon
Joined: 16 Sep 2013 Posts: 64 Location: Puerto Rico(USA)
|
Posted: Wed 23 Oct 2013, 17:07 Post subject:
PupRescue_Precise |
|
L18L:
The thread that you gave me talks about a utility called PupSaveConfig. Do you think this utility would help me, at least, to decide to save or not to save at shut down? Will it work with PupRescue_Precise? Thanks.
wp
|
Back to top
|
|
 |
Pelo
Joined: 10 Sep 2011 Posts: 12591 Location: Mer méditerrannée (1 kms°)
|
Posted: Thu 06 Mar 2014, 05:33 Post subject:
pupsaveconfig 'save or not' Subject description: Boot on usb : Fail with Grub. |
|
pupsaveconfig 'save or not' : that seems already included in Precise rescue, that's a good thing. Pupsaveconfig works everywhere, excepted.. ?.
I use v. 2.2.2, not 2.2.5.
BOOT USB : I get a boot process to replace Puprescue one from another Precise distro. It works (now).
Description |
|

Download |
Filename |
pupsaveconfig-2.2.2.pet |
Filesize |
65.31 KB |
Downloaded |
266 Time(s) |
_________________ Passenger Pelo ! don't ask him to repair the aircraft. Don't use him as a demining dog .... pleeease.
|
Back to top
|
|
 |
wimpy

Joined: 22 Aug 2012 Posts: 409 Location: Essex, UK
|
Posted: Tue 23 Sep 2014, 06:15 Post subject:
|
|
I use a dedicated iso directory to test isos. I just copy each iso into it's own directory inside the iso directory and unarchive it. I then make the appropriate adjustment to menu.lst and voila!. The puprescue- precise iso works fine and can be booted from grub4dos, no problems.
However, when I tried this with puprescue.2.5.iso I got an Error 15 File not found message. Has anybody done a frugal install of the puprescue.2.5 iso successfully?
_________________ LxXenial16.08, LxPupSc17.07.01,Lucid 5.2.8 and others - all frugal
|
Back to top
|
|
 |
CatDude

Joined: 03 Jan 2007 Posts: 1573 Location: UK
|
Posted: Tue 23 Sep 2014, 08:12 Post subject:
|
|
Hi
wimpy wrote: | ...Has anybody done a frugal install of the puprescue.2.5 iso successfully? |
I assume you mean PupRescue_2.5.iso
if so, then the answer to your question is Yes
The following stanza works for me using Legacy Grub:
Code: | # Linux bootable partition config begins
title PupRescue 2.5 (on sda11)
rootnoverify (hd0,10)
kernel /pr25/vmlinuz pmedia=atahd pdev1=sda11 psubdir=pr25
initrd /pr25/initrd.gz
# Linux bootable partition config ends |
CatDude
.
_________________

|
Back to top
|
|
 |
wimpy

Joined: 22 Aug 2012 Posts: 409 Location: Essex, UK
|
Posted: Wed 24 Sep 2014, 01:55 Post subject:
|
|
@CatDude Thanks for the reply. I'm using grub4dos and all I do is add the following to menu.lst for each distro that I am testing
Code: |
title distro
find --set-root --ignore-floppies
kernel /iso/distro/vmlinuz psubdir=iso/distro pmedia=atahd pfix=fsck
initrd /iso/distro/initrd.gz |
Works so far for all distros, except that puprescue_2.5.iso.
_________________ LxXenial16.08, LxPupSc17.07.01,Lucid 5.2.8 and others - all frugal
|
Back to top
|
|
 |
CatDude

Joined: 03 Jan 2007 Posts: 1573 Location: UK
|
Posted: Wed 24 Sep 2014, 08:40 Post subject:
|
|
@ wimpy
wimpy wrote: | @CatDude Thanks for the reply. I'm using grub4dos and all I do is add the following to menu.lst for each distro that I am testing
Code: |
title distro
find --set-root --ignore-floppies
kernel /iso/distro/vmlinuz psubdir=iso/distro pmedia=atahd pfix=fsck
initrd /iso/distro/initrd.gz |
Works so far for all distros, except that puprescue_2.5.iso. |
OK, once again you refer to the ISO as: puprescue_2.5.iso
yet the actual name of the one i have here is: PupRescue_2.5.iso
Where did you get this thing from
Did you check the md5sum when you downloaded the file
Here is the md5sum of the ISO that i have here: 624765761faa77868800d7969b23de39 PupRescue_2.5.iso
and the 3 files of interest inside of that ISO are these:
bf18f3fa38e4f19f3ae74fec6b081a1e initrd.gz
6a83667442e5840d68a7b92988749693 PupRescue_2.5.sfs
51adeb52099a1a89bb1c2e5f98e48245 vmlinuz
Do your files match these
Any chance you could provide a copy of your actual menu.lst
and a screeny showing the files in the subdir where they reside, it may help
CatDude
.
_________________

|
Back to top
|
|
 |
|