From owner-freebsd-current@freebsd.org Fri May 14 01:43:57 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id E104F6355B5 for ; Fri, 14 May 2021 01:43:57 +0000 (UTC) (envelope-from jakehfreebsd@gmail.com) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 4FhBC14Bbfz4Zy5 for ; Fri, 14 May 2021 01:43:57 +0000 (UTC) (envelope-from jakehfreebsd@gmail.com) Received: by mailman.nyi.freebsd.org (Postfix) id 8FEF2635812; Fri, 14 May 2021 01:43:57 +0000 (UTC) Delivered-To: current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 8FB8C6352F6 for ; Fri, 14 May 2021 01:43:57 +0000 (UTC) (envelope-from jakehfreebsd@gmail.com) Received: from mail-ot1-x335.google.com (mail-ot1-x335.google.com [IPv6:2607:f8b0:4864:20::335]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4FhBC13Wlmz4Zc9 for ; Fri, 14 May 2021 01:43:57 +0000 (UTC) (envelope-from jakehfreebsd@gmail.com) Received: by mail-ot1-x335.google.com with SMTP id d3-20020a9d29030000b029027e8019067fso25191124otb.13 for ; Thu, 13 May 2021 18:43:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=uGXmftd3aoDdOjcqNt97xRGmAumt7mEYTngDRnmANGs=; b=t81e0YiOsIaThIBeqCJyoTfbtXPYgjo2ZYUhBFojtq7Ng3dTKR9JBI6MtUzRlD+NBw acZ7ZudsM6v3xbq/Dvvwh+YA2aVX9pVTnV2KqHlkliXFQxNT4Yn8Bz7TpY4qDmMVkPgd iLq6MyTTpvAI9BQQZR3vX4/kGxkRtEnE/He8wTWDou/KaBp+wsBVDq5d+9tEk4cEQxRe X5+Vgs2X1DlEWNfdsnrGYtI/CzzT6YKSgt0snw5alD7UtYykQvZ773QQ/Js8GKtuizct IF5+F+1Gwe9kqgT6WuNsf+aDZmsDGeGXZcYr4XDrwP6Qy85TW+1KhQiAxPlr/uf7gSei KSCw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=uGXmftd3aoDdOjcqNt97xRGmAumt7mEYTngDRnmANGs=; b=O36IiHfxCEqdFQylsAJDUJ7p6riWLUr7ijHyKblqZ2qiFDsLWMVAEcOVpgSBAK2DXO QpPDxjDMhuakOjTTROtZ870VlawyQK6lUXBbzhPHYWo00DX/sfnxIqscw4ubdDiOmYZb M2g2+cYXFp9ozVDOs93bAvQOfbSFgpvoDdFmW1WQbEguvoQeSl+5i9ao+7JDNrp7aVoZ jlOponCgcbWxh1w+7KbOmBSBWjti8VDGsn+TC7ppTXIjEpBl+7W7hkNDcU9dSfT9OU49 94EC/fQFUufhqtS7E+KMtebcw5P8iJ2uXqMlqDQCxdadTIKrLVKdWPhI+NMeQVyqwLrN uXiQ== X-Gm-Message-State: AOAM531+DMPc0iekzHwjLFaG8X0XllQsaO9mprhEDVtu4ejMDzLiifLC 6+0ihtTfEyr/iBDc6ezNYTXxu5W9JJMIRb4XevKS9rFKTzVqzQ== X-Google-Smtp-Source: ABdhPJyNOmaminIk5G8GAiq4VeF/bJJmZczRYGQfqBN99qwS6oEAfi7RPQLwetYIJQnSL6kgSGnSRTE9/2EdeVePqI8= X-Received: by 2002:a05:6830:351:: with SMTP id h17mr7392964ote.320.1620956636216; Thu, 13 May 2021 18:43:56 -0700 (PDT) MIME-Version: 1.0 References: <6070.1620907795@critter.freebsd.dk> <202105131913.14DJDCZa077839@gndrsh.dnsmgr.net> In-Reply-To: <202105131913.14DJDCZa077839@gndrsh.dnsmgr.net> From: jake h Date: Fri, 14 May 2021 11:43:45 +1000 Message-ID: Subject: Re: HEADSUP: i2c(8) has been washed and ironed To: "Rodney W. Grimes" Cc: Poul-Henning Kamp , current@freebsd.org X-Rspamd-Queue-Id: 4FhBC13Wlmz4Zc9 X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.34 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 May 2021 01:43:57 -0000 > What about adding a new flag to enable strtoul behavior? I have had a look at the available flag options for a potential strtoul flag, and a flag that makes sense to me is [-s] / [--strtoul]. [-s] is not currently being used in i2c, if we wanted to use it. On Fri, May 14, 2021 at 5:13 AM Rodney W. Grimes < freebsd-rwg@gndrsh.dnsmgr.net> wrote: > > I have renovated the i2c(8) program and while I belive all argument > > processing is 100% compatible, various undocumented aspects of the > > program may have changed, amongst these precisely what goes to > > stdout and stderr. > > > > Apologies if this breaks any of your scripts. > > > > > > > > There is one aspect of this program which I have not changed, but > > which bugs me utterly: All arguments are in hex, except [-c count] > > which is decimal. > > > > My personal preference would be if all the arguments called strtoul(3) > > with zero third argument, so that users can use decimal, octal or > > hex as they prefer, but I fear that would break pretty much every > > single script. > > > > Alternatively [-c count] could be changed to be hex like the rest. > > What about adding a new flag to enable strtoul behavior? > Or invoked by another name i2cX and install a hard link? > > > > > > > phk@FreeBSD.ORG | TCP/IP since RFC 956 > -- > Rod Grimes > rgrimes@freebsd.org > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >