From: Pacho Ramos <pacho@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] rfc: netplugd and ifplugd support in OpenRc
Date: Wed, 12 Sep 2012 19:45:44 +0200 [thread overview]
Message-ID: <1347471944.2365.2.camel@belkin4> (raw)
In-Reply-To: <505083BE.60305@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1856 bytes --]
El mié, 12-09-2012 a las 08:44 -0400, Ian Stakenvicius escribió:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> On 11/09/12 06:23 PM, Rich Freeman wrote:
> > On Tue, Sep 11, 2012 at 5:01 PM, William Hubbs
> > <williamh@gentoo.org> wrote:
> >>
> >> I can agree that a server would probably want a static
> >> configuration, but all work stations do not use gnome, kde, etc.
> >>
> >
> > Most do not run unix, but at work I can't think of any servers
> > that are using static configurations. They might be assigned
> > static IPs, but they'll use DHCP just the same.
> >
> > I deploy my network at home in the same way - most of my standing
> > PCs have DNS and static IP assignments, but they still use DHCP.
> > This way I can still utilize PXE for backups/etc, and adjust things
> > at any time fairly easily.
> >
> > Rich
> >
>
> Some of my servers have a back-end nic that has static config defined,
> and i use netplug or ifplugd for that to bring the iface up and down
> based on link -- link detection != auto-configuration, imo.
>
> Suffice to say, networkmanager is not a reasonable means to determine
> link state for oldnet. Newnet, well, all of that gets handled outside
> of openrc's config anyhow so...
>
> But this is getting a little beyond the original point of the thread.. :)
>
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.19 (GNU/Linux)
>
> iF4EAREIAAYFAlBQg74ACgkQ2ugaI38ACPAL5gEArhYn4Zzas8k6ijddwP9F4q+F
> 95hFTjw9h0lp0nIrrDIA/R6twsmCnPt1T7yYN6jr0ZcjBonZgI+pk3TZS9qnLa/U
> =dJUq
> -----END PGP SIGNATURE-----
>
>
Also my father has two machines in his job with static config and
ifplugd to detect link up/down. I also remember to migrate years ago
from netplugd to ifplugd for some reason I can't remember now, probably
ifplugd worked better :/
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2012-09-12 17:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-10 14:48 [gentoo-dev] rfc: netplugd and ifplugd support in OpenRc William Hubbs
2012-09-10 20:05 ` David Leverton
2012-09-11 13:15 ` Ian Stakenvicius
2012-09-10 20:26 ` Olivier Crête
2012-09-10 21:05 ` William Hubbs
2012-09-11 18:01 ` Luca Barbato
2012-09-11 18:43 ` Olivier Crête
2012-09-11 21:01 ` William Hubbs
2012-09-11 22:23 ` Rich Freeman
2012-09-12 12:44 ` Ian Stakenvicius
2012-09-12 17:45 ` Pacho Ramos [this message]
2012-09-10 21:47 ` Christopher Head
2012-09-10 22:54 ` William Hubbs
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=1347471944.2365.2.camel@belkin4 \
--to=pacho@gentoo.org \
--cc=gentoo-dev@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