From: 320095285153-0001@t-online.de (Achim Gottinger)
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] issues with installing a new kernel
Date: Tue Feb 6 19:22:01 2001 [thread overview]
Message-ID: <3A80AAEA.C1199B30@gottinger.de> (raw)
In-Reply-To: 20010206112424.C27453@cvs.gentoo.org
drobbins@gentoo.org wrote:
> On Tue, Feb 06, 2001 at 10:47:51AM -0700, Pete Gavin wrote:
> > Hi,
> >
> > I found a couple of issues with installing a new kernel...
> >
> > First of all, I accidently installed the package w/o first mounting
> > /boot. So, after I rebooted, grub loaded the old kernel, since it
> > wasn't overwritten by the new one. I don't know if it would be a good
> > idea to mount /boot from the ebuild script, but we should maybe add
> > some kind of warning to it to at least remind people of it. Second, I
> > *do* think it would be a good idea to add depmod -a {kernel_version}
> > to the ebuild script, since this only changes stuff in the new module
> > directory, which just got installed anyways. What do you guys think?
>
> I think it would be good if the /boot mounted check were done in the
> pkg_preinst() function, which gets called right before a merge.
>
But a /boot partition is not neccesary.
> Yes, it's fine to call depmod -a; if possible, find a way to make it
> work with ${ROOT} so that we can merge to non-root filesystems and
> have depmod operate on the correct set of modules.
achim~
>
>
> Thanks again,
>
> --
> Daniel Robbins <drobbins@gentoo.org>
> President/CEO http://www.gentoo.org
> Gentoo Technologies, Inc.
>
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@gentoo.org
> http://www.gentoo.org/mailman/listinfo/gentoo-dev
next prev parent reply other threads:[~2001-02-07 2:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-06 10:48 [gentoo-dev] issues with installing a new kernel Pete Gavin
2001-02-06 11:25 ` drobbins
2001-02-06 19:22 ` Achim Gottinger [this message]
2001-02-06 20:10 ` Pete Gavin
2001-02-06 20:37 ` Achim Gottinger
2001-02-06 20:43 ` Pete Gavin
2001-02-06 20:53 ` Achim Gottinger
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=3A80AAEA.C1199B30@gottinger.de \
--to=320095285153-0001@t-online.de \
--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