Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 15 Oct 2019 09:34:34 -0700
From:      Cy Schubert <Cy.Schubert@cschubert.com>
To:        freebsd-hackers@freebsd.org, Mark Johnston <markj@freebsd.org>, Gordon Bergling <gbergling@gmail.com>
Subject:   Re: uname -a default options
Message-ID:  <B50FCD18-08E2-4623-A7B3-F84E387C8090@cschubert.com>
In-Reply-To: <20191015162600.GE26396@raichu>
References:  <F49E4A66-9874-4126-AEEF-5F32FD662668@gmail.com> <20191015162600.GE26396@raichu>

next in thread | previous in thread | raw e-mail | index | archive | help
On October 15, 2019 9:26:00 AM PDT, Mark Johnston <markj@freebsd=2Eorg> wro=
te:
>On Tue, Aug 13, 2019 at 05:41:26PM +0200, Gordon Bergling wrote:
>> Hello List,
>>=20
>> "uname -a" is currently mapping the -a option to =E2=80=9E-mnrsv=E2=80=
=9C, which
>results in something similar like
>>=20
>> $ uname -a
>> FreeBSD lion=2E0xfce3=2Enet 12=2E0-STABLE FreeBSD 12=2E0-STABLE r350835
>GENERIC  amd64
>>=20
>> What would you think about reducing the option mapping for =E2=80=9E-a=
=E2=80=9C to
>=E2=80=9E-vmn=E2=80=9C , which would result in a less repetitive version =
string like
>the one below=2E
>>=20
>> $ uname -vmn
>> lion=2E0xfce3=2Enet FreeBSD 12=2E0-STABLE r350835 GENERIC  amd64
>>=20
>> Adapting this would be trivial, but before I hack something together,
>I would like to get some feedback if such a change would be welcomed?
>
>I'm not sure about the history which led to the current behaviour of
>-a,
>but the unfortunately reality is that changes like the one you propose
>will likely break programs that process uname -a output=2E  Of course,
>such programs should likely be using more specialized uname options
>instead, but the current behaviour of -a has been in place for
>something
>like 25 years, so it's quite likely that something depends on it=2E  In
>these situations I prefer to maintain backwards compatibility=2E
>_______________________________________________
>freebsd-hackers@freebsd=2Eorg mailing list
>https://lists=2Efreebsd=2Eorg/mailman/listinfo/freebsd-hackers
>To unsubscribe, send any mail to
>"freebsd-hackers-unsubscribe@freebsd=2Eorg"

How about a $UNAME_A environment variable? The downside: people will submi=
t PRs taking time from legitimate development=2E



--=20
Pardon the typos and autocorrect, small keyboard in use=2E=20
Cy Schubert <Cy=2ESchubert@cschubert=2Ecom>
FreeBSD UNIX: <cy@FreeBSD=2Eorg> Web: https://www=2EFreeBSD=2Eorg

The need of the many outweighs the greed of the few=2E

Sent from my Android device with K-9 Mail=2E Please excuse my brevity=2E
From owner-freebsd-hackers@freebsd.org  Tue Oct 15 16:48:09 2019
Return-Path: <owner-freebsd-hackers@freebsd.org>
Delivered-To: freebsd-hackers@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 CF66214DBD2
 for <freebsd-hackers@mailman.nyi.freebsd.org>;
 Tue, 15 Oct 2019 16:48:09 +0000 (UTC)
 (envelope-from markjdb@gmail.com)
Received: from mail-qk1-x742.google.com (mail-qk1-x742.google.com
 [IPv6:2607:f8b0:4864:20::742])
 (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits)
 server-signature RSA-PSS (4096 bits)
 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 46t1Zc4Vf6z4VsB
 for <freebsd-hackers@freebsd.org>; Tue, 15 Oct 2019 16:48:08 +0000 (UTC)
 (envelope-from markjdb@gmail.com)
