From: John Mylchreest <johnm@gentoo.org>
To: Greg KH <gregkh@gentoo.org>
Cc: Nathaniel McCallum <npmccallum@gentoo.org>,
John Nilsson <john@milsson.nu>,
gentoo-dev@lists.gentoo.org, gentoo-core@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: [gentoo-core] Re: [gentoo-dev] GLEP 26 -- Handling kernels with portage
Date: Wed, 05 May 2004 17:33:36 +0100 [thread overview]
Message-ID: <1083774815.9596.45.camel@johnm.willow.local> (raw)
In-Reply-To: <20040503162246.GA32549@kroah.com>
[-- Attachment #1: Type: text/plain, Size: 996 bytes --]
On Mon, 2004-05-03 at 17:22, Greg KH wrote:
> > > How would this system update the bootmgr?
> > I purposely left this out of the GLEP as it is would be a much more hot
> > topic.
>
> ???
>
> That's the easiest thing to do, and something that I'm pretty amazed
> Gentoo has not implemented yet, as all other distros already come with a
> simple script that handles this functionality (works with different boot
> loaders too...)
I havent yet read on from this email in the thread, but fyi - I have a
working system to do this with grub/lilo. it is "modular" so would work
with any other. It can just be tagged into this system or any other.
I shall dig it out and email it it/commit it/do somethign with it
--
Regards
John Mylchreest
Gentoo Linux: http://www.gentoo.org
Public Key: gpg --recv-keys 0xEAB9E721
Key fingerprint: 0670 E5E4 F461 806B 860A 2245 A40E 72EB EAB9 E721
Web: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xEAB9E721
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-05-05 16:33 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-03 2:04 [gentoo-dev] GLEP 26 -- Handling kernels with portage Nathaniel McCallum
2004-05-03 2:45 ` [gentoo-dev] Re: [gentoo-core] " Greg KH
2004-05-03 2:54 ` Nathaniel McCallum
2004-05-03 3:06 ` [gentoo-dev] " Greg KH
2004-05-03 3:18 ` [gentoo-dev] Re: [gentoo-core] " Nathaniel McCallum
2004-05-03 3:32 ` [gentoo-dev] " Greg KH
2004-05-03 3:39 ` [gentoo-dev] Re: [gentoo-core] " Nathaniel McCallum
2004-05-03 17:17 ` Greg KH
2004-05-03 17:36 ` Nathaniel McCallum
2004-05-06 11:31 ` Duncan
2004-05-06 12:22 ` John Nilsson
2004-05-03 2:56 ` [gentoo-dev] Re: [gentoo-core] " Nathaniel McCallum
2004-05-03 3:56 ` [gentoo-dev] " Greg KH
2004-05-03 4:29 ` [gentoo-dev] Re: [gentoo-core] " Nathaniel McCallum
2004-05-03 5:40 ` John Nilsson
2004-05-03 6:04 ` Nathaniel McCallum
2004-05-03 10:12 ` Stuart Herbert
2004-05-03 10:18 ` Todd Berman
2004-05-03 11:18 ` Stuart Herbert
2004-05-03 12:12 ` Patrick Börjesson
2004-05-03 14:51 ` Andrew Gaffney
2004-05-03 15:20 ` Nathaniel McCallum
2004-05-03 15:16 ` Nathaniel McCallum
2004-05-03 16:22 ` Greg KH
2004-05-05 16:33 ` John Mylchreest [this message]
2004-05-05 16:43 ` Ciaran McCreesh
[not found] ` <20040502222039.45139edd@traam-ii>
2004-05-03 22:02 ` [gentoo-dev] " Greg KH
2004-05-03 8:57 ` [gentoo-dev] " Ciaran McCreesh
2004-05-03 14:46 ` [gentoo-dev] Re: [gentoo-core] " Nathaniel McCallum
2004-05-03 10:09 ` Stuart Herbert
2004-05-03 15:15 ` Nathaniel McCallum
2004-05-03 16:36 ` Stuart Herbert
2004-05-03 22:48 ` John Nilsson
2004-05-05 1:16 ` N. Owen Gunden
2004-05-05 1:42 ` John Nilsson
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=1083774815.9596.45.camel@johnm.willow.local \
--to=johnm@gentoo.org \
--cc=gentoo-core@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=gregkh@gentoo.org \
--cc=john@milsson.nu \
--cc=npmccallum@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