similar to: [PATCH] Replace the HAL calls with udev/systool calls.

It fixes how removable media are detected and removes any device which has no storage space available. Signed-off-by: Darryl L. Pierce <dpierce at redhat.com> --- scripts/ovirt-config-storage | 168 +++++++++++++++++++++++++++++++----------- 1 files changed, 125 insertions(+), 43 deletions(-) diff --git a/scripts/ovirt-config-storage b/scripts/ovirt-config-storage index 5560b5f..f6a30c9

Quote everywhere that we reference wwid in o-c-storage, o-c-boot and ovirt-functions. Signed-off-by: Mike Burns <mburns at redhat.com> --- scripts/ovirt-config-boot | 6 +- scripts/ovirt-config-storage | 178 +++++++++++++++++++++--------------------- scripts/ovirt-functions | 38 +++++----- 3 files changed, 111 insertions(+), 111 deletions(-) diff --git

This patch just includes the repo name in the subject.

This one incorporates feedback from mburns and apevec to ensure that all multipath devices are excluded in the list of available drives. Only drives with an identified bus are included in the list now.

This patch will scan through the list of devices that have the net.80203 capability. It will then also ensure that only those which originate from a physical device and are not logical devices are presented. Resolves: rhbz#511369 Signed-off-by: Darryl L. Pierce <dpierce at redhat.com> --- scripts/ovirt-config-networking | 4 +++- 1 files changed, 3 insertions(+), 1 deletions(-) diff

Signed-off-by: Alan Pevec <apevec at redhat.com> --- scripts/ovirt-config-storage | 31 +++++++++++++++++++------------ 1 files changed, 19 insertions(+), 12 deletions(-) diff --git a/scripts/ovirt-config-storage b/scripts/ovirt-config-storage index be5aec0..671ad7d 100755 --- a/scripts/ovirt-config-storage +++ b/scripts/ovirt-config-storage @@ -36,15 +36,17 @@ logging_min_size=5

This patch includes a fix to no longer list devices with 0 bytes of storage, such as removeable media devices with no media present.

This set of patches introduces support for multipath devices for storage. Comments and suggestions are appreciated. Mike

Putting these out for feedback and comments. These will eventually support the new newt/python based ui for installation/configuration storage.py functions will be moved under a class for better data portability before final version --- scripts/ovirtfunctions.py | 672 +++++++++++++++++++++++++++++++++++++++++++++ scripts/storage.py | 451 ++++++++++++++++++++++++++++++ 2 files

This patch adds a safety verification to configure_from_network function, where network configuration will not be performed if it is already up and running, preventing lost of communication for connections already established. Signed-off-by: Ricardo Marin Matinata <matinata at br.ibm.com> --- scripts/ovirt-early | 9 ++++++--- scripts/ovirt-functions | 7 +++++++ 2 files changed,

Used in conjunction with livecd-iso-to-iscsi. Creates a local boot partition with vmlinuz/initrd and grub configuration. Disk Partitioning > enable iscsi target > configure storage > local install and reboot --- scripts/ovirt-config-boot | 131 +++++++++++++++++++-------------- scripts/ovirt-config-storage | 164 +++++++++++++++++++++++++----------------- tools/livecd-iso-to-iscsi

[was: svn commit r915 - in trunk: . drivers] Hi Kjell, sorry, I'm still much late in emptying my mail stack... 2007/5/25, Kjell Claesson <kjell.claesson at epost.tidanet.se>: > Den Friday 25 May 2007 08.52.20 skrev Arnaud Quette: > > > > I would be interested in some more info: > > - lshal -u <your device's UDI> > > the UDI can be obtained for ex.

If more than one UDI is returned, they are delimited by a carriage return. That is changed to a space, then the lot is iterated over. Each UDI is tested to see if it has the property "block.is_volume=false". If so then that UDI is for the underlying block device and not a logical volume on the device. Signed-off-by: Darryl L. Pierce <dpierce at redhat.com> ---

All other patches from the sequence remain unchanged. Repost of patch 6 based on comments from Joey to follow. Mike

Guys, one of our boxes just died with the following error: kernel panic - not syncing: fs/block_dev.c:396: spin_lock (fs/block_dev.c:c0361c0) already locked by fs/block_dev.c/287. The system's an LVS running CentOS 4.3: centos-release-4-3.2 kernel-2.6.9-34.EL ipvsadm-1.24-6 heartbeat-1.2.3.cvs.20050927-1.centos4 I note that there's a bug report filed related to CentOS 4.2:

If a device is a removeable media device, then o-c-storage will now check if there's media present before attempting to get the storage size for the device. Signed-off-by: Darryl L. Pierce <dpierce at redhat.com> --- scripts/ovirt-config-storage | 5 ++++- 1 files changed, 4 insertions(+), 1 deletions(-) diff --git a/scripts/ovirt-config-storage b/scripts/ovirt-config-storage index

From: John Hubbard <jhubbard at nvidia.com> In commit d241a95f3514 ("block: optionally mark pages dirty in bio_release_pages"), new "bool mark_dirty" argument was added to bio_release_pages. In upcoming work, another bool argument (to indicate that the pages came from get_user_pages) is going to be added. That's one bool too many, because it's not desirable have

> Hello > I complied openssh like this "./configure --with-pam" and I did configure > /etc/pam.conf as follows > # PAM configuration > # > # Authentication management > # > sshd auth required /lib/security/pam_securid.so reserve > sftp auth required /lib/security/pam_securid.so reserve > # > login auth required

Hello, Can anyone advise if there is a limit on the length of share names in Samba when accessing via NT Workstation 4.0 clients? It seems that the limit is 12 characters for NT, our Windows 98, 2000 and XP machines work with longer share names. If so does anyone know if there is a patch to make long share names work with NTWS 4.0? Best regards, Keith

FreeBSD Real-Quick(TM) NewsLetter. Things Happening in FreeBSD. Volume #1 Issue #5 September 1998 Release Information: The latest RELEASE is 2.2.7-RELEASE. FreeBSD 2.2.8 is scheduled to be released November 30th. FreeBSD 3.0 is scheduled to be released October 15th. Start BETA Testing!!! FreeBSD in the News: