hello,
touch utility telling weird error on file creation on a immutable/ro dir.
apparently, it does not catch/report the first error (EPERM) but only
the second one (ENOENT), when trying to set the time on the non-existing
file.
regards
roland kletzing
sysadmin
root@s900:/tmp# mkdir /tmp
line break in the option description. The line
breaks should be computed based on the terminal size or a fixed line
width. It's not possible to predict the screen column in which in the
option description will start, since that depends on the names of the
other options. Therefore, the option descriptions should be wrapped as
necessary. See fold(1).
Roland
ot;gnu-" or pretty much any other string. What is the correct way of
solving this problem?
Roland
Am 03.10.2019 um 21:43 schrieb Paul Eggert:
> Thanks for the bug report. I looked for similar problems involving
> integer-overflow diagnostics in coreutils and installed the attached
> patches. The second patch should fix the bug you mentioned.
Ah, the code looks so much simpler and nicer with th
The current code says:
next_line_no = line_no + page_incr;
if (next_line_no < line_no)
die (EXIT_FAILURE, 0, _("line number overflow"));
Since intmax_t is a regular integer type, overflow invokes undefined
behavior and must therefore be checked using other means.
* .github/ISSUE_TEMPLATE.txt, .github/PULL_REQUEST_TEMPLATE.txt:
fix typo "coreitils" in the URL to the bug tracker.
---
.github/ISSUE_TEMPLATE.txt| 2 +-
.github/PULL_REQUEST_TEMPLATE.txt | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/.github/ISSUE_TEMPLATE.txt b
-Translator", among
other information.
This string should therefore be left untranslated.
Greetings,
Roland
Hi.
I have noticed that sort seems to have problems when the LANG environment
variable is set with language and country.
As a test case, i tried to sort
a
b
a
⺌
⺕
⺌
It sorts OK like this, with LANG just the language.encoding:
( setenv LANG en.UTF-8 ; echo 'a\nb\na\n⺌\n⺕\n⺌' | sort )
a
a
b
⺌
⺌
⺕
I think you can portably detect the failure case with the errno=0 method,
rather than relying on #ifdef.
On Friday September 15th 2006 10:32 Jim Meyering wrote:
> Roland Eggner <[EMAIL PROTECTED]> wrote:
> > install -m a-x SOURCE DEST
> > install -m a-X SOURCE DEST
> > both commands reset ALL bits like "chmod 000 DEST", should ONLY reset
> > executable bi
install -m a-x SOURCE DEST
install -m a-X SOURCE DEST
both commands reset ALL bits like "chmod 000 DEST", should ONLY reset
executable bits!
--
Roland Eggner A-8020 Graz, Vinzenzgasse 36 Telefon 0043-316-58 66 48
Wer seinen Computer einrichtet, hat die Qual der Wahl:
Da
s.m4?root=coreutils&r1=1.32&r2=1.33>.
I assume you're talking about coreutils 5.95.
Jim, perhaps this fix should also be propagated into the b5_9x branch?
(I just now propagated it into Autoconf CVS.)
Thanks.
That fix made it onto the branch just in time for 5.96.
Thanks fo
Hi,
when using the ls-mntd-fs.m4 file on NetBSD 3.0/i386, I got an error
caused by an empty variable ($ac_cv_func_getmntent):
test: =: unary operator expected
So I patched all variable uses to include the proper quotes.
Roland
Index: fsusage.m4
effective-user access checking.
int faccessat (int fd, const char *file, int type, int flag);
Does that sound reasonable?
Thanks,
Roland
___
Bug-coreutils mailing list
Bug-coreutils@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-coreutils
It's a natural, obvious, and useful addition, no matter what Solaris does
or doesn't have. I've put it in. If there are any more *at additions that
might be useful, right now is the time to bring them up. So rack your brain.
Thanks,
Roland
Greetings.
I notice that my name appears in the THANKS file, presumably as a result of a bug
report that I filed somewhere, sometime. The header in this file includes "if you'd
prefer a different address be used, please let me know" without making clear who "me"
is; [EMAIL PROTECTED] seemed an
re was something like an option
--interactive-multiple that would turn rm into an interactive
command only when it is operating on more than one file so that
there is a larger probability that one of the files is erroneously
in the list of files I am removing.
Is this useful? Or is all this to
> Alfred M. Szmidt wrote:
> >> + if (trans_stat.st_mode & S_IPTRANS)
> >> +{
> >> + char buf[1024], *trans = buf;
> >Is this 1024-byte buffer guaranteed to be large enough?
Code like this is using a mig stub feature whereby a larger buffer is
alloc
18 matches
Mail list logo
