This message generated a parse failure. Raw output follows here. Please use 'back' to navigate. From devnull@lkml.org Tue Apr 23 12:40:29 2024 Received: from entropy.muc.muohio.edu (IDENT:root@entropy.muc.muohio.edu [134.53.213.10]) by herbie.ucs.indiana.edu (8.9.3/8.9.3) with ESMTP id TAA20278 for ; Mon, 5 Jul 1999 19:40:57 -0500 (EST) Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by entropy.muc.muohio.edu (8.8.7/8.8.7) with ESMTP id UAA27440; Mon, 5 Jul 1999 20:22:54 -0400 Received: by vger.rutgers.edu via listexpand id ; Mon, 5 Jul 1999 17:20:29 -0400 Received: by vger.rutgers.edu id ; Mon, 5 Jul 1999 17:20:12 -0400 Received: from flits102-126.flits.rug.nl ([129.125.102.126]:12319 "EHLO flits102-126.flits.rug.nl") by vger.rutgers.edu with ESMTP id ; Mon, 5 Jul 1999 17:20:02 -0400 Received: from flits102-126.flits.rug.nl (root@port222.dialin.keyaccess.nl [193.172.212.222]) by flits102-126.flits.rug.nl (8.8.3/8.8.3) with ESMTP id XAA20257 for ; Mon, 5 Jul 1999 23:20:33 +0200 Message-Id: <378120A5.84F7BFBC@flits102-126.flits.rug.nl> Date: Mon, 05 Jul 1999 23:16:22 +0200 From: Rolf Fokkens X-Mailer: Mozilla 4.51 [en] (X11; I; Linux 2.2.10so i686) X-Accept-Language: en Mime-Version: 1.0 To: linux-kernel@vger.rutgers.edu Subject: small scsi_scanorder patch Content-Type: text/plain; charset=iso-8859-1 Sender: owner-linux-kernel@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu X-Orcpt: rfc822;linux-kernel-outgoing-dig Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by herbie.ucs.indiana.edu id TAA20278 The kernel assigns minor SCSI device numbers dynamically. This is done by assigning them only to actually connected devices in order of their SCSI-id's (mostly ascending). This means that connecting an external SCSI device changes the minors of all internal devices with a higher SCSI-id forcing me to change /etc/fstab when connecting the external device and to change it back when disconnecting the device. I created a small scsiorder patch to solve this by fixing the problem where it originates. For example the kernel parameter "scsi_scanorder=1,10,6" means to scan the devices in the following order: 1,10,6,0,2,3,4,5,7,8,9,11,12,13,15. Which means SCSI-id's 1,10,6 and 0 will allways be mapped on sda, sdb, sdc en sdd (if all connected). More info: http://flits102-126.flits.rug.nl/~rolf/scanorder/index.html There's a small description of the alternatives like devfs and scsidev as well. cheers! Rolf. :.˛mkabzwmb˛mbz_^nrzh&zvy杶ii