Hello, [email protected], le ven. 17 avril 2026 15:49:31 +0000, a ecrit: > April 15, 2026 at 6:16 PM, "Samuel Thibault" <[email protected] > mailto:[email protected]?to=%22Samuel%20Thibault%22%20%3Csamuel.thibault%40gnu.org%3E > > wrote: > > Perhaps we could use > > > > settrans -c /dev/hd0s /hurd/partfs /dev/hd0 > > > > and then we'd have /dev/hd0s/1, which is almost like before, but allows > > the entries to be dynamic. Actually, we could even have some > > > > settrans -c /dev/hd /hurd/probedisk hd > > > > and then we'd have /dev/hd/0, and we could have /dev/hd/0s being partfs, > > so we'd eventually have > > > > /dev/hd/0s/1 > > > > But I'm also thinking that perhaps it could be integrated more with > > storeio, i.e. /dev/hd0 can as well also act as a directory with partfs > > behavior, so you could have > > > > /dev/hd0/1 > > > > and with the probedisk translator, you could have > > > > /dev/hd/0/1 > > > > What do people think about it? > > As someone who is not super technical...so take this with a grain of salt. > > /dev/hd0/1 seems easier to remember. "mount /dev/hd0/1 /mnt/usb" seems > like it will beeasier for me to remember. > > /dev/hd/0/1 seems long ...? > > But I really don't understand the merits of one approach over the other.
The merit is that the /dev/hd/ directory can contain exactly the device numbers that do exist, instead of the current series of /dev/hd* that do not necessarily exist. > If I understand Oliver's followup email... > > the latter approach /dev/hd/0/1 allows the node to expose both > the raw hard drive and the partition itself. /dev/hd0/1 would as well: you use /dev/hd0 to access the raw disk, and /dev/hd0/1 for the partition. Using /dev/hd/0/1 does not change that part, only the enumeration. Samuel
