Messages in this thread | | | From | Kay Sievers <> | Date | Mon, 11 May 2009 23:27:01 +0200 | Subject | Re: [patch 00/13] devtmpfs patches |
| |
On Mon, May 11, 2009 at 23:19, Alan Cox <alan@lxorguk.ukuu.org.uk> wrote: >> By doing its own fstype, we could also make the auto-mount optional, >> because you could always reach the filesystem anytime later. > > Killing the automount would also fix a lot of the other problems as you > can then mount it in the initrd and dump it when you have the real fs up, > or you can mount it privately thanks to Al Viro's magic with mount points > and only the daemon that must make the "real" device file system need > have it mounted and accessible.
Sounds good.
>> A different fstype has the slight inconvenience, that existing >> userspace needs to be taught to handle it explicitly, while a tmfps is >> already handled automatically because we use tmpfs already today. But >> that may not be too important. > > Thats a good thing - it stops some of the suprise behaviour the Eric > pointed out and objected to.
I'll give it try. Any name suggestions to throw at that thing? :)
>> Thanks a lot for your tests and analysis, > > And I think btw the underlying failure was in the tty layer - I just need > to find it. It's the second report vaguely of this form so something is > lurking in the stygian depths.
Ah, good. So that was a useful outcome of it at least. :)
Thanks, Kay
| |