All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Ornati <ornati@fastwebnet.it>
To: Matthew <jackdachef@gmail.com>
Cc: 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 14:52:06 +0200	[thread overview]
Message-ID: <20070614145206.58fdec91@localhost> (raw)
In-Reply-To: <e85b9d30706140437s5f3622c3rc86c75a4f845e7a3@mail.gmail.com>

On Thu, 14 Jun 2007 13:37:32 +0200
Matthew <jackdachef@gmail.com> wrote:

> now back to topic:
> 
> /dev/loop* seems to be broken since (at least) 2.6.22-rc3, since that
> was the first kernel I tried of the 2.6.22-rc* series
> 
> ls -l /dev/ | grep loop
> 
> shows no output

Yes, now the "loop" devices are dynamically allocated.... a patch to
provide the 8 "static allocated" loop devices is already in current git
(post -rc4, will be in -rc5).


commit a47653fc2643cf61bcabba8c9ff5c45517c089ba
Author: Ken Chen <kenchen@google.com>
Date:   Fri Jun 8 13:46:44 2007 -0700

    loop: preallocate eight loop devices

    The kernel on-demand loop device instantiation breaks several user space
    tools as the tools are not ready to cope with the "on-demand feature".  Fix
    it by instantiate default 8 loop devices and also reinstate max_loop module
    parameter.


-- 
	Paolo Ornati
	Linux 2.6.22-rc4-cfs-v16-g47932c49 on x86_64

  reply	other threads:[~2007-06-14 12:53 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-14 11:37 /dev/loop* devices not appearing in /dev (at least since 2.6.22-rc3*) Matthew
2007-06-14 12:52 ` Paolo Ornati [this message]
2007-06-14 14:10   ` Matthew
2007-06-14 15:22     ` Paolo Ornati
2007-06-14 15:44       ` markus reichelt
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=20070614145206.58fdec91@localhost \
    --to=ornati@fastwebnet.it \
    --cc=jackdachef@gmail.com \
    --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 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.