Creating custom kernels with Debian's kernel-packaging system | ||
---|---|---|
Prev |
Fixing make xconfig error. NEED to get this updated
bash:/usr/src/linux# make xconfig rm -f include/asm ( cd include ; ln -sf asm-i386 asm) make -C scripts kconfig.tk make[1]: Entering directory `/usr/src/kernel-source-2.2.19/scripts' cat header.tk >> ./kconfig.tk ./tkparse < ../arch/i386/config.in >> kconfig.tk echo "set defaults \"arch/i386/defconfig\"" >> kconfig.tk echo "set ARCH \"i386\"" >> kconfig.tk cat tail.tk >> kconfig.tk chmod 755 kconfig.tk make[1]: Leaving directory `/usr/src/kernel-source-2.2.19/scripts' wish -f scripts/kconfig.tk Xlib: connection to ":0.0" refused by server Xlib: Client is not authorized to connect to Server Application initialization failed: couldn't connect to display ":0" Error in startup script: invalid command name "button" while executing "button .ref" (file "scripts/kconfig.tk" line 51) make: *** [xconfig] Error 1 |
It turns out this is a normal security precaution in Debian. If you get this, the way to fix it, is to do this:
bash:/usr/src/linux# xauth merge ~user/.Xauthority And then try it again: bash:/usr/src/linux# make xconfig |
Replacing user with the username you are logged in as. Do not put root there. Put your username. You may currently be logged on as root (in the terminal) but you should have logged into X-windows as a regular user.
There are some security issues to doing this. I don't know what they are, but I do know that there was a huge discussion about it on the debian-user mailing list. If you're worried about it check the archives. |