<?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: Executed lilo -u on RH7.2 in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/executed-lilo-u-on-rh7-2/m-p/2682687#M1310</link>
    <description>In lilo.conf, you have "default=linux", but you don't have a label of "linux" set anywhere.  I would change the default= paramater to "default=linux_7_2_9_31" or whichever kernel you want to boot with.  It's not really all that important because lilo allows you to choose which image you want to boot to at the boot prompt (by typing the &lt;TAB&gt; key), but lilo will bark at you if the default you've defined doesn't exist.  &lt;BR /&gt;&lt;BR /&gt;The man page says that lilo will pick the first image in lilo.conf if a default is not specified.  I guess that incorrectly specifying a default image is not the same as not specifying it at all.  :-)&lt;BR /&gt;&lt;BR /&gt;Just as an FYI from a fairly experienced admin... make boot disks.  I know it's a pain, but it'll save your rear just like it has mine a couple of times now when something like this happens.&lt;BR /&gt;&lt;BR /&gt;Hope this helps.  Good luck.&lt;BR /&gt;&lt;BR /&gt;&lt;/TAB&gt;</description>
    <pubDate>Thu, 14 Mar 2002 04:42:39 GMT</pubDate>
    <dc:creator>Christopher C. Weis</dc:creator>
    <dc:date>2002-03-14T04:42:39Z</dc:date>
    <item>
      <title>Executed lilo -u on RH7.2</title>
      <link>https://community.hpe.com/t5/operating-system-linux/executed-lilo-u-on-rh7-2/m-p/2682686#M1309</link>
      <description>I accidentally executed the &lt;BR /&gt;command /sbin/lilo -u. The man&lt;BR /&gt;page says the -u option will&lt;BR /&gt;"Uninstall lilo, by copying&lt;BR /&gt;the saved boot sector back. A&lt;BR /&gt;time-stamp is checked. When I&lt;BR /&gt;do a /sbin/lilo -t, I get this&lt;BR /&gt;message: lilo -t&lt;BR /&gt;Added linux_7_2_7_10&lt;BR /&gt;Added linux_7_2_9_31&lt;BR /&gt;Fatal: No images have been defined.&lt;BR /&gt;&lt;BR /&gt;What have I done to my system,&lt;BR /&gt;and is it reparirable? I included&lt;BR /&gt;a copy of my /etc/lilo.conf file&lt;BR /&gt;as an attachment.</description>
      <pubDate>Thu, 14 Mar 2002 00:04:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/executed-lilo-u-on-rh7-2/m-p/2682686#M1309</guid>
      <dc:creator>Gerald Penyweit</dc:creator>
      <dc:date>2002-03-14T00:04:11Z</dc:date>
    </item>
    <item>
      <title>Re: Executed lilo -u on RH7.2</title>
      <link>https://community.hpe.com/t5/operating-system-linux/executed-lilo-u-on-rh7-2/m-p/2682687#M1310</link>
      <description>In lilo.conf, you have "default=linux", but you don't have a label of "linux" set anywhere.  I would change the default= paramater to "default=linux_7_2_9_31" or whichever kernel you want to boot with.  It's not really all that important because lilo allows you to choose which image you want to boot to at the boot prompt (by typing the &lt;TAB&gt; key), but lilo will bark at you if the default you've defined doesn't exist.  &lt;BR /&gt;&lt;BR /&gt;The man page says that lilo will pick the first image in lilo.conf if a default is not specified.  I guess that incorrectly specifying a default image is not the same as not specifying it at all.  :-)&lt;BR /&gt;&lt;BR /&gt;Just as an FYI from a fairly experienced admin... make boot disks.  I know it's a pain, but it'll save your rear just like it has mine a couple of times now when something like this happens.&lt;BR /&gt;&lt;BR /&gt;Hope this helps.  Good luck.&lt;BR /&gt;&lt;BR /&gt;&lt;/TAB&gt;</description>
      <pubDate>Thu, 14 Mar 2002 04:42:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/executed-lilo-u-on-rh7-2/m-p/2682687#M1310</guid>
      <dc:creator>Christopher C. Weis</dc:creator>
      <dc:date>2002-03-14T04:42:39Z</dc:date>
    </item>
    <item>
      <title>Re: Executed lilo -u on RH7.2</title>
      <link>https://community.hpe.com/t5/operating-system-linux/executed-lilo-u-on-rh7-2/m-p/2682688#M1311</link>
      <description>If I remember correctly, lilo -u will restore your mbr to its original state, i.e. the state it was in before lilo was installed.  You should be able to run lilo -v to re-install lilo into the mbr.&lt;BR /&gt;&lt;BR /&gt;In addition, all of Christopher's comments are valid.&lt;BR /&gt;&lt;BR /&gt;-Santosh</description>
      <pubDate>Thu, 14 Mar 2002 21:31:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/executed-lilo-u-on-rh7-2/m-p/2682688#M1311</guid>
      <dc:creator>Santosh Nair_1</dc:creator>
      <dc:date>2002-03-14T21:31:58Z</dc:date>
    </item>
  </channel>
</rss>

