Custom Kernel - Revision history

Sidetone at 13:18, 30 October 2015

2015-10-30T13:18:35Z

Sidetone: make.conf cpu architecture

2015-10-30T13:16:19Z

make.conf cpu architecture

Sidetone: updating sources before compiling

2014-12-21T14:25:44Z

updating sources before compiling

Jimbo: Reverted edits by 158.232.241.4 (Talk); changed back to last version by 203.213.7.132

2007-11-07T13:51:37Z

Reverted edits by 158.232.241.4 (Talk); changed back to last version by 203.213.7.132

203.213.7.132 at 12:21, 30 May 2005

2005-05-30T12:21:22Z

203.213.7.132 at 12:20, 30 May 2005

2005-05-30T12:20:55Z

Taxman: linked to the kernel article I wrote. Accidentally duplicated some of this

2004-09-17T18:43:36Z

linked to the kernel article I wrote. Accidentally duplicated some of this

Jimbo at 20:52, 25 August 2004

2004-08-25T20:52:24Z

Jimbo: /* Editing your new kernel */

2004-08-23T07:30:04Z

Editing your new kernel

Jimbo: /* Compiling your new kernel */

2004-08-23T06:57:47Z

Compiling your new kernel

@@ Line 28: / Line 28: @@
 == Editing your new kernel ==
-This is relatively easy: just '''edit /root/kernels/MYKERNEL'''.  This article isn't going to go into much detail about all the wonderful things you can do to a custom kernel - see [[Why Custom Kernels]] if you're interested in that.
+This is relatively easy: just edit {{file|/root/kernels/MYKERNEL}}.  This article isn't going to go into much detail about all the wonderful things you can do to a custom kernel - see [[Why Custom Kernels]] if you're interested in that.
 ==Editing make.conf==
@@ Line 53: / Line 53: @@
 == Recovering from your new kernel if you messed up ==
-Did you screw something up in your kernel, and the system won't boot?  Fear not, recovery is easier than you think.  When the system boots, instead of selecting "Normal", "ACPI Disabled", or "Safe" at the menu (FreeBSD 5.x) or hitting enter to boot (FreeBSD 4.x), go into the boot loader - it's the option at the bottom of the menu on FreeBSD 5.x, and you just press any key OTHER than enter to get into it if you're running FreeBSD 4.x.  Now that you're looking at this ominous and unhelpful-seeming command line, type '''boot kernel.old''' and you should be in business - and once the system is back up, you will probably want to '''mv /boot/kernel /boot/kernel.oops''' and '''cp -Rpv /boot/kernel.old /boot/kernel''' so that you'll have your old, working kernel in place again in case you have to reboot again before trying to fix what you did wrong the last time and reinstall a new kernel again.
+Did you screw something up in your kernel, and the system won't boot?  Fear not, recovery is easier than you think.  When the system boots, instead of selecting "Normal", "ACPI Disabled", or "Safe" at the menu (FreeBSD 5.x) or hitting enter to boot (FreeBSD 4.x), go into the boot loader - it's the option at the bottom of the menu on FreeBSD 5.x, and you just press any key OTHER than enter to get into it if you're running FreeBSD 4.x.  Now that you're looking at this ominous and unhelpful-seeming command line, type {{cmd|boot kernel.old}} and you should be in business - and once the system is back up, you will probably want to {{cmd|mv /boot/kernel /boot/kernel.oops}} and {{cmd|cp -Rpv /boot/kernel.old /boot/kernel}} so that you'll have your old, working kernel in place again in case you have to reboot again before trying to fix what you did wrong the last time and reinstall a new kernel again.
 [[Category:Common Tasks]]

@@ Line 2: / Line 2: @@
 == Updating Kernel sources==
-You may want to update kernel sources before starting. Use [[subversion]] to do this. It's also a good idea to update the base with the command ''[[freebsd-update]]'' before compiling the custom kernel.
+You may want to update kernel sources before starting. Use [[subversion]] to do this. It's also a good idea to update the base with the command {{cmd|[[freebsd-update]]}} before compiling the custom kernel.
-To use svnup, install, then configure ''/usr/local/etc/svnup.conf'' . Based on its settings the command with an example arguments is:
+To use svnup, install, then configure {{file|/usr/local/etc/svnup.conf}}. Based on its settings the command with an example arguments is:
   # svnup sources
 == Copying GENERIC so that you can edit it ==
