Greg 'groggy' Lehey said:
> The current status of Vinum in -CURRENT is that it is being
> rewritten. The introduction of the GEOM layer has badly broken Vinum,
> and it has been decided better to rewrite it than to fix it. It'll be
> a while before it's smooth again.
This would be a good note to
On Thursday, 8 July 2004 at 2:21:30 -0500, Mario Doria wrote:
> Hi,
>
> Another vinum question. I have a machine running 5-CURRENT sources from
> yesterday (yes I know the dangers of running CURRENT and I did read the
> mailing list archives).
Well, the issue was discussed there.
> I think I f
Hi again,
Sorry for replying to my own post, I wanted to add some more details.
Here's a more detailed message about the panic on boot:
Mounting root from ufs:/dev/ad0s1a
Pre-seeding PRNG: kickstart.
Loading configuration files.
Entropy harvesting: interrupts ethernet point_to_point kickstart.
Hi,
Another vinum question. I have a machine running 5-CURRENT sources from
yesterday (yes I know the dangers of running CURRENT and I did read the
mailing list archives). I think I found a bug, if I add
start_vinum="YES" to /etc/rc.conf, at boot I get a panic with a message
saying:
panic: v
