9 More Discussions You Might Find Interesting
1. Linux
Hello Friends,
Please anyone share with me, the name of different versions of Linux?
Which are the latest versions of Linux ?? (2 Replies)
Discussion started by: ggiwebsinfo
2 Replies
2. HP-UX
Lo guys, I've just started a new department in work and I'm going to be using HP-UX with Vi. The problem is I'm completely new to UNIX, I'm currently learning at work but I only have limited amounts of time on our dev systems. Is it possible to get a free/educational version any where? I don't... (4 Replies)
Discussion started by: john2012
4 Replies
3. UNIX for Advanced & Expert Users
2.6.32-028stab094.3 x86_64
vs
2.6.32-5-amd64 x86_64
and where can i download the first one?
thx (1 Reply)
Discussion started by: suffeks
1 Replies
4. Red Hat
I will shortly be adding a fedora flavor to my devel box. I currently have XP (installed first on an ssd), ubuntu 10.04 (installed second on the first partition of a platter drive), and I want to add either Cent or SL on the second partition of the platter drive. I will probably also want to... (0 Replies)
Discussion started by: LMHmedchem
0 Replies
5. Linux
Hi everyone,
I hope this question goes here. Anyways, I have a unique situation where my friend's comp has Fedora installed and wants to add Win XP as a dual boot without formatting the drive. Is it possible to create a partition on the current hard drive and then install win xp? I couldn't find... (4 Replies)
Discussion started by: eltinator
4 Replies
6. UNIX for Dummies Questions & Answers
Can I install a HP-UX or IBM AIX in my home pc?. It is a Intel Pentium 4 of 64 bits.
Is there any version for me?. (5 Replies)
Discussion started by: kurt1978
5 Replies
7. HP-UX
I got my hands on a HP9000/380 and need a (really) old version of HP-UX, like 7 or 8.
Is there any vendor who sells older versions? I did a quick search here and checked the FAQ and HPs HP-UX site but couldn't find anything. :confused:
Any help is appreciated! (4 Replies)
Discussion started by: dlundh
4 Replies
8. UNIX for Dummies Questions & Answers
Hi all:
I was just wondering if someone could tell me what versions of UNIX are available to public? I'm aware of all the available distro's for Linux e.g. Debain, SuSe, RedHat, etc ... However you never really here much about UNIX distro's! Is UNIX BDS a common one in use?
Thanks
Oliver (4 Replies)
Discussion started by: oliver79
4 Replies
9. Shell Programming and Scripting
can someone tell me a shell-script to convert an older version of a file with the current one? (1 Reply)
Discussion started by: deeptia
1 Replies
OS-RELEASE(5) os-release OS-RELEASE(5)
NAME
os-release - Operating system identification
SYNOPSIS
/etc/os-release
DESCRIPTION
The /etc/os-release file contains operating system identification data.
The basic file format of os-release is a newline-separated list of environment-like shell-compatible variable assignments. It is possible
to source the configuration from shell scripts, however, beyond mere variable assignments no shell features are supported (this means
variable expansion is explicitly not supported), allowing applications to read the file without implementing a shell compatible execution
engine. Variable assignment values should be enclosed in double or single quotes if they include spaces, semicolons or other special
characters outside of A-Z, a-z, 0-9. All strings should be in UTF-8 format, and non-printable characters should not be used. If double or
single quotes or backslashes are to be used within variable assignments they should be escaped with backslashes, following shell style. It
is not supported to concatenate multiple individually quoted strings. Lines beginning with "#" shall be ignored as comments.
/etc/os-release contains data that is defined by the operating system vendor and should not be changed by the administrator.
As this file only encodes names and identifiers it should not be localized.
The file /etc/os-release might be a symlink to another file, but it is important that the file is available from earliest boot on, and
hence must be located on the root file system.
For a longer rationale for /etc/os-release please refer to the Announcement of /etc/os-release[1].
OPTIONS
The following OS identifications parameters may be set using /etc/os-release:
NAME=
A string identifying the operating system, without a version component, and suitable for presentation to the user. If not set defaults
to NAME=Linux. Example: NAME=Fedora or NAME="Debian GNU/Linux".
VERSION=
A string identifying the operating system version, excluding any OS name information, possibly including a release code name, and
suitable for presentation to the user. This field is optional. Example: VERSION=17 or VERSION="17 (Beefy Miracle)".
ID=
A lower-case string (no spaces or other characters outside of 0-9, a-z, ".", "_" and "-") identifying the operating system, excluding
any version information and suitable for processing by scripts or usage in generated file names. If not set defaults to ID=linux.
Example: ID=fedora or ID=debian.
ID_LIKE=
A space-separated list of operating system identifiers in the same syntax as the ID= setting. Should list identifiers of operating
systems that are closely related to the local operating system in regards to packaging and programming interfaces, for example listing
one or more OS identifiers the local OS is a derivative from. An OS should generally only list other OS identifiers it itself is a
derivative from, and not any OSes that are derived from it, but symmetric relationships are possible. Build scripts and similar should
check this variable if they need to identify the local operating system and the value of ID= is not recognized. Operating systems
should be listed in order of how closely the local operating system relates to the listed ones, starting with the closest. This field
is optional. Example: for an operating system with ID=centos an assignment of ID_LIKE="rhel fedora" would be appropriate. For an
operating system with ID=ubuntu an assignment of ID_LIKE=debian is appropriate.
VERSION_ID=
A lower-case string (mostly numeric, no spaces or other characters outside of 0-9, a-z, ".", "_" and "-") identifying the operating
system version, excluding any OS name information or release code name, and suitable for processing by scripts or usage in generated
file names. This field is optional. Example: VERSION_ID=17 or VERSION_ID=11.04.
PRETTY_NAME=
A pretty operating system name in a format suitable for presentation to the user. May or may not contain a release code name or OS
version of some kind, as suitable. If not set defaults to PRETTY_NAME="Linux". Example: PRETTY_NAME="Fedora 17 (Beefy Miracle)".
ANSI_COLOR=
A suggested presentation color when showing the OS name on the console. This should be specified as string suitable for inclusion in
the ESC [ m ANSI/ECMA-48 escape code for setting graphical rendition. This field is optional. Example: ANSI_COLOR="0;31" for red, or
ANSI_COLOR="1;34" for light blue.
CPE_NAME=
A CPE name for the operating system, following the Common Platform Enumeration Specification[2] as proposed by the MITRE Corporation.
This field is optional. Example: CPE_NAME="cpe:/o:fedoraproject:fedora:17"
HOME_URL=, SUPPORT_URL=, BUG_REPORT_URL=
Links to resources on the Internet related the operating system. HOME_URL= should refer to the homepage of the of operating system, or
alternatively some homepage of the specific version of the operating system. SUPPORT_URL= should refer to the main support page for
the operating system, if there is any. This is primarily intended for operating systems which vendors provide support for.
BUG_REPORT_URL= should refer to the main bug reporting page for the operating system, if there is any. This is primarily intended for
operating systems that rely on community QA. These settings are optional, and providing only some of these settings is common. These
URLs are intended to be exposed in "About this system" UIs behind links with captions such as "About this Operating System", "Obtain
Support" resp. "Report a Bug". The values should be in RFC3986 format[3], and should be http: or https: URLs, and possibly mailto: or
tel:. Only one URL shall be listed in each setting. If multiple resources need to be referenced it is recommended to provide an online
landing page linking all available resources. Examples: HOME_URL="https://fedoraproject.org/" and
BUG_REPORT_URL="https://bugzilla.redhat.com/"
If you are reading this file from C code or a shell script to determine the OS or a specific version of it, use the ID and VERSION_ID
fields, possibly with ID_LIKE as fallback for ID. When looking for an OS identification string for presentation to the user use the
PRETTY_NAME field.
Note that operating system vendors may choose not to provide version information, for example to accommodate for rolling releases. In this
case VERSION and VERSION_ID may be unset. Applications should not rely on these fields to be set.
Operating system vendors may extend the file format and introduce new fields. It is highly recommended to prefix new fields with an OS
specific name in order to avoid name clashes. Applications reading this file must ignore unknown fields. Example:
DEBIAN_BTS="debbugs://bugs.debian.org/"
EXAMPLE
NAME=Fedora
VERSION="17 (Beefy Miracle)"
ID=fedora
VERSION_ID=17
PRETTY_NAME="Fedora 17 (Beefy Miracle)"
ANSI_COLOR="0;34"
CPE_NAME="cpe:/o:fedoraproject:fedora:17"
HOME_URL="https://fedoraproject.org/"
BUG_REPORT_URL="https://bugzilla.redhat.com/"
SEE ALSO
systemd(1), lsb_release(1), hostname(5), machine-id(5), machine-info(5)
AUTHOR
Lennart Poettering <lennart@poettering.net>
Developer
NOTES
1. Announcement of /etc/os-release
http://0pointer.de/blog/projects/os-release
2. Common Platform Enumeration Specification
http://cpe.mitre.org/specification/
3. RFC3986 format
https://tools.ietf.org/html/rfc3986
systemd 10/07/2013 OS-RELEASE(5)
