From owner-freebsd-hackers Fri Jan 27 15:28:18 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id PAA00823 for hackers-outgoing; Fri, 27 Jan 1995 15:28:18 -0800 Received: from hda.com (hda.com [199.232.40.182]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id PAA00781; Fri, 27 Jan 1995 15:27:21 -0800 Received: (dufault@localhost) by hda.com (8.6.9/8.3) id SAA09764; Fri, 27 Jan 1995 18:27:06 -0500 From: Peter Dufault Message-Id: <199501272327.SAA09764@hda.com> Subject: Re: SCSI device configuring.. (was scsi renames devices) To: julian@tfs.com (Julian Elischer) Date: Fri, 27 Jan 1995 18:27:05 -0500 (EST) Cc: hsu@fx7.cs.hut.fi, freebsd-hackers@freefall.cdrom.com, freebsd-scsi@freefall.cdrom.com In-Reply-To: from "Julian Elischer" at Jan 27, 95 12:08:58 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 1093 Sender: hackers-owner@FreeBSD.org Precedence: bulk Julian Elischer writes: (Interesting stuff that I'll comment on later, but this I have to comment on right away...) > > However, we have to consider the problem of booting an old kernel e > and having the same problem Heikki mentions, namely, the new sd0 > > is scsi id3 or something and we mount on top of it and trash the > > disk. > how many really old kernels do people run? particularly after > a revision upgrade? I don't think we can make changes that will damage a file system if someone boots an older kernel of the same major rev. (I can see the 2.1 post now: "I had a copy of 2.0R on floppy, so I booted that and...") Although I also suppose that there are sanity checks that prevent a UFS file system from being mounted as swap, right? Am I right that most scenarios where a file system is trashed are bugs that we can address? Peter -- Peter Dufault Real Time Machine Control and Simulation HD Associates, Inc. Voice: 508 433 6936 dufault@hda.com Fax: 508 433 5267 -- Formerly hd@world.std.com. E-mail problems? Tell hdslip@iii.net