Bug 13407

Summary: FHS compliancy
Product: Base System Reporter: nzanella <nzanella>
Component: miscAssignee: freebsd-bugs (Nobody) <bugs>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: Unspecified   
Hardware: Any   
OS: Any   

Description nzanella 1999-08-27 07:30:01 UTC
The machine is not compliant with the File Hierarchy Standard set
forth at <http://www.pathname.com/fhs/> (version 2.0) as far as the
requirements of certain directories (eg. /bin and /usr/bin etc...)go.
Complying with FHS means that scripts on a heterogenous network of
FreeBSD, Linux, and eventually Unix systems would become much more portable and
hence would be in the interest of everyone.

Fix: 

Move the relevant files to the standard places according to FHS.
Comment 1 cpiazza freebsd_committer freebsd_triage 1999-08-27 07:48:39 UTC
State Changed
From-To: open->closed

This is not a bug, there are more appropriate places to discuss 
this than a bug report.  For the record I contend that *they* should 
be using *our* hierarchy as outlined in hier(7). 

Comment 2 Neil Blakey-Milner 1999-08-27 07:51:16 UTC
On Thu 1999-08-26 (23:26), nzanella@cs.mun.ca wrote:
> >Number:         13407
> >Category:       misc
> >Synopsis:       FHS compliancy

> The machine is not compliant with the File Hierarchy Standard set
> forth at <http://www.pathname.com/fhs/> (version 2.0) as far as the
> requirements of certain directories (eg. /bin and /usr/bin etc...)go.
> Complying with FHS means that scripts on a heterogenous network of
> FreeBSD, Linux, and eventually Unix systems would become much more
> portable and hence would be in the interest of everyone.

Could you supply a (possibly selective) list, perhaps?  Possibly with
reasons?  You need to give a slightly more in-depth account of the
problem. (since the site seems inapproachable from my current location)

Thinking ahead, would a "fhs-compliant" package which was separate from
the build system, and simply created the necessary symlinks, suit your
needs?

Also, have you read hier(7)?  As far as I can ascertain, we share these
conventions with at least our sibling BSDs.

Neil
-- 
Neil Blakey-Milner
nbm@rucus.ru.ac.za
Comment 3 Sheldon Hearn 1999-08-27 07:52:11 UTC
On Thu, 26 Aug 1999 23:26:05 MST, nzanella@cs.mun.ca wrote:

> The machine is not compliant with the File Hierarchy Standard set
> forth at <http://www.pathname.com/fhs/> (version 2.0) as far as the
> requirements of certain directories (eg. /bin and /usr/bin etc...)go.
> Complying with FHS means that scripts on a heterogenous network of
> FreeBSD, Linux, and eventually Unix systems would become much more
> portable and hence would be in the interest of everyone.

If you tell us _which_ files and directories you think should be moved,
where _from_ and where _to_, we might be able to do something with your
PR.

As it stands, though, it's pretty content-free. :-(

Are you in a position to send more specific information?

Ciao,
Sheldon.
Comment 4 nzanella 1999-08-27 09:03:19 UTC
On Fri, 27 Aug 1999, Neil Blakey-Milner wrote:

> Could you supply a (possibly selective) list, perhaps?  Possibly with
> reasons?  You need to give a slightly more in-depth account of the
> problem. (since the site seems inapproachable from my current location)

The document should at least be approchable from any location as it
resides at <ftp://metalab.unc.edu/pub/Linux/docs/fhs/fhs-2.0.tar.gz>.
All the details are in that document. I am sorry about running the
old 2.2.7 version of FreeBSD but I am not the systems administrator
and so I'm afraid I cannot perform the upgrade although the sys admin
will certainly upgrade the machine in the future.

The standard also contains instructions on how to subscribe to the mailing
list fhs-discuss. This is the main place for discussing future changes
to the standard.

> Thinking ahead, would a "fhs-compliant" package which was separate from
> the build system, and simply created the necessary symlinks, suit your
> needs?

Well, if there was such an fhs-compliant package then it would be in the
interest of all that such a package would get installed by default.

Best Regards and thanks for your cooperation,

Neil Zanella
nzanella@cs.mun.ca