OMV V3.xx Erasmus X86_64 LTS kernels
-
- OMV 3.x
- Update
- demetris
-
-
That's a long process.
Question: for the "Select Linux kernel config options and drivers to build ", do I have manually download network drivers, UPS ... and compile them too?
-
When you do the make menuconfig step, you can select drivers to be compiled into the kernel or created as a module. Sometimes, the desired driver is neither. With the newer kernels like 4.5 and 4.6, most drivers should be available.
I used Gentoo for years and compiling kernels becomes second nature when using it
-
I found someone mention the script for compile kernel on that site: https://github.com/mtompkins/linux-kernel-utilities
The script seems to be easy to use. -
Go through the manual process a few times and learn what is going on. The script won't add drivers for you that you add with make menuconfig.
-
Ok, but the video for the script does show make menuconfig: https://www.youtube.com/watch?v=Us88qzNL3oI
-
Ok, but the video for the script does show make menuconfig: https://www.youtube.com/watch?v=Us88qzNL3oI
I know it executes it. I was just saying it won't enable the drivers for you and that is toughest part of compiling a kernel (which is not tough). -
Alles anzeigen
@tinh_x7
I dont have OMV v2 to test but am positive at 99.99% they would work.
@pr_bond
You can find various guides over google like the one @ryecoaaron have link to.
You are welcome to install and molest any of my released kernels and if you can find ANY intended security hole please report me to moderators so this thread can close to oblivion.
Have in mind that i compile and use these kernels myself on my production systems so install with confidence that i stand behind my work and i always accept any opinion good or bad
when is valid and not making assumptions about it beforehand.Molest?
LOL. -
Molest also means:
Pester or harass (someone), typically in an aggressive or persistent manner.
That someone can be my kernel
In other news
4.4.15 LTS is up!
Enjoy -
It only work if I use sudo, why?
I got permission denied at the last step of fakeroot:
I tried this code, and it failed too:Codemake-kpkg --rootcmd fakeroot --initrd --revision=1.0.NAS kernel_image kernel_headers -j 2Codefakeroot make-kpkg --initrd --revision=1.0.NAS kernel_image kernel_headers -j 2 exec make kpkg_version=12.036+nmu3 -f /usr/share/kernel-package/ruleset/minimal.mk debian DEBIAN_REVISION=1.0.NAS INITRD=YES ====== making target debian/stamp/conf/minimal_debian [new prereqs: ]====== This is kernel package version 12.036+nmu3. test -d debian || mkdir debian mkdir: cannot create directory `debian': Permission denied make: *** [debian/stamp/conf/minimal_debian] Error 1 Failed to create a ./debian directory: No such file or directory at /usr/bin/make-kpkg line 984.I got the required packages installed:
Codesudo apt-get install git fakeroot build-essential ncurses-dev xz-utils libssl-dev bc sudo apt-get install kernel-package -
@demetris
various guides over google don't interest me, i'am interested of guide of you to check how you do.
For security reasons, at my works, i need check all unofficial source if any malicious code is present.
If there are not any problems, I say nothing.
I have nothing against you, is to be vigilant.
building kernel is a long, tedious and difficult, you make good job !! -
Who in here know how to resolve that fakeroot ?
-
It is a permissions issue. Can you build the kernel as root?
-
I tried root and it worked, but I canceled it in the middle of process.
I can't find the solution anywhere. I can run as 'sudo' but that defeat the purpose of having 'fakeroot'.
I tried chown root:root; root:users, but same error.By the way, there are many questions during the compilation process, which options should I check 'Yes"?
Does the directory that I build kernel matter? -
Why are you concerned about building a kernel with root? On Gentoo, you always build as root. I know what fakeroot does because I build the plugins with it. The problem with building the kernel is using where the sources are located (/usr/src/linux) and that is not owned by non-root users. I don't recommend changing it. Building most .deb packages with non-root is fine. Building the kernel package is best left for building with root.
What questions? If you post the specific question, I can answer better.
-
I'm currently compiling in /opt/.
The questions start after I ran the fakeroot make-kpkg --initrd --revision=1.0.NAS kernel_image kernel_headers -j 2.
There is a lot. -
Why /opt? If you want to build as a user, build it in a sub-directory of the user's home directory.
I don't know what those questions are since I have rarely built a kernel the Debian way. Typically I would say take the defaults. If the kernel doesn't build correctly, you can just do it again.
-
Kernel is building just fine in /home/aaron as aaron. I will post more about the questions when it gets there. I could see it asking a lot of questions if you ran make oldconfig because that asks you about all new modules/drivers/etc that are included in the new kernel but weren't in your old kernel.
-
The make menuconfig doesn't ask many, but it asks when I'm compiling the kernel at the end.
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!