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
>
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
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
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
> 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
Hi, ive been playing around with kernel modules, and i intend to make
/proc/filesystems, /proc/partitions available as devices in the same way
as busybox's devmtab, devps and devmodules.
My reasons for this are that when debian installer starts one of its
first priorities may be to find space tha
6 matches
Mail list logo
