IIRC, ripped files are .wav, then encoded ones are .mp3 (or .ogg, etc)
You can try running grip from the CLI, instead of the GUI, so that you see
its stdout and stderr on your command line... that might help.
Also make sure grip is running as a user which has permissions to write
where you want (
Grip is not working for me after I changed the Rip File Format. It is
now set as ~/mp3/%A/%d/%n.mp3 and it begins to rip and encode then just
stops as though I hit Abort Rip & Encode. What should the Rip file
format be, or is that not the likely problem. Grip 3.0.7 on Fedora
Yarrow.
Dirk
_
In somewhat-related news, I just found this project via freshmeat:
http://freshmeat.net/projects/rsnapshot/?branch_id=43437&release_id=146249&topic_id=19%2C137%2C861
About:
rsnapshot is a filesystem snapshot utility based on rsync. It makes it easy
to make periodic snapshots of local machines, an
Quoting:
"""
From: Hal Pomeranz
Date: Mon, 29 Dec 2003 18:25:29 -0800
...
Frankly, using GNU tar is probably a better option precisely because
it doesn't have this particular issue (tar is a "file at a time"
archiver, and is therefore relatively resistant to file system changes
during the archive p
--- Bob Miller <[EMAIL PROTECTED]> wrote:
> Larry Price wrote:
> > This is kind of a borderline question;
> > A disk was intentionally zero'd out using
> > dd if=/dev/zero of=/dev/hda
> > however the DOS fdisk utility couldn't rebuild the partition
> table
> > afterwards.
This is shifting the sub
