public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Paul Hartman" <paul.hartman+gentoo@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Transferring an existing install to new disk
Date: Wed, 12 Nov 2008 11:58:22 -0600	[thread overview]
Message-ID: <58965d8a0811120958k121d4bcraa89441de8c12f27@mail.gmail.com> (raw)
In-Reply-To: <491B1777.8060505@gmail.com>

On Wed, Nov 12, 2008 at 11:50 AM, Dale <rdalek1967@gmail.com> wrote:
> Alan Mackenzie wrote:
>> Hi, Dirk, Hi, List!
>>
>> On Wed, Nov 12, 2008 at 09:59:09AM +0200, Dirk Uys wrote:
>>
>>> - Update the grub.conf to pass the correct root. (btw, does anyone use
>>> anything other than grub these days?)
>>>
>>
>> Yes.  I use LILO.  My lilo.conf traces its ancestry back to my original
>> Linux installation, SuSE 5.3.
>>
>> Why?  Because learning grub would take time.  Maybe not very much time,
>> but it would take some.  By contrast, although learning LILO took a very
>> great deal of time, that time is already spent, and can never more be got
>> back.  Putting an extra entry into lilo.conf and regenerating the boot
>> loader now takes, at most, a few minutes.
>>
>> But if the motivation of your question is simplifying Gentoo by leaving
>> out LILO, that wouldn't bother me at all.  While I've still got a Debian
>> on my PC, I can use it to lie low, and when I need to learn grub, no big
>> deal.  In fact, by the time I get to learn grub, it will, in its turn,
>> probably have been superseded by something else.  :-)
>>
>>
>>> Regards
>>> Dirk
>>>
>>
>>
>
>
> I started out with Lilo too. I can't recall why I switched but I did.
> Grub is so much easier than Lilo. I have no regrets with switching and
> would only use Lilo if it was all that was available.
>
> The biggest thing to learn is the way the drives are listed. It uses
> (hd0,0) and such. It's really not that hard once you get how it does it.
> Also, it is real easy to switch to a older kernel at the grub boot
> screen. Just edit the boot line and let it rip. You can also edit other
> options for the boot line but changing kernels is the big one for me.
>
> It's a thought.

I have my grub menu set up with 2 kernel choices; one points
to/vmlinuz and the other points to /vmlinuz.old, that way i don't ever
have to edit anything. Comes in handy if the new kernel blows up :)



  reply	other threads:[~2008-11-12 17:58 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-12  7:35 [gentoo-user] Transferring an existing install to new disk Harry Putnam
2008-11-12  7:59 ` Dirk Uys
2008-11-12  9:52   ` Garry Smith
2008-11-12 10:22     ` Daniel Pielmeier
2008-11-12 14:54   ` Alan Mackenzie
2008-11-12 17:50     ` Dale
2008-11-12 17:58       ` Paul Hartman [this message]
2008-11-12 18:20         ` Dale
2008-11-13  8:18     ` Dirk Uys
2008-11-12 10:35 ` Neil Bothwick
2008-11-12 14:03   ` [gentoo-user] " Harry Putnam
2008-11-12 14:53     ` Neil Bothwick
2008-11-12 15:51       ` Harry Putnam
2008-11-12 16:20         ` Neil Bothwick
2008-11-12 17:56           ` Harry Putnam
2008-11-12 17:58         ` Dale
2008-11-13 10:54       ` Peter Humphrey
2008-11-12 19:55 ` [gentoo-user] " Michele Schiavo

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=58965d8a0811120958k121d4bcraa89441de8c12f27@mail.gmail.com \
    --to=paul.hartman+gentoo@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /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