mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Richard Gooch <rgooch@ras.ucalgary.ca>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@borntraeger.net (Christian Bornträger),
	acmay@acmay.homeip.net (andrew may),
	ajschrotenboer@lycosmail.com (Adam Schrotenboer),
	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 13:01:06 -0700	[thread overview]
Message-ID: <200112022001.fB2K16Q12503@vindaloo.ras.ucalgary.ca> (raw)
In-Reply-To: <E16Acjq-0004M3-00@the-village.bc.nu>
In-Reply-To: <200112021941.fB2Jfmg12171@vindaloo.ras.ucalgary.ca> <E16Acjq-0004M3-00@the-village.bc.nu>

Alan Cox writes:
> > I consider this issue closed. I'd suggest you contact Mandrake and get
> > them to upgrade to devfsd-v1.3.20, remove the boot script code and use
> > the RESTORE directive instead. This requires v1.2 of the devfs core
> > (found in 2.4.17-pre1).
> 
> So the devfs in 2.4.17pre isnt back compatible - definitely 2.5
> material then. This is the same sort of reason the 32bit uid quota
> code can't go into 2.4 proper. Its a pain but its not reasonable to
> expect every random devfs user to handle this in a stable tree
> update

I wouldn't say it's not back compatible. If you want to use a new
devfsd feature, then you need the new devfs. The key difference
between the old and new devfs core (aside from fixing those races) is
that the new devfs core will spit out an EEXIST warning message
whereas before it didn't. But his system still worked. It didn't
break.

				Regards,

					Richard....
Permanent: rgooch@atnf.csiro.au
Current:   rgooch@ras.ucalgary.ca

  parent reply	other threads:[~2001-12-02 20:01 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 [this message]
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=200112022001.fB2K16Q12503@vindaloo.ras.ucalgary.ca \
    --to=rgooch@ras.ucalgary.ca \
    --cc=acmay@acmay.homeip.net \
    --cc=ajschrotenboer@lycosmail.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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®