-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Sunday 2008-02-17 at 17:18 +0100, Anders Johansson wrote:
What on earth is it wanting the network for? Is there some other way to mount the virtual disk without such a thing?
Why are you opposed to it?
Because an attempt to modify my network setup without proper explanation is unjustified and unnecessary. I do not see why creating a network device is needed to _mount_ a disk.
It smells of virus or trojan. :-/
Just to make it clear: a network block device is not a network device, it is a way to access a block device (disk) over a network connection
Well, that's better. But I don't see why it needs a network connection to mount a local file. [...] Demonstration: nimrodel:/Reserva/vmware/Virtual Machines/Windows Me # file /Reserva/vmware/Virtual\ Machines/Windows\ Me/Windows\ Me-flat.vmdk /Reserva/vmware/Virtual Machines/Windows Me/Windows Me-flat.vmdk: x86 boot sector nimrodel:/Reserva/vmware/Virtual Machines/Windows Me # vmware-mount.pl -p Windows\ Me.vmdk -------------------------------------------- VMware for Linux - Virtual Hard Disk Mounter Version: 1.0 build-56528 Copyright 1998 VMware, Inc. All rights reserved. -- VMware Confidential -------------------------------------------- Nr Start Size Type Id Sytem -- ---------- ---------- ---- -- ------------------------ 1 63 16771797 BIOS C Win95 FAT32 (LBA) Offset is 63*512. So: nimrodel:/Reserva/vmware/Virtual Machines/Windows Me # losetup -o 32256 /dev/loop5 Windows\ Me-flat.vmdk nimrodel:/Reserva/vmware/Virtual Machines/Windows Me # file -s /dev/loop5 /dev/loop5: x86 boot sector, code offset 0x58, OEM-ID "MSWIN4.1", sectors/cluster 8, reserved sectors 34, Media descriptor 0xf8, heads 255, hidden sectors 63, sectors 16771792 (volumes > 32 MB) , FAT (32 bit), sectors/FAT 16347, reserved3 0x800000, serial number 0x432917ea, label: "BOOT-VMWARE" nimrodel:/Reserva/vmware/Virtual Machines/Windows Me # mount -o ro /dev/loop5 ../mnt1/ nimrodel:/Reserva/vmware/Virtual Machines/Windows Me # ls ../mnt1/ .windows-label Data PropiedadesSistema.ps autoexec.bat config.bak netlog.txt ut .windows-serial Desinstalados PropiedadesSistemaPorConexion.ps bootlog.prv config.sys nvidia windows 0_Disco_C_hdc1_320.0_GB Images Recycled bootlog.txt gs scandisk.log 0_Notas_Midnight_Comander My Documents WUTemp cabs hp2P.ps setupxlg.txt See? There is no need to warn about wrong kernel version, use any network, etc. I did it. It just took some time for me to think it out, I thought I would have to use the device mapper when I discovered the -o option for losetup. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFHuLBbtTMYHG2NR9URAkP5AKCSInvS/EgkHielAfLwr2YkHQX0NACfbje2 Lcf9EEfvXn7AUJlI22xuFX4= =Riyx -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org