| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Fri, 23 Mar 2007 00:37:44 +0100 From: "roland" <devzero@....de> To: <linux-kernel@...r.kernel.org> Subject: Re: max_loop limit partitions on loop or device-mapper devices ? you can use kpartx tool for this. bryn m. reeves told me, that it's probably poissible to create udev rules that will automatically create partition maps when a new loop device is setup, which is better than adding partitioning logig into dm-loop for example. example: >kpartx -a /dev/mapper/loop0 > ># ls /dev/mapper/loop0* >/dev/mapper/loop0 /dev/mapper/loop0p1 /dev/mapper/loop0p2 >/dev/mapper/loop0p3 i have seen a patch for loop.c doing this, though. search the archives for this regards roland On Thu, Mar 22, 2007 at 02:33:14PM +0000, Al Viro wrote: > Correction: current ABI is crap. To set the thing up you need to open > it and issue an ioctl. Which is a bloody bad idea, for obvious reasons... Agreed. What would be a right way? Global device ala ptmx/tun/tap? New syscall? Something else? OG. - ] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists