On Thursday 23 August 2007 9:56:33 pm Jeff Dike wrote:
> On Thu, Aug 23, 2007 at 08:47:33PM -0500, Rob Landley wrote:
> > Does anybody know why loopback mounts stopped working when I went
> > from 2.6.22 to 2.6.23-rc3?  My config didn't change, the only thing
> > that did was which  source tarball I pointed the build at.
>
> Works here - verify that it really doesn't work and provide more
> details:

Yeah, it's not working for me:

> losetup /dev/loop0
> loop: can't open device /dev/loop0: No such device or address

It's probably a build thing.  Probably the config changed since 2.6.22...

Yup.  In additon to CONFIG_BLOCK I now have to enable CONFIG_BLK_DEV in order 
to enable CONFIG_BLK_DEV_LOOP.  Why on EARTH did this subsystem develop two 
redundant guard symbols?  Is there ever a reason to have the block layer 
enabled but no block devices?

(And while we're at it, I don't suppose there's any way to get a list of the 
module names that are statically linked into the kernel?  /proc/modules only 
shows you the dynamically linked ones...)

That's interesting:

> root@(none):/sys# exit
> Kernel panic - not syncing: Attempted to kill init!
> Segmentation fault (core dumped)

UML now segfaults on a panic?

Anyway, this was "upgrading to 2.6.23-rc3" breakage, not UML specific...

Thanks,

Rob
-- 
"One of my most productive days was throwing away 1000 lines of code."
  - Ken Thompson.

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
User-mode-linux-user mailing list
User-mode-linux-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-user

Reply via email to