IF YOU WOULD LIKE TO GET AN ACCOUNT, please write an
email to Administrator. User accounts are meant only to access repo
and report issues and/or generate pull requests.
This is a purpose-specific Git hosting for
BaseALT
projects. Thank you for your understanding!
Только зарегистрированные пользователи имеют доступ к сервису!
Для получения аккаунта, обратитесь к администратору.
These s390-tools-1.6.0 (applicable for the "October 2005 stream") replace s390-tools-1.5.4.
New tools:
* tape390_crypt: Tool to control and query crypto settings for 3592 zSeries tape devices.
* mon_fsstatd: Daemon that writes filesystem utilization data to the z/VM monitor stream.
* dumpconf: Allows to configure the dump device used for system dump in case a kernel panic occurs.
* dasdinfo: Display unique DASD ID, either uid or volser.
* 59-dasd.rules: udev rules for unique DASD device nodes created in /dev/disk/.
http://www.ibm.com/developerworks/linux/linux390/s390-tools-1.6.0.html
Seems we find the md signature in cpu-order on the disk. Let's
look for both endian encodings ...
Thanks to Michael Prokop for his help finding the bug.
Bryan Kadzban wrote:
> Marco d'Itri wrote:
> > Bryan Kadzban wrote:
> >
> > > This is a sort of follow-up of my path-based persistence patch for
> > > net devices; it's the opposite type of addition for CD symlinks.
> >
> > Looks good. I am attaching a slightly reformatted version, I think it
> > should be applied.
>
> That's probably a lot more clear than my version anyway: what you posted
> looks like it does basically the same thing, just with some changes in
> the order and sense of checks.
This scheme is more consistent and makes it obvious if a match happens
against the event device only, or the full chain of parent devices.
The old key names are now:
BUS -> SUBSYSTEMS
ID -> KERNELS
SYSFS -> ATTRS
DRIVER -> DRIVERS
Match keys for the event device:
KERNEL
SUBSYSTEM
ATTR
DRIVER (in a future release, for now the same as DRIVERS)
Match keys for all devices along the parent device chain:
KERNELS
SUBSYSTEMS
ATTRS
DRIVERS
ID, BUS, SYSFS are no longer mentioned in the man page but still work.
DRIVER must be converted to DRIVERS to match the new scheme. For now,
an error is logged, if DRIVER is used. In a future release, the DRIVER
key behaviour will change.
