Re: PATCH: mouse and keyboard by default if not embedded

From: Rob Landley (rob_at_landley.net)
Date: 08/08/03

  • Next message: Arkadiusz Miskiewicz: "watchdog daemon causes kernel oops (2.4.18, 2.4.20, 2.4.21)"
    To: Christoph Hellwig <hch@infradead.org>, Alan Cox <alan@lxorguk.ukuu.org.uk>
    Date:	Fri, 8 Aug 2003 06:27:51 -0400
    
    

    On Monday 28 July 2003 03:14, Christoph Hellwig wrote:
    > Again this is stupid. With the select CONFIG_INPUt if CONFIG_VT people
    > get this asked now on make oldconfig. Even more important many ports
    > newer used PS/2 style mouses previously as did older PeeCees.
    >
    > Please stop this over-eager spreading of CONFIG_EMBEDDED, we're not
    > gnome..

    Actually, I was going to move all this stuff to the embedded menu as soon as I
    caught up on Linux-kernel to make sure nobody else had already done it. (I
    was only 2500 messages behind the day before yesterday, but people keep
    posting more... :)

    Finding out that Alan beat me to this is exactly why I'm catching up on my
    reading before pushing patches. :)

    The 2.5 kernel I just compiled is currently about three times larger than the
    uclibc+busybox root filesystem I built yesterday. I'm all for stripping it
    down, but saying that your average server doesn't need the ability to plug in
    a monitor and keyboard and see what's up if it suddenly goes peculiar...
    Well, I wouldn't want to support that system, and certainly Red Hat ain't
    gonna ship like that any time soon. (As for the servers you mentioned in
    your previous post, we're potentially saving tens of kilobytes by doing so,
    on a system with around gigabyte of ram. So if we're saving 10-30k (not just
    kernel code but run-time allocations), we're talking about saving 0.001 to
    0.003% of ram on a server setup. Oooh. Aaaah. Definitely the kind of
    micro-optimization we want everybody in the world (and their dog) to have to
    figure out if they need or not the first time they compile a kernel.)

    Rob
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/


  • Next message: Arkadiusz Miskiewicz: "watchdog daemon causes kernel oops (2.4.18, 2.4.20, 2.4.21)"

    Relevant Pages

    • Re: Tracking down a memory leak
      ... > assuming it's a memory leak in kernel space. ... > The server has been mainly running PostgreSQL at a fairly high load for ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • ppc32 lockups with 2.6 (maybe network related)
      ... eth0 192.168.1.1" results in a lockup. ... then compiled some debug options into the kernel, ... Mail server hit by UniSpammer. ... To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ ...
      (Linux-Kernel)
    • ppc32 lockups with 2.6
      ... eth0 192.168.1.1" results in a lockup. ... then compiled some debug options into the kernel, ... Mail server hit by UniSpammer. ... To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ ...
      (Linux-Kernel)
    • Re: Sluggish performances with FreeBSD
      ... I've also done some tests with netperf ... If I use a kernel 2.4.26 on my server, I have 48Mb/s from server to ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: [patch] trivial change in kernel/sched.c in 2.6.0-test9+
      ... > Just off the top of my head, you could try something like a kernel ... Well, I ran about 6 different compiles each on a patched and an unpatched, ... it may end up saving a bit more. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)