Date: Fri, 1 Oct 2004 13:37:50 -0700 From: Kris Kennaway <kris@obsecurity.org> To: Andrey Slusar <anray@inet.ua> Cc: Kris Kennaway <kris@obsecurity.org> Subject: Re: [5.3-BETA6] uuencode Message-ID: <20041001203750.GA84103@xor.obsecurity.org> In-Reply-To: <86mzz6mkm3.fsf@santinel.home.ua> References: <864qle7gs2.fsf@santinel.home.ua> <20041001163427.GB71766@xor.obsecurity.org> <86mzz6mkm3.fsf@santinel.home.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
--RnlQjJ0d97Da+TV1 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Oct 01, 2004 at 08:08:52PM +0300, Andrey Slusar wrote: > > > uuencode is not worked under FreeBSD 5.3-BETA6 >=20 > > Yes it does, this just isn't how you use it ;) > uuenview is worked: > ,---- > | anray@santinel:~$ uuenview -u bash-completion-20040711.tar.gz=20 Fine, but that's a different application with different syntax. > uuencode: > ,---- > | anray@santinel:~$ uuencode bash-completion-20040711.tar.gz=20 > | begin 644 bash-completion-20040711.tar.gz > |=20 > `---- > ? See the manpage: uuencode [file] name encodes <file> with name <name>. If you omit <file> (i.e. give only one argument), then it encodes stdin with output <name>. Kris --RnlQjJ0d97Da+TV1 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBXcAdWry0BWjoQKURAuB9AKCEQiRLN17q0fH+1YLiH8is9MNntACeOkYy zaBSPqKilojfhS0v1TGPLbU= =Y5K8 -----END PGP SIGNATURE----- --RnlQjJ0d97Da+TV1--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041001203750.GA84103>