Re: DISCUSSION: /dev/fd%d.%d and /dev/{a}cd%d[ac] to be discontinued ?

2003-10-20 Thread Poul-Henning Kamp
In message <[EMAIL PROTECTED]>, Andrew Gallatin writes: > >Poul-Henning Kamp writes: > > > > As soon as these uses of cloning code has been removed, I will move > > the floppy and CD drivers under GEOM, paving the way for the > > significant changes to the buf/VM system which some of you have > >

Re: DISCUSSION: /dev/fd%d.%d and /dev/{a}cd%d[ac] to be discontinued ?

2003-10-19 Thread Andrew Gallatin
Poul-Henning Kamp writes: > > As soon as these uses of cloning code has been removed, I will move > the floppy and CD drivers under GEOM, paving the way for the > significant changes to the buf/VM system which some of you have > already heard rumours about. (more will emerge after BSDcon'03

Re: DISCUSSION: /dev/fd%d.%d and /dev/{a}cd%d[ac] to be discontinued ?

2003-09-04 Thread Poul-Henning Kamp
In message <[EMAIL PROTECTED]>, Andrew Gallatin writes: >Can you give a hint as to what you mean by the significant buf/VM >system changes? Are you talking about removing the vnode detour for >drivers and giving drivers who want it access to the struct file? Well, there really isn't more than t

DISCUSSION: /dev/fd%d.%d and /dev/{a}cd%d[ac] to be discontinued ?

2003-09-04 Thread Poul-Henning Kamp
I am committing a BURN_BRIDGES patch which puts the density select devices of the floppy driver and the 'a' and 'c' compat partitions of the CD drivers on the chopping block for 6-current. There is no loss of functionality from this, the fdcontrol(8) utility allows even greater flexibility than t