Skip to contentSkip to conversation

Merging?

fuse-devel Miklos Szeredi 14 participants 23 messages Jan 12, 2005 – Jan 18, 2005 3 messages not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

#2 lore raw
Quoted 7 lines
Quoted 2 lines

How goes the attempt to get FUSE merged into Andrew or Linus' tree? I saw that an attempt was made about three weeks ago on the LKML.

I made some changes to the kernel code since the last submission (related to being able to interrupt requests), and some problems still need to be ironed out. Then I'll submit again, hopefully this time with more success :)

Well, there doesn't seem to be a great rush to include FUSE in the kernel. Maybe they just don't realize what they are missing out on ;)

So if any of you would like to support this motion, you can mail the linux-kernel list and maybe Linus and Andrew, to generate a little discussion on why (or why not) inclusion is a good idea.

Thanks,
Miklos

#3 lore raw
Quoted 3 lines · El Wed, 12 Jan 2005 14:49:35 +0100 Miklos Szeredi <[email protected]> escribió:

So if any of you would like to support this motion, you can mail the linux-kernel list and maybe Linus and Andrew, to generate a little discussion on why (or why not) inclusion is a good idea.

Personally I think it's cool for "desktops" and other reasons because:

-It could replace gnome-vfs AND kioslaves by a more generic solution that works
for all environments

-You could implement several "not-performance-critical" filesystems (fat,
isofs) with FUSE to avoid possible security issues. Give that nowadays usb sticks and cd/dvds are so common it'd be possible to modify a filesystem on purpose to crash the kernel if a bug were found in those filesytems. With FUSE that posibility decreases.

-Since you can use other programming languages, I suposse it'd be easier for
people to write support for weird filesystems.

-Better for kernel (less code to maintain given a big number of filesystems)
and less pressure for VFS developers when making big changes to the VFS.

-Possibility to write stupid filesystems like "gmailfs".

#4 lore raw
Quoted 6 lines

-You could implement several "not-performance-critical" filesystems (fat,
isofs) with FUSE to avoid possible security issues. Give that nowadays usb sticks and cd/dvds are so common it'd be possible to modify a filesystem on purpose to crash the kernel if a bug were found in those filesytems. With FUSE that posibility decreases.

One of my pet ideas, is a userspace loopback mounter, which would use UML to actually mount an image, and export the resulting filesystem through FUSE to the host.

Brilliant isn't it?

Miklos

A message that is not in the archive (sent off-list or not yet received): [email protected]

#6 lore raw
Quoted 3 lines

Perhaps a little heavyweight but it would solve an outstanding problem which is "I have the software, I have the hardware, hell, why should I type my root password to mount a ****ing iso ?" :)

Exactly!

In fact it's not so heavyweight either. A standalone UML binary which just contains all the major filesystems and the core kernel is little over 3Mbytes. It's smaller than many binaries even without their library dependencies. It loads in less than a second... The linux kernel is still pretty nice and lean!

Miklos

#7 lore raw
In reply to Miklos Szeredi

Hi!

Quoted 11 lines
Quoted 5 lines

-You could implement several "not-performance-critical" filesystems (fat,
isofs) with FUSE to avoid possible security issues. Give that nowadays usb sticks and cd/dvds are so common it'd be possible to modify a filesystem on purpose to crash the kernel if a bug were found in those filesytems. With FUSE that posibility decreases.

One of my pet ideas, is a userspace loopback mounter, which would use UML to actually mount an image, and export the resulting filesystem through FUSE to the host.

Brilliant isn't it?

Uh, yes, it actually makes sense.

OTOH perhaps porting linux's vfs to userland would be better idea. People would like to tap on .iso images in mc to open them, but running full UML to do this is little heavy-weight solution.
Pavel

Signature · 1 line
64 bytes from 195.113.31.123: icmp_seq=28 ttl=51 time=448769.1 ms         
#8 lore raw
In reply to Diego Calleja
Quoted 2 lines · Diego Calleja

-It could replace gnome-vfs AND kioslaves by a more generic solution that works for all environments

