Any guarantees of future environment for NuTyX?

bozonius · Sat Jun 09 23:05:41 2018

So it looks like there is a new kernel -- not sure when that happened, because I did a sync and upgrade yesterday and all was up to date. Even after updating the kernel-lts.devel package, I still get the same error.

So what did I "forget" this time?

bash-4.4# ls /boot
config_64-4.14.48 kernel System_64.map-4.14.48
grub kernel-4.14.48-NuTyX-lts
bash-4.4# uname -a
Linux nutyx 4.14.48-NuTyX-lts #1 SMP Wed Jun 6 10:27:38 UTC 2018 x86_64 GNU/Linux
bash-4.4# uname -m
x86_64
bash-4.4# ./VBoxLinuxAdditions.run
Verifying archive integrity... All good.
Uncompressing VirtualBox 5.2.12 Guest Additions for Linux........
VirtualBox Guest Additions installer
Removing installed version 5.2.12 of VirtualBox Guest Additions...
You may need to restart your guest system to finish removing the guest drivers.
Copying additional installer modules ...
Installing additional modules ...
VirtualBox Guest Additions: Building the VirtualBox Guest Additions kernel modules.
VirtualBox Guest Additions: Look at /var/log/vboxadd-setup.log to find out what went wrong
VirtualBox Guest Additions: Starting.
VirtualBox Guest Additions: Building the VirtualBox Guest Additions kernel modules.
VirtualBox Guest Additions: Look at /var/log/vboxadd-setup.log to find out what went wrong
bash-4.4# cat /var/log/vboxadd-setup.log
Building the main Guest Additions module.
make V=1 CONFIG_MODULE_SIG= -C /lib/modules/4.14.48-NuTyX-lts/build SUBDIRS=/tmp/vbox.0 SRCROOT=/tmp/vbox.0 -j1 modules
test -e include/generated/autoconf.h -a -e include/config/auto.conf || ( \
echo >&2; \
echo >&2 " ERROR: Kernel configuration is invalid."; \
echo >&2 " include/generated/autoconf.h or include/config/auto.conf are missing.";\
echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix it."; \
echo >&2 ; \
/bin/false)
mkdir -p /tmp/vbox.0/.tmp_versions ; rm -f /tmp/vbox.0/.tmp_versions/*
make -f ./scripts/Makefile.build obj=/tmp/vbox.0
make[2]: *** No rule to make target '/tmp/vbox.0/VBoxGuest-linux.o', needed by '/tmp/vbox.0/vboxguest.o'. Stop.
make[1]: *** [Makefile:1522: _module_/tmp/vbox.0] Error 2
make: *** [/tmp/vbox.0/Makefile.include.footer:101: vboxguest] Error 2
Creating user for the Guest Additions.
Creating udev rule for the Guest Additions kernel module.
modprobe vboxguest failed
bash-4.4#

Thierry · Sun Jun 10 01:05:55 2018

Reboot maybe

Thierry · Sun Jun 10 09:18:59 2018

OK I manage to reproduce: /etc/bashrc is needed ... It fails without. Another minor issue, you do:

Code Select

su
instead of

Code Select

su -

Anyway start all over again will be very fast, (i took me less then 5 minutes) and don't delete any bash config file. Instead comment the line:
PROMPT_COMMAND=prompt_command in /etc/bashrc

Thierry · Sun Jun 10 10:24:48 2018

https://vimeo.com/274329195

bozonius · Sun Jun 10 19:29:35 2018

I replaced /etc/bashrc and it made no difference. I have been using sudo not su.

Is there a way to get rid of that string that hovers in the upper right of the bash terminal window? It is annoying. I am not sure I understand why it is there or is needed.

Even after setting a root password and logging in as "su" (not "su -") and dotting in the /etc/bashrc script, the build still fails. This does not surprise me, given that /etc/bashrc only does some tputs (which is probably causing the problem with the string appearing that scrambles the scrollback) and sets a few non-make, non-vbox related variables.

How would bashrc impact make(1) or vbox? What am I not understanding? (It is possible I am not seeing something obvious.)

Also, the exact means of logging in as root won't typically have much of an impact either. I use sudo, su, and other means of becoming root on various systems and I've not noticed any particular variation in behavior from one to another.

You need to look at those tput calls, btw. I don't think they are doing what you think they do. Maybe a French v. English difference? Idk.

Thierry · Mon Jun 11 08:00:10 2018

QuoteIs there a way to get rid of that string that hovers in the upper right of the bash terminal window?

Quote from: Thierry on Sun Jun 10 09:18:59 2018
Anyway start all over again will be very fast, (i took me less then 5 minutes) and don't delete any bash config file. Instead comment the line:
PROMPT_COMMAND=prompt_command in /etc/bashrc

And do EXACTLY like in the tuto (video)

bozonius · Wed Jun 13 04:33:26 2018

Your fix corrected the shell issue, thanks.

Now, back to the GA question. Which version of VirtualBox are you running? This may be important because there are some issues with recent kernels. Your response should be either 5.1.x or 5.2.x. Thanks again.

Thierry · Wed Jun 13 05:00:12 2018

As I told you before, as long your prompt look like this:

Code Select

bash-4.4#
which means that your environment variables are not properly sets, GA will not compile ( I was able to reproduce this issue).

bozonius · Wed Jun 13 05:44:23 2018

Please tell me which VBox version you are using. There is nothing in the shell environment that affects the GA build. I made the change you requested, and the GA's still do not build!

Thierry · Wed Jun 13 05:57:33 2018

You can find easily all the packages version on http://www.nutyx.org/en/packages.

I use Virtualbox 5.2.12

Regards,
Thierry

bozonius · Wed Jun 13 16:46:09 2018

Are you using 5.1.12 on both the host AND the guest? Which OS's?

Thierry · Wed Jun 13 17:20:33 2018

Yes on both and NuTyX OS

bozonius · Wed Jun 13 18:00:05 2018

I am running CentOS as my VBox host with VBox 5.1.12. So there is some other difference as to why I can't get GA's to compile.

I'll have a test box in a few days or so; maybe I can try some things then unless you have any more suggestions. Not having the GA's makes evaluation of NuTyX difficult because the clipboard, shared file systems, and other VBox features do not work without them which slows me down a bit. There's always FTP I guess...

Thierry · Wed Jun 13 18:03:39 2018

Hello
My suggestion would be: Make a video of your all process so I can point out what you maybe wrong.

Thanks a lot for keep trying anyway. I'm shure it's a small detail we miss.

You could also setup an ssh server and connect via ssh

Dania5583 · Sat Jun 16 16:57:54 2018

Hi Bozonius Hi Thierry
I think there is a mismatch between the version of virtualbox you use.
Bozonius says he uses 5.1.12 (are you sure because your test show that you are uncompressing GA 5.2.12) and you Thierry 5.2.12 on both sides.
Normally you must use the same level on both the host and the guest if you have virtualbox 5.1.12 the GA must would be 5.1.12. To complicate the Nutyx kernel has the modules of virtualbox 5.2.12 compile in.

if you use 5.1.12 the best way is to upgrade Virtualbox to 5.2.12 on the host

Best regards Daniel