i'm now getting regardless of the config a question whether i'd like to enable this and that when i issue the command:
make-kpkg --initrd --append-to-version=-botnetgodalphamale kernel_image kernel_headers
"Prompt for development and/or incomplete code/drivers (EXPERIMENTAL) [N/y/?] n
Local version - append to kernel release (LOCALVERSION) []
Automatically append version information to the version string (LOCALVERSION_AUTO) [N/y/?] n
Support for paging of anonymous memory (swap) (SWAP) [Y/n/?] y
System V IPC (SYSVIPC) [Y/n/?] y
BSD Process Accounting (BSD_PROCESS_ACCT) [Y/n/?] y
BSD Process Accounting version 3 file format (BSD_PROCESS_ACCT_V3) [Y/n/?] y
Export task/process statistics through netlink (EXPERIMENTAL) (TASKSTATS) [N/y/?] n
Auditing support (AUDIT) [Y/n/?] y
Enable system-call auditing support (AUDITSYSCALL) [N/y/?] n
Kernel .config support (IKCONFIG) [N/m/y/?] n
Kernel log buffer size (16 => 64KB, 17 => 128KB) (LOG_BUF_SHIFT) [14] 14
Control Group support (CGROUPS) [N/y/?] n
Group CPU scheduler (GROUP_SCHED) [Y/n/?] (NEW) "
i don't want to go thru them all, i'd just like to compile the darn kernel like It used to compile.
| Problem booting a barebone kernel in VMWare | 2 hours ago | Linux kernel |
| IP layer send packet | 6 hours ago | Linux kernel |
| PID to ELF image full path | 9 hours ago | Linux kernel |
| SMDK2410 LCD Framebuffer driver | 12 hours ago | Linux kernel |
| types of kernel | 23 hours ago | Linux kernel |
| magical mounts | 2 days ago | Linux kernel |
| Problem in scim in Fedora 9 | 2 days ago | Linux general |
| The new Western Digital power saving drives | 2 days ago | Hardware |
| Battery Maximizer Software | 3 days ago | Linux kernel |
| windows folder creation surprise | 3 days ago | Windows |
n/m
n/m I just went into menuconfig and exited - it asked if i'd like to save the changes - i said yes and now it's compiling fine. :)
append-to-version
I really do think your --append-to-version is the most interesting part of your post :)
Trying to build the next storm network?
make oldconfig vs. make menuconfig
What you were experiencing before was a 'make oldconfig'.
Every new kernel may contain new configuration options versus the previous kernel, and when you run 'make oldconfig', it asks you explicitly at the command line whether you want the default setting for the new option (i.e. hit enter) or if you want to change the setting. It goes ahead and fills in the values for all the carryover options.
This is a necessary step when upgrading from a 2.6.x kernel to 2.x.y kernel (when x
Don't skip it.
What you see there is "make oldconfig", which is ran on the existing configuration file (which again is taken from the running kernel, unless you haven't supplied your own .config). It's usually a very good idea to check all the new features, because blindly compiling you might end up with suboptimal, or even non working system if something crucial has changed.
For example, if you were using some SATA/PATA driver which has been deprecated for some time because of a newer and better driver, the new kernel dropping the old driver would lead to a nonbootable system.
Running make menuconfig and exiting with saving changes equals to having pressed enter to every single line, but then you'll be missing all the changes.