On Sun, Aug 15 2010, Stephen Powell wrote:
> On Sun, 15 Aug 2010 13:53:41 -0400 (EDT), Manoj Srivastava wrote:
>>
>> With the new versions of kernel-package in Squeeze, running
>> make-kpkg clean should almost never be required (if the upstream
>> Makefiles are not borked, as they rarely are). T
On Sun, 15 Aug 2010 13:53:41 -0400 (EDT), Manoj Srivastava wrote:
>
> With the new versions of kernel-package in Squeeze, running
> make-kpkg clean should almost never be required (if the upstream
> Makefiles are not borked, as they rarely are). The new make-kpkg
> starts by removing and re-creat
On Sat, Aug 14 2010, Stephen Powell wrote:
> Oops! I forgot to show the "make-kpkg clean" step after "make
> menuconfig". I'm not sure if this is still needed anymore, but it's
> good practice. In real life, I did issue it; but when I composed the
> e-mail, I forgot to document it.
Wit
On Sun, 15 Aug 2010 09:11:21 -0400 (EDT), Angus Hedger wrote:
> Stephen Powell wrote:
>>
>> If you copy your module directly into the source tree, then you need
>> to download a new kernel source tree and unpack it due to kernel
>> maintenance, you lose your modifications. By keeping the out-of-ke
On Sun, Aug 15, 2010 at 1:40 PM, Stephen Powell wrote:
> On Sun, 15 Aug 2010 05:27:12 -0400 (EDT), Angus Hedger wrote:
>> On Sun, Aug 15, 2010 at 1:29 AM, Stephen Powell wrote:
>>> ...
>>> $ make-kpkg --append-to-version -custom5-686 --revision 2.6.32-18 \
>>> --initrd --rootcmd fakeroot kernel_
On Sun, 15 Aug 2010 05:27:12 -0400 (EDT), Angus Hedger wrote:
> On Sun, Aug 15, 2010 at 1:29 AM, Stephen Powell wrote:
>> ...
>> $ make-kpkg --append-to-version -custom5-686 --revision 2.6.32-18 \
>> --initrd --rootcmd fakeroot kernel_image modules_image
>> ...
>
> Quick question, is there an adv
Hey,
Sorry for the double, but forgot something!
On Sun, Aug 15, 2010 at 1:29 AM, Stephen Powell wrote:
> $ make-kpkg --append-to-version -custom5-686 --revision 2.6.32-18 \
> --initrd --rootcmd fakeroot kernel_image modules_image
Quick question, is there an advantage to building a modules_
Hey.
On Sun, Aug 15, 2010 at 1:29 AM, Stephen Powell wrote:
>
> I don't think that this is a bug. I think you're trying to mix and match
> two different ways of doing things. There are two basic ways of creating
> an out-of-kernel-source-tree module from source: (1) install the kernel
> header
On Jo, 12 aug 10, 11:10:16, Arthur Machlas wrote:
>
> Isn't there a risk in granting user access to src, adm, and such if
> ever your user account is compromised? My uninformed opinion is that
> it's a question of relative risk; the 'risk' involved in building
> kernels as root, versus the risk in
On Sat, 14 Aug 2010 20:29:11 -0400 (EDT), Stephen Powell wrote:
> --
>
> $ cd linux-source-2.6.32
> $ cp /boot/config-2.6.32-5-686 .config
> $ make menuconfig
> $ make-kpkg --append-to-version -custom5-686 --revision 2.6.32-18 \
>--initrd --rootcmd fakeroot kernel_image modules_image
>
On Fri, 13 Aug 2010 15:12:02 -0400 (EDT), Angus Hedger wrote:
>
> The two things that i use k-headers for myself are the nvidia blob,
> and the virtual-box km's
>
> The only issues I ran into when building headers via make-kpkg where as
> follows,
>
> Make sure you use the same "-append-to-vers
On Fri, Aug 13, 2010 at 4:28 PM, Angus Hedger wrote:
> Hey!
>
>> I don't use the -j3 switch, and I don't think that -j3 switch works
>> like you think it does when using make-kpkg, at least, not if that's
>> meant to utilize multiple processors when building. I'm at work right
>> so this is all fr
Hey!
>>> On Fri, 13 Aug 2010 13:27:50 -0400 (EDT), Arthur Machlas wrote:
>> The only issues I ran into when building headers via make-kpkg where as
>> follows,
>>
>> Make sure you use the same "-append-to-version -stuff-here" line as
>> you do when building your kernel, or they wont match up and
On Fri, Aug 13, 2010 at 2:12 PM, Angus Hedger wrote:
> On Fri, Aug 13, 2010 at 7:46 PM, Stephen Powell wrote:
>> On Fri, 13 Aug 2010 13:27:50 -0400 (EDT), Arthur Machlas wrote:
> The only issues I ran into when building headers via make-kpkg where as
> follows,
>
> Make sure you use the same "-a
On Fri, Aug 13, 2010 at 7:46 PM, Stephen Powell wrote:
> On Fri, 13 Aug 2010 13:27:50 -0400 (EDT), Arthur Machlas wrote:
>> Stephen Powell wrote:
>>> The latest version of my kernel building web page, revised yesterday
>>> (http://www.wowway.com/~zlinuxman/Kernel.htm), recommends unpacking,
>>> co
On Fri, 13 Aug 2010 13:27:50 -0400 (EDT), Arthur Machlas wrote:
> Stephen Powell wrote:
>> The latest version of my kernel building web page, revised yesterday
>> (http://www.wowway.com/~zlinuxman/Kernel.htm), recommends unpacking,
>> configuring, and compiling the kernel from its default location
> The latest version of my kernel building web page, revised yesterday
> (http://www.wowway.com/~zlinuxman/Kernel.htm), recommends unpacking,
> configuring, and compiling the kernel from its default location
> as a non-root user which is a member of group src. It can be the
> system administrator'
On Fri, 13 Aug 2010 10:11:33 -0400 (EDT), Celejar wrote:
> On Thu, 12 Aug 2010 12:34:34 -0400 (EDT), Stephen Powell wrote:
>> ...
>> I suppose the most secure method would be to create an id just
>> for kernel building which is a member of group src and its login
>> group, and that's it.
>
> How a
On Thu, 12 Aug 2010 12:34:34 -0400 (EDT)
Stephen Powell wrote:
...
> says! I suppose the most secure method would be to create an id just
> for kernel building which is a member of group src and its login
> group, and that's it.
How about copying the source to an unprivileged location, assumin
On Thu, 12 Aug 2010 13:55:40 -0400 (EDT), Sven Joachim wrote:
> Stephen Powell wrote:
>> I do know about groups, but I don't necessarily know the intended
>> purpose of all of the pre-defined groups in a Linux system. Where
>> can I find documentation for that?
>
> For Debian, there is some infor
On Thu, 12 Aug 2010 13:25:50 -0400 (EDT), Bob Proulx wrote:
> Stephen Powell wrote:
>> Still, I should have noticed that the /usr/src directory was owned
>> by user root and by group src. For some reason, I never made that
>> connection. That's a great tip, thanks. I will have to play around
>>
On Fri, Aug 13, 2010 at 1:29 AM, Alexander Samad wrote:
> Hi
>
> Well its still doesn't work. I am trying to build the VB kernel
> modules and well it fails.
>
> I need to build the linux-kbuild-2.6.35, working with linux-source
> just doesn't work ... (I don't want to build a new linux-image)
>
Okay I have a working solution and set of steps
Unfortunately I didn't keep the url where I got this. But it works, I have
to change the changelog to 2.6.35 instead of 2.6.34
==
How to build linux-kbuild-2.6 yourself
Fetch the sources from SVN:
svn co svn://svn.debian.org/kernel/dists/trun
Hi
Well its still doesn't work. I am trying to build the VB kernel
modules and well it fails.
I need to build the linux-kbuild-2.6.35, working with linux-source
just doesn't work ... (I don't want to build a new linux-image)
Alex
On Wed, Aug 11, 2010 at 6:19 PM, Alexander Samad wrote:
> [snip
Arthur Machlas wrote:
> > Bob Proulx wrote:
> >> With those in place you can work as yourself in those areas. Safer
> >> than using root since as yourself you can't smash anything in the
> >> system directories /etc or /bin or /var or other system locations.
>
> Isn't there a risk in granting use
On 2010-08-12 19:25 +0200, Bob Proulx wrote:
> Stephen Powell wrote:
>> I do know about groups, but I don't necessarily know the intended
>> purpose of all of the pre-defined groups in a Linux system. Where
>> can I find documentation for that?
>
> Unfortunately I have no idea. I don't even know
Stephen Powell wrote:
> I do know about groups, but I don't necessarily know the intended
> purpose of all of the pre-defined groups in a Linux system. Where
> can I find documentation for that?
Unfortunately I have no idea. I don't even know if they are all
documented someplace. And distro to
On 2010-08-12 18:10 +0200, Arthur Machlas wrote:
> Isn't there a risk in granting user access to src, adm, and such if
> ever your user account is compromised?
This depends on how the computer is used, I suppose. On personal
desktops/laptops, giving intruders access to these groups is the least
On Thu, 12 Aug 2010 12:10:16 -0400 (EDT), Arthur Machlas wrote:
> On Wed, 11 Aug 2010 17:33:12 -0400 (EDT), Bob Proulx wrote:
>> Then log out. At login you will be set to those additional groups.
>> With those in place you can work as yourself in those areas. Safer
>> than using root since as you
On Thu, Aug 12, 2010 at 8:41 AM, Stephen Powell wrote:
> On Wed, 11 Aug 2010 17:33:12 -0400 (EDT), Bob Proulx wrote:
>> Then log out. At login you will be set to those additional groups.
>> With those in place you can work as yourself in those areas. Safer
>> than using root since as yourself yo
On Wed, 11 Aug 2010 17:33:12 -0400 (EDT), Bob Proulx wrote:
>
> If it is your own machine then you should certainly be in the 'src'
> group and then you would have access to /usr/src as your own normal
> user self. And if you don't know about src then you probably don't
> know about 'staff' and '
Stephen Powell wrote:
> (1) I believe that "aptitude install linux-source-x.x.xx", as with any
> package installation, requires root privileges.
Yes, but that isn't the only way to get the source. There are many
ways of getting linux kernel source that don't involve installing
packages.
> (2) B
On Tue, 10 Aug 2010 16:43:04 -0400 (EDT), Arthur Machlas wrote:
>
> A less religious explanation, from Greg Kroah-Hartman, author of The
> Linux Kernel in a Nutshell, and well-known kernel hacker.
>
> "This warning is the most important thing to remember while working through
> the
> steps in th
[snip]
>> What do I need to do :)
>>
>
> Maybe this will help...
>
> The "make headers_install" command exports the kernel's header files in a
> form suitable for use by userspace programs.
>
> The kernel header files can be generated from the kernel sources.
>
> Define INSTALL_HDR_PATH= for outpu
> On Wed, 11 Aug 2010 08:45:04 +0800 wrote:
>
> [snip]
> >>>
> >>> I did trying using the packages for 2.6.35, but you can't install the
> >>> headers because the linux-kbuild-2.6.35 is there
> >>
> >> Why do you want to install the headers if you already have the whole
> >> kernel source code?
[snip]
>>>
>>> I did trying using the packages for 2.6.35, but you can't install the
>>> headers because the linux-kbuild-2.6.35 is there
>>
>> Why do you want to install the headers if you already have the whole
>> kernel source code? What are you trying to accomplish besides
>> building a custom
> If you've looked at my kernel building web page,
> http://www.wowway.com/~zlinuxman/Kernel.htm, you will see that I
> don't cover this. That's because I don't use it when I build my
> own custom kernels. I do use it when building a "regular"
> Debian package, but for some reason I've never both
On Tue, 10 Aug 2010 14:58:04 -0400 (EDT), Tom H wrote:
>
> I have and I agree with you regarding what fakeroot does (based on the
> manpage that I've read in the past and read again after you posted
> part of it).
>
> IIUC, instead of giving you additional powers, fakeroot gives your
> environmen
On Mon, Aug 9, 2010 at 8:18 PM, John Hasler wrote:
> Tom H writes:
>> I wasn't saying that you should use sudo. I was pointing out that you
>> were wrong in saying that "shouldn't compile using root permissions".
>
> No he wasn't.
>
>> Whether you choose fakeroot, sudo, su, or log on as root, is a
On Tue, Aug 10, 2010 at 9:00 PM, Stephen Powell wrote:
> On Mon, 09 Aug 2010 19:01:50 -0400 (EDT), Alexander Samad wrote:
>> On Mon, Aug 9, 2010 at 9:26 AM, Stephen Powell wrote:
>>> On Sun, 08 Aug 2010 03:10:10 -0400 (EDT), Angus Hedger wrote:
[snip
>>
>> I did trying using the packages for
On Mon, 09 Aug 2010 19:01:50 -0400 (EDT), Alexander Samad wrote:
> On Mon, Aug 9, 2010 at 9:26 AM, Stephen Powell wrote:
>> On Sun, 08 Aug 2010 03:10:10 -0400 (EDT), Angus Hedger wrote:
>>>
>>> I have been fumbling my way though building custom kernels on debian
>>> using this guide http://www.wow
On Mon, 9 Aug 2010 19:38:48 -0400
Tom H wrote:
...
> Whether you choose fakeroot, sudo, su, or log on as root, is a
> religious-type discussion that you can have with someone who cares
> about such things.
As others have pointed out, the difference between fakeroot and the
other choices is sign
Tom H writes:
> I wasn't saying that you should use sudo. I was pointing out that you
> were wrong in saying that "shouldn't compile using root permissions".
No he wasn't.
> Whether you choose fakeroot, sudo, su, or log on as root, is a
> religious-type discussion that you can have with someone w
On Mon, Aug 9, 2010 at 7:05 PM, John Hasler wrote:
> Tom H wrote:
>> 4% $Get_Root make-kpkg --revision=custom.1.0 kernel_image
>> (Get_Root is whatever you need to become root -- fakeroot or
>> sudo are examples that come to mind).
>
> >From the fakeroot man page:
>
> DESCRIPTION
>
On Mon, Aug 9, 2010 at 5:51 PM, Bob Proulx wrote:
> Tom H wrote:
>> Bob Proulx wrote:
>> > Alexander Samad wrote:
>> >> sudo CONCURRENCY_LEVEL=4 make-kpkg --initrd kernel_image
>> >
>> > You shouldn't compile using root permissions. You don't need to use
>> > sudo there and it is not desired.
>>
Tom H wrote:
> 4% $Get_Root make-kpkg --revision=custom.1.0 kernel_image
> (Get_Root is whatever you need to become root -- fakeroot or
> sudo are examples that come to mind).
>From the fakeroot man page:
DESCRIPTION
fakeroot runs a command in an environment wherein it app
On Mon, Aug 9, 2010 at 9:26 AM, Stephen Powell wrote:
> On Sun, 08 Aug 2010 03:10:10 -0400 (EDT), Angus Hedger wrote:
>>
>> I have been fumbling my way though building custom kernels on debian
>> using this guide http://www.wowway.com/~zlinuxman/Kernel.htm.
>>
>> Though, I have been using the .con
Tom H wrote:
> Bob Proulx wrote:
> > Alexander Samad wrote:
> >> sudo CONCURRENCY_LEVEL=4 make-kpkg --initrd kernel_image
> >
> > You shouldn't compile using root permissions. You don't need to use
> > sudo there and it is not desired.
>
> >From the kernel-package documentation:
>
> 4% $Get_Roo
On Mon, Aug 9, 2010 at 2:26 AM, Stephen Powell wrote:
> On Sun, 08 Aug 2010 03:10:10 -0400 (EDT), Angus Hedger wrote:
>>
>> I have been fumbling my way though building custom kernels on debian
>> using this guide http://www.wowway.com/~zlinuxman/Kernel.htm.
>>
>> Though, I have been using the .con
On Sun, 08 Aug 2010 07:48:48 -0400 (EDT), Tom H wrote:
>
> http://www.wowway.com/~zlinuxman/Kernel.htm
> is a good guide to building a kernel the Debian way. It is written by
> d-u regular and is included in the kernel-package documentation as
> /usr/share/kernel-package/docs/Kernel.htm
Unfortuna
On Sun, 08 Aug 2010 03:10:10 -0400 (EDT), Angus Hedger wrote:
>
> I have been fumbling my way though building custom kernels on debian
> using this guide http://www.wowway.com/~zlinuxman/Kernel.htm.
>
> Though, I have been using the .config from the stock 2.6.32 kernel and
> customising it to fit
* Alexander Samad [100808 12:45 +1000]:
> Hi
>
> I am looking at how to build 2.6.35 the debian way so I end up with
> deb packages.
http://kernel-handbook.alioth.debian.org/ch-common-tasks.html
Elimar
--
>what IMHO then?
IMHO - Inhalation of a Multi-leafed Herbal Opiate ;)
-
On Sat, Aug 7, 2010 at 11:57 PM, Bob Proulx wrote:
> Alexander Samad wrote:
>
>> sudo CONCURRENCY_LEVEL=4 make-kpkg --initrd kernel_image
>
> You shouldn't compile using root permissions. You don't need to use
> sudo there and it is not desired.
>From the kernel-package documentation:
4% $Get_
On Sat, Aug 7, 2010 at 10:45 PM, Alexander Samad wrote:
>
> I am looking at how to build 2.6.35 the debian way so I end up with
> deb packages. the current situation is 2.6.35 is avail in experimental
> (>?!) with out a linux-kbuild packages - last time I asked about this
> it was because they onl
On 2010-08-08 09:39 +0200, Jochen Schulz wrote:
> Alexander Samad:
>>
>> I am looking at how to build 2.6.35 the debian way so I end up with
>> deb packages.
>
> The easiest way to get a kernel deb is to fetch vanilla sources from
> kernel.org, unpack them and run 'make && make deb-pkg'. I am not
Alexander Samad:
>
> I am looking at how to build 2.6.35 the debian way so I end up with
> deb packages.
The easiest way to get a kernel deb is to fetch vanilla sources from
kernel.org, unpack them and run 'make && make deb-pkg'. I am not sure
whether such packages create an initramfs on installa
On Sun, Aug 8, 2010 at 3:45 AM, Alexander Samad wrote:
> Hi
>
> I am looking at how to build 2.6.35 the debian way so I end up with
> deb packages. the current situation is 2.6.35 is avail in experimental
> (>?!) with out a linux-kbuild packages - last time I asked about this
> it was because they
I should also say that I have the following in my ~/.devscripts file
so as to always customize dpkg-buildpackage.
DEBUILD_DPKG_BUILDPACKAGE_OPTS="-uc -us"
That avoids signing the source or changes files. Which IMNHO really
shouldn't be done as part of the build but only later when you are
read
Alexander Samad wrote:
> I have had a look here
> http://wiki.debian.org/HowToRebuildAnOfficialDebianKernelPackage,
> there is a section on building linux-kbuild - but guess what the svn
> co downloads the 2.6.34 version :(
>
> I found this http://www.linuxconfig.org/building-kernels-the-debian-wa
59 matches
Mail list logo
