Re: Hardwiring SCSI device ID broken?

2000-02-13 Thread Igor Timkin
Sorry for delay, it's production server (newsfeed.gamma.ru is #3 on Freenix). 4.0-2208-CURRENT fix this problem, thank you. > Igor Timkin wrote: > > > Martin Cracauer wrote: > > > > It seem hardwiring SCSI devices is broken in -current: > > > > > > > > LINT seems to recommend: > > > > > > >

Re: Hardwiring SCSI device ID broken?

2000-02-11 Thread Kun Limfjordsporter
On Tue, 2355 September 1993, Matthew Sean Thyer wrote: > When "device scbus0" changed to "device scbus" in LINT and I applied > that to my config file I found I could no longer wire down my disks > to scbus0 unless I changed the base SCSI code line back to "device > scbus0". > > This is what I h

Re: Hardwiring SCSI device ID broken?

2000-02-08 Thread Matthew Sean Thyer
Barry, I think I know the problem you have. When "device scbus0" changed to "device scbus" in LINT and I applied that to my config file I found I could no longer wire down my disks to scbus0 unless I changed the base SCSI code line back to "device scbus0". This is what I have: device

Re: Hardwiring SCSI device ID broken?

2000-02-07 Thread tele danmarQ kvindeservice
On Mon, 7 Feb 1900, Noted Usenet Pedophile Barry Bouwsma wrote: > More about this later. Here's more now: Here is FreeBSD-*STABLE* as it properly wires the devices to where I want them to be (highlighted by ^) The kernel configuration looks like this (meat stripped away) machine

Re: Hardwiring SCSI device ID broken?

2000-02-07 Thread Barry Bouwsma
On Tue, Feb 08, 2000 at 03:36:43AM +0800, Peter Wemm wrote: > > > > Hope this is enough to help, if not, I'll provide more. The two- > > line errors that repeat for the second and each following drive > > present seem interesting... > > I'm sorry, I'm still not following this, there's far too m

Re: Hardwiring SCSI device ID broken?

2000-02-07 Thread Peter Wemm
Barry Bouwsma wrote: > > > > > > > > It seem hardwiring SCSI devices is broken in -current: > > > > > dmesg would be useful, otherwise we can't even begin to guess what ha ppened. > > > > > > > I don't have it in /var/log/messages, but I can reboot my machine > > > (that has this problem) and

Re: Hardwiring SCSI device ID broken?

2000-02-07 Thread Barry Bouwsma
> > > > > > > It seem hardwiring SCSI devices is broken in -current: > > > > dmesg would be useful, otherwise we can't even begin to guess what happened. > > > > > I don't have it in /var/log/messages, but I can reboot my machine > > (that has this problem) and copy down what I see. Okay, this m

Re: Hardwiring SCSI device ID broken?

2000-02-07 Thread Barry Bouwsma
On Mon, Feb 07, 2000 at 04:40:21PM +0100, Martin Cracauer wrote: > > > > I don't have it in /var/log/messages, but I can reboot my machine > > (that has this problem) and copy down what I see. > > If it has been thrown out by newer kernel messages, try > /var/run/dmesg.boot That wouldn't even b

Re: Hardwiring SCSI device ID broken?

2000-02-07 Thread Martin Cracauer
In <[EMAIL PROTECTED]>, tele danmarQ kvindeservice wrote: > On Mon, 7 Feb 19100, Martin Cracauer wrote: > > > > > > > It seem hardwiring SCSI devices is broken in -current: > > > dmesg would be useful, otherwise we can't even begin to guess what happened. > > > > I can't provide it now. > > I

Re: Hardwiring SCSI device ID broken?

2000-02-07 Thread tele danmarQ kvindeservice
On Mon, 7 Feb 19100, Martin Cracauer wrote: > > > > > It seem hardwiring SCSI devices is broken in -current: > > dmesg would be useful, otherwise we can't even begin to guess what happened. > > I can't provide it now. I don't have it in /var/log/messages, but I can reboot my machine (that has t

Re: Hardwiring SCSI device ID broken?

2000-02-07 Thread Martin Cracauer
In <[EMAIL PROTECTED]>, Peter Wemm wrote: > Igor Timkin wrote: > > > Martin Cracauer wrote: > > > > It seem hardwiring SCSI devices is broken in -current: > > dmesg would be useful, otherwise we can't even begin to guess what happened. I can't provide it now. The machine is in production use th

Re: Hardwiring SCSI device ID broken?

2000-02-07 Thread Peter Wemm
Igor Timkin wrote: > > Martin Cracauer wrote: > > > It seem hardwiring SCSI devices is broken in -current: > > > > > > LINT seems to recommend: > > > > > > device ahc > > > device scbus0 at ahc0 > > > device scbus1 at ahc1 bus 0 > > > > > > de

Re: Hardwiring SCSI device ID broken?

2000-02-06 Thread Igor Timkin
> Martin Cracauer wrote: > > It seem hardwiring SCSI devices is broken in -current: > > > > LINT seems to recommend: > > > > device ahc > > device scbus0 at ahc0 > > device scbus1 at ahc1 bus 0 > > > > device sa0 at scbus1 tar

Re: Hardwiring SCSI device ID broken?

2000-02-02 Thread Peter Wemm
Martin Cracauer wrote: > It seem hardwiring SCSI devices is broken in -current: > > LINT seems to recommend: > > device ahc > device scbus0 at ahc0 > device scbus1 at ahc1 bus 0 > > device sa0 at scbus1 target 4 > device

Hardwiring SCSI device ID broken?

2000-02-02 Thread Martin Cracauer
It seem hardwiring SCSI devices is broken in -current: LINT seems to recommend: device ahc device scbus0 at ahc0 device scbus1 at ahc1 bus 0 device sa0 at scbus1 target 4 device sa1 at scbus1 target 5 device