Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #176326
| From | <tomas@tuxteam.de> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: hotpluggable member of a bridge |
| Date | 2017-01-05 10:30 +0100 |
| Message-ID | <sWcwW-Vl-35@gated-at.bofh.it> (permalink) |
| References | <sW74d-5AZ-13@gated-at.bofh.it> <sWcdz-Is-7@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thu, Jan 05, 2017 at 10:07:59AM +0100, Nicolas George wrote: > Le quintidi 15 nivôse, an CCXXV, Stefan Monnier a écrit : > > Is there something better? Like a predefined way to just say that when > > `usb0` appears, it should be added to `br0` (and ideally, this would > > also `ifup` the `br0` interface if it's not up yet). > > Not with /etc/network/interfaces and ifupdown, but udev can do all that. I always thought this is a division of labor between udev (generating a "hotplug event", like "eth0 link went just up" and ifupdown, declaring what has to happen (cf. the "allow-hotplug" directive). But I must admit I never looked to deeply into that to be authoritative. The docs [1] seem to suggest that, though. Of course, udev would be involved for other network management systems too, like NM: ideally, udev just dispatches and normalizes kernel events and delegates to specialized subsystems. In a pinch you can just sneak a complete shell script in an udev rule (and I'm guilty of having done such a thing [2]), but doing this as "system architecture" might lead to madness :-) [1] https://www.debian.org/doc/manuals/debian-reference/ch05.en.html [2] Once, for a customer: inserting the right storage medium (with the right UUID) triggered a system backup. regards - -- t -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlhuEdwACgkQBcgs9XrR2kZtowCfb0Glm/fJD9ByArT9nkGMmh4L 7NkAn2L0r4w7NeYa4E7PgK1BguWM7oZK =VqAG -----END PGP SIGNATURE-----
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
hotpluggable member of a bridge Stefan Monnier <monnier@iro.umontreal.ca> - 2017-01-05 04:40 +0100
Re: hotpluggable member of a bridge Nicolas George <george@nsup.org> - 2017-01-05 10:10 +0100
Re: hotpluggable member of a bridge <tomas@tuxteam.de> - 2017-01-05 10:30 +0100
Re: hotpluggable member of a bridge Michael Biebl <biebl@debian.org> - 2017-01-05 16:30 +0100
Re: hotpluggable member of a bridge Sven Hartge <sven@svenhartge.de> - 2017-01-06 03:00 +0100
Re: hotpluggable member of a bridge <tomas@tuxteam.de> - 2017-01-06 09:40 +0100
Re: hotpluggable member of a bridge Stefan Monnier <monnier@iro.umontreal.ca> - 2017-01-05 16:30 +0100
Re: hotpluggable member of a bridge Nicolas George <george@nsup.org> - 2017-01-05 16:40 +0100
Re: hotpluggable member of a bridge Stefan Monnier <monnier@IRO.UMontreal.CA> - 2017-01-05 18:30 +0100
Re: Congratulations Danielle , Your Roof is Covered - FREE!GYfb Danielle Gregory <danielle.k.gregory@gmail.com> - 2017-01-05 22:10 +0100
Re: Congratulations Aileen , Your Roof is Covered - FREE!PHYi tazzygirl tazzygirl <saratazmtz77@gmail.com> - 2017-01-05 22:10 +0100
RE: Congratulations Emmanuel , Your Roof is Covered - FREE!44OO Jennyetta Washington <manolofimbres@gmail.com> - 2017-01-05 22:20 +0100
Re: hotpluggable member of a bridge Reco <recoverym4n@gmail.com> - 2017-01-05 17:10 +0100
Re: hotpluggable member of a bridge Joshua Schaeffer <jschaeffer0922@gmail.com> - 2017-01-05 17:20 +0100
Re: hotpluggable member of a bridge Reco <recoverym4n@gmail.com> - 2017-01-05 17:40 +0100
Re: hotpluggable member of a bridge Joshua Schaeffer <jschaeffer0922@gmail.com> - 2017-01-05 18:10 +0100
Re: hotpluggable member of a bridge Pascal Hambourg <pascal@plouf.fr.eu.org> - 2017-01-05 22:20 +0100
Re: hotpluggable member of a bridge Pascal Hambourg <pascal@plouf.fr.eu.org> - 2017-01-05 22:30 +0100
Re: hotpluggable member of a bridge Reco <recoverym4n@gmail.com> - 2017-01-05 22:40 +0100
Re: hotpluggable member of a bridge Pascal Hambourg <pascal@plouf.fr.eu.org> - 2017-01-08 16:50 +0100
Re: hotpluggable member of a bridge Reco <recoverym4n@gmail.com> - 2017-01-08 17:20 +0100
Re: hotpluggable member of a bridge Pascal Hambourg <pascal@plouf.fr.eu.org> - 2017-01-08 18:00 +0100
Re: hotpluggable member of a bridge Stefan Monnier <monnier@iro.umontreal.ca> - 2017-01-06 02:20 +0100
Re: hotpluggable member of a bridge Reco <recoverym4n@gmail.com> - 2017-01-06 12:40 +0100
Re: hotpluggable member of a bridge Reco <recoverym4n@gmail.com> - 2017-01-06 13:20 +0100
Re: hotpluggable member of a bridge Pascal Hambourg <pascal@plouf.fr.eu.org> - 2017-01-08 17:00 +0100
Re: hotpluggable member of a bridge Reco <recoverym4n@gmail.com> - 2017-01-08 17:20 +0100
Re: hotpluggable member of a bridge Reco <recoverym4n@gmail.com> - 2017-01-08 17:30 +0100
Re: hotpluggable member of a bridge Pascal Hambourg <pascal@plouf.fr.eu.org> - 2017-01-08 17:30 +0100
Re: hotpluggable member of a bridge Stefan Monnier <monnier@iro.umontreal.ca> - 2017-01-06 22:50 +0100
Re: hotpluggable member of a bridge Jonathan Dowland <jmtd@debian.org> - 2017-01-06 18:20 +0100
csiph-web