-First, you'll need to know your system architecture - are you using an i386 (386, 486, athlon, pentium, etc) machine, an ia64 (Intel Itanium 64-bit) machine, an AMD64 (Athlon64 or Opteron) machine...?  If you have no idea, odds are good that 1. you're using an i386 machine, and 2. you should really start paying more attention to your system's hardware specs.
+First, you'll need to know your system architecture - are you using an i386 (386, 486, athlon, pentium, etc) machine, an ia64 (Intel Itanium 64-bit) machine, an AMD64 (Athlon64 or Opteron) machine...?  To get this information, run {{cmd|uname -p}}.
-Once you've got that figured out, '''cd''' into the appropriate directory like this: '''cd /usr/src/sys/<nowiki>[i386/amd64/ia64/whatever]</nowiki>/conf''', and '''ls'''.  You'll see something like this:
+Once you've got that figured out, {{cmd|cd}} into the appropriate directory like this: {{cmd|cd /usr/src/sys/''<nowiki>[i386/amd64/ia64/architecture]</nowiki>''/conf}}, and {{cmd|ls}}.  You'll see something like this:
   ph34r#''' cd /usr/src/sys/amd64/conf'''
@@ Line 24: / Line 24: @@
   ph34r#''' ln -s /root/kernels/MYKERNEL MYKERNEL'''
-What we just did is make a directory named "kernels" in root's home directory, then copy GENERIC to MYKERNEL in that directory, then make a symlink from /usr/src/sys/yourarchitecture/conf/MYKERNEL to that file to make sure that any scripts looking for your kernel in ''this'' directory will find it.  (This IS important for later.)
+What we just did is make a directory named {{file|kernels}} in root's home directory, then copy {{file|GENERIC}} to {{file|MYKERNEL}} in that directory, then make a symlink from {{file|/usr/src/sys/yourarchitecture/conf/MYKERNEL}} to that file to make sure that any scripts looking for your kernel in ''this'' directory will find it.  (This IS important for later.)
-−
 == Editing your new kernel ==
 This is relatively easy: just '''edit /root/kernels/MYKERNEL'''.  This article isn't going to go into much detail about all the wonderful things you can do to a custom kernel - see [[Why Custom Kernels]] if you're interested in that.
 == Compiling your new kernel ==

← Older revision		Revision as of 14:25, 21 December 2014
Line 1:		Line 1:
	The default [[kernel]] installed with the system, also known as GENERIC, is generally a good choice for all-purpose use but sometimes you may want to tweak it a little. For example, if you have a motherboard with flaky [[ACPI]] support, you may need to change your kernel configurations to disable [[APIC]] so that you can still use the [[ACPI]] features. Or you may choose to [[Disable ACPI]] altogether. Or perhaps you just want to remove unnecessary kernel drivers to [[conserve memory]] on some legacy hardware you're trying to keep useful. Here's how you do it:		The default [[kernel]] installed with the system, also known as GENERIC, is generally a good choice for all-purpose use but sometimes you may want to tweak it a little. For example, if you have a motherboard with flaky [[ACPI]] support, you may need to change your kernel configurations to disable [[APIC]] so that you can still use the [[ACPI]] features. Or you may choose to [[Disable ACPI]] altogether. Or perhaps you just want to remove unnecessary kernel drivers to [[conserve memory]] on some legacy hardware you're trying to keep useful. Here's how you do it:

		+	== Updating Kernel sources==
		+	You may want to update kernel sources before starting. Use [[subversion]] to do this. It's also a good idea to update the base with the command ''[[freebsd-update]]'' before compiling the custom kernel.
		+
		+	To use svnup, install, then configure ''/usr/local/etc/svnup.conf'' . Based on its settings the command with an example arguments is:
		+	# svnup sources

	== Copying GENERIC so that you can edit it ==		== Copying GENERIC so that you can edit it ==

← Older revision		Revision as of 12:21, 30 May 2005
Line 49:		Line 49:

	[[Category:Common Tasks]]		[[Category:Common Tasks]]
−
−	~~123~~

← Older revision		Revision as of 12:20, 30 May 2005
Line 49:		Line 49:

	[[Category:Common Tasks]]		[[Category:Common Tasks]]
		+
		+	123

← Older revision		Revision as of 18:43, 17 September 2004
Line 1:		Line 1:
−	The default kernel installed with the system, also known as GENERIC, is generally a good choice for all-purpose use but sometimes you may want to tweak it a little. For example, if you have a motherboard with flaky [[ACPI]] support, you may need to change your kernel configurations to disable [[APIC]] so that you can still use the [[ACPI]] features. Or you may choose to [[Disable ACPI]] altogether. Or perhaps you just want to remove unnecessary kernel drivers to [[conserve memory]] on some legacy hardware you're trying to keep useful. Here's how you do it:	+	The default [[kernel]] installed with the system, also known as GENERIC, is generally a good choice for all-purpose use but sometimes you may want to tweak it a little. For example, if you have a motherboard with flaky [[ACPI]] support, you may need to change your kernel configurations to disable [[APIC]] so that you can still use the [[ACPI]] features. Or you may choose to [[Disable ACPI]] altogether. Or perhaps you just want to remove unnecessary kernel drivers to [[conserve memory]] on some legacy hardware you're trying to keep useful. Here's how you do it:

@@ Line 8: / Line 8: @@
 Once you've got that figured out, '''cd''' into the appropriate directory like this: '''cd /usr/src/sys/<nowiki>[i386/amd64/ia64/whatever]</nowiki>/conf''', and '''ls'''.  You'll see something like this:
-  '''ph34r#''' cd /usr/src/sys/amd64/conf
+  ph34r#''' cd /usr/src/sys/amd64/conf'''
- '''ph34r#''' ls
+ ph34r#''' ls'''
   GENERIC         GENERIC.hints   Makefile        gethints.awk    noSMPnoAPIC
