On So 04-02-06 01:36:59, Olivier Galibert wrote:
> On Sat, Feb 04, 2006 at 12:55:47AM +0100, Pavel Machek wrote:
> > The weird reasons were stated few times already. My favourite weird
> > reason is "can be done in userspace" these days.
>
> Oh please, stop that. Network can be done in userspace. NFS can be
> done in userspace. Filesystems can be done in userspace. You need a
> better reason than that.
I have few more. That was my favourite :-).
> Now the pressure to add progress bar and other chrome, I can
> understand. Not wanting the chrome in the kernel, I understand even
> more. Deciding the solution for that is to more everything in
Good.
> Why don't you try to design the system so that the progress bar can't
> fuck up the suspend unless they really, really want to? Instead of
> one where a forgotten open(O_CREAT) in a corner of graphics code can
> randomly trash the filesystem through metadata corruption?
Even if I only put chrome code to userspace, open() would still be
deadly. I could do something fancy with disallowing syscalls, but it
is probably easier to just read the chrome code to be used... It
should be as simple as memcpy(framebuffer, prepared image).
Pavel
--
Thanks, Sharp!
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
