From owner-freebsd-current Thu Aug 20 14:45:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA00829 for freebsd-current-outgoing; Thu, 20 Aug 1998 14:45:58 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA00774; Thu, 20 Aug 1998 14:45:42 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from gate.lan.awfulhak.org (brian@localhost [127.0.0.1]) by awfulhak.org (8.8.8/8.8.8) with ESMTP id WAA03519; Thu, 20 Aug 1998 22:44:40 +0100 (BST) (envelope-from brian@gate.lan.awfulhak.org) Message-Id: <199808202144.WAA03519@awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: Peter Dufault cc: bde@FreeBSD.ORG (Bruce Evans), current@FreeBSD.ORG Subject: Re: cvs commit: src/sys/kern subr_xxx.c src/sys/scsi su.c src/sys/sys conf.h In-reply-to: Your message of "Thu, 20 Aug 1998 04:55:21 EDT." <199808200855.EAA11979@hda.hda.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 20 Aug 1998 22:44:39 +0100 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > bde 1998/08/19 23:10:42 PDT > > > > Modified files: > > sys/kern subr_xxx.c > > sys/scsi su.c > > sys/sys conf.h > > Log: > > Moved `nx' functions to the one place where they are used (su.c). > > They shouldn't be used there either. They should have gone away > > about 3 years ago when the statically initialized devswitches went > > away, but su.c unfortunately still frobs the cdevswitch in the old > > way. > > "su" should go away in -current. The reason for it was quick and > dirty fixed SCSI targets before I put in the wire-down code and > the "uk" device. > > Anyone who notices it goes away will have an easy time to change > to a wired down device, and it will serve as a heads up to them > for work they have to do in the CAM cutover. > > Does anyone disagree? Maybe... the ``scsi -p'' command uses ssc(4) which requires su(4). This functionality is vital if you've got (say) an external scsi device that's the only thing on the bus and is normally switched off. Would wiring down the device cover this ? > Peter > > -- > Peter Dufault (dufault@hda.com) Realtime development, Machine control, > HD Associates, Inc. Safety critical systems, Agency approval -- Brian , , Don't _EVER_ lose your sense of humour.... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message