Re: HEADS UP kernel & burncd change..

2001-10-03 Thread Jim Bryant
Kris Kennaway wrote: > On Wed, Oct 03, 2001 at 01:56:11PM -0500, Jim Bryant wrote: > >>This may sounds strange, but as I don't actually recall seeing any actual changes to >burncd unless i missed something in my cvsup >>early this morning CDT... >> >>I just decided to give it another try befor

Re: HEADS UP kernel & burncd change..

2001-10-03 Thread Kris Kennaway
On Wed, Oct 03, 2001 at 01:56:11PM -0500, Jim Bryant wrote: > This may sounds strange, but as I don't actually recall seeing any actual changes to >burncd unless i missed something in my cvsup > early this morning CDT... > > I just decided to give it another try before booting into the kernel b

Re: HEADS UP kernel & burncd change..

2001-10-03 Thread Jim Bryant
This may sounds strange, but as I don't actually recall seeing any actual changes to burncd unless i missed something in my cvsup early this morning CDT... I just decided to give it another try before booting into the kernel built this morning, and it seems that it was a "world" issue, and no

Re: HEADS UP kernel & burncd change..

2001-10-02 Thread Jim Bryant
Heheh... Just to clarify for some... my standard practice involves following buildworld with installworld... Jim Bryant wrote: > Søren Schmidt wrote: > >> Kernel and burncd must be in sync again, a make kernel followed >> by a make world should do it. >> >> -Søren > > > > acd0: CD-RW at

Re: HEADS UP kernel & burncd change..

2001-10-02 Thread Jim Bryant
Søren Schmidt wrote: > Kernel and burncd must be in sync again, a make kernel followed > by a make world should do it. > > -Søren acd0: CD-RW at ata1-master PIO4 This is from -current as of about 1am or so CDT today. I did a make buildworld instead of a make world, but I would assume that

HEADS UP kernel & burncd change..

2001-10-01 Thread Søren Schmidt
Kernel and burncd must be in sync again, a make kernel followed by a make world should do it. -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message