title: Linux apanic mechanism and difference from newer ram_console/persistent_ram mechanism
body: <p>I am studying the different logging mechanisms on Linux in case of a Kernel panic (OOPS). So far from  my search on the web, I have been able to derive the following information:</p>
  
  <ul>
  <li>apanic was an old mechanism of getting the job done.</li>
  <li>ram_console/persistent_ram is a new mechanism.</li>
  </ul>
  
  <p>Could someone enlighten me about the following in this regard ?</p>
  
  <ul>
  <li>What was the old apanic mechanism, at a high-level how did this work
  ?</li>
  <li>Why was the apanic mechanism deprecated, in favor of the ram_console/persistent_ram mechanism ?</li>
  <li>What advantages does the new ram_console/persistent_ram mechinsm bring to the table.</li>
  <li>In what way is the ram_console/persistent_ram functionally different from the old apanic approach ?</li>
  </ul>
  
  <p>I am just looking for pointers and high level answers, in some sense a direction which I can take to research the mechanisms further. I would appreciate any relevant information in this regard.</p>
  
  <p>Thanks</p>