On Mon, Feb 25, 2002 at 02:33:44PM +0100, Matijs van Zuijlen wrote: | On Sun, Feb 24, 2002 at 11:47:28PM +1000, mdevin wrote:
| > Yes. I agree. But it would be interesting to check if the config file | > shows that devfs was selected but not enabled at boot to be sure. | | Yes, that is the case. Now we have the following situation, which I | think is undesirable: If you install the pre-compiled kernel image and | noflushd, noflushd will just complain in the logs about the kernel | supporting devfs but not using it, and aborting. Problem is, of course, | how to warn users about this. I don't see a solution right now. I was | just lucky to read the boot logs at the right time, I guess. I don't know anything about flushd, but | Maybe someone can enlighten my on why the 2.4.17 precompiled image | package does not enable devfs at boot time? Not everyone will want devfs, just like not everyone wants APM or framebuffer. The best thing the pre-built packages can do is include the support, but leave it disabled by default. Then the admin can simply place the proper command line argument in their bootloader to control the features they want to use. -D -- Microsoft encrypts your Windows NT password when stored on a Windows CE device. But if you look carefully at their encryption algorithm, they simply XOR the password with "susageP", Pegasus spelled backwards. Pegasus is the code name of Windows CE. This is so pathetic it's staggering. http://www.cegadgets.com/artsusageP.htm
