Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
go-fuse
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Levin Zimmermann
go-fuse
Commits
391230f2
Commit
391230f2
authored
Jan 06, 2014
by
Han-Wen Nienhuys
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
fuse/nodefs: clarify types.
parent
570a84cd
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
7 additions
and
5 deletions
+7
-5
fuse/nodefs/api.go
fuse/nodefs/api.go
+2
-2
fuse/nodefs/inode.go
fuse/nodefs/inode.go
+5
-3
No files found.
fuse/nodefs/api.go
View file @
391230f2
...
@@ -23,8 +23,8 @@ type FileSystem interface {
...
@@ -23,8 +23,8 @@ type FileSystem interface {
SetDebug
(
debug
bool
)
SetDebug
(
debug
bool
)
}
}
// The Node i
mplements the basic functionality of inodes; this is
// The Node i
nterface implements the user-defined file system
//
where the majority of the FS code for a typical filesystem will be.
//
functionality
type
Node
interface
{
type
Node
interface
{
// Inode and SetInode are basic getter/setters. They are
// Inode and SetInode are basic getter/setters. They are
// called by the FileSystemConnector. You get them for free by
// called by the FileSystemConnector. You get them for free by
...
...
fuse/nodefs/inode.go
View file @
391230f2
...
@@ -7,9 +7,11 @@ import (
...
@@ -7,9 +7,11 @@ import (
"github.com/hanwen/go-fuse/fuse"
"github.com/hanwen/go-fuse/fuse"
)
)
// An Inode reflects the kernel's idea of the inode. Inodes may be
// An Inode reflects the kernel's idea of the inode. Inodes have IDs
// created automatically when the kernel does lookups inode, or by
// that are communicated to the kernel, and they have a tree
// explicitly by calling Inode.New().
// structure: a directory Inode may contain named children. Each
// Inode object is paired with a Node object, which file system
// implementers should supply.
type
Inode
struct
{
type
Inode
struct
{
handled
handled
handled
handled
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment