Re: Can't seem to build a release.

Quoting Grover Lines <grover_at_ceribus.net>:

>> Edwin Culp wrote:
>>> For a while now, my releases haven't finished.  After the error md0
>>> exists as does mdctl.  I have no idea what is causing the error.  Any
>>> help would be appreciated.
>>>
>>> + [ x != x ]
>>> + mdconfig -a -t vnode -f /R/stage/mfsroot/mfsroot MDDEVICE=md0 [ !
>>> + -c /dev/md0 ] echo No /dev/md0
>>> No /dev/md0
>>> + exit 1
>>> *** Error code 1
>>>
>>> Stop in /usr/src/release.
>>> + umount /dev
>>> *** Error code 1
>>>
>>> Stop in /usr/src/release.
>>>
>>
>> I found a workaround in PR misc/68528 (beware of cutandpaste):
>>
>> --- src/release/scripts/doFS.sh.orig        Thu Jul  1 03:47:59 2004
>> +++ src/release/scripts/doFS.sh     Thu Jul  1 03:48:21 2004
>> _at__at_ -64,6 +64,7 _at__at_
>>          fi
>>
>>          MDDEVICE=`mdconfig -a -t vnode -f ${FSIMG}`
>> +       sleep 1
>>          if [ ! -c /dev/${MDDEVICE} ] ; then
>>                  echo "No /dev/$MDDEVICE" 1>&2
>>                  exit 1
>>
>> works for me.
>>
>>> TIA,
>>>
>>> ed
>>
>> Claude Buisson
>> _______________________________________________
>
> Sorry about that last mail it was sent prematurely.
>
>
> I know this probably isn't the correct way to do this but it worked for me
> also without patching or having to rebuild the whole release.
>
>
> mdconfig -a -t swap -s 4m
> mdconfig -a -t swap -s 4m
> mdconfig -a -t swap -s 4m
> mdconfig -a -t swap -s 4m
> mdconfig -a -t swap -s 4m
>
> to make the md0-4 in /dev
>
> then chroot to your build dir
>
> chroot /home2/build/work/5-current-chrootdir /mk cdrom.1
> chroot /home2/build/work/5-current-chrootdir /mk iso.1

Testing now, thanks.  I had already ereased my previous build.

ed