[gentoo-dev] using more than one kernel

[gentoo-dev] using more than one kernel

[Amiel Martin]

Hi, Ive been playing with my kernel options and trying out a few 
different kernels, and Ive got a few small ideas.

first of all, there are a few packages that need to be re-emerged when 
you compile a new kernel (ie nvidia-kernel and emu10k1)

it would be nice to have a way to be able to run something like
emerge new-kernel
after compiling a new kernel. this could be done with an ebuilkd 
variable that registers an ebuild as being dependant on the kernel?

the other thing is that if I am using two different kernels, only one 
can have external packages (like nvidia-kernel and emu10k1) because they 
get cleaned out. I dont know how this would be possible, but It would be 
nice to implement something like SLOT (only different because its the 
same ebuild) that would allow you to have two versions of the same 
ebuild installed.

oh, and by the way, I just niticed that if you emerge a different 
*-sources, your .config gets copied over. That rocks.


Thanks for your time,

-AMIel


--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] using more than one kernel

[Peter Ruskin]

On Saturday 31 May 2003 23:51, Amiel Martin wrote:
> Hi, Ive been playing with my kernel options and trying out a few
> different kernels, and Ive got a few small ideas.
>
> first of all, there are a few packages that need to be re-emerged
> when you compile a new kernel (ie nvidia-kernel and emu10k1)
>
> it would be nice to have a way to be able to run something like
> emerge new-kernel
> after compiling a new kernel. this could be done with an ebuilkd
> variable that registers an ebuild as being dependant on the kernel?

I like that idea.  I currently use two build-kernel scripts that work 
around the nvidia-kernel, alsa, emu10k1 and lm_sensors thing:

============================================================
#!/bin/sh
# /usr/local/bin/build-kernel
# start this script from the kernel source directory,
# for example /usr/src/linux-2.4.20-xfs-r2
# ...test for that...
grep -q "Linux kernel" ./README
if [ "$(echo $?)" != "0" ] ; then
	echo "ERROR: You don't appear to be in a kernel source directory"
	echo
	exit
fi
# This kernel variable produces something like "-2.4.20-xfs-r2"
kernel=$(pwd | cut -dx -f2-9)
make xconfig
make dep clean
[ "$(echo $?)" == "0" ] || echo "make dep clean failed"
make bzImage
[ "$(echo $?)" == "0" ] || echo "make bzImage failed"
make modules
[ "$(echo $?)" == "0" ] || echo "make modules failed"
make modules_install
[ "$(echo $?)" == "0" ] || echo "make modules_install failed"
mount /boot
[ "$(echo $?)" == "0" ] || echo "problem mounting /boot"
cp arch/i386/boot/bzImage /boot/vmlinuz$kernel
cp System.map /boot/System.map$kernel
cp .config /boot/.config$kernel
# if just rebuilding booted kernel...
if [[ "-$(uname -r)" == "$kernel" ]] ; then
	AUTOCLEAN="no" ACCEPT_KEYWORDS="~x86" emerge lm_sensors nvidia-kernel
else
	echo "Run build-kernel-2 after next reboot to"
	echo "update lm_sensors and nvidia-kernel."
fi
echo
echo "    All done.  Now edit /boot/grub/grub.conf and reboot"
============================================================
#!/bin/sh
# /usr/local/bin/build-kernel-2
# Run this after booting into a new kernel
AUTOCLEAN="no" ACCEPT_KEYWORDS="~x86" emerge lm_sensors nvidia-kernel


--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] using more than one kernel

[Daniel Armyr]

[-- Attachment #1: Type: text/plain, Size: 360 bytes --]

> On Saturday 31 May 2003 23:51, Amiel Martin wrote:
> > Hi, Ive been playing with my kernel options and trying out a few
> > different kernels, and Ive got a few small ideas.

Your thoughts sound like something for the genkernel (emerge genkernel) program. I am pretty sure a little patch would be appreciated from the developer in charge. ;)

--Daniel Armyr

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-dev] using more than one kernel

[Hasse Hagen Johansen]

[-- Attachment #1: Type: text/plain, Size: 1018 bytes --]

On Sun, 2003-06-01 at 21:27, Peter Ruskin wrote:

> >
> > it would be nice to have a way to be able to run something like
> > emerge new-kernel
> > after compiling a new kernel. this could be done with an ebuilkd
> > variable that registers an ebuild as being dependant on the kernel?
> 

I think it would be nice to keep the alsa modules for more than one
kernel at a time (shouldn't be a problem, modules are in different
directories anyway). 

Couldn't the alsa-drivers ebuild just be changed so it doesn't unmerge
the modules, if I am gonna change kernel I would still have to manually
delete /lib/modules/x.x.x because of all the other modules not "managed"
b ebuilds. 

In my opinion the ebuilds shouldn't "control" kernel modules at all.

For me it is frustrating. I have at low latency patched kernel for audio
work, and another when I am not making music. It would be nice if I
didn't need to reemerge alsa-drivers, when switching between those
kernels.


Regards

Hasse Johansen

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-dev] using more than one kernel

[Norberto BENSA]

[-- Attachment #1: signed data --]
[-- Type: text/plain, Size: 284 bytes --]

nbensa@venkman ~ $ date ; echo ${Hasse Hagen Johansen}
Sunday 01 June 2003 05:50 pm

> In my opinion the ebuilds shouldn't "control" kernel modules at all.
>

What about CONFIG_PROTECT=/lib/modules ?? 

I didn't tried it myself, but it should (in theory) work...

Norberto

[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-dev] using more than one kernel

[Zach Welch]

Amiel Martin wrote:
> the other thing is that if I am using two different kernels, only one 
> can have external packages (like nvidia-kernel and emu10k1) because they 
> get cleaned out. I dont know how this would be possible, but It would be 
> nice to implement something like SLOT (only different because its the 
> same ebuild) that would allow you to have two versions of the same 
> ebuild installed.

This is a highly desired feature that is being tracked in Bugzilla:

http://bugs.gentoo.org/show_bug.cgi?id=20071

Cheers,

Zach Welch
Gentoo Embedded Lead
Superlucidity Services


--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] using more than one kernel

[Georgi Georgiev]

On 01/06/2003 at 20:27:54(+0100), Peter Ruskin used 2.1Kbytes just to say:
> #!/bin/sh
> # /usr/local/bin/build-kernel-2
> # Run this after booting into a new kernel
> AUTOCLEAN="no" ACCEPT_KEYWORDS="~x86" emerge lm_sensors nvidia-kernel

As sometimes I am not sure what packages need reemerging, I use this script:

for i in `grep -l ' /lib/modules/' /var/db/pkg/*/*/CONTENTS`; do
	ii=`dirname $i`;
	cat $ii/COUNTER; echo " $ii";
done | sort -n | cut -f5,6 -d/ | sed -e 's/^/>=/'

which on my system currently produces:

>=sys-libs/cdfs-0.5c
>=media-sound/alsa-driver-0.9.3a
>=x11-base/xfree-drm-4.3.0-r2
>=sys-apps/i2c-2.7.0
>=sys-apps/lm-sensors-2.7.0
>=media-video/mplayer-0.90-r1
>=sys-apps/lufs-0.9.5

This can be directly piped to "xargs emerge" or... whatever. I like to keep the
original order of the packages, hence the sorting.

-- 
 /^^^^^^^^^^^^^^^^^^^^^^^^^^^\/^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\
/ Georgi Georgiev    (-<     / Send your questions to ``ASK     \
\ chutz@chubaka.net  /\   .o)\ ZIPPY'', Box 40474, San          /
/ +81(90)6266-1163  V_/_ |(/)/ Francisco, CA 94140, USA         \
\___________________________/\__________________________________/

--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] using more than one kernel

[Amiel Martin]

oh, thanks

should ideas like this be sent here? I kind of like seeing fast response 
to ideas like this.
but I hope Im not creating undesireable noise.

-Amiel

Zach Welch wrote:

> Amiel Martin wrote:
>
>> the other thing is that if I am using two different kernels, only one 
>> can have external packages (like nvidia-kernel and emu10k1) because 
>> they get cleaned out. I dont know how this would be possible, but It 
>> would be nice to implement something like SLOT (only different 
>> because its the same ebuild) that would allow you to have two 
>> versions of the same ebuild installed.
>
>
> This is a highly desired feature that is being tracked in Bugzilla:
>
> http://bugs.gentoo.org/show_bug.cgi?id=20071
>
> Cheers,
>
> Zach Welch
> Gentoo Embedded Lead
> Superlucidity Services
>
>
> -- 
> gentoo-dev@gentoo.org mailing list



--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] using more than one kernel

[Zach Welch]

Amiel Martin wrote:
 >>
 >> This is a highly desired feature that is being tracked in Bugzilla:
 >>
 >>
 >>
 >>
 >> http://bugs.gentoo.org/show_bug.cgi?id=20071
 >
 > should ideas like this be sent here? I kind of like seeing fast
 > response to ideas like this. but I hope Im not creating undesireable
 > noise.
 >

I suppose I should have mentioned that the whole reason we don't already
have this feature is because we can't see anyway around the fact that it
will take a fairly major filesystem layout change in /var/db/.  In fact,
this feature may not arrive in Portage 2.0 and almost certainly not
before we get 1.4 out the door.

I welcome any python coders to step up to the plate to help us address
this problem (and prove my timeline estimate incorrect), as the is but
one feature in my critical path for cross-compiling integration.

Cheers,

Zach Welch
Gentoo Embedded Lead
Superlucidity Services



--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] using more than one kernel

[Peter Ruskin]

On Monday 02 Jun 2003 02:19, Georgi Georgiev wrote:
> As sometimes I am not sure what packages need reemerging, I use this
> script:
>
> for i in `grep -l ' /lib/modules/' /var/db/pkg/*/*/CONTENTS`; do
>         ii=`dirname $i`;
>         cat $ii/COUNTER; echo " $ii";
> done | sort -n | cut -f5,6 -d/ | sed -e 's/^/>=/'

Hey, I like that Georgi.

I now have:
#!/bin/sh
# /usr/local/bin/kernel-deps
# list the ebuilds that depend on kernel version.
# suggested by Georgi Georgiev <chutz@gg3.net>

for i in `grep -l ' /lib/modules/' /var/db/pkg/*/*/CONTENTS`; do
	ii=`dirname $i`;
	cat $ii/COUNTER || continue; echo " $ii";
done | sort -n | cut -f5,6 -d/ | sed -e 's/^/>=/'

I'm not sure what COUNTER does, but the "|| continue" skips files that 
don't have it.

The tail end of my build-kernel scripts now looks like this:
AUTOCLEAN="no" ACCEPT_KEYWORDS="~x86" kernel-deps | xargs emerge

...and it works a treat (getting over my misspelled "lm_sensors"

Thanks


--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] using more than one kernel

[Georgi Georgiev]

On 02/06/2003 at 12:36:36(+0100), Peter Ruskin used 1.0Kbytes just to say:
> I'm not sure what COUNTER does, but the "|| continue" skips files that 
> don't have it.

COUNTER is incremented by one for every ebuild. I like to keep the original
order... just in case. I think I even had some reason once.

> The tail end of my build-kernel scripts now looks like this:
> AUTOCLEAN="no" ACCEPT_KEYWORDS="~x86" kernel-deps | xargs emerge

probably

kernel-deps | env AUTOCLEAN=no ACCEPT_KEYWORDS="~x86" xargs emerge

would be better. I am pretty sure that AUTOCLEAN=no is not set for xargs the
way you wrote it.

-- 
 /^^^^^^^^^^^^^^^^^^^^^^^^^^^\/^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\
/ Georgi Georgiev    (-<     / Some men are so interested in    \
\ chutz@chubaka.net  /\   .o)\ their wives' continued happiness /
/ +81(90)6266-1163  V_/_ |(/)/ that they hire detectives to     \
\                   ^^^^^^^^^\ find out the reason for it.      /
 \___________________________/\________________________________/

--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] using more than one kernel

[Peter Ruskin]

On Monday 02 Jun 2003 13:03, Georgi Georgiev wrote:
> On 02/06/2003 at 12:36:36(+0100), Peter Ruskin used 1.0Kbytes just to 
say:
> > I'm not sure what COUNTER does, but the "|| continue" skips files
> > that don't have it.
>
> COUNTER is incremented by one for every ebuild. I like to keep the
> original order... just in case. I think I even had some reason once.
>
Ah, now I understand.  "|| continue" is gone.

> > The tail end of my build-kernel scripts now looks like this:
> > AUTOCLEAN="no" ACCEPT_KEYWORDS="~x86" kernel-deps | xargs emerge
>
> probably

> kernel-deps | env AUTOCLEAN=no ACCEPT_KEYWORDS="~x86" xargs emerge
>
> would be better. I am pretty sure that AUTOCLEAN=no is not set for
> xargs the way you wrote it.

Thanks...changed it.


--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] using more than one kernel

[Peter Ruskin]

On Monday 02 Jun 2003 13:03, Georgi Georgiev wrote:
> > The tail end of my build-kernel scripts now looks like this:
> > AUTOCLEAN="no" ACCEPT_KEYWORDS="~x86" kernel-deps | xargs emerge
>
> probably
>
> kernel-deps | env AUTOCLEAN=no ACCEPT_KEYWORDS="~x86" xargs emerge
>
> would be better. I am pretty sure that AUTOCLEAN=no is not set for
> xargs the way you wrote it.

AUTOCLEAN="no" is never accepted.  The only thing that works here is 
adding:
CONFIG_PROTECT="/lib/modules"
to /etc/env.d/00basic

...and this to /etc/init.d/bootmisc:
		# Ensure that /usr/src/linux points to booted kernel
		if [ "/usr/src/linux-$(uname -r)" != "$(ls -l /usr/src/linux|cut -f2 
-d\>|cut -f2,3,4 -d' ')" ]
		then
			if [ "$( file /usr/src/linux | grep 'symbolic link' )" != "" ]
			then
				rm -f /usr/src/linux
				ln -s /usr/src/linux-$(uname -r) /usr/src/linux
			fi
		fi


--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] using more than one kernel

[Troy Dack]

On Thu, 2003-06-05 at 10:36, Peter Ruskin wrote:
> On Monday 02 Jun 2003 13:03, Georgi Georgiev wrote:
> > > The tail end of my build-kernel scripts now looks like this:
> > > AUTOCLEAN="no" ACCEPT_KEYWORDS="~x86" kernel-deps | xargs emerge
> >
> > probably
> >
> > kernel-deps | env AUTOCLEAN=no ACCEPT_KEYWORDS="~x86" xargs emerge
> >
> > would be better. I am pretty sure that AUTOCLEAN=no is not set for
> > xargs the way you wrote it.
> 
> AUTOCLEAN="no" is never accepted.  The only thing that works here is 
> adding:
> CONFIG_PROTECT="/lib/modules"
> to /etc/env.d/00basic
> 
> ...and this to /etc/init.d/bootmisc:

Add this to /etc/conf.d/local.start, that way you don't have to keep
remembering to not update or merge changes with baselayout changes

> 		# Ensure that /usr/src/linux points to booted kernel
> 		if [ "/usr/src/linux-$(uname -r)" != "$(ls -l /usr/src/linux|cut -f2 
> -d\>|cut -f2,3,4 -d' ')" ]
> 		then
> 			if [ "$( file /usr/src/linux | grep 'symbolic link' )" != "" ]
> 			then
> 				rm -f /usr/src/linux
> 				ln -s /usr/src/linux-$(uname -r) /usr/src/linux
> 			fi
> 		fi
> 

and an alternative:

if [ -L /usr/src/linux ]
then
	rm -f /usr/src/linux
	ln -s /usr/src/linux-$(uname r) /usr/src/linux
fi


-- 
Troy Dack					http://linux.tkdack.com
<troy@tkdack.com>				http://webportage.sf.net

