LinuxQuestions.org
Review your favorite Linux distribution.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - General > LinuxAnswers Discussion
User Name
Password
LinuxAnswers Discussion This forum is to discuss articles posted to LinuxAnswers.

Notices

Reply
 
Search this Thread
Old 03-07-2005, 03:43 PM   #1
acidjuice
Member
 
Registered: Jan 2005
Location: a tiny spot on the iceberg
Distribution: Slackware 10.1 (dropline 2.10, kernel 2.6.11.6)
Posts: 320

Rep: Reputation: 30
Post DISCUSSION: Compiling kernel 2.6.10 on a Slackware 10.1


This thread is to discuss the article titled: Compiling kernel 2.6.10 on a Slackware 10.1
 
Old 03-07-2005, 10:10 PM   #2
masand
Guru
 
Registered: May 2003
Location: INDIA
Distribution: Ubuntu, Solaris,CentOS
Posts: 5,522

Rep: Reputation: 58
hi there

everthing looks good
but i think it will be a good point to specify here

"3. Also, since I've formatted my disks using ReiserFS, I also want to be sure that at boot time the Kernel is able to read from them. To do so, under File systems I enable Reiserfs support <*>.

that nomatter what FS u use u neecxd to have ext2 Filesystem support in ur kernel
since this is required while booting

also why are u using "-j5" in the make bzImge command


regards
 
Old 03-22-2005, 05:58 AM   #3
acidjuice
Member
 
Registered: Jan 2005
Location: a tiny spot on the iceberg
Distribution: Slackware 10.1 (dropline 2.10, kernel 2.6.11.6)
Posts: 320

Original Poster
Rep: Reputation: 30
hello masand,

are you sure you need ext2 even on all reiser disks? if so, i will modify this guide.

to answer your question, the -j5 is just an optimization for CPU speed.

cheers,

aj.
 
Old 03-22-2005, 08:48 AM   #4
masand
Guru
 
Registered: May 2003
Location: INDIA
Distribution: Ubuntu, Solaris,CentOS
Posts: 5,522

Rep: Reputation: 58
hi there

yes u need ext2 fs support as well because linux first mounts as ext2 then it remounts it as reiserfs

u can check this after removing support for ext2 fs in ur kernel and it won't work

regards
 
Old 03-23-2005, 07:15 AM   #5
acidjuice
Member
 
Registered: Jan 2005
Location: a tiny spot on the iceberg
Distribution: Slackware 10.1 (dropline 2.10, kernel 2.6.11.6)
Posts: 320

Original Poster
Rep: Reputation: 30
hi,

thanks for this, however i can't modify the guide anymore. i'll keep this however.

cheers,

aj.
 
Old 03-25-2005, 05:46 PM   #6
Komakino
Senior Member
 
Registered: Feb 2004
Location: Somerset, England
Distribution: Slackware 10.2, Slackware 10.0, Ubuntu 9.10
Posts: 1,938

Rep: Reputation: 53
Hey, just read your article to see how similar your experience was to mine.

One comment:

You say to delete the /usr/src/linux symlink and replace it with one pointing to the new source. This is BAD!! According to linus /usr/src/linux should point to the kernel headers that glibc was compiled against, not those of the running kernel.

Programs will still link (or whatever) to the right headers because they will use uname -r to find the right directory, i.e.:
Code:
cd /usr/src/`uname -r`/
 
Old 03-28-2005, 09:03 AM   #7
hameedkhan
LQ Newbie
 
Registered: Oct 2004
Location: Karachi, Pakistan
Distribution: Slackware, SuSe, Ubuntu, CentOS
Posts: 19

Rep: Reputation: 0
Hi,
Thanks for your guide. One thing that I really didn't understand is why do we need /sys? What if I'll not make this dir? Will my kernel not work? What is the use of this dir?

Thanks,
Hameed U. Khan
 
Old 04-01-2005, 03:45 AM   #8
acidjuice
Member
 
Registered: Jan 2005
Location: a tiny spot on the iceberg
Distribution: Slackware 10.1 (dropline 2.10, kernel 2.6.11.6)
Posts: 320

Original Poster
Rep: Reputation: 30
Quote:
Originally posted by Komakino
This is BAD!! According to linus /usr/src/linux should point to the kernel headers that glibc was compiled against, not those of the running kernel.

Programs will still link (or whatever) to the right headers because they will use uname -r to find the right directory, i.e.:
Code:
cd /usr/src/`uname -r`/
i guess no real harm done then...

but this is still strange to me, 95% of all users compiling kernel DO use this method. there are metropolitan legends about this symlink... i guess it's the most discussed symlink ever

any opinions on this welcomed.

cheers,

