From: Colin Morey <peitolm@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Build Doc Error
Date: 14 Jun 2002 22:18:58 +0100 [thread overview]
Message-ID: <1024089539.3494.6.camel@koch.random-chaos.org.uk> (raw)
In-Reply-To: <200206141552.34781.dougg@ufl.edu>
On Fri, 2002-06-14 at 20:52, Doug Goldstein wrote:
> Works perfectly fine the doc way and I think you wanted the splashimage to be
> without the /boot but you didn't type that. However I like it the doc way
> with /boot in there. Makes it a bit more clear to look at.
>
indeed, the docs way is clearer imho, and if you look closely, there is
a symlink in /boot pointing back to /boot (/boot/boot-> /boot) it's a
hack, but it's a clean one, and one that makes a lot of sense.(other
wise many people could easily get confused.
> -Doug
>
> On Friday 14 June 2002 03:21 pm, Hanford_Smith, Jason wrote:
> > Code Listing 40
> >
> > The following two lines have errors:
> >
> > splashimage=(hd0,0)/boot/grub/splash.xpm.gz
> >
> > should be
> >
> > splashimage=(hd0,0)/boot/grub/splash.xpm.gz
> >
> >
> > and
> >
> > kernel /boot/bzImage root=/dev/hda3
> >
> > should be
> >
> > kernel /bzImage root=/dev/hda3
> >
> >
> > Reason: Both file references are relative to (hd0,0) which is already /boot
> >
> >
> > --Jason
> > _______________________________________________
> > gentoo-dev mailing list
> > gentoo-dev@gentoo.org
> > http://lists.gentoo.org/mailman/listinfo/gentoo-dev
>
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@gentoo.org
> http://lists.gentoo.org/mailman/listinfo/gentoo-dev
>
next prev parent reply other threads:[~2002-06-14 23:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-14 19:21 [gentoo-dev] Build Doc Error Hanford_Smith, Jason
2002-06-14 19:52 ` Doug Goldstein
2002-06-14 21:18 ` Colin Morey [this message]
2002-06-15 7:42 ` Mario Witt
2002-06-15 14:06 ` orange-pc.ces.clemson.edu
2002-06-16 10:05 ` Ryan Phillips
2002-06-15 5:02 ` orange-pc.ces.clemson.edu
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=1024089539.3494.6.camel@koch.random-chaos.org.uk \
--to=peitolm@gentoo.org \
--cc=gentoo-dev@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