Subject: R: cgdconfig: can't open cgd "cgd0", after update
To: None <current-users@NetBSD.org>
From: Alessandro Manunza <email@example.com>
Date: 05/31/2005 14:41:36
I'm felling so silly.......
> I guess that the update replaced your custom kernel with a GENERIC =
> which doesn't include the cgd(4) driver.
Yes, it is!
I don't know way, but after build.sh distribution, I build.sh
kernel=3DMYKENEL, but it doesn't build MYKERNEL, it rebuild a GENERIC!! =
make clean && make cleandir && rm -rf compile/MYKERNEL and than, after a =
build.sh, it build.sh me a correct MYKENEL that works fine!!
So thanks for suggestion, it solve may problem.
But, first of all, sorry for the question; next time I should be more
careful with these stupid errors!!
Da: current-users-owner@NetBSD.org =
Per conto di Mike M. Volokhov
Inviato: marted=EC 31 maggio 2005 8.23
A: Matthias Scheler
Oggetto: Re: cgdconfig: can't open cgd "cgd0", after update
On Mon, 30 May 2005 17:23:21 +0000 (UTC)
firstname.lastname@example.org (Matthias Scheler) wrote:
> In article <20050530160303.46A4E3A519@mail.netbsd.org>,
> "Alessandro Manunza" <email@example.com> writes:
> > I get a more verbose error:
> > # cgdconfig -vvv -V ffs cgd0 /dev/wd0e
> > opendisk_werror(cgd0, , 1024) called.
> > cgdconfig: can't open cgd "cgd0", "/dev/rcgd0d"
> > don't know how to solve this problem.
Yes, seems it is.
Could we provide an LKM for cgd? I've wrote my own, but unfortunately
erased it while migrating to my own CVS mirror.