Project

General

Profile

Actions

Bug #1053

closed

hammer: nohistory doesn't show up in mount

Added by mneumann over 15 years ago. Updated over 14 years ago.

Status:
Closed
Priority:
Low
Assignee:
Category:
-
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:

Description

Hi,

Either "nohistory" has no effect or it just does not appear in the
"mount -v" output. As I can use "undo" and I mounted with "-o nohistory"
I assume the first.

Regards,

Michael
Actions #1

Updated by dillon over 15 years ago

:Hi,
:
:Either "nohistory" has no effect or it just does not appear in the
:"mount -v" output. As I can use "undo" and I mounted with "-o nohistory"
:I assume the first.
:
:Regards,
:
: Michael

Doesn't appear in the mount -v output.  Not sure there is anything
I can do about that, the option is flagged separately in the
hammer-specific hammer_mount structure and not in the basic mount
structure.
-Matt
Matthew Dillon
<>
Actions #2

Updated by mneumann over 15 years ago

Ah, I understand. Could it be made a "global" flag (non-hammer
specific), like "readonly"? If not, something like "hammer mount-info"
would be nice.

Regards,

Michael
Actions #3

Updated by dillon about 15 years ago

This requires mount -v to specifically understand the HAMMER VFS. Unresolved
atm. I don't recommend making this flag global at this time. Another option is
to add a VFS_* op to return active options in a string buffer which mount -v can
generically query.

Actions #4

Updated by tuxillo over 14 years ago

Hi

A fix has been committed in HEAD, see dad088a5471c72523a12b0ca4270729e6c3c1919
Can you please check?

Cheers,
Antonio

Actions #5

Updated by tuxillo over 14 years ago

This is solved

Actions

Also available in: Atom PDF