F5F Stay Refreshed Software Operating Systems config

config

config

Pages (2): 1 2 Next
K
Ks34_MisteR
Member
245
08-30-2021, 06:04 AM
#1
I have been trying to recompile the Linux kernel in kali but when I get do the <make menuconfig> command it throws me this error: <make menuconfig make: *** No rule to make target 'menuconfig'. Stop.> I have been following instructions from the Kali Linux site and have changed the command for the new release of the kernel: https://www.kali.org/docs/development/re...pendencies
K
Ks34_MisteR
08-30-2021, 06:04 AM #1

I have been trying to recompile the Linux kernel in kali but when I get do the <make menuconfig> command it throws me this error: <make menuconfig make: *** No rule to make target 'menuconfig'. Stop.> I have been following instructions from the Kali Linux site and have changed the command for the new release of the kernel: https://www.kali.org/docs/development/re...pendencies

N
NetaGamesMan
Junior Member
22
08-30-2021, 10:48 AM
#2
No, there were no additional errors.
N
NetaGamesMan
08-30-2021, 10:48 AM #2

No, there were no additional errors.

M
mistercraft77
Posting Freak
900
09-16-2021, 01:37 AM
#3
Yes, you are in the right folder.
M
mistercraft77
09-16-2021, 01:37 AM #3

Yes, you are in the right folder.

T
TheDeath_Pro
Member
128
09-23-2021, 03:47 PM
#4
I was in the kernel directory.
T
TheDeath_Pro
09-23-2021, 03:47 PM #4

I was in the kernel directory.

U
136
09-23-2021, 03:53 PM
#5
I switched the version from 4.9 to 6.0 and moved it into the .config folder—it was pretty straightforward.
U
UltraPieGaming
09-23-2021, 03:53 PM #5

I switched the version from 4.9 to 6.0 and moved it into the .config folder—it was pretty straightforward.

K
KillSt3al
Member
113
09-23-2021, 09:58 PM
#6
The configuration should reside in a single file, not as a directory.
K
KillSt3al
09-23-2021, 09:58 PM #6

The configuration should reside in a single file, not as a directory.

K
kloseseb11
Member
61
09-25-2021, 09:22 PM
#7
It seems you meant to clarify that the path could be copied as well (/.config).
K
kloseseb11
09-25-2021, 09:22 PM #7

It seems you meant to clarify that the path could be copied as well (/.config).

Z
ZeKiSelf
Junior Member
4
09-26-2021, 08:44 PM
#8
No, I don't have access to files in that folder.
Z
ZeKiSelf
09-26-2021, 08:44 PM #8

No, I don't have access to files in that folder.

H
HannibalPlays
Junior Member
47
09-27-2021, 07:35 AM
#9
I’m not sure I grasp your point. Could you clarify what you’re referring to?
H
HannibalPlays
09-27-2021, 07:35 AM #9

I’m not sure I grasp your point. Could you clarify what you’re referring to?

C
Cefreak113
Senior Member
484
09-30-2021, 11:32 PM
#10
In short, don't keep your kernel settings in /Personally. You can pull tarballs into /usr/src/ and run tasks from /usr/src/linux[whatever] as root, which is acceptable. You're setting up the lowest level of your system, and running make as root makes sense—some modules rely on finding kernels at /usr/src/linux. The Makefile you see is usually located in the root of your project, guiding make on how to build specific parts. When compiling a kernel, targets like "[something]config" handle the setup before compilation. If make says a target is missing, it's likely due to typos or being in the wrong directory. The advice you're getting is useful but lacks context; it doesn't explain why you're packaging the kernel this way. Also, moving /boot/config-[version] to /usr/src/linux/.config might not be ideal, as zcat will always use the current config and reduce errors. Just confirm you're in the correct kernel source before making changes.
C
Cefreak113
09-30-2021, 11:32 PM #10

In short, don't keep your kernel settings in /Personally. You can pull tarballs into /usr/src/ and run tasks from /usr/src/linux[whatever] as root, which is acceptable. You're setting up the lowest level of your system, and running make as root makes sense—some modules rely on finding kernels at /usr/src/linux. The Makefile you see is usually located in the root of your project, guiding make on how to build specific parts. When compiling a kernel, targets like "[something]config" handle the setup before compilation. If make says a target is missing, it's likely due to typos or being in the wrong directory. The advice you're getting is useful but lacks context; it doesn't explain why you're packaging the kernel this way. Also, moving /boot/config-[version] to /usr/src/linux/.config might not be ideal, as zcat will always use the current config and reduce errors. Just confirm you're in the correct kernel source before making changes.

Pages (2): 1 2 Next