Re: recurring installworld problem

That's exactly opposite of what UPDATING states.  I don't intend to nit pick 
the point, but I'm about to dig back into this tonight and I'm curious as to 
which order to run things in.

According the the note in UPDATING, you should build world, build and install 
kernel, reboot, then lastly install world.  It seems that is exactly what the 
original poster did.  You're suggesting to install world before the kernel.  
I'm suggesting that I'm very confused.

Lanny Baron wrote:
> Hey,
> 1) cvsup
> 2) make buildworld
> 3) make installworld
> 4) make kernel KERNCONF=KERNNAME
> 
> or
> cd /sys/i386/conf; config KERNNAME
> cd ../compile/KERNNAME
> make depend && make && make install && shutdown -r now
> 
> POOF! Your done :)
> 
> Hope that helps.
> 
> Lanny
> 
> On Mon, 2003-11-17 at 18:25, freebsd_at_msquaredweb.net wrote:
>> Hey all...
>> 
>> Been trying to get 5.1-CURRENT installed since thursday.
>> 
>> This is my procedure:
>> 
>> cvsup
>> make buildworld
>> make buildkernel
>> make installkernel
>> -- reboot --
>> make installworld
>> 
>> This is the error I've been getting (probably 25x since thursday... yes..
>> 25 fresh installs since then)
>> 
>> ===> bin/rcp
>>  install -s -o root -g wheel -m 4555  -fschg rcp /bin
>>  install -o root -g wheel -m 444 rcp.1.gz  /usr/share/man/man1
>>  ===> bin/csh
>>  install -s -o root -g wheel -m 555   csh /bin
>>  install -o root -g wheel  -m 444
>> /usr/src/bin/csh/../../contrib/tcsh/complete.tcsh
>> /usr/src/bin/csh/../../contrib/tcsh/csh-mode.el /usr/share/examples/tcsh
>>  gencat -new et_EE.ISO8859-15.cat et_EE.ISO8859-15.msg
>>  gencat:No such file or directory
>>  *** Error code 1
>> 
>>  Stop in /usr/src/bin/csh.
>>  *** Error code 1
>> 
>>  Stop in /usr/src/bin.
>>  *** Error code 1
>> 
>>  Stop in /usr/src.
>>  *** Error code 1
>> 
>>  Stop in /usr/src.
>>  *** Error code 1
>> 
>>  Stop in /usr/src.
>>  *** Error code 1
>> 
>>  Stop in /usr/src.
>> 
>> Yes, I must use -CURRENT because that apparently is the only way for me
>> to use the multi-ip jail patch. However, these errors occur without the
>> patch. Once I successfully bring the box to 5.1-CURRENT, then I'll try
>> the patch. My goal now is to just get -CURRENT up and running.
>> 
>> Any ideas?
>> 
>> _______________________________________________
>> freebsd-current_at_freebsd.org mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-current
>> To unsubscribe, send any mail to
>> "freebsd-current-unsubscribe_at_freebsd.org"

-- 
"In theory, there is no difference between theory and practice.
In practice, there is."
- Yogi Berra