Re: Problem with compiling kernel

2007-05-09 Thread Manoj Srivastava
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 mis

Re: Problem with compiling kernel

2007-05-09 Thread Celejar
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 More

Re: Problem with compiling kernel

2007-05-08 Thread Manoj Srivastava
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

Re: Problem with compiling kernel

2007-05-08 Thread Manoj Srivastava
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

Re: Problem with compiling kernel

2007-05-08 Thread Andrew Sackville-West
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 installi

Re: Problem with compiling kernel

2007-05-08 Thread Celejar
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

Problem with compiling kernel

2007-05-08 Thread pizzapie_linuxanchovies
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 /usr/b

Re: Problem with compiling kernel

2007-05-08 Thread Andrew Sackville-West
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 > >> con

Re: Problem with compiling kernel

2007-05-08 Thread Manoj Srivastava
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.

Re: Problem with compiling kernel

2007-05-08 Thread Raffaele Morelli
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 unl

Re: Problem with compiling kernel

2007-05-08 Thread Celejar
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 i

Re: Problem with compiling kernel

2007-05-08 Thread Hugo Vanwoerkom
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)

Re: Problem with compiling kernel

2007-05-08 Thread Raffaele Morelli
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

Re: Problem with compiling kernel

2007-05-08 Thread Hugo Vanwoerkom
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: dpkg-a

Re: Problem with compiling kernel

2007-05-07 Thread John L Fjellstad
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

Re: Problem with compiling kernel

2007-05-07 Thread Manoj Srivastava
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" Howe

Problem with compiling kernel

2007-05-07 Thread pizzapie_linuxanchovies
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 --print