mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Christian Bornträger" <linux-kernel@borntraeger.net>
To: Richard Gooch <rgooch@ras.ucalgary.ca>,
	andrew may <acmay@acmay.homeip.net>
Cc: "Adam Schrotenboer" <ajschrotenboer@lycosmail.com>,
	"Christian Bornträger" <linux-kernel@borntraeger.net>,
	linux-kernel@vger.kernel.org
Subject: Re: 2.4.17pre2: devfs: devfs_mk_dir(printers): could not append to dir: dffe45c0 "", err: -17
Date: Sun, 2 Dec 2001 20:10:30 +0100	[thread overview]
Message-ID: <E16Ac1n-0001Bd-00@mrvdom00.schlund.de> (raw)
In-Reply-To: <E16A6LR-00042s-00@mrvdom02.schlund.de> <20011201180940.B21185@ecam.san.rr.com> <200112021847.fB2IlmZ11175@vindaloo.ras.ucalgary.ca>
In-Reply-To: <200112021847.fB2IlmZ11175@vindaloo.ras.ucalgary.ca>

<-snip->

> This appears reasonable. However, if they call this initialisation
> code twice, it's a bug.


I found the reason for these messages. It has a boot-script source.
Mandrake stores the attributes of device nodes in /lib/dev-state.
This directory is copied into /dev directly before devfsd is started.

If there is a device file in /lib/dev-state it is created in /dev even before 
the driver is loaded.
When the driver is loaded it tries again to create the node and the message 
appears. 
Thanks for your suggestions and remarks.

greetings 

Christian


  reply	other threads:[~2001-12-02 19:12 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-01  9:20 Christian Bornträger
2001-12-01 18:08 ` Richard Gooch
2001-12-02  1:37   ` Adam Schrotenboer
2001-12-02  2:09     ` andrew may
2001-12-02 18:47     ` Richard Gooch
2001-12-02 19:10       ` Christian Bornträger [this message]
2001-12-02 19:41       ` Richard Gooch
2001-12-02 19:57         ` Alan Cox
2001-12-02 20:01         ` Richard Gooch
2001-12-02 20:14           ` Alan Cox
2001-12-02 20:22           ` Richard Gooch
2001-12-02  1:49   ` Richard Gooch

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E16Ac1n-0001Bd-00@mrvdom00.schlund.de \
    --to=linux-kernel@borntraeger.net \
    --cc=acmay@acmay.homeip.net \
    --cc=ajschrotenboer@lycosmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rgooch@ras.ucalgary.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®