You are not logged in.
Pages: 1
Hello,
I was thinking about at the kernel compiling to get an own kernel. But I would to know some things:
- Which are the advantages?
- Is difficult to do?
- I will get a better boot time?
- On a dual-core system (cpu Intel e6300 @3.3Ghz), how much time it about requires?
- Probably I will install two kernel (the first that I'm using, and the second as custom), if the second will be stable and better than the first, can I remove the first to use only the second?
Thanks for attention.
Regards,
Grant.
Last edited by Grant (2012-12-22 14:40:40)
Offline
Not exactly a new topic, a search would provide several threads on this point. Nonetheless, my personal point of view:
- Which are the advantages?
The main significant advantage is that you are forced to read a lot of kernel documentation and to understand what does what in the kernel. A very minor advantage is that, if you compile the relevant stuff into the kernel, you can get rid of the initcpio, gaining a simplification of the system.
- Is difficult to do?
If you want to streamline the compilation to the stuff you really need then the first time you do it is a cognitive challenge. The gentoo wiki (in gentoo almost everybody compiles the kernel) is a nice source of infos about this.
- I will get a better boot time?
No, at least not a significant degree.
- On a dual-core system (cpu Intel e6300 @3.3Ghz), how much time it about requires?
If you streamline the configuration, the compilation will be quite fast (10-20 minutes). If you do not streamline it (but in this case you really have time to waste), the compilation will be much longer.
- Probably I will install two kernel (the first that I'm using, and the second as custom), if the second will be stable and better than the first, can I remove the first to use only the second?
You can do whatever you want, but its is a safe practice to keep two kernels with different bootloader entries, just in case something goes wrong with one of them.
Mortuus in anima, curam gero cutis
Offline
'What can be asserted without evidence can also be dismissed without evidence.' - Christopher Hitchens
'There's no such thing as addiction, there's only things that you enjoy doing more than life.' - Doug Stanhope
GitHub Junkyard
Offline
I have asked this because I want to get a better boot time and memory usage.
But the real thing that's fat is gnome 3. Arch linux boots in about 9 seconds, gnome 3 in 23 seconds more or less.
OT: Do you think that with kde I will get what I want?
Wow really?
Last edited by Grant (2012-12-22 12:25:49)
Offline
Think about it this way: With a custom kernel you'll eliminate two or three seconds from boot, mostly by eliminating the need for an initramfs. But how long will it take you to learn how to compile a kernel and then get a fully working, fully streamlined kernel together? How many boots will it require to break even time-wise?
I'm not saying you shouldn't learn to create your own kernel. It's cool knowing the details of what's in there. But chasing boot times is not a good reason to do it. Only do it if you want to tinker for the sake of tinkering - you know, to satisfy your inner geek
.
Also, worrying about memory usage of the kernel, when you're running a monster DE on top of it? Kinda silly, don't you think? ![]()
And finally, a streamlined, machine-specific kernel will compile in like 3-5 minutes, not 10-20 like patroclo7 says.
Last edited by Gusar (2012-12-22 13:00:51)
Offline
I tried compiling my own streamlined kernel. It was worth it, but only as a learning experience that taught me I never want to do that again.
The decrease in boot time was not any better than using the stock kernel with a streamlined initramfs. Falconindy has a blog post about trimming down mkinitcpio.conf trim a bit off of boot time. The savings here are also quite small, but this is *much* easier to do. I'd suggest trimming your initramfs before you bother compiling a kernel.
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
As others have mentioned, compiling the Arch kernel takes a long time, and figuring out which options you can safely switch off will take even longer. To get a good compromise to get you started you could try "make localyesconfig". That will automatically switch off all modules that you don't have loaded on your machine, and compile in the ones you have loaded. That should allow you to boot without an initramfs.
Offline
I have read some stuff more about kernel compiling. I will probably do, but not now. I don't need it.
Right now I'm using about 1,2gb of ram: I have only opened chromium to answer you. I have thought: "Arch should be lighter than ubuntu, but why I use better ram? It's strange.".
But the real problem is gnome 3.
Do you think that switching to kde I will get better performance?
Sorry if I'm OT.
Offline
About your Gnome vs KDE question, here's a wild idea:
Try It And See
![]()
Offline
But is faster that someone tells me, you don't think?
Offline
For you maybe, not for that "someone."
Don't be a help vampire.
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
Installing kde with gnome3, there will be any conflicts?
I'm a newbie in Arch Linux, for this I prefer to read the think of someone instead to try directly. We are talking of a new DE, not a simple program.
Last edited by Grant (2012-12-22 14:28:04)
Offline
@Grant - Arch is not a hand-holding distro. Your thread seems to be all over the place, kernel questions, de question, etc. Suggest you read the wiki on topics of interest before posting.
Offline
I know to be OT, I'm only trying to get some little answer at my doubts. I think for those is useless open a new thread, because I should to open many threads.
I go to find something, else I will open a new thread.
I'm very sorry for my ot.
Grant.
Last edited by Grant (2012-12-22 14:41:45)
Offline
Pages: 1