quitting here. The rest of the story needs to be read by someone who
actually knows MacOS.
--
Alan Curry
Rafal W. writes:
But if Control-4 is sending QUIT signal, why:
Control-1 does kill the process?
I've checked again and actually it's not even about the number.
When I press only: Control-SysRq it kills the process as well.
Sometimes it happens on press, sometimes on release.
Is your SysRq
is another one.
--
Alan Curry
.
--
Alan Curry
Sven Joachim writes:
On 2012-09-24 08:37 +0200, Alan Curry wrote:
Georgiy Treyvus writes:
Finally I had him show me the mount options of the relevant partitions.
Many I recognized. Some I did not. I started researching those I did
Did you notice this one?:
Mount options
Rafal W. writes:
$ cat /dev/zero
^\Quit (core dumped)
Steps to reproduce:
1. Switch to any text console (it doesn't happen in X).
2. Login
3. Run: cat /dev/zero
4. Press: Ctrl-Alt-SysRq-1 (or any number except letters:)
What's that supposed to do? Ctrl isn't normally used with
strace -o cptrace cp ... and publish the cptrace
for others to look at. (If the files being copied are private, the names and
contents will be in the trace so you will have to inspect it yourself.)
--
Alan Curry
very much like
V7, but I can't find anything to compare it to until OpenSolaris.
Did POSIX force BSD to change their rm in 1988? I think it's more likely that
POSIX simply documents a restriction that BSD had already added. Either way
the latest POSIX revisions certainly can't be blamed.
--
Alan
think the
change you're referring to is a change at all. -f never had the effect you
think it should have.
--
Alan Curry
Linda Walsh writes:
Alan Curry wrote:
Linda Walsh writes:
So far no one has addressed when the change in -f' went in
NOT to ignore the non-deletable dir . and continue recursive delete,
In the historic sources I pointed out earlier (4.3BSD and 4.3BSD-Reno) the
-f
option
on . and .. though. They're magic.)
--
Alan Curry
Jim Meyering writes:
Alan Curry wrote:
rm -rf $PWD, meaning basically the same thing as rm -rf ., works, and leaves
If you use that, in general you would want to add quotes,
in case there are spaces or other shell meta-characters:
rm -rf $PWD
Well, when I do it I'm in zsh which
d4db0cb1827730ed5536c12c0ebd024283b3a4db can be cherry-picked and applied to
older coreutils to fix the bug. I tested this with upstream 8.9 and Debian's
8.5, both applied with fuzz but worked correctly.
--
Alan Curry
around, but not a lot worse if the files are big enough
that the time spent reading their contents overshadows the time spent on
directory lookups.
--
Alan Curry
=Brazil/East date +%d --date=1986-10-25 12:00:00
25
--
Alan Curry
, and your shell is doing it stupidly. With
zsh, you'd get the correct result:
% echo abcde | tee (tr a 1) | tr b 2
a2cde
1bcde
ksh and bash recently copied the process substitution feature from zsh, and
they haven't got it right yet.
--
Alan Curry
at the end. unmount and fsck it to fix if I'm right.
--
Alan Curry
at handling obscured mount points as
ours?
--
Alan Curry
EISDIR, and intentionally skips printing it. Grr.
But wait, there's a -d option with 3 alternatives for what to do with
directories! ...and none of choices is just print the EISDIR so I'll know
if I accidentally grepped a directory.
--
Alan Curry
?
--
Alan Curry
Paul Eggert writes:
On 12/16/11 18:36, Alan Curry wrote:
The straightforward method would be to simply the directory you intend to
remove and keep track of the discrepancy between st_nlink and how many links
you've seen.
Sorry, I can't parse that. But whatever it is, it sounds like
. As a
creative improvised use of pre-existing tools it's a good example, but as a
justification for an intentional feature, it's just too inefficient.
--
Alan Curry
there is less
redundancy in the output. Each number actually tells me something you can't
derive from the others. There is higher information content. This is good,
not bad.
--
Alan Curry
RIGHT SINGLE QUOTATION MARK in UTF8, then misinterpret it as
windows-1252 and convert it to UTF8 again.
We were *so* unfortunate when we didn't have all these extra kinds of
quotation marks.
--
Alan Curry
as special. Trying it out, it seems to be treated
as equivalent to setuid(1). Not what I expected, but it doesn't really
support your -1 is a valid uid theory.
--
Alan Curry
derived from st_blocks are reported in units of blocks, and others
aren't.
If you're going to define --block-size to have this effect, then you really
need to document it as being an option that does 2 separate things:
1. sets the size of a block
2. alters the definition of the -l format
--
Alan
like BSD.
--
Alan Curry
you're replying to, and put your reply in logical order with it.
--
Alan Curry
?- ? ? ? ?? novas_fli.so
ls can read the directory, getting the filenames, but the lack of x
permission prevents it from getting any other information.
First chmod u+x doc modules project, then see what you get from ls -l on
them.
--
Alan Curry
use to kill it (committed to my own git tree which is
exported to no one and has been seen by nobody but me until now):
commit 0b76f0a49a52ac37fb220f1481955426b6814f86
Author: Alan Curry pac...@kosh.dhis.org
Date: Wed Sep 22 16:35:01 2010 -0500
The echoing of ^C when a process is interrupted
distinction is a good idea at all. Which I don't.
--
Alan Curry
' shouldn't
be exposing those internals to users; it should behave like
'sleep' does, as that's more consistent.
What's the difference between running a command with a 0 second timeout
and not running the command at all? It could be killed before it even gets
scheduled.
--
Alan Curry
be sent to a
background process that attempts to change the tty settings, even if tostop
is not enabled.
--
Alan Curry
something wrong there too?
--
Alan Curry
(as far
as the tty knows) so it will be getting SIGTTIN and possibly SIGTTOU on tty
operations.
I don't think there's anything that will make every scenario happy. (Except
for a recursive-kill that doesn't use pgrps!).
--
Alan Curry
to be killed by
timeout, there's reason to believe it's not behaving well at the moment.
--
Alan Curry
to the exit code.
--
Alan Curry
=?UTF-8?Q?P=C3=A1draig?= Brady writes:
This is a multi-part message in MIME format.
--03030307000505070101
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
On 27/06/11 21:12, Alan Curry wrote:
What seems to be happening is that make
of arbitrary file
names. If FILE is omitted or specified as `-', standard input is read.
(the sha*sum utilities all refer back to md5sum's description)
I better go fix all my scripts that rely on /^[0-9a-f]{32} /
--
Alan Curry
(for last) but not utmp
(for who). Check the config files for recent changes, and if you can't find
the cause, find someplace that gives help with pppd.
An strace of the pppd process during connection setup could be enlightening.
--
Alan Curry
.
--
Alan Curry
level of popularity. (Curious header
watchers will have noticed I'm an elm user. And yep, I used mmencode to
decode the mmencode in the original question.)
The coreutils equivalent is base64(1).
After a rewrite with mutt, the whole script might be a one-liner.
--
Alan Curry
them as literal
strings and not globs.
Switch to zsh for better diagnostics...
% echo ABCD Directory | tr [:lower:] [:upper:]
zsh: no matches found: [:lower:]
% echo ABCD Directory | tr '[:lower:]' '[:upper:]'
ABCD DIRECTORY
--
Alan Curry
Eric Blake writes:
On 04/28/2011 12:34 PM, Jason Vas Dias wrote:
I do:
=20
$ ls --version | grep '[(]G'
ls (GNU coreutils) 8.12
Thanks for the report.
$ ls -dl /. | od -cx
od -cx is not always the best choice in formatting - it depends on the
endianness of your machine since
demonstration, I could make another attempt and
log it all. But if you're trying to tell us that checking out old versions
from the repository and compiling them shouldn't be expected to work... then
you're wrong.
--
Alan Curry
/cygwin/bin/sort to make it
use the right one.
cygwin's bug, if a bug at all...
--
Alan Curry
description of your intent.
--
Alan Curry
George Goffe writes:
Alan,
Oops. I goofed... My apologies.
The example would be this somescript | tee somescript.log 21.
The intent is to capture all the output (stdout and stderr) from
somescript. somescript runs several commands that may or may not utilize
other FDs. I was hoping to
. But it doesn't.
The reader's only hope is to infer this GNU anti-readability convention by
reading the man page for a command they already know how to use, and then
apply that convention when reading about other commands.
The Linux man-pages project should take on section 1.
--
Alan Curry
the opposite. Looks like an intentional feature removal to me. Patches
welcome? How about a revert?
[1] commit 99f09784cc98732a440de86bb99a46f11f7355d8
--
Alan Curry
done
The idea of using head to control a loop means you are either a newbie who
didn't know about read, or you are trying to do something subtly different
which I didn't understand. Excuse me if I guessed the wrong one.
--
Alan Curry
too.
If tac -s $'\0' did something different from tac -s '', it could only have
been a shell builtin. (Assuming the shell supported the $'...' notation at
all)
--
Alan Curry
directory.
I still think strerror(3p) ought to imply a strerror(1) command,
but I leave it to you to decide. It's just my preference.
Just as write(2) implies write(1), and time(2) implies time(1). Or something
like that.
--
Alan Curry
, all files named *.pdf or *.ps, whose last
modification was more than 30 days ago, with a size less than 500k)
--
Alan Curry
/': Is a directory
$
--
Alan Curry
.
--
Alan Curry
) doesn't. ls has a lot more
options.
And the conflict between -R and -d should be explicitly mentioned. One
of them makes the other meaningless, and we should say which one.
--
Alan Curry
implementations which you don't need to
know about unless you're writing code at or below the libc layer.
--
Alan Curry
Jim Meyering writes:
Gilles Espinasse wrote:
Just tested 8.6 on linux glibc-2.11.1/gcc-4.4.5 LFS build on x86, sparc and
ppc
First a good news is that on sparc (32-bits), 8.6 test suite is now passing
I didn't report yet a failure on misc/stty which was
Failure was
+ stty -icanon
Ole Tange writes:
I recently needed to randomize some lines. So I tried using 'sort -R'.
I was astonished how slow that was. So I tested how slow a competing
strategies are. GNU sort is two magnitudes slower than unsort and more
than one magnitude slower than perl:
Never heard of unsort.
up a bunch of numbers?!
You're using dynamite to kill a mosquito. There must be a dozen basic
utilities that can do arithmetic. Like awk:
... | uniq -c | awk '{t+=$1}END{print t,total}1'
--
Alan Curry
Paul Eggert writes:
On 08/22/10 18:09, Alan Curry wrote:
There might be less occurrences of this misunderstanding if we could teach
date that -d 4/14/1991 is not actually a request for 4/14/1991 00:00:00, but
any time that existed during the day 4/14/1991, or perhaps a more specific
Bob Proulx writes:
date -d '1991-04-14 12:00 +1 day'
I'm from china by the way, and the time zone I am in and to which
the systems were set is GMT8(or CST, China Standard Time).
Indeed,
TZ=Asia/Shanghai date -d '4/14/1991'
date: invalid date `4/14/1991'
TZ=Asia/Shanghai date -d
. If this isn't what you
meant, you did something wrong. mv just did what it was told.
4. Like #1, but with a nomatch shell option enabled, you get a No match
error message.
Your career as a unix wizard isn't complete until you've done something like
#3 *on purpose*.
--
Alan Curry
too hard.
--
Alan Curry
In the dark ages before the bug tracker (i.e. November), a message was sent:
http://lists.gnu.org/archive/html/bug-coreutils/2009-11/msg00206.html
providing an RFC4648 base32 output option for the cryptographic hash
utilities. I'm sending this now to
1. endorse the idea
2. get it a bug number
users 0 Apr 24 17:55 b
Silly aliases.
--
Alan Curry
Andreas Schwab writes:
Alan Curry pacman...@kosh.dhis.org writes:
Who's the power here anyway?
You are, actually. Everyone can define locales to behave the way he
likes, see localedef(1).
I avoid this by not having any locales installed. But that doesn't help all
the other victims
them?
--
Alan Curry
);
}
if (*s)
OK now let's not say I haven't done any legwork.
--
Alan Curry
.
--
Alan Curry
no necessarily a bad idea. I just
mention this because lots of people overlook the +X option.
--
Alan Curry
| ISIG | ECHO | ECHOE | ECHOK| ECHOKE | IEXTEN;
/* no longer| ECHOCTL | ECHOPRT*/
tp-c_oflag |= OPOST;
/* tp-c_cflag = 0; */
--
Alan Curry
-coreutils/2010-02/msg00020.html
It didn't get through to Tom directly, though. His part of the Internet
doesn't accept mail from my part. Someone in the middle (Bob?) could maybe
tell him that he's missing out, by not being subscribed to the list and not
checking the archive.
--
Alan Curry
Tom writes:
I'm using Ubuntu 9.10 (32-bit).
I'm trying to use an ASR-33 Teletype (uppercase only)
Are you trying to write the best message this mailing list has ever aseen?
Because so far, it is.
on ttyS0. I have -U specified in getty for uppercase conversions and
stty -F/dev/ttyS0
on the format of the
error message.
--
Alan Curry
as errors.
--
Alan Curry
Karl Berry writes:
It's definitely a compiler problem. That extern inline asm alias trickery
The gcc people say that the behavior is correct; not a bug.
(I don't understand all of their replies, but the conclusion seems clear.)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42440
OK, I
the stack growth.
In the future, .s files are usually better without -g (as long as you're not
looking for a bug in the part of the compiler that generates the debugging
info). The assembler directives that produce the debugging symbols add a lot
of clutter.
--
Alan Curry
Jim Meyering writes:
The code in question is calling btowc(EOF), which uses
this definition from wchar.h:
extern wint_t __btowc_alias (int __c) __asm (btowc);
extern __inline wint_t
__NTH (btowc (int __c))
{ return (__builtin_constant_p (__c) __c = '\0' __c = '\x7f'
?
-a? I'd like to be sure it's not just
an arch-dependent kernel bug before reporting it as a man page bug. Something
still needs to get fixed, even if coreutils no longer cares about it.
--
Alan Curry
?)
teach timeout to do a whole process tree instead of just a pgrp
Over the course of various experiments, I found another flaw in this test:
tail_forever_inotify can be inlined, and then gdb can't break on it.
--
Alan Curry
as far as trying to
add the 1 days.
In Argentina, the jump forward happens at 00:00:00 (according to my reading
of the tzdata file), so if you use 12:00:00 you should be safe for any day.
$ TZ=America/Buenos_Aires date --date 1920-05-01 12:00:00 1 days +%F
1920-05-02
--
Alan Curry
in the tarball put there to teach a lesson to those
who trust a tarball to have sane permissions? Or is it a bug?
--
Alan Curry
Jim Meyering writes:
P=C3=A1draig Brady wrote:
Alan Curry wrote:
SIGTERM to gdb, but gdb has SIGTERM blocked so nothing happens.
thanks for investigating.
Perhaps we need to use `timeout -sKILL ...`
Sounds good to me.
I added that and re-ran make check. It worked but gdb's child
it won't be necessary,
Alan Curry
86 matches
Mail list logo
