[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: distro name
- From: Rodrigo Barbosa <rodrigob suespammers org>
- To: RPM Package Manager <rpm-list redhat com>
- Subject: Re: distro name
- Date: Tue, 3 Aug 2004 18:24:55 -0300
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
As far as I know, an existing, abeit old one (LSB 1.1.0).
I'm not an LSB expert, tho. I'm just mentioning this based on my
own systems, where I run Conectiva Linux.
This file is instaled by the package lsb-release, and was included during
the LSB compliance process Conective went through.
Here is the output of this file:
LSB_VERSION="1.1.0"
DISTRIB_ID=Conectiva
DISTRIB_DESCRIPTION="Conectiva Linux"
DISTRIB_RELEASE="9"
On the help file that comes with this package:
If the installation is LSB compliant, the "/etc/lsb-release" file
should contain the LSB_VERSION field. The value of the field should be
the version number of the LSB specification against which the installa-
tion is compliant. If the installation is not compliant, the above
field should not be present.
Optional fields are DISTRIB_ID, DISTRIB_RELEASE, DISTRIB_CODENAME, DIS-
TRIB_DESCRIPTION and can be used to overwrite information which is
parsed from the next file.
There is also a command lsb_release.
On Tue, Aug 03, 2004 at 02:16:00PM -0700, Aaron Hanson wrote:
> Hi-
>
> A search of the lsb core document, v1.3 and the v2.0 candidate,
> do not mention such a file. Rodrigo, were you referring to an existing
> standard, or just proposing one?
>
> Thanks...
>
> -Aaron
>
> > -----Original Message-----
> > From: rpm-list-bounces@redhat.com
> > [mailto:rpm-list-bounces@redhat.com] On Behalf Of Rodrigo Barbosa
> > Sent: Tuesday, August 03, 2004 2:05 PM
> > To: RPM Package Manager
> > Subject: Re: distro name
> >
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > On Tue, Aug 03, 2004 at 01:27:53PM -0700, Jim C. wrote:
> > > In the long run, I guess it really just isn't practical. You would
> > > think there would be a requirement for at least a link to a
> > filename
> > > that never changes. I mean like if mandrake wanted to have
> > a specific
> > > file name for thier /etc/version file there should be a Linux
> > > standards base compliance rule that states they need to
> > have a link to
> > > that file such that the link is the same on all systems.
> >
> > You mean, like /etc/lsb-release ?
> >
> > - --
> > Rodrigo Barbosa <rodrigob@suespammers.org> "Quid quid Latine
> > dictum sit, altum viditur"
> > "Be excellent to each other ..." - Bill & Ted (Wyld Stallyns)
> >
> > -----BEGIN PGP SIGNATURE-----
> > Version: GnuPG v1.2.3 (GNU/Linux)
> >
> > iD8DBQFBD/38pdyWzQ5b5ckRAufHAKCMxaQTAAZNSO43X0hvpMoWQB92dwCgk5Ww
> > khiVh4TzXuK683YfUVVk94k=
> > =C/nl
> > -----END PGP SIGNATURE-----
> >
> >
> > _______________________________________________
> > Rpm-list mailing list
> > Rpm-list@redhat.com
> > https://www.redhat.com/mailman/listinfo/rpm-list
> >
>
>
> _______________________________________________
> Rpm-list mailing list
> Rpm-list@redhat.com
> https://www.redhat.com/mailman/listinfo/rpm-list
- --
Rodrigo Barbosa <rodrigob@suespammers.org>
"Quid quid Latine dictum sit, altum viditur"
"Be excellent to each other ..." - Bill & Ted (Wyld Stallyns)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
iD8DBQFBEAKnpdyWzQ5b5ckRAqQmAJ0cktS2jpZ4QwwXrUzGYQfR6Iig9wCeLFbF
o5Kqxtlw0inrScpD+9JB+Ts=
=lViS
-----END PGP SIGNATURE-----
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]