kioslaves such as camera, smb, etc.. are obvious to replace (and this has already happened from what I can see), and I think are a good idea. We have a single mountpoint for these things, for example:
/camera/mycamera/picture1.png /smb/workgroup/computer/share/file.blah

How would you go about replacing a kioslaves which operate "somewhere in the middle" (i dunno the correct technical term) such as tar? In other words how would tar:/home/foo/bar.tar.bz2/baz/picture.png work with a FUSE (so reiserfs4 is not a valid answer to this question) filesystem?

Just some thoughts,

Florian

#9 lore raw
In reply to Diego Calleja
Quoted 9 lines · Diego Calleja
Quoted 6 lines · El Wed, 12 Jan 2005 14:49:35 +0100 Miklos Szeredi <[email protected]> escribió:

Well, there doesn't seem to be a great rush to include FUSE in the kernel. Maybe they just don't realize what they are missing out on ;)

So if any of you would like to support this motion, you can mail the linux-kernel list and maybe Linus and Andrew, to generate a little discussion on why (or why not) inclusion is a good idea.

-Possibility to write stupid filesystems like "gmailfs".

Not to mention Fuse::DBI which allows you to mount relational database as a file-system. Imagine editing templates from your CMS with vi. Joy, right?

Back to serious notes, having ability to write filesystems in user-space is something that micro kernels (like HURD or plan9) had for a long time and it's extremely useful if file-system semantic is mappable to problem at hand.

That would also help reduce kernel bloat because you could write something like umsdos in user-space where it belongs in first place.

Signature · 2 lines
Dobrica Pavlinusic               2share!2flame            [email protected]
Unix addict. Internet consultant.             http://www.rot13.org/~dpavlin
#10 lore raw
In reply to Diego Calleja
Quoted 2 lines · Diego Calleja

-Since you can use other programming languages, I suposse it'd be easier for
people to write support for weird filesystems.

Very weird, since the FUSE C library layer is small enough that if needs be you can rewrite *that* in other languages as well.

I have plans for a Guile version of the userspace part of FUSE, for instance, and some filesystems written in Guile: you certainly couldn't do *that* in the kernel.

