From owner-freebsd-arch@freebsd.org Sun Feb 9 17:25:04 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 3D5EC23DC7C for ; Sun, 9 Feb 2020 17:25:04 +0000 (UTC) (envelope-from josh@kflag.net) Received: from mail-ed1-x52f.google.com (mail-ed1-x52f.google.com [IPv6:2a00:1450:4864:20::52f]) (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 48FwsB482Dz4LsW for ; Sun, 9 Feb 2020 17:25:02 +0000 (UTC) (envelope-from josh@kflag.net) Received: by mail-ed1-x52f.google.com with SMTP id dc19so5874933edb.10 for ; Sun, 09 Feb 2020 09:25:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kflag.net; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=W7+VUm/gVT9tZV7gQJFh1ikmZsClR9I7C5V7DeaPyNo=; b=Hp0M4lDWFUrZoYKBvvhWEIQQnjqH1jqTqOmgxC5aq+2QAp1YSQRHwwRnxlnIrypBrJ d7WgtAerNZvzfntXi0jwjuVqYyj5EaRiocy7j0qJdlN59gzlaY4Yyu+7TEQy0HpynFu9 2lr/ecn/tKgjS3QrYvN9wQYU1hpyfrfFftPMs= 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=W7+VUm/gVT9tZV7gQJFh1ikmZsClR9I7C5V7DeaPyNo=; b=qxpSLoVrhuhLgHKTFnuhnVEqsJj7hYuMlkEYCBBkwrA2lL5SkjsUdQMwhBPAl9nuvW 1fcEDDBxHlRxRaSfQH+8bMfy96BIuAk9W5Yg3nu9JfCoFAirC9JvASJ+YvtBaCUgJtl7 aLdqyA3ZxnoHqjg+TapEG/FbKENpe1QLO8EckYpHNXhSAfPCBQr7eni5U1aoSa0tFaMq 1Dx7eeG3RrImBEl60MsKjpASBp0gtYyh6vu5h1qtrIboGUN0fAwtDPpsl1OYPPxLT4UN 3T+vau28VX4eOVb6Bjwpj+lgK3dKha2SzAKihVtpa2Otn5lVma/K7AFzwGWe+Ime6BDZ /Y9g== X-Gm-Message-State: APjAAAVo/5x3gjsaMF0BmFSj3R9ye46MCag3ZeGoeGfkJJn3S9InLi3V IkxGVPlv1Cj6onyGwZUyLR/JKGK5dTWtjumdTSxhLGnvowA5kQ== X-Google-Smtp-Source: APXvYqxLJ04nULYVgqDZAlpxWofIc2+CyfG6PxQFBwmNm7erwHi3659m6YJRRTtQWmxknNzi/n1N5hcOjcRcitOqr8c= X-Received: by 2002:a17:906:2649:: with SMTP id i9mr8518054ejc.120.1581269100848; Sun, 09 Feb 2020 09:25:00 -0800 (PST) MIME-Version: 1.0 References: <6701.1581190231@critter.freebsd.dk> <97A66670F59C9C626B5090E3@triton.njm.me.uk> <8967.1581243035@critter.freebsd.dk> <55C50689-6DA8-4D44-92BB-72C38B54AC96@cschubert.com> <202002091350.019DoZrf084564@slippy.cwsent.com> <202002091605.019G5Csj051412@slippy.cwsent.com> In-Reply-To: <202002091605.019G5Csj051412@slippy.cwsent.com> From: Josh Aas Date: Sun, 9 Feb 2020 17:24:50 -0500 Message-ID: Subject: Re: updating cron and atrun To: Cy Schubert Cc: freebsd-arch@freebsd.org, Poul-Henning Kamp , "N.J. Mann" Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 48FwsB482Dz4LsW X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=pass header.d=kflag.net header.s=google header.b=Hp0M4lDW; dmarc=none; spf=none (mx1.freebsd.org: domain of josh@kflag.net has no SPF policy when checking 2a00:1450:4864:20::52f) smtp.mailfrom=josh@kflag.net X-Spamd-Result: default: False [-1.06 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-0.999,0]; R_DKIM_ALLOW(-0.20)[kflag.net:s=google]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; TO_DN_SOME(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arch@freebsd.org]; DMARC_NA(0.00)[kflag.net]; DATE_IN_FUTURE(4.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[kflag.net:+]; RCVD_IN_DNSWL_NONE(0.00)[f.2.5.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.5.4.1.0.0.a.2.list.dnswl.org : 127.0.5.0]; R_SPF_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; IP_SCORE(-2.76)[ip: (-9.55), ipnet: 2a00:1450::/32(-2.48), asn: 15169(-1.73), country: US(-0.05)]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Feb 2020 17:25:04 -0000 I understand that some other operating systems have integrated atrun into cron, but that's not, in and of itself, a reason for FreeBSD to do it. Other operating systems do lots of things not worth copying in FreeBSD. I'm curious to hear if there are actual technical reasons that it's worthwhile for FreeBSD to do it. Even if such integration advantages do exist, they might rest on the assumption that at/atrun is worth keeping in base in the first place. >From what you and others have said, maybe at/atrun doesn't deserve "basic functionality" status you're ascribing to it. I don't know, I'm not an expert on this, but it's a perspective that seems worth considering. In an earlier email you said "People generally have no idea what they do and people are unwilling to chance using them or learning something new..." That doesn't sound like a description of "basic functionality" that necessarily needs to be a part of a base operating system. Vi is a very heavily used program, which many people appreciate being available in base. That is not the case for "at." It's something a small minority of people appreciate, but nonetheless, I agree that they should have access to it. Sounds to me like a great candidate for inclusion in ports. I imagine the default position should be that things are not in base unless there's a strong argument for it, not the other way around. Does FreeBSD have a set of written guidelines for what makes something appropriate for inclusion in the base system? On Sun, Feb 9, 2020 at 11:05 AM Cy Schubert wrote: > > In message om> > , Josh Aas writes: > > There seems to be a real question here about the value of at/atrun. > > Maybe a good compromise is to move that functionality to ports instead > > of the base system. If we integrate the functionality into cron then > > we're basically stuck with it in core. All functionality adds > > complexity, and complexity adds maintenance cost and risk. Sometimes > > that's totally worth it, but I don't think it's clear that saddling > > FreeBSD base with at/atrun because we integrated it with cron for > > unclear reasons is necessarily a good idea. > > That is not a compromise. The functionality has been in cron in Solaris, > AIX, HP-UX, DG/UX, Tru64, and now NetBSD for years, in some cases decades. > Why such a reluctance to maintain basic functionality because it is either > not understood or you never use it? > > Atrun should be integrated into cron, where all other major UNIX and > UNIX-like systems have the function. However when we implement pkgbase > crond(8), crontab(1), and at(1)/batch(1) should be three separate packages, > like Linux distros do. crond(8) could be installed by default whereas > crontab(1) and at(1)/batch(1) would not. > > Moving at(1) and batch(1) to ports would be tantamount to putting vi in > ports because, well, nano is an easier to use editor. (Yes, we did that at > $JOB on our RHEL servers for a while because vi is too hard for most people > to use, it used up valuable space, and only installed it if a customer > specifically requested it. That policy is no more but that it was makes my > point. We now install vim and nano.) You get my point. The fact that some > people don't understand a utility and don't have the time or patience to > learn it (yes, we're all busy, like at $JOB, and taking time out to learn > something, like at $JOB, has a cost) doesn't mean it's not useful. > > Coming from a SunOS, Solaris, HP-UX, DG/UX, Tru64 background, at(1) and > batch(1) are a basic function of cron, even if some in the Linux community > feel they're not. > > > -- > Cheers, > Cy Schubert > FreeBSD UNIX: Web: http://www.FreeBSD.org > > The need of the many outweighs the greed of the few. > > > > > > > > -- Josh Aas (215) 206-2020