Re: problem with buildworld
On 5 Feb 2018, at 18:48, Filippo Morettiwrote: > > Buildworld failed with libpam/modules error.I tried to delete /usr/obj/usr > but I get the following error[root@sting /usr/src]# rm -rf /usr/obj/usrrm: > /usr/obj/usr/src/i386.i386/lib/libpam/modules/pam_opieaccess/pam_opieaccess.so.6.debug: > Bad file descriptorrm: > /usr/obj/usr/src/i386.i386/lib/libpam/modules/pam_opieaccess: Directory not > emptyrm: /usr/obj/usr/src/i386.i386/lib/libpam/modules: Directory not > emptyrm: /usr/obj/usr/src/i386.i386/lib/libpam: Directory not emptyrm: > /usr/obj/usr/src/i386.i386/lib: Directory not emptyrm: > /usr/obj/usr/src/i386.i386: Directory not emptyrm: /usr/obj/usr/src: > Directory not emptyrm: /usr/obj/usr: Directory not empty[root@sting > /usr/src]# Any help would be appreciatedsincerelyFilippo Try rebooting into single user mode, and running "fsck -f -y" until all your filesystems are completely clean. Also, please switch to a mail client that does not completely mangle your messages. -Dimitry signature.asc Description: Message signed with OpenPGP
Re: Jan 18 04:05 vboxdrv.ko breaks r328637: Wed Jan 31 kernel. crashes
On Mon, Feb 5, 2018 at 2:49 AM, Taaviwrote: > Hi > > Not really wanting to do that. Using pkg binary system for purpose > > That would lead to question why binary package driver crashes kernel? > > regards, > Taavi > This is a real problem with kmod packages. If hte kernel is modified in any way, modules must be re-built. It may take a while for the package to get re-built for a given change as the port has not been modified. The recommended method is to put port modules into /etc/src.conf PORTS_MODULES list so that kernel rebuild will always rebuild the modules, but that only works if the kernel IS built from sources and re-installed. It will be a bigger issue when more people start doing binary updates to the kernel.more routinely. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
problem with buildworld
Buildworld failed with libpam/modules error.I tried to delete /usr/obj/usr but I get the following error[root@sting /usr/src]# rm -rf /usr/obj/usrrm: /usr/obj/usr/src/i386.i386/lib/libpam/modules/pam_opieaccess/pam_opieaccess.so.6.debug: Bad file descriptorrm: /usr/obj/usr/src/i386.i386/lib/libpam/modules/pam_opieaccess: Directory not emptyrm: /usr/obj/usr/src/i386.i386/lib/libpam/modules: Directory not emptyrm: /usr/obj/usr/src/i386.i386/lib/libpam: Directory not emptyrm: /usr/obj/usr/src/i386.i386/lib: Directory not emptyrm: /usr/obj/usr/src/i386.i386: Directory not emptyrm: /usr/obj/usr/src: Directory not emptyrm: /usr/obj/usr: Directory not empty[root@sting /usr/src]# Any help would be appreciatedsincerelyFilippo ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Jan 18 04:05 vboxdrv.ko breaks r328637: Wed Jan 31 kernel. crashes
Hi Not really wanting to do that. Using pkg binary system for purpose That would lead to question why binary package driver crashes kernel? regards, Taavi Sent with ProtonMail Secure Email. Original Message On February 4, 2018 8:19 PM, Cy Schubertwrote: >In message <1JOKDx2CeRUWS-ZzfU-7hCpDv4Yb0eMqlfrGzV-DnL89_Qg9MMxTZqdZJNu5 > FMckEUy >rF3KwemDLaSlMY20vAlIW332XEhUTh3qcihfQfv8=@protonmail.com>, Taavi writes: >>see subject >> > > Try rebuilding and reinstalling virtualbox-ose-kmod. > > > >Cheers, > Cy Schubert cy.schub...@cschubert.com >FreeBSD UNIX: c...@freebsd.org Web: http://www.FreeBSD.org > > The need of the many outweighs the greed of the few. > > > ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: buildkernel with PORTS_MODULES fails: Variable OBJTOP is recursive
On Sun, Feb 04, 2018, O. Hartmann wrote: > Am Sat, 3 Feb 2018 11:17:06 +0100 > "O. Hartmann"schrieb: > > > Am Sat, 3 Feb 2018 11:10:53 +0300 > > Vladimir Zakharov schrieb: > > > > > Hello, Oliver! > > > > > > On Fri, Feb 02, 2018, O. Hartmann wrote: > > > > On Thu, 1 Feb 2018 12:10:30 +0300 > > > > Vladimir Zakharov wrote: > > > > > > > > > Hello! > > > > > > > > > > For some time (about a week) building and installing kernel fails with > > > > > the error "Variable OBJTOP is recursive." when going to build/install > > > > > module from ports. > > > > > > > > > > Last successful build was at r328426. Next build at r328527 failed and > > > > > still broken at r328649. > > > > > > > > > > Without PORTS_MODULES building and installing kernel succeeds. Another > > > > > workaround: ignore error and build/install module directly from ports. > > > > > > > > > > > > > I have had the very same issue! > > > > > > > > You need to perform a "installworld" first (just comment out the > > > > PORTS_MODULES= > > > > parts of /etc/src.conf or /etc/make.conf, buildworld and buildkernel > > > > (maybe not > > > > a full buildworld, but I do not know the state of your source tree) and > > > > perform > > > > a regular installation of the world. It could be something easier by > > > > direkctly > > > > install-only the mk-portions, but recently, some changes to world > > > > (LLVM) made > > > > it worth anyway to buildworld. > > > > > > > > As recommended by others earlier on this list according to this > > > > subject, this > > > > procedure makes the problem go away. > > > > > > Thanks for your answer. Unfortunately, this didn't help. > > > > > > > You are correct! I made a mistake and had the portions still commented out. > > I'm very > > sorry. > > > > This remains a bug! > > > > This problem has been introduced with > > svn commit: r328489 - head/sys/conf > > The the appropriate list for reference. > Indeed, reverting r328489 fixes the problem. -- Regards, | "In theory there is no difference between theory Vladimir Zakharov | and practice. In practice there is."- Yogi Berra ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"