Date: Fri, 18 Oct 1996 08:04:02 -0500 (CDT) From: Joe Greco <jgreco@brasil.moneng.mei.com> To: bsdisp@shadows.aeon.net (mika ruohotie) Cc: michaelv@MindBender.serv.net, jgreco@brasil.moneng.mei.com, msv@arisia.net, freebsd-isp@FreeBSD.org Subject: Re: **ccd, disk striping, and fsck problems** Message-ID: <199610181304.IAA02676@brasil.moneng.mei.com> In-Reply-To: <199610180956.LAA19211@shadows.aeon.net> from "mika ruohotie" at Oct 18, 96 11:56:33 am
next in thread | previous in thread | raw e-mail | index | archive | help
> > Even more simply... If you're bringing it up in single user mode,
> > don't forget to do "ccdconfig -C" before you do your fsck's by hand.
> >
> > You didn't specify if this is what you were doing, but I forget to do
> > that every now and then. Fsck bombs. I grumble; type ccdconfig -C.
> > Fsck works...
>
> hmm?
>
> but but... i did put the said ccdconfig -Cv (i think i had v too) just
> above the fsck -p in the /etc/rc and it doesnt cause me any? problems
> anymore...
>
> is that not the right way?
This should only be a problem in single user mode. Your /etc/rc
should already have
HOME=/; export HOME
PATH=/sbin:/bin:/usr/sbin:/usr/bin
export PATH
# Configure ccd devices.
if [ -f /etc/ccd.conf ]
then
ccdconfig -C
fi
swapon -a
if [ $1x = autobootx ]
in it. (2.1.5R and later ship with this).
... JG
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199610181304.IAA02676>
