Delivery-Date: Sat, 23 Jan 2016 18:30:08 -0500
Return-Path: <tor-talk-bounces@lists.torproject.org>
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on moria.seul.org
X-Spam-Level: 
X-Spam-Status: No, score=-4.1 required=5.0 tests=BAYES_00,DKIM_ADSP_CUSTOM_MED,
	DKIM_SIGNED,FREEMAIL_FROM,RCVD_IN_DNSWL_MED,T_DKIM_INVALID,T_RP_MATCHES_RCVD
	autolearn=ham version=3.3.1
X-Original-To: archiver@seul.org
Delivered-To: archiver@seul.org
Received: from eugeni.torproject.org (eugeni.torproject.org [38.229.72.13])
	(using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by khazad-dum.seul.org (Postfix) with ESMTPS id EBBA21E0AB2;
	Sat, 23 Jan 2016 18:30:06 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 494FB36571;
	Sat, 23 Jan 2016 23:30:02 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 76C692163D
 for <tor-talk@lists.torproject.org>; Sat, 23 Jan 2016 23:29:55 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at 
Received: from eugeni.torproject.org ([127.0.0.1])
 by localhost (eugeni.torproject.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id BnvtH7oxECof for <tor-talk@lists.torproject.org>;
 Sat, 23 Jan 2016 23:29:55 +0000 (UTC)
Received: from mail-ig0-x229.google.com (mail-ig0-x229.google.com
 [IPv6:2607:f8b0:4001:c05::229])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id 54E3D2411B
 for <tor-talk@lists.torproject.org>; Sat, 23 Jan 2016 23:29:55 +0000 (UTC)
Received: by mail-ig0-x229.google.com with SMTP id z14so13936642igp.1
 for <tor-talk@lists.torproject.org>; Sat, 23 Jan 2016 15:29:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:in-reply-to:references:from:date:message-id:subject:to
 :content-type; bh=odQJ6jiT3ChzFoGwW+Y0FcmPyfE8BgjJwgi+kyLUrxQ=;
 b=KGjJobGoNgG2zCnuA+1Xo7OrOkIrwhiLTb0EHmZ64ncm5T7xwVzY5arvJOdw0OSqqm
 8Mw6PNdPgmJ4Lxjd5k3Hmk/4Wc2H8AujieLiyHo86RFQsGOQmXxkNwXoEBV2wBh3wunp
 aJecjBUpd8Yj/uEFmyWG/NOUE5cqx7NGQ9DpiZVrBniYzlrKEzEjm0efgJRawhr0/Wba
 2XQreDpy+JsYLgolujpXnjxvuJ16bdXzVLLdE5pRwj8er4ipCWis/WjcIEuMJMNDeYdA
 +KGedvfOb4zaTT7TaSXk5ncCOD/SYmz9VPvZNTQXX2DtCK6AcUnHry8fU205lIlxncdz
 n63g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20130820;
 h=x-gm-message-state:mime-version:in-reply-to:references:from:date
 :message-id:subject:to:content-type;
 bh=odQJ6jiT3ChzFoGwW+Y0FcmPyfE8BgjJwgi+kyLUrxQ=;
 b=WMN9wiz6nhHDQoA66xbgGZDJh72V1qgLZc8fj+WSteReUQL2ZVKUXazqXAqampRpeH
 VZIIhLhx2SFqc3XTz3/GiX9XlmCXvkfSGeR3JOUmaamPJG6bq0sZMAg4VfixEHylTjHm
 yD/cgfZs32va5ZwT7uP3qi+HpuhqI9P/CP9WbKXhVrvzSrBMQkaV3/yV+dFIbazbNE/B
 RN9LfuhLJLp5WCOT/hR27+XyGy16xvRNZlk6L6TvrQ3lQPCSZZYoHtm927zs3ecYduIN
 DkN/u6S1dv8mdx1/uQXl+VYQel0vs3qgZzg5kzVKQWANEdEWB3K2xXZA0kJJcHQcBJzx
 yVOA==
X-Gm-Message-State: AG10YORippqy9F8RD8AEer/Y1VUZXRylmTWNk8UQFXTfieZqCIm7SCfwJ45V8ZR6Jg30pmvdstnvor5/wFU9Sw==
X-Received: by 10.50.126.8 with SMTP id mu8mr10024788igb.52.1453591793001;
 Sat, 23 Jan 2016 15:29:53 -0800 (PST)
MIME-Version: 1.0
Received: by 10.36.137.197 with HTTP; Sat, 23 Jan 2016 15:29:13 -0800 (PST)
In-Reply-To: <975f6dce11caa36e05b79e0b6172bacf@blackmesa.at>
References: <20160116212250.GA14827@ix-293.local> <n7p00n$ia8$1@ger.gmane.org>
 <20160123191442.GA2981@ix.home>
 <975f6dce11caa36e05b79e0b6172bacf@blackmesa.at>
From: grarpamp <grarpamp@gmail.com>
Date: Sat, 23 Jan 2016 18:29:13 -0500
Message-ID: <CAD2Ti2-iaD0yct=2215rsG7QEP7WQSpoQcw3hQYoDLn-C8FjpQ@mail.gmail.com>
To: tor-talk@lists.torproject.org
Subject: Re: [tor-talk] Kernel OOPS through Tor - report or ignore?
X-BeenThere: tor-talk@lists.torproject.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: tor-talk@lists.torproject.org
List-Id: "all discussion about theory, design,
 and development of Onion Routing" <tor-talk.lists.torproject.org>
List-Unsubscribe: <https://lists.torproject.org/cgi-bin/mailman/options/tor-talk>, 
 <mailto:tor-talk-request@lists.torproject.org?subject=unsubscribe>
List-Archive: <http://lists.torproject.org/pipermail/tor-talk/>
List-Post: <mailto:tor-talk@lists.torproject.org>
List-Help: <mailto:tor-talk-request@lists.torproject.org?subject=help>
List-Subscribe: <https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk>, 
 <mailto:tor-talk-request@lists.torproject.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: tor-talk-bounces@lists.torproject.org
Sender: "tor-talk" <tor-talk-bounces@lists.torproject.org>

On Sat, Jan 23, 2016 at 4:05 PM, creo <creo-tor-lists@blackmesa.at> wrote:
> Does it make sense to report the content of the oops notice and

Typically
Kernel panics go to the OS people.
Program crashes go to the app people.
Neither should happen, so people should report them.

> wait, I'd better get the node up and doing some work again ;-)

Then if it gets us closer to onioncat v2, sure ;)
-- 
tor-talk mailing list - tor-talk@lists.torproject.org
To unsubscribe or change other settings go to
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk

