From nobody Sun Jan 14 18:04:10 2024
X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
	by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4TCjp55CMkz56nGF
	for <freebsd-current@mlmmj.nyi.freebsd.org>; Sun, 14 Jan 2024 18:04:13 +0000 (UTC)
	(envelope-from lyndon@orthanc.ca)
Received: from orthanc.ca (orthanc.ca [208.79.93.154])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
	 key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA512)
	(Client did not present a certificate)
	by mx1.freebsd.org (Postfix) with ESMTPS id 4TCjp50Hylz4bQd;
	Sun, 14 Jan 2024 18:04:12 +0000 (UTC)
	(envelope-from lyndon@orthanc.ca)
Authentication-Results: mx1.freebsd.org;
	none
Received: from orthanc.ca (localhost [127.0.0.1])
	by orthanc.ca (OpenSMTPD) with ESMTP id 3f217a68;
	Sun, 14 Jan 2024 10:04:10 -0800 (PST)
From: "Lyndon Nerenberg (VE7TFX/VE6BBM)" <lyndon@orthanc.ca>
To: Warner Losh <imp@bsdimp.com>
cc: Olivier Certner <olce@freebsd.org>,
    Rick Macklem <rick.macklem@gmail.com>,
    FreeBSD Current <freebsd-current@freebsd.org>
Subject: Re: noatime on ufs2
In-reply-to: <CANCZdfosFb1xQdRL9rW1icbVAYbspqnKwWR4CO2guVd5LAv4HA@mail.gmail.com>
References: <ZZqmmM-6f606bLJx@int21h> <a5e38bfbabd37084@orthanc.ca> <CAM5tNy4HuHb=GpQXvE4h2NC8_azOwDS3H7wY3UK+cE07owPr3A@mail.gmail.com> <4014880.cjyAsbXg9l@ravel> <a5e3a25e0d57d1a9@orthanc.ca> <CANCZdfosFb1xQdRL9rW1icbVAYbspqnKwWR4CO2guVd5LAv4HA@mail.gmail.com>
Comments: In-reply-to Warner Losh <imp@bsdimp.com>
   message dated "Sun, 14 Jan 2024 10:58:13 -0700."
List-Id: Discussions about the use of FreeBSD-current <freebsd-current.freebsd.org>
List-Archive: https://lists.freebsd.org/archives/freebsd-current
List-Help: <mailto:freebsd-current+help@freebsd.org>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Subscribe: <mailto:freebsd-current+subscribe@freebsd.org>
List-Unsubscribe: <mailto:freebsd-current+unsubscribe@freebsd.org>
Sender: owner-freebsd-current@freebsd.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <54822.1705255450.1@orthanc.ca>
Date: Sun, 14 Jan 2024 10:04:10 -0800
Message-ID: <a5e3a29d6765ce1c@orthanc.ca>
X-Rspamd-Queue-Id: 4TCjp50Hylz4bQd
X-Spamd-Bar: ----
X-Rspamd-Pre-Result: action=no action;
	module=replies;
	Message is reply to one we originated
X-Spamd-Result: default: False [-4.00 / 15.00];
	REPLY(-4.00)[];
	TAGGED_RCPT(0.00)[];
	ASN(0.00)[asn:25795, ipnet:208.79.88.0/21, country:US]

Warner Losh writes:

> > I'm really interested in hearing from people who actively use
> > atime on a regular basis for non-trivial purposes.  What are
> > the modern use cases for atime?

> The consensus was we'd fix it in the installer.

Sure, but my question still stands.  I'm genuinely curious
to know how (or if) people still use atime.

--lyndon