Received: by 2002:a05:6a10:1a4d:0:0:0:0 with SMTP id nk13csp5544615pxb; Mon, 14 Feb 2022 01:26:19 -0800 (PST) X-Google-Smtp-Source: ABdhPJy9h1TBgh83DRBvQZKHH5foNeJZo8E0KKqBLWIJJJ9yq3Vxp7dyiZ4n3t0oIK0cNsShzWqf X-Received: by 2002:a17:90a:780f:: with SMTP id w15mr13720130pjk.139.1644830779498; Mon, 14 Feb 2022 01:26:19 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1644830779; cv=none; d=google.com; s=arc-20160816; b=h+Y1I12Cc8ECXTnrP6MdVhRMeYoVo5aMpXVD0k5qgDEdeKjXPL+7Tcrkcl651CDYVf YI8Y8aZcjoBBbsbTRs3VKERjYaLYJL3UzNxGj33aXoKR28HmghtGVbcfq3SmUYFwzfCs SxkwThmCaiKcxrQYPGuoZnpoMOKnR5tK2GPTq3bIktf8AlmFQL45w2YtqiBzsqnpLXrO d4UCQI8Oo8ftIhhCNUVKoui4kSPJ8ced66Sv1ZQVy2CBJPZoVdNaoFbHrbLnciuIwnBx muL9Z1sOmCdrtQyRPVHxOtM3MGOzr3h4ULDleeDzCRXDwkPOIMKq4xpS+5FUKYtLxXB+ 0/lw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:references:in-reply-to:message-id :date:subject:cc:to:from:dkim-signature; bh=+gMHAHJjUIuVvqgJrQ4D2pppsnOXu6yKlmOVOoarmMg=; b=jQwowir2nt2OdI9Ow6zSyyb2Q/FY88hpRhF27ZZc6NgrnvWqfHRNFNlN7D7NYsFHLX hHDjcXuTe8g2iY1Sid1X08hZfwGejhYWzr/+MR89TW6RD26/HkylIOYVTsV5mDAQsxoD 0ow0MqtLJBOoe8G+uMpOB9x+tmQUbLjAzpq9gMDdygGUBdz05uIAKRJAF3fKj//WcIfM pYhbglMmTqINU2OZ6/uQQ/I+6RhRw44TT2ToMZZ9G9qJ74HoOYuz3MiQZEHVcCFJVPCJ 5v3EwHFX5cEJyqE4CNQ1udcyJZ3t2gwhsKO7Afvw8gHKn0a3p9DmIiEd6SRdNTLQ+SNj zZkQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=F8dJa5kQ; spf=pass (google.com: domain of linux-nfs-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-nfs-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id q22si30919453pfk.45.2022.02.14.01.25.56; Mon, 14 Feb 2022 01:26:19 -0800 (PST) Received-SPF: pass (google.com: domain of linux-nfs-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=F8dJa5kQ; spf=pass (google.com: domain of linux-nfs-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-nfs-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1344904AbiBKUQy (ORCPT + 99 others); Fri, 11 Feb 2022 15:16:54 -0500 Received: from mxb-00190b01.gslb.pphosted.com ([23.128.96.19]:55480 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1347932AbiBKUQw (ORCPT ); Fri, 11 Feb 2022 15:16:52 -0500 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id E3F1BCF9 for ; Fri, 11 Feb 2022 12:16:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1644610610; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=+gMHAHJjUIuVvqgJrQ4D2pppsnOXu6yKlmOVOoarmMg=; b=F8dJa5kQyabKC4Xh8onxamNhJjJKH8Xmi5ROENBKPk4H+rgoSuUz+jBB34TT2eqv+rJTyI fhVi188igaP80cJuOkoim1V+Dq6mXyJuhr7lE3X7fsf6Mmn1ZKQ2GaOzbt/0kQnx2fNCsZ 16cit0wFXAoM7hjSORAVjrxatHGaXu8= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-231-9MkCE9ReNCSz43qK2YdHOA-1; Fri, 11 Feb 2022 15:16:48 -0500 X-MC-Unique: 9MkCE9ReNCSz43qK2YdHOA-1 Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.phx2.redhat.com [10.5.11.22]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id C7E97814246; Fri, 11 Feb 2022 20:16:47 +0000 (UTC) Received: from [10.10.66.2] (ovpn-66-2.rdu2.redhat.com [10.10.66.2]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 695BA10E54FE; Fri, 11 Feb 2022 20:16:47 +0000 (UTC) From: "Benjamin Coddington" To: "Chuck Lever III" Cc: "Steve Dickson" , "Linux NFS Mailing List" Subject: Re: [PATCH v2 1/2] nfsuuid: a tool to create and persist nfs4 client uniquifiers Date: Fri, 11 Feb 2022 15:16:43 -0500 Message-ID: <945849B4-BE30-434C-88E9-8E901AAFA638@redhat.com> In-Reply-To: References: <9c046648bfd9c8260ec7bd37e0a93f7821e0842f.1644515977.git.bcodding@redhat.com> <7642FA55-F3F2-4813-86E2-1B65185E6B36@oracle.com> <3d2992df-7ef7-50ba-4f11-f4de588620d2@redhat.com> <4657F9AE-3B9E-4992-9334-3FF1CF18EF31@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; format=flowed X-Scanned-By: MIMEDefang 2.84 on 10.5.11.22 X-Spam-Status: No, score=-2.8 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_LOW, SPF_HELO_NONE,SPF_NONE,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-nfs@vger.kernel.org On 11 Feb 2022, at 15:00, Chuck Lever III wrote: >> On Feb 11, 2022, at 2:30 PM, Benjamin Coddington >> wrote: >> >> All the arguments for exacting tolerances on how it should be named >> apply >> equally well to anything that implies its output will be used for nfs >> client >> ids, or host ids. > > I completely disagree with this assessment. But how, and in what way? The tool just generates uuids, and spits them out, or it spits out whatever's in the file you specify, up to 64 chars. If we can't have uuid in the name, how can we have NFS or machine-id or host-id? > I object strongly to the name nfsuuid, and you seem to be inflexible. > This > is not a hill I want to die on, however I reserve the right to say "I > told > you so" when it turns out to be a poor choice. How does agreeing with you multiple times in my last response and making further suggestions for names seem inflexible to you? This is the worst part of working over email - I think you're misreading my good humor in the face of a drudging discussion as sarcasm or ill will. Let's find the best name.. I'm still going here. I do really like `persistychars`, but I expect that's too fun for everyone. The name at least gets closer to your bar of describing exactly what the tool does. I'm really tired of arguing over the name, and I'm trying my best to keep some good humor about it, and find something that meets everyone's needs. Ben