devfs support code(was Re: kernel dev patches)

2000-07-20 Thread bug1
Ben Collins wrote: > > If you are really interesed in writing some code, I'de like to see a > smallish library that interprets things in /dev of a devfs mounted > filesystem. query things like drives, partitions, devices, etc.. Devfs is > definitely going to be the way to go in woody. > > Ben >

Re: kernel dev patches

2000-07-19 Thread Ben Collins
On Wed, Jul 19, 2000 at 04:44:11PM +1000, bug1 wrote: > Daniel Jacobowitz wrote: > > > > On Wed, Jul 19, 2000 at 12:02:30AM -0400, Ben Collins wrote: > > > > The reason for not just using the normal /proc is that it enlarges the > > > > kernel by about 67KB in 2.[34].x which is about 5% of our sp

Re: kernel dev patches

2000-07-18 Thread bug1
Daniel Jacobowitz wrote: > > On Wed, Jul 19, 2000 at 12:02:30AM -0400, Ben Collins wrote: > > > The reason for not just using the normal /proc is that it enlarges the > > > kernel by about 67KB in 2.[34].x which is about 5% of our space on the > > > initial boot floppy. By using a few dev modules

Re: kernel dev patches

2000-07-18 Thread Daniel Jacobowitz
On Wed, Jul 19, 2000 at 12:02:30AM -0400, Ben Collins wrote: > > The reason for not just using the normal /proc is that it enlarges the > > kernel by about 67KB in 2.[34].x which is about 5% of our space on the > > initial boot floppy. By using a few dev modules we could (if we choose) > > avoid h

Re: kernel dev patches

2000-07-18 Thread Ben Collins
> The reason for not just using the normal /proc is that it enlarges the > kernel by about 67KB in 2.[34].x which is about 5% of our space on the > initial boot floppy. By using a few dev modules we could (if we choose) > avoid having to use a kernel with /proc support compiled in. I Don't think