Re: New utility suggestion: chdir(1)

2017-08-26 Thread Colin Watson
["env"] + ["%s=%s" % (key, value) for key, value in env.items()] + args) subprocess.check_call( ["sudo", "chroot", chroot_path, "chdir", "/build"] + args) -- Colin Watson [cjwat...@debian.org]

New utility suggestion: chdir(1)

2017-08-26 Thread Colin Watson
w) this is an innovation rather than something that other operating systems already implement; I think my suggested name is the most natural choice by analogy with the system call and chroot(8). Thanks, -- Colin Watson [cjwat...@debian.org]

Re: New utility suggestion: chdir(1)

2017-08-27 Thread Colin Watson
gestion is the second one ("env: add --chdir option"), but I'd be happy either way. If either of these requires a copyright assignment and I don't have one on file for coreutils, then I'd appreciate it if a maintainer could get the ball rolling on the necessary paperwork.

Re: New utility suggestion: chdir(1)

2017-08-27 Thread Colin Watson
On Sat, Aug 26, 2017 at 06:23:33PM -0700, Kaz Kylheku (Coreutils) wrote: > On 26.08.2017 11:10, Colin Watson wrote: > > sudo chroot /path/to/chroot sh -c 'cd /foo && ls -l' > > The -c option is not the only way to pass a script to the shell. > > You can also

Re: New utility suggestion: chdir(1)

2017-08-27 Thread Colin Watson
On Sun, Aug 27, 2017 at 06:58:19AM -0700, Kaz Kylheku (Coreutils) wrote: > On 26.08.2017 11:10, Colin Watson wrote: > > I would like there to be an adverbial version of "cd", which takes a > > path followed by a command and optional arguments and executes the > > com

Re: New utility suggestion: chdir(1)

2017-08-29 Thread Colin Watson
the environment with the previous version. > It's of no functional value to print the env while > also changing dir as far as I can see. I approve of these changes in my name (with Jim's adjustments). Thanks. -- Colin Watson [cjwat...@debian.org]

Re: [PATCH] ls: issue error message on removed directory

2020-02-12 Thread Colin Watson
On Wed, Feb 12, 2020 at 10:54:43AM +, Pádraig Brady wrote: > Sorry I sent the following to the list only. > Please cc coreutils@gnu.org on any responses... > > On 11/02/2020 10:45, Colin Watson wrote: > > If the current directory has been removed, then "ls" confus

[PATCH] ls: issue error message on removed directory

2020-02-11 Thread Colin Watson
If the current directory has been removed, then "ls" confusingly produced no output and no error message, indistinguishable from the case of running on an empty directory. It makes more sense to report ENOENT in this case. Reported by Owen Thomas. * src/ls.c (print_dir): Report ENOENT if

Re: [PATCH] ls: issue error message on removed directory

2020-02-11 Thread Colin Watson
On Tue, Feb 11, 2020 at 10:45:46AM +, Colin Watson wrote: > If the current directory has been removed, then "ls" confusingly > produced no output and no error message, indistinguishable from the case > of running on an empty directory. It makes more sense to report EN

bug#8700: Simple way to switch user/group permissions without requiring PAM sessions

2011-05-19 Thread Colin Watson
is not all that great IMO, so it's probably only useful to know about it to avoid using the same (tempting) name. Thanks, -- Colin Watson [cjwat...@debian.org]

bug#13030: factor: infinite loop on Linux/powerpc

2012-11-29 Thread Colin Watson
W_TYPE_SIZE == 64 defined (_LP64) #if !defined (_LONG_LONG_LIMB) /* _LONG_LONG_LIMB is ABI=mode32 where adde operates on 32-bit values. So use adde etc only when not _LONG_LONG_LIMB. */ Thanks, -- Colin Watson [cjwat...@ubuntu.com]

bug#13030: factor: infinite loop on Linux/powerpc

2012-12-05 Thread Colin Watson
On Wed, Dec 05, 2012 at 09:58:11AM +0100, Bernhard Voelker wrote: On 11/29/2012 08:34 PM, Pádraig Brady wrote: The fix looks good thanks. I'll commit [...] Now, make syntax-check fails: Colin Watson maint.mk: remove the above names from THANKS.in make