ezjail: problemas de atualização

1

Estou tendo problemas sempre que tento atualizar meu beisebol do ezjail no FreeSDB 10.

Estou no FreeBSD 10.2-RELEASE-p11 e no ezjail v3.4.2

As prisões mostram a versão correta dentro, mas o progresso da atualização parece não ter terminado.

Isso é o que estou recebendo:

ezjail-admin update -u
Looking up update.FreeBSD.org mirrors... 4 mirrors found.
Fetching metadata signature for 10.2-RELEASE from update6.freebsd.org... done.
Fetching metadata index... done.
Inspecting system... done.
Preparing to download files... done.

No updates needed to update system to 10.2-RELEASE-p11.
No updates are available to install.
Run '/usr/sbin/freebsd-update fetch' first.
Looking up update.FreeBSD.org mirrors... 4 mirrors found.
Fetching metadata signature for 10.2-RELEASE from update3.freebsd.org... done.
Fetching metadata index... done.
Inspecting system... done.
Preparing to download files... done.

The following files will be added as part of updating to 10.2-RELEASE-p11:
/usr/src/contrib/ntp/include/ntp_keyacc.h
/usr/src/contrib/ntp/include/rc_cmdlength.h
/usr/src/contrib/ntp/include/safecast.h
/usr/src/contrib/ntp/libntp/is_ip_address.c
/usr/src/contrib/ntp/sntp/m4/ntp_problemtests.m4
/usr/src/contrib/ntp/sntp/tests/fileHandlingTest.c
/usr/src/contrib/ntp/sntp/tests/run-t-log.c
/usr/src/contrib/ntp/sntp/tests/sntptest.c
/usr/src/contrib/ntp/sntp/tests/t-log.c
/usr/src/contrib/ntp/sntp/unity/auto/parseOutput.rb
/usr/src/contrib/ntp/sntp/unity/auto/type_sanitizer.rb
/usr/src/contrib/ntp/sntp/unity/auto/unity_test_summary.py
/usr/src/contrib/ntp/sntp/unity/unity_config.h
/usr/src/contrib/ntp/tests/libntp/lfptest.c
/usr/src/contrib/ntp/tests/libntp/sockaddrtest.c
/usr/src/contrib/ntp/tests/ntpd/leapsec.c
/usr/src/contrib/ntp/tests/ntpd/ntp_prio_q.c
/usr/src/contrib/ntp/tests/ntpd/ntp_restrict.c
/usr/src/contrib/ntp/tests/ntpd/rc_cmdlength.c
/usr/src/contrib/ntp/tests/ntpd/run-leapsec.c
/usr/src/contrib/ntp/tests/ntpd/run-ntp_prio_q.c
/usr/src/contrib/ntp/tests/ntpd/run-ntp_restrict.c
/usr/src/contrib/ntp/tests/ntpd/run-rc_cmdlength.c
/usr/src/contrib/ntp/tests/ntpd/run-t-ntp_scanner.c
/usr/src/contrib/ntp/tests/ntpd/run-t-ntp_signd.c
/usr/src/contrib/ntp/tests/ntpd/t-ntp_scanner.c
/usr/src/contrib/ntp/tests/ntpd/t-ntp_signd.c
/usr/src/contrib/ntp/tests/ntpq
/usr/src/contrib/ntp/tests/ntpq/Makefile.am
/usr/src/contrib/ntp/tests/ntpq/Makefile.in
/usr/src/contrib/ntp/tests/ntpq/run-t-ntpq.c
/usr/src/contrib/ntp/tests/ntpq/t-ntpq.c
Installing updates...mkdir: /usr/jails/newjail//boot: No such file or directory
mtree: /usr/jails/newjail//boot/kernel: No such file or directory
mtree: /usr/jails/newjail//boot/kernel.old: No such file or directory
touch: /usr/jails/newjail//boot/kernel.old/.freebsd-update: No such file or directory
Could not create kernel backup directory
    
por basbebe 28.01.2016 / 11:59

1 resposta

2

Estou tentando resolver isso no momento também. Até agora eu encontrei este post nos fóruns do FreeBSD que me levaram a tentar

mkdir /basejail
mount -t nullfs -o rw /usr/jails/basejail /basejail

que permite que o /usr/jails/newjail que está sendo atualizado encontre os caminhos, como boot, etc e outros, e atualize-os. Então você pode então correr

ezjail-admin update -u

não se esqueça de desmontar e remover a pasta / basejail depois de atualizar.

Parece que você também pode executar

ezjail-admin install

para recriar a base e parece que isso também funciona, embora demore mais.

    
por 30.01.2016 / 11:21