On Tue, Mar 20, 2007 at 12:45:51PM +, Tyler Smith wrote:
> On 2007-03-17, Tyler Smith <[EMAIL PROTECTED]> wrote:
> > On 2007-03-17, Douglas Allan Tutty <[EMAIL PROTECTED]> wrote:
> >>
> >> Within that directory I issued:
> >>
> >>$ls -1 | xargs -L 1 tar -xf
> >>
> >> and ended up with a tes
On 2007-03-17, Tyler Smith <[EMAIL PROTECTED]> wrote:
> On 2007-03-17, Douglas Allan Tutty <[EMAIL PROTECTED]> wrote:
>>
>> Within that directory I issued:
>>
>> $ls -1 | xargs -L 1 tar -xf
>>
>> and ended up with a test subdirectory containing all nine files.
>>
>
> The argument to ls,
On Mon, 2007-03-19 at 03:36 -0500, Adam Porter wrote:
> So it looks like the ultimate solution is Greg Folkert's suggestion to
> install the package "unp", which handles multiple archives and
> automatically chooses the right extractor. Cameron Hutchison's shell
> function is also handy, but unp
On 2007-03-17 18:49:59 +0100, Joe Hart wrote:
> unp, orange. Right. Never heard of either of them. I have now.
unp doesn't do proper character escaping, though. So, never do things
like "unp *.tar.bz2" on files that come from an external source, as
I fear that this may execute arbitrary code on
So it looks like the ultimate solution is Greg Folkert's suggestion to
install the package "unp", which handles multiple archives and
automatically chooses the right extractor. Cameron Hutchison's shell
function is also handy, but unp probably makes that unnecessary if you can
install packages on
ED]
> with a subject of "unsubscribe". Trouble? Contact
> [EMAIL PROTECTED]
>
>
>
--
View this message in context:
http://www.nabble.com/A-silly-question-about-tar-tf3418581.html#a9537723
Sent from the Debian User mailing list archive at Nabble.com.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On 2007-03-17, Douglas Allan Tutty <[EMAIL PROTECTED]> wrote:
>
> Within that directory I issued:
>
> $ls -1 | xargs -L 1 tar -xf
>
> and ended up with a test subdirectory containing all nine files.
>
Ok, I tried that out. The key seems to be the arguments to xarg,
either "-L 1" as you sugge
On Sat, Mar 17, 2007 at 01:23:02PM +, Tyler Smith wrote:
> On 2007-03-17, Douglas Allan Tutty <[EMAIL PROTECTED]> wrote:
> >
> I have, and unfortunately it doesn't work. The result is the same as
> the original problem with the regular * expansion:
>
> tyler:tar-> find ./ -name '*.tar.gz' |
On 2007-03-17, Andrei Popescu <[EMAIL PROTECTED]> wrote:
> Tyler Smith <[EMAIL PROTECTED]> wrote:
>>
>> I have, and unfortunately it doesn't work. The result is the same as
>> the original problem with the regular * expansion:
>>
>> tyler:tar-> find ./ -name '*.tar.gz' | xargs echo
>> ../one.tar.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Greg Folkert wrote:
> On Sat, 2007-03-17 at 14:34 +0100, Joe Hart wrote:
[snip] (script can be found in the previous message)
>> Another handy little script. I just love this list. It's a lot easier
>> to type x *.zip or x *.rar than it is to right
On Thu, Mar 15, 2007 at 02:59:01AM EST, Adam Porter wrote:
> I've read the man page, googled this list and the rest of the Net, but I
> still can't figure out why this doesn't work:
>
> $ tar xjf *.tar.bz2
> tar: beryl-core-0.2.0.tar.bz2: Not found in archive
> tar: beryl-manager-0.2.0.tar.bz2: No
On Sat, 2007-03-17 at 14:34 +0100, Joe Hart wrote:
> Cameron Hutchison wrote:
> [snip]
>
> >
> > I have the following shell function defined in my .bashrc which I use to
> > extract the various archives I come across. It handles multiple archives
> > on the command line. Usage is simple:
> >
> >
Tyler Smith <[EMAIL PROTECTED]> wrote:
> On 2007-03-17, Douglas Allan Tutty <[EMAIL PROTECTED]> wrote:
> >
> > You use find to spit out a list of the files you want (you _may_ be
> > able to just use ls -1 .tar), pipe that through xargs. Something
> > like this:
> >
> > ls -1 .tar.gz | xargs
Douglas Allan Tutty <[EMAIL PROTECTED]> wrote:
> On Sat, Mar 17, 2007 at 02:35:01PM +0100, Thomas Jollans wrote:
> > On Saturday 17 March 2007 13:58, Douglas Allan Tutty wrote:
> > > On Sat, Mar 17, 2007 at 05:00:21AM -0500, Adam Porter wrote:
> >
> > > You use find to spit out a list of the file
On Saturday 17 March 2007 14:45, Douglas Allan Tutty wrote:
> On Sat, Mar 17, 2007 at 02:35:01PM +0100, Thomas Jollans wrote:
> > On Saturday 17 March 2007 13:58, Douglas Allan Tutty wrote:
> > > On Sat, Mar 17, 2007 at 05:00:21AM -0500, Adam Porter wrote:
> > >
> > > You use find to spit out a lis
On 2007-03-17, Douglas Allan Tutty <[EMAIL PROTECTED]> wrote:
>
> You use find to spit out a list of the files you want (you _may_ be able
> to just use ls -1 .tar), pipe that through xargs. Something like this:
>
> ls -1 .tar.gz | xargs tar [tar options -f ]
>
> for each line of input it re
On Sat, Mar 17, 2007 at 02:35:01PM +0100, Thomas Jollans wrote:
> On Saturday 17 March 2007 13:58, Douglas Allan Tutty wrote:
> > On Sat, Mar 17, 2007 at 05:00:21AM -0500, Adam Porter wrote:
>
> > You use find to spit out a list of the files you want (you _may_ be able
> > to just use ls -1 .tar),
On Saturday 17 March 2007 13:58, Douglas Allan Tutty wrote:
> On Sat, Mar 17, 2007 at 05:00:21AM -0500, Adam Porter wrote:
> > Thanks for your replies, everyone. It seems to me that there might be a
> > market for a simple script frontend to tar that would handle
> > shell-expanded wildcards; perh
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Cameron Hutchison wrote:
[snip]
>
> I have the following shell function defined in my .bashrc which I use to
> extract the various archives I come across. It handles multiple archives
> on the command line. Usage is simple:
>
> $ x *.tar.gz
>
> x (
On Sat, Mar 17, 2007 at 05:00:21AM -0500, Adam Porter wrote:
> Thanks for your replies, everyone. It seems to me that there might be a
> market for a simple script frontend to tar that would handle shell-expanded
> wildcards; perhaps it could be included in Debian's package of tar. Would
> that b
Adam Porter wrote:
>Thanks for your replies, everyone. It seems to me that there might be a
>market for a simple script frontend to tar that would handle shell-expanded
>wildcards; perhaps it could be included in Debian's package of tar. Would
>that be a good idea? Does anything like that alrea
Thanks for your replies, everyone. It seems to me that there might be a
market for a simple script frontend to tar that would handle shell-expanded
wildcards; perhaps it could be included in Debian's package of tar. Would
that be a good idea? Does anything like that already exist?
--
To UNSUB
I've read the man page, googled this list and the rest of the Net, but I
still can't figure out why this doesn't work:
$ tar xjf *.tar.bz2
tar: beryl-core-0.2.0.tar.bz2: Not found in archive
tar: beryl-manager-0.2.0.tar.bz2: Not found in archive
tar: beryl-plugins-0.2.0.tar.bz2: Not found in archi
On Thu, 15 Mar 2007 09:24:17 +0100
Florian Kulzer <[EMAIL PROTECTED]> wrote:
[snip]
> The wildcard (glob pattern) will be expanded to all the *.tar.bz2
> filenames in one line, separated by spaces. This is fed as the argument
> to tar. It looks like the "extract" action interprets the first filen
On Thu, Mar 15, 2007 at 02:59:01 -0500, Adam Porter wrote:
> I've read the man page, googled this list and the rest of the Net, but I
> still can't figure out why this doesn't work:
>
> $ tar xjf *.tar.bz2
> tar: beryl-core-0.2.0.tar.bz2: Not found in archive
> tar: beryl-manager-0.2.0.tar.bz2: No
On Thu, Mar 15, 2007 at 02:59:01AM -0500, Adam Porter wrote:
> I've read the man page, googled this list and the rest of the Net, but I
> still can't figure out why this doesn't work:
>
> $ tar xjf *.tar.bz2
> tar: beryl-core-0.2.0.tar.bz2: Not found in archive
> tar: beryl-manager-0.2.0.tar.bz2:
I've read the man page, googled this list and the rest of the Net, but I
still can't figure out why this doesn't work:
$ tar xjf *.tar.bz2
tar: beryl-core-0.2.0.tar.bz2: Not found in archive
tar: beryl-manager-0.2.0.tar.bz2: Not found in archive
tar: beryl-plugins-0.2.0.tar.bz2: Not found in archi
27 matches
Mail list logo
