Though the printer is now being used on a friend's PC under Windows, but I'll try it as soon as possible.
thanks in advance ;-)

Yes, that's exactly what I want. OK, now, assume I want a kernel, with the traits similar to the one of Ubuntu, I mean all main Kernel directories put there under /, including /boot and /lib. What part in the above process I wanna do I'm omitting, or I'm doing wrong? Since it'll all be done when I know this (what am I NOT doing and what am I doing wrong).

Still thanks for your helps Marc.

Fine! thanks. ;)

Well, documentations confused me a little bit.

I have some new questions now: So you mean that even if I omit "make module_install" still the .config file applies it, right? I mean loadable modules are activated by default, as I left it to itself, so it won't actually need make module_install, and they WILL be installed, right?

About the sda thing: I have created 4 partitions on my HDD for OS, of which 2 are Ubuntu and Kubuntu now, and the 2 others I've left, 1 for messing with and shuffling and twiddling my custom kernel compilation(s), and the otherone just to keep one stable operational kernel that I'll compile myself.

Now:
sda1 -> Ubuntu,
sda2 -> Kubuntu,
sda3 -> Stable, working Kernel,
sda4 -> (extended),
sda5 -> messy kernel,

What I'm asking you to tell me, is the most straight forward procedure to put my kernel in /dev/sda5, just how in GUI of installation I chose my Kubuntu to go to /dev/sda2.
I haven't yet tried modifying the makefile, but I wonder if there was some way, built into the makefile itself (or something like that) that makes the choice of installation directory more automated.

Thanks :)

:-D , yeah, I know its obvious, but I thought maybe the drive directories in /media, like RAMFS ought to be something temporary or virtual or something, well now you're telling me its not so, thanks so much!

And oh, one last question (I'm just curious so I repeat it): Therefore softwares such as file managers do automatically create and remove the directories, right? (I now know I must create the dirs myself manually, and at least once.)

And no, its not related to compilation, I was just asking it for other uses.

Thanks so much anyway, Marc.

Hi.
I wanna compile a kernel myself, but haven't proceeded yet.

I've just used menuconfig to save the default ".config" file :-D . As I know, I must now run:

make

make module_install

make install

(The Kernel is 3.1.8, obviously from kernel.org)

Here are my questions:
1. Is the order above correct?
2. As I know, just as I run the above commands, my compilation will replace the kernel of this Ubuntu, (since it'll go to directories like /boot /etc, which are my CURRENT UBUNTU, at the time of installation), but what I want and have meant to do, is to install it to my /dev/sda5. How may I do this?
3. And then an update-grub from here in Ubuntu should add the kernel to boot list, yet keeping this Ubuntu's GRUB/MBR config, right?

thanks so much for you helps.

Yes it worked this time, without any error or something.
Now I have another question: Is the process the same under ANY compilation of the Linux kernel? I mean Debian, Fedora, RedHat, whatever. Is it that in general "in Linux OS" first the mount directory must exists, and then do the mounting?

If yes, then in Ubuntu file managers, such as Dolphin, when I mount a volume something like a script ought to create the directory, then execute the mount command, and remove the directory when unmounting, right? And thus there's no way to do the mounting with a nonexistent directory, right?

oops! When I execute:

sudo mount /dev/sda10 /media/tmp_ext4

mount: mount point /media/tmp_ext4 does not exist

No matter what other parameters I use besides (-t, auto, ...), I always get this same message. What should I do?

Yes, I've gained much more insight to GNU/Linux, thanks to 1. so often, your rich supports, 2. my own strong commitment. :-)

YES! That's it man, it worked! I just removed all unity, GNOME shell, lightdm and gdm from tty(1-6) which were my only access to the OS, and installed GNOME shell and lightdm again, and everything is normal again. Something related to lightdm should have been removed the last time I twiddled the packages.

Thanks Matthew.