From owner-freebsd-arch@freebsd.org Sat Feb 17 15:51:53 2018 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8E11FF1AA57 for ; Sat, 17 Feb 2018 15:51:53 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 30BB78654A for ; Sat, 17 Feb 2018 15:51:53 +0000 (UTC) (envelope-from ian@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id E90DCF1AA56; Sat, 17 Feb 2018 15:51:52 +0000 (UTC) Delivered-To: arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D674DF1AA54 for ; Sat, 17 Feb 2018 15:51:52 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound1b.ore.mailhop.org (outbound1b.ore.mailhop.org [54.200.247.200]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 63CAB86545 for ; Sat, 17 Feb 2018 15:51:52 +0000 (UTC) (envelope-from ian@freebsd.org) X-MHO-User: 6ac8c2f9-13fa-11e8-bb8e-b35b57339d60 X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 67.177.211.60 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [67.177.211.60]) by outbound1.ore.mailhop.org (Halon) with ESMTPSA id 6ac8c2f9-13fa-11e8-bb8e-b35b57339d60; Sat, 17 Feb 2018 15:51:29 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id w1HFpgZo049613; Sat, 17 Feb 2018 08:51:43 -0700 (MST) (envelope-from ian@freebsd.org) Message-ID: <1518882702.72050.204.camel@freebsd.org> Subject: Re: ps output line length change From: Ian Lepore To: Cy Schubert , mike@karels.net Cc: arch@freebsd.org Date: Sat, 17 Feb 2018 08:51:42 -0700 In-Reply-To: <201802170203.w1H23ZTE023044@slippy.cwsent.com> References: <201802170203.w1H23ZTE023044@slippy.cwsent.com> Content-Type: text/plain; charset="ISO-8859-1" X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Feb 2018 15:51:53 -0000 On Fri, 2018-02-16 at 18:03 -0800, Cy Schubert wrote: > In message <201802170046.w1H0kvxN032252@mail.karels.net>, Mike Karels  > writes: > > > > [...] > Agreed. I also agree scripts that expect wide output without ww are  > broken. However Linux ps, at least Red Hat, behaves the same. I believe  > the change was made to be more Linux compatible and allow greater  > portability. > > > > > > > What do people think should be done? > That's a tough one. Break Linux compatibility or break BSD  > compatibility? > > Generally Linux users use ps -ef which we don't support and columns are  > different so, Linux compatibility is... well just isn't. > > My vote is to revert and have an environment variable with defaults,  > e.g., PS=--linux or something similar. > > Linux compatibility is good and desirable, right up to the point where it stomps on BSD compatibility.  I think we should revert to historic behavior. I'm agnostic about whether an env var is a good idea or not.  I use the env vars for LESS and TOP and love the idea, but hate hate hate the names (I've fought with conflicts on the too-common name TOP multiple times over the years, most recently just last week my env var TOP confused some makefile that had a TOP var in it).  Could the var be named something like PS_OPTS? -- Ian