Re: [RFC PATCH] /sys/block -> /sys/class/block (Fedora 3 & 4 testers wanted)

[Cornelia Huck <cornelia.huck@de.ibm.com>]

On Mon, 21 May 2007 16:53:53 -0700,
Greg KH <greg@kroah.com> wrote:

> So, could anyone still running the crufty and unsupported Fedora 3 and 4
> releases test this patch out and let us know if it boots your machine or
> not?  I don't want to break legacy distros if we can possibly help it.
> 
> This has been successfully tested on both SuSE and Gentoo boxes, so
> we do hope this works for others.

Unfortunately, it doesn't :(

I tried this on one of our internal drivers, which is based on FC 3 (or
4, can look this up). With s390 defconfig, it is unable to open the
root device /dev/dasda1 (which is unsurprising, considering udev (063)
decided to create /dev/dasda(1) as a character node instead of a block
node). The only udev rule I found which could affect the dasd device
nodes is

SUBSYSTEM=="block",             GROUP="disk", MODE="0640"

When I look at the system, /sys/block/ and /sys/class/block/ look sane
at first glance (working on a 3270 console is usally PITA...)

Even more surprisingly, the system comes up fine (once I added ptmx to
makedev.d/) with CONFIG_SYSFS_DEPRECATED not set. /sys/block/
and /sys/class/block/ look just like expected. (Unfortunately, our
lsdasd tool breaks with this...)

I'll see if I can find out more.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/