I have seen people try to achieve the forever elusive single digit boot time before, and fail continually at it. I was once called in to try and fix this supposedly chaotic behavior with a friend's computer: He was optimizing everything, removing things he did not need, and I remember that he was particularly interested in repeated defragmentation (no effing idea), and he managed to get his boot time, which was about a minute when he started, to around 30 seconds. Here's the funny part: he then did some minor tweaks to the system, hoping to squeeze the last one or two seconds out of it, and KABOOM! His boot time jumped to two frigging minutes!
What happened was that he had pushed his system to the limit, such that it realised that something was wrong and jumped to the safest setting, which happened to be the slowest one. Two weeks of his effort, down the drain just like that.
This is the reason why I always tell people not to follow online guides that offer to speed up your system 'quick' since none of them, even if they work, make a lasting impact.
In this case, since I'm trying for something that I know is going to be hard, I've decided to work on it from the ground up. The first step: compile the kernel by hand. This is something everyone, experts and beginners alike, myself included, try very hard to stay away from. The reason is simple: its messy. Not to mention time-consuming. I remember my first time trying to compile a kernel: I sat up from 1 am till 6 watching each individual module get compiled, and at 6.14 the whole process crashed. It took another all-nighter to find the problem, and another to watch the compile process closely.
But, in this case, I'm going to do it. First thing to do, go through the config sheets looking for every extra piece of code I don't need. This would make the kernel impossible to boot on any other computer, but that was something we knew all along, right?
I'll get back to you once I'm done.
Over and out.
What happened was that he had pushed his system to the limit, such that it realised that something was wrong and jumped to the safest setting, which happened to be the slowest one. Two weeks of his effort, down the drain just like that.
This is the reason why I always tell people not to follow online guides that offer to speed up your system 'quick' since none of them, even if they work, make a lasting impact.
In this case, since I'm trying for something that I know is going to be hard, I've decided to work on it from the ground up. The first step: compile the kernel by hand. This is something everyone, experts and beginners alike, myself included, try very hard to stay away from. The reason is simple: its messy. Not to mention time-consuming. I remember my first time trying to compile a kernel: I sat up from 1 am till 6 watching each individual module get compiled, and at 6.14 the whole process crashed. It took another all-nighter to find the problem, and another to watch the compile process closely.
But, in this case, I'm going to do it. First thing to do, go through the config sheets looking for every extra piece of code I don't need. This would make the kernel impossible to boot on any other computer, but that was something we knew all along, right?
I'll get back to you once I'm done.
Over and out.
