public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: Nuitari <nuitari@melchior.nuitari.net>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] initrd
Date: Sun, 30 Oct 2005 15:32:49 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0510301532220.4212@melchior.nuitari.net> (raw)
In-Reply-To: <200510301324.30816.xcourse97@charter.net>

I finally switched my only grub system to lilo yesterday.

On Sun, 30 Oct 2005, William Tetrault wrote:

> Date: Sun, 30 Oct 2005 13:24:30 -0600
> From: William Tetrault <xcourse97@charter.net>
> Reply-To: gentoo-amd64@lists.gentoo.org
> To: gentoo-amd64@lists.gentoo.org
> Subject: Re: [gentoo-amd64] initrd
> 
> I too have been on the amd64 platform since early last year, and am still
> using grub-static, although I know that grub now compiles fine for this
> platform (at least, that is what I've heard - I'm still using grub-static).
> But whether one uses grub or grub-static, the installed files are the same,
> and grub works the same regardless of which is chosen.  My grub.conf has not
> changed from when I was using Athlon XP's (although it's no longer called
> grub.lst).
>
> On Sunday 30 October 2005 12:07 pm, Dmitri Pogosyan wrote:
>> Actually, that reminds me that a year ago on amd64 architecture the
>> compiled grub did not work for me (it did compile but fail to boot) and I
>> had to use grub-static-0.93, which worked fine.  I looked now and see that
>> I still use this version of grub on all my amd64 machines.
>>
>>
>>
>> --
>> Dmitri Pogosyan            Department of Physics
>> Associate Professor        University of Alberta
>> tel 1-780-492-2150         412 Avadh Bhatia Physics Labs
>> fax 1-780-492-0714         Edmonton, AB, T6G 2J1, CANADA
>
-- 
gentoo-amd64@gentoo.org mailing list



  reply	other threads:[~2005-10-30 20:35 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-30 18:07 [gentoo-amd64] initrd Dmitri Pogosyan
2005-10-30 19:24 ` William Tetrault
2005-10-30 20:32   ` Nuitari [this message]
2005-10-31  9:52     ` DR GM SEDDON
2005-10-31 13:43     ` DR GM SEDDON
2005-10-31 16:39       ` Drake Donahue
2005-11-01 14:45         ` DR GM SEDDON
2005-11-01 17:31           ` Drake Donahue
2005-11-01 18:06             ` Drake Donahue
2005-11-02 12:38             ` DR GM SEDDON
2005-11-02 13:14               ` Harm Geerts
2005-10-31  9:47   ` DR GM SEDDON
  -- strict thread matches above, loose matches on Subject: below --
2005-10-31  0:56 Dmitri Pogosyan
2005-10-30 15:59 Dmitri Pogosyan
2005-10-30 15:59 Dmitri Pogosyan
2005-10-30 17:35 ` Karol Krizka
2005-10-31  9:33 ` DR GM SEDDON
2005-10-29 23:54 Dmitri Pogosyan
2005-10-29 23:49 Dmitri Pogosyan
2005-10-28 16:19 Dmitri Pogosyan
2005-10-29  6:12 ` Lee Thompson
2005-10-29 13:21 ` DR GM SEDDON
2005-10-29 13:29   ` Craig Webster
2005-10-29 14:16     ` DR GM SEDDON
2005-10-29 15:41       ` Karol Krizka
2005-10-30  9:48         ` DR GM SEDDON
2005-10-30 15:45           ` Karol Krizka
2005-10-30 17:38           ` William Tetrault
2005-10-29 16:40       ` Drake Donahue
2005-10-29 18:12         ` Drake Donahue
2005-10-29 17:15       ` William Tetrault
2005-10-31  1:23   ` bruce harding
2005-10-28 14:13 DR GM SEDDON
2005-10-28 14:54 ` Mark Knecht
2005-10-29 15:36 ` Hemmann, Volker Armin

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.64.0510301532220.4212@melchior.nuitari.net \
    --to=nuitari@melchior.nuitari.net \
    --cc=gentoo-amd64@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