tag:blogger.com,1999:blog-377789772024-02-08T06:17:28.564-05:00Penguin Siren - Linux BeckonsAdventures with Linux and maybe BSD.empraptorhttp://www.blogger.com/profile/16908631443876760713noreply@blogger.comBlogger5125tag:blogger.com,1999:blog-37778977.post-79706414208065328362007-11-15T15:58:00.000-05:002007-11-15T16:00:05.528-05:00MovingI've decided to do away with multiple blogs and just try to keep one generic blog - <a href="http://wagonfly.blogspot.com/"> Wagonfly</a>. Will be mostly about Linux, open source software, science, philosophy, politics, etc.empraptorhttp://www.blogger.com/profile/16908631443876760713noreply@blogger.com0tag:blogger.com,1999:blog-37778977.post-43937991997518546992007-05-15T01:05:00.000-05:002007-05-15T01:24:50.015-05:00Latest FUD From MS Nothing New, Nothing Worrisome<a href="http://www.linux-watch.com/news/NS6670466370.html">"Microsoft reignites its war on Linux"</a> points out that the <a href="http://money.cnn.com/magazines/fortune/fortune_archive/2007/05/28/100033867/"> latest FUD campaign</a> is nothing new. Back in 2004, Ballmer claimed that Richard Stallman himself admitted Linux infringes upon hundreds of patents. The article points out, though, the numbers referenced by Stallman came from a study done to allay fears about patent infringements. The study measured the number of infringements and showed that it's nothing unexpected in these crazy patent-happy days.<br /><br />Groklaw also <a href="http://www.groklaw.net/article.php?story=20070513234519615"> lists reasons to not worry</a>.<br /><br />In summary, MS is up to its old tricks - hoping to scare users away from Linux with unsubstantiated FUD.empraptorhttp://www.blogger.com/profile/16908631443876760713noreply@blogger.com0tag:blogger.com,1999:blog-37778977.post-1164648746724943852006-11-27T12:31:00.000-05:002006-11-27T13:30:03.808-05:00Argh.So I upgraded to "etch". Didn't solve the problem. Whenever I get to it again, I will have to focus back on kernel configuration.empraptorhttp://www.blogger.com/profile/16908631443876760713noreply@blogger.com0tag:blogger.com,1999:blog-37778977.post-1164507979569212272006-11-25T21:26:00.000-05:002006-11-27T13:32:47.933-05:00Problem RemainsI had to compile the kernel once more - I had left ext2 file system support included as a module (the default setting). Since the ext2 support module was on the root partition and the root partition is in ext2 format, the kernel couldn't mount it.<br /><br />Second custom kernel booted the system fine with ext2 support built-in, but 137GB limit remained.<br /><br />I may have configured kernel wrong. Or it could be the BIOS or could be fdisk. I had upgraded the BIOS to the latest version available before the building the new kernel. So I will cross BIOS off the list of possible causes.<br /><br />I'll next follow <a href="http://www.debian.org/releases/testing/i386/release-notes/ch-upgrading.en.html"> these instructions for upgrading my Debian distribution to etch</a>.empraptorhttp://www.blogger.com/profile/16908631443876760713noreply@blogger.com0tag:blogger.com,1999:blog-37778977.post-1164395923062902182006-11-24T13:47:00.000-05:002006-11-24T19:13:52.070-05:00My First Custom KernelI'm compiling my first custom kernel today.<br /><br />I got going on this when my Debian machine with ASUS A7A266 could access only the first 137GB of a large hard drive I bought recently.<br /><br />I noticed that <a href="http://www.knoppix.org/">KNOPPIX 5.0.1</a> could see the whole hard drive fine, so I decided to grab the latest stable kernel available on Debian's apt-get repository - 2.6.8 for AMD K7. Well, that didn't solve it.<br /><br />After some researching, I decided compiling a custom kernel might be the way to go. Among many changes from default setting, I set the CONFIG_BLK_DEV_ALI15X3 option on (A7A266 uses ALi's chipset).<br /><br />If this doesn't work, I'll be updating fdisk.<br /><br />(update: Used steps in <a href="http://www.debian.org/doc/FAQ/ch-kernel.en.html"> The Debian GNU/Linux FAQ Chapter 9 - Debian and the kernel</a>, section 9.2)empraptorhttp://www.blogger.com/profile/16908631443876760713noreply@blogger.com0