Re: Bug#472590: ls in Debian/Unstable

2008-03-31 Thread Russell Coker
On Monday 31 March 2008 20:02, Jim Meyering <[EMAIL PROTECTED]> wrote: > I like Michael's suggestion.  Rephrasing it, > >     if (SELinux, with no other MAC or ACL) >       use '.' >     else if (any other combination of alternate access methods) >       use '+' > > If someone who already has a cop

Re: Bug#472590: ls in Debian/Unstable

2008-03-31 Thread Jim Meyering
[ I'm Cc'ing [EMAIL PROTECTED] FYI, this is a continuation of discussion from the SELinux list: http://marc.info/?t=12064507403&r=1&w=2 and the debian bug tracking system: http://bugs.debian.org/472590 The problem is that on an SELinux-enabled system, 'ls -l's "+", the "alternate acc

Re: Bug#472590: ls in Debian/Unstable

2008-03-31 Thread Jim Meyering
Russell Coker <[EMAIL PROTECTED]> wrote: > On Monday 31 March 2008 20:02, Jim Meyering <[EMAIL PROTECTED]> wrote: >> I like Michael's suggestion.  Rephrasing it, >> >>     if (SELinux, with no other MAC or ACL) >>       use '.' >>     else if (any other combination of alternate access methods) >>  

Error : Cannot create directory 'usr/local/nagios': permission denied

2008-03-31 Thread Pallav . S . Gupta
I am trying to Install nagios 3.0 in Ubuntu 7.10 Desktop edition. After compliation , when i type " make install " I get error messege saying that cannot create directory 'usr/local/nagios': permission denied. Pls help to rectify !!! The information contained in this e-mail message is in

Re: Error : Cannot create directory 'usr/local/nagios': permission denied

2008-03-31 Thread Philip Rowlands
On Mon, 31 Mar 2008, [EMAIL PROTECTED] wrote: I am trying to Install nagios 3.0 in Ubuntu 7.10 Desktop edition. After compliation , when i type " make install " I get error messege saying that cannot create directory 'usr/local/nagios': permission denied. Presumably your user account does

Re: Error : Cannot create directory 'usr/local/nagios': permission denied

2008-03-31 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Philip Rowlands on 3/31/2008 6:42 AM: | If you have access to run commands as root on your system, then "make | install" should succeed. Otherwise you'll need to ask your system | administrator. Or choose a different --prefix when config

FYI: "rm -r DIR" would mistakenly prompt about very long names

2008-03-31 Thread Jim Meyering
FYI, I've just discovered and fixed a bug that the average user is not likely to encounter: When a non-root user runs "rm -r ..." to remove a (deep) hierarchy, rm would mistakenly prompt about each full relative name that is longer than ~8K (or PATH_MAX if that's smaller). The work-around is easy:

Re: Patch against src/remove.c for correct handling of negative error codes

2008-03-31 Thread Jim Meyering
"Axel Dörfler" <[EMAIL PROTECTED]> wrote: > the enclosed patch changes the following (remove.c against HEAD): ... Thank you for the patch. Sorry not to have replied sooner. At first I hesitated to make a relatively invasive change to remove.c solely to accommodate a fringe target like BeOS/Haiku.

Re: Modifiable NMERGE in sort

2008-03-31 Thread Bo Borgerson
On Mon, Mar 31, 2008 at 2:29 AM, Paul Eggert <[EMAIL PROTECTED]> wrote: > Alas, that patch assumes C99, and we can't assume that quite yet. > Also, it mishandles nmerge values that are "too large" (you'll get > core dumps or worse on many hosts). That being said, it might be > worth adding

Re: Modifiable NMERGE in sort

2008-03-31 Thread Jim Meyering
"Bo Borgerson" <[EMAIL PROTECTED]> wrote: > On Mon, Mar 31, 2008 at 2:29 AM, Paul Eggert <[EMAIL PROTECTED]> wrote: > > Alas, that patch assumes C99, and we can't assume that quite yet. > > Also, it mishandles nmerge values that are "too large" (you'll get > > core dumps or worse on many host

Re: Modifiable NMERGE in sort

2008-03-31 Thread Jim Meyering
"Bo Borgerson" <[EMAIL PROTECTED]> wrote: > On Mon, Mar 31, 2008 at 2:29 AM, Paul Eggert <[EMAIL PROTECTED]> wrote: > > Alas, that patch assumes C99, and we can't assume that quite yet. > > Also, it mishandles nmerge values that are "too large" (you'll get > > core dumps or worse on many host

Re: Modifiable NMERGE in sort

2008-03-31 Thread Jim Meyering
"Bo Borgerson" <[EMAIL PROTECTED]> wrote: > On Mon, Mar 31, 2008 at 2:29 AM, Paul Eggert <[EMAIL PROTECTED]> wrote: > > Alas, that patch assumes C99, and we can't assume that quite yet. > > Also, it mishandles nmerge values that are "too large" (you'll get > > core dumps or worse on many host

Re: Modifiable NMERGE in sort

2008-03-31 Thread Bo Borgerson
On Mon, Mar 31, 2008 at 11:05 AM, Pádraig Brady <[EMAIL PROTECTED]> wrote: > Jim Meyering wrote: > > > > One more suggestion ;-) > > > > Add tests > > you beat me to it :) > > Also I would mention that to ammend a patch do: > > edit your files > git commit --amend -e -a > git format

Re: Modifiable NMERGE in sort

2008-03-31 Thread Jim Meyering
Pádraig Brady <[EMAIL PROTECTED]> wrote: > Also I would mention that to ammend a patch do: > > edit your files > git commit --amend -e -a > git format-patch --stdout --signoff HEAD~1 > your-branch.diff Thanks. I added a few words for that and pushed the new file with the ungainly long name:

cp -u vs. vfat's TWO seconds

2008-03-31 Thread jidanni
Bad news fellows, regarding: `-u' `--update' Do not copy a non-directory that has an existing destination with the same or newer modification time. If time stamps are being preserved, the comparison is to the source time stamp truncated to the resolutions of the destin

Re: Modifiable NMERGE in sort

2008-03-31 Thread Bo Borgerson
Okay, I've added some tests and documentation as per your contribution guidelines. I realize it may be a little premature for a "signoff", but I want to verify that I'm using the tools correctly. Thanks, Bo From 70b1e98b5bbf119e9b14b63780c4d02769cdb8ea Mon Sep 17 00:00:00 2001 From: Bo Borgerson

Re: Modifiable NMERGE in sort

2008-03-31 Thread Jim Meyering
"Bo Borgerson" <[EMAIL PROTECTED]> wrote: > Okay, I've added some tests and documentation as per your contribution > guidelines. Thanks! One real bug: this should be "sizeof *ord": > + size_t *ord = xnmalloc(nmerge, sizeof ord); Some nits: - s/int nmerge/unsigned int nmerge/ - in comments, re