Re: cdrecord stopped working with 4.2 upgrade

2000-12-07 Thread Vivek Khera
> "WB" == Wilko Bulte <[EMAIL PROTECTED]> writes: >> Here's the device from boot: >> >> cd0 at ahc1 bus 0 target 4 lun 0 WB>^ bus *** 0 *** No, that's ach1 which is scsi bus 1 as per camcontrol: # camcontrol devlist at scbus0 target 0 lun 0 (da0) at scbus0

Re: cdrecord stopped working with 4.2 upgrade

2000-12-07 Thread Wilko Bulte
On Thu, Dec 07, 2000 at 04:29:43PM -0500, Vivek Khera wrote: > > "WB" == Wilko Bulte <[EMAIL PROTECTED]> writes: > > >> Here's the device from boot: > >> > >> cd0 at ahc1 bus 0 target 4 lun 0 > > WB>^ bus *** 0 *** > > No, that's ach1 which is scsi bus 1 as per camcontr

Re: cdrecord stopped working with 4.2 upgrade

2000-12-08 Thread Wilko Bulte
On Fri, Dec 08, 2000 at 11:11:00AM -0500, Vivek Khera wrote: > > "MS" == Mike Smith <[EMAIL PROTECTED]> writes: > > >> Hmmm. Must be a new requirement. I never had that before. I'll give > >> it a try. Thanks for the pointer. > > MS> No excuses. cdrecord has always required the pass dev

Re: cdrecord stopped working with 4.2 upgrade

2000-12-08 Thread Vivek Khera
> "WB" == Wilko Bulte <[EMAIL PROTECTED]> writes: >> Ok... can we have this requirement documented somewhere? Perhaps the >> pkg-descr file for the port? That would have been a timesaver! WB> 'man ktrace' for a way to debug this sort of things. The ktrace output was not so helpful yesterd