After upgrading to 2.4.13 I recognised some programs are complaining about /dev/null. And yes, /dev/null flags were changed to crw------- , again and again.
It turned out that happens every morning when my cron.daily scripts run. And more specifically it happens every time when: 1. sensord (version 0.5.0) is restarted (in about one-two seconds after sensord starts again) 2. syslog-ng (1.5.9) initalizes after boot, is restarted, or get a kill -1 (the flags change at the next minute when syslog-ng awakes). I went back to 2.4.9 and was not able to reproduce the same there. Tried out in 2.4.13 also with and without devfs, it does not matter; however in the boot sequence with devfs there is (a perhaps unrelated) error in reparent_to_init sr1: scsi3-mmc drive: 20x/20x writer cd/rw xa/form2 cdda tray Adding Swap: 40952k swap-space (priority -2) Adding Swap: 136512k swap-space (priority -3) eth0: Setting half-duplex based on auto-negotiated partner ability 0000. ****** task `ifconfig' exit_signal 17 in reparent_to_init ****** Real Time Clock Driver v1.10e parport0: PC-style at 0x378 [PCSPP(,...)] I would be glad to supply more debug info - please ask for them specifically. Some general system info: Debian, testing; Linux version 2.4.13 ([EMAIL PROTECTED]) (gcc version 2.95.4 20011006 (Debian prerelease)) #4 Sat Oct 27 17:24:05 CEST 2001 Kernel command line: BOOT_IMAGE=current ro root=307 pci=biosirq devfs=nomount Memory: 127124k/131056k available (832k kernel code, 3544k reserved, 212k data, 212k init, 0k highmem) CPU: AMD-K6(tm) 3D processor stepping 0c PCI: PCI BIOS revision 2.10 entry at 0xf0560, last bus=1 PCI: Using IRQ router ALI [10b9/1533] at 00:07.0 es1371: found chip, vendor id 0x1274 device id 0x1371 revision 0x06 i2c-proc.o version 2.6.1 (20010825) w83781d.o version 2.6.1 (20010830) Sándor
