From: markus reichelt <ml@mareichelt.de>
To: linux-kernel@vger.kernel.org
Subject: Re: /dev/loop* devices not appearing in /dev (at least since 2.6.22-rc3*)
Date: Thu, 14 Jun 2007 17:44:48 +0200 [thread overview]
Message-ID: <20070614154448.GC4155@tatooine.rebelbase.local> (raw)
In-Reply-To: <20070614172234.7f636307@localhost>
[-- Attachment #1: Type: text/plain, Size: 786 bytes --]
* Paolo Ornati <ornati@fastwebnet.it> wrote:
> So with this patch "max_loop=32" will create 32 loop devices... but
> then it doesn't allow more of them.
Well, that's what a max_ parameter implies ;p
A manually set limit of loop devices is ok with me. (32 was just an
example -- After all, I could have chosen 256 just to annoy some
people :-)
And with the recent hype of creating things when needed, or even
recycling already used ones (sdx), I worry that this impacts
stability or even usability as a whole. (yes, it's a -rc release ...)
I'll be staying with 2.6.20.x for a year or so. Get the newly
introduced bugs squashed before they have a chance to bug me, heh ;P
PS: Just wondering: Who came up with this "on-demand" hype?
--
left blank, right bald
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-06-14 15:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-14 11:37 Matthew
2007-06-14 12:52 ` Paolo Ornati
2007-06-14 14:10 ` Matthew
2007-06-14 15:22 ` Paolo Ornati
2007-06-14 15:44 ` markus reichelt [this message]
2007-06-14 16:32 ` Matthias Schniedermeyer
2007-06-15 9:00 ` Jan Engelhardt
2007-06-14 12:52 ` markus reichelt
2007-06-15 9:01 ` Jan Engelhardt
2007-06-15 11:19 ` Simon Arlott
2007-06-15 17:19 ` Paolo Ornati
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=20070614154448.GC4155@tatooine.rebelbase.local \
--to=ml@mareichelt.de \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®