Does devlable support RedHat Linux 5.5 or later version?

 
Thread Tools Search this Thread
Operating Systems Linux Red Hat Does devlable support RedHat Linux 5.5 or later version?
# 1  
Old 08-23-2011
Does devlable support RedHat Linux 5.5 or later version?

Dear Guru,

Last time when I install ORACLE RAC with ASM, I have use udev to mapping the raw device. Someone told me that "devlable" is good tool to achieve that. But I can find the rpm package for Linux 5.5.

Look devlable only for x86 system? Am I right?

What is the different between: udev and devlable?

Thanks for any comments!
David Feng
Login or Register to Ask a Question

Previous Thread | Next Thread

9 More Discussions You Might Find Interesting

1. Red Hat

RedHat version in rpm spec files

Hi In opensuse we have this nice version control variable I use much when designing rpm spec files: rpm --showrc | grep suse_version %if 0%{?suse_version} > 0 && 0%{?suse_version} < 1700 -14: suse_version 1140But I do not find anything close to this in rhel/centos The only way... (0 Replies)
Discussion started by: mortenb
0 Replies

2. UNIX for Dummies Questions & Answers

How to get Xconsole of Redhat 5 version.

Hi How would i get xconsole of redhat5 linux machine. Following is the distribution detail. # lsb_release -a LSB Version: :core-3.1-ia32:core-3.1-noarch:graphics-3.1-ia32:graphics-3.1-noarch Distributor ID: RedHatEnterpriseServer Description: Red Hat Enterprise Linux Server release 5.5... (1 Reply)
Discussion started by: pinga123
1 Replies

3. Red Hat

Differences in the version of RedHat linux 5.2 and 9.0.

hi , Can anybody please let me know the difference in the version of RedHat linux 5.2 and 9.0. Will there be any difference if i execute the script in RedHat linux 9.0 insead of RedHat linux 5.2? Thanks in Advance. (7 Replies)
Discussion started by: flamingo_l
7 Replies

4. Red Hat

Redhat Enterprise version 4 RHEL4 patches

Hi, I would like to know if should i patch my system and sshd based on the version that i have here below: cat /etc/redhat-release Red Hat Enterprise Linux ES release 4 (Nahant Update 5) ------------ uname -a: redhat kernel version and type (64-bit or not) Linux server2 2.6.9-55.ELsmp... (2 Replies)
Discussion started by: lamoul
2 Replies

5. UNIX for Advanced & Expert Users

Find RedHat version.

How can I find out with a C program, on which RedHat version the program is being ran ? I do know through compilation variables that I'm on RedHat but so far cannot find out which one. Currently the closest I got was to invoke an ls or cat through syscall for the release or motd files. ... (5 Replies)
Discussion started by: amirvosko
5 Replies

6. UNIX for Dummies Questions & Answers

Redhat linux command to check Version

Hi All, I need to know RedHat linux version installed on a different servers. I know uname -a or /proc/version Is any other command to know the Linux version???? When we telnet to any of the Linux server, the version shows very clearly like Red Hat Enterprise Linux ES release 3 (Taroon... (1 Reply)
Discussion started by: bache_gowda
1 Replies

7. Linux Benchmarks

Dual Xeon 2.6, RedHat EL 4 ES, up to latest release version. 2.6.9 kernel

============================================================== BYTE UNIX Benchmarks (Version 3.11) System -- Linux linux.hhc.ac.uk 2.6.9-11.ELsmp #1 SMP Fri May 20 18:26:27 EDT 2005 i686 i686 i386 GNU/Linux Start Benchmark Run: Wed Jul 6 15:06:07 BST 2005 1 interactive users.... (2 Replies)
Discussion started by: Garp
2 Replies

8. Linux

Linksys WPC11 Version 4 (NOT FOR REDHAT!)

I just purchased a Linksys WPC11 Version 4 wireless PCMCIA card, and am looking for the device driver for it. Apparently, as opposed to Version 1-4, it uses a RealTek 8180 chipset. However, the kernel module which Linksys released does not work on any other distribution EXCEPT for Redhat Linux.... (0 Replies)
Discussion started by: Farhan
0 Replies

9. UNIX for Dummies Questions & Answers

Redhat linux version

Guys How do i know the version of linux (Redhat) on one of our systems..Thanks in advance..The uname -r gives 2.4.18-0.13..Is it the kernel version (3 Replies)
Discussion started by: sssow
3 Replies
Login or Register to Ask a Question
SYSTEMD.DEVICE(5)						  systemd.device						 SYSTEMD.DEVICE(5)

NAME
systemd.device - Device unit configuration SYNOPSIS
device.device DESCRIPTION
A unit configuration file whose name ends in ".device" encodes information about a device unit as exposed in the sysfs/udev(7) device tree. This unit type has no specific options. See systemd.unit(5) for the common options of all unit configuration files. The common configuration items are configured in the generic "[Unit]" and "[Install]" sections. A separate "[Device]" section does not exist, since no device-specific options may be configured. systemd will dynamically create device units for all kernel devices that are marked with the "systemd" udev tag (by default all block and network devices, and a few others). This may be used to define dependencies between devices and other units. To tag a udev device, use "TAG+="systemd"" in the udev rules file, see udev(7) for details. Device units are named after the /sys and /dev paths they control. Example: the device /dev/sda5 is exposed in systemd as dev-sda5.device. For details about the escaping logic used to convert a file system path to a unit name see systemd.unit(5). THE UDEV DATABASE
The settings of device units may either be configured via unit files, or directly from the udev database (which is recommended). The following udev device properties are understood by systemd: SYSTEMD_WANTS= Adds dependencies of type Wants from the device unit to all listed units. This may be used to activate arbitrary units when a specific device becomes available. Note that this and the other tags are not taken into account unless the device is tagged with the "systemd" string in the udev database, because otherwise the device is not exposed as systemd unit (see above). Note that systemd will only act on Wants dependencies when a device first becomes active, it will not act on them if they are added to devices that are already active. Use SYSTEMD_READY= (see below) to influence on which udev event to trigger the device dependencies. SYSTEMD_ALIAS= Adds an additional alias name to the device unit. This must be an absolute path that is automatically transformed into a unit name. (See above.) SYSTEMD_READY= If set to 0, systemd will consider this device unplugged even if it shows up in the udev tree. If this property is unset or set to 1, the device will be considered plugged the moment it shows up in the udev tree. This property has no influence on the behavior when a device disappears from the udev tree. This option is useful to support devices that initially show up in an uninitialized state in the tree, and for which a "changed" event is generated the moment they are fully set up. Note that SYSTEMD_WANTS= (see above) is not acted on as long as SYSTEMD_READY=0 is set for a device. ID_MODEL_FROM_DATABASE=, ID_MODEL= If set, this property is used as description string for the device unit. SEE ALSO
systemd(1), systemctl(8), systemd.unit(5), udev(7), systemd.directives(7) systemd 208 SYSTEMD.DEVICE(5)