From: Tom Wijsman <TomWij@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: 1i5t5.duncan@cox.net
Subject: Re: [gentoo-dev] Re: Can we have process names and stdout / stderr indication to more efficiently parse build logs? (was: Re: rfc: escape sequences in logs)
Date: Thu, 5 Sep 2013 11:10:38 +0200 [thread overview]
Message-ID: <20130905111038.00b52c7f@TOMWIJ-GENTOO> (raw)
In-Reply-To: <pan$1fae3$17b3c9c4$8767dc62$a710673d@cox.net>
[-- Attachment #1: Type: text/plain, Size: 1509 bytes --]
On Thu, 5 Sep 2013 04:54:46 +0000 (UTC)
Duncan <1i5t5.duncan@cox.net> wrote:
> Kent Fredric posted on Wed, 04 Sep 2013 23:38:40 +1200 as excerpted:
>
> > I see. I have a few gvim instances also reading/writing to that
> > terminal I didn't know about, interesting.
>
> Which brings up the privacy point.
Not really, because those instances wouldn't appear in logs.
> Anything getting this fancy and convoluted in terms of
> implementation is going to have to be very careful to narrow the
> scope of what it's looking at, lest it become the NSA in terms of
> dragnet.
It would be narrowed down to just the processes of the log; so, I don't
think anything special needs to be done.
> Even then, how many people would REALLY trust it, knowing
> the lengths to which it has to go to narrow down and focus in on JUST
> the info it needs? I don't think I'd trust it, for the same reason I
> don't trust the NSA doing similar things under "just trust us"
> pretenses. Would YOU? (Granted, our implementation would presumably
> be open, something the NSA most certainly is NOT, but still...)
You already put trust in us; a tiny feature difference that doesn't
really reveal anything (compared to eg. `emerge --info --verbose`),
isn't going to make a difference in that.
--
With kind regards,
Tom Wijsman (TomWij)
Gentoo Developer
E-mail address : TomWij@gentoo.org
GPG Public Key : 6D34E57D
GPG Fingerprint : C165 AF18 AB4C 400B C3D2 ABF0 95B2 1FCD 6D34 E57D
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2013-09-05 9:10 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-02 19:21 [gentoo-dev] rfc: escape sequences in logs William Hubbs
2013-09-02 19:41 ` Michał Górny
2013-09-02 20:29 ` William Hubbs
2013-09-03 4:00 ` Zac Medico
2013-09-04 13:16 ` [gentoo-dev] " Chris Brannon
2013-09-02 21:22 ` [gentoo-dev] " Ulrich Mueller
2013-09-02 23:59 ` Kent Fredric
2013-09-03 0:22 ` Can we have process names and stdout / stderr indication to more efficiently parse build logs? (was: Re: [gentoo-dev] rfc: escape sequences in logs) Tom Wijsman
2013-09-03 8:25 ` Ulrich Mueller
[not found] ` < 20130903194343.GB26683@waltdnes.org>
2013-09-03 19:03 ` William Hubbs
2013-09-03 20:11 ` Tom Wijsman
2013-09-03 20:41 ` [gentoo-dev] Re: Can we have process names and stdout / stderr indication to more efficiently parse build logs? Alan McKinnon
2013-09-03 21:00 ` Magnus Granberg
2013-09-03 21:10 ` Alan McKinnon
2013-09-03 21:33 ` Tom Wijsman
2013-09-03 21:03 ` Rich Freeman
2013-09-03 21:12 ` Michał Górny
2013-09-03 21:17 ` Rich Freeman
2013-09-03 21:42 ` Tom Wijsman
2013-09-03 21:22 ` Alan McKinnon
2013-09-03 21:44 ` Tom Wijsman
2013-09-04 1:43 ` Walter Dnes
2013-09-04 8:49 ` Tom Wijsman
2013-09-03 21:52 ` Rich Freeman
2013-09-03 21:29 ` Tom Wijsman
2013-09-03 21:16 ` Tom Wijsman
2013-09-04 6:25 ` Duncan
2013-09-04 9:01 ` Tom Wijsman
2013-09-04 6:03 ` Can we have process names and stdout / stderr indication to more efficiently parse build logs? (was: Re: [gentoo-dev] rfc: escape sequences in logs) Kent Fredric
2013-09-04 9:07 ` Tom Wijsman
2013-09-03 19:43 ` Walter Dnes
2013-09-03 20:15 ` Tom Wijsman
2013-09-03 22:57 ` Walter Dnes
2013-09-04 7:17 ` Michał Górny
2013-09-04 9:24 ` Tom Wijsman
2013-09-04 9:59 ` Michał Górny
2013-09-04 10:38 ` Tom Wijsman
2013-09-04 11:38 ` Kent Fredric
2013-09-05 4:54 ` [gentoo-dev] Re: Can we have process names and stdout / stderr indication to more efficiently parse build logs? (was: " Duncan
2013-09-05 9:10 ` Tom Wijsman [this message]
2013-09-04 11:45 ` Can we have process names and stdout / stderr indication to more efficiently parse build logs? (was: Re: [gentoo-dev] " Kent Fredric
2013-09-04 12:21 ` Michał Górny
2013-09-03 4:17 ` [gentoo-dev] rfc: escape sequences in logs Richard Yao
2013-09-03 4:24 ` Kent Fredric
2013-09-03 7:33 ` Tobias Klausmann
2013-09-03 8:44 ` Ulrich Mueller
2013-09-03 7:59 ` Diego Elio Pettenò
[not found] ` <21029.415.94299.937045@a1i15.kph .uni-mainz.de>
[not found] ` <CAATnKFDzLTN76Y=Td_FuSFNVRM8JOX9_ssdTQmJDNedVcvAWNA@mail. gmail.com>
2013-09-03 12:36 ` [gentoo-dev] " Duncan
2013-09-03 13:01 ` Ulrich Mueller
[not found] ` <21029.56744. 939619.943959@a1i15.kph.uni-mainz.de>
2013-09-03 16:19 ` Duncan
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=20130905111038.00b52c7f@TOMWIJ-GENTOO \
--to=tomwij@gentoo.org \
--cc=1i5t5.duncan@cox.net \
--cc=gentoo-dev@lists.gentoo.org \
/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