Lol, that's not ugly. Ugly is taking out a feature in a program that many have come to rely on without even documenting it on the change log.
Ugly is doing so because it might generate more emails about support on scripts that they have no control over because obviously it takes too long to ask "list the contents of the pre-up, pre-down folders here, to make sure there isn’t something new in there that might be timing out." Ugly is saying that if you need to get something done that was previously in those folders, you need to do it somewhere else, without suggesting an option. Ugly is also expecting those scripts or commands that someone has been relying on, that load at a specific phase, that might impact security, to be moved somewhere else so that it's not their problem (yes, I know, it was never their problem, but rather the user/admin). The scripts/commands still need to be loaded, they could still time out, but now they won't hear about it so problem solved? Very ugly is doing all of the above on an operating system that has been looked down upon by many before because it simply "is not windows" (read dumbbed down or "user friendly") while at the same time having the best record for reliability. When so many (including I) have come to love, and prefer this snappy, reliable? and customizable? OS (which frankly is a hell of a lot more "user friendly" now, to the point where if there were more games/commercial apps being developed for it I would ditch Windows in a heartbeat) and encounter things like this, is quite disappointing. Very hard to defend it when its best quality is being "community driven" and customizable and that is obviously not true in this case. Hell if all linux devs think this way then Grub needs to go away because it might not load one of the images or it might time-out. Take out startup scripts before logon, after logon, or on Desktop load for the same reason, I'm sure they will get less emails/bugs that way. As a matter of fact take out all possible scripts from loading at any time...just give us a hardcoded OS, wait, don’t they call that Windows? Nope, they actually have startup scripts...see a pattern yet? This email has gone on for way too long and a bit (ok, a lot) of frustration is showing. I appreciate the work of the developers, especially when it's done without any retribution other than the appreciation of the users. I really love the open source mentality and community, so please do not get offended or mad at my ranting. In the spirit of being "open" I had to vent and give my $20.50 (all out of two cents). I apologize if I seem a bit bitter and strong about it, I could be wrong about all of it. I have been wrong many times before. Thank you, Marlon -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of JoeDuncan Sent: Friday, December 11, 2009 10:10 AM To: [email protected] Subject: Re: [Bug 336736] Re: NetworkManager does not call /etc/network/if-pre-up.d scripts Eric, I think you have missed the point. Using "pre-up" scripts is what this bug is about. "pre-up" script functionality has been removed. Marlon was asking to how to load iptable configs before an interface comes up without using "pre-up" scripts. I had a similar issue, but the only thing I could think of was to hand-edit the if-up scripts to do what I want - now that's ugly. On Thu, Dec 10, 2009 at 7:14 AM, Eric Carvalho <[email protected]>wrote: > A (ugly) work around is to use the loopback pre-up script. > > /etc/network/interfaces: > > auto lo > iface lo inet loopback > pre-up /path/to/script > > > That way I was able to change my MAC address before the ethX get up. > I think this could be used to load firewall rules as well. > > Definitely, this job should be done by NM. > > -- > NetworkManager does not call /etc/network/if-pre-up.d scripts > https://bugs.launchpad.net/bugs/336736 > You received this bug notification because you are a direct subscriber > of the bug. > > Status in “network-manager” package in Ubuntu: Won't Fix > > Bug description: > Binary package hint: network-manager > > Ubuntu 8.10, Linux 2.6.27-12-generic #1 SMP Thu Feb 5 09:26:35 UTC 2009 > i686 GNU/Linux > NetworkManager 0.7~~svn20081018t105859-0ubuntu1.8.10.1 > > I've been trying to get a script to trigger on the "pre-up" phase of > network configuration, however, NetworkManager doesn't seem to call it's > dispatcher for "pre-up" or "post-down" events. > > None of the scripts I put in /etc/network/if-pre-up.d ever got called, so I > added the following line to the top of the dispatcher script > "/etc/NetworkManager/dispatcher.d/01ifupdown": > > logger -t $0 "called with $1 $2" > > Where $0 is the name of the script, $1 is the network interface and $2 is > the network event. > > After bringing some network connections up and down, I checked the logs, > and NetworkManager doesn't seem to be calling > "/etc/NetworkManager/dispatch.d/01ifupdown" for either "pre-up" or > "post-down" events. The only entries that show up are for "up" and "down" > events. > > According to the changelog both "pre-up" and "post-down" events are > supposed to be supported as of version 0.5.1-0ubuntu12: > > https://launchpad.net/ubuntu/+source/network-manager > > To unsubscribe from this bug, go to: > > https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/336736/+subscribe > -- Joe Duncan PhD Program, Psychology Queen's University [email protected] (647)216-9135 -- NetworkManager does not call /etc/network/if-pre-up.d scripts https://bugs.launchpad.net/bugs/336736 You received this bug notification because you are a direct subscriber of the bug. Status in “network-manager” package in Ubuntu: Won't Fix Bug description: Binary package hint: network-manager Ubuntu 8.10, Linux 2.6.27-12-generic #1 SMP Thu Feb 5 09:26:35 UTC 2009 i686 GNU/Linux NetworkManager 0.7~~svn20081018t105859-0ubuntu1.8.10.1 I've been trying to get a script to trigger on the "pre-up" phase of network configuration, however, NetworkManager doesn't seem to call it's dispatcher for "pre-up" or "post-down" events. None of the scripts I put in /etc/network/if-pre-up.d ever got called, so I added the following line to the top of the dispatcher script "/etc/NetworkManager/dispatcher.d/01ifupdown": logger -t $0 "called with $1 $2" Where $0 is the name of the script, $1 is the network interface and $2 is the network event. After bringing some network connections up and down, I checked the logs, and NetworkManager doesn't seem to be calling "/etc/NetworkManager/dispatch.d/01ifupdown" for either "pre-up" or "post-down" events. The only entries that show up are for "up" and "down" events. According to the changelog both "pre-up" and "post-down" events are supposed to be supported as of version 0.5.1-0ubuntu12: https://launchpad.net/ubuntu/+source/network-manager To unsubscribe from this bug, go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/336736/+subscribe -- NetworkManager does not call /etc/network/if-pre-up.d scripts https://bugs.launchpad.net/bugs/336736 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
