Skip to contentSkip to conversation

New device naming convention

DISCUSSION Guillaume Boissiere 2 participants 3 messages Feb 1, 2002 – Feb 6, 2002

lore
Share & tools
lore
#0 lore raw

I added this item on my kernel 2.5 status list a few weeks ago, and it seems to be _the_ hot topic for 2.5.

o Pending Finalize new device naming convention (Linus Torvalds)

What exactly are people expecting Linus to decide on? And once it has been decided, what is the next step after that?

I really don't want to start a flame war on the subject (so please refrain from rants), I am just trying to understand what people are waiting for.

Anyone care to explain? Thanks,

-- Guillaume

#1 lore raw
Quoted 7 lines · On Fri 01 Feb at 01:39:15 -0500 [email protected] done said:

I added this item on my kernel 2.5 status list a few weeks ago, and it seems to be _the_ hot topic for 2.5.

o Pending Finalize new device naming convention (Linus Torvalds)

What exactly are people expecting Linus to decide on? And once it has been decided, what is the next step after that?

I tried to explain when I asked that it be added to the list...here's another go:

I think there are various (especially hotpluggable?) subsystems where people have issues, but here's one example...

Say I'm a big file or db server in a fibre channel environment and have 1000 disk luns on various disk subsystems and there happen to be 8 paths to those luns because of how the fabric is set up. What do those 8000 'sd' devices get named. And will there be persistence of whatever the name is? If I'm booting off 'sdfoo' will the device (host:bus:target:lun) behind that name be the same between scsi driver loads. Right now the user just has to know and control what's going on magically and make sure the right thing happens. This might work on a couple devices in your pc for which you can easily look and see what all the luns are and deduce how the sd's get populated, figure out which one is the disk you want. But it doesn't scale. Persistence may be best solved in userspace, but right now the kernel assures that there isn't any.

There've been huge discussions in the past about how to handle /dev; they're in the archive. Is it a problem that needs an answer? Is devfs the answer? Will an answer be in 2.5?

t.

Signature · 4 lines
*********************************************************
*  tpepper@vato dot org             * Venimus, Vidimus, *
*  http://www.vato.org/~tpepper     * Dolavimus         *
*********************************************************
#2 lore raw
Quoted 8 lines · Tim Pepper
Quoted 7 lines · On Fri 01 Feb at 01:39:15 -0500 [email protected] done said:

I added this item on my kernel 2.5 status list a few weeks ago, and it seems to be _the_ hot topic for 2.5.

o Pending Finalize new device naming convention (Linus Torvalds)

What exactly are people expecting Linus to decide on? And once it has been decided, what is the next step after that?

[snip...]

Thanks for the explanations, that was pretty helpful to illustrate the current issues.

Quoted 3 lines

There've been huge discussions in the past about how to handle /dev; they're in the archive. Is it a problem that needs an answer? Is devfs the answer? Will an answer be in 2.5?

Yes, that's the $1000 question! If there is nothing people are expecting Linus to decide on for 2.5 regarding device naming, let me know and I'll remove this item from my status list.

-- Guillaume