Mmmmm, Linuxy goodness!

So I got my system to work in Fedora Core 2 with the 2.6 kernel finally. I just went through the X configuration file and removed all references to /dev/psaux, and damned if it didn’t work.

Now, why it worked with the 2.4 kernel but not the 2.6 kernel is beyond me. I don’t even know what /dev/psaux does. But hey, it’s up and running, and I’m typing this entry using Mozilla for Linux even now!

I’m also setting up telnet and ssh and apache and all kinds of other goodness, so Shelly can get into this machine and experiment on it. Her new job requires her to be able to troubleshoot Apache servers via telnet, so this’ll make a good test bed machine for her to play with, and no real harm done if something blows up.

Anyway, since I have Apache running on here, anyone got any ideas about what kind of Web content we should put on it? It’ll be semi-private, as you can only reach it if you know the IP address (which changes periodically as it’s on cable modem with DHCP), so my mind immediately runs to naughty places, which will come as a surprise to…well, nobody.

8 thoughts on “Mmmmm, Linuxy goodness!

  1. If I’m remembering correctly, /dev/psaux is the PS/2 mouse port.

    Isn’t Linux fun? Don’t you wish all operating systems were that easy to configure and get running?

    (I’m remembering why I liked FreeBSD more as a “free Unix.” It’s not that it’s easier to configure, but rather that, unlike most Linux distributions, it doesn’t suffer under the illusion that it’s user-friendly, but rather tries to consolidate and document its configuration files. As opposed to spending 10 minutes in the GUI and 10 hours debugging what the GUI screwed up, you just spend an hour or two in the text editor to start with.)

    • Heh. You’re right, mostly; /dev/psaux was the mouse port.

      The Linux 2.6 kernel doesn’t use /dev/psaux as the mouse port; it uses /dev/input/mice, which lives in kernel space, not user space. And, furthermore, it blocks access to /dev/psaux. I don’t know what they were thinking…

      Kernel Hacker #1: “I know! I know! I know! We can roll the mouse driver into the kernel, and then see if we can break every living piece of software known to man! That’d be k00l!”
      Kernel Hacker #2: “Hey, pass me that crack pipe, man…”

      So upshot is, kernel 2.4, use /dev/psaux. Kernel 2.6, use /dev/input/mice, and if you try to do anything with /dev/psaux, the system, she fall down go boom.

  2. If I’m remembering correctly, /dev/psaux is the PS/2 mouse port.

    Isn’t Linux fun? Don’t you wish all operating systems were that easy to configure and get running?

    (I’m remembering why I liked FreeBSD more as a “free Unix.” It’s not that it’s easier to configure, but rather that, unlike most Linux distributions, it doesn’t suffer under the illusion that it’s user-friendly, but rather tries to consolidate and document its configuration files. As opposed to spending 10 minutes in the GUI and 10 hours debugging what the GUI screwed up, you just spend an hour or two in the text editor to start with.)

  3. Heh. You’re right, mostly; /dev/psaux was the mouse port.

    The Linux 2.6 kernel doesn’t use /dev/psaux as the mouse port; it uses /dev/input/mice, which lives in kernel space, not user space. And, furthermore, it blocks access to /dev/psaux. I don’t know what they were thinking…

    Kernel Hacker #1: “I know! I know! I know! We can roll the mouse driver into the kernel, and then see if we can break every living piece of software known to man! That’d be k00l!”
    Kernel Hacker #2: “Hey, pass me that crack pipe, man…”

    So upshot is, kernel 2.4, use /dev/psaux. Kernel 2.6, use /dev/input/mice, and if you try to do anything with /dev/psaux, the system, she fall down go boom.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.