[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: bash uses tmp files for inter-process communication instead of pipes

From: Linda Walsh
Subject: Re: bash uses tmp files for inter-process communication instead of pipes?
Date: Thu, 09 Oct 2014 16:22:14 -0700
User-agent: Thunderbird

Greg Wooledge wrote:
there is a
file named /etc/udev/rules.d/70-persistent-net.rules
Perhaps you should get in touch with a SuSE mailing list and see how
other SuSE users have dealt with this.  You might be reinventing the
SuSE has had the same file.  At first we were told port name customization
was going away.  That didn't go well, so they decided to continue to support
the udev rules for this next release.  I.e. -- it was going to be removed
this release, but but that decision got reversed this time.  I figure it's
just a matter of time, like other things they wanted to get rid of.

Seems the systemd people may put in a feature to
deal with this, but they really would rather people use hardware-busmapped
based names like p5p1 p5p2 p3p1 p3p2, that would changed if you changed from
one slot to another (those are what I get for eth[0145]).

So... think I got in to the current system in  some early incarnation of it.
It left my old interfaces the same, but new interfaces were added according
to the new scheme with no easy way to get old behavior back.  After manually
renaming them, they stayed, but again... for how long?  I figured I should
have a script that would set/reset them to consistent values so I would
have to deal with variable new release policies.

Even using basic color and status scripts from their process is problematic
now, as it has checks to no longer call scripts -- but systemd, if it's
configs tell it to -- i.e. a status include file was
upgraded to "forward" some requests to systemd, while others were replaced by
systemd commands.  Nice status.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]