Re: ados fs and vnd

[Michael van Elst <mlelstv%serpens.de@localhost>]

On Sun, Sep 06, 2009 at 01:47:51AM +0200, Frank Wille wrote:
> On Sun, 6 Sep 2009 00:08:07 +0200
> Michael van Elst <mlelstv%serpens.de@localhost> wrote:
> 
> > On Sat, Sep 05, 2009 at 09:44:04PM +0200, Frank Wille wrote:
> > > On Sat, 5 Sep 2009 12:12:14 +0200
> > > Michael van Elst <mlelstv%serpens.de@localhost> wrote:
> > >
> > > > The only API for disktab(5) is getdiskbyname() which returns
> > > > a prototype disk label. It should be trivial to teach it
> > > > more fields.
> > > 
> > > Hm... this will change a libc function. Do you think I might introduce a
> > > new identifier there, as for example ca..ch to define the p_cpg field?
> > 
> > That's probably the best solution. disktab(4) and getdiskbyname()
> > seem to be rather non-portable interfaces and adding identifiers
> > to disktab for missing members of a disklabel are harmless.
> 
> Ok. So far no problem with getdiskbyname().
> 
> But when I looked into vnconfig.c again, I realized that it will only
> pass general disk-geometry data to the vnd driver, but no partition data.
> p_fsize and p_cpg do exist per partition.
> 
> Or do we assume that a default label for vnd has always one partition,
> and we take p_fsize and p_cpg from partition 'a' (i.e. "fa" and "ca"
> from disktab(5))?

The vnd default label currently has only one partition, I don't think
that you have to provide more.


-- 
                                Michael van Elst
Internet: mlelstv%serpens.de@localhost
                                "A potential Snark may lurk in every tree."