LinuxQuestions.org
Help answer threads with 0 replies.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - General
User Name
Password
Linux - General This Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.

Notices

Reply
 
Search this Thread
Old 07-09-2011, 04:59 AM   #1
origami-sheep
Member
 
Registered: Dec 2009
Distribution: Arch
Posts: 103

Rep: Reputation: 2
can i compile it all into the kernel?


as someone constantly suffering from driver troubles: and as i like to shunt the same OS across several computers, i was wondering: can i compile all the software, the drivers, everything: into one big vmlinuz for easy transportation?

i'm probably a fool but hey: can i?
 
Old 07-09-2011, 05:05 AM   #2
TobiSGD
Moderator
 
Registered: Dec 2009
Location: Hanover, Germany
Distribution: Gentoo
Posts: 15,346
Blog Entries: 2

Rep: Reputation: 3978Reputation: 3978Reputation: 3978Reputation: 3978Reputation: 3978Reputation: 3978Reputation: 3978Reputation: 3978Reputation: 3978Reputation: 3978Reputation: 3978
Yes, you can.
Code:
make allyesconfig
should do the job.
 
Old 07-09-2011, 06:16 AM   #3
origami-sheep
Member
 
Registered: Dec 2009
Distribution: Arch
Posts: 103

Original Poster
Rep: Reputation: 2
what will that give me?

a vmlinux with just drivers? or will it be everything
 
Old 07-09-2011, 06:17 AM   #4
TobiSGD
Moderator
 
Registered: Dec 2009
Location: Hanover, Germany
Distribution: Gentoo
Posts: 15,346
Blog Entries: 2

Rep: Reputation: 3978Reputation: 3978Reputation: 3978Reputation: 3978Reputation: 3978Reputation: 3978Reputation: 3978Reputation: 3978Reputation: 3978Reputation: 3978Reputation: 3978
It would be the same as if you do a make menu-config and choose all available drivers to be compiled into the kernel.
 
Old 07-09-2011, 11:26 AM   #5
onebuck
Moderator
 
Registered: Jan 2005
Location: Midwest USA, Central Illinois
Distribution: SlackwareŽ
Posts: 11,013
Blog Entries: 1

Rep: Reputation: 1364Reputation: 1364Reputation: 1364Reputation: 1364Reputation: 1364Reputation: 1364Reputation: 1364Reputation: 1364Reputation: 1364Reputation: 1364
Hi,

You might find 'Linux Kernel Newbies' to be of help. Great site with loads of information available for everyone.
 
1 members found this post helpful.
Old 07-09-2011, 11:49 AM   #6
mike_rhce
Member
 
Registered: Jun 2011
Posts: 157

Rep: Reputation: Disabled
Would you want to compile it all into the kernel? IIRC, such kernels are a --lot-- bigger than standard.

In addition, I'm not quite sure what you mean by this:

Quote:
as i like to shunt the same OS across several computers
But it sounds like a good case for a common virtual machine on all four systems -- or even access to a central system via ssh -X or VNC.
 
Old 07-10-2011, 02:11 AM   #7
origami-sheep
Member
 
Registered: Dec 2009
Distribution: Arch
Posts: 103

Original Poster
Rep: Reputation: 2
my networks not quite up to that sadly :/

but i shall build all the drivers in
 
Old 07-10-2011, 04:20 AM   #8
H_TeXMeX_H
Guru
 
Registered: Oct 2005
Location: $RANDOM
Distribution: slackware64
Posts: 12,928
Blog Entries: 2

Rep: Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269
It is a bad idea, you will only have more driver trouble if you do this.
 
Old 07-10-2011, 09:26 AM   #9
onebuck
Moderator
 
Registered: Jan 2005
Location: Midwest USA, Central Illinois
Distribution: SlackwareŽ
Posts: 11,013
Blog Entries: 1

Rep: Reputation: 1364Reputation: 1364Reputation: 1364Reputation: 1364Reputation: 1364Reputation: 1364Reputation: 1364Reputation: 1364Reputation: 1364Reputation: 1364
Hi,

If you know the scope of the machines then a list of drivers necessary would be the best choice. By placing everything in the kernel you are not necessarily doing yourself any favors let alone the systems. Just do a inventory for the machines that are going to be used then compile for each. Look at 'Drivers - Linux Kernel Newbies' tutorial for aid installing or developing Drivers. Don't forget;
You will find other usable material at 'Linux Kernel Newbies' for some helpful information.

By inclusion of everything into the kernel you will be opening doors that may create problems. Size of the kernel created is not the problem unless you are changing a current Gnu/Linux distribution then size may be restricted because of media size! Some Gnu/Linux are at the fringe of the media limitations. Rebuild limitations for the ISO will be dependent on the media type.

Kernel distribution method will be dependent on the hardware to be used. Network or storage media? Don't forget that you will need to get the source for newer hardware to compile for said hardware. Some newer hardware drivers will/may still be in development stage.

For the network or storage media you can create build trees for each machine type that is to be serviced. Each build will be for a specific machine's hardware class. Much easier than to build huge kernel to service multiple machine environments. Especially changing machine environments.

Kernel modules have strengths and utility to allow one to modify. You should learn to use whenever possible. You will not see any monumental gains for built in.

Your wish to have a 'huge' kernel to suit multiple machine type environments is doable but not the best choice. If you have the same family for a hardware class with just minor differences then modules are the way to utility the service for hardware.

If your needs are for different processor architecture or families then you have different suite of problems for the machines in question. Then 'builds' to suit each is the best choice. Therefore the kernel can be customized for each architecture install.

Don't forget that some Gnu/Linux do provide different architecture support. You could then hopefully provide specific module drivers for any hardware not supported by that Gnu/Linux.

"Knowledge is of two kinds. We Know a subject ourselves, or we know where we can find information upon it."- Samuel Johnson
 
  


Reply

Tags
combo, compile, kernel


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 On
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Debian 6.0 - custom kernel compile Kernel panic - not syncing: VFS: Unable to mount Bono Debian 5 05-06-2011 06:18 PM
[Compile kernel] How to compile/install the modules ? frenchn00b Linux - General 1 09-06-2009 03:18 PM
Trying to patch kernel + compile, compile is looping. kripz Linux - Kernel 1 06-16-2009 06:51 AM
upgraded kernel, won't let me compile kernel once Suspend2 patches are applied microsoft/linux Linux - Laptop and Netbook 3 10-02-2005 02:37 PM
Kernel 2.4.23 compile causes kernel panics on ATA RAID-1 (mirror) array Raptor Ramjet Slackware 3 12-18-2003 01:40 PM


All times are GMT -5. The time now is 11:17 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