From: Uwe Thiem <uwix@iway.na>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: SOLVED Creating loop devices
Date: Mon, 30 Oct 2006 20:28:37 +0200 [thread overview]
Message-ID: <200610302028.37169.uwix@iway.na> (raw)
In-Reply-To: <200610301759.53225.alan@linuxholdings.co.za>
On 30 October 2006 17:59, Alan McKinnon wrote:
> On Monday 30 October 2006 16:57, Harm Geerts wrote:
> > On Monday 30 October 2006 13:54, Alan McKinnon wrote:
> > > Hi all,
> > >
> > > I seem to be missing my loop devices in /dev...
> > > And I don't find any docs on the current method to do this. I
> > > imagine it's done with udev rules - anyone have working rules for
> > > this that they'd be willing to share?
> > >
> > > alan
> >
> > Do you have support for loop devices in your kernel?
> > udev has default rules for this in /etc/udev/rules.d/50-udev.rules
>
> Problem solved! With the last kernel upgrade I must have changed my loop
> devices from compiled in to modular, and there's no "loop" entry
> in /etc/modules.autoload.d/kernel-2.6. If I "modprobe loop" everything
> works like it's supposed to.
Hm... My loop devices are compiled as modules, I don't have any loop entry
in /etc/modules.autoload.d/kernel-2.6 - but my loop devices are all there
under /dev.
Magic? White magic, black magic? Actually, this white=good and black=bad stuff
is a bit of a no-no here in Africa. ;-)
Uwe
--
Mark Twain: I rather decline two drinks than a German adjective.
http://www.SysEx.com.na
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2006-10-30 19:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-30 12:54 [gentoo-user] Creating loop devices Alan McKinnon
2006-10-30 13:05 ` F.J.Zhao
2006-10-30 15:50 ` Alan McKinnon
2006-10-30 14:57 ` [gentoo-user] " Harm Geerts
2006-10-30 15:49 ` Novensiles divi Flamen
2006-10-30 16:41 ` Alan McKinnon
2006-10-30 15:59 ` [gentoo-user] Re: SOLVED " Alan McKinnon
2006-10-30 18:28 ` Uwe Thiem [this message]
2006-10-31 7:04 ` Alan McKinnon
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=200610302028.37169.uwix@iway.na \
--to=uwix@iway.na \
--cc=gentoo-user@lists.gentoo.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