Messages in this thread |  | | From | Christian Bornträger <> | Subject | 2.4.17pre2: devfs: devfs_mk_dir(printers): could not append to dir: dffe45c0 "", err: -17 | Date | Sat, 1 Dec 2001 10:20:44 +0100 |
| |
After upgrading from 2.4.16 to 2.4.17pre2 I got the following message in dmesg:
. parport0: assign_addrs: aa5500ff(80) parport_pc: Via 686A parallel port: io=0x378 devfs: devfs_mk_dir(printers): could not append to dir: dffe45c0 "", err: -17 lp0: using parport0 (polling). .
or
devfs: devfs_register(nvidiactl): could not append to parent, err: -17 devfs: devfs_register(nvidia0): could not append to parent, err: -17
with 2.4.16 and before the message was:
devfs: devfs_register(): device already registered: "nvidia0"
Why has this changed, and what is actually happen? My system runs fine.
greetings
Christian Bornträger - 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/
|  |