Make md(4) support GEOM::ident. For swap- and malloc-backed disks
it's random; for vnode-backed ones it's based on backing file device
and inode numbers.
Details
Details
Diff Detail
Diff Detail
- Repository
- rS FreeBSD src repository - subversion
- Lint
Lint Passed - Unit
No Test Coverage - Build Status
Buildable 11560 Build 11913: arc lint + arc unit
Event Timeline
sys/dev/md/md.c | ||
---|---|---|
1301 | I mean that two arc4random() call makes no guarantee about uniqueness of the result. You add some feature and do not explain its purpose, more, you state that in some cases the feature has no purpose. |
Comment Actions
I don't see a point in reporting random ident strings. Those are normally useful to make things persistent, but random is not a way for that. May be I'd see it more useful to have it user-configurable.