-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2014-06-13 12:25, Josef Wolf wrote:
Thanks for the reply, Carlos!
On Fri, Jun 13, 2014 at 11:47:57AM +0200, Carlos E. R. wrote:
I think it would have this Message-ID:
In-Reply-To: <alpine.LNX.2.00.0903100026320.30508@Fatou.suse.de>
and it was perhaps sent privately. I did a search, and I have never seen a post from him on the opensuse general mail list. Only factory, security, and bugzillas.
This message was addressed to:
To: Josef Wolf <jw@raven.inka.de>, opensuse@opensuse.org Maybe Christian's messages were removed from the archives?
Not Christian, but Ruediger's. He was probably not subscribed to the opensuse list, so they never appeared there. I have my own archives. You probably got that answer directly from him, so nobody but you saw it.
What happened in that case was that you had /root/.bash_history symlinked to /dev/null, and the postinstall script of the aaa_base rpm did: touch root/.bash_history chmod 600 root/.bash_history
which changed /dev/null, not the symlink (which is impossible).
The cause of the problem is clear to me.
I was posting the short history so that we all could see it without reading the long thread ;-)
The symlink is still there, since I set it by intent. I don't want bash-history for root, even if some variables happen to pass through /bin/su or sudo.
Ok.
The solution, according to Cristian, would be to «"touch & chmod" only if it the file doesnt exists.»
Yeah. Something like
if [ ! -e /root/.bash_history ] ; then touch /root/.bash_history chmod 600 /root/.bash_history fi
in the postinstall script or something.
which you can see in the post from Berny that it is not done.
But I don't see in the thread a bugzilla number for the issue.
I never created a bug. Due to Christian's message, I assumed the fix was already applied. There's no point in creating a bug for something that's already fixed, IMHO.
Ok, but now you can not re-open the bugzilla, or open a new one pointing to it.
The procedure for finding out the culprit this time would be to repeat the steps again ;-)
Sorry, I don't understand. We know the cause and we know the fix. What else do we need to find out by repeating the steps?
A proof :-) You know the symptoms only. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlOa2R4ACgkQtTMYHG2NR9Uh8wCeJcFhccaJalV4k10Td5qViRBk xUcAn02j8Mcx+sMJwTb4oee0ulYCgYf7 =X7aQ -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org