From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Re: Kernel not updating...
Date: Thu, 16 Feb 2006 23:45:02 +0000 [thread overview]
Message-ID: <20060216234502.551b480b@krikkit.digimed.co.uk> (raw)
In-Reply-To: <dt2qfr$4pl$1@sea.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 681 bytes --]
On Thu, 16 Feb 2006 21:24:01 +0000, Mick wrote:
> > Looks like this was it. I had it in the /etc/portage/rsync_excludes
> > file. Not really sure why. Guess I'll find out when something breaks
> > after I boot to the new kernel. ;-)
>
> I know why: to stop using loads of bandwidth and disk space to
> download and save the latest kernel sources, when you may not yet want
> to compile a new kernel? ;-)
It only stops you downloading the latest kernel ebuilds, only a few KB.
You don't download the sources until you emerge the package (or world).
--
Neil Bothwick
You are about to give someone a piece of your mind,
something you can ill afford...
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 191 bytes --]
next prev parent reply other threads:[~2006-02-16 23:58 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-16 17:07 [gentoo-user] Kernel not updating gentuxx
2006-02-16 17:29 ` Daniel da Veiga
2006-02-16 18:35 ` gentuxx
2006-02-16 19:03 ` Bo Andresen
2006-02-16 19:16 ` Daniel da Veiga
2006-02-16 20:24 ` [gentoo-user] " Mick
2006-02-16 20:48 ` gentuxx
2006-02-16 21:24 ` [gentoo-user] " Mick
2006-02-16 23:45 ` Neil Bothwick [this message]
2006-02-16 19:53 ` [gentoo-user] " gentuxx
2006-02-16 21:15 ` Neil Bothwick
2006-02-16 21:46 ` Bo Andresen
2006-02-16 22:24 ` gentuxx
2006-02-16 23:43 ` Neil Bothwick
2006-02-16 19:16 ` [gentoo-user] " james
2006-02-16 19:44 ` gentuxx
2006-02-16 19:21 ` [gentoo-user] " Holly Bostick
2006-02-16 19:41 ` gentuxx
2006-02-16 20:07 ` Neil Bothwick
2006-02-16 20:26 ` gentuxx
2006-02-16 20:52 ` Daniel da Veiga
2006-02-16 21:23 ` Nick Rout
2006-02-17 2:05 ` Ernie Schroder
2006-02-17 9:43 ` Neil Bothwick
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=20060216234502.551b480b@krikkit.digimed.co.uk \
--to=neil@digimed.co.uk \
--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