#3237: Linux-3.6.10
------------------------------------------+---------------------------------
 Reporter:  matthew@…                     |       Owner:  matthew@…             
      
     Type:  enhancement                   |      Status:  assigned              
      
 Priority:  normal                        |   Milestone:  7.3                   
      
Component:  Book                          |     Version:  SVN                   
      
 Severity:  normal                        |    Keywords:                        
      
------------------------------------------+---------------------------------

Comment(by matthew@…):

 Replying to [comment:4 fo]:
 > I had just downloaded the patch for 3.6.10, when I saw 3.7. Before
 upgrading 7 machines to any, I decided to ask about some doubts, because
 do not yet fully understand.
 >
 > In [https://www.kernel.org/], it is marked:
 >
 > Latest Stable Kernel: 3.6.10
 >
 > mainline:     3.7     2012-12-11[[BR]]
 > stable:       3.6.10  2012-12-10

 LFS uses both mainline and stable kernels, depending on whichever is
 newer.  I don't think I'd be comfortable putting an LFS release out with a
 mainline (non-stable) kernel, but they're reliable enough for development,
 and the 1st stable kernel is normally only a couple of weeks away.

 So, I'd recommend you use 3.7 after testing it on one of your machines
 first.

 > A side note:
 >
 > In "Upgrade Warning !!!"
 [http://lkml.indiana.edu/hypermail/linux/kernel/1212.0/03194.html]:
 > "... you have exceeded your email Database limit of
 > 500 MB quota and your email IP ..."

 That's a fairly obvious spam.  I would not recommend clicking on the
 Google Docs link in that message, and especially not from a Windows
 machine!

-- 
Ticket URL: <http://wiki.linuxfromscratch.org/lfs/ticket/3237#comment:5>
LFS Trac <http://wiki.linuxfromscratch.org/lfs/>
Linux From Scratch: Your Distro, Your Rules.
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-book
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Reply via email to