public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mark David Dumlao <madumlao@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] systemd installation location
Date: Mon, 30 Sep 2013 10:25:14 +0800	[thread overview]
Message-ID: <CAG2nJkM6hz-pq=yYTWN0kYJf2mFVemo1U5sxNbK_S6zs5=QR+A@mail.gmail.com> (raw)
In-Reply-To: <5248DB6D.50903@sporkbox.us>

On Mon, Sep 30, 2013 at 10:01 AM, Daniel Campbell <lists@sporkbox.us> wrote:
> On 09/29/2013 08:51 PM, Mark David Dumlao wrote:
>> On Mon, Sep 30, 2013 at 9:22 AM, Daniel Campbell <lists@sporkbox.us> wrote:
>>> It's fairly obvious (to me, anyway) that anything mounting a filesystem
>>> and making it available is system-critical. I run samba and don't need
>>> it for boot, but like you said, someone may need that. I wouldn't see a
>>> problem with smbmount being in /bin. FUSE deserves similar treatment.
>>> LVM's another that probably deserves special treatment.
>>>
>>
>> If you allow FUSE you've already failed, because arbitrary programs can
>> be required by FUSE filesystems. Suddenly your ssh client should be pushed
>> to /, or your telnet, or rsync, or ftp.
>>
> FUSE is that lenient with what it can use to mount with? o_O

Fuse is filesystems in userspace. The hard problem that isn't obvious
here, is that
anybody can come up with a userspace filesystem, and there is ZERO intelligence
in the package manager that some filesystem is dependent on some userspace
logic.

for example, there's a filesystem called sshfs. It allows you to view an ssh
connection as a directory. sshfs itself could be in /, but it depends
on ssh and its
libraries, which are normally in /usr. Now what do you do? Just to
support sshfs,
you have to move or copy all those programs to /. Portage doesn't know this.
Ebuilds don't know this. Manual compiles don't know this. What should the ssh
packagers do? What should the fuse-sshfs packagers do? What should users
who are manually rolling out sshfs do?

How about when you develop the next revolutionary crazy filesystem that
allows you to view emacs sessions as directories? What should the emacs
packagers do? What should the fuse-emacsfs packagers do? What should users
manually rolling out that do?

You want to automatically version /etc using some filesystem that uses a git
backend (I'll call it gitfs). What should git packagers do? What
should fuse-gitfs
packagers do? etc.... How about svnfs? hgfs? bzrfs? scpfs? ...
-- 
This email is:    [ ] actionable   [x] fyi        [ ] social
Response needed:  [ ] yes          [ ] up to you  [x] no
Time-sensitive:   [ ] immediate    [ ] soon       [x] none


  reply	other threads:[~2013-09-30  2:25 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-29 19:52 [gentoo-user] systemd installation location William Hubbs
2013-09-30  0:54 ` Daniel Campbell
2013-09-30  1:17   ` Mark David Dumlao
2013-09-30  1:22     ` Daniel Campbell
2013-09-30  1:51       ` Mark David Dumlao
2013-09-30  2:01         ` Daniel Campbell
2013-09-30  2:25           ` Mark David Dumlao [this message]
2013-09-30  2:31             ` Daniel Campbell
2013-09-30  4:13               ` Pandu Poluan
2013-09-30  5:08                 ` Mark David Dumlao
2013-09-30  1:40   ` Mark David Dumlao
2013-09-30  1:50     ` Daniel Campbell
2013-09-30  2:05       ` Mark David Dumlao
2013-09-30  2:15         ` Daniel Campbell
2013-09-30  2:42           ` Mark David Dumlao
2013-09-30  8:07             ` Neil Bothwick
2013-09-30  6:24         ` pk
2013-09-30  6:45           ` Alan McKinnon
2013-09-30 22:14             ` pk
2013-09-30 22:43               ` Neil Bothwick
2013-10-01  6:16               ` Alan McKinnon
2013-10-01 19:59                 ` pk
2013-09-30 16:06           ` [gentoo-user] " Martin Vaeth
2013-09-30 17:47           ` [gentoo-user] " Mark David Dumlao

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAG2nJkM6hz-pq=yYTWN0kYJf2mFVemo1U5sxNbK_S6zs5=QR+A@mail.gmail.com' \
    --to=madumlao@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox