From owner-freebsd-arch@FreeBSD.ORG Mon Sep 8 21:38:42 2014 Return-Path: Delivered-To: freebsd-arch@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5E9724A2; Mon, 8 Sep 2014 21:38:42 +0000 (UTC) Received: from wonkity.com (wonkity.com [67.158.26.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "wonkity.com", Issuer "wonkity.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 12FE71012; Mon, 8 Sep 2014 21:38:41 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.9/8.14.9) with ESMTP id s88LcdfK074301 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 8 Sep 2014 15:38:39 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.9/8.14.9/Submit) with ESMTP id s88Lcdqh074298; Mon, 8 Sep 2014 15:38:39 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Mon, 8 Sep 2014 15:38:39 -0600 (MDT) From: Warren Block To: Bryan Drewery Subject: Re: /etc/motd summary In-Reply-To: <540E18ED.1070003@FreeBSD.org> Message-ID: References: <540E18ED.1070003@FreeBSD.org> User-Agent: Alpine 2.11 (BSF 23 2013-08-11) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (wonkity.com [127.0.0.1]); Mon, 08 Sep 2014 15:38:39 -0600 (MDT) Cc: freebsd-arch@FreeBSD.org X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Sep 2014 21:38:42 -0000 On Mon, 8 Sep 2014, Bryan Drewery wrote: > On 9/8/2014 2:08 PM, Warren Block wrote: >> Summarizing the responses and changes to /etc/motd: >> >> Using ANSI has both philosphical and practical problems, and should be >> avoided. In short, it has cooties. >> >> Extra horizontal whitespace is the least likely to cause problems as >> command delimiters, and inoffensive to most responders. Rearranging >> the information into a list of URLs is a net win. >> >> Shorter is better. A simpler motd that links to a single web page >> might be acceptable. >> >> My suggestions: >> >> Short-term: >> >> Here is the most popular/least objectionable version with all of the >> suggestions implemented as best I could: >> >> http://www.wonkity.com/~wblock/motd/motd.whitespace-url > > For other languages, replace "en" with a language code like de or fr. > > Should de and fr also be quoted? That was intentional. The "en" being the part that the user is to replace, there is no ambiguity with those quotes--they don't exist in the source. With the de and fr, no quotes are shown so the user is not tempted to enter them, and the de alone shows that the final period after fr is not part of the language code. > I don't mean to bikeshed on this but I find the spaced commands > confusing. I find quoted commands more readable: > > Please include the output of 'uname -a' and any relevant error messages... > Use 'man man' for an introduction to manual pages. 'man hier' > describes the. > > or `cmd` or `cmd' Right, but you are used to the conventions. The idea here is to only show the reader what they have to type* without forcing them to interpret. % 'uname -a' uname -a: Command not found. % 'man man' man man: Command not found. % `man hier` Unknown user: ftp;. % `man hier' Unmatched `. The third one is particularly intriguing. [*: admittedly, we are not telling them that they have to press Enter. There is just not enough space for a quick intro on entering CLI commands. But we could have one on a "FreeBSD Support Links" page.]