linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Olaf Hering <olh@suse.de>
To: Michel Dänzer <daenzerm@student.ethz.ch>
Cc: Hollis Blanchard <hollis@amulet.co.jp>,
	arcane@verinet.com, yellowdog-general@lists.yellowdoglinux.com,
	linuxppc-dev@lists.linuxppc.org
Subject: Re: Need for Cross Platform Updates Distribution
Date: Mon, 19 Jun 2000 10:58:53 +0200	[thread overview]
Message-ID: <20000619105853.A11715@suse.de> (raw)
In-Reply-To: <394DDB66.62A97110@student.ethz.ch>; from daenzerm@student.ethz.ch on Mon, Jun 19, 2000 at 10:35:50AM +0200


On Mon, Jun 19, Michel Dänzer wrote:


> > > Also, what's this about suse using /opt for kde and gnome? sn't
> > > /opt in the filesystem standard for commercial software only?
> >
> > It all depends on what "standard" you're using.
>
> Check out FHS (http://www.pathname.com/fhs/), which is an affiliated project
> of The Free Standards Group.
>
> Debian is already mostly FHS conformant and aiming to be fully so AFAIK.

<AOL>
me too
</AOL>

Just read FHS (2.0 for 6.4-ppc) and compare it with the reality. It will
be amazing. Flamewars should go to comp.os.advocacy ;)


Gruss Olaf

--
 $ man clone

BUGS
       Main feature not yet implemented...

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2000-06-19  8:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <394D2013.AAD184AB@golden.net>
2000-06-19  5:57 ` Need for Cross Platform Updates Distribution Olaf Hering
2000-06-19  7:33   ` Bryan Stillwell
2000-06-19  8:03     ` Steven Hanley
2000-06-19  8:19     ` Hollis Blanchard
2000-06-19  8:35       ` Michel Dänzer
2000-06-19  8:58         ` Olaf Hering [this message]
2000-06-19  9:03         ` Hollis Blanchard
2000-06-19  9:13           ` Michel Dänzer
2000-06-18 15:41 hendricks

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=20000619105853.A11715@suse.de \
    --to=olh@suse.de \
    --cc=arcane@verinet.com \
    --cc=daenzerm@student.ethz.ch \
    --cc=hollis@amulet.co.jp \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=yellowdog-general@lists.yellowdoglinux.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.
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).