Bruce Ferrell wrote:
On 06/07/2014 06:29 PM, Anton Aylward wrote:
Out with the old, in with the new. Here's something else for Aaron and Linda to complain about:
Why would I care, Anton? Why do you project your failings on others?
Linda, might you be willing to share your scripts and techniques for eviscerating systemd? I suspect there would be wide interest in them. I know I'd love to have them to put my system(s) to rights and keep them that way
---- I have no issue sharing what I have, BUT, since it was done under 'emergency' conditions I had to cut corners in places, which has made me reluctant to share anything until I could smooth off the edges, so to speak. I.e. people using the scripts 'now' would have to deal with little things like: ##inline data (should be in external file) # eth5 is in twice -- once for before bonding once for after; map hw2if=( [00:15:17:bf:be:b2]=eth0 [00:15:17:bf:be:b3]=eth1 [00:26:b9:48:71:e2]=eth2 [00:26:b9:48:71:e4]=eth3 [a0:36:9f:15:c9:c0]=eth4 [a0:36:9f:15:c9:c2]=eth5 ) map if2hw=( [eth0]=00:15:17:bf:be:b2 [eth1]=00:15:17:bf:be:b3 [eth2]=00:26:b9:48:71:e2 [eth3]=00:26:b9:48:71:e4 [eth4]=a0:36:9f:15:c9:c0 [eth5]=a0:36:9f:15:c9:c2 ) --- Also haven't figured out why it doesn't work reliably at boot (it works great when I run it by hand, which is unfortunate. But I made another change and am hoping it might work (I don't reboot my system that often, so usually wait for some other reason to reboot than just retesting this script. (above script written in bash, sets normal names on the interfaces by their hardware ethernet addrs). But it *should* read such things from a separate config... so "rough edges"... It was my intention to put them online when I got them to some ready state, but historically, I take way too long to do that, being one of those perfectionist types. I'm trying to keep most stuff in bash, but the script to test for bad symlinks and dependencies was more complex so went to perl. But too many *holes would have a field day examining anything I put out with a microscope -- have seen it before -- releasing images where @ 300-500% size, you could see some fine-detail problems --- it wasn't designed for over magnification...irrelevant. It was only my 3rd work... irrelevant.... etc etc etc... Or ... I released a pretty good module on CPAN -- and got http://ledgersmbdev.blogspot.co.uk/2013/11/on-cpan-community-and-p-case-stud... Never mind that it was my first CPAN module, never mind that I was asked to prove my concepts by writing such a module, never mind that he doesn't really critique the module, but the 'name', the CPAN porting difficulties (which were overcome after less than a month of being on CPAN), it's all "Fox News" quality commentary in their typical 'fair and balanced format'. He didn't even know what the module did before he wrote it! He didn't even bother to read the documentation, but it was good enough for his "case study". Or people's ignorance and malevolent intent of deliberately lying about the module and shutting out my answers to them by making sure that my response isn't shown (it's hidden as an "unhelpful review") -- on 'P', and 'mem'...(the later one of them copied part of its functionality because it was useful while saying they'd never use it in production code...idiots. Of course if you look at my modules (http://search.cpan.org/~lawalsh/) All of them except 1 with no tests show 100% passing (over 300 different testers) --- a stark contrast to the initial liar who wrote his case study. Maybe if enough people from here voted up those modules that they marked down and marked their trashy reviews as 'not helpful', it might reverse some people's feelings.. As it is, I don't even know where I'd release such "specialty" scripts. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org