Olivier Valentin, le jeu. 16 avril 2026 07:56:14 +0200, a ecrit: > Le 16 avril 2026 00:16:33 GMT+02:00, Samuel Thibault > <[email protected]> a écrit : > >I'm then wondering how this would fit in the "grand scheme". Our current > >approach, /dev/hd0s* being always there, is indeed not really good > >because it doesn't easily tell the user which partitions are actually > >there. We used to have to have this because partitions used to be > >handled by the kernel, and then we have moved to > >storerio+parted-supported partitions, which brings much more > >flexibility. > > > >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 > > This is mostly curiosity and not suggestion : is it possible for an FS node > to implement both 'device' and 'directory' interfaces ? Like facets ?
Yes, that's a cool thing with the Hurd. > If yes, then we could have the root dir of partfs serve the raw device/file > content. > > Actually, rereading the previous mail, that may be the last proposal. Yes, that's it. Samuel
