On 06/02/2009 02:23 PM, Victor Lowther wrote:
On Tue, 2009-06-02 at 14:07 +0200, Harald Hoyer wrote:
On 06/02/2009 02:04 PM, Victor Lowther wrote:
On Tue, 2009-06-02 at 13:41 +0200, Harald Hoyer wrote:
---
modules.d/95iscsi/check | 11 +++
modules.d/95iscsi/install | 8 ++
modules.d/95iscsi/iscsi-netroot.sh | 13 ++++
modules.d/95iscsi/iscsiroot | 121 ++++++++++++++++++++++++++++++++++
modules.d/95iscsi/parse-iscsiroot.sh | 37 ++++++++++
test/TEST-30-ISCSI/Makefile | 10 +++
test/TEST-30-ISCSI/create-root.sh | 34 ++++++++++
test/TEST-30-ISCSI/cryptroot-ask | 6 ++
test/TEST-30-ISCSI/hard-off.sh | 2 +
test/TEST-30-ISCSI/test.sh | 68 +++++++++++++++++++
10 files changed, 310 insertions(+), 0 deletions(-)
create mode 100755 modules.d/95iscsi/check
create mode 100755 modules.d/95iscsi/install
create mode 100755 modules.d/95iscsi/iscsi-netroot.sh
create mode 100755 modules.d/95iscsi/iscsiroot
create mode 100755 modules.d/95iscsi/parse-iscsiroot.sh
create mode 100644 test/TEST-30-ISCSI/Makefile
create mode 100755 test/TEST-30-ISCSI/create-root.sh
create mode 100755 test/TEST-30-ISCSI/cryptroot-ask
create mode 100755 test/TEST-30-ISCSI/hard-off.sh
create mode 100755 test/TEST-30-ISCSI/test.sh
Perhaps I missed it, but where do you create the VM that hosts the isci
target? That would make fully automating this test much easier for
those of us who do not have a spare iscsi target lying around.
Well, for now, I hosted the iSCSI disk on a local NAS.
But, we could setup a small virtual machine that serves the iSCSI disk. I was
just too lazy to do that step now :-)
Understood -- I just found it odd to commit a test suite that only
worked for you.
work in progress :) and yes, I should deactive it for now, until I have created
the iSCSI target VM
--
To unsubscribe from this list: send the line "unsubscribe initramfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
