From owner-freebsd-arch@freebsd.org Thu Sep 24 21:35:18 2020 Return-Path: Delivered-To: freebsd-arch@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 1C1593E12EA for ; Thu, 24 Sep 2020 21:35:18 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from smtp-out-so.shaw.ca (smtp-out-so.shaw.ca [64.59.136.139]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Client", Issuer "CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4By7cj098qz4Ghm; Thu, 24 Sep 2020 21:35:16 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from spqr.komquats.com ([70.67.125.17]) by shaw.ca with ESMTPA id LYtVkCzneHxtDLYtWk05B4; Thu, 24 Sep 2020 15:35:15 -0600 X-Authority-Analysis: v=2.4 cv=Ce22WJnl c=1 sm=1 tr=0 ts=5f6d1113 a=VFtTW3WuZNDh6VkGe7fA3g==:117 a=VFtTW3WuZNDh6VkGe7fA3g==:17 a=xqWC_Br6kY4A:10 a=kj9zAlcOel0A:10 a=reM5J-MqmosA:10 a=iKhvJSA4AAAA:8 a=ypVJL4-jAAAA:8 a=YxBL1-UpAAAA:8 a=6I5d2MoRAAAA:8 a=EkcXrb_YAAAA:8 a=Ry37uF0CeVfSWXlgR6sA:9 a=CjuIK1q_8ugA:10 a=odh9cflL3HIXMm4fY7Wr:22 a=khIbc0fXALFIcTpOSxgJ:22 a=Ia-lj3WSrqcvXOmTRaiG:22 a=IjZwj45LgO3ly-622nXo:22 a=LK5xJRSDVpKd5WXXoEvA:22 Received: from slippy.cwsent.com (slippy [IPv6:fc00:1:1:1::5b]) by spqr.komquats.com (Postfix) with ESMTPS id 673EF339; Thu, 24 Sep 2020 14:35:12 -0700 (PDT) Received: from slippy (localhost [127.0.0.1]) by slippy.cwsent.com (8.16.1/8.16.1) with ESMTP id 08OLZAkQ036749; Thu, 24 Sep 2020 14:35:11 -0700 (PDT) (envelope-from Cy.Schubert@cschubert.com) Message-Id: <202009242135.08OLZAkQ036749@slippy.cwsent.com> X-Mailer: exmh version 2.9.0 11/07/2018 with nmh-1.7.1 Reply-to: Cy Schubert From: Cy Schubert X-os: FreeBSD X-Sender: cy@cwsent.com X-URL: http://www.cschubert.com/ To: "Rodney W. Grimes" cc: "Greg 'groggy' Lehey" , freebsd-arch@freebsd.org, Shawn Webb Subject: Re: Refactoring calendar(1) (was: svn commit: r365984 - head/usr.bin/calendar/calendars) In-reply-to: <202009241555.08OFtjKx047062@gndrsh.dnsmgr.net> References: <202009241555.08OFtjKx047062@gndrsh.dnsmgr.net> Comments: In-reply-to "Rodney W. Grimes" message dated "Thu, 24 Sep 2020 08:55:45 -0700." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 24 Sep 2020 14:35:10 -0700 X-CMAE-Envelope: MS4xfHjSxkDmnsSTUychXb6ePnlSkkq4Xk6+Mlke9VGriGYKTmK0JyqiTCHiwm87f1Vxam0cCNH5mZgAoBgEWAIRtTprdoUHLH3HqdA9HiH10AveARanizUD FXlFkiX5DX1i9gk3eQr8HkGJkM0f7j/ZVAi+RA6TyZwlBkmNFcTh2MCPJ2I9jwZfLSigeInFh1zxlPxjOF5EVP9pF5KLIdmsnSqznWIPZGD8vzL+deJkbb5O v0sIVm0tcgprHC64uN5zn3m3WdbQiCGZRyv2ouvkvDetZpRrohtd+Gw+eNT6pq67FBVZF/g8dng+osulTQDkpw== X-Rspamd-Queue-Id: 4By7cj098qz4Ghm X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of cy.schubert@cschubert.com has no SPF policy when checking 64.59.136.139) smtp.mailfrom=cy.schubert@cschubert.com X-Spamd-Result: default: False [-0.92 / 15.00]; HAS_REPLYTO(0.00)[Cy.Schubert@cschubert.com]; RCVD_VIA_SMTP_AUTH(0.00)[]; REPLYTO_EQ_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; MV_CASE(0.50)[]; NEURAL_HAM_LONG(-0.85)[-0.851]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[cschubert.com: no valid DMARC record]; ARC_NA(0.00)[]; TO_DN_SOME(0.00)[]; AUTH_NA(1.00)[]; RCVD_COUNT_THREE(0.00)[4]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_HAM_SHORT(-0.57)[-0.574]; NEURAL_HAM_MEDIUM(-0.79)[-0.792]; R_SPF_NA(0.00)[no SPF record]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:6327, ipnet:64.59.128.0/20, country:CA]; RCVD_TLS_LAST(0.00)[]; MAILMAN_DEST(0.00)[freebsd-arch]; RCVD_IN_DNSWL_LOW(-0.10)[64.59.136.139:from] X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Sep 2020 21:35:18 -0000 In message <202009241555.08OFtjKx047062@gndrsh.dnsmgr.net>, "Rodney W. Grimes" writes: > -- Start of PGP signed section. > > [Trimmed] > > > > People, please adjust your posts. It's hard fighting your way through > > a lot of expired verbiage. > > > > On Wednesday, 23 September 2020 at 9:18:27 -0600, Warner Losh wrote: > > > On Wed, Sep 23, 2020 at 7:43 AM Shawn Webb > > > wrote: > > > > > >> Would it make sense to prune calendar entries to only BSD-related > > >> entries? > > > > > > Fortunately, I have already contacted grog@ directly. He was quite > > > receptive to my email suggesting something be done. After a couple of > > > rounds, there's the rough plan we're talking about. Briefly: > > > > > > 1. ... > > > > > > So, it's just an outline at this time, which is why I hadn't sent a > > > concrete proposal here just yet. Wanted to at least get a list of > > > the files that would remain so we can have an intelligent discussion > > > about those, but since this showed up I thought I'd send a heads up > > > so people know what's going on. > > > > The real issue is: what do we remove? Summarizing imp@'s points, I > > think that the base functionality of calendar(1) should stay, and so > > should the FreeBSD-related calendar files. There's really a question > > as to whether the non-FreeBSD related ones should remain anywhere > > (including as a port). As somebody said, they're a relict of a bygone > > day, and some are very inaccurate. I seem to be the only one > > maintaining them, and even that is not without criticism. It might be > > a better idea to write a completely new port that sucks in calendar > > entries from *somewhere* and makes BSD-compliant calendar files out of > > them. So, as imp@ says, it would be good to discuss which files > > should go and which should remain. > > > > While I have your attention, does anybody think that the -a option of > > calendar(1) is worth keeping? It goes through *all* calendar files on > > a system and mails them to the owner. It has the interesting side > > effect (we wouldn't want to call it a bug) that root gets three copies > > (one each for root, toor and daemon). I can't see anything useful > > there that a per-user cron job can't do. > > What the per-user cron job does is create a larger workload for > systems that are expecting all users to be running calendar, as > possible in an acedemic system which each student has a login. Have it use libxo might be a good exercise for someone wanting to get back into it after a while, or a student. -- Cheers, Cy Schubert FreeBSD UNIX: Web: https://FreeBSD.org NTP: Web: https://nwtime.org The need of the many outweighs the greed of the few.