| 1 |
On Mon, Sep 30, 2013 at 10:01 AM, Daniel Campbell <lists@××××××××.us> wrote: |
| 2 |
> On 09/29/2013 08:51 PM, Mark David Dumlao wrote: |
| 3 |
>> On Mon, Sep 30, 2013 at 9:22 AM, Daniel Campbell <lists@××××××××.us> wrote: |
| 4 |
>>> It's fairly obvious (to me, anyway) that anything mounting a filesystem |
| 5 |
>>> and making it available is system-critical. I run samba and don't need |
| 6 |
>>> it for boot, but like you said, someone may need that. I wouldn't see a |
| 7 |
>>> problem with smbmount being in /bin. FUSE deserves similar treatment. |
| 8 |
>>> LVM's another that probably deserves special treatment. |
| 9 |
>>> |
| 10 |
>> |
| 11 |
>> If you allow FUSE you've already failed, because arbitrary programs can |
| 12 |
>> be required by FUSE filesystems. Suddenly your ssh client should be pushed |
| 13 |
>> to /, or your telnet, or rsync, or ftp. |
| 14 |
>> |
| 15 |
> FUSE is that lenient with what it can use to mount with? o_O |
| 16 |
|
| 17 |
Fuse is filesystems in userspace. The hard problem that isn't obvious |
| 18 |
here, is that |
| 19 |
anybody can come up with a userspace filesystem, and there is ZERO intelligence |
| 20 |
in the package manager that some filesystem is dependent on some userspace |
| 21 |
logic. |
| 22 |
|
| 23 |
for example, there's a filesystem called sshfs. It allows you to view an ssh |
| 24 |
connection as a directory. sshfs itself could be in /, but it depends |
| 25 |
on ssh and its |
| 26 |
libraries, which are normally in /usr. Now what do you do? Just to |
| 27 |
support sshfs, |
| 28 |
you have to move or copy all those programs to /. Portage doesn't know this. |
| 29 |
Ebuilds don't know this. Manual compiles don't know this. What should the ssh |
| 30 |
packagers do? What should the fuse-sshfs packagers do? What should users |
| 31 |
who are manually rolling out sshfs do? |
| 32 |
|
| 33 |
How about when you develop the next revolutionary crazy filesystem that |
| 34 |
allows you to view emacs sessions as directories? What should the emacs |
| 35 |
packagers do? What should the fuse-emacsfs packagers do? What should users |
| 36 |
manually rolling out that do? |
| 37 |
|
| 38 |
You want to automatically version /etc using some filesystem that uses a git |
| 39 |
backend (I'll call it gitfs). What should git packagers do? What |
| 40 |
should fuse-gitfs |
| 41 |
packagers do? etc.... How about svnfs? hgfs? bzrfs? scpfs? ... |
| 42 |
-- |
| 43 |
This email is: [ ] actionable [x] fyi [ ] social |
| 44 |
Response needed: [ ] yes [ ] up to you [x] no |
| 45 |
Time-sensitive: [ ] immediate [ ] soon [x] none |
Archives