Re: Patching a kernel source --verbose

2006-08-12 Thread Roberto C. Sanchez
On Sat, Aug 12, 2006 at 08:44:29PM -0400, Matej Cepl wrote: > Roberto C. Sanchez wrote: > > I use the symlinks /boot/vmlinuz, /boot/initrd.img, /boot/vmlinuz.old > > and /boot/initrd.img.old to point to my current and previous kernels. > > These are listed in my menu.lst. Whenever I update the ker

Re: Patching a kernel source --verbose

2006-08-12 Thread Matej Cepl
Roberto C. Sanchez wrote: > I use the symlinks /boot/vmlinuz, /boot/initrd.img, /boot/vmlinuz.old > and /boot/initrd.img.old to point to my current and previous kernels. > These are listed in my menu.lst. Whenever I update the kernel, if > /sbin/update-grub is run, it helpfully replaces those with

Re: Patching a kernel source --verbose

2006-08-12 Thread Jon Dowland
At 1155222171 past the epoch, Chuckk Hubbard wrote: > I'm a little confused why, when I enter: > Hammertime:/home/chuckk/Desktop/kernel/new/linux-2.6.17-mm6# > patch --verbose -p1 ../2.6.17-mm6 > > the terminal sits idle, apparently indefinitely. As other(s) have mentioned, you need to add -i or

Re: Patching a kernel source --verbose

2006-08-12 Thread Roberto C. Sanchez
On Sat, Aug 12, 2006 at 12:43:08PM +0930, Arthur Marsh wrote: > > I've wanted to have the automated tools to work for me, so I backed up > /boot/grub/menu.lst, then read the manual page for update-grub before > running it, observing the differences between the backed-up copy and the > automatic

Re: Patching a kernel source --verbose

2006-08-11 Thread Arthur Marsh
Roberto C. Sanchez wrote: On Fri, Aug 11, 2006 at 01:18:30PM +0930, Arthur Marsh wrote: The memtest86+ package installs as a grub option, so one doesn't need a separate boot image on CD to run it. True, but from a user-friendliness stand point, it is much simpler. I know that grub always des

Re: Patching a kernel source --verbose

2006-08-11 Thread Chuckk Hubbard
On 8/10/06, Roberto C. Sanchez <[EMAIL PROTECTED]> wrote: On Thu, Aug 10, 2006 at 10:26:40PM -0400, Chuckk Hubbard wrote: > Unfortunately, Linux has completely frozen up on me four times in a > row while running #make-kpkg. Different patches each time, and > different spots each time. I'll have

Re: Patching a kernel source --verbose

2006-08-11 Thread Roberto C. Sanchez
On Fri, Aug 11, 2006 at 01:18:30PM +0930, Arthur Marsh wrote: > > The memtest86+ package installs as a grub option, so one doesn't need a > separate boot image on CD to run it. > True, but from a user-friendliness stand point, it is much simpler. I know that grub always destroys my menu.lst whe

Re: Patching a kernel source --verbose

2006-08-10 Thread Arthur Marsh
Roberto C. Sanchez wrote: On Thu, Aug 10, 2006 at 10:26:40PM -0400, Chuckk Hubbard wrote: Unfortunately, Linux has completely frozen up on me four times in a row while running #make-kpkg. Different patches each time, and different spots each time. I'll have to figure this out when I don't have

Re: Patching a kernel source --verbose

2006-08-10 Thread Roberto C. Sanchez
On Thu, Aug 10, 2006 at 10:26:40PM -0400, Chuckk Hubbard wrote: > Unfortunately, Linux has completely frozen up on me four times in a > row while running #make-kpkg. Different patches each time, and > different spots each time. I'll have to figure this out when I don't > have deadlines. Sadly, I

Re: Patching a kernel source --verbose

2006-08-10 Thread Chuckk Hubbard
Unfortunately, Linux has completely frozen up on me four times in a row while running #make-kpkg. Different patches each time, and different spots each time. I'll have to figure this out when I don't have deadlines. Sadly, I think it's WinXP for now. Thanks for your help. -Chuckk On 8/10/06, R

Re: Patching a kernel source --verbose

2006-08-10 Thread Chuckk Hubbard
On 8/10/06, Roberto C. Sanchez <[EMAIL PROTECTED]> wrote: On Thu, Aug 10, 2006 at 03:47:42PM -0400, Chuckk Hubbard wrote: > > Cool, thank you. > BTW, I know it must seem like the most obvious thing in the world, but > the more I google and search Debian help, the less answers I find... > what do

Re: Patching a kernel source --verbose

