Subject: Re: Vinum in NetBSD: status and questions
To: Greg 'groggy' Lehey <email@example.com>
From: Jaromir Dolecek <firstname.lastname@example.org>
Date: 04/08/2003 11:13:23
Greg 'groggy' Lehey wrote:
-- Start of PGP signed section.
> I'm currently testing the Vinum/NetBSD code that the Infosys people
> sent me. It's still a bit rough round the edges, but I have got to
> the stage where I can build a kernel with Vinum "support" and talk to
> the driver. I currently have a few questions:
> 1. vinum(8) has a command-line mode and uses readline for command
> line editing and history. I can find the headers for readline,
> but I can't find a library. What's the policy? Is readline
> deprecated? I've found editline, but the interface is quite
> different, and I'd prefer to keep things the same.
editline has readline compatibility layer. You use <readline.h>
and link against editline. Should be fine for simple readline stuff -
if not, I can work with you on extending editline readline layer.
> 2. I see that direct access to bdevsw is no longer used. Instead,
> there's the bdevsw_lookup() function. In the case of Vinum,
> bdevsw accesses are either to Vinum itself, or to one of the
> drives. Can I assume that the drive will not lose its bdevsw? Or
> should I call bdevsw_lookup() for every I/O?
Every driver defines it's own bdevsw, which is added to system lists
So no, you can't 'lose' your bdevsw.
Jaromir Dolecek <jdolecek@NetBSD.org> http://www.NetBSD.org/
-=- We should be mindful of the potential goal, but as the tantric -=-
-=- Buddhist masters say, ``You may notice during meditation that you -=-
-=- sometimes levitate or glow. Do not let this distract you.'' -=-