From: Thomas Weidner <yasea@gmx.net>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] little filesystem layout idea
Date: Sat, 07 Jun 2003 14:04:34 +0200 [thread overview]
Message-ID: <3EE1D4D2.2050103@gmx.net> (raw)
In-Reply-To: <20030606131158.1d1b778c.svyatogor@gentoo.org>
I think using a symlink will end up in a more FHS like filesystem. where
all, also QT,KDE,..., libraries/header/... are in proper locations under
/usr/lib,/usr/include,... . having /usr/qt and others is for me the
first step to make a "windows-like" filesystem. As network admin, you
don't need an extra mount entry for /usr/qt/3/lib, but only for
/usr/lib. (if bins,libs,shares are mounted seperately which might happen
in networks with several archs...)
Svyatogor wrote:
>May I ask you then what is the point of having a /usr/qt/3/bin symlink at all?
>The idea (as far as I understand) is that the programs are is spearate locations.
>Expesially the one like qt, which stay in the place they were compiled.
>
>On Thu, 05 Jun 2003 22:11:09 +0200
>Thomas Weidner <yasea@gmx.net> wrote:
>
>
>
>>What about the following:
>>instead of heaving /usr/X/Y, /usr/X/Y is a symlink to /usr/Y/X.
>>so /usr/qt/3/bin whould be a symlink to /usr/bin/qt/3.
>>the advantage? all binaries/libraries/headers/... are under a common
>>subdirectory (/usr/bin,/usr/lib,/usr/include) and not spread in /usr.
>>This could be usable in network environments where
>>/usr/bin,/usr/share,... are mounted as NFS export. (and it's closer to
>>the FHS....).
>>
>>bye Thomas
>>
>>PS: sorry for bad english
>>PPS: i don't want another filesystem layout flame thread,it's just an
>>idea....
>>
>>
>>--
>>gentoo-dev@gentoo.org mailing list
>>
>>
>>
>>
>
>
>
>
--
gentoo-dev@gentoo.org mailing list
prev parent reply other threads:[~2003-06-07 12:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-05 20:11 [gentoo-dev] little filesystem layout idea Thomas Weidner
2003-06-06 0:21 ` Nick Perry
2003-06-06 13:11 ` Svyatogor
2003-06-07 12:04 ` Thomas Weidner [this message]
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=3EE1D4D2.2050103@gmx.net \
--to=yasea@gmx.net \
--cc=gentoo-dev@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