From owner-freebsd-hackers Thu Jun 8 23:01:45 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id XAA15078 for hackers-outgoing; Thu, 8 Jun 1995 23:01:45 -0700 Received: from leo.ibms.sinica.edu.tw ([140.109.40.249]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id XAA15049 for ; Thu, 8 Jun 1995 23:01:07 -0700 Received: (from taob@localhost) by leo.ibms.sinica.edu.tw (8.6.11/8.6.9) id OAA00274; Fri, 9 Jun 1995 14:00:29 +0800 Date: Fri, 9 Jun 1995 14:00:28 +0800 (CST) From: Brian Tao To: FREEBSD-HACKERS-L Subject: MAKEDEV sd* deletes partition devices Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: hackers-owner@freebsd.org Precedence: bulk I think there is some broken (or at least non-intuitive) behaviour in the way MAKEDEV handles disk slices. Recall that my 2.0.5A installation had incorrect minor numbers for the /dev/sd*.ctl devices. Today I brought the system down to single user for some unrelated maintenance, and decided to fix up the /dev directory. I ran "MAKEDEV sd0" and noted that /dev/rsd0.ctl now had the correct minor number. The next thing I did was umount the /usr and /tmp filesystems for a quick fsck (this was after the "biodone" panic I mention in a separate message). fsck complained that it could not stat /dev/sd0s1e nor /dev/sd0s1f, and that /dev/rsd0s1e and /dev/rsd0s1f were not character devices. I looked in /dev and found sd0s1* and rsd0s1* had all been deleted. It appears that a "MAKEDEV sd0" deletes the partitions, but then forgets to put them back. You need to do a separate "MAKEDEV sd0s1*" (* = [a-h]). "MAKEDEV sds1" only makes /dev/sd0s1. I would rather have the "sds1" target make the slice and partition devices, and if the "sd0" target deletes something, it should put them back. You're supposed to end up with *more* devices after running MAKEDEV, not less. ;-) -- Brian ("Though this be madness, yet there is method in't") Tao taob@gate.sinica.edu.tw <-- work ........ play --> taob@io.org