How to Install and Uninstall golang-github-jacobsa-fuse-dev Package on Ubuntu 20.10 (Groovy Gorilla)

Last updated: November 21,2024

1. Install "golang-github-jacobsa-fuse-dev" package

Please follow the instructions below to install golang-github-jacobsa-fuse-dev on Ubuntu 20.10 (Groovy Gorilla)

$ sudo apt update $ sudo apt install golang-github-jacobsa-fuse-dev

2. Uninstall "golang-github-jacobsa-fuse-dev" package

This guide let you learn how to uninstall golang-github-jacobsa-fuse-dev on Ubuntu 20.10 (Groovy Gorilla):

$ sudo apt remove golang-github-jacobsa-fuse-dev $ sudo apt autoclean && sudo apt autoremove

3. Information about the golang-github-jacobsa-fuse-dev package on Ubuntu 20.10 (Groovy Gorilla)

Package: golang-github-jacobsa-fuse-dev
Architecture: all
Version: 0.0~git20150806.0.9a7512a-4
Priority: extra
Section: universe/devel
Source: golang-github-jacobsa-fuse
Origin: Ubuntu
Maintainer: Ubuntu Developers
Original-Maintainer: pkg-go
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 401
Depends: golang-github-jacobsa-bazilfuse-dev, golang-github-jacobsa-oglematchers-dev, golang-github-jacobsa-ogletest-dev, golang-github-jacobsa-reqtrace-dev, golang-github-jacobsa-syncutil-dev, golang-github-jacobsa-timeutil-dev, golang-golang-x-net-dev, golang-golang-x-sys-dev
Filename: pool/universe/g/golang-github-jacobsa-fuse/golang-github-jacobsa-fuse-dev_0.0~git20150806.0.9a7512a-4_all.deb
Size: 63316
MD5sum: 756adeb42d5140cbdc21211011c908cd
SHA1: c6458d8396ab14bc23a6c0cb245e1073dd943771
SHA256: e5d8015a91d7069eb4ae863c0656ceb0a987723e3e99831f6ed899ec5dd1a2d4
SHA512: c9c55ed9fe77e2dc5a5a632feddaa36ee901765847bd7f4db95cc04d3700bea15618b4a272b86fdb84753f5e2293143baa4c2b3448b64c45fab2eb9fb406d44b
Homepage: https://github.com/jacobsa/fuse
Description-en: writing and mounting user-space file systems from Go
This package allows for writing and mounting user-space file systems from Go.
It is a wrapper around bazil.org/fuse, which does the heavy lifting. It does
not make use of the bazil.org/fuse/fs sub-package, which allows for something
like an object-orientend representation of files and directories, and contains
a decent amount of canned behavior.
.
The chief improvements and/or differences from the bazil.org packages are:
.
* No surprises in the form of magic/default behaviors. You must provide an
implementation for every method in the interface. Embed a
fuseutil.NotImplementedFileSystem struct to have default implementations
that return ENOSYS.
.
* Every method, struct, and field is thoroughly documented. This may help you
get your bearings in the world of FUSE, the Linux VFS, traditional file
system implementations, etc., all of which tend to be very poorly
documented.
.
* Support for arbitrary offsets in directory entries returned by ReadDir.
(The bazil.org package assumes that offsets must be counts of bytes.)
.
The very large disadvantage over using the bazil.org packages is that many
features have not yet been exposed.
Description-md5: 40ac9a9ae90475962f92ff57a966b520