12-24-2015
Note that SLES is an "enterprise" distribution. This usually means the compatibility is limited to fewer (industrial grade) hardware platforms and a consumer PC (respectively its components) you got from your next boxshifter might just not be supported.
In such a case you might want to use another distribution with a broader set of drivers, like (plain) "SuSE" instead of "SuSE Linux Enterprise".
I hope this helps.
bakunin
10 More Discussions You Might Find Interesting
1. Solaris
Hey all,
I'm a newbie to iso files and I just downloaded
the 2 iso files for *cough* ms2003 R2 *cough*
trial software. After I downloaded the iso files
I just dragged them to my burn software gui
and sure enough it burned to dvd 2 iso files.
When I attempted to boot the image using VMware... (0 Replies)
Discussion started by: bdsffl
0 Replies
2. Filesystems, Disks and Memory
In our HP/Unix system, our master scsi drive was bootable and our mirrored drive was non-bootable. Are any of these alternatives possible:
1) Make the non-bootable scsi drive bootable? How?
2) Create a bootable scsi drive, then copy the mirrored data to the newly created scsi drive?
I seek... (1 Reply)
Discussion started by: bfisk
1 Replies
3. Linux
Hi everyone,
I want to run on VMWare the Linux XP 2010 Desktop 4.0.31 distro, Iīve downloaded the latest realese from its website (Trustverse Desktop 4.0 RC1 -build 31)-->http://www.linux-xp.com/desktop/download/.
Itīs 4.47 GB in size, but when I mount on an ISO software, the size is 2.75GB... (0 Replies)
Discussion started by: cgkmal
0 Replies
4. Linux
I just tried to run the command
kexec memtest86-4.0.iso
To boot into memtest86 using kexec.
This is the output:
Cannot determine the file type of memtest86-4.0.iso
How am I supposed to do this? (2 Replies)
Discussion started by: locoroco
2 Replies
5. Fedora
I need to boot the ultimate boot cd from an usb stick. Do I just copy the iso image to the usb key?
How do I make the usb stick bootable? (4 Replies)
Discussion started by: locoroco
4 Replies
6. Red Hat
Hi All,
I want to create kick start bootable ISO file. I have Centos 5.4 ISO and customized ks.cfg file. Now I need to recreate ISO with ks.cfg and content of existing ISO.
During installation, it automatically should pick the kick start file and need to proceed with the installation.
... (0 Replies)
Discussion started by: kalpeer
0 Replies
7. Red Hat
Hello Everyone,
Can anyone let me know how to make minimal boot.iso from rhl6 installation dvd iso image. I have a dvd image with me but i want to make just a minimal boot media. Somehow it is not shipped with dvd iso. I know we can download boot.iso from redhat site but is there any anyway we... (5 Replies)
Discussion started by: Rohit Bhanot
5 Replies
8. Red Hat
Hi All,
I have one query on creating bootable ISO.
I have installed Centos 5.6 and done few configuration changes which is needed for deploying my App. Later I have deployed my app. Now Centos is up and running in a dedicated box along with my app.
Now I want to create the... (3 Replies)
Discussion started by: kalpeer
3 Replies
9. Red Hat
Hi All
On one of my sandbox machine, I want to replace RHEL 6.2 to RHEL 7.3.
I am using both developer editions.
rhel-server-7.3-x86_64-dvd.iso ... This is what I have downloaded from
Red Hat Enterprise Linux Download | Red Hat Developers
My understanding is this file would work as a... (1 Reply)
Discussion started by: videsh77
1 Replies
10. UNIX for Beginners Questions & Answers
I have a .dmg file which was created from a disk consisting of two partitions. When I mount the dmg both partitions pop up, so I know the imaging worked properly. One partition is HFS+ and the other is FAT32.
So far, I've been unable to find a way to restore the dmg to a flash drive where both... (17 Replies)
Discussion started by: paulcristo
17 Replies
LEARN ABOUT SUSE
lsb_release
FSG(1) FSG FSG(1)
NAME
FSG - manual page for FSG lsb_release v2.0-SuSE
SYNOPSIS
lsb_release [OPTION]...
DESCRIPTION
FSG lsb_release v2.0-SuSE prints certain LSB (Linux Standard Base) and Distribution information.
With no OPTION specified defaults to -v.
OPTIONS
-v, --version
Display the version of the LSB specification against which the distribution is compliant.
-i, --id
Display the string id of the distributor.
-d, --description
Display the single line text description of the distribution.
-r, --release
Display the release number of the distribution.
-c, --codename
Display the codename according to the distribution release.
-a, --all
Display all of the above information.
-s, --short
Use short output format for information requested by other options (or version if none).
-h, --help
Display this message.
FILES
If the installation is LSB compliant, the "/etc/lsb-release" file should contain the LSB_VERSION field. The value of the field should be a
colon separated list of supported module versions indicating the LSB specification modules to which the installation is compliant. If the
installation is not compliant, the above field should not be present.
Optional fields are DISTRIB_ID, DISTRIB_RELEASE, DISTRIB_CODENAME, DISTRIB_DESCRIPTION and can be used to override information which is
parsed from the "/etc/distrib-release" file.
If the "/etc/lsb-release.d" directory exists, it is searched for filenames which are taken as additional module-version strings to add to
LSB_VERSION.
The "/etc/distrib-release" file contains a description line which is parsed to get information (especially on currently non-LSB compliant
systems).
The required line style is:
"Distributor release x.x (Codename)"
Where Distributor can be a couple of words, but then concatenated (i.e. Linux Foo BarLinux Linux -> FooBarLinux),
x.x starts with a digit followed by any non-blank characters, Codename will also be concatenated (blanks cleanup only).
release may not be used as a keyword in DISTRIB_DESCRIPTION if you don't want to override "/etc/distrib-release" data.
Notice: To support the Debian distributions' lack of information (see "/etc/debian_version" file) some have been directly added into the
lsb_release script.
EXAMPLES
If the "/etc/lsb-release" file contains:
LSB_VERSION="core-2.0-ia64:core-2.0-noarch"
DISTRIB_DESCRIPTION="I enjoy using my distrib"
and the "/etc/lsb-release.d" directory contains:
graphics-2.0-ia64 graphics-2.0-noarch
and the "/etc/foobar-release" file contains:
My Linux Distrib release 1.0RC4 (TryIt)
Then the results of various options will be:
$ ./lsb_release --all
LSB Version: core-2.0-ia64:core-2.0-noarch:graphics-2.0-ia64:graphics-2.0-noarch
Distributor ID: MyDistrib
Description: I enjoy using my distrib
Release: 1.0RC4
Codename: TryIt
$ ./lsb_release -a -s
1.0 MyDistrib "I enjoy using my distrib" 1.0RC4 TryIt
If the "/etc/lsb-release" file is absent (indicating this is not an LSB compliant distribution), the result will be:
$ ./lsb_release -a
LSB Version: n/a
Distributor ID: MyDistrib
Description: My Linux Distrib release 1.0RC4 (TryIt)
Release: 1.0RC4
Codename: TryIt
REPORTING BUGS
Report bugs at http://bugs.linuxbase.org. Please include a complete, self contained example that will allow the bug to be reproduced, and
say which version of lsb_release you are using.
COPYRIGHT
Copyright (C) 2000, 2002, 2004 Free Standards Group, Inc.
This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICU-
LAR PURPOSE.
Originally written by Dominique MASSONIE.
FSG lsb_release v2.0-SuSE July 2010 FSG(1)