linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Marco Shaw <marco@nbnet.nb.ca>
To: linux-lvm@e35.marxmeier.com
Subject: Re: [linux-lvm] SuSE/LVM boot problem
Date: Tue, 2 May 2000 21:15:58 -0300 (ADT)	[thread overview]
Message-ID: <Pine.LNX.4.21.0005022111490.956-100000@localhost.localdomain> (raw)
In-Reply-To: <20000502114113.C1608@archimedes.suse.com>

On Tue, 2 May 2000 dgould@suse.com wrote:

Well I just have the eval version so no 2nd CD.  I tried creating a lilo
disk with another system, but I guess lilo needs the same
boot.b/system.map files to create a lilo disk?

So now I'm left with creating lilo on a disk somehow with another
system...  How could I create it?  Otherwise, I could always install a
copy of SuSE 6.3 in a VMWare VM and create a disk there...

Marco


> On Tue, May 02, 2000 at 11:51:31AM +0000, Michael Marxmeier wrote:
> > > 
> > > I lost my floppy with lilo on it.  Now I have to reconstruct it.  I've
> > > tried booting in rescue mode, but even the rescue SuSE CD doesn't appear to
> > > have LVM support.
> > > 
> > > What can I do at this point?
> > 
> > Use the installation disk - it has LVM support while the Rescue disk has not.
> > You can boot from the 2nd CD-ROM into the old Yast, do a "expert install"
> > and switch to a shell.
> > 
> 
> Be careful. I have found that the install disks are very happy to create
> systems that cannot be booted because lilo does not know about lvm.
> 
> On this topic, what is needed to make lvm work for both / and /boot with
> full lilo support? I think it somewhat limits the utility of lvm not to
> be able to make a fully lvm system, and might be tempted to do some of
> the heavy lifting if it is not too gruesome.
> 
> -dg
> 
> 

  parent reply	other threads:[~2000-05-03  0:15 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-05-02  5:20 [linux-lvm] SuSE/LVM boot problem Marco Shaw
2020-11-27 16:17 ` Michael Marxmeier
2000-05-02 18:41   ` dgould
2000-05-02 21:22     ` Jan Niehusmann
2000-05-02 22:18       ` Heinz Mauelshagen
2000-05-03 10:05       ` Ulf Bartelt
2000-05-31  8:40       ` Andi Kleen
2000-05-03  0:15     ` Marco Shaw [this message]
2000-05-03  7:38 Michael Marxmeier
2000-05-03 16:53 ` dgould
2000-05-31  9:01   ` Andi Kleen
2000-05-31 16:13     ` Christoph Hellwig
2000-05-31 16:18       ` Andi Kleen
2000-05-31 18:25         ` Michael Marxmeier
2000-06-01 12:15           ` Ulf Bartelt
2000-06-01  9:01     ` David Gould
2000-05-03 18:09 Andreas Dilger
2000-05-03 21:01 ` Eric M. Hopper
2000-05-03 23:50 Andreas Dilger
2000-05-04  2:28 ` dgould
2000-05-04  5:21   ` Michael Loftis
2000-05-04  2:38 ` Eric M. Hopper
2000-05-04 12:18 Shaw, Marco

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.21.0005022111490.956-100000@localhost.localdomain \
    --to=marco@nbnet.nb.ca \
    --cc=linux-lvm@e35.marxmeier.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).