Slashdot Mirror
Upgrading Your Current System To Kernel 2.6
An anonymous reader writes "This white paper provides an overview of the process of moving an existing desktop system to the 2.6 kernel. It will highlight other software requirements imposed by the new kernel and administrative changes that you must make when migrating an existing system to the 2.6 kernel. It supplements previous whitepapers in the same series about Customizing the 2.6 kernel [Slashdot discussion here(1)] and porting drivers to the 2.6 kernel [Slashdot discussion here(2)] to the 2.6 kernel."
Myself and my partner have for the last 13 years been doing our best to raise our adopted son in the fine traditions of GNU/Linux and free software. Imagine my horror when, upon arriving home early from work yesterday, I caught my boy touching himself while looking at pictures like this!
Further examination of his hard drive (made easy by the numerous exploits possible with the Linux kernel) we discovered references to a despicable non-GNU OS and other subversive material.
What should we do? How can we guide our boy away from filth like this and back to the true GNU way?
-- Richard
suckah
remove also the semicolon and the space from this block but leave all semicolons in the other blocks
Amen, brother
not to flame, but why is slashdot posting an article from feb 24, 2004 on how to upgrade to linux 2.6?
this article i have bookmarked tells you how to upgrade to 2.6 and its from august 29, 2003.
http://kerneltrap.org/node/view/799
Does the name Pavlov ring a bell?
Hey, I known that guy.
he probably would at least recommend against fear based persecution of those who may seem to be different than you, having been through all that himself.
with white paper....
Due to excessive bad posting from this IP or Subnet, comment posting has temporarily been disabled. If it's you, consider this a chance to sit in the timeout corner. If it's someone else, this is a chance to hunt them down. If you think this is unfair, please email moderation@slashdot.org with your MD5'd IPID and SubnetIDDue to excessive bad posting from this IP or Subnet, comment posting has temporarily been disabled. If it's you, consider this a chance to sit in the timeout corner. If it's someone else, this is a chance to hunt them down. If you think this is unfair, please email moderation@slashdot.org with your MD5'd IPID and SubnetIDDue to excessive bad posting from this IP or Subnet, comment posting has temporarily been disabled. If it's you, consider this a chance to sit in the timeout corner. If it's someone else, this is a chance to hunt them down. If you think this is unfair, please email moderation@slashdot.org with your MD5'd IPID and SubnetIDDue to excessive bad posting from this IP or Subnet, comment posting has temporarily been disabled. If it's you, consider this a chance to sit in the timeout corner. If it's someone else, this is a chance to hunt them down. If you think this is unfair, please email moderation@slashdot.org with your MD5'd IPID and SubnetID
Should be an exciting read. Maybe tomorrow I'll read how to upgrade my bios so I can reprogram the LED for my hard drive.
I struggled with the upgrade recently: why oh why didn't Debian make sure the mouse driver modules are loaded, just like the 2.2 and 2.4 kernels before it.
Anyway, if I launch X with "startx", everything works fine.
If I boot straight to X, the mouse doesn't respond. The driver's definitely loaded etc because otherwise X fails to start.
Any suggestions?
Gotta say I'm pissed off with how this was handled - why make it painful for something so generic and imperative as a PS/2 mouse? There are many reasons to knock Windows, but the very basic things that haven't changed for years always work out of the box.
That does it. Moderators on slashdot really do love the cock. A score 0 troll for a joke. Do you mod's realize you suck or do you do it for enjoyment?
it doesn't seem to have FBSD 5.x specific instructions.
Yeah? Well face it, Linux is the one true OS.
sig under development
First I jammed the knuckles of my left hand real hard against the solder points on the back of the motherboard, just enough to tear into the skin a bit.
Then I reached in and impaled my right hand on the edges of the fan guard that I had cut out to increase airflow. Finally I had my mom slam the case shut on my arms and jump on it until it latched, but when she booted the machine for me the sound still wasn't working with the 2.6 kernel.
I'd appreciate any help here. I'm running Slackware 9.1