pkgsrc-Bugs archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: pkg/42256: check-files with /usr/pkgsrc mounted read-only




To: pkg-manager%netbsd.org@localhost,gnats-admin%netbsd.org@localhost,pkgsrc-bugs%netbsd.org@localhost,Steven Drake <sdrake%xnet.co.nz@localhost>

Subject: Re: pkg/42256: check-files with /usr/pkgsrc mounted read-only

From: Joerg Sonnenberger <joerg%britannica.bec.de@localhost>

Date: Tue, 3 Nov 2009 16:25:02 +0000 (UTC)


The following reply was made to PR pkg/42256; it has been noted by GNATS.

From: Joerg Sonnenberger <joerg%britannica.bec.de@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: 
Subject: Re: pkg/42256: check-files with /usr/pkgsrc mounted read-only
Date: Tue, 3 Nov 2009 17:23:40 +0100

 On Tue, Nov 03, 2009 at 07:45:02AM +0000, Steven Drake wrote:
 >  The coreutils rm does an unlinkat and checks the errno value on failure
 >  ignoring it if its ENOENT.  With linux/glibc (at least) unlinkat/unlink
 >  sets errno to EROFS for a non-existent file on a read-only filesystem.
 >  
 >  That begs the question, what should unlink set errno to?  I like to know
 >  what other OSes/libcs do?
 
 ENOENT. They are basically breaking a lot of programs for no good
 reason.
 
 Joerg
 




Prev by Date: PR/42259 CVS commit: pkgsrc/graphics/clutter

Next by Date: pkg/42260: update old version of databases/py-sqlalchemy

Previous by Thread: Re: pkg/42256: check-files with /usr/pkgsrc mounted read-only

Next by Thread: Re: pkg/42256: check-files with /usr/pkgsrc mounted read-only

Indexes:

reverse Date

reverse Thread

Old Index



Home | Main Index | Thread Index | Old Index