From owner-freebsd-hackers Thu Jan 9 13:53:30 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id NAA23622 for hackers-outgoing; Thu, 9 Jan 1997 13:53:30 -0800 (PST) Received: from thelab.hub.org (hal-ns1-28.netcom.ca [207.181.94.92]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id NAA23599 for ; Thu, 9 Jan 1997 13:53:26 -0800 (PST) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.8.4/8.8.2) with SMTP id RAA09330 for ; Thu, 9 Jan 1997 17:53:23 -0400 (AST) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Thu, 9 Jan 1997 17:53:22 -0400 (AST) From: The Hermit Hacker To: hackers@freebsd.org Subject: mount w/ noatime option Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi... With all the talk about the noatime option, I figured I'd see what happens if I used mount from -current (3.0) on my 2.2 machine, since /usr/include/sys/mount.h defines MNT_NOATIME... It worked, but I'm wondering if this is "A Bad Thing"...like, I know that if I were to try to move some binaries from 3.0 to 2.2, I'd be asking for problems, due to struct incompatibilities (w comes to mind)...am I risking the same thing with mount, or should I be safe? Thanks...