From: Kevin Corry <corryk@us.ibm.com>
To: evms-devel@lists.sourceforge.net
Cc: evms-announce@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: [ANNOUNCE] EVMS Release 1.0.0
Date: Thu, 28 Mar 2002 18:16:24 -0600 [thread overview]
Message-ID: <02032818104600.29828@boiler> (raw)
The EVMS team is announcing the first full release of the Enterprise Volume
Management System. Package 1.0.0 is now available for download at the project
web site:
http://www.sf.net/projects/evms
Highlights for version 1.0.0:
v1.0.0 - 3/28/02
- Core Kernel
- Support for /proc.
- New directory /proc/evms/.
- File entries: volumes, info, plugins
- Sysctl entry: /proc/sys/dev/evms/evms_info_level can be used to
query and set the EVMS kernel messaging level.
- GUI
- Option panel fixes.
- New columns in most panels: Read-only and Corrupt.
- Default engine logging level changed from "everything" to "default".
- Check for minimum required engine API version.
- Text-Mode UI
- Added "F5=Commit" to menu to allow saving changes without exiting.
- Screen refresh fixes.
- Default engine logging level changed from "everything" to "default".
- Check for minimum required engine API version.
- Command Line
- On-line help cleanup.
- New Plugin: s390 Segment Manager
- Recognizes existing CDL, LDL, and CMS partitions.
- Can build on top of these partitions in the engine, but
cannot yet create new s390 partitions.
- MD Plugin
- Added proc entry: /proc/evms/mdstat
- Added sysctl entries: /proc/sys/dev/evms/md/speed_limit_[min|max] for
controlling the speed of RAID-1 and RAID-5 sync'ing.
- BBR Plugin
- Bug fixes to the I/O error remap handling.
- AIX Plugin
- Bug fixes in the discovery path and mirroring I/O path.
- LVM Plugin
- Added proc entry: /proc/evms/lvm/global
Kevin Corry
corryk@us.ibm.com
Enterprise Volume Management System
http://www.sf.net/projects/evms
reply other threads:[~2002-03-29 0:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=02032818104600.29828@boiler \
--to=corryk@us.ibm.com \
--cc=evms-announce@lists.sourceforge.net \
--cc=evms-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox