On Wednesday 21 February 2007, Neil Bothwick wrote:
> On Wed, 21 Feb 2007 09:51:45 +0200, Alan McKinnon wrote:
> > That would be true except I've beeen setting loop to since many
> > kernel versions back. I actually suspect it's more a udev thing,
> > there has been a lot of activity and changes
On Wed, 21 Feb 2007 09:51:45 +0200, Alan McKinnon wrote:
> That would be true except I've beeen setting loop to since many
> kernel versions back. I actually suspect it's more a udev thing, there
> has been a lot of activity and changes with the rules recently. But I'm
> too rushed to decrypt
On Wednesday 21 February 2007, Walter Dnes wrote:
> If you want loopback devices to "just work", they should be
> compiled into the kernel, like so...
>
> make menuconfig
> Device Drivers --->
> Block devices --->
> <*> Loopback device support
>
> My guess is that somewhere along the line, th
On Mon, Feb 19, 2007 at 12:35:13PM +0200, Alan McKinnon wrote
> Hi all,
>
> Kernel 2.6.20-gentoo
>
> My various /dev/loop/* devices used to always JustWork, until a recent
> update. Unfortunately I can't tell when the breakage happened.
>
> Right now what happens is I don't get these devices au
Hi all,
Kernel 2.6.20-gentoo
My various /dev/loop/* devices used to always JustWork, until a recent
update. Unfortunately I can't tell when the breakage happened.
Right now what happens is I don't get these devices automatically
and 'mount - o loop' fails. A simple 'modprobe loop' fixes this,
5 matches
Mail list logo