Re: [dsfjdssdfsd] Any plans for drafts or discussions on here?

"Dan Harkins" <dharkins@lounge.org> Thu, 23 January 2014 01:36 UTC

Return-Path: <dharkins@lounge.org>
X-Original-To: dsfjdssdfsd@ietfa.amsl.com
Delivered-To: dsfjdssdfsd@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CD0EE1A0348 for <dsfjdssdfsd@ietfa.amsl.com>; Wed, 22 Jan 2014 17:36:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.867
X-Spam-Level:
X-Spam-Status: No, score=-3.867 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TRU4xGIWAgYZ for <dsfjdssdfsd@ietfa.amsl.com>; Wed, 22 Jan 2014 17:36:31 -0800 (PST)
Received: from colo.trepanning.net (colo.trepanning.net [69.55.226.174]) by ietfa.amsl.com (Postfix) with ESMTP id 98EAD1A01B7 for <dsfjdssdfsd@ietf.org>; Wed, 22 Jan 2014 17:36:31 -0800 (PST)
Received: from www.trepanning.net (localhost [127.0.0.1]) by colo.trepanning.net (Postfix) with ESMTP id 0155410224008; Wed, 22 Jan 2014 17:36:30 -0800 (PST)
Received: from 205.201.168.123 (SquirrelMail authenticated user dharkins@lounge.org) by www.trepanning.net with HTTP; Wed, 22 Jan 2014 17:36:31 -0800 (PST)
Message-ID: <82535cea19e2c6434090b94565e652f5.squirrel@www.trepanning.net>
In-Reply-To: <201401230025.s0N0PxMU080596@givry.fdupont.fr>
References: <201401230025.s0N0PxMU080596@givry.fdupont.fr>
Date: Wed, 22 Jan 2014 17:36:31 -0800 (PST)
From: "Dan Harkins" <dharkins@lounge.org>
To: "Francis Dupont" <Francis.Dupont@fdupont.fr>
User-Agent: SquirrelMail/1.4.14 [SVN]
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
Cc: dsfjdssdfsd@ietf.org, Paul Hoffman <paul.hoffman@vpnc.org>
Subject: Re: [dsfjdssdfsd] Any plans for drafts or discussions on here?
X-BeenThere: dsfjdssdfsd@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "The dsfjdssdfsd list provides a venue for discussion of randomness in IETF protocols, for example related to updating RFC 4086." <dsfjdssdfsd.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dsfjdssdfsd>, <mailto:dsfjdssdfsd-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dsfjdssdfsd/>
List-Post: <mailto:dsfjdssdfsd@ietf.org>
List-Help: <mailto:dsfjdssdfsd-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dsfjdssdfsd>, <mailto:dsfjdssdfsd-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jan 2014 01:36:33 -0000

On Wed, January 22, 2014 4:25 pm, Francis Dupont wrote:
>  In your previous mail you wrote:
>
>>  > That seems like a strawman: who says that there is a "single source"
>> of
>>  > ideas for how to implement randomness? Three large server OSs (Linux,
>>  > FreeBSD, Windows) all do it differently.
>>
>>    The single source is "your OS". While there are 3 large server OSs,
>> there
>>  is no single application that can obtain randomness from all three
>> since
>>  there is no application that runs on all of them
>
> => I know many applications which run on these 3 OSs (and more, i.e.,
> Solaris, AIX and HP-UX too if you limit to still alive OSs).
> So either I didn't understand you or we are not talking about the same
> thing...

  If you take the executable from Solaris and copy it onto your HP-UX
machine it will not run.

  My point was that there were not 3 sources (Paul mentioned 3)
available to an application, there is just one: the one that's part of
OS that the application happened to be compiled for.

>>  (and my experience is
>>  that a single linux application won't necessarily work from version X
>> of
>>  the OS to version Y-- hell, sometimes the source won't even compile).
>
> => change your application developer?

  Ha, ha. Funny. I have considered firing myself several times.

  The issue was not the code I was writing, it is the annoying habit of
linux driver developers to change data structures (the one in question
was for an 802.11 device) in gratuitous ways that cause breakage. I
have never had that problem with freeBSD. In fact, the inability of an
application to just compile from one OS release to another is touted
as a feature by some of the more zealous linux people.

  Dan.