I just filled my drive when compiling. So, I will have to start over.
OMV V3.xx Erasmus X86_64 LTS kernels
-
- OMV 3.x
- Update
- demetris
-
-
I'm not sure which options to say No, so I hit Enter for default.
Here are most of the questions that I copied: http://pastebin.com/G9Q7p4KhI think about 400 questions.
This is more than my final exam ! -
You are answering questions from make oldconfig. Hitting enter taking the defaults is fine. If it says (new), you most likely don't need it. If you aren't sure, include it. It just makes the kernel bigger.
-
-
I just compiled my own kernel 4.6.4, and it working!
It took 30 mins to be done.uname -aLinux server 4.6.4 #1 SMP Wed Jul 13 18:33:30 EDT 2016 x86_64 GNU/Linux
openmediavault 2.2.5 allCodelinux-headers-4.6.4_1.0.NAS_amd64.deb 11M linux-headers-4.6.4_1.0.NAS_amd64.deb linux-image-4.6.4_1.0.NAS_amd64.deb 51M linux-image-4.6.4_1.0.NAS_amd64.deb
One error that I notice is showing on boot up:
Codeiptables v1.4.14: can't initialize iptables table `nat': Table does not exist (do you need to insmod?) Perhaps iptables or your kernel needs to be upgraded.
Am I going to answer all these 400 questions again whenever I compile the kernel?
-
If your keep the .config file, you won't have to unless you move to a new kernel version. Look through the .config for iptables/nat to see what
-
-
-
You need to keep the .config file. Once you copy the config file from /boot/ and do make oldconfig, the .config file is updated. Keep using that file and not the config file from /boot/ anymore. If you use the file from /boot/, you will have lots of questions to answer again when using make oldconfig
-
My server is currently offline, so I can't see them.
I thought you talking about the .config and .config.old from by built kernel folder.
Are they the same from /boot/ ?
Where do I copy the .config file from /boot/ to ? -
I'm confused. I guess I don't know how you are building this kernel. When I say .config, that is the only file I am talking about and since I don't know what folder you are using, I don't mention the folder. Definitely not .config.old. Didn't you copy in your config from /boot/ to the compile folder before compiling? It isn't called .config in /boot. It is called something like config-4.5.0-0.bpo.2-amd64.
-
-
I think you meant this : cp /boot/config-$(uname -r) .config
Yes, I did copied it.I built my kernel under my home user sub directory.
-
Yep, that is what I meant. And after you answer all those questions, the .config file is changed. So, if you don't want to answer all those questions when moving to a new version of the kernel, keep using that .config file. Don't copy in the config from /boot/ every time you compile a new kernel.
-
Ok, how do I fix this IP tables?
-
-
I don't use iptables but it looks like you need to modprobe iptable_nat
If that works, I would change it from a module to a compiled in driver in make menuconfig (change M to Y). -
Ok, I'll try that tonight.
Thanks.I think this is the section:
* IP: Netfilter Configuration
*
IPv4 connection tracking support (required for NAT) (NF_CONNTRACK_IPV4) [M/n/?] m
proc/sysctl compatibility with old connection tracking (NF_CONNTRACK_PROC_COMPAT) [Y/n/?] y
IPv4 nf_tables support (NF_TABLES_IPV4) [M/?] m
IPv4 nf_tables route chain support (NFT_CHAIN_ROUTE_IPV4) [M/n/?] m
IPv4 nf_tables packet duplication support (NFT_DUP_IPV4) [N/m/?] (NEW)
ARP nf_tables support (NF_TABLES_ARP) [M/n/?] m
Netfilter IPv4 packet duplication to alternate destination (NF_DUP_IPV4) [M/?] (NEW) m
ARP packet logging (NF_LOG_ARP) [N/m/y] (NEW)
IPv4 packet logging (NF_LOG_IPV4) [M/y] (NEW)
IPv4 packet rejection (NF_REJECT_IPV4) [M/y] (NEW)
IPv4 NAT (NF_NAT_IPV4) [M/n/?] m
IPv4 nf_tables nat chain support (NFT_CHAIN_NAT_IPV4) [M/n/?] m
IPv4 masquerade support (NF_NAT_MASQUERADE_IPV4) [N/m/?] (NEW)
Basic SNMP-ALG support (NF_NAT_SNMP_BASIC) [M/n/?] m
IP tables support (required for filtering/masq/NAT) (IP_NF_IPTABLES) [M/n/y/?] m
"ah" match support (IP_NF_MATCH_AH) [M/n/?] m
"ecn" match support (IP_NF_MATCH_ECN) [M/n/?] m
"rpfilter" reverse path filter match support (IP_NF_MATCH_RPFILTER) [M/n/?] m
"ttl" match support (IP_NF_MATCH_TTL) [M/n/?] m
Packet filtering (IP_NF_FILTER) [M/n/?] m
REJECT target support (IP_NF_TARGET_REJECT) [M/n/?] m
SYNPROXY target support (IP_NF_TARGET_SYNPROXY) [M/n/?] m
iptables NAT support (IP_NF_NAT) [N/m/?] (NEW)
Packet mangling (IP_NF_MANGLE) [M/n/?] m
CLUSTERIP target support (IP_NF_TARGET_CLUSTERIP) [M/n/?] m
ECN target support (IP_NF_TARGET_ECN) [M/n/?] m
"TTL" target support (IP_NF_TARGET_TTL) [M/n/?] m
raw table support (required for NOTRACK/TRACE) (IP_NF_RAW) [M/n/?] m
Security table (IP_NF_SECURITY) [M/n/?] m
ARP tables support (IP_NF_ARPTABLES) [M/n/y/?] m
ARP packet filtering (IP_NF_ARPFILTER) [M/n/?] m
ARP payload mangling (IP_NF_ARP_MANGLE) [M/n/?] m
*
* IPv6: Netfilter Configuration
*
IPv6 connection tracking support (NF_CONNTRACK_IPV6) [M/n/?] m
IPv6 nf_tables support (NF_TABLES_IPV6) [M/?] m
IPv6 nf_tables route chain support (NFT_CHAIN_ROUTE_IPV6) [M/n/?] m
IPv6 nf_tables packet duplication support (NFT_DUP_IPV6) [N/m/?] (NEW)
Netfilter IPv6 packet duplication to alternate destination (NF_DUP_IPV6) [M/?] (NEW) m
IPv6 packet rejection (NF_REJECT_IPV6) [M/y] (NEW)
IPv6 packet logging (NF_LOG_IPV6) [M/y] (NEW)
IPv6 NAT (NF_NAT_IPV6) [M/n/?] m
IPv6 nf_tables nat chain support (NFT_CHAIN_NAT_IPV6) [M/n/?] m
IPv6 masquerade support (NF_NAT_MASQUERADE_IPV6) [N/m/?] (NEW)
IP6 tables support (required for filtering) (IP6_NF_IPTABLES) [M/y/?] m
"ah" match support (IP6_NF_MATCH_AH) [M/n/?] m
"eui64" address check (IP6_NF_MATCH_EUI64) [M/n/?] m
"frag" Fragmentation header match support (IP6_NF_MATCH_FRAG) [M/n/?] m
"hbh" hop-by-hop and "dst" opts header match support (IP6_NF_MATCH_OPTS) [M/n/?] m
"hl" hoplimit match support (IP6_NF_MATCH_HL) [M/n/?] m
"ipv6header" IPv6 Extension Headers Match (IP6_NF_MATCH_IPV6HEADER) [M/n/?] m
"mh" match support (IP6_NF_MATCH_MH) [M/n/?] m
"rpfilter" reverse path filter match support (IP6_NF_MATCH_RPFILTER) [M/n/?] m
"rt" Routing header match support (IP6_NF_MATCH_RT) [M/n/?] m
"HL" hoplimit target support (IP6_NF_TARGET_HL) [M/n/?] m
Packet filtering (IP6_NF_FILTER) [M/n/?] m
REJECT target support (IP6_NF_TARGET_REJECT) [M/n/?] m
SYNPROXY target support (IP6_NF_TARGET_SYNPROXY) [M/n/?] m
Packet mangling (IP6_NF_MANGLE) [M/n/?] m
raw table support (required for TRACE) (IP6_NF_RAW) [M/n/?] m
Security table (IP6_NF_SECURITY) [M/n/?] m
ip6tables NAT support (IP6_NF_NAT) [N/m/?] (NEW)
*
-
I just recompiled the kernel today...
I have overwritten the .config from make menuconfig, then it goes straight the compilation process, but if I save it as a different name, then it force me to answer the old menuconfig.
I have to answers twice.So, if compile a new kernel, instead copy the config from boot, I just load my existing .config in the make menuconfig, right?
This is what I got at the end of the compiling process.
-
-
make menuconfig doesn't load the config. You don't even have to execute make menuconfig if you don't have any changes to make.
apt-get install libfile-fcntllock-perl will fix the warning
-
So, if I just copy the /boot/config---name.... that I want to use, then do make menuconfig, it should be fine ?
Some users say it's a proper way to do make menuconfig then make oldconfig, but to me it seems redundant.
What do you think? -
make oldconfig should come before make menuconfig. If you execute make oldconfig, you don't have to use make menuconfig unless you want to change something.
-
-
I don't like the make oldconfig, can I just use make menuconfig, and proceed the rest of the process?
-
Never tried. If you don't want to answer the questions, just use make olddefconfig before make menuconfig.
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!