From: Joost Roeleveld <joost@antarean.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] IPv6 not ready here; Hmmm
Date: Fri, 10 Jun 2011 15:17:46 +0200 [thread overview]
Message-ID: <1411735.7Wzxds3ylK@eve> (raw)
In-Reply-To: <BANLkTinC+ZJL529jSUGdb8t40cuoZQx8hA@mail.gmail.com>
On Friday 10 June 2011 17:08:40 Pandu Poluan wrote:
> On Fri, Jun 10, 2011 at 14:22, Joost Roeleveld <joost@antarean.org> wrote:
> > On Friday 10 June 2011 08:52:15 Pandu Poluan wrote:
> >> -original message-
> >> Subject: Re: [gentoo-user] IPv6 not ready here; Hmmm
> >> From: Paul Hartman <paul.hartman+gentoo@gmail.com>
> >> Date: 2011-06-10 03:52
> >>
> >> >And another bonus is that there are plenty of
> >>
> >> funny things we can spell in hexadecimal. ;)
> >>
> >> While I'm sure I'll tag the C001:D00D address for my workstation, I'm
> >> not sure upper management will appreciate me naming some servers
> >> DEAD:BEEF or BAD:D06 or A55:401E ... :-P
> >
> > If you don't tell them and, when they do notice, tell them that changing
> > the IPs is not recommended due to possible issues with the installed
> > software, you might get away with that.
> >
> > Although, why reserve those for servers instead of said management? ;)
>
> There's playing with fire, and there's playing with FIRE. :D
Considering I regularly play with Nitro mixtures and sharp blades spinning
around through the air, playing with FIRE isn't too bad :)
Besides, how many managers do you have that actually check the IP-addresses
the DHCP server gives their machines "randomly"? :)
--
Joost
next prev parent reply other threads:[~2011-06-10 14:07 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-10 1:52 [gentoo-user] IPv6 not ready here; Hmmm Pandu Poluan
2011-06-10 7:22 ` Joost Roeleveld
2011-06-10 10:08 ` Pandu Poluan
2011-06-10 13:17 ` Joost Roeleveld [this message]
2011-06-10 14:30 ` Alan McKinnon
2011-06-10 15:59 ` Joost Roeleveld
2011-06-10 16:04 ` Paul Hartman
-- strict thread matches above, loose matches on Subject: below --
2011-06-09 1:52 Pandu Poluan
2011-06-08 1:27 Dale
2011-06-08 1:53 ` Dale
2011-06-08 2:18 ` Adam Carter
2011-06-08 5:31 ` Mick
2011-06-08 17:01 ` Volker Armin Hemmann
2011-06-08 18:59 ` Dale
2011-06-09 3:25 ` Volker Armin Hemmann
2011-06-09 4:56 ` Dale
2011-06-09 6:59 ` Volker Armin Hemmann
2011-06-08 19:51 ` Paul Hartman
2011-06-08 22:04 ` Mick
2011-06-09 1:25 ` Paul Hartman
2011-06-09 5:46 ` Mick
2011-06-09 15:06 ` Paul Hartman
2011-06-09 15:51 ` Paul Hartman
2011-06-09 20:27 ` Mick
2011-06-09 20:52 ` Paul Hartman
2011-06-09 11:16 ` Tanstaafl
2011-06-09 14:23 ` Mick
2011-06-09 16:21 ` Paul Hartman
2011-06-08 19:45 ` Paul Hartman
2011-06-08 20:08 ` Alan McKinnon
2011-06-08 20:01 ` Paul Hartman
2011-06-09 2:15 ` Dale
2011-06-09 3:23 ` Pandu Poluan
2011-06-09 4:50 ` Dale
2011-06-09 5:14 ` Paul Hartman
2011-06-09 6:52 ` Dale
2011-06-09 7:46 ` Alan McKinnon
2011-06-09 8:48 ` Dale
2011-06-10 15:46 ` Dale
2011-06-10 16:03 ` Paul Hartman
2011-06-10 17:39 ` 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=1411735.7Wzxds3ylK@eve \
--to=joost@antarean.org \
--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