2006-08-10 Thread Roberto C. Sanchez
On Thu, Aug 10, 2006 at 03:47:42PM -0400, Chuckk Hubbard wrote: > > Cool, thank you. > BTW, I know it must seem like the most obvious thing in the world, but > the more I google and search Debian help, the less answers I find... > what do you do when applying two patches tells you: > Reversed (or

Re: Patching a kernel source --verbose

2006-08-10 Thread Chuckk Hubbard
On 8/10/06, Roberto C. Sanchez <[EMAIL PROTECTED]> wrote: On Thu, Aug 10, 2006 at 03:02:51PM -0400, Chuckk Hubbard wrote: > I have linux-2.6.17, trying to patch it with 2.6.17-mm6, > patch-2.6.17-rt8 from Molnar, and bootsplash-3.1.6-2.6.15.diff. > I'm a little confused why, when I enter: > Hamme

Re: Patching a kernel source --verbose

2006-08-10 Thread Roberto C. Sanchez
On Thu, Aug 10, 2006 at 03:02:51PM -0400, Chuckk Hubbard wrote: > I have linux-2.6.17, trying to patch it with 2.6.17-mm6, > patch-2.6.17-rt8 from Molnar, and bootsplash-3.1.6-2.6.15.diff. > I'm a little confused why, when I enter: > Hammertime:/home/chuckk/Desktop/kernel/new/linux-2.6.17-mm6# patc

Re: Patching a kernel source --verbose

2006-08-10 Thread Chuckk Hubbard
P.S.- #ps -aux in another terminal shows 0.0 for CPU and memory of the patch operation, if that matters. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Patching a Kernel

2005-08-01 Thread Roberto C. Sanchez
On Mon, Aug 01, 2005 at 06:36:06PM +0200, Rakotomandimby (R12y) Mihamina wrote: > On Monday 01 August 2005 17:59, Roberto C. Sanchez wrote: > > Patching is easy. > > Not really. I rememeber my beginnings: I never knew where should I have to > 'cd' before applying the patch. > > Then understandi

Re: Patching a Kernel

2005-08-01 Thread Rakotomandimby (R12y) Mihamina
On Monday 01 August 2005 17:59, Roberto C. Sanchez wrote: > Patching is easy. Not really. I rememeber my beginnings: I never knew where should I have to 'cd' before applying the patch. Then understanding the error messages too. For ewample, patches initially made for vanilla kernels may not wo

Re: Patching a Kernel

2005-08-01 Thread Roberto C. Sanchez
On Mon, Aug 01, 2005 at 04:44:09PM +0100, Jim Blake wrote: > Sorry Guys...stupid newbie question, but I've been able to avoid doing this > in > the past... > > Is there a good HOWTO available for patching a Kernel. I have a Debian 2.4 > kernel, running in a Shuttle, and have identified a patch

Re: Patching a kernel.

2003-06-20 Thread Alexander Schmehl
* Marino Fernandez <[EMAIL PROTECTED]> [030620 10:20]: > [EMAIL PROTECTED]:/usr/src# bzip2 -dc xfs-2.4.20-all-i38620030114.bz2 | patch -p1 > kernel-source-2.4.20.tar.bz2 Your kernel source is still packed. De-pack it, using "tar -xjvf kernel-source-2.4.20.tar.bz2".

Re: Patching a kernel.

2003-06-20 Thread Joris
Marino Fernandez verraste ons met de boodschap: > [EMAIL PROTECTED]:/usr/src# bzip2 -dc xfs-2.4.20-all-i38620030114.bz2 | patch -p1 you might want to run 'patch' in the kernel source directory: cd /usr/src ln -sf kernel-source-2.4.20 linux cd linux bzip2 -dc ../xfs-2.4.20-all-i38620030114.bz2 |p

Re: Patching a kernel.

2003-06-20 Thread Marino Fernandez
On Friday 20 June 2003 12:08 pm, Joerg Johannes wrote: > On Friday 20 June 2003 04:40, Marino Fernandez wrote: > > I've trying to patch a 2.4.20 kernel with the xfs patch. I've have > > some commandline argumants, but I get error mesages. > > It would be interesting to know > 1.) What commands did

Re: Patching a kernel.

2003-06-20 Thread Alexander Schmehl
* Marino Fernandez <[EMAIL PROTECTED]> [030620 04:40]: > I've trying to patch a 2.4.20 kernel with the xfs patch. I've have some > commandline argumants, but I get error mesages. Which commands? Which error messages? Do you use the kernel-patch-xfs package or have you downloaded the patch manual

Re: Patching a kernel.

2003-06-20 Thread Joerg Johannes
On Friday 20 June 2003 04:40, Marino Fernandez wrote: > I've trying to patch a 2.4.20 kernel with the xfs patch. I've have > some commandline argumants, but I get error mesages. It would be interesting to know 1.) What commands did you use 2.) What error messages you get Then we might be able to