<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: RE : Ramdisk in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/re-ramdisk/m-p/3667292#M67084</link>
    <description>Took the next line from internet:&lt;BR /&gt;&lt;BR /&gt;RAMDisk is a software driver that emulates as fully as possible the low-level functionality of a hard disk with system RAM.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;To remove it you can use the simple &lt;BR /&gt;rm filename&lt;BR /&gt;where filename is the name of the file that you've created with mkinitrd.</description>
    <pubDate>Wed, 09 Nov 2005 03:24:36 GMT</pubDate>
    <dc:creator>Alexander Chuzhoy</dc:creator>
    <dc:date>2005-11-09T03:24:36Z</dc:date>
    <item>
      <title>RE : Ramdisk</title>
      <link>https://community.hpe.com/t5/operating-system-linux/re-ramdisk/m-p/3667291#M67083</link>
      <description>Dea Sir,&lt;BR /&gt;   What's Ram disk? If created the ram disk with mkinitrd , how to remove it? Please advise. thank you.</description>
      <pubDate>Tue, 08 Nov 2005 22:49:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/re-ramdisk/m-p/3667291#M67083</guid>
      <dc:creator>Charles Ooi Chia Lun</dc:creator>
      <dc:date>2005-11-08T22:49:23Z</dc:date>
    </item>
    <item>
      <title>Re: RE : Ramdisk</title>
      <link>https://community.hpe.com/t5/operating-system-linux/re-ramdisk/m-p/3667292#M67084</link>
      <description>Took the next line from internet:&lt;BR /&gt;&lt;BR /&gt;RAMDisk is a software driver that emulates as fully as possible the low-level functionality of a hard disk with system RAM.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;To remove it you can use the simple &lt;BR /&gt;rm filename&lt;BR /&gt;where filename is the name of the file that you've created with mkinitrd.</description>
      <pubDate>Wed, 09 Nov 2005 03:24:36 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/re-ramdisk/m-p/3667292#M67084</guid>
      <dc:creator>Alexander Chuzhoy</dc:creator>
      <dc:date>2005-11-09T03:24:36Z</dc:date>
    </item>
    <item>
      <title>Re: RE : Ramdisk</title>
      <link>https://community.hpe.com/t5/operating-system-linux/re-ramdisk/m-p/3667293#M67085</link>
      <description>RAM disks are used at boot time to load kernel modules. You cannot just delete a ram disk. If you delete a ramdisk that is used to boot the current kernel, you system won't boot next time.</description>
      <pubDate>Wed, 09 Nov 2005 10:03:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/re-ramdisk/m-p/3667293#M67085</guid>
      <dc:creator>Ivan Ferreira</dc:creator>
      <dc:date>2005-11-09T10:03:34Z</dc:date>
    </item>
    <item>
      <title>Re: RE : Ramdisk</title>
      <link>https://community.hpe.com/t5/operating-system-linux/re-ramdisk/m-p/3667294#M67086</link>
      <description>Unless you compiled yourself a custom Linux kernel that contains all the drivers for the HW built into your PC it is most likely that the kernel that you are running used an initial RAM disk to bootstrap itself, especially when your boot disk is a SCSI device.&lt;BR /&gt;If you look into /boot you will notice files beginning with initrd*.&lt;BR /&gt;These are the RAM disks needed to boot up your kernel.&lt;BR /&gt;Because in a modular kernel drivers are commonly loaded only on demand, i.e. when the system needs to access a device,&lt;BR /&gt;this could pose a typical hen and egg problem.&lt;BR /&gt;The kernel needs to load the SCSI driver to access your boot disk, which is the very place where the driver module resides beneath /lib/modules/$(uname -r).&lt;BR /&gt;So if you don't have a monolithical kernel you need an initial RAM disk to have the driver load from to boot up.&lt;BR /&gt;It only resides temporarily in memory,&lt;BR /&gt;as long as needed.&lt;BR /&gt; &lt;BR /&gt;If you run a recent RH/Fedora Linux distro you can extract the initrd file to have a look at what's required during that early boot up phase.&lt;BR /&gt;In fact if you're HW requires any special treatment or loading of uncommon drivers&lt;BR /&gt;during boot up you are required to build a custom initrd file.&lt;BR /&gt;RedHat supplies a helper shell script to ease the creation of such a file, called mkinitrd&lt;BR /&gt;(see its manpage)&lt;BR /&gt;&lt;BR /&gt;See also my reply to this thread:&lt;BR /&gt;&lt;A href="http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=972313" target="_blank"&gt;http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=972313&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 09 Nov 2005 11:16:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/re-ramdisk/m-p/3667294#M67086</guid>
      <dc:creator>Ralph Grothe</dc:creator>
      <dc:date>2005-11-09T11:16:08Z</dc:date>
    </item>
  </channel>
</rss>

