Re: [RFC] make it easy to test new kernels

[Tejun <htejun@gmail.com>]

jerome lacoste wrote:
> But maybe I am focusing on the wrong approach?
> Linux developers, what would be the thing that takes no more than 4-5
> min per day that people like me could do with our machines to help you
> improve Linux?

Hello, Jerome.

As you've noted earlier in the message, swsusp will be helpful, I think. 
 Here's my suggestion.

1. setup swsusp/swsusp2 on target machines (swsusp2 works pretty well)
2. setup small (10G maybe) test partition on target machines with 
minimal distribution (just install on one machine and copy the partition 
over)
3. setup netboot for target machines (reserve one machine for kernel 
serving)

When a new kernel comes out...

1. build the kernel and set it up for netbooting
2. software suspend testing machines & reboot'em with the new kernel
   using netbooting
3. see whether things work
4. reboot and resume production system

The suspend/resume instead of full rebooting should save a lot of time. 
 If you also use netbooting for the production kernel, you can just 
change settings on the kernel serving machine to select which kernel to 
boot and which partition to mount for root fs.

--
tejun
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/