On 2014-08-22, GKH wrote:
> Aside from the stupid way:
>
> create a file "org_name"
> copy it to new_name
> rm org_name
> mv new_name org_name
>
> I don't know of a way to change inode
> and keep md5 the same.
If the bug that Matthew cited is involved, then that's likely very much
what happened.
Meikel,
Aside from the stupid way:
create a file "org_name"
copy it to new_name
rm org_name
mv new_name org_name
I don't know of a way to change inode
and keep md5 the same.
Does anyone know of a way?
This would be the perfect question for this forum.
GKH
> Hi folks,
>
> on CentOS 6.5 I run
On Fri, Aug 22, 2014 at 11:13:40PM +0200, Meikel wrote:
> By browsing those tripwire reports I found that there are files which
> did not change at all (i.e. the MD5 hash is the same as before) but the
> inode changed. I do not understand what yum did to the file that
> resulted in an inode chan
Hi folks,
on CentOS 6.5 I run tripwire software which verifies data integrity. My
system is automatically updated by yum (as far as I understand the
/etc/cron.daily/0yum.cron is responsible for the regular system
updates). After a system update I'm then notified by tripwire about the
changes o
4 matches
Mail list logo
