uuencode
Hi... I'm playing with uuencode under 3.8/i386 and amd64/current but I can't seem to make it work. I'm trying with a simple text file (I tried binary files too): $ uuencode test.txt begin 644 test.txt - and it never ends. $ uuencode -o test.uu test.txt - it stalls forever and test.uu is mode -- What am I doing wrong here ? I'm kind of lost... Thanks! Regards, Antoine
Re: uuencode
Hello! On Tue, Jan 24, 2006 at 12:33:16PM +, Antoine Jacoutot wrote: Hi... I'm playing with uuencode under 3.8/i386 and amd64/current but I can't seem to make it work. I'm trying with a simple text file (I tried binary files too): $ uuencode test.txt begin 644 test.txt - and it never ends. $ uuencode -o test.uu test.txt - it stalls forever and test.uu is mode -- What am I doing wrong here ? I'm kind of lost... Thanks! Regards, Antoine Read the manual page. uuencode [-m] [-o output_file] [file] name Note that *file* is the optional argument, defaulting to standard input. Kind regards, Hannah.
Re: uuencode
Antoine Jacoutot wrote: $ uuencode test.txt begin 644 test.txt - and it never ends. It waits for input from stdin; ie: cat infile | uuencode # Han
Re: uuencode
Hello! On Tue, Jan 24, 2006 at 01:56:13PM +0100, Han Boetes wrote: Antoine Jacoutot wrote: $ uuencode test.txt begin 644 test.txt - and it never ends. It waits for input from stdin; ie: cat infile | uuencode Hereby you get granted the useless use of cat award. # Han Kind regards, Hannah.
Re: uuencode
Hannah Schroeter wrote: Hello! On Tue, Jan 24, 2006 at 01:56:13PM +0100, Han Boetes wrote: Antoine Jacoutot wrote: $ uuencode test.txt begin 644 test.txt - and it never ends. It waits for input from stdin; ie: cat infile | uuencode Hereby you get granted the useless use of cat award. Really? It does have a didactic use in this case. To make Antoine understand about programs that expect input from stdin. ``grep foo'' also waits like that. Of course a guru would avoid the cat. Hereby you get granted the haughty guru of the week award. ;-D # Han
Re: uuencode
Hello! On Tue, Jan 24, 2006 at 02:27:00PM +0100, Han Boetes wrote: cat infile | uuencode Hereby you get granted the useless use of cat award. Really? It does have a didactic use in this case. To make Antoine understand about programs that expect input from stdin. ``grep foo'' also waits like that. Of course a guru would avoid the cat. It's not as complicated as to need a guru: uuencode infile. And as redirects standard input, it should help for understanding in the same way (perhaps accompanied by the manual page of your favourite shell, e.g. sh(1), section Input/output redirection). Kind regards, Hannah.
Re: uuencode
uuencode test.txt test.txt The parameter is not the file name, it's what is written after the begin (ie the ouyput file name) G
Re: uuencode
Selon Han Boetes [EMAIL PROTECTED]: cat infile | uuencode Ok I found the correct syntax... $ uuencode -o test.uu test.bin test.bin Thank you all who responded ; it was as I supposed a stupid error on my part. -- Antoine
Re: uuencode
Selon Han Boetes [EMAIL PROTECTED]: It waits for input from stdin; ie: cat infile | uuencode No, I already tried this too and it is not working. $ cat test.txt | uuencode usage: uuencode [-m] [-o outfile] [infile] remotefile b64encode [-o outfile] [infile] remotefile $ echo blabla | uuencode usage: uuencode [-m] [-o outfile] [infile] remotefile b64encode [-o outfile] [infile] remotefile
Re: uuencode
Hello! On Tue, Jan 24, 2006 at 01:36:40PM +, Antoine Jacoutot wrote: Selon Han Boetes [EMAIL PROTECTED]: It waits for input from stdin; ie: cat infile | uuencode No, I already tried this too and it is not working. $ cat test.txt | uuencode usage: uuencode [-m] [-o outfile] [infile] remotefile b64encode [-o outfile] [infile] remotefile $ echo blabla | uuencode usage: uuencode [-m] [-o outfile] [infile] remotefile b64encode [-o outfile] [infile] remotefile echo foo | uuencode filename-to-display-at-other-side uuencode filename-to-display-at-other-side test.file Kind regards, Hannah.