-  '''ph34r#'''
+  ph34r#
 See that file named GENERIC?  That's the kernel configuration.  YOU DO NOT WANT TO EDIT THIS ONE DIRECTLY - for one thing, if you screw up your kernel configuration so badly you need to start over, you'll want GENERIC to refer back to.  For another, even if you're a genius and never ever ever screw up, the next time you update your system sources, you could lose your shiny new kernel config!  So this is what we'll do instead.
-  '''ph34r#''' mkdir /root/kernels
+  ph34r#''' mkdir /root/kernels'''
- '''ph34r#''' cp GENERIC /root/kernels/MYKERNEL
+ ph34r#''' cp GENERIC /root/kernels/MYKERNEL'''
- '''ph34r#''' ln -s /root/kernels/MYKERNEL MYKERNEL
+ ph34r#''' ln -s /root/kernels/MYKERNEL MYKERNEL'''
 What we just did is make a directory named "kernels" in root's home directory, then copy GENERIC to MYKERNEL in that directory, then make a symlink from /usr/src/sys/yourarchitecture/conf/MYKERNEL to that file to make sure that any scripts looking for your kernel in ''this'' directory will find it.  (This IS important for later.)
@@ Line 30: / Line 30: @@
 Still easy... do it like this:
-  '''ph34r#''' cd /usr/src
+  ph34r#''' cd /usr/src'''
- '''ph34r#''' make buildkernel KERNCONF=MYKERNEL
+ ph34r#''' make buildkernel KERNCONF=MYKERNEL'''
 This is going to take a while - on my Athlon64 3000+, it takes approximately three and a half minutes.  On [[User:Pete | Pete]]'s Athlon 2000+, it took around seven minutes.  If you're trying to build a stripped down kernel for legacy hardware with very few resources to work with at all, you could easily be in for half an hour or so of hot kernel compiling action, so go get a cup of coffee or something while it compiles.
@@ Line 39: / Line 39: @@
 Does it ever get hard?  Nah.
-  '''ph34r#''' make installkernel KERNCONF=MYKERNEL
+  ph34r#''' make installkernel KERNCONF=MYKERNEL'''
 This won't take any time at all - but if it ''does'' take a lot of time and throw pages and pages of text on the screen, you made a typo in the KERNCONF section of the command, and it's trying to build and install some other kernel, and you will have to hit Ctrl-C to break out of the compilation and go right back up to '''Compiling your new kernel''' and start from there.  Whoops.

@@ Line 34: / Line 34: @@
   '''ph34r#''' make buildkernel KERNCONF=MYKERNEL
-This is going to take a while - on my Athlon64 3000+, it takes approximately three and a half minutes.  On [[User:Pete]]'s Athlon 2000+, it took around seven minutes.  If you're trying to build a stripped down kernel for legacy hardware with very few resources to work with at all, you could easily be in for half an hour or so of hot kernel compiling action, so go get a cup of coffee or something while it compiles.
+This is going to take a while - on my Athlon64 3000+, it takes approximately three and a half minutes.  On [[User:Pete | Pete]]'s Athlon 2000+, it took around seven minutes.  If you're trying to build a stripped down kernel for legacy hardware with very few resources to work with at all, you could easily be in for half an hour or so of hot kernel compiling action, so go get a cup of coffee or something while it compiles.
-−
 == Installing your new kernel ==