From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: gcc 4.7.3 --> 4.8.3
Date: Wed, 12 Nov 2014 10:18:02 +0000 [thread overview]
Message-ID: <20141112101802.4590d382@hactar.digimed.co.uk> (raw)
In-Reply-To: <loom.20141112T030631-267@post.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1889 bytes --]
On Wed, 12 Nov 2014 02:07:23 +0000 (UTC), James wrote:
> > No, simply log out of the desktop and back in.
>
> Um, Tomas's little one-liner:
> lsof -n | grep 'DEL.*lib'
>
> revealed far to much to deal with. I got lib issues coming out of my
> arse (I've been hacking at a few things I do not fully understand
> (wink wink :: nudge nudge) ?
Oh yes, there are times when a reboot is the simplest option, it makes
sure everything is back as baseline. I have no problem with rebooting,
just wouldn't recommend the worldwide recompile that leads to the need to
do so - unless it is necessary, which is clearly is not in the case of
the GCC 4.7 -> 4.8 switch. I run ~arch on my desktop, so most things will
be recompiled in the next few weeks anyway.
> > Yes, things may be a little different with 4.9, but the last time a
> > rebuild was really required was,AFAIR, somewhere around 3.3.
> OK, so I reboot workstations more often than you. I hope that does
> not upset you?
As long as they are your workstations and not mine,m it doesn't upset me
in the least ;-)
> Yes, I've kept workstations online for over a year more
> times that I can count (fingers and toes). And when the reboot comes,
> It's a day or 2 fixing things, imho. YMMV.
Not by much. Severs may stay up for a while but desktops tend to be
rebooted quite often after kernel updates.
> A judicious reboot now and
> again, timed well, is keenly a good idea, imho. ymmv. Besides I'm an
> old FT via redundancy, kind of guy; aka I *always* have spare systems,
> ready to go.
As a fully paid up member of the Old Farts Club, I can appreciate that.
> I deeply appreciate your concerns over the admin skills of an
> old_fart.... RFC 5798.
I don't see how that RFC relates to being an old fart...
--
Neil Bothwick
I backed up my hard drive and ran into a bus.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2014-11-12 10:18 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-07 17:46 [gentoo-user] gcc 4.7.3 --> 4.8.3 James
2014-11-07 18:19 ` Mark Pariente
2014-11-08 19:08 ` Stefan G. Weichinger
2014-11-08 22:39 ` Volker Armin Hemmann
2014-11-07 19:01 ` Todd Goodman
2014-11-08 16:17 ` [gentoo-user] " Nikos Chantziaras
2014-11-08 19:55 ` James
2014-11-09 9:59 ` Peter Humphrey
2014-11-10 18:52 ` James
2014-11-10 22:23 ` Neil Bothwick
2014-11-11 6:04 ` Tomas Mozes
2014-11-11 21:12 ` James
2014-11-11 9:51 ` Dale
2014-11-11 20:19 ` James
2014-11-11 21:03 ` Neil Bothwick
2014-11-11 21:27 ` Mick
2014-11-12 2:07 ` James
2014-11-12 10:18 ` Neil Bothwick [this message]
2014-11-14 4:52 ` Jonathan Callen
2014-11-14 9:55 ` Neil Bothwick
2014-11-12 5:58 ` Dale
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=20141112101802.4590d382@hactar.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