[prev in list] [next in list] [prev in thread] [next in thread] 

List:       evms-announce
Subject:    [Evms-announce] EVMS assigned a new major number
From:       Kevin Corry <corryk () us ! ibm ! com>
Date:       2002-07-05 15:16:08
[Download RAW message or body]

Greetings,

As of version 1.1.0-pre4, the EVMS device major number has changed from 63 to 
117.  63 was actually a number reserved for experimental drivers, and EVMS 
has now been assign 117 as a permanent major number. Yeah!!!

How does this affect you?

If you have never run EVMS before, this will not affect you at all, and you 
can stop reading now. :)

If you have run EVMS before, it means any existing volumes you have on your 
system will have device-nodes that currently use the old major number. You 
can verify this by looking in the /dev/evms directory. For example:

$ ls -l /dev/evms
brw-rw-rw-    1 root     root      63, 254 Dec 31  1969 Data
brw-rw-rw-    1 root     root      63, 255 Dec 31  1969 Music
brw-rw-rw-    1 root     root      63,   0 Dec 31  1969 block_device
brw-rw-rw-    1 root     root      63,   1 Dec 31  1969 hda1
brw-rw-rw-    1 root     root      63,   2 Dec 31  1969 hda2
brw-rw-rw-    1 root     root      63,   3 Dec 31  1969 hda5

This shows several EVMS and compatibility volumes with major number 63.


So what should you do about this?

If you are running DevFS, you may not need to do anything. When you boot the 
first time with the EVMS 1.1.0-enabled kernel, DevFS will automatically 
create all of the EVMS device nodes with the correct major number. However, 
please read below for further instructions if you are using the LILO patch 
for EVMS.

If you are not running DevFS, all of your existing device nodes need to be 
changed to reflect the new major number. We have provided a simple Perl 
script that will take care of this for you. However, it must be run 
**BEFORE** you install and reboot with the EVMS 1.1.0-enabled kernel. 
Otherwise, any EVMS volumes in your /etc/fstab file will not mount correctly, 
and the EVMS engine will not run correctly.

Run the script "evms_update_devnodes.pl", which is located in the top 
directory of the 1.1.0-pre4 and later EVMS source packages.

$ ./evms_update_devnodes.pl

This script will recursively search through /dev/evms and recreate all of your
old dev-nodes with the new major number. Again, this script should be run
immediately **BEFORE** you install the 1.1.0-enabled kernel, run LILO and 
reboot. After the script runs, the /dev/evms directory will look like this 
(using the same example from above).

$ ls -l /dev/evms
brw-rw-rw-    1 root     root     117, 254 Dec 31  1969 Data
brw-rw-rw-    1 root     root     117, 255 Dec 31  1969 Music
brw-rw-rw-    1 root     root     117,   0 Dec 31  1969 block_device
brw-rw-rw-    1 root     root     117,   1 Dec 31  1969 hda1        
brw-rw-rw-    1 root     root     117,   2 Dec 31  1969 hda2
brw-rw-rw-    1 root     root     117,   3 Dec 31  1969 hda5


What if I'm using the EVMS patch for LILO?

If you have your kernel image file on an EVMS volume, then you must have
rebuilt LILO using the patch provided in a previous EVMS release. In order for
LILO to recognize the new EVMS major number, it will need to be rebuilt again
with a small change. You can do this in one of two ways:

Choice 1) Start with a fresh copy of the LILO source (version 22.2 or 22.3.1,
          available at http://freshmeat.net/projects/lilo/). Apply the new
          LILO patch, which is available in the "kernel" directory of the
          latest source package, or as a separate download from
          http://www.sf.net/projects/evms. Then rebuild and reinstall LILO.
Choice 2) If you still have the LILO source with the previous EVMS patch
          applied, you can edit the "lilo.h" file, and change the line that
          says "#define MAJOR_EVMS 63" to "#define MAJOR_EVMS 117". Then
          rebuild and reinstall LILO.

However, unlike the script above that updates the dev-nodes, this update to
LILO must be done **AFTER** rebooting into the EVMS 1.1.0-enabled kernel.


If you have any questions or difficulties related to this update, please send
email to the EVMS mailing list: evms-devel@lists.sf.net. These instructions 
can also be found at http://evms.sf.net/new_major.html.

Thanks,
The EVMS Team


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Bringing you mounds of caffeinated joy.
http://thinkgeek.com/sf
_______________________________________________
Evms-announce mailing list
Evms-announce@lists.sourceforge.net
To subscribe/unsubscribe, please visit:
https://lists.sourceforge.net/lists/listinfo/evms-announce
[prev in list] [next in list] [prev in thread] [next in thread]