John Covici wrote:
> I am trying to do something very simple, with the config file supplied
> from Debian, I need to do a make bzImage and possible a make modules,
> how can dI do this? Do I need to change the config in some way in
> order to do this?
be patient and start reading - free means
On Mon, 30 Sep 2019 16:47:29 -0400,
deloptes wrote:
>
> John Covici wrote:
>
> > Google did not give me that at all. I am not trying to build a Debian
> > package,just trying to compile the kernel.
>
> Then just do
>
> make deb-pkg
>
> You could read more about the make system used by the
John Covici wrote:
> I am doing a straight makebzImage not trying to build a deb package.
> In Debian 9, I could do this with no problem.
Obviously you are trying to build the kernel from debian source. You have to
use the original source, without the debian directory. IF there is debian
John Covici wrote:
> Google did not give me that at all. I am not trying to build a Debian
> package,just trying to compile the kernel.
Then just do
make deb-pkg
You could read more about the make system used by the kernel
https://www.kernel.org/doc/html/latest/
or in the directory
$ less
On Mon, Sep 30, 2019 at 04:20:53PM -0400, John Covici wrote:
> > On Mon, Sep 30, 2019 at 04:10:27PM -0400, John Covici wrote:
> > > So, how do I turn this off so I can compile the thing?
> >
> > "dpkg-buildpackage -b" considers it a warning and skips it.
> > At least it does so for me.
>
> I am
On Mon, 30 Sep 2019 16:05:16 -0400,
deloptes wrote:
>
> John Covici wrote:
>
> > debian/certs/debian-uefi-certs.pem
>
> https://wiki.debian.org/BuildADebianKernelPackage
>
> I hope you can read - also find a good search engine - first hit
>
>
Google did not give me that at all. I am not
On Mon, 30 Sep 2019 16:15:38 -0400,
Reco wrote:
>
> Please do not top post.
>
> On Mon, Sep 30, 2019 at 04:10:27PM -0400, John Covici wrote:
> > So, how do I turn this off so I can compile the thing?
>
> "dpkg-buildpackage -b" considers it a warning and skips it.
> At least it does so for me.
Please do not top post.
On Mon, Sep 30, 2019 at 04:10:27PM -0400, John Covici wrote:
> So, how do I turn this off so I can compile the thing?
"dpkg-buildpackage -b" considers it a warning and skips it.
At least it does so for me.
Reco
So, how do I turn this off so I can compile the thing?
On Mon, 30 Sep 2019 16:02:02 -0400,
Reco wrote:
>
> Hi.
>
> On Mon, Sep 30, 2019 at 03:46:41PM -0400, John Covici wrote:
> > Hi. I am getting an error while compiling the kernel 4.19-0-6-amd64.
> >
> > CC kernel/rseq.o
> >
John Covici wrote:
> debian/certs/debian-uefi-certs.pem
https://wiki.debian.org/BuildADebianKernelPackage
I hope you can read - also find a good search engine - first hit
On 2019-09-30 15:46 -0400, John Covici wrote:
> Hi. I am getting an error while compiling the kernel 4.19-0-6-amd64.
>
> CC kernel/rseq.o
> AR kernel/built-in.a
> make[1]: *** No rule to make target
> 'debian/certs/debian-uefi-certs.pem', needed by
>
Hi.
On Mon, Sep 30, 2019 at 03:46:41PM -0400, John Covici wrote:
> Hi. I am getting an error while compiling the kernel 4.19-0-6-amd64.
>
> CC kernel/rseq.o
> AR kernel/built-in.a
> make[1]: *** No rule to make target
> 'debian/certs/debian-uefi-certs.pem',
Hi. I am getting an error while compiling the kernel 4.19-0-6-amd64.
CC kernel/rseq.o
AR kernel/built-in.a
make[1]: *** No rule to make target
'debian/certs/debian-uefi-certs.pem', needed by
'certs/x509_certificate_list'. Stop.
What package do I need to fix this
I spoke too soon, someone in the ubuntu forums had the same problem,
installed libssl-dev and it worked.
Sorry to trouble y'all.
Curt-
On Fri, Nov 6, 2015 at 3:06 PM, Curt Howland wrote:
> So, there I was, doing a compile of the new kernel, 4.3
>
> I get the following
So, there I was, doing a compile of the new kernel, 4.3
I get the following interesting error:
===
scripts/extract-cert.c:21:25: fatal error: openssl/bio.h: No such file
or directory
#include
^
compilation terminated.
===
I'm accustomed to getting compile time
csanyi...@gmail.com writes:
Gary Dale garyd...@torfree.net writes:
On 17/01/15 10:19 AM, csanyi...@gmail.com wrote:
I have a headless powerpc box and run on it Debian Wheezy with kernel
Linux b2 3.2.62-1 #1 Mon Aug 25 04:22:40 UTC 2014 ppc GNU/Linux .
But this kernel doesn't have support
On 17/01/15 10:19 AM, csanyi...@gmail.com wrote:
Hi,
I have a headless powerpc box and run on it Debian Wheezy with kernel
Linux b2 3.2.62-1 #1 Mon Aug 25 04:22:40 UTC 2014 ppc GNU/Linux .
But this kernel doesn't have support for the rtl8192cu kernel-module.
One can to get the kernel source
Gary Dale garyd...@torfree.net writes:
On 17/01/15 10:19 AM, csanyi...@gmail.com wrote:
I have a headless powerpc box and run on it Debian Wheezy with kernel
Linux b2 3.2.62-1 #1 Mon Aug 25 04:22:40 UTC 2014 ppc GNU/Linux .
But this kernel doesn't have support for the rtl8192cu
Hi,
I have a headless powerpc box and run on it Debian Wheezy with kernel
Linux b2 3.2.62-1 #1 Mon Aug 25 04:22:40 UTC 2014 ppc GNU/Linux .
But this kernel doesn't have support for the rtl8192cu kernel-module.
One can to get the kernel source from here:
The same problem, with kernel 3.10, was present
with Wheezy 486 on same computer.
Thanks
Regards
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
The same problem, with kernel 3.10, was present
with Wheezy 486 on same computer.
Thanks
Regards
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
Hi all
I try compiling kernel 3.10 on Squeeze 6.0.7. with cpu
Intel Centrino1 32bit.
Unpack source in /usr/src, and:
adduser user src
chown -R root:src /usr/src
chmod -R g+w /usr/src
cp /boot/config-`uname -r` ./.config
make menuconfig, but don't change any!
make deb-pkg
After
On Wed, 06 Nov 2013 15:07:58 -0500 (EST), Antispammbox-debian wrote:
Hi all
I try compiling kernel 3.10 on Squeeze 6.0.7. with cpu
Intel Centrino1 32bit.
Unpack source in /usr/src, and:
adduser user src
chown -R root:src /usr/src
chmod -R g+w /usr/src
cp /boot/config-`uname -r
Sorry, my mistake, nothing about 64 bit. I compiled the 32bit kernel in xfs.
On Tue, Jun 29, 2010 at 9:17 AM, Magicloud Magiclouds
magicloud.magiclo...@gmail.com wrote:
I am using debian unstable 64 bit with lvm and ext3. All options are default.
How did I find out? This OS is a VM. And the
On Lu, 28 iun 10, 10:51:02, Magicloud Magiclouds wrote:
PS: Certainly this is not my real name. 8-) I am not from an English
country. Some people cannot pronounce my name right. So I use this
pseudonym.
That doesn't stop me from using my real name ;)
Regards,
Andrei
--
Offtopic discussions
On Monday 28 June 2010 08:44:15 Andrei Popescu wrote:
On Lu, 28 iun 10, 10:51:02, Magicloud Magiclouds wrote:
PS: Certainly this is not my real name. 8-) I am not from an English
country. Some people cannot pronounce my name right. So I use this
pseudonym.
That doesn't stop me from using
On Mon, Jun 28, 2010 at 10:44:15AM +0300, Andrei Popescu wrote:
On Lu, 28 iun 10, 10:51:02, Magicloud Magiclouds wrote:
PS: Certainly this is not my real name. 8-) I am not from an English
country. Some people cannot pronounce my name right. So I use this
pseudonym.
That doesn't stop
Op 28-06-10 13:12, Tzafrir Cohen schreef:
On Mon, Jun 28, 2010 at 10:44:15AM +0300, Andrei Popescu wrote:
On Lu, 28 iun 10, 10:51:02, Magicloud Magiclouds wrote:
PS: Certainly this is not my real name. 8-) I am not from an English
country. Some people cannot pronounce my name right. So I
On Mon, 28 Jun 2010 07:20:05 -0400 (EDT), Sjoerd Hardeman wrote:
Op 28-06-10 13:12, Tzafrir Cohen schreef:
On Mon, Jun 28, 2010 at 10:44:15AM +0300, Andrei Popescu wrote:
On Lu, 28 iun 10, 10:51:02, Magicloud Magiclouds wrote:
PS: Certainly this is not my real name. 8-) I am not from an
On Monday 28 June 2010 12:12:23 Tzafrir Cohen wrote:
So I guess we're still looking for an example of a non-English name
that can't be pronounced right. Can't think of any.
It isn't a case of whether it can be correctly pronounced, but of whether it
is.
Lisi
--
To UNSUBSCRIBE, email to
On 27/06/10 10:51 PM, Magicloud Magiclouds wrote:
Thank you guys.
I have not follow Stephen's guide, but I figured the reason out. It
seems like an ext3's fault. The space (i-node wise) was used 5.x GB,
but the actual space (data wise) was used only 1 GB. So a lot of space
was just empty and
I am using debian unstable 64 bit with lvm and ext3. All options are default.
How did I find out? This OS is a VM. And the disk data is in a
non-fixed size file, not compressed. Sorry I forgot how to say this in
English, by non-fixed size, I mean the VM software just allocate the
actual disk space
Thank you guys.
I have not follow Stephen's guide, but I figured the reason out. It
seems like an ext3's fault. The space (i-node wise) was used 5.x GB,
but the actual space (data wise) was used only 1 GB. So a lot of space
was just empty and wasted.
I attached another disk to get the job done.
Hi,
I am using debian unstable 64. Recently I wanted to compile a 2.6.34 kernel.
Well, the source package is 64MB. Before `make-kpkg linux-image
linux-headers --initrd` finished, the source directory took 6GB space,
made the volume full.
Tried a few times, the problem is still there, and
On Fri, Jun 25, 2010 at 18:25, Magicloud Magiclouds
magicloud.magiclo...@gmail.com wrote:
Hi,
I am using debian unstable 64. Recently I wanted to compile a 2.6.34
kernel.
Well, the source package is 64MB. Before `make-kpkg linux-image
linux-headers --initrd` finished, the source directory
On Fri, 25 Jun 2010 08:55:41 -0400 (EDT), Magicloud Magiclouds wrote:
I am using debian unstable 64. Recently I wanted to compile a 2.6.34 kernel.
Well, the source package is 64MB. Before `make-kpkg linux-image
linux-headers --initrd` finished, the source directory took 6GB space,
made the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 06/25/2010 09:10 AM, Stephen Powell wrote:
Magicloud Magiclouds? That can't be your real name!
Can't you give us your real name? At least a first name?
That is not the correct command syntax. I suggest that you read
On Fri, 25 Jun 2010 09:34:29 -0400 (EDT), Jordan Metzmeier wrote:
On 06/25/2010 09:10 AM, Stephen Powell wrote:
That is not the correct command syntax. I suggest that you read
http://www.wowway.com/~zlinuxman/Kernel.htm
Kernel building in Debian is a complex task fraught with many
Hello
I have a doubt about kernel compilation. Two days ago I compiled by hand
2.6.31.6 and it crashed during the boot process. The configuration was
made by hand, starting from the default configuration and perhaps I missed
something.
Since I had to restore my old slackware bakcup to recover
On Sat, Dec 05, 2009 at 06:59:48AM -0700, deb...@toursbymexico.com wrote:
I have a doubt about kernel compilation. Two days ago I compiled by hand
2.6.31.6 and it crashed during the boot process. The configuration was
made by hand, starting from the default configuration and perhaps I missed
Kumar Appaiah wrote:
On Sat, Dec 05, 2009 at 06:59:48AM -0700, deb...@toursbymexico.com wrote:
I have a doubt about kernel compilation. Two days ago I compiled by hand
2.6.31.6 and it crashed during the boot process. The configuration was
made by hand, starting from the default configuration
On Sat, Dec 05, 2009 at 11:11:08AM -0500, Dave Witbrodt wrote:
Yes. In addition, I would highly recommend using kernel-package to
compile your kernel to generate a deb. Here's a nice primer:
http://newbiedoc.sourceforge.net/system/kernel-pkg.html
I would recommend using the 'make-kpkg'
I am getting some problems while compiling kernel 2.6.31 using Debian Lenny
make-kpkg
The messages are -
make[3]: Entering directory `/root/linux-2.6.31'
CHK include/linux/version.h
CHK include/linux/utsrelease.h
SYMLINK include/asm - include/asm-x86
CALLscripts
On 29.10.09 1311 (+0530), surreal wrote:
I am getting some problems while compiling kernel 2.6.31 using Debian Lenny
make-kpkg
The messages are -
make[3]: Entering directory `/root/linux-2.6.31'
CHK include/linux/version.h
CHK include/linux/utsrelease.h
SYMLINK include/asm
[snip]
Regarde du côté de make deb-pkg sinon. Make-kpkg est déprécié, il faut
maintenant utilisé make deb-pkg [1]
[1] http://lists.debian.org/debian-devel-announce/2009/10/msg3.html
Thomas Preud'homme
Salut,
petit question à propos de ce make deb-pkg :
je compile depuis qqs
Le mercredi 21 octobre 2009 09:30:06, mess-mate a écrit :
Bonjour,
j'ai un petit problème pour compiler mon noau:
voici le message d'erreur:
make-kpkg --initrd --append-to-version=-amd64-mm kernel-image
kernel-headers kernel-doc
exec make kpkg_version=12.021 -f
Bonsoir,
Le jeudi 22 octobre 2009 22:04:12, Thomas Preud'homme a écrit :
Regarde du côté de make deb-pkg sinon. Make-kpkg est déprécié, il faut
maintenant utilisé make deb-pkg [1]
[1] http://lists.debian.org/debian-devel-announce/2009/10/msg3.html
Merci pour cette info. Pour voir, j'ai
Le jeudi 22 octobre 2009 22:35:47, Jean-Damien Durand a écrit :
Bonsoir,
Le jeudi 22 octobre 2009 22:04:12, Thomas Preud'homme a écrit :
Regarde du côté de make deb-pkg sinon. Make-kpkg est déprécié, il faut
maintenant utilisé make deb-pkg [1]
[1]
Le jeudi 22 octobre 2009 23:40:50, Thomas Preud'homme a écrit :
Le jeudi 22 octobre 2009 22:35:47, Jean-Damien Durand a écrit :
Bonsoir,
Le jeudi 22 octobre 2009 22:04:12, Thomas Preud'homme a écrit :
Regarde du côté de make deb-pkg sinon. Make-kpkg est déprécié, il faut
maintenant
Bonjour,
j'ai un petit problème pour compiler mon noau:
voici le message d'erreur:
make-kpkg --initrd --append-to-version=-amd64-mm kernel-image
kernel-headers kernel-doc
exec make kpkg_version=12.021 -f
/usr/share/kernel-package/ruleset/minimal.mk debian
APPEND_TO_VERSION=-amd64-mm
Le 21-10-2009, à 09:30:06 +0200, mess-mate (mess-m...@orange.fr) a écrit :
Bonjour,
Salut,
j'ai un petit problème pour compiler mon noau:
voici le message d'erreur:
make-kpkg --initrd --append-to-version=-amd64-mm kernel-image
kernel-headers kernel-doc
exec make kpkg_version=12.021 -f
Salut,
mess-mate a écrit :
j'ai un petit problème pour compiler mon noau:
voici le message d'erreur:
make-kpkg --initrd --append-to-version=-amd64-mm kernel-image
kernel-headers kernel-doc
exec make kpkg_version=12.021 -f
/usr/share/kernel-package/ruleset/minimal.mk debian
Pascal Hambourg wrote:
Salut,
mess-mate a écrit :
j'ai un petit problème pour compiler mon noau:
voici le message d'erreur:
make-kpkg --initrd --append-to-version=-amd64-mm kernel-image
kernel-headers kernel-doc
exec make kpkg_version=12.021 -f
On Tue, 25 Aug 2009 00:50:10 +0200, Bernard wrote:
- snip --
The initrd.img that I have on my working system, as well as those
initrd.img that 'mkinitrd' generates when requested, are not compressed
files. Filenames are : initrd.img-2.6.20-16-386 for instance. No .gz
behind. I still
Amax wrote:
On Tue, 25 Aug 2009 00:50:10 +0200, Bernard wrote:
- snip --
The initrd.img that I have on my working system, as well as those
initrd.img that 'mkinitrd' generates when requested, are not compressed
files. Filenames are : initrd.img-2.6.20-16-386 for instance. No .gz
Bernard wrote:
You really could use the recent 2.6.30.4. There were different problems
with 2.6.20 to 2.6.30. I find 2.6.30.4 the best I've had since 2.6.20.
I tried 2.6.30.4. Same result as with 2.6.26.2 : compiles without
errors, but crashes on boot.
so you are missing some essential
Emanoil Kotsev wrote:
Bernard wrote:
Emanoil Kotsev wrote:
Bernard wrote:
Compiling md in the kernel is the right approach to boot from raided root
without initrd. You can try this just skipping (deleteing the line in grub
temporary)
I just tried that. Raid compiled
Emanoil Kotsev wrote:
Bernard wrote:
Compiling md in the kernel is the right approach to boot from raided root
without initrd. You can try this just skipping (deleteing the line in grub
temporary)
I just tried that. Raid compiled into the kernel instead of modules. No
initrd. Still
Bernard wrote:
Emanoil Kotsev wrote:
Bernard wrote:
Compiling md in the kernel is the right approach to boot from raided root
without initrd. You can try this just skipping (deleteing the line in grub
temporary)
I just tried that. Raid compiled into the kernel instead of modules. No
Emanoil Kotsev wrote:
Emanoil Kotsev wrote:
Sorry forgot to write
Yes there is problem compiling the 2.6.20 with recent gcc
The problem is the compiler. If you are compiling just grab the last
version from kernel.org.
2.6.30.4 seems to be working fine
Just to be objective the
Bernard wrote:
2.6.30.4 does compile all right, so does 2.6.26, but 2.6.20 does not.
you find out why in the archives
Problem is that I still can't boot those I compiled, i.e. 2.6.26. because
the initrd.img is buggy. I did find something, still it is not enough to
get the process to work.
Hi to Everyone,
I need to re-compile my kernel so that it does not include sound support
inside. I am running Debian 3.1 (Sarge). My system is on RAID1. My /boot
partition is from /dev/sda1 (mirror on /dev/sdb1) installed on /dev/md0
(ext3), while my '/' partition is from /dev/sda2 and
Bernard wrote:
Hi to Everyone,
I need to re-compile my kernel so that it does not include sound support
inside. I am running Debian 3.1 (Sarge). My system is on RAID1. My /boot
partition is from /dev/sda1 (mirror on /dev/sdb1) installed on /dev/md0
(ext3), while my '/' partition is from
Sorry forgot to write
Yes there is problem compiling the 2.6.20 with recent gcc
The problem is the compiler. If you are compiling just grab the last version
from kernel.org.
2.6.30.4 seems to be working fine
So, upon my failures to recompile kernel 2.6.20-16-386, I tried
downloading
Emanoil Kotsev wrote:
Sorry forgot to write
Yes there is problem compiling the 2.6.20 with recent gcc
The problem is the compiler. If you are compiling just grab the last
version from kernel.org.
2.6.30.4 seems to be working fine
Just to be objective the gnu compiler people said
Emanoil Kotsev wrote:
Bernard wrote:
why not just compile it on your notebook (or copy a compiled kernel) ?!
you also can just disable the loading of the sound modules to make it more
simple.
Things would be easy if all sound support were in modules. But some
functions are
Emanoil Kotsev wrote:
do you have a not raid boot partition, where you can put the initrd image?
My boot partition is not raid, or, at least, even though it is mirrored,
it remains in ext2fs, while the rest is in LVM2. So, the initrd image
that I am trying is available at
Emanoil Kotsev wrote:
try compiling the necessary modules _in_ the kernel.
This is the way it has been done.
So, I re-tried compiling after de-activating raid0 in the config,
leaving only raid1... to the same end result.
In the config it should be [*] not [M] if booting
Bernard wrote:
Emanoil Kotsev wrote:
Bernard wrote:
why not just compile it on your notebook (or copy a compiled kernel) ?!
you also can just disable the loading of the sound modules to make it more
simple.
Things would be easy if all sound support were in modules. But some
From: news [mailto:n...@ger.gmane.org] On Behalf Of Emanoil Kotsev
Sent: Friday, August 21, 2009 1:55 PM
Bernard wrote:
Emanoil Kotsev wrote:
Bernard wrote:
why not just compile it on your notebook (or copy a compiled kernel)
?!
you also can just disable the loading of
Hi all,
My box is on debian/testing, and I have compiled kernel by the debian
way. Because it's testing and kernel-patches are often provided, I
wonder whether I have to compile the kernel again after retrieving a
kernel patch or even a new kernel via aptitude full-upgrade operation.
Thanks for
On Tue, 08 May 2007 17:29:38 -0500
Manoj Srivastava [EMAIL PROTECTED] wrote:
On Tue, 8 May 2007 16:11:54 -0400, Celejar [EMAIL PROTECTED] said:
On Tue, 08 May 2007 12:47:28 -0500
Manoj Srivastava [EMAIL PROTECTED] wrote:
On Tue, 8 May 2007 16:10:29 +0200, Raffaele Morelli
[EMAIL
On Wed, 9 May 2007 15:32:08 -0400, Celejar [EMAIL PROTECTED] said:
On Tue, 08 May 2007 17:29:38 -0500
Manoj Srivastava [EMAIL PROTECTED] wrote:
Hmm. I should amend that to say: Step 5 does require (fake)root
privileges.
Huh? Here's a longer excerpt:
Oops. I think I
pizzapie_linuxanchovies wrote:
I was following a tutorial
(http://newbiedoc.sourceforge.net/system/kernel-pkg.html) for compiling
a custom kernel, and got to the stage where it said to run this:
fakeroot make-kpkg clean
However, this command generated a bunch of errors saying this:
I just changed:
1. Processor type and features - Paravirtualization support
(EXPERIMENTAL) OFF
2. Processor type and features - Timer frequency (1000 HZ)
3. Processor type and features - Preemption Model (Preemptible Kernel
(Low-Latency Desktop))
4. Device Drivers - Graphics support - Logo
Raffaele Morelli wrote:
I just changed:
1. Processor type and features - Paravirtualization support
(EXPERIMENTAL) OFF
2. Processor type and features - Timer frequency (1000 HZ)
3. Processor type and features - Preemption Model (Preemptible Kernel
(Low-Latency Desktop))
On Tue, 8 May 2007 12:12:22 +0200
Raffaele Morelli [EMAIL PROTECTED] wrote:
[snip]
Me too compile kernels as root and really would like to know why it is
considered such a bad habit.
It's generally considered a bad idea to do anything as root unless it's
absolutely necessary. I suppose it's
2007/5/8, Celejar [EMAIL PROTECTED]:
On Tue, 8 May 2007 12:12:22 +0200
Raffaele Morelli [EMAIL PROTECTED] wrote:
[snip]
Me too compile kernels as root and really would like to know why it is
considered such a bad habit.
It's generally considered a bad idea to do anything as root unless
On Tue, 8 May 2007 16:10:29 +0200, Raffaele Morelli
[EMAIL PROTECTED] said:
That's ok, I follow the general (healthy) rule and do not log as root
if unnecessary, but for kernel (and program) compile I can not picture
'make-kpkg' or 'configure make' doing something regrettable.
On Tue, May 08, 2007 at 04:10:29PM +0200, Raffaele Morelli wrote:
2007/5/8, Celejar [EMAIL PROTECTED]:
On Tue, 8 May 2007 12:12:22 +0200
Raffaele Morelli [EMAIL PROTECTED] wrote:
[snip]
Me too compile kernels as root and really would like to know why it is
considered such a bad
Thanks to everyone who replied with ideas about my post. Let me give quick
replies to the questions you asked me:
Manoj--yes, dpkg is in /usr/bin, and is in the user's path, but no normal user
has execute access to dpkg:
$ ls -l /usr/bin/dpkg
-rwxr-x--- 1 root root 174040 May 26 2005
On Tue, 08 May 2007 12:47:28 -0500
Manoj Srivastava [EMAIL PROTECTED] wrote:
On Tue, 8 May 2007 16:10:29 +0200, Raffaele Morelli
[EMAIL PROTECTED] said:
That's ok, I follow the general (healthy) rule and do not log as root
if unnecessary, but for kernel (and program) compile I can not
On Tue, May 08, 2007 at 08:50:13PM +0200, pizzapie_linuxanchovies wrote:
Andrew (and anyone else who can do a make-kpkg under a non-root
account)--what permissions do YOU see when you say ls -l /usr/bin/root?
I was referring to the general case of compiling source as a user and
installing
On Tue, 8 May 2007 20:50:13 +0200 (CEST), pizzapie linuxanchovies [EMAIL
PROTECTED] said:
Thanks to everyone who replied with ideas about my post. Let me give
quick replies to the questions you asked me:
Manoj--yes, dpkg is in /usr/bin, and is in the user's path, but no
normal user has
On Tue, 8 May 2007 16:11:54 -0400, Celejar [EMAIL PROTECTED] said:
On Tue, 08 May 2007 12:47:28 -0500
Manoj Srivastava [EMAIL PROTECTED] wrote:
On Tue, 8 May 2007 16:10:29 +0200, Raffaele Morelli
[EMAIL PROTECTED] said:
That's ok, I follow the general (healthy) rule and do not log as
I was following a tutorial (http://newbiedoc.sourceforge.net/system/kernel-pkg.html) for
compiling a custom kernel, and got to the stage where it said to run this: fakeroot
make-kpkg clean
However, this command generated a bunch of errors saying this:
dpkg-architecture: failure: dpkg
On Tue, 8 May 2007 05:37:58 +0200 (CEST), pizzapie linuxanchovies
[EMAIL PROTECTED] said:
I was following a tutorial
(http://newbiedoc.sourceforge.net/system/kernel-pkg.html) for
compiling a custom kernel, and got to the stage where it said to run
this: fakeroot make-kpkg clean However,
pizzapie_linuxanchovies [EMAIL PROTECTED] writes:
I was following a tutorial
(http://newbiedoc.sourceforge.net/system/kernel-pkg.html) for
compiling a custom kernel, and got to the stage where it said to run
this: fakeroot make-kpkg clean
However, this command generated a bunch of errors
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, Aug 15, 2006 at 01:23:20PM -0700, shahim essaid.com wrote:
Hi all,
I am somewhat new to Debian and Iam not sure if this is possible. I want to
compile a 2.6.16 from source but the minimum requirement listed under
Documentation/Changes
Hi everyone!
I'm trying to upgrade my 2.6.14.2 kernel in my server to a 2.6.17.4 or
higher using my current .config. There isn't any problem in compiling
time and in grub i put the same config but with different vmlinuz
file, but when i reboot i get a kernel panic error like that Kernel
panic:
shahim essaid.com wrote:
Hi all,
I am somewhat new to Debian and Iam not sure if this is possible. I want
to compile a 2.6.16 from source but the minimum requirement listed under
Documentation/Changes are not satisfied under Sarge. udev, for example,
has to be 071 or higher.
I've never
Mario de Frutos wrote:
I'm trying to upgrade my 2.6.14.2 kernel in my server to a 2.6.17.4 or
higher using my current .config. There isn't any problem in compiling
time and in grub i put the same config but with different vmlinuz
file, but when i reboot i get a kernel panic error like that
Hi all,
I am somewhat new to Debian and Iam not sure if this is possible. I want
to compile a 2.6.16 from source but the minimum requirement listed under
Documentation/Changes are not satisfied under Sarge. udev, for example,
has to be 071 or higher.
I did try backports.org but there were
Hello everybody. I am trying to install anbd on a PIII cluster, and for
that I have to compile the module that they provide. But unfortunately,
I am not being capable of compile this module agaist the
kernel-headers-2.6.8-2-686-smp. make menuconfig works nicely, but when I
try to make or make
On Sat, Nov 26, 2005 at 12:51:55AM -0500, Amish Rughoonundon wrote:
lemme see if I understand what you meant: The kernel-source files that I
downloaded is common to all linux distribution while the kernel-header
files is particular to a certain version and distribution.
...not so much the
Hi,
I have been trying to compile and insert a simple
kernel module but without luck. This is what I did.
Since the freshly installed debian sarge 3.1 distro
did not have any source files under /usr/src, I di uname -a to make sure of the
kernel version that is installed:
Linux test
On Fri, Nov 25, 2005 at 05:36:26PM -0500, Amish Rughoonundon wrote:
Hi,
I have been trying to compile and insert a simple kernel module but
without luck. This is what I did.
Since the freshly installed debian sarge 3.1 distro did not have any
source files under /usr/src, I di uname -a to make
me out,
Amish
- Original Message -
From: Almut Behrens [EMAIL PROTECTED]
To: debian-user@lists.debian.org
Sent: Friday, November 25, 2005 9:43 PM
Subject: Re: compiling kernel module question
On Fri, Nov 25, 2005 at 05:36:26PM -0500, Amish Rughoonundon wrote:
Hi,
I have been trying
On 9/22/05, Ritesh Raj Sarraf [EMAIL PROTECTED] wrote:
-BEGIN PGP SIGNED MESSAGE-Hash: SHA1L.V.Gandhi on Monday 19 Sep 2005 12:46 wrote: I have found the problem with debian apt-get kernel which contains debian patches.Debian shipped kernels don't come with with bootsplash patch included.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
L.V.Gandhi on Monday 19 Sep 2005 12:46 wrote:
On 9/17/05, Kumar Appaiah [EMAIL PROTECTED] wrote:
I don't know whether this is a stupid doubt, but are you using
`pristine' kernel sources or Debian patched kernel sources (apt-got
ones)? I
1 - 100 of 513 matches
Mail list logo