Do you 
    1. Intend to compile 2.6 for the first time
and
    2. Don't follow kernel devel

  ? 

then this message is probably for you.

  I had to be told explicitly about the 2.6 document drawn up by 
Dave Jones, http://lwn.net/Articles/39901/. It, and I am quoting:


                explains some of the new functionality to be found in
    the 2.5 Linux kernel, some pitfalls you may encounter, and also 
    points out some new features which could really use testing.

    Certain known bugs are being reported over and over. Here are the
    workarounds.
    - Blank screen after decompressing kernel?
      Make sure your .config has CONFIG_INPUT=y, CONFIG_VT=y,
      CONFIG_VGA_CONSOLE=y and CONFIG_VT_CONSOLE=y A lot of people have
      discovered that taking their .config from 2.4 and running make
      oldconfig to pick up new options leads to problems, notably
      with CONFIG_VT not being set.
    - An additional bug biting some people is that NICs fail to receive 
      packets (usually notable by a NIC not getting a DHCP lease for
      eg, despite being sent one by the server). Booting with "noapic"
      "acpi=off" or a combination of both fixes this for most people.
      Additional breakage reports should go to Jeff Garzik 
      <[EMAIL PROTECTED]>
    - (Possibly linked to above bug) VIA APIC routing is currently broken.
      boot with 'noapic'.
    - Can't load any modules? You need updated tools (See modules section
      below).

  A similar link was posted here on
http://plasma-gate.weizmann.ac.il/Linux/maillists/03/07/msg00519.html.
However I didn't understood the importance of that link until recently.
Hopefully,

  The target audience of this message is not empty.
    and
  There will be at least one person here that will read it before 
  upgrading. 
  
In addition, msg00519.html refers to what is now a slightly older
version of that doc, but I didn't diff the two.

  Wouldn't it be nice if members who follow the kernel devel would
post here similar links on similar occasions?
-- 

    Shaul Karl,    shaulk @ actcom . net . il

=================================================================
To unsubscribe, send mail to [EMAIL PROTECTED] with
the word "unsubscribe" in the message body, e.g., run the command
echo unsubscribe | mail [EMAIL PROTECTED]

Reply via email to