Sponsored Content
Full Discussion: Linux without loosing Win9x
Top Forums UNIX for Dummies Questions & Answers Linux without loosing Win9x Post 2921 by nzenzen on Sunday 10th of June 2001 05:47:37 PM
Old 06-10-2001
Data VMWare

I just went to the VMWare homepage and found out that you can't run it with Win9X. The only supported operating systems are NT and 2K. Just thought that I would let you know.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

How to install FreeBSD without loosing my data?

hi. I am newbie in Unix. I wanted to install Free BSD 5.2.1 to my computer which winXp was already installed. But i couldn't. I chose Standard. Then it said you are going to use dos style fdisk partitioning. Then a window displayed begining like this. WARNING: A geometry of 155127/16/63 for... (0 Replies)
Discussion started by: sualcavab
0 Replies

2. Shell Programming and Scripting

replace ascii chars without loosing it.

Hi, Can some one tell, how to replace ascii non printable TAB from the while to something, then later on replace it back to TAB. Basciallz we do bulk data processing, our processin treats TAB as new field , So I thought we can replace it with something and later on revert it. TIA (4 Replies)
Discussion started by: braindrain
4 Replies

3. Programming

Loosing signals even with sigqueue

Hi everyone, I have a process that forks many times.At a random time point the children must send a SIGUSR1 to the parent.To do that I'm using a pair of sigaction & sigqueue.However many signals are getting lost. Here are some code segments: a)sigaction sigset_t mask_set; /* used to set a... (12 Replies)
Discussion started by: jonas.gabriel
12 Replies

4. Shell Programming and Scripting

Replacing Carriage returns without loosing EOL

Hello, I have read a few threads on this subject and tried a few things out, but still come up short. There was one good example, then the last reply was something to the effect of 'Use Sed' & 'Read a book'... Well I read a bunch of online tutorials on sed, awk, tr, but still can't get the... (2 Replies)
Discussion started by: Majiktom
2 Replies

5. What is on Your Mind?

You know your on the brink of loosing it when.....

you spend an entire day with scripting nightmares and go to bed real late in the early morning hrs to wake up to your gf asking you a question and your only answer is "It's in the script" LMAO Happened to me this morning would you believe that?? My daughter is 10yrs old and my gf wanted to check... (3 Replies)
Discussion started by: phpfreak
3 Replies

6. SCO

SCO box loosing network connection

Hello, We have a SCO box running OpenServer 5.0.5. This has our business software on it (15 users connecting via terminal emulator (ansio lite)) which has been running for about 12-15yrs strong! Within the past 6-8 months, at random times of the day, we've been loosing connection to this box. ... (8 Replies)
Discussion started by: rpcbrielle
8 Replies

7. Homework & Coursework Questions

Loosing formatting when echoing an awk script

1. The problem statement, all variables and given/known data: When I echo out the output of my awk script I loose the formatting that I set in my awk script (it should be in a table format). 2. Relevant commands, code, scripts, algorithms: 3. The attempts at a solution (include all... (2 Replies)
Discussion started by: ROFL
2 Replies

8. UNIX and Linux Applications

Samba loosing SID UID mapping

Hi all, I don't know how many times I've setup samba shares, but... It's been a while since the last time. The SID UID maps used to always seem random. I.E. if I had to move the data to another box, I'd have to note all of the SID / UID relations and write scripts to convert them on the new... (0 Replies)
Discussion started by: mph
0 Replies

9. Shell Programming and Scripting

Loosing trailing new line in Bash var assignment

I have come across a weird behaviour in bash and would love to get to the bottom of it. If I execute echo -e "\na\nb\nc\n" at the command line, I get: a b c However, if I wrap it in an assignment such as: A="$( echo -e "\na\nb\nc\n" )"then I get a b cIt doesn't show very well,... (4 Replies)
Discussion started by: jamesbor
4 Replies

10. Solaris

Loosing connection after authentication

Hi! I am having a problem when logging in on a solaris 10 server, after typing one or two commands, I lose connectivity, with the following message: server unexpectedly closed network connection I have checked the following: grep `uname -n` /etc/inet/hosts /etc/inet/ipnodes... (8 Replies)
Discussion started by: fretagi
8 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)
All times are GMT -4. The time now is 12:59 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy