Why won't Woof work?
Why won't Woof work?
I don't know what happened, but some time ago Woof stopped working for me. Woof 1 or Woof 2, it doesn't matter. The program crashes during "build distro", right after it asks about the zdrv file (I say no to that).
If I tell it to check dependencies, it gives a bunch of error messages about not having ldd and chrooting.
It doesn't seem to matter if it's Ubuntu or Slack.
What do I have to do to get this working?
If I tell it to check dependencies, it gives a bunch of error messages about not having ldd and chrooting.
It doesn't seem to matter if it's Ubuntu or Slack.
What do I have to do to get this working?
- L18L
- Posts: 3479
- Joined: Sat 19 Jun 2010, 18:56
- Location: www.eussenheim.de/
Re: Why won't Woof work?
It does matter for anyone who will try to help youChili Dog wrote:I don't know what happened, but some time ago Woof stopped working for me. Woof 1 or Woof 2, it doesn't matter...
http://www.murga-linux.com/puppy/viewtopic.php?t=36872
Ok I'll paraphrase. Woof 1 used to work awesome. I could just go through the steps in the gui, and I would end up with a bootable iso. Now, it doesn't matter whether it's Woof1 or Woof2, it always crashes at the same point in the process.
But people are still building things with Woof, so it must be possible.
Last night I found the part of Barry's tutorial where it goes through enabling a couple of online options. Ended up with the same problem, though.
But people are still building things with Woof, so it must be possible.
Last night I found the part of Barry's tutorial where it goes through enabling a couple of online options. Ended up with the same problem, though.
Do you have woof in its own partition? This may help. that is what I have woof2 is completely all alone in its partition. If you have this already than reformat the partition and redownload woof2.Chili Dog wrote:Ok I'll paraphrase. Woof 1 used to work awesome. I could just go through the steps in the gui, and I would end up with a bootable iso. Now, it doesn't matter whether it's Woof1 or Woof2, it always crashes at the same point in the process.
But people are still building things with Woof, so it must be possible.
Last night I found the part of Barry's tutorial where it goes through enabling a couple of online options. Ended up with the same problem, though.
You can also check this thread for help with woof2
http://murga-linux.com/puppy/viewtopic.php?t=81762
This should help you to get started all over again.
Cheers
- L18L
- Posts: 3479
- Joined: Sat 19 Jun 2010, 18:56
- Location: www.eussenheim.de/
Sounds like Barry should be informed about.
http://bkhome.org/blog/?viewDetailed=02612
He is interested in just woof2 I think.
edit
I have no experiences with woof
Wrote this before I have seen oldyeller's post
http://bkhome.org/blog/?viewDetailed=02612
He is interested in just woof2 I think.
edit
I have no experiences with woof
Wrote this before I have seen oldyeller's post
I havent ever used that gui thingy. I have used the underlying scripts straight. 0setup, 1download, 2createpackages, 3builddistro.
Launching them in console gives you usually error reports and if not....give the script -x parameter and you get more verbosity. You maybe can pinpoint in what stage the script fails.
Corrupted woof content has been many times my problem. Starting from fresh packages, fresh woof download has helped when the build just has failed.
Launching them in console gives you usually error reports and if not....give the script -x parameter and you get more verbosity. You maybe can pinpoint in what stage the script fails.
Corrupted woof content has been many times my problem. Starting from fresh packages, fresh woof download has helped when the build just has failed.
@oldyeller
Actually we are describing the same thing - I thought you meant a dedicated partition just for Woof. I have it in a directory on another partition, wouldn't consider using a savefile for anything that big.
The GUI part I don't like at all. Very tedious to select packages, and the end result always need manual editing anyway - things I want to leave out still appear.
Actually we are describing the same thing - I thought you meant a dedicated partition just for Woof. I have it in a directory on another partition, wouldn't consider using a savefile for anything that big.
The GUI part I don't like at all. Very tedious to select packages, and the end result always need manual editing anyway - things I want to leave out still appear.