Waffelson@lemmy.world to linuxmemes@lemmy.world · 8 months ago:wq!lemmy.worldimagemessage-square118fedilinkarrow-up1229arrow-down170
arrow-up1159arrow-down1image:wq!lemmy.worldWaffelson@lemmy.world to linuxmemes@lemmy.world · 8 months agomessage-square118fedilink
minus-squareDocMcStuffin@lemmy.worldlinkfedilinkarrow-up6·8 months agoTry editing a file in /etc as a regular user. It happens sometimes and you really want that warning that the write failed. Anyway, :x is superior. It only writes if there are changes. So, your mtime doesn’t change unnecessarily.
minus-squareMiku Luna \ she/it@lemmy.blahaj.zonelinkfedilinkarrow-up4·8 months agowait people care about the mtime?
minus-squarecarcus@lemmy.mllinkfedilinkEnglisharrow-up4·8 months agoI’ve had to do forensics on a rogue change. In finding when and who actually changed the file, mtime can help narrow it down when compared with wtmp.
Try editing a file in
/etc
as a regular user. It happens sometimes and you really want that warning that the write failed.Anyway,
:x
is superior. It only writes if there are changes. So, your mtime doesn’t change unnecessarily.wait people care about the mtime?
I’ve had to do forensics on a rogue change. In finding when and who actually changed the file, mtime can help narrow it down when compared with wtmp.