From: devzero@web.de
To: dm-devel@redhat.com
Subject: Re: device mapper integrated loops - and one more year !
Date: Sun, 19 Nov 2006 12:30:05 +0100 [thread overview]
Message-ID: <1439173022@web.de> (raw)
Hello !
after desparately seeking for a solution to have more than 256 loop devices (for a huge cd-rom server), i have recently come across dm-loop, which looks very promising (to replace loop.c)
can i have more than 256 devices which this?
our cd-rom server is going to have more than 256 iso-images soon and i need to upgrade to a more recent OS, anyway, so this won`t be a problem that dm-loop is so brand new.
but - any timeline for dm-loop mainline inclusion ?
should i wait for 2.6.19 or 2.6.20 ?
is it already useable with less recent kernels, i.e. can i download dm-loop patch and recent dmsetup tool and use with older kernel ?
i really would like to give it a try - no problem if there are still bugs inside, because i`d happily test and report if there are bugs left.
regards
Roland K.
systems engineer
_______________________________________________________________________
Viren-Scan für Ihren PC! Jetzt für jeden. Sofort, online und kostenlos.
Gleich testen! http://www.pc-sicherheit.web.de/freescan/?mc=022222
next reply other threads:[~2006-11-19 11:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-19 11:30 devzero [this message]
2006-11-21 21:11 ` Re: device mapper integrated loops - and one more year ! Bryn M. Reeves
2006-11-21 21:55 ` Roland PJ
2006-11-21 23:20 ` Bryn M. Reeves
2006-11-22 8:29 ` Roland Paterson-Jones
2006-11-22 21:37 ` Bryn M. Reeves
2006-11-23 11:15 ` Roland Paterson-Jones
-- strict thread matches above, loose matches on Subject: below --
2007-01-20 14:57 devzero
2007-01-22 9:43 ` Bryn M. Reeves
2006-10-06 9:38 David Guyon Martin
2006-10-09 22:36 ` Jonathan E Brassow
2006-10-10 18:37 ` Heinz Mauelshagen
2006-10-10 20:11 ` David Guyon Martin
2006-10-05 14:26 David Guyon Martin
2006-10-05 19:40 ` Alasdair G Kergon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1439173022@web.de \
--to=devzero@web.de \
--cc=dm-devel@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.