Re: [gentoo-user] Switching from Genkernel to manual build
Dan Cowsill escribió: Is there any specific process to or problems one might encounter as a result of switching from a Genkernel built kernel over to a manually built kernel? Thanks. As far as I can think of it would be enough getting the config file generated by genkernel, editing it through make config or similar and go ahead. Actually, if you take it as is it would work, but probably you'll have lots of stuff you don't want/need, so your task will be mainly tuning it down; be careful with those things you think you don't need, I'd cut parameters away in several step (change config, build, install, try a couple of days, then change again). HTH, Abraham -- -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] Switching from Genkernel to manual build
Abraham Marín Pérez wrote: Dan Cowsill escribió: Is there any specific process to or problems one might encounter as a result of switching from a Genkernel built kernel over to a manually built kernel? Thanks. As far as I can think of it would be enough getting the config file generated by genkernel, editing it through make config or similar and go ahead. Actually, if you take it as is it would work, but probably you'll have lots of stuff you don't want/need, so your task will be mainly tuning it down; be careful with those things you think you don't need, I'd cut parameters away in several step (change config, build, install, try a couple of days, then change again). HTH, Abraham And always keep a working kernel as a backup just in case you get a bad one. I keep a few for that reason myself like this: [EMAIL PROTECTED] / # ls -al /boot/bzImage-2.6.* -rw-r--r-- 1 root root 2189488 Jan 4 2007 /boot/bzImage-2.6.18.gentoo-r6-1 -rw-r--r-- 1 root root 2357808 Jun 8 05:47 /boot/bzImage-2.6.20-r8-1 -rw-r--r-- 1 root root 2389616 Jun 8 07:01 /boot/bzImage-2.6.20-r8-2 -rw-r--r-- 1 root root 2396880 Jun 13 01:53 /boot/bzImage-2.6.20-r8-3 [EMAIL PROTECTED] / # I try to keep one from a earlier version plus at least one older of the current version. Also, you may want to keep a copy of the .config file too. It can be a life saver. I hope that helps. Dale :-) :-) -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] Switching from Genkernel to manual build
On 8/1/07, Dan Cowsill [EMAIL PROTECTED] wrote:
/etc/genkernel.conf
# Run 'make menuconfig' before compiling this kernel?
MENUCONFIG=no
# Run 'make clean' before compilation?
# If set to NO, implies MRPROPER WILL NOT be run
# Also, if clean is NO, it won't copy over any configuration
# file, it will use what's there.
CLEAN=no
# Run 'make mrproper' before configuration/compilation?
MRPROPER=no
# Save the new configuration in /etc/kernels upon
# successfull compilation
SAVE_CONFIG=yes
# Debug Level
DEBUGLEVEL=5
Set those, and then I recommend just stay with using genkernel, it
basically converts genkernel from a kernel configurator, to merely a
nice automated build-and-install script.
that way you can configure your kernel custome like usual, and then just
genkernel --kernname=somenickname all
and go away and leave it and it will take care of the rest :)
--
Kent
ruby -e '[1, 2, 4, 7, 0, 9, 5, 8, 3, 10, 11, 6, 12, 13].each{|x|
print enNOSPicAMreil [EMAIL PROTECTED][(2*x)..(2*x+1)]}'
--
[EMAIL PROTECTED] mailing list
Re: [gentoo-user] Switching from Genkernel to manual build
On Mittwoch, 1. August 2007, Kent Fredric wrote:
On 8/1/07, Dan Cowsill [EMAIL PROTECTED] wrote:
/etc/genkernel.conf
# Run 'make menuconfig' before compiling this kernel?
MENUCONFIG=no
# Run 'make clean' before compilation?
# If set to NO, implies MRPROPER WILL NOT be run
# Also, if clean is NO, it won't copy over any configuration
# file, it will use what's there.
CLEAN=no
# Run 'make mrproper' before configuration/compilation?
MRPROPER=no
# Save the new configuration in /etc/kernels upon
# successfull compilation
SAVE_CONFIG=yes
# Debug Level
DEBUGLEVEL=5
Set those, and then I recommend just stay with using genkernel, it
basically converts genkernel from a kernel configurator, to merely a
nice automated build-and-install script.
that way you can configure your kernel custome like usual, and then just
genkernel --kernname=somenickname all
and go away and leave it and it will take care of the rest :)
--
Kent
ruby -e '[1, 2, 4, 7, 0, 9, 5, 8, 3, 10, 11, 6, 12, 13].each{|x|
print enNOSPicAMreil [EMAIL PROTECTED][(2*x)..(2*x+1)]}'
cp .config linux/
make oldconfig
make all modules_install install
that is all that is needed to build a kernel without that genkernel stuff.
You can put that in a script or in one line with some in between, if you
want.
Results in sexy /boot like this:
ls -lh /boot/
insgesamt 7,1M
lrwxrwxrwx 1 root root1 20. Apr 2006 boot - .
lrwxrwxrwx 1 root root 36 29. Jul 11:16 config -
config-2.6.22.1-cfs-v19reiser4libata
-rw-r--r-- 1 root root 36K 29. Jul 01:50 config-2.6.22.1-cfs-v19reiser4
-rw-r--r-- 1 root root 34K 29. Jul 11:16 config-2.6.22.1-cfs-v19reiser4libata
-rw-r--r-- 1 root root 34K 29. Jul 03:19
config-2.6.22.1-cfs-v19reiser4libata.old
lrwxrwxrwx 1 root root 40 29. Jul 11:16 config.old -
config-2.6.22.1-cfs-v19reiser4libata.old
drwxr-xr-x 2 root root 1,0K 19. Jun 03:18 grub
drwx-- 2 root root 12K 24. Mär 2003 lost+found
drwxr-xr-x 2 root root 1,0K 11. Jun 19:27 memtest86plus
lrwxrwxrwx 1 root root 40 29. Jul 11:16 System.map -
System.map-2.6.22.1-cfs-v19reiser4libata
-rw-r--r-- 1 root root 934K 29. Jul 01:50 System.map-2.6.22.1-cfs-v19reiser4
-rw-r--r-- 1 root root 883K 29. Jul 11:16
System.map-2.6.22.1-cfs-v19reiser4libata
-rw-r--r-- 1 root root 883K 29. Jul 03:19
System.map-2.6.22.1-cfs-v19reiser4libata.old
lrwxrwxrwx 1 root root 44 29. Jul 11:16 System.map.old -
System.map-2.6.22.1-cfs-v19reiser4libata.old
lrwxrwxrwx 1 root root 37 29. Jul 11:16 vmlinuz -
vmlinuz-2.6.22.1-cfs-v19reiser4libata
-rw-r--r-- 1 root root 1,6M 29. Jul 01:50 vmlinuz-2.6.22.1-cfs-v19reiser4
-rw-r--r-- 1 root root 1,4M 29. Jul 11:16
vmlinuz-2.6.22.1-cfs-v19reiser4libata
-rw-r--r-- 1 root root 1,4M 29. Jul 03:19
vmlinuz-2.6.22.1-cfs-v19reiser4libata.old
lrwxrwxrwx 1 root root 41 29. Jul 11:16 vmlinuz.old -
vmlinuz-2.6.22.1-cfs-v19reiser4libata.old
the symlinks are all created by install.
just have a vmlinuz and a vmlinuz.old entry in menu.lst and you are always
safe.
--
[EMAIL PROTECTED] mailing list
Re: [gentoo-user] Switching from Genkernel to manual build
On 8/1/07, Abraham Marín Pérez [EMAIL PROTECTED] wrote: Dan Cowsill escribió: Is there any specific process to or problems one might encounter as a result of switching from a Genkernel built kernel over to a manually built kernel? As far as I can think of it would be enough getting the config file generated by genkernel, editing it through make config or similar and go ahead. Only other thing I ran into (admittedly in 2004 or 2005 or so) is if genkernel is doing any initrd-magick for you you'll need to either understand it and do it yourself, or config your kernel so all that stuff is built-in. It was a little embarrassing when none of my JFS partitions got found on that first reboot. Keep a boot CD or DVD in case of real disaster, and configure your current boot kernel as an alternative choice in GRUB until you get the hand-rolled version stabilized. -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] Switching from Genkernel to manual build
On 8/2/07, Volker Armin Hemmann [EMAIL PROTECTED] wrote:
On Mittwoch, 1. August 2007, Kent Fredric wrote:
On 8/1/07, Dan Cowsill [EMAIL PROTECTED] wrote:
/etc/genkernel.conf
# Run 'make menuconfig' before compiling this kernel?
MENUCONFIG=no
# Run 'make clean' before compilation?
# If set to NO, implies MRPROPER WILL NOT be run
# Also, if clean is NO, it won't copy over any configuration
# file, it will use what's there.
CLEAN=no
# Run 'make mrproper' before configuration/compilation?
MRPROPER=no
# Save the new configuration in /etc/kernels upon
# successfull compilation
SAVE_CONFIG=yes
# Debug Level
DEBUGLEVEL=5
Set those, and then I recommend just stay with using genkernel, it
basically converts genkernel from a kernel configurator, to merely a
nice automated build-and-install script.
that way you can configure your kernel custome like usual, and then just
genkernel --kernname=somenickname all
and go away and leave it and it will take care of the rest :)
--
Kent
ruby -e '[1, 2, 4, 7, 0, 9, 5, 8, 3, 10, 11, 6, 12, 13].each{|x|
print enNOSPicAMreil [EMAIL PROTECTED][(2*x)..(2*x+1)]}'
cp .config linux/
make oldconfig
make all modules_install install
that is all that is needed to build a kernel without that genkernel stuff.
You can put that in a script or in one line with some in between, if you
want.
Results in sexy /boot like this:
ls -lh /boot/
insgesamt 7,1M
lrwxrwxrwx 1 root root1 20. Apr 2006 boot - .
lrwxrwxrwx 1 root root 36 29. Jul 11:16 config -
config-2.6.22.1-cfs-v19reiser4libata
-rw-r--r-- 1 root root 36K 29. Jul 01:50 config-2.6.22.1-cfs-v19reiser4
-rw-r--r-- 1 root root 34K 29. Jul 11:16 config-2.6.22.1-cfs-v19reiser4libata
-rw-r--r-- 1 root root 34K 29. Jul 03:19
config-2.6.22.1-cfs-v19reiser4libata.old
lrwxrwxrwx 1 root root 40 29. Jul 11:16 config.old -
config-2.6.22.1-cfs-v19reiser4libata.old
drwxr-xr-x 2 root root 1,0K 19. Jun 03:18 grub
drwx-- 2 root root 12K 24. Mär 2003 lost+found
drwxr-xr-x 2 root root 1,0K 11. Jun 19:27 memtest86plus
lrwxrwxrwx 1 root root 40 29. Jul 11:16 System.map -
System.map-2.6.22.1-cfs-v19reiser4libata
-rw-r--r-- 1 root root 934K 29. Jul 01:50 System.map-2.6.22.1-cfs-v19reiser4
-rw-r--r-- 1 root root 883K 29. Jul 11:16
System.map-2.6.22.1-cfs-v19reiser4libata
-rw-r--r-- 1 root root 883K 29. Jul 03:19
System.map-2.6.22.1-cfs-v19reiser4libata.old
lrwxrwxrwx 1 root root 44 29. Jul 11:16 System.map.old -
System.map-2.6.22.1-cfs-v19reiser4libata.old
lrwxrwxrwx 1 root root 37 29. Jul 11:16 vmlinuz -
vmlinuz-2.6.22.1-cfs-v19reiser4libata
-rw-r--r-- 1 root root 1,6M 29. Jul 01:50 vmlinuz-2.6.22.1-cfs-v19reiser4
-rw-r--r-- 1 root root 1,4M 29. Jul 11:16
vmlinuz-2.6.22.1-cfs-v19reiser4libata
-rw-r--r-- 1 root root 1,4M 29. Jul 03:19
vmlinuz-2.6.22.1-cfs-v19reiser4libata.old
lrwxrwxrwx 1 root root 41 29. Jul 11:16 vmlinuz.old -
vmlinuz-2.6.22.1-cfs-v19reiser4libata.old
the symlinks are all created by install.
just have a vmlinuz and a vmlinuz.old entry in menu.lst and you are always
safe.
--
[EMAIL PROTECTED] mailing list
Yeah, but 1: no INITRD is built,
2: using genkernel build script will automatically add new entries in grub.conf
ie:
zcat /proc/config.gz .config
make oldconfig
genkernel --kernname=sexy all reboot
;)
--
Kent
ruby -e '[1, 2, 4, 7, 0, 9, 5, 8, 3, 10, 11, 6, 12, 13].each{|x|
print enNOSPicAMreil [EMAIL PROTECTED][(2*x)..(2*x+1)]}'
--
[EMAIL PROTECTED] mailing list
Re: [gentoo-user] Switching from Genkernel to manual build
On 8/1/07, Neil Bothwick [EMAIL PROTECTED] wrote: On Thu, 2 Aug 2007 08:28:46 +1200, Kent Fredric wrote: Yeah, but 1: no INITRD is built, Which you rarely need with a hand built kernel, but if you do it can be compiled with the kernel. 2: using genkernel build script will automatically add new entries in grub.conf ie: make install removes the need for adding new entries to an ever-growing menu.lst, all you need are two entries for current kernel and previous kernel (vmlinu[zx] and vmlinu[zx].old). Right. The only reason I see for keeping genkernel (and the reason I use it in the first place) is a machine that changes hardware frequently (like mine at work), so, a simple rsync of my whole HD to the new machine can boot with most hardware recognized for a starter... I also use it on my laptops because its easier... (but that's not a good reason, cause there are people who think manual build is easier). -- Daniel da Veiga Computer Operator - RS - Brazil -BEGIN GEEK CODE BLOCK- Version: 3.1 GCM/IT/P/O d-? s:- a? C++$ UBLA++ P+ L++ E--- W+++$ N o+ K- w O M- V- PS PE Y PGP- t+ 5 X+++ R+* tv b+ DI+++ D+ G+ e h+ r+ y++ --END GEEK CODE BLOCK-- -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] Switching from Genkernel to manual build
On Thu, 2 Aug 2007 08:28:46 +1200, Kent Fredric wrote: Yeah, but 1: no INITRD is built, Which you rarely need with a hand built kernel, but if you do it can be compiled with the kernel. 2: using genkernel build script will automatically add new entries in grub.conf ie: make install removes the need for adding new entries to an ever-growing menu.lst, all you need are two entries for current kernel and previous kernel (vmlinu[zx] and vmlinu[zx].old). -- Neil Bothwick Jimmy Hoffa is buried here -- X signature.asc Description: PGP signature
