similar to: Processed: jessie

Processing commands for control at bugs.debian.org: > user debian-qa at lists.debian.org Setting user to debian-qa at lists.debian.org (was anbe at debian.org). > tags 714794 - moreinfo Bug #714794 {Done: Gilles Filippini <pini at debian.org>} [release.debian.org] pu: package sikuli/1.0~x~rc3.tesseract3-dfsg1-5+deb7u1 Removed tag(s) moreinfo. > tags 710035 - moreinfo Bug #710035

Hello, Need anyone's help regarding issues I encountered during make on iscsitarget-1.40.20 which I get from "svn co https://iscsitarget.svn.sourceforge.net/svnroot/iscsitarget/trunkiscsitarget" checkout revision 481 Issues where found below after a series of my command, as shown: [junix at thesisQRMproject iscsitarget]$ make *cc:

I'm having trouble updating my iscsitarget modules, and it seems to be related to a naming convention mixup? here's the output of the build command: [root at vmhost ~]# rpmbuild --rebuild --sign iscsitarget-0.4.14.96-0.amherst.src.rpm Installing iscsitarget-0.4.14.96-0.amherst.src.rpm error: Failed build dependencies: kernel-devel = 2.6.9-42.0.10.ELlarge is needed by

Hello, I'm running a server that needs to have a kernel 2.4.xxx. So now I'm running a CentOS 3.6 with kernel 2.4.21-37.0.1.ELsmp. Now, I want to make this server usable for ISCSI, so I started to install the ISCSI target, and the problems begin. If I try to install ISCSI version 0.4.13 from source code I got the following error : The present kernel configuration has modules disabled.

I am trying to install Oracle RAC in a two node cluster for testing purposes, so performance is not something that concerns me. I just want to go through the process all the way to creating a database. I have all the prerequisites except the shared storage and thought I'd give this a try. I'm running: - CentOS 5.3 kernel 2.6.18-164.el5 - iscsitarget-1.4.18-1 -

> This should already be useful, at least for file-based disks. It''d be > nice to > have the ENBD script working and have some kind of iSCSI script at some > stage. For iSCSI, have a look at iscsi-init at sourceforge. http://iscsi-init.sourceforge.net. Load it as a module in an initrd and it uses some kernel parameters and automatically configures the network and then

I was looking up on iSCSI in preparation and became aware that there are different iSCSI software/drivers/whatever-is-the-correct-term available. e.g. IET http://iscsitarget.sourceforge.net/ SCST http://scst.sourceforge.net/ STGT http://stgt.berlios.de/ LIO http://linux-iscsi.org/ Based on what I can see, it seems to be STGT because the site provides a link to Redhat advisory which seems to

I really like the idea of Mock Proxies as explained in Brian Takita''s post here: http://pivots.pivotallabs.com/users/brian/blog/articles/352-introducing-rr I posted to this list eariler with an incomplete implementation of .stops_mocking in the thread "Mocking Time, delegating to original object." The Mock Proxy pattern would make this simpler.

Package: blktap-dkms Followup-For: Bug #717157 I picked the commits from upstream. You should consider pushing it to the archive. root at ibmx3650m2-210-147:/usr/src/blktap-2.0.91# diff -Naru ring.c /tmp/ring.c --- ring.c 2013-09-17 11:47:27.468200000 -0400 +++ /tmp/ring.c 2013-09-17 11:47:56.836200000 -0400 @@ -210,7 +210,7 @@ pgoff = 1 + request->usr_idx *

>Yes, jumbo frames, no irq coalescence, blockio and see if >you can get Backup Exec to use large io request sizes when >reading and writing the data. The larger the better. Ok, Jumbo's enabled on the switch and media server. For the sake of our sanity jumping back and forth, I am trying to enable jumbo's on the bonded pair in the target, # ifconfig bond0 mtu 9014 and it errors

Package: blktap-dkms Severity: grave Justification: renders package unusable Hi, blktap-dkms FTBFS against linux 3.10-1 from unstable: Cheers, Moritz CC [M] /var/lib/dkms/blktap/2.0.91/build/control.o In file included from /var/lib/dkms/blktap/2.0.91/build/control.c:30:0: /var/lib/dkms/blktap/2.0.91/build/blktap.h:75:41: warning: variably modified ?pending? at file scope [enabled by

Hola buenas, utlimamente estoy teniendo más problemas con mi equipo de los que debería. Bajo windows no me funciona bien Rstudio y bajo linux soy incapaz de instalar rJava. ¿Alguien que sepa de Linux me podría ayudar? He probado a instalar los openJDK y nada. También he probado, para instalar Java, a hacer un: sudo add-apt-repository ppa:webupd8team/java sudo apt-get update && sudo

Hello everyone, I''m totally new to Xen and trying to run it on some platforms (x86, x64) using SLES (that is what I have to use for reasons other than technical). Several machines on which I tried using Xen simply fails to run normally using Xen kernel: either network communication is not functioning at all despite proper configuration (that works on non-Xen kernel), or the kernel

Hi everyone, I need some help to setup my configuration failover system. My goal is to have a redundance system using Xen + DRBD + Corosync + Pacemaker On Xen I will have one virtual machine. When this computer has network down, I will do a Live migration to the second computer. The first configuration I will need is a crossover cable, won''t I? It is really necessary? Ok, I did it. eth0

I wanted to draw attention to this bug report [A] which highlights a change that was made between Mocha 0.4 and 0.5. It may have lead to tests which pass unexpectedly. Does my explanation (below) make sense to people? It feels like we should at least add some warnings to the documentation. You are correct that this behaviour did change between Mocha v0.4.0 and > v0.5.0 (in revision 115).

I''m not sure if this is a problem with the iscsitarget or zfs. I''d greatly appreciate it if it gets moved to the proper list. Well I''m just about out of ideas on what might be wrong.. Quick history: I installed OS 2008.05 when it was SNV_86 to try out ZFS with VMWare. Found out that multilun''s were being treated as multipaths so waited till SNV_94 came out to

Can someone point me to some documentation on how to set up centos 5.0 as an iscsi target? I'm completely new to iscsi so need something basic. _____________________________________ "He's no failure. He's not dead yet." William Lloyd George -------------- next part -------------- An HTML attachment was scrubbed... URL:

Does anyone have any recommendations for the best way to bring up a iSCSI Target on a C5.3+ server ? Various blogs suggest compiling IET from source, but thats not real appealing to me (not that I can't do it, I just don't want to have to support it long term). I looked in rpmforge but didn't see anything.

Hi List, I've started looking into iSCSI, and I'm wondering if there is an iSCSI target (I've found the initiator in iscsi-initiator-utils) that ships with CentOS, or if not, what the recommended target would be. I'd like to export either a partition or (preferably) a file-as-a-partition. Yours, -S -- Simen Thoresen, Wulfkit Support, Dolphin ICS

Hello fellow sysadmins! I've assembled a whitebox system with a SuperMicro motherboard, case, 8GB of memory and a single quad core Xeon processor. I have two 9650SE-8LPML cards (8 ports each) in each server with 12 1TB SATA drives total. Three drives per "lane" on each card. CentOS 5.2 x86_64. I'm looking for advice on tuning this thing for performance. Especially for the