kernel-source-2.6.0-test1?

[Travis Crump]

Where can I find the source used to build kernel-image-2.6.0-test1-i386?
kernel-source-2.6.0-test1 doesn't exist as far as I can determine[and
apt-get source kernel-source-2.6.0-test1-i386 and/or apt-get build-dep
kernel-source-2.6.0-test1 suggest that is where the source should be and
is in line with past practice]. Am I just supposed to assume that the
source is identical to upstream?

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - [url]http://enigmail.mozdev.org[/url]

iD8DBQE/LWHWlxHEcbyY0skRAp1zAJ4vmn97DPAsqCLDp8SllI9jEx0wHQ CfVPIu
X3b7pkctJBSICg8vsRJQK8Q=
=lQi1
-----END PGP SIGNATURE-----

[ramzez@netcourrier.com]

Le Dimanche 3 Août 2003 21:26, Travis Crump a écrit :

> Where can I find the source used to build kernel-image-2.6.0-test1-i386?
> kernel-source-2.6.0-test1 doesn't exist as far as I can determine[and
> apt-get source kernel-source-2.6.0-test1-i386 and/or apt-get build-dep
> kernel-source-2.6.0-test1 suggest that is where the source should be and
> is in line with past practice]. Am I just supposed to assume that the
> source is identical to upstream?

Yes, you can use the upstream and put the files found in the source package in the kernel source tree. So you can thus use make-kpkg.
The config file used by debian kernel image package can be found in the source package

-------------------------------------------------------------
NetCourrier, votre bureau virtuel sur Internet : Mail, Agenda, Clubs, Toolbar...
Web/Wap : [url]www.netcourrier.com[/url]
Téléphone/Fax : 08 92 69 00 21 (0,34 € TTC/min)
Minitel: 3615 NETCOURRIER (0,15 € TTC/min)


--
To UNSUBSCRIBE, email to [email]debian-user-request@lists.debian.org[/email]
with a subject of "unsubscribe". Trouble? Contact [email]listmaster@lists.debian.org[/email]

[Micha Feigin]

On Sun, 2003-08-03 at 22:26, Travis Crump wrote:

> Where can I find the source used to build kernel-image-2.6.0-test1-i386?
> kernel-source-2.6.0-test1 doesn't exist as far as I can determine[and
> apt-get source kernel-source-2.6.0-test1-i386 and/or apt-get build-dep
> kernel-source-2.6.0-test1 suggest that is where the source should be and
> is in line with past practice]. Am I just supposed to assume that the
> source is identical to upstream?
>

You can find the source under [url]www.kernel.org[/url]. I don't think that there
is a debian package for it yet (it can build a debian package using
make-kpkg though).


--
To UNSUBSCRIBE, email to [email]debian-user-request@lists.debian.org[/email]
with a subject of "unsubscribe". Trouble? Contact [email]listmaster@lists.debian.org[/email]

[Eduard Bloch]

#include <hallo.h>
* Travis Crump [Sun, Aug 03 2003, 03:26:07PM]:

> Where can I find the source used to build kernel-image-2.6.0-test1-i386?

apt-get source kernel-image-2.6.0-test1-i386
apt-get build-dep kernel-image-2.6.0-test1-i386

MfG,
Eduard.
--
Labello und kein Kuß quietscht mehr.


--
To UNSUBSCRIBE, email to [email]debian-user-request@lists.debian.org[/email]
with a subject of "unsubscribe". Trouble? Contact [email]listmaster@lists.debian.org[/email]

[François Chenais]

Hello,

Is this working with test2 flavour ??

François

On Sun, 3 Aug 2003 21:46:22 CEST
[email]ramzez@netcourrier.com[/email] wrote:

> Le Dimanche 3 Août 2003 21:26, Travis Crump a écrit :

> > Where can I find the source used to build kernel-image-2.6.0-test1-i386?
> > kernel-source-2.6.0-test1 doesn't exist as far as I can determine[and
> > apt-get source kernel-source-2.6.0-test1-i386 and/or apt-get build-dep
> > kernel-source-2.6.0-test1 suggest that is where the source should be and
> > is in line with past practice]. Am I just supposed to assume that the
> > source is identical to upstream?

>
>
> Yes, you can use the upstream and put the files found in the source package in the kernel source tree. So you can thus use make-kpkg.
> The config file used by debian kernel image package can be found in the source package
>
> -------------------------------------------------------------
> NetCourrier, votre bureau virtuel sur Internet : Mail, Agenda, Clubs, Toolbar...
> Web/Wap : [url]www.netcourrier.com[/url]
> Téléphone/Fax : 08 92 69 00 21 (0,34 _ TTC/min)
> Minitel: 3615 NETCOURRIER (0,15 _ TTC/min)
>
>
> --
> To UNSUBSCRIBE, email to [email]debian-user-request@lists.debian.org[/email]
> with a subject of "unsubscribe". Trouble? Contact [email]listmaster@lists.debian..org[/email]
>
>

--
Debian SID
Linux tanna 2.4.20-freeswan-ipvs-xfs #7 SMP Tue Feb 11 11:01:05 CET 2003 i686 unknown unknown GNU/Linux
Linux Counter #59413
PGP fingerprint : 9AFA 15EC 96C9 F607 EBC1 DD41 70C5 F0E0 25A5 105B

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQE/LlMLcMXw4CWlEFsRAn+7AJ0WR21soIhC4JZg31i7+aAdjMtZgQ CdF9oi
jf+nCIYGm9KYxi6Bdy7M3Yw=
=cKKo
-----END PGP SIGNATURE-----

[Marino Fernandez]

On Monday 04 August 2003 8:57 am, François Chenais wrote:

> doesn't work :-|
>
>
>
> tanna:~/tmp/kernel-image-2.6.0-test1-i386-2.6.0-test1# apt-get build-dep
> kernel-image-2.6.0-test1-i386 Reading Package Lists... Done
> Building Dependency Tree... Done
> E: Build-Depends dependency for kernel-image-2.6.0-test1-i386 cannot be
> satisfied because the package kernel-source-2.6.0-test1 cannot be found
>
>

I cannot help you with the debian way... that I found more complex than the
regular way.

Download a pristine kernel (get 2.6.0-test2)
cd /usr/src
Untar kernel in /usr/src
mv linux linux~
ln -s linux-2.6.0-test2 linux
make menuconfig or make xconfig
make
make modules_install
Put bzimage in /boot, rename it vmlinuz-2.6.0-test2
Update lilo or grub
reboot

PS
I assume you have the proper entries in fstab (for sysfs) and the new package
to handle modules (if not to this last one do apt-get instal
modules-init-tools)

PPS
Check and post your questions to the kernel mailing list... you are more
likely to get help there.


--
To UNSUBSCRIBE, email to [email]debian-user-request@lists.debian.org[/email]
with a subject of "unsubscribe". Trouble? Contact [email]listmaster@lists.debian.org[/email]

[Noah L. Meyerhans]

On Mon, Aug 04, 2003 at 03:29:51PM -0500, Marino Fernandez wrote:

> I cannot help you with the debian way... that I found more complex than the
> regular way.
>
> Download a pristine kernel (get 2.6.0-test2)
> cd /usr/src
> Untar kernel in /usr/src
> mv linux linux~
> ln -s linux-2.6.0-test2 linux
> make menuconfig or make xconfig
> make
> make modules_install
> Put bzimage in /boot, rename it vmlinuz-2.6.0-test2
> Update lilo or grub
> reboot

Please tell me how that is less complex than

$ cd <kernel source dir>
$ fakeroot make-kpkg --config menu kernel_image
$ sudo dpkg -i ../kernel-image-<whatever the version was>.deb
$ sudo reboot

I just don't get it.

noah


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see [url]http://www.gnupg.org[/url]

iD8DBQE/LsVwYrVLjBFATsMRAjaaAJ9+qVNWx5OkoM+E/spEMW59GPO6KgCgiBXA
IX23MzX9rQOG6DWF+cn/lOE=
=+zjF
-----END PGP SIGNATURE-----

[Rich Puhek]

Noah L. Meyerhans wrote:

> On Mon, Aug 04, 2003 at 03:29:51PM -0500, Marino Fernandez wrote:
>

>>I cannot help you with the debian way... that I found more complex than the
>>regular way.
>>
>>Download a pristine kernel (get 2.6.0-test2)
>>cd /usr/src
>>Untar kernel in /usr/src
>>mv linux linux~
>>ln -s linux-2.6.0-test2 linux
>>make menuconfig or make xconfig
>>make
>>make modules_install
>>Put bzimage in /boot, rename it vmlinuz-2.6.0-test2
>>Update lilo or grub
>>reboot

>
>
> Please tell me how that is less complex than
>
> $ cd <kernel source dir>
> $ fakeroot make-kpkg --config menu kernel_image
> $ sudo dpkg -i ../kernel-image-<whatever the version was>.deb
> $ sudo reboot
>
> I just don't get it.
>
> noah
>

Plus, the Debian way is much easier, IMHO, for compiling on one machine,
and installing on another. This is useful in cases where you:

1) Don't want to bog down a machine with compiling a kernel (I like to
compile during the day when I'm awake enough to be sure I caught
everything... people get mad at me if all the RAM disappears on my
spamassassin server, or if I steal all the CPU cycles on my MySQL server).

2) Don't want to put gcc et. al. on a machine (for security or space
concerns).

3) Have more than one machine with the same hardware, etc. If only one
kernel config is required, why recompile 10 times (or compile once, copy
bzImage to all the machines, copy the modules ot all the machines,
reboot, discover you forgot system.map on one, and forgot to run LILO on
three machines).

Very handy to compile on one machine, scp kernal_image.servername.1
servername:/usr/local/src and dpkg -i the image...

--Rich

__________________________________________________ _______

Rich Puhek
ETN Systems Inc.
2125 1st Ave East
Hibbing MN 55746

tel: 218.262.1130
email: [email]rpuhek@etnsystems.com[/email]
__________________________________________________ _______


--
To UNSUBSCRIBE, email to [email]debian-user-request@lists.debian.org[/email]
with a subject of "unsubscribe". Trouble? Contact [email]listmaster@lists.debian.org[/email]

[Marino Fernandez]

On Monday 04 August 2003 3:43 pm, Noah L. Meyerhans wrote:

> On Mon, Aug 04, 2003 at 03:29:51PM -0500, Marino Fernandez wrote:

> > I cannot help you with the debian way... that I found more complex than
> > the regular way.
> >
> > Download a pristine kernel (get 2.6.0-test2)
> > cd /usr/src
> > Untar kernel in /usr/src
> > mv linux linux~
> > ln -s linux-2.6.0-test2 linux
> > make menuconfig or make xconfig
> > make
> > make modules_install
> > Put bzimage in /boot, rename it vmlinuz-2.6.0-test2
> > Update lilo or grub
> > reboot

>
> Please tell me how that is less complex than
>
> $ cd <kernel source dir>
> $ fakeroot make-kpkg --config menu kernel_image
> $ sudo dpkg -i ../kernel-image-<whatever the version was>.deb
> $ sudo reboot
>
> I just don't get it.
>

This discussion if kind of pointless. I've done it both ways, both work,
but...

It is more lines the stardard way, I give you that. But it is trivial since
most of the time you spend recompiling your kernel is spent... well,
compiling.

And then you just have to cut an paste the kernel to wherever it goes, and
deal with the boot loader, as oposed to installing a large package, ... In my
case I feel that it takes longer if I do it "the debian way", and also you
loose track of whats going on.

In conclussion, I think "the standard way" as opposed to "the debian way"
gives you a clear idea of whats going on, more control over the process, as
opposed to the "click'n go" approach that debian uses. But Rich is right...
if you have to install 10 kernels on 10 different machines, having a nice
package you can just click on and forget about it is more efficient. I am
just talking from the perspective of the end user with a couple of
machines... I guess I should have stated that from the begining.


--
To UNSUBSCRIBE, email to [email]debian-user-request@lists.debian.org[/email]
with a subject of "unsubscribe". Trouble? Contact [email]listmaster@lists.debian.org[/email]

[Marino Fernandez]

On Monday 04 August 2003 4:20 pm, Rich Puhek wrote:

>
> Very handy to compile on one machine, scp kernal_image.servername.1
> servername:/usr/local/src and dpkg -i the image...
>

There is no doubt about the advantages of compiling in one machine for many...
but if you only have one, then I do not see the point.

Also see my previous post


--
To UNSUBSCRIBE, email to [email]debian-user-request@lists.debian.org[/email]
with a subject of "unsubscribe". Trouble? Contact [email]listmaster@lists.debian.org[/email]