Pessoal: Fiz um CVSUP e como a TAG estava incorreta o sistema trouxe o 5_2. Fiz o buildworld, buildkernel, installkernel, shutdown now,mount -t ufs -a, cd /usr/src e no make installworld deu erro. Por sorte, rebootou mas meu NAT nao funcionou mais. Refiz a TAG para 5_1, exclui todo /usr/src e fiz o CVSUP novamente com as diretivas abaixo. So que, ao dar o make buildworld com a 5_1, ocorre o seguinte erro:
#make buildworld Running test variables PASS: Test variables detected no regression, output matches. Running test targets PASS: Test targets detected no regression. Running test sysvmatch PASS: Test sysvmatch detected no regression. Running test lhs_expn PASS: Test lhs_expn detected no regression. Running test notdef PASS: Test notdef detected no regression. Running test modifiers PASS: Test modifiers detected no regression. Running test funny_targets PASS: Test funny_targets detected no regression.
--------------------------------------------------------------Rebuilding the temporary build tree-------------------------------------------------------------- rm -rf /usr/obj/usr/src/i386 bla bla bla... --------------------------------------------------------------stage 1: legacy release compatibility shims-------------------------------------------------------------- cd /usr/src; MAKEOBJDIRPREFIX=/usr/obj/usr/src/i386 DESTDIR= INSTALL="sh /usr/src/tools/install.sh" PATH=/usr/obj/usr/src/i386/legacy/usr/sbin:/usr/obj/usr/src/i386/legacy/usr/ bin:/usr/obj/usr/src/i386/legacy/usr/games:/sbin:/bin:/usr/sbin:/usr/bin WORLDTMP=/usr/obj/usr/src/i386 MAKEFLAGS="-m /usr/src/tools/build/mk -m /usr/src/share/mk" /usr/obj/usr/src/make.i386/make -f Makefile.inc1 BOOTSTRAPPING=502100 -DNOHTML -DNOINFO -DNOLINT -DNOMAN -DNOPIC -DNOPROFILE -DNOSHARED -DNO_CPU_CFLAGS -DNO_WARNS legacy ===> tools/build /usr/obj/usr/src/i386/usr/src/tools/build created for /usr/src/tools/build cd /usr/src/tools/build; /usr/obj/usr/src/make.i386/make buildincludes; /usr/obj/usr/src/make.i386/make installincludes rm -f .depend mkdep -f .depend -a -I/usr/obj/usr/src/i386/legacy/usr/include /usr/src/tools/build/dummy.c cc -O -pipe -I/usr/obj/usr/src/i386/legacy/usr/include -c /usr/src/tools/build/dummy.c -o dummy.o building static egacy library ranlib libegacy.a sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 libegacy.a /usr/obj/usr/src/i386/legacy/usr/lib *** Signal 11
Arquivo do CVSUP #-----------INICIO ---------------- *default host=cvsup.freebsd.org *default base=/usr *default prefix=/usr *default release=cvs *default tag=RELENG_5_1 *default delete use-rel-suffix *default compress
src-all ports-all tag=. CURRENT #---------- FIM -------------------
Help Paulo Quartieri
Retirado do /usr/src/UPDATING
20031112:
The statfs structure has been updated with 64-bit fields to
allow accurate reporting of multi-terabyte filesystem
sizes. You should build world, then build and boot the new kernel
BEFORE doing a `installworld' as the new kernel will know about
binaries using the old statfs structure, but an old kernel will
not know about the new system calls that support the new statfs
structure.
Note that the backwards compatibility is only present when the
kernel is configured with the COMPAT_FREEBSD4 option. Since
even /bin/sh will not run with a new kernel without said option
you're pretty much dead in the water without it. Make sure you
have COMPAT_FREEBSD4!
Running an old kernel after a `make world' will cause programs
such as `df' that do a statfs system call to fail with a bad
system call. Marco Wertejuk <[EMAIL PROTECTED]> also reports
that cfsd (ports/security/cfs) needs to be recompiled after
these changes are installed.****************************DANGER*******************************
DO NOT make installworld after the buildworld w/o building and
installing a new kernel FIRST. You will be unable to build a
new kernel otherwise on a system with new binaries and an old
kernel.Voce compilou o 5.2 e deu um 'shutdown now', ou seja, ficou com o kernel do 5.1 na memoria, quando deu o installworld, ele foi instalando os novos binarios, que eram imcompativeis com o kernel antigo, e quando ele precisou usar um desses binarios novos que jah estava instalado, provocou o erro, o ideal sera ao inves de ter dado um 'shutdown now', ter dado um 'reboot', com isso vc iria rodar o make installworld com o kernel novo.
Agora voce esta com metade dos binarios novos e metade antigos, e o kernel novo, eu o aconselho a tentar recompilar o 5.2 e instalar ele por completo, pelo menos voce vai ficar com um release correto, aih depois vc tenta fazer o downgrade, nao sei se essa mudanca ira compilcar a sua vida ou nao, mas tente e depois poste aqui.
[]�s -- Renato Botelho Developer & Unix Admin
_______________________________________________________________ Sair da Lista: http://lists.fugspbr.org/listinfo.cgi Historico: http://www4.fugspbr.org/lista/html/FUG-BR/
