From: Daniel Kriesten <daniel.kriesten@etit.tu-chemnitz.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Using PTXdist on Mac OS
Date: Thu, 19 Apr 2012 12:41:21 +0200 [thread overview]
Message-ID: <742DF9D3-D7F9-4E91-B5DB-D5B33C424B8F@etit.tu-chemnitz.de> (raw)
In-Reply-To: <0CD03835-B077-48D9-98B3-D6BD380253BA@etit.tu-chemnitz.de>
[-- Attachment #1.1: Type: text/plain, Size: 1310 bytes --]
Hi Michael,
at leas on a Mac (OS X 10.6.8) the BSD find supports -print0
[me@mymac:ptxdist:master u=] $ ls bin/
awk@ chown@ find@ md5sum@ mknod@ ptxdist* readlink@ rmdir@ stat@ xargs@
chmod@ cp@ install@ mkdir@ mv@ python@ rm@ sed@ tar@
[me@mymac:ptxdist:master u=] $ which find
/usr/bin/find
[me@mymac:ptxdist:master u=] $ find bin -type l -print0 | xargs -0 rm -vf
bin/awk
bin/chmod
bin/chown
bin/cp
bin/find
bin/install
bin/md5sum
bin/mkdir
bin/mknod
bin/mv
bin/python
bin/readlink
bin/rm
bin/rmdir
bin/sed
bin/stat
bin/tar
bin/xargs
[me@mymac:ptxdist:master u=] $ ls bin
ptxdist*
Am 18.04.2012 um 16:28 schrieb Daniel Kriesten:
> Am 18.04.2012 um 16:16 schrieb Michael Olbrich:
> [...]
>> So "find -print0" works, right? I wasn't sure if that's a GNU extension.
>> The xargs man-page I have says "... The GNU find -print0 option produces
>> input suitable for this mode.". So I wasn't sure if this works _only_ with
>> GNU find.
>
> Uh - I'll check that.
Regards,
Daniel
--
Daniel Kriesten
Chair for Circuit and System Design
Chemnitz University of Technology, Reichenhainer Str. 31-33, D-09126 Chemnitz
Phone: +49 371 531-33158, Fax: +49 371 531-833158
http://www.tu-chemnitz.de/etit/sse
[-- Attachment #1.2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 4964 bytes --]
[-- Attachment #2: Type: text/plain, Size: 48 bytes --]
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2012-04-19 10:41 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-09 17:11 Bernhard Walle
2012-04-09 17:48 ` Juergen Beisert
2012-04-10 9:37 ` Bernhard Walle
2012-04-09 18:01 ` Andreas Bießmann
2012-04-09 18:59 ` Bernhard Walle
2012-04-09 19:47 ` Juergen Beisert
2012-04-09 20:04 ` Andreas Bießmann
2012-04-09 20:48 ` Andreas Bießmann
2012-04-10 9:04 ` Bernhard Walle
2012-04-10 18:35 ` Bernhard Walle
2012-04-17 11:08 ` Daniel Kriesten
2012-04-17 11:24 ` Michael Olbrich
2012-04-17 11:45 ` Bernhard Walle
2012-04-17 11:59 ` Daniel Kriesten
2012-04-17 12:03 ` Bernhard Walle
2012-04-17 12:32 ` Daniel Kriesten
2012-04-18 8:29 ` Michael Olbrich
2012-04-18 11:25 ` Daniel Kriesten
2012-04-18 14:16 ` Michael Olbrich
2012-04-18 14:28 ` Daniel Kriesten
2012-04-19 10:41 ` Daniel Kriesten [this message]
2012-04-19 11:29 ` Andreas Bießmann
2012-04-19 12:04 ` Daniel Kriesten
2012-04-19 12:25 ` Andreas Bießmann
2012-04-19 13:12 ` Daniel Kriesten
2012-04-19 13:27 ` Michael Olbrich
2012-04-19 14:03 ` Andreas Bießmann
2012-04-19 20:13 ` Bernhard Walle
2012-12-08 15:31 ` Daniel Kriesten
2012-12-08 15:43 ` [ptxdist] Using PTXdist on Mac OS 10.7 Daniel Kriesten
2012-12-10 8:48 ` Michael Olbrich
2012-12-10 8:46 ` [ptxdist] Using PTXdist on Mac OS Michael Olbrich
2012-12-11 15:00 ` Daniel Kriesten
2012-12-12 11:00 ` Michael Olbrich
2012-04-17 11:48 ` Bernhard Walle
2012-04-17 12:04 ` Daniel Kriesten
2012-04-17 12:18 ` Bernhard Walle
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=742DF9D3-D7F9-4E91-B5DB-D5B33C424B8F@etit.tu-chemnitz.de \
--to=daniel.kriesten@etit.tu-chemnitz.de \
--cc=ptxdist@pengutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox