My pleasure.. As i dont use puppy 5, I cant really help you there... But have you tried Moo (by Iguleder)?Dragynn wrote:So, trying to remaster 5.1.1 in 5.1.1.
Thanks for keeping an eye on this thread and replying.
Woofy 0.91
[b][url=https://bit.ly/2KjtxoD]Pkg[/url], [url=https://bit.ly/2U6dzxV]mdsh[/url], [url=https://bit.ly/2G49OE8]Woofy[/url], [url=http://goo.gl/bzBU1]Akita[/url], [url=http://goo.gl/SO5ug]VLC-GTK[/url], [url=https://tiny.cc/c2hnfz]Search[/url][/b]
not found
is there a specific way i'm suppose to 'path' to the files i want deleted? am i suppose to mount the iso and sfs and list the entries in the 'delete.txt' file to that path?
i'm trying to delete opera from nop431. i have a delete.txt file with the entries:
/root/.local/share/applications/opera.desktop
/root/.opera
/root/.opera/operaprefs.ini
/root/.opera/icons/http%3A%2F%2Fredir.opera.com%2Ffavicons%2Famazon%2Ffavicon.ico
/root/.opera/icons/http%3A%2F%2Fredir.opera.com%2Ffavicons%2Fask%2Ffavicon.ico
/root/.opera/icons/http%3A%2F%2Fredir.opera.com%2Ffavicons%2Fdownloadcom%2Ffavicon.ico
/root/.opera/icons/http%3A%2F%2Fredir.opera.com%2Ffavicons%2Febay%2Ffavicon.ico
/root/.opera/icons/http%3A%2F%2Fredir.opera.com%2Ffavicons%2Fgoogle%2Ffavicon.ico
/root/.opera/icons/http%3A%2F%2Fredir.opera.com%2Ffavicons%2Fkayak%2Ffavicon.ico
/root/.opera/icons/http%3A%2F%2Fredir.opera.com%2Ffavicons%2Fmyopera%2Ffavicon.ico
/root/.opera/icons/http%3A%2F%2Fredir.opera.com%2Ffavicons%2Fopera%2Ffavicon.ico
/root/.opera/icons/http%3A%2F%2Fredir.opera.com%2Ffavicons%2Fshopping%2Ffavicon.ico
/root/.opera/icons/http%3A%2F%2Fredir.opera.com%2Ffavicons%2Fwikipedia%2Ffavicon.ico
all i'm getting in the terminal when i hit go on woofy is 'not found' next to the paths, and my files aren't being deleted from the pup_431.sfs, and my new iso file is the exact same size as the old one...
what am i doing wrong???
i'm trying to delete opera from nop431. i have a delete.txt file with the entries:
/root/.local/share/applications/opera.desktop
/root/.opera
/root/.opera/operaprefs.ini
/root/.opera/icons/http%3A%2F%2Fredir.opera.com%2Ffavicons%2Famazon%2Ffavicon.ico
/root/.opera/icons/http%3A%2F%2Fredir.opera.com%2Ffavicons%2Fask%2Ffavicon.ico
/root/.opera/icons/http%3A%2F%2Fredir.opera.com%2Ffavicons%2Fdownloadcom%2Ffavicon.ico
/root/.opera/icons/http%3A%2F%2Fredir.opera.com%2Ffavicons%2Febay%2Ffavicon.ico
/root/.opera/icons/http%3A%2F%2Fredir.opera.com%2Ffavicons%2Fgoogle%2Ffavicon.ico
/root/.opera/icons/http%3A%2F%2Fredir.opera.com%2Ffavicons%2Fkayak%2Ffavicon.ico
/root/.opera/icons/http%3A%2F%2Fredir.opera.com%2Ffavicons%2Fmyopera%2Ffavicon.ico
/root/.opera/icons/http%3A%2F%2Fredir.opera.com%2Ffavicons%2Fopera%2Ffavicon.ico
/root/.opera/icons/http%3A%2F%2Fredir.opera.com%2Ffavicons%2Fshopping%2Ffavicon.ico
/root/.opera/icons/http%3A%2F%2Fredir.opera.com%2Ffavicons%2Fwikipedia%2Ffavicon.ico
all i'm getting in the terminal when i hit go on woofy is 'not found' next to the paths, and my files aren't being deleted from the pup_431.sfs, and my new iso file is the exact same size as the old one...
what am i doing wrong???
Re: not found
You should make a list of full paths to the files you want to delete..stifiling wrote:is there a specific way i'm suppose to 'path' to the files i want deleted? am i suppose to mount the iso and sfs and list the entries in the 'delete.txt' file to that path?.... what am i doing wrong???
Possibly your list is throwing Woofy because you have lots of special characters..
Try this list:
Code: Select all
/root/.local/share/applications/opera.desktop
/root/.opera
/root/.opera/operaprefs.ini
/root/.opera/icons
You could tick the 'Edit Filesystem' bit and (semi) manually delete the files that you want removed..
You could simply create a script in the root of the mounted sfs, and put something like this in it:
Code: Select all
#!/bin/bash
$prefix=.
while read line
do
[ -e $prefix$line ] && rm -v $prefix$line
done < /path/to/files-to-delete.txt
..not on Puppy at the moment though, so can't test it..
Sorry about the late response.
[b][url=https://bit.ly/2KjtxoD]Pkg[/url], [url=https://bit.ly/2U6dzxV]mdsh[/url], [url=https://bit.ly/2G49OE8]Woofy[/url], [url=http://goo.gl/bzBU1]Akita[/url], [url=http://goo.gl/SO5ug]VLC-GTK[/url], [url=https://tiny.cc/c2hnfz]Search[/url][/b]
Updated to version 0.6. (a big improvement!)
See main post for changelog.
See main post for changelog.
[b][url=https://bit.ly/2KjtxoD]Pkg[/url], [url=https://bit.ly/2U6dzxV]mdsh[/url], [url=https://bit.ly/2G49OE8]Woofy[/url], [url=http://goo.gl/bzBU1]Akita[/url], [url=http://goo.gl/SO5ug]VLC-GTK[/url], [url=https://tiny.cc/c2hnfz]Search[/url][/b]
You're welcome.mauri wrote:... thanks a lot for updating !sc0ttman wrote:Updated to version 0.6. (a big improvement!)
See main post for changelog.
[b][url=https://bit.ly/2KjtxoD]Pkg[/url], [url=https://bit.ly/2U6dzxV]mdsh[/url], [url=https://bit.ly/2G49OE8]Woofy[/url], [url=http://goo.gl/bzBU1]Akita[/url], [url=http://goo.gl/SO5ug]VLC-GTK[/url], [url=https://tiny.cc/c2hnfz]Search[/url][/b]
Thanks for Woofy sc0ttman - i have tried most of the remaster scripts and applications and find woofy the easies to use.
There may be an easier way that this?
But in case this is of help to anyone else using woofy.
For making a list of application / files to be removed.
i first dragged pfind.desktop file to my desktop from /usr/share/applications.
i then make a new directory in /root called remove and keep that directory open then open /tmp directory.
I do this because every time you search for applications with pfind it sends a file list to /tmp so i simply copy each file list to /root/remove - once i have all the pfind file lists files in /root/remove i then open a terminal in that directory and type command: cat * > remove_files.txt to merge all the individual pfind results into one big file that can be used by woofy.
cheers.
There may be an easier way that this?
But in case this is of help to anyone else using woofy.
For making a list of application / files to be removed.
i first dragged pfind.desktop file to my desktop from /usr/share/applications.
i then make a new directory in /root called remove and keep that directory open then open /tmp directory.
I do this because every time you search for applications with pfind it sends a file list to /tmp so i simply copy each file list to /root/remove - once i have all the pfind file lists files in /root/remove i then open a terminal in that directory and type command: cat * > remove_files.txt to merge all the individual pfind results into one big file that can be used by woofy.
cheers.
I basically do the same, but I use pfilesearch (with the 'search within' option), then copy n paste the last bit.stu90 wrote:For making a list of application / files to be removed.
i first dragged pfind.desktop file to my desktop from /usr/share/applications.
i then make a new directory in /root called remove and keep that directory open then open /tmp directory.
I do this because every time you search for applications with pfind it sends a file list to /tmp so i simply copy each file list to /root/remove - once i have all the pfind file lists files in /root/remove i then open a terminal in that directory and type command: cat * > remove_files.txt to merge all the individual pfind results into one big file that can be used by woofy.
cheers.
I find it fast (enough) and easy..
HOWEVER:
I want to upgrade Woofy later, so that:
1- you simply enter the filenames you want deleted, separated by a comma,
2- then woofy will basically do what pfilesearch/pfind did for us (finding all matching dirs/files),
3- then woofy will delete all results found in the new sfs base..
But (nearly) noone seems to use Woofy (or Puplite), so I may only bother when I want to remaster something next, for myself..
(not complaining, just saying there's no urgent need)
Thanks for your appreciation though stu90.. Glad you like it.
[b][url=https://bit.ly/2KjtxoD]Pkg[/url], [url=https://bit.ly/2U6dzxV]mdsh[/url], [url=https://bit.ly/2G49OE8]Woofy[/url], [url=http://goo.gl/bzBU1]Akita[/url], [url=http://goo.gl/SO5ug]VLC-GTK[/url], [url=https://tiny.cc/c2hnfz]Search[/url][/b]
Hi Sc0ttman,
I seem to have run into a problem with woofy when using Barry's latest debain squeezed puppy.
http://bkhome.org/blog/?viewDetailed=02292
I get this info box pop up regarding the .sfs.
i enter the location of the squeezed.sfs in /mnt/oldiso/ into the input box - it then goes through the build process as expected but the resulting .iso for me fails to boot with the message unable to find .sfs
I seem to have run into a problem with woofy when using Barry's latest debain squeezed puppy.
http://bkhome.org/blog/?viewDetailed=02292
I get this info box pop up regarding the .sfs.
i enter the location of the squeezed.sfs in /mnt/oldiso/ into the input box - it then goes through the build process as expected but the resulting .iso for me fails to boot with the message unable to find .sfs
Hmmm, what is the name of the actual sfs file in question? Most likely Woofy does not account for the naming pattern or something like that... Unless something else is wrong... I don't know too much about Dpup or Woof, but perhaps check the boot options of the ISO, and maybe the init script in initrd.gz, to see for what, and where, it is looking...stu90 wrote:Hi Sc0ttman,
I seem to have run into a problem with woofy when using Barry's latest debain squeezed puppy.
http://bkhome.org/blog/?viewDetailed=02292
.... (image above)
i enter the location of the squeezed.sfs in /mnt/oldiso/ into the input box - it then goes through the build process as expected but the resulting .iso for me fails to boot with the message unable to find .sfs
To be honest, it's been a while since I worked on Woofy, I would have to have another look at it to be of more help, as I have a terrible memory!
[b][url=https://bit.ly/2KjtxoD]Pkg[/url], [url=https://bit.ly/2U6dzxV]mdsh[/url], [url=https://bit.ly/2G49OE8]Woofy[/url], [url=http://goo.gl/bzBU1]Akita[/url], [url=http://goo.gl/SO5ug]VLC-GTK[/url], [url=https://tiny.cc/c2hnfz]Search[/url][/b]
jesus, when did the sfs files get such weird names? I'll have a look into it...stu90 wrote:Hi sc0ttman,
Barrys squeezed pup .iso is named "sqzd-4.99.2.iso"
and the .sfs is named "puppy_sqzd_4.99.2.sfs"
[b][url=https://bit.ly/2KjtxoD]Pkg[/url], [url=https://bit.ly/2U6dzxV]mdsh[/url], [url=https://bit.ly/2G49OE8]Woofy[/url], [url=http://goo.gl/bzBU1]Akita[/url], [url=http://goo.gl/SO5ug]VLC-GTK[/url], [url=https://tiny.cc/c2hnfz]Search[/url][/b]
Stu90, I dont think it is a problem with Woofy not finding the SFS file, or Woofy would exit and the remaster would not continue, if the path you entered is not found to be correct.
However, Woofy does not search for any SFS files starting with puppy_* by default... But you can easily add support for this filename, by adding the following to line 431:
So you have, from line 430:
Woofy should then find your SFS file without problems - if the remastered version still cannot boot, you know it has nothing to do with this part of the script.
My guess is that it still will not boot, and that the problem lies elsewhere... I think maybe you should monitor the console as it goes, and also keep the directories used (such as '/mnt/oldiso') open as well - just to check all the relevant files are where they should be, at the right time!
Does your remastered version have the SFS on the ISO? If so, I'm guessing the init script might be next place to check???
Not sure what it may be, might have to download Dpup-squeeze
However, Woofy does not search for any SFS files starting with puppy_* by default... But you can easily add support for this filename, by adding the following to line 431:
Code: Select all
[ ! "$oldsfspath" ] && oldsfspath=`find /mnt/oldiso -name puppy_sqzd_\*.sfs -o -name puppy_sqzd_\*.sfs`
Code: Select all
[ ! "$oldsfspath" ] && oldsfspath=`find /mnt/oldiso -name tpup-\*.sfs -o -name tpup_\*.sfs`
[ ! "$oldsfspath" ] && oldsfspath=`find /mnt/oldiso -name puppy_sqzd_\*.sfs -o -name puppy_sqzd_\*.sfs`
My guess is that it still will not boot, and that the problem lies elsewhere... I think maybe you should monitor the console as it goes, and also keep the directories used (such as '/mnt/oldiso') open as well - just to check all the relevant files are where they should be, at the right time!
Does your remastered version have the SFS on the ISO? If so, I'm guessing the init script might be next place to check???
Not sure what it may be, might have to download Dpup-squeeze
[b][url=https://bit.ly/2KjtxoD]Pkg[/url], [url=https://bit.ly/2U6dzxV]mdsh[/url], [url=https://bit.ly/2G49OE8]Woofy[/url], [url=http://goo.gl/bzBU1]Akita[/url], [url=http://goo.gl/SO5ug]VLC-GTK[/url], [url=https://tiny.cc/c2hnfz]Search[/url][/b]
Also Stu, just a quick question, this got me thinking...
Lots of your remasters do not JWM, is that correct? Have you ever tried editing themes and stuff through Woofy when remastering a non-JWM puppy, that uses OpenBox or whatever?
Would you like something that checks for the WM in use on the ISO, and lets you edit some settings for that WM? (Basically, support for non JWM Wms)..
Lots of your remasters do not JWM, is that correct? Have you ever tried editing themes and stuff through Woofy when remastering a non-JWM puppy, that uses OpenBox or whatever?
Would you like something that checks for the WM in use on the ISO, and lets you edit some settings for that WM? (Basically, support for non JWM Wms)..
[b][url=https://bit.ly/2KjtxoD]Pkg[/url], [url=https://bit.ly/2U6dzxV]mdsh[/url], [url=https://bit.ly/2G49OE8]Woofy[/url], [url=http://goo.gl/bzBU1]Akita[/url], [url=http://goo.gl/SO5ug]VLC-GTK[/url], [url=https://tiny.cc/c2hnfz]Search[/url][/b]
Glad it worked (of sorts!)....stu90 wrote:just noticed what the problem is, for some reason the .sfs in the new .iso is being named wrong - new .sfs is called "puppy_sqzd_4.99.2.sfssqz.sfs"
Did you try to set a suffix in the main menu, at the start??
It will help me fix it if I know...
[b][url=https://bit.ly/2KjtxoD]Pkg[/url], [url=https://bit.ly/2U6dzxV]mdsh[/url], [url=https://bit.ly/2G49OE8]Woofy[/url], [url=http://goo.gl/bzBU1]Akita[/url], [url=http://goo.gl/SO5ug]VLC-GTK[/url], [url=https://tiny.cc/c2hnfz]Search[/url][/b]
sc0ttman wow this Woofy looks very tempting to try out.
What makes me hesitate is there is no description on what one need.
Does it work on Full install? On frugal install? On USB install and how big should that USB be then? Does a 1GB RAM do or maybe 3GB or something needed or a big swap file to hold things in place? Such info? I have an Atom CPU and them are kind of single core? maybe it does not work on them does it?
What makes me hesitate is there is no description on what one need.
Does it work on Full install? On frugal install? On USB install and how big should that USB be then? Does a 1GB RAM do or maybe 3GB or something needed or a big swap file to hold things in place? Such info? I have an Atom CPU and them are kind of single core? maybe it does not work on them does it?
I use Google Search on Puppy Forum
not an ideal solution though
not an ideal solution though
lucid puppy has openbox as the default windows manager - if i recall i did try the theme setting through woofy but the desktop icons didn't display properly (they were just the normal script icon) - this wasn't a problem for me as i edit the filesystem anyway so just changed the theme, icons, wallpaper etc then.sc0ttman wrote:Also Stu, just a quick question, this got me thinking...
Lots of your remasters do not JWM, is that correct? Have you ever tried editing themes and stuff through Woofy when remastering a non-JWM puppy, that uses OpenBox or whatever?
Would you like something that checks for the WM in use on the ISO, and lets you edit some settings for that WM? (Basically, support for non JWM Wms)..
I have noticed there has been a few puplets lately using openbox / tint2 - so i think it must be growing as a popular alternative to JWM it also as far as i can tell doesn't have the recurring fullscreen problem that JWM suffers ( i think that was one of the reasons lucid puppy used openbox as the default?)
The ability to set the openbox theme could be a nice feature to have in woofy
No, no suffix - the input box is just left blank.sc0ttman wrote:Glad it worked (of sorts!)....stu90 wrote:just noticed what the problem is, for some reason the .sfs in the new .iso is being named wrong - new .sfs is called "puppy_sqzd_4.99.2.sfssqz.sfs"
Did you try to set a suffix in the main menu, at the start??
It will help me fix it if I know...
cheers.
OK thanks... I'll checkout the sfs naming part of the script... Also, if you have any details on how openbox themes work, it would help me in applying the feature to Woofy... Although I can of course check it out myself, but it might take longer... So, up to you...stu90 wrote:The ability to set the openbox theme could be a nice feature to have in woofy
No, (I added) no suffix - the input box is just left blank.
cheers.
[b][url=https://bit.ly/2KjtxoD]Pkg[/url], [url=https://bit.ly/2U6dzxV]mdsh[/url], [url=https://bit.ly/2G49OE8]Woofy[/url], [url=http://goo.gl/bzBU1]Akita[/url], [url=http://goo.gl/SO5ug]VLC-GTK[/url], [url=https://tiny.cc/c2hnfz]Search[/url][/b]