https://github.com/rene/nlinkfs
FUSE filesystem to allow symbolic links on filesystems without such support
https://github.com/rene/nlinkfs
Last synced: 2 months ago
JSON representation
FUSE filesystem to allow symbolic links on filesystems without such support
- Host: GitHub
- URL: https://github.com/rene/nlinkfs
- Owner: rene
- License: gpl-3.0
- Created: 2019-01-30T14:39:36.000Z (over 6 years ago)
- Default Branch: master
- Last Pushed: 2023-05-18T10:17:53.000Z (about 2 years ago)
- Last Synced: 2025-04-20T13:36:35.570Z (3 months ago)
- Language: Shell
- Size: 206 KB
- Stars: 5
- Watchers: 2
- Forks: 4
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
- License: COPYING
- Authors: AUTHORS
Awesome Lists containing this project
README
# NLINKFS
Some file systems does not support symbolic links. NLINKFS was written to act
over some other file system (fs) to deal with symbolic links as regular files
on the original fs.
## How to install
```bash
$ ./autogen.sh
$ ./configure
$ make
$ make install # (as root)
```
For more information, see INSTALL file.
## How to use
NLINKFS uses the follow syntax:
```bash
$ nlinkfs
```
* **** - Original file system directory
* **** - Directory to mount NLINKFS file system
Each symbolic link created at **** will be converted to a regular .LNK
file at **** with the information to where the link points to. In the
same way, nlinkfs will read each .LNK file on **** and show it as
symbolic links at ****. Files created by NLINKFS contains a signature, so
common .LNK (non link) files are allowed.
Example of usage:
```bash
$ mkdir {test,mdir}
$ touch test/hello.txt
$ nlinkfs test mdir
$ cd mdir
$ ln -s hello.txt mylink
$ cd ..
$ fusermount -u mdir
```
## Bug Reports
Bugs should be reported to [email protected]