This blog is not meant for this., maybe I'll delete this post some day... but I just have to let it out: AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAARRRRRRRRRRGHHHHHHHHHHHHHHH!!!
Yet another discouraging and disappointing day. *&#@!! Puh-leasee remind me again why I chose to do this and why the heck am I still doing it?! Yargh!
I think I'll go and have a haircut. Nah, I'm not shaving the head bald, have a punk haircut or anything like that. I'm not that traumatised ... yet. Will just have the fringes and the back part trimmed slightly. Not at all adventurous ... Maybe if someone were to pop out of a bank and hand me a wad of cash, I might have my hair dyed. Hmmm... then again, I think I'll probably take the cash and buy either another set of graphic novels or another ipod! 'Hair' is not on top of my priority list at all!
Monday, August 21, 2006
Sunday, August 20, 2006
Kernel compile and kernel sources
I didn't know that everytime the package gentoo-sources is updated, the symlink of /usr/src/linux still points to the first original sources, from which the kernel was compiled. Therefore, although I compile a new kernel everytime there is an updated version of the source, it is actually not compiled using the updated version but rather the old version. I found this out while trying to compile the new ATI-drivers and found that there were errors because they were using the old kernel source. Am I making any sense? Ah well, as long as I know what I'm saying... Anyway, I got this from the Gentoo Linux Documentation regarding kernel upgrade:
Three ways in order to make the /usr/src/linux symbolic link point to the sources of the kernel you are running.
1. Portage can update the symlink automatically when you emerge new kernel sources. All you have to do is add the symlink flag to the USE variable in /etc/make.conf
(Add the symlink keyword)
USE="symlink x86 3dnow 3dnowex X aac aalib adns alsa apache2"
2. Use app-admin/eselect to modify the symlink.
Install eselect if you don't have it)
#emerge eselect
(See the list of available kernels)
#eselect kernel list
Available kernel symlink targets:
[1] linux-2.6.9-gentoo-r1
[2] linux-2.6.9-gentoo-r2
(Select the correct kernel)
#eselect kernel set 1
3. Manually update the symlink
# cd /usr/src
# ln -sfn linux-latest-version linux
Three ways in order to make the /usr/src/linux symbolic link point to the sources of the kernel you are running.
1. Portage can update the symlink automatically when you emerge new kernel sources. All you have to do is add the symlink flag to the USE variable in /etc/make.conf
(Add the symlink keyword)
USE="symlink x86 3dnow 3dnowex X aac aalib adns alsa apache2"
2. Use app-admin/eselect to modify the symlink.
Install eselect if you don't have it)
#emerge eselect
(See the list of available kernels)
#eselect kernel list
Available kernel symlink targets:
[1] linux-2.6.9-gentoo-r1
[2] linux-2.6.9-gentoo-r2
(Select the correct kernel)
#eselect kernel set 1
3. Manually update the symlink
# cd /usr/src
# ln -sfn linux-latest-version linux
Thursday, August 10, 2006
Firefox and Mouse 2
Another thing I noticed about Firefox: Scrolling up and down a page very quickly with the mouse wheel will trigger the command 'Go Back' and 'Go Forward' respectively.
After reading some websites, I've found out that this is not a Firefox bug (therefore the title of this post is actually not justified) but rather a problem with xorg or something like that. Apparently this will occur in all applications with a horizontal scroll bar.
To prevent this from occuring in Firefox alone:
set mousewheel.horizscroll.withnokey.action to 0 in about:config
Or edit the xorg.conf:
For my case, I edited this line:
Option "ZAxisMapping" "4 5 6 7"
into
Option "ZAxisMapping" "4 5"
## Note the absence of 6 and 7. Why they were there in the first place, I don't know. I only have one mouse wheel. At least, I think that 6 and 7 represent the second wheel (for horizontal scrolling?)
After reading some websites, I've found out that this is not a Firefox bug (therefore the title of this post is actually not justified) but rather a problem with xorg or something like that. Apparently this will occur in all applications with a horizontal scroll bar.
To prevent this from occuring in Firefox alone:
set mousewheel.horizscroll.withnokey.action to 0 in about:config
Or edit the xorg.conf:
For my case, I edited this line:
Option "ZAxisMapping" "4 5 6 7"
into
Option "ZAxisMapping" "4 5"
## Note the absence of 6 and 7. Why they were there in the first place, I don't know. I only have one mouse wheel. At least, I think that 6 and 7 represent the second wheel (for horizontal scrolling?)