Sometimes when you make some mistake in an app, like forgetting to enter a subject for email, you get these popups warning of the problem. Then you have to click OK to dismiss the popup and correct the error.

What I would like to see is for the app to also be checking the error condition that caused the problem, and if it gets corrected, take the popup down automatically. Of course this also means the app developer would have to learn about multithreading and how to put the popup...

We need a standardized integrated connector that supports ALL of the following in one connector:

1. Dual DVI data links for video up to 2560x1600
2. Single VGA compatible analog signal likes (as in DVI-A)
3. PS/2 keyboard connection
4. PS/2 mouse connection
5. USB

Then maybe the KVM switch market can get their act together.

BIOS is still not smart enough, and has failed to reach the "holy grail" of doing just what system administrators want it to do. This means you AMI. And the others, too.

What I (and just about every system administrator I've talk to about this) want is to be able to specify a device boot order that does NOT get modified by the BIOS just because the media or device is absent in a future boot cycle. I want to have the USB memory stick be the FIRST boot device, conditional...

Isn't one of the kernel design intentions to move more things to user space and keep the kernel itself smaller? I think network filtering should be one of those things.

So why haven't they done that? Is it considered too much of a performance issue to use user processes filter packets? I don't think it would be. But maybe there is some functionality missing that can be done in the kernel and not in user space?

The API would not be hard. Just create device nodes...

Previously I wrote about configuring interfaces with static IPs based on matching them with what actual network (subnet) the interface is connected to. Now I'm thinking about it in even more different terms. But this concept will need some changes in the kernel itself.

To start with, the kernel already (by default) will "leak" an IP address to other interfaces. Specifically, if an ARP query comes in on one interface for an IP address only configured on another interface,...