Daniel P. Berrange wrote: > > I expect the first problem you'll run into is that copy/paste daemon has > > to run as an unprivileged user but /dev/vmch3 is going to be owned by > > root. You could set udev rules for /dev/vmch3 but that's pretty > > terrible IMHO. > > I don't think that's not too bad, for example, with fast-user-switching > between multiple X servers and/or text consoles, there's already support > code that deals with chown'ing things like /dev/snd/* devices to match > the active console session. Doing the same with the /dev/vmch3 device so > that it is only ever accessible to the current logged in user actually > fits in to that scheme quite well. With multiple X servers, there can be more than one currently logged in user. Same with multiple text consoles - that's more familiar. Which one owns /dev/vmch3? -- Jamie -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
