In article ,
Michael van Elst wrote:
>m...@netbsd.org (Emmanuel Dreyfus) writes:
>
>>But since almost all commands do the NAME=label to /dev/device translation,
>>you can take NAME=label as a device path.
>
>Only some NetBSD commands do. Most are old-fashioned and want file paths
>to deal with, an
On Wed, Sep 18, 2019 at 01:24:24PM -0700, John Nemeth wrote:
> We just need the device path to be the name, which it already
> is for LVMs. This is something that a devfs could do easily. :->
> More seriously, I do believe that a devfs would be a good thing.
Ah, a can of worms, open too. :
On Sep 18, 2:57pm, Michael van Elst wrote:
}
} >Is there a reason why we do not translate wedges devices to their name?
} >I mean, df and mount report about /dev/dkN, which is not very helpful
} >since it can change quickly. Reporting about NAME= seems a better idea.
}
} >In order to do it, we n
m...@netbsd.org (Emmanuel Dreyfus) writes:
>But since almost all commands do the NAME=label to /dev/device translation,
>you can take NAME=label as a device path.
Only some NetBSD commands do. Most are old-fashioned and want file paths
to deal with, and that's where the current mount output may c
On Wed, Sep 18, 2019 at 02:57:39PM -, Michael van Elst wrote:
> It's not necessarily a good idea to hide the dk devices, so that probably
> needs to be an optional output. Also because there are people parsing
> such output and expect a device path.
But since almost all commands do the NAME=la
m...@netbsd.org (Emmanuel Dreyfus) writes:
>Hello
>Is there a reason why we do not translate wedges devices to their name?
>I mean, df and mount report about /dev/dkN, which is not very helpful
>since it can change quickly. Reporting about NAME= seems a better idea.
>In order to do it, we need a
Hello
Is there a reason why we do not translate wedges devices to their name?
I mean, df and mount report about /dev/dkN, which is not very helpful
since it can change quickly. Reporting about NAME= seems a better idea.
In order to do it, we need a reverse getfsspecname(), and use it everywhere
r
