On Fri, 13 Apr 2007 08:40:10 +0100, Neil Bothwick wrote:
equery --quiet --nocolor list --duplicates gentoo-sources | awk
'{print $1}' | head -n -2 | xargs --no-run-if-empty emerge
--unmerge /dev/null
Out of interest:
1) Why --duplicates (i.e. am I missing something ;).
On Monday 16 April 2007 15:00:30 Neil Bothwick wrote:
On Fri, 13 Apr 2007 08:40:10 +0100, Neil Bothwick wrote:
equery --quiet --nocolor list --duplicates gentoo-sources | awk
'{print $1}' | head -n -2 | xargs --no-run-if-empty emerge
--unmerge /dev/null
Out of interest:
1)
On Mon, 16 Apr 2007 15:06:54 +0200, Bo Ørsted Andresen wrote:
I remember now. If you have only one kernel installed, --duplicates
prevents it being uninstalled - quite a useful feature ;-)
head -n -2 would prevent that anyway. As well as preventing the
deletion from /boot and
On Fri, 13 Apr 2007 02:11:58 +0200, Bo Ørsted Andresen wrote:
equery --quiet --nocolor list --duplicates gentoo-sources | awk
'{print $1}' | head -n -2 | xargs --no-run-if-empty emerge --unmerge
/dev/null
Out of interest:
1) Why --duplicates (i.e. am I missing something ;).
No
Neil Bothwick wrote:
On Fri, 13 Apr 2007 01:33:43 +0200, Bo Ørsted Andresen wrote:
At around 300MB per kernel, that's ten excess kernels, so you can't
be doing it that often. Once you're happy with the current kernel,
you only need emerge -P gentoo-sources to remove the rest. I use
a script
Neil Bothwick wrote:
At around 300MB per kernel, that's ten excess kernels, so you can't be
doing it that often. Once you're happy with the current kernel, you only
need emerge -P gentoo-sources to remove the rest. I use a script that
removes all but the last two, and also cleans out
On Friday 13 April 2007 01:12:08 Anthony E. Caudel wrote:
At around 300MB per kernel, that's ten excess kernels, so you can't be
doing it that often. Once you're happy with the current kernel, you only
need emerge -P gentoo-sources to remove the rest. I use a script that
removes all but
On Fri, 13 Apr 2007 01:33:43 +0200, Bo Ørsted Andresen wrote:
At around 300MB per kernel, that's ten excess kernels, so you can't
be doing it that often. Once you're happy with the current kernel,
you only need emerge -P gentoo-sources to remove the rest. I use
a script that removes
On Friday 13 April 2007 01:59:47 Neil Bothwick wrote:
Provided you have gentoolkit something as simple as this works:
# emerge -Cva $(equery -q list gentoo-sources | head -n -2)
That only cleans out /usr/src, it's slightly different to what I use
(which rm's the directories first to speed
On Mon, 2 Apr 2007 01:02:32 -0400, Walter Dnes wrote:
I don't mind the 30 or 40 megs for the source tarball+patches in my
distfiles directory. But the quarter gig for each minor r bump, most
of which I never build, is a bit much.
Why install it if you're not going to build it?
r bumps are
On Mon, 2 Apr 2007 01:35:42 -0400, Walter Dnes wrote:
I got bitten in the latest stable kernel (2.6.19-r5). It moved SATA
support out of SCSI, and into a separate section altogether. I plowed
through make oldconfig, hitting N for every option. Because I have
a SATA drive, the result was
Hemmann, Volker Armin ha scritto:
In almost every kernel release a security problem is found, that is fixed in a
stable release.
Stable release? AFAIK, *all* 2.6.x releases are stable releases. The
days of double trees (2.4.x and 2.5.x) are gone.
Probably I don't get what you mean. I use x86
On Sonntag, 1. April 2007, b.n. wrote:
Hemmann, Volker Armin ha scritto:
In almost every kernel release a security problem is found, that is fixed
in a stable release.
Stable release? AFAIK, *all* 2.6.x releases are stable releases.
No, they aren't. There are the 'normal' releases (for
Hemmann, Volker Armin ha scritto:
On Sonntag, 1. April 2007, b.n. wrote:
Hemmann, Volker Armin ha scritto:
In almost every kernel release a security problem is found, that is fixed
in a stable release.
Stable release? AFAIK, *all* 2.6.x releases are stable releases.
No, they aren't. There
On Montag, 2. April 2007, b.n. wrote:
Hemmann, Volker Armin ha scritto:
On Sonntag, 1. April 2007, b.n. wrote:
Hemmann, Volker Armin ha scritto:
In almost every kernel release a security problem is found, that is
fixed in a stable release.
Stable release? AFAIK, *all* 2.6.x releases
On Sun, 1 Apr 2007 23:35:25 +0200, Hemmann, Volker Armin wrote:
1)I only see gentoo-sources-2.6.X-rY, I never see
gentoo-sources-2.6.X.a.b-rY .What am I installing when I install
gentoo-sources-2.6.x-rY?
look into the changelogs ;)
I don't use gentoo-sources, but AFAIK, the -rX
On Sat, Mar 31, 2007 at 09:21:22AM +0100, Neil Bothwick wrote
At around 300MB per kernel, that's ten excess kernels, so you can't be
doing it that often.
I ran df and ll between each individual unmerge. The individual
kernels take approx 250 megs, freshly emerged. Compiling generates
On Sat, Mar 31, 2007 at 04:11:42PM +0200, Hemmann, Volker Armin wrote
Which risk? Which mess? There is not a risk, if you use oldconfig.
With oldconfig, 99% of the updates seem to consist of added support
for exotic raid controllers or network cards. Since my system has been
running OK for
On Sat, 31 Mar 2007 01:55:10 -0400, Walter Dnes wrote:
Partial df output before unmerging a bunch of kernels
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda1 11726996 7325372 4401624 63% /
Partial df output after unmerging a bunch of
On Saturday 31 March 2007 00:55:10 Walter Dnes wrote:
Having gotten rather tired of doing this
manually... again... I went into /etc/portage/package.mask and added
sys-kernel/gentoo-sources-2.6.19-r5
It won't hurt me now, but is there anything that might depend on newer
kernels? It's
On Samstag, 31. März 2007, Walter Dnes wrote:
Partial df output before unmerging a bunch of kernels
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda1 11726996 7325372 4401624 63% /
Partial df output after unmerging a bunch of kernels
On Samstag, 31. März 2007, Boyd Stephen Smith Jr. wrote:
On Saturday 31 March 2007 00:55:10 Walter Dnes wrote:
Having gotten rather tired of doing this
manually... again... I went into /etc/portage/package.mask and added
sys-kernel/gentoo-sources-2.6.19-r5
It won't hurt me now, but
Hemmann, Volker Armin ha scritto:
besides critical bug fixes, security fixes and driver updates?
IMHO masking never kernels is a really bad idea.
Why? I upgrade my kernel once in a blue moon -that is, when I need to
because of new features I need, because of incompatibility with current
On Samstag, 31. März 2007, b.n. wrote:
Hemmann, Volker Armin ha scritto:
besides critical bug fixes, security fixes and driver updates?
IMHO masking never kernels is a really bad idea.
Why?
because of:
- filesystem bugs (2.6.17 and XFS for example)
- security problems (local and
Partial df output before unmerging a bunch of kernels
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda1 11726996 7325372 4401624 63% /
Partial df output after unmerging a bunch of kernels
Filesystem 1K-blocks Used Available Use%
25 matches
Mail list logo
