mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@aerifal.cx>
To: musl@lists.openwall.com
Subject: Re: filesystem layout
Date: Tue, 25 Sep 2012 13:44:25 -0400	[thread overview]
Message-ID: <20120925174425.GZ254@brightrain.aerifal.cx> (raw)
In-Reply-To: <50618D43.2000704@gentoo.org>

On Tue, Sep 25, 2012 at 12:53:55PM +0200, Luca Barbato wrote:
> On 09/25/2012 11:58 AM, Daniel Cegiełka wrote:
> > @vision of the new platform
> > 
> > http://sta.li/filesystem
> > 
> > stali from  http://suckless.org/ proposes an alternative filesystem
> > scheme. It gives clear organization of the system... but not
> > compatible with FHS. What do you think of this solution? Sabotage
> > distro also has its own concept...
> 
> I commend their idea of removing dbus and implementing bluez w/out it.

I'm quite interested in this. Do they have it working?

> Hopefully a libc wouldn't require a specific fs layout.

From a libc standpoint, the only thing I have to say is that I'm
against any gratuitous filesystem layout changes that would force libc
to be aware of additional variants; that's just gratuitous bloat and
incompatibility. In particular, /dev, /proc, /etc, /tmp, /bin/sh, and
/lib/ld* should not move.

Otherwise, the fs layout is rather irrelevant to libc. As discussed
before, non-libc topics related to this community's projects/ideas are
on-topic on this list, but I also think fs layout is mostly irrelevant
to the "new platform" thread as well. It wasn't my intent to impose
any particular filesystem policy with the new platform except perhaps
some unix socket paths, etc. that would be part of the "api".

Where the fs layout topic is interesting is when you're designing a
distro or want to make binary packages that fit into an existing fs
layout. I don't mind if that's discussed here, but it's getting mildly
off-topic.

Rich


  parent reply	other threads:[~2012-09-25 17:44 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-25  9:58 Daniel Cegiełka
2012-09-25 10:53 ` Luca Barbato
2012-09-25 11:09   ` Daniel Cegiełka
2012-09-25 11:22     ` Luca Barbato
2012-09-25 11:26       ` Kurt H Maier
2012-09-25 11:35         ` Luca Barbato
2012-09-25 11:58           ` Daniel Cegiełka
2012-09-25 12:31             ` Luca Barbato
2012-09-25 12:50           ` Kurt H Maier
2012-09-25 13:08             ` Luca Barbato
2012-09-25 13:09           ` Christian Neukirchen
2012-09-25 13:41             ` Luca Barbato
2012-09-25 13:51               ` Daniel Cegiełka
2012-09-25 11:35     ` Szabolcs Nagy
2012-09-25 17:44   ` Rich Felker [this message]
2012-09-26  8:13     ` Daniel Bainton
2012-09-25 13:01 ` Christian Neukirchen
2012-09-25 13:42   ` Daniel Cegiełka
2012-09-25 17:40 ` Nathan McSween

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=20120925174425.GZ254@brightrain.aerifal.cx \
    --to=dalias@aerifal.cx \
    --cc=musl@lists.openwall.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).