From: "Pete" <pi2list@pi2tech.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] system boot
Date: 27 Feb 2006 00:30:03 -0000 [thread overview]
Message-ID: <20060227003003.3595.qmail@yourcakes.com> (raw)
In-Reply-To: <>
Duh ! I didn't notice this. I am working on gentoo for the first time and
the other flavor has /boot auto mounted.
Thanks a ton !
Regards
Pete
On Mon, 27 Feb 2006 09:40:42 +0930, Iain Buchanan <iaindb@netspace.net.au>
wrote :
> Hi,
>
> On Sun, 2006-02-26 at 23:51 +0000, Pete wrote:
> > This is what I don't understand
> >
> > ------------------
> >
> > yababa root # ls -l /boot/
> > total 1272
> > -rw-r--r-- 1 root root 483904 Feb 26 04:56
System.map-2.4.19r10AR
> > lrwxrwxrwx 1 root root 1 Jan 12 2003 boot -> .
> > -rw-r--r-- 1 root root 814688 Feb 26 04:40 bzImageAR
> > yababa root #
> >
> > ---------------------
> >
> > boot points to itself. Before I copied the System.map-2.4.19r10AR and
> > bzImageAR, there was nothing in there.
> >
> > How does the system boot? ? ?
>
> you need to mount /boot. Before you do that, delete (or move) the files
> that you put in (the unmounted) /boot! /boot isn't mounted by default.
>
> Once you've mounted /boot, you should see lots of stuff in there.
>
> HTH,
> --
> Iain Buchanan <iain at netspace dot net dot au>
>
> If it happens once, it's a bug.
> If it happens twice, it's a feature.
> If it happens more than twice, it's a design philosophy.
>
> --
> gentoo-user@gentoo.org mailing list
>
>
>
>
--
gentoo-user@gentoo.org mailing list
next reply other threads:[~2006-02-27 0:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-27 0:30 Pete [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-02-27 0:27 [gentoo-user] system boot Pete
2006-02-26 23:51 Pete
2006-02-26 23:57 ` Brett I. Holcomb
2006-02-27 0:02 ` Boyd Stephen Smith Jr.
2006-02-27 0:10 ` Iain Buchanan
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=20060227003003.3595.qmail@yourcakes.com \
--to=pi2list@pi2tech.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