Received: by mail-qk1-x742.google.com with SMTP id u22so19779209qkk.11
 for <freebsd-hackers@freebsd.org>; Tue, 15 Oct 2019 09:48:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
 h=sender:date:from:to:cc:subject:message-id:references:mime-version
 :content-disposition:content-transfer-encoding:in-reply-to
 :user-agent; bh=4bC0HELRv7L2ufEtOWOItZjtkiJoG4ZYJ15fyLmNNTM=;
 b=fbIsK/TJDdHokrY5mSkPK1o3ps+MS7V/ShTYwiqRZEeP00xcNoPgXkYMAQNbHAdTVG
 XMEYqgMonmdNRtd5oSOLC9Jf5JO0aFsvL6Rla/LyJOAzKzhEMioAZGuKtT2ltjoBwrwb
 9ak1bOWIkK/cWluN50MSE+ysXZFDzhzGoWHPxjbG7BXpxelTOx0sxcb4UwBGIHra3hbA
 amw2tLFjYQE6FU0f4OgSymz1e8C2kWdIz50iYe7vQiHNkQsb3ewpLJkVGJn6qc84bJAZ
 zu2y4B2DG0QMjBfXFIuQrCtkNHR10GzeadIx9sUJ4Ir0COeUDmCvyxHPiJiX5oUYikAV
 AZtg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20161025;
 h=x-gm-message-state:sender:date:from:to:cc:subject:message-id
 :references:mime-version:content-disposition
 :content-transfer-encoding:in-reply-to:user-agent;
 bh=4bC0HELRv7L2ufEtOWOItZjtkiJoG4ZYJ15fyLmNNTM=;
 b=lH+i0um7ZbIQOgu2AN1Hm0zeDqKPPzkfya/rKqYGqeJNR718Cs9wtm0D/HfDzZqWz6
 bi3Dd8+OwPqDz1WU9oEImffvGJO+eX7vJRGtCQDv9Us6P8SEsoN91Y2JeoXu+Jd3bagT
 EOPd9TkK9bjcZTdxliqsza/lRbozCTKK+WkL3NcAUEuQxbSqYMl+5WdGxqrAcCyhjyOL
 dyi22Lr7+Eu6bl6zgJufnvsDmN98kViyN1QzXbg0LL1Okl1FjsuYeivIPsArt1s/CzAK
 vH99soZtwC/0/t1ej6librWjdr4FylhaY7Dbr1vlIVr4MgkqZvRC+u+QTk/oE69EITEG
 6yTw==
X-Gm-Message-State: APjAAAUHQDuQzI2T3jASfJ7wwXvkAuJ1OV4U6G33B1vgfM0tcpLqm9Gi
 V6UD25D5KlX57A3zK4AxB31oKphy
X-Google-Smtp-Source: APXvYqzf4LtrHwa5yh4OnMM2ojhNOOZesl14jgzhaL+lw+YRIoSs0dda1uobdn14I2RNdngIIHplBw==
X-Received: by 2002:a05:620a:2f3:: with SMTP id
 a19mr36760923qko.501.1571158087368; 
 Tue, 15 Oct 2019 09:48:07 -0700 (PDT)
Received: from raichu (toroon0560w-lp130-05-69-158-183-252.dsl.bell.ca.
 [69.158.183.252])
 by smtp.gmail.com with ESMTPSA id w73sm10498871qkb.111.2019.10.15.09.48.05
 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256);
 Tue, 15 Oct 2019 09:48:06 -0700 (PDT)
Sender: Mark Johnston <markjdb@gmail.com>
Date: Tue, 15 Oct 2019 12:48:04 -0400
From: Mark Johnston <markj@freebsd.org>
To: Gordon Bergling <gbergling@gmail.com>
Cc: freebsd-hackers@freebsd.org
Subject: Re: uname -a default options
Message-ID: <20191015164804.GG26396@raichu>
References: <F49E4A66-9874-4126-AEEF-5F32FD662668@gmail.com>
 <20191015162600.GE26396@raichu>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <20191015162600.GE26396@raichu>