aj.
 
Old 04-01-2005, 03:50 AM   #9
acidjuice
Member
 
Registered: Jan 2005
Location: a tiny spot on the iceberg
Distribution: Slackware 10.1 (dropline 2.10, kernel 2.6.11.6)
Posts: 320

Original Poster
Rep: Reputation: 30
Quote:
Originally posted by hameedkhan
Hi,
Thanks for your guide. One thing that I really didn't understand is why do we need /sys? What if I'll not make this dir? Will my kernel not work? What is the use of this dir?

Thanks,
Hameed U. Khan
Starting with kernel 2.6 there's a new /sys directory for Plug and Play configuration. upgrading from previous versions of the kernel, you might therefore not have it there.
 
Old 04-12-2005, 12:40 PM   #10
michaelsanford
Member
 
Registered: Feb 2005
Location: Ottawa/Montréal
Distribution: Slackware + Darwin (MacOS X)
Posts: 468

Rep: Reputation: 30
I've just built 2.6.11.7 using a similar method, reiserfs, SATA and all (we have very similar setups).

I'm running an AMD64 3500+ (on an nVidiva nForce 3-based motherboard) and recently tried to install an app that was designed for x86_64, which is my system, right?

For some reason the program (nVidia motherboard drivers) reports that this is really a 32 bit kernel. Did I forget to check something off when I built it, or should I have built a different target (like `make bzImage x86_64` or something)?

uname -a
Code:
Linux gateway 2.6.11.7 #1 Mon Apr 11 17:18:24 EDT 2005 i686 unknown unknown GNU/Linux
GREAT how-to by the way!
 
Old 05-04-2005, 06:10 AM   #11
r_x
LQ Newbie
 
Registered: Apr 2005
Distribution: slackware 10.1
Posts: 21

Rep: Reputation: 15
this was cool...............
i upgraded my slack box from 2.4.29 to 2.6.11.8 .............
add that 1 more step in the end...................removing the old kernel when the new one fires up
 
Old 05-04-2005, 07:06 AM   #12
masand
Guru
 
Registered: May 2003
Location: INDIA
Distribution: Ubuntu, Solaris,CentOS
Posts: 5,522

Rep: Reputation: 58
Quote:
Originally posted by r_x
this was cool...............
i upgraded my slack box from 2.4.29 to 2.6.11.8 .............
add that 1 more step in the end...................removing the old kernel when the new one fires up
yes u can do that but i personlly do not recommend that

ther is not harm in keeping a kernel or 2 extra in stock,in case u find on later that u have something missing u can just boot in the other kernel and check there

regards

Last edited by masand; 05-04-2005 at 07:09 AM.
 
Old 05-13-2005, 02:28 AM   #13
LQer928
LQ Newbie
 
Registered: Apr 2005
Location: Australia
Distribution: Slackware 10.1
Posts: 17

Rep: Reputation: 0
This is a great guild for Slackware newbies , I have a question though : if I took the optional steps which remove all the symbolic links
linking to the old kernel , and then link them to the new one , does it
still make sense to make an entry for the old kernel when configuring LILO ?
Once again , great work and it's much appreciated .
 
Old 05-30-2005, 09:53 AM   #14
acidjuice
Member
 
Registered: Jan 2005
Location: a tiny spot on the iceberg
Distribution: Slackware 10.1 (dropline 2.10, kernel 2.6.11.6)
Posts: 320

Original Poster
Rep: Reputation: 30
LILO needs anyway to be run after every config change. therefore setting up a symlink would still ask you to activate those changes by running lilo.
 
Old 05-30-2005, 10:30 AM   #15
samael26
Member
 
Registered: Oct 2004
Location: France, Provence
Distribution: Debian
Posts: 848

Rep: Reputation: 30
QUOTE : from acidjuice

"Before you begin, download the necessary files and save them to /etc/src:"

Shouldn't it be /usr/src ?

Just a thought..
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
DISCUSSION: Slackware - Easy 2.6 kernel from Install disc #2 halo14 LinuxAnswers Discussion 8 06-22-2007 02:14 PM
DISCUSSION: nForce2 hardware to work in Slackware with kernel 2.4.22 TCPMeta2k1 LinuxAnswers Discussion 1 03-12-2007 03:19 AM
Slackware 10 error compiling kernel 2.6.7 nirvanix Slackware 3 05-29-2006 11:52 PM
Compiling new kernel with Slackware 10 madhatter2 Linux - Newbie 2 07-29-2004 04:08 PM
Compiling kernel 2.6.4 on Slackware 9.1 ProtoformX Linux - General 1 03-13-2004 10:41 AM


All times are GMT -5. The time now is 04:25 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration