On Mon, 2005-10-31 at 07:53 +0100, Lionel Elie Mamane wrote:
On Mon, Oct 31, 2005 at 02:23:06AM +0200, Aaron wrote:
fakeroot make-kpkg --append-to-version -vanilla --revision 0.1
kernel_image
Tzafrir mentioned: make-kpkg --rootcmd fakeroot
Yes, use make-kpkg --rootcmd fakeroot
On Sun, Oct 30, 2005 at 12:11:15AM +0200, Yedidyah Bar-David wrote:
On Sun, Oct 30, 2005 at 01:16:53AM +0200, Aaron wrote:
I have been building for 2 days and am wondering why, I see that a
process called faked-sysv is using 80% of my processor, anyone know what
that is?
faked is used
On Sun, 30 Oct 2005, Aaron wrote:
However on Debian it is generally preffered to build kernels using
make-kpkg --rootcmd fakeroot (from the package kernel-kpg) even when
building a vanilla kernel.
faked should take that much CPU time, though.
So it has been building for two days
I have a pIII with 300mg ram.
I am also thinking maybe its a loop
Aaron
On Sun, 2005-10-30 at 18:37 +0200, guy keren wrote:
On Sun, 30 Oct 2005, Aaron wrote:
However on Debian it is generally preffered to build kernels using
make-kpkg --rootcmd fakeroot (from the package kernel-kpg)
No I scrolled up I don't think its a loop.
I didn't make clean before I started and a previous build was interupted
by a kid.
could this make things go so slow?
Aaron
On Sun, 2005-10-30 at 18:37 +0200, guy keren wrote:
On Sun, 30 Oct 2005, Aaron wrote:
However on Debian it is generally
On Sun, 30 Oct 2005, Aaron wrote:
No I scrolled up I don't think its a loop.
I didn't make clean before I started and a previous build was interupted
by a kid.
could this make things go so slow?
no - but it could explain why it's in such a loop.
if i were you, i'd start afresh - if it's
On 10/30/05, Aaron [EMAIL PROTECTED] wrote:
O
faked should take that much CPU time, though.
if that means anything, but I remember kernel building only taking a few
hours??
I think he forgot to type the not - a kernel build should *not* take that long
on any kind of hardware (not even on a
ok I just killed it.
Ignoring the instructions I got from googling.
how should I proceed now.
what I did was copy the config from my running kernel and the remove a
few obvious things and then
fakeroot make-kpkg --append-to-version -vanilla --revision 0.1
kernel_image
btw the kernel_image
Hi all I am starting again and noticed that in building my kernel the
processor type was pentium pro.
I have a PIII, should this be Pentium MMX?
Thanks
Aaron
On Sun, 2005-10-30 at 01:45 +0200, Aaron wrote:
Ok some background.
I am running demudi which has custom lowlatency kernels. This is
On 10/31/05, Aaron [EMAIL PROTECTED] wrote:
ok I just killed it.
Ignoring the instructions I got from googling.
how should I proceed now.
There are pretty clear instrcutions under
/usr/share/doc/kernel-package/README.gz,
read the entire document and decide which route you want to take BEFORE
Strange how miopic I get, for things I am familiar with I run
to /usr/share/doc/* to learn new things but just don't think to look
there for the obvious...
On Mon, 2005-10-31 at 11:44 +1100, Amos Shapira wrote:
/usr/share/doc/kernel-package/README.gz
As for ccing I am to my dismay back to using
On Mon, Oct 31, 2005 at 02:23:06AM +0200, Aaron wrote:
fakeroot make-kpkg --append-to-version -vanilla --revision 0.1
kernel_image
Tzafrir mentioned: make-kpkg --rootcmd fakeroot
Yes, use make-kpkg --rootcmd fakeroot instead of fakeroot
make-kpkg. It will give fakeroot less work, because
On Mon, Oct 31, 2005 at 03:06:03AM +0200, Aaron wrote:
Hi all I am starting again and noticed that in building my kernel
the processor type was pentium pro. I have a PIII, should this be
Pentium MMX?
Well, no, it should be Pentium III. (Config option CONFIG_MPENTIUMIII,
labelled
Hi all,
I am trying to build a custom kernel for debian and as I am building I
see a ton of scsi drivers, go by.
There is no way I need all these drivers, but how do I determine which
ones I need?
I see that usb storage devices are treated as scsi devices, I also have
one plextor scsi cdrom and
Hello Aaron,
If you did not play too much with the kernel configuration, then you
probably left all those SCSI device drivers configured as M (modules).
This means that thosee drivers would be loaded only if the corresponding
SCSI device is detected when peripherals are being probed.
Therefore,
Beware, though, that if the hard drive you boot from is a SCSI / SATA
one too, you should take a special precaution -- either don't build the
'SCSI disk (sd) driver' nor your SCSI / SATA controller's driver built
as modules (but rather compile them into the kernel) or use the
initrd feature.
On Sat, Oct 29, 2005 at 09:09:59PM +0200, Aaron wrote:
Hi all,
I am trying to build a custom kernel for debian and as I am building I
see a ton of scsi drivers, go by.
There is no way I need all these drivers, but how do I determine which
ones I need?
A recent issue of kernel traffic
On 10/30/05, Aaron [EMAIL PROTECTED] wrote:
Hi all,
I am trying to build a custom kernel for debian and as I am building I
see a ton of scsi drivers, go by.
There is no way I need all these drivers, but how do I determine which
ones I need?
In addition to Omer's explenation about modules,
Ok some background.
I am running demudi which has custom lowlatency kernels. This is for
proaudio, which I sometimes play with..
But with the latest kernels from demudi the smp kernels won't boot on my
system.
Why do you think your kernel won't boot? If it contains all the options then
it
19 matches
Mail list logo
