Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 14 Sep 1998 01:28:12 -0700 (PDT)
From:      Julian Elischer <julian@whistle.com>
To:        S?ren Schmidt <sos@FreeBSD.ORG>
Cc:        cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG
Subject:   Re: cvs commit: src/sys/dev/vn vn.c
Message-ID:  <Pine.BSF.3.95.980914011838.1526A-100000@current1.whistle.com>
In-Reply-To: <199809121846.LAA13394@freefall.freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help
Actually it was not 'Missed'
the theory was that the single disk abstraction
that SLICE attempts to supply would also apply to vn devices.
I really don't think that devfs is fully feasible without something like
SLICE. I had to write SLICE because all my atempts to come up with 
a way of making a functional devfs based system without such an
abstraction failed in one way or another.

I'm basically too exhausted from work and REAL LIFE(TM) to think
my way out through the last 10%. Abstracting out all the disk devices to a
single interface is  what SLICE tries to do.  That way every new Randm
access device automatically can slice&dice without any extra support.
I just can't finish it in this state of mind.
it needs

1/ extended slice support
2/ a way of doing the initialisation of slices
3/ useful handlers (e.g. a ccd variant)

I'm basically in need of help. The aim was to make the whole system
dynamic, but I seem to have lost the plot somewhere.


On Sat, 12 Sep 1998, S?ren Schmidt wrote:

> sos         1998/09/12 11:46:06 PDT
> 
>   Modified files:
>     sys/dev/vn           vn.c 
>   Log:
>   Enable the vn device under DEVFS without SLICE.
>   
>   This was apparently missed when all the #ifdef SLICE gunk was put in.
>   
>   Revision  Changes    Path
>   1.70      +33 -4     src/sys/dev/vn/vn.c
> 




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.95.980914011838.1526A-100000>