Bug #1259
closed
installer does not set nohistory flag for hammer pfs
Added by corecode almost 16 years ago.
Updated over 15 years ago.
Description
Unlike hammer.sh, the installer does not set the nohistory flag for those pfs
which should be created without history.
For which PFS did you observe this? The only difference to hammer.sh I could
find was /tmp which isn't chflags nohistory'd in the installer (I'll fix that).
In my install, no pfs had the nohistory flag set
Just to follow up - this still exists in the release installer. Something
definitely is wrong.
Simon 'corecode' Schubert (via DragonFly issue tracker) schrieb:
Unlike hammer.sh, the installer does not set the nohistory flag for those pfs
which should be created without history.
The problem is not in the installer, but rather cpdup resetting the
chflags changes again when files are copied.
And regarding hammer.sh, I just tested it, and no flags were set after
installation either. Are you really sure it worked for you?
Sascha
Sascha Wildner (via DragonFly issue tracker) wrote:
And regarding hammer.sh, I just tested it, and no flags were set after
installation either. Are you really sure it worked for you?
No, I'm not sure at all.
I've committed a workaround:
6b8a26e2a91661b74c4082dcc0d43de60b121803
...and one for hammer.sh too:
fb422ccafeeaf8e9dc595841a308211d5b2a73f1
Also available in: Atom
PDF