Public Key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x4D90BE3C
Key fingerprint = 1F3D 6C15 16AA 09D5 0C96  92E5 FD89 16F9 4D90 BE3C


--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] using more than one kernel

[Peter Ruskin]

On Thursday 05 Jun 2003 08:10, Troy Dack wrote:
> On Thu, 2003-06-05 at 10:36, Peter Ruskin wrote:
> > On Monday 02 Jun 2003 13:03, Georgi Georgiev wrote:
> > > > The tail end of my build-kernel scripts now looks like this:
> > > > AUTOCLEAN="no" ACCEPT_KEYWORDS="~x86" kernel-deps | xargs
> > > > emerge
> > >
> > > probably
> > >
> > > kernel-deps | env AUTOCLEAN=no ACCEPT_KEYWORDS="~x86" xargs
> > > emerge
> > >
> > > would be better. I am pretty sure that AUTOCLEAN=no is not set
> > > for xargs the way you wrote it.
> >
> > AUTOCLEAN="no" is never accepted.  The only thing that works here
> > is adding:
> > CONFIG_PROTECT="/lib/modules"
> > to /etc/env.d/00basic
> >
> > ...and this to /etc/init.d/bootmisc:
>
> Add this to /etc/conf.d/local.start, that way you don't have to keep
> remembering to not update or merge changes with baselayout changes

That's what I did first, but local starts after all the modules are 
loaded, so it's too late.
>
> > 		# Ensure that /usr/src/linux points to booted kernel
> > 		if [ "/usr/src/linux-$(uname -r)" != "$(ls -l /usr/src/linux|cut
> > -f2 -d\>|cut -f2,3,4 -d' ')" ]
> > 		then
> > 			if [ "$( file /usr/src/linux | grep 'symbolic link' )" != "" ]
> > 			then
> > 				rm -f /usr/src/linux
> > 				ln -s /usr/src/linux-$(uname -r) /usr/src/linux
> > 			fi
> > 		fi
>
> and an alternative:
>
> if [ -L /usr/src/linux ]
> then
> 	rm -f /usr/src/linux
> 	ln -s /usr/src/linux-$(uname r) /usr/src/linux
> fi

Yes, much better, thanks Troy.  I wish this would get included in 
baselayout, right after booting.

Peter


--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] using more than one kernel

[Georgi Georgiev]

On 05/06/2003 at 08:56:09(+0000), Peter Ruskin used 1.6Kbytes, just to say:
> On Thursday 05 Jun 2003 08:10, Troy Dack wrote:
> >
> > Add this to /etc/conf.d/local.start, that way you don't have to keep
> > remembering to not update or merge changes with baselayout changes
> 
> That's what I did first, but local starts after all the modules are 
> loaded, so it's too late.

It's too late for what? Do you need the kernel sources to load some modules?

Furthermore, the /lib/modules/`uname -r`/build link usually points to the full
path of the sources and not to /usr/src/linux... so I guess the modules have no
reason (even if they had one) to care where /usr/src/linux points to.

-- 
 /^^^^^^^^^^^^^^^^^^^^^^^^^^^\/^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\
/ Georgi Georgiev    (-<     / I'd rather be led to hell than   \
\ chutz@chubaka.net  /\   .o)\ managed to heavan.               /
/ +81(90)6266-1163  V_/_ |(/)/                                  \
\___________________________/\__________________________________/

--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] using more than one kernel

[Peter Ruskin]

On Thursday 05 Jun 2003 10:31, Georgi Georgiev wrote:
> > That's what I did first, but local starts after all the modules are
> > loaded, so it's too late.
>
> It's too late for what? Do you need the kernel sources to load some
> modules?
>
> Furthermore, the /lib/modules/`uname -r`/build link usually points to
> the full path of the sources and not to /usr/src/linux... so I guess
> the modules have no reason (even if they had one) to care where
> /usr/src/linux points to.

Yes, you're quite right of course.  I was getting paranoid about the 
kernel link being correct before emerging nvidia-kernel.  Making the 
link in local is OK


--
gentoo-dev@gentoo.org mailing list