Date: Fri, 20 May 2005 13:03:20 -0500 From: William Richter <wrichter@texaslife.com> To: Kris Kennaway <kris@obsecurity.org> Cc: freebsd-questions@freebsd.org Subject: Re: mdconfig problem on make release of 5_4_0_RELEASE Message-ID: <20050520130320.1c43a2ac.wrichter@texaslife.com> In-Reply-To: <20050520164922.GA20460@xor.obsecurity.org> References: <20050520064944.79881857.wrichter@texaslife.com> <20050520164922.GA20460@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
well, it's the kernel that's on disc1 of the 5.4 release iso's. mdconfig works. it just doesn't work when chroot'ed into the build directory. i've just discovered that the /sbin/mdconfig that comes with the distribution works when copied into the release tree (i also had to copy libc.so.5 in the release directory's /lib). but then i was able to complete building the release. i've been building my own releases since 5.2 and never had this issue.
On Fri, 20 May 2005 09:49:22 -0700
Kris Kennaway <kris@obsecurity.org> wrote:
> On Fri, May 20, 2005 at 06:49:44AM -0500, William Richter wrote:
> > i'm attempting to make a release and the build of the mfs image is failing (see below).
> >
> > it's mdconfig that's failing:
> >
> > + mdconfig -a -t vnode -f /R/stage/mfsroot/mfsroot
> > mdconfig: ioctl(/dev/mdctl): Inappropriate ioctl for device
>
> Do you have md support in your kernel?
>
> Kris
>
--
Any opinions as lame as the ones expressed above could only belong to me,
and are not those of Texas Life Insurance Company.
The very powerful and the very stupid have one thing in common.
Instead of altering their views to fit the facts, they alter the facts
to fit their views ... which can be very uncomfortable if you happen to
be one of the facts that needs altering.
-- Doctor Who, "Face of Evil"
Those who do not understand Unix are condemned to reinvent it, poorly.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050520130320.1c43a2ac.wrichter>