From owner-freebsd-hackers Thu Mar 27 17:41:55 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id RAA10897 for hackers-outgoing; Thu, 27 Mar 1997 17:41:55 -0800 (PST) Received: from boulder.syr.servtech.com (boulder.syr.servtech.com [206.106.144.94]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA10872; Thu, 27 Mar 1997 17:41:25 -0800 (PST) Received: from boulder.syr.servtech.com (boulder.syr.servtech.com [206.106.144.94]) by boulder.syr.servtech.com (8.8.4/8.8.4) with SMTP id UAA04671; Thu, 27 Mar 1997 20:47:38 -0500 (EST) Message-ID: <333B2338.41C67EA6@servtech.com> Date: Thu, 27 Mar 1997 20:47:36 -0500 From: Shawn Carey X-Mailer: Mozilla 3.0 (X11; I; FreeBSD 2.2-BETA_A i386) MIME-Version: 1.0 To: stesin@gu.net CC: msmith@atrad.adelaide.edu.au, dyson@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: Anyone else seen this? References: <199703270128.LAA04400@genesis.atrad.adelaide.edu.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 26 Mar 1997 13:28:28 Andrew Stesin said: > > Just curious, what will happen in case the program file affected > by this bug will occasionally reside on a R/O-mounted FS? > > If the kernel will eat this difference quietly, without > any strange side effects, crashes, messages or so -- I'd probably > wonder... > Yes, it will. I tried this today, and even GDB was happy. As soon as I remounted the filesystem R/W the problem reappeared... So, it seems to me we have two interesting data points regarding this: 1) Statically linked binaries are not affected by this phenomenon. 2) Binaries residing on R/O filesystems are not affected either. Does anyone know anything else? -Shawn