User-Agent: Mutt/1.12.2 (2019-09-21)
X-Rspamd-Queue-Id: 46t1Zc4Vf6z4VsB
X-Spamd-Bar: --
Authentication-Results: mx1.freebsd.org;
 dkim=pass header.d=gmail.com header.s=20161025 header.b=fbIsK/TJ;
 dmarc=none;
 spf=pass (mx1.freebsd.org: domain of markjdb@gmail.com designates
 2607:f8b0:4864:20::742 as permitted sender) smtp.mailfrom=markjdb@gmail.com
X-Spamd-Result: default: False [-2.01 / 15.00]; ARC_NA(0.00)[];
 RCVD_VIA_SMTP_AUTH(0.00)[];
 R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025];
 NEURAL_HAM_MEDIUM(-1.00)[-0.996,0]; FROM_HAS_DN(0.00)[];
 TO_DN_SOME(0.00)[];
 R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36];
 NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain];
 PREVIOUSLY_DELIVERED(0.00)[freebsd-hackers@freebsd.org];
 DMARC_NA(0.00)[freebsd.org]; RCVD_COUNT_THREE(0.00)[3];
 MIME_TRACE(0.00)[0:+]; TO_MATCH_ENVRCPT_SOME(0.00)[];
 DKIM_TRACE(0.00)[gmail.com:+]; RCPT_COUNT_TWO(0.00)[2];
 RCVD_IN_DNSWL_NONE(0.00)[2.4.7.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org
 : 127.0.5.0]; 
 IP_SCORE(-0.31)[ip: (3.08), ipnet: 2607:f8b0::/32(-2.48), asn: 15169(-2.10),
 country: US(-0.05)]; 
 FORGED_SENDER(0.30)[markj@freebsd.org,markjdb@gmail.com];
 FREEMAIL_TO(0.00)[gmail.com]; MID_RHS_NOT_FQDN(0.50)[];
 FREEMAIL_ENVFROM(0.00)[gmail.com];
 ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US];
 FROM_NEQ_ENVFROM(0.00)[markj@freebsd.org,markjdb@gmail.com];
 RCVD_TLS_ALL(0.00)[]
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
 <freebsd-hackers.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-hackers>, 
 <mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers/>;
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-hackers>, 
 <mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Oct 2019 16:48:09 -0000

On Tue, Oct 15, 2019 at 12:26:00PM -0400, Mark Johnston wrote:
> On Tue, Aug 13, 2019 at 05:41:26PM +0200, Gordon Bergling wrote:
> > Hello List,
> > 
> > "uname -a" is currently mapping the -a option to „-mnrsv“, which results in something similar like
> > 
> > $ uname -a
> > FreeBSD lion.0xfce3.net 12.0-STABLE FreeBSD 12.0-STABLE r350835 GENERIC  amd64
> > 
> > What would you think about reducing the option mapping for „-a“ to „-vmn“ , which would result in a less repetitive version string like the one below.
> > 
> > $ uname -vmn
> > lion.0xfce3.net FreeBSD 12.0-STABLE r350835 GENERIC  amd64
> > 
> > Adapting this would be trivial, but before I hack something together, I would like to get some feedback if such a change would be welcomed?
> 
> I'm not sure about the history which led to the current behaviour of -a,
> but the unfortunately reality is that changes like the one you propose
> will likely break programs that process uname -a output.  Of course,
> such programs should likely be using more specialized uname options
> instead, but the current behaviour of -a has been in place for something
> like 25 years, so it's quite likely that something depends on it.  In
> these situations I prefer to maintain backwards compatibility.

It seems that the mail I replied to is a duplicate of [1], but it
reappeared in my inbox for some reason.  The conclusion there was
basically the same as what I wrote.

[1] https://lists.freebsd.org/pipermail/freebsd-hackers/2019-August/054963.html



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?B50FCD18-08E2-4623-A7B3-F84E387C8090>