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 this week (which I didn't expect when I posted the question). Sorry Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer <[EMAIL PROTECTED]> http://www.cons.org/cracauer/ Tel.: (private) +4940 5221829 Fax.: (private) +4940 5228536 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
- Hardwiring SCSI device ID broken? Martin Cracauer
- Re: Hardwiring SCSI device ID broken? Peter Wemm
- Re: Hardwiring SCSI device ID broken? Igor Timkin
- Re: Hardwiring SCSI device ID brok... Peter Wemm
- Re: Hardwiring SCSI device ID ... Martin Cracauer
- Re: Hardwiring SCSI device ID ... Igor Timkin
- Re: Hardwiring SCSI device ID broken? tele danmarQ kvindeservice
- Re: Hardwiring SCSI device ID broken? Martin Cracauer
- Re: Hardwiring SCSI device ID brok... Barry Bouwsma
- Re: Hardwiring SCSI device ID brok... Barry Bouwsma
- Re: Hardwiring SCSI device ID ... Peter Wemm
- Re: Hardwiring SCSI devic... Barry Bouwsma
- Re: Hardwiring SCSI device ID broken? tele danmarQ kvindeservice
- Re: Hardwiring SCSI device ID broken? Matthew Sean Thyer
- Re: Hardwiring SCSI device ID broken? Kun Limfjordsporter