Signature · 2 lines
`Blish is clearly in love with language. Unfortunately,
 language dislikes him intensely.' --- Russ Allbery
#11 lore raw
In reply to Miklos Szeredi
Quoted 3 lines · Miklos Szeredi

Well, there doesn't seem to be a great rush to include FUSE in the kernel. Maybe they just don't realize what they are missing out on ;)

heh. What userspace filesystems have thus-far been developed, and what are people using them for?

#12 lore raw
Quoted 7 lines · Andrew Morton
Quoted 3 lines · Miklos Szeredi

Well, there doesn't seem to be a great rush to include FUSE in the kernel. Maybe they just don't realize what they are missing out on ;)

heh. What userspace filesystems have thus-far been developed, and what are people using them for?

I was using siefs, to mount the fs of my Siemens mobile phone (via serial cable). However it doesn't seem to work with the current fuse anymore.

Signature · 1 line
Erik Hensema <[email protected]>
#13 lore raw
Quoted 3 lines

I was using siefs, to mount the fs of my Siemens mobile phone (via serial cable). However it doesn't seem to work with the current fuse anymore.

The following patch makes it compile with FUSE 2.2-pre3 too. You need to run autoreconf after patching.

Not tested, since I don't have a Siemens phone.

Miklos

configure.in +0 -8
diff -ru siefs-0.4.orig/configure.in siefs-0.4/configure.in
@@ -39,14 +39,6 @@
 ])
 fi
 
-if ! grep -q '\(\*release\)' $fuseinst/include/fuse.h ; then
-	AC_MSG_RESULT([old])
-	AC_MSG_ERROR([
-*** You need fuse version 1.0 or later.
-*** Please go to http://sourceforge.net/projects/avf
-*** and download the latest version
-])
-fi
 AC_MSG_RESULT(${fuseinst})
 AC_SUBST(fuseinst)
 
siefs/Makefile.am +1 -1
diff -ru siefs-0.4.orig/siefs/Makefile.am siefs-0.4/siefs/Makefile.am
@@ -1,6 +1,6 @@
 ## Process this file with automake to produce Makefile.in
 
-CFLAGS = -I$(fuseinst)/include
+CFLAGS = -I$(fuseinst)/include -D_FILE_OFFSET_BITS=64 -DFUSE_USE_VERSION=11
 
 bin_PROGRAMS = siefs slink
 
#14 lore raw
In reply to Andrew Morton
Quoted 2 lines · Andrew Morton

heh. What userspace filesystems have thus-far been developed, and what are people using them for?

Im using the LUFS bridge from time to time for nice access to remote filesystems over ssh. I also plan to use the bluetooth filesystem (btfs) as soon as I get my #/%" bluetooth adapter working again ;)

For a list of other more or less serious filesystems (as gmailfs) checkout http://fuse.sourceforge.net/filesystems.html

Signature · 2 lines
Regards,
Christian
#15 lore raw
In reply to Andrew Morton
Quoted 5 lines
Quoted 2 lines

Well, there doesn't seem to be a great rush to include FUSE in the kernel. Maybe they just don't realize what they are missing out on ;)

heh. What userspace filesystems have thus-far been developed, and what are people using them for?

Sshfs (idea shamelessly stolen from the LUFS project). If you can ssh to some host you can also mount it as a normal user like this:

mkdir /tmp/kempelen
sshfs mszeredi@kempelen: /tmp/kempelen

It pretty much trumps all other network filesystems wrt ease of server setup, it's secure, efficient, all you need in a network filesystem :)

(available from http://sourceforge.net/projects/fuse; needs fuse-2.2-pre3 and libglib-2.0)

Miklos

#16 lore raw
In reply to Andrew Morton
Quoted 7 lines · El Wed, 12 Jan 2005 11:01:09 -0800 Andrew Morton <[email protected]> escribió:
Quoted 3 lines · Miklos Szeredi

Well, there doesn't seem to be a great rush to include FUSE in the kernel. Maybe they just don't realize what they are missing out on ;)

heh. What userspace filesystems have thus-far been developed, and what are people using them for?

I know of several gmailfs users (mount your 1GB-space gmail account an use it to get put things and retrieve them anywhere)

(If it gets into mainline people will probably stop developing things for gnome-vfs/kioslave and use FUSE instead for "desktops")

#17 lore raw
Quoted 2 lines · Diego Calleja

(If it gets into mainline people will probably stop developing things for gnome-vfs/kioslave and use FUSE instead for "desktops")

Not likely. GNOME/KDE are crossplatform. FUSE is Linux specific.

Signature · 2 lines
Tomasz Torcz                Only gods can safely risk perfection,
[email protected]     it's a dangerous thing for a man.  -- Alia
#18 lore raw
In reply to Andrew Morton

Hi!

Quoted 5 lines
Quoted 2 lines

Well, there doesn't seem to be a great rush to include FUSE in the kernel. Maybe they just don't realize what they are missing out on ;)

heh. What userspace filesystems have thus-far been developed, and what are people using them for?

Right now, every project (mc, gnome, kde) has their own vfs implementation, so that they can work transparently over ftp, handle archives, etc.

Done properly, userspace filesystem like fuse can unify those, plus provide better caching.
It also has chance to be a place for niche filesystems (like atari800) that would be too much pain to keep in kernel.

Pavel

Signature · 1 line
64 bytes from 195.113.31.123: icmp_seq=28 ttl=51 time=448769.1 ms         
#19 lore raw
In reply to Andrew Morton
Quoted 7 lines · Andrew Morton
Quoted 3 lines · Miklos Szeredi

Well, there doesn't seem to be a great rush to include FUSE in the kernel. Maybe they just don't realize what they are missing out on ;)

heh. What userspace filesystems have thus-far been developed, and what are people using them for?

At Plasmon we've developed a userland driver for our new UDO (Ultra Density Optical) drive using FUSE. To avoid the complexity of supporting a native 8KB sector size directly in kernel, we have instead used FUSE to allow us to work on filesystems in userland. That's made life _very_ much easier for us...

FUSE is very cool - there are many useful things that can be done with it. Kudos to Miklos and others for their work on it!

Signature · 2 lines
Steve McIntyre, Plasmon                       [email protected]
For more information on UDO, visit www.udo.com
#20 lore raw
In reply to Andrew Morton

Il Wed, 12 Jan 2005 11:01:09 -0800, Andrew Morton <[email protected]> ha scritto:

Quoted 7 lines
Quoted 3 lines · Miklos Szeredi

Well, there doesn't seem to be a great rush to include FUSE in the kernel. Maybe they just don't realize what they are missing out on ;)

heh. What userspace filesystems have thus-far been developed, and what are people using them for?

For my master laurea thesis I developed PackageFS that aims to transparently manage packages in several distros.
There are also many other facilities:
- View a directory-based tree of packages (with the files that each package owns) which can be nested by category, or by priority

In the future
- you will be able to add users to "packages" group to make them able to manage packages
- you can mount the file system on a cluster to transparently manage several hosts

You can find my thesis at http://packagefs.sourceforge.net

I think FUSE is a very good idea (as good as the actual implementation is), IMHO it should be inserted in the mainline kernel.
Thanks to Miklos and other developers.

Luca

Signature · 4 lines
Non ci toglieranno mai....la LIBERTA'!!!
Luca Ferroni
ICQ #317977679
www.cs.unibo.it/~fferroni/
#21 lore raw
In reply to Miklos Szeredi

Hi!

Quoted 8 lines
Quoted 7 lines
Quoted 2 lines

How goes the attempt to get FUSE merged into Andrew or Linus' tree? I saw that an attempt was made about three weeks ago on the LKML.

I made some changes to the kernel code since the last submission (related to being able to interrupt requests), and some problems still need to be ironed out. Then I'll submit again, hopefully this time with more success :)

Quoted 6 lines

Well, there doesn't seem to be a great rush to include FUSE in the kernel. Maybe they just don't realize what they are missing out on ;)

So if any of you would like to support this motion, you can mail the linux-kernel list and maybe Linus and Andrew, to generate a little discussion on why (or why not) inclusion is a good idea.

I like fuse, but I do not think Linus and Akpm have enough mails already. Getting it merged to some distribution might do the trick....

Pavel

Signature · 1 line
64 bytes from 195.113.31.123: icmp_seq=28 ttl=51 time=448769.1 ms         
#22 lore raw
Quoted 3 lines

I like fuse, but I do not think Linus and Akpm have enough mails already. Getting it merged to some distribution might do the trick....

I know debian and gentoo already carry packages. It doesn't get it closer to inclusion though.

Miklos

#23 lore raw

Hi!

Quoted 6 lines
Quoted 3 lines

I like fuse, but I do not think Linus and Akpm have enough mails already. Getting it merged to some distribution might do the trick....

I know debian and gentoo already carry packages. It doesn't get it closer to inclusion though.

Does Debian carry kernel patched with FUSE patches by default?

Pavel
PS: IIRC and not speaking for suse: I think suse was seriously thinking about using FUSE by default. It did not work well enough back then. Not sure who exactly was working on it...

Signature · 2 lines
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!
#24 lore raw
Quoted 1 line

Does Debian carry kernel patched with FUSE patches by default?

No.

Quoted 4 lines

Pavel
PS: IIRC and not speaking for suse: I think suse was seriously thinking about using FUSE by default. It did not work well enough back then. Not sure who exactly was working on it...

Well, they never talked with me about it.

Thanks,
Miklos

#25 lore raw
In reply to Miklos Szeredi
Quoted 2 lines

Well, there doesn't seem to be a great rush to include FUSE in the kernel. Maybe they just don't realize what they are missing out on ;)

I'm a little bit confused... a few weeks ago I read a thread regarding the remove of some - unneeded ? - symbols from IEEE1394 core. Some persons in the discussion told, that everything should be included into kernel mainline, cause if not, symbols needed may be removed.

Now here is the discussion about including FUSE into kernel... So WHAT? In any case, I do not think that FUSE, compiled in as module, could bother someone.

regards

Bernhard