From: Richard Gooch <rgooch@ras.ucalgary.ca>
To: Adam Schrotenboer <ajschrotenboer@lycosmail.com>
Cc: "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: Sat, 1 Dec 2001 18:49:54 -0700 [thread overview]
Message-ID: <200112020149.fB21nso04834@vindaloo.ras.ucalgary.ca> (raw)
In-Reply-To: <20011202013724.9085AFB80D@tabris.net>
In-Reply-To: <E16A6LR-00042s-00@mrvdom02.schlund.de> <200112011808.fB1I8lq31535@vindaloo.ras.ucalgary.ca> <20011202013724.9085AFB80D@tabris.net>
Adam Schrotenboer writes:
> On Saturday 01 December 2001 13:08, Richard Gooch wrote:
> > linux-kernel@borntraeger.net writes:
> <snip>
> > The new devfs core is less forgiving about these kinds of
> > bugs/misuses.
> >
> > > 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"
> >
> > Who knows what nvidia does? Talk to them. Could be a bug in their
> > driver where they create duplicate entries (the old devfs code would
> > often let you get away with this). Or again, perhaps something in
> > user-space is creating these entries.
> >
> As of 1541 anyway (haven't tried anything newer, assuming newer
> exists), the make install of the nvidia driver also runs
> makedevices.sh (a vendor sp script that makes the devnodes. This may
> also have been put in the initscripts (mine isn't, but i tend to use
> the tar.gz fmt, not using the RPMs) Perhaps there is no check for
> devfs (likely will be fixed in the next release, as this is a new
> situation)
Well, it doesn't matter if the install script dumps things into /dev,
since that will be lost on the next boot anyway. What matters is if
the boot scripts (or something else) puts things in devfs.
> > > Why has this changed, and what is actually happen? My system runs
> > > fine.
> >
> > You're lucky that the with way you use your system, it still works.
> >
> <snip> AFAIK, the nvidia scipt does not make the devnodes persistent
> (if so, it's b0rken on my box)
You can easily check this: move the NVidia drivers elsewhere and
reboot. If device nodes for nvidia appear in devfs, then something in
user-space is creating those inodes.
Regards,
Richard....
Permanent: rgooch@atnf.csiro.au
Current: rgooch@ras.ucalgary.ca
prev parent reply other threads:[~2001-12-02 1:50 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
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 [this message]
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=200112020149.fB21nso04834@vindaloo.ras.ucalgary.ca \
--to=rgooch@ras.ucalgary.ca \
--cc=ajschrotenboer@lycosmail.com \
--cc=linux-kernel@borntraeger.net \
--cc=linux-kernel@vger.kernel.org \
/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®