gmane.os.miros.mksh

Salam Sahajetra

Widiyana Samudra — 2013-05-08T20:12:16

Assalamualaikum Wr.Wb...

Sebelum dan sesudahnya saya ingin memperkenalkan diri saya,nama saya WIDIYANA SAMUDRA berasal dari Indonesia dan bekerja di London (United Kingdom), ingin berkenalan dengan anda di sana.
Saya ingin menawarkan satu peluang bisnis yang begitu bagus,dan bagi Anda yang berminat dengan bisnis ... Inilah kesempatan Anda,kapan lagi kalau bukan sekarang bukan.???
Produk ini di namakan (MULITE CLEANSER) kegunaannya untuk mencuci barangan yang sangat berharga sekali seperti batu intan permata yg masih mentah.
Dan pada waktu yang sama perusahaan di tempat saya bekerja membutuhkan MULITE CLEANSER dimana mineral tersbut tersedia dari operator yg di Indonesia.
Jadi bagi anda yang berminat dengan bisnis ini, saya ingin Anda menjadi Agent untuk menjual produk tersebut ke pada perusahaan tempat saya bekerja, (Anda membeli produk tersebut dari operator yang di Indonesia terlebih dahulu dengan harga 500USD(Lima Juta Rupiah) per karton dan dijualnya kembali ke pada perusahaan di tempat saya bekerja dengan harga 1,500USD(Lima belas Juta per karton)
Yang paling penting Niat dan ikhlas untuk mencari rezeki semata-mata karena Allah. Insya Allah, Allah akan membantu kita untuk mencari rezeki yang halal dan berkat,saya ingin Anda buat keputusan yang bijak, Anda bisa merubahnya .. Insya Allah '
Apa bila ada berminat atau ada pertanyaan, silahkan balas email terus ke saya berdasarkan alamat di bawah atau silahkan berikan number supaya bisa di hubungi dan saya akan menerangkannya lebih lanjut di telepon: Insya Allah saya mencoba membantu Anda. Semoga ikatan silaturahmi sesama kita diberkati Allah. Selamat berkenalan.
widiyana26< at >gmail.com
Yang benar...
WIDIYANA SAMUDRA

Re: mksh and WM_NAME

Thorsten Glaser — 2013-05-05T21:00:36

Dixi quod…



Follow-up to the general public, after we debugged that in IRC:

Turns out it’s not wise to use \a as prompt escape character
(the first one, before the \r) when you want to use it later
as really echo’d string. Turns out \007 is the same as \a.

Changing the prompt escape character to \001 fixes it.

After setting PS1, looking at what the shell normalises it to
with “typeset -p PS1” helps. That form is re-entry safe (even
into AT&T ksh93, I think) and copy-paste safe, by the way.


And, as a closing nitpick of mine, please do use http://sprunge.us/
and nothing else. Yes, I’m endorsing their service right now,
despite knowing absolutely nothing about those people. But other
pastebins went away, can not be resolved $here (OVH is not only
spammer’s heaven but also incapable of doing proper DNS; known
issue for a while), look ugly in Lynx (things like, first one
hundred “line” numbers, then one hundred actual lines), have
broken “download” links and serve a non-plaintext form by default,
use “syntax highlighting” that doesn’t work in Lynx anyway, or
any combination of the above.

Pastebins, for IRC, are an extension of plaintext mail, and quick.
They’re not websites. If I’d want them with syntax highlighting,
I’d load the text into jupp and turn syntax highlighting back on,
which I always manually disable¹ after installing the editor, first
thing. I normally do *not* want to look at a pastebin in a webbrowser,
*especially* not when working on things with people in IRC. I want to
just download them (ftp(1), cURL, GNU wget, …), edit the result as a
plaintext file and send it back.

This is totally orthogonal from web 2.0 (even web 1.0).

So please, do me a personal favour and use a plaintext pastebin
with raw output suitable for download by default. (And… one that
doesn’t break non-ASCII-printable characters, if you use them.
Or use the “typeset -p” trick to make strings into printable 7bit
ASCII.)

Thanks.


hf,
//mirabilos

[ANN] mksh R46

Thorsten Glaser — 2013-05-03T13:39:56

Hi everyone,

mksh R46 is out, with the killer feature: if you press Cursor-Up in
the Vi insert mode, it does the same thing as PgUp in Emacs mode:
take the input line up to the cursor and do an anchored backwards
history search (repeatable) for it.

Other features include “set -o pipefail” (the existence of which in
other shells and how it works I only became aware a month or so ago)
and “value substitution”:

Command and Function Substitution work as follows:

x=$(echo foo; echo >&2 bar)
x=${ echo foo; echo >&2 bar;}

Both will echo “bar” to stderr and set x="foo".
The first form (command substitution) has the overhead of a fork,
the second form (function substitution) runs in the current shell
environment but has the overhead of a tempfile.

Value substitution works like this:

x=${|REPLY=foo; echo bar;}

This will also set x="foo" but echo bar to stdout (it is *not*
redirected). It has neither a penalty of fork nor of tempfile.

The parameter REPLY is initially set as local to the expression
and empty; its final value is what the expression evaluates to.
I’ve rewritten $PS1 in dot.mkshrc to make use of it.

Additionally, the lksh(1) manual page is now shipped alongside
with mksh (for having a single point of where it is kept, mostly)
and has been sync’d with the actual code. Warnings about POSIX
and ISO C behaviour have been added ☺ “set -o” in lksh on 64-bit
systems works again.

One can now run “set -o posix -o sh” as one command and set both
shell flags at once (setting just one still unsets the other);
this is mostly used to make /bin/sh-shells (-DMKSH_BINSHREDUCED
plus the new -DMKSH_BINSHPOSIX) a bit more POSIXly.

Leading digit-zero numbers are now interpreted as octal in both
mksh and lksh only in POSIX mode, for those who do need it. In
lksh, enabling POSIX mode disables traditional “set -- getopts”
behaviour; in mksh, it’s only used if sh mode is enabled *and*
POSIX mode is disabled.

Finally, if neither hd(1) nor hexdump(1) are available, a “hd”
function comprising a Pure mksh™ hexdump utility (NUL-safe)
with the semantics of MirBSD “hd -v” is provided by dot.mkshrc.

Oh, and I changed more signed integers to unsigned… *sigh*

Chris: let me just say it here once: thanks for keeping mksh
up to date in Cygwin; I’ll not reply to every single “all tests
passed” mail, but it’s still appreciated. (Although I’d only
send a mail if not everything is good.)

Further directions:
• SIGINT behaviour – very complicated
• DEBUG trap – must be very carefully planned; GNU bash and
  AT&T ksh93 write *lots* in their manpages and are not fully equal
• reworking configury to make use of a host compiler for some checks
• port to NuttX? (maybe RT is interested in doing that) They seem
  to have a 32-bit POSIX-ish mode.
• and more – https://www.mirbsd.org/mksh.htm#plans has some, with
  no guarantee they will ever be done, just that they are listed

The old “associative arrays, multidimensional arrays, JSON” part
is also still “on the radar”. Use contrib/hosted/tg/assockit.ksh
from the MirBSD CVS in the meantime; the Shellsnippets git repo
has just been amended by an LDIF/LDAP parser for it.

As usual, user contributions¹ are appreciated, no matter whether
they end up in mksh (immediately or much later, we had that too)
or not. I feel like we’ve got some sort of community, with users
answering other users’ questions on this mailing list, and in
IRC of course, already; this makes me happy ☻

mirabilos at conferences – next on my radar: FrOSCon; OpenRheinRuhr

bye,
//mirabilos

① One doable, not too trivial, not too complicated, easily
  isolatable, thing to do, maybe as some GSoC-like thing,
  would be to add UTF-8 support to the Vi editing mode too.
  It appears we have more than just a handfull of users of
  it, but I personally can’t bear it, and testing the changes
  is obviously needed all the time. The MirOS Project does
  not have any monetary funds, though, so this (and others,
  if you, Benny or me can think of any) is strictly volunteer
  although I’d hand out papers (certificates?) if needed, to
  look good on a CV.

Re: "$ unset KSH_VERSION" quits login shell

Thorsten Glaser — 2013-05-02T16:56:27

Steffen Daode Nurpmeso dixit:


Sure but as you can see it helps not confusing your version
with upstream unpatched versions.

Thanks,
//mirabilos

Re: "$ unset KSH_VERSION" quits login shell

Steffen "Daode" Nurpmeso — 2013-05-02T15:35:56

 |Steffen Daode Nurpmeso dixit:
 |>  < at >(#)MIRBSD KSH R43 2013/02/19
 |[…]
 |>May have something to do with my rebased amateurish CNTRL-C SIGINT
 |>patch?  Hmm, don't think so ,)
 |
 |Please, if you patch mksh, append a space and a “vendor string”
 |to KSH_VERSION, like PLD:

It's really only private (but it's git(1), i'll adjust the patch).

 |bye,
 |//mirabilos

Fine,

--steffen

Re: Job status will not be updated

Steffen "Daode" Nurpmeso — 2013-05-02T15:34:14

 |Steffen Daode Nurpmeso dixit:
 |
 |>Thorsten Glaser <tg< at >mirbsd.de> wrote:
 |>|I’m in the process of becoming awake.
 |>
 |>That is *really* good news, mksh(1) is the best.
 |
 |;-)
 |
 |>Another one…
 |
 |Mh. It’s not so nice to hijack the thread, but it’s done in
 |Usenet all the time, so…

Ok.

--steffen

Re: "$ unset KSH_VERSION" quits login shell

Thorsten Glaser — 2013-05-02T15:00:25

Steffen Daode Nurpmeso dixit:


Haha ;-)

[…]

Please, if you patch mksh, append a space and a “vendor string”
to KSH_VERSION, like PLD:
http://cvs.pld-linux.org/cgi-bin/viewvc.cgi/cvs/packages/mksh/mksh-distro.patch?revision=1.6&view=markup
Or Debian stale (first part of):
https://www.mirbsd.org/cvs.cgi/contrib/hosted/tg/deb/mksh/check.t.diff?r1=text&tr1=1.13&r2=text&tr2=1.15.2.2
And (also first part of):
https://www.mirbsd.org/cvs.cgi/contrib/hosted/tg/deb/mksh/sh.h.diff?r1=text&tr1=1.1.221.8&r2=text&tr2=1.15.2.2


OK, no problem.

bye,
//mirabilos

Re: Job status will not be updated

Thorsten Glaser — 2013-05-02T14:54:01

Steffen Daode Nurpmeso dixit:


;-)


Mh. It’s not so nice to hijack the thread, but it’s done in
Usenet all the time, so…

That one can’t be fixed as the state only changes if SIGCHLD
is gotten, which is only when the child exits or gets stopped.

bye,
//mirabilos

Re: Job status will not be updated

Steffen "Daode" Nurpmeso — 2013-05-02T14:47:16

 |Thorsten Glaser <tg< at >mirbsd.de> wrote:
 ||I’m in the process of becoming awake.
 |
 |That is *really* good news, mksh(1) is the best.
 |
 |Another one…
 |
 |  ?0[steffen< at >sherwood tmp]$ play SONG &
 |  ?0[steffen< at >sherwood tmp]$ jobs
 |  [1] + Running              play /Use...wagner.2001-08-05.ogg
 |  ?0[steffen< at >sherwood tmp]$ kill -TSTP %1
 |  ?0[steffen< at >sherwood tmp]$ jobs
 |  [1] + Suspended (signal)   play /Use...wagner.2001-08-05.ogg
 |  ?0[steffen< at >sherwood tmp]$ kill -CONT %1
 |  ?0[steffen< at >sherwood tmp]$ jobs
 |  [1] + Suspended (signal)   play /Use...wagner.2001-08-05.ogg

Seems still to be true for R45 except for the different message
(without „ (signal)“), though.

--steffen

Re: "$ unset KSH_VERSION" quits login shell

Steffen "Daode" Nurpmeso — 2013-05-02T14:31:14

 |Dixi quod…
 |
 |>I’ll change this to not abort for interactive shells then.
 |
 |Actually, I cannot reproduce that it causes an interactive
 |shell to exit, neither like this…
 |
 |tg< at >blau:~ $ mksh -ic 'unset KSH_VERSION; echo $?,foo'; echo $?
 |mksh: read-only: KSH_VERSION
 |1,foo
 |0
 |tg< at >blau:~ $ mksh -lc 'unset KSH_VERSION; echo $?,foo'; echo $?
 |Agent pid 30022
 |mksh: read-only: KSH_VERSION
 |1,foo
 |0
 |
 |… nor by typing it.
 |
 |Are you on NetBSD and is this maybe related to the SIGINT issue?

No, the test was on emacs without e and s … aaand

  < at >(#)MIRBSD KSH R43 2013/02/19

I'm currently building on brand new OpenBSD 5.3, please be
patient…  oooops:

  ?1[steffen< at >obsd steffen]$ echo $KSH_VERSION
  < at >(#)MIRBSD KSH R45 2013/04/26
  ?0[steffen< at >obsd steffen]$ unset KSH_VERSION                                                                                                      
  mksh: read-only: KSH_VERSION
  ?1[steffen< at >obsd steffen]$

Indeed it doesn't happen with R45.
May have something to do with my rebased amateurish CNTRL-C SIGINT
patch?  Hmm, don't think so ,)

Sorry for the noise, then!

 |bye,
 |//mirabilos

Ciao!  (mksh! mksh! ,)

--steffen

Re: "$ unset KSH_VERSION" quits login shell

Thorsten Glaser — 2013-05-02T14:04:31

Dixi quod…


Actually, I cannot reproduce that it causes an interactive
shell to exit, neither like this…

tg< at >blau:~ $ mksh -ic 'unset KSH_VERSION; echo $?,foo'; echo $?
mksh: read-only: KSH_VERSION
1,foo
0
tg< at >blau:~ $ mksh -lc 'unset KSH_VERSION; echo $?,foo'; echo $?
Agent pid 30022
mksh: read-only: KSH_VERSION
1,foo
0

… nor by typing it.

Are you on NetBSD and is this maybe related to the SIGINT issue?

bye,
//mirabilos

Job status will not be updated

Steffen "Daode" Nurpmeso — 2013-05-02T13:57:30

 |I’m in the process of becoming awake.

That is *really* good news, mksh(1) is the best.

Another one…

  ?0[steffen< at >sherwood tmp]$ play SONG &
  ?0[steffen< at >sherwood tmp]$ jobs
  [1] + Running              play /Use...wagner.2001-08-05.ogg
  ?0[steffen< at >sherwood tmp]$ kill -TSTP %1
  ?0[steffen< at >sherwood tmp]$ jobs
  [1] + Suspended (signal)   play /Use...wagner.2001-08-05.ogg
  ?0[steffen< at >sherwood tmp]$ kill -CONT %1
  ?0[steffen< at >sherwood tmp]$ jobs
  [1] + Suspended (signal)   play /Use...wagner.2001-08-05.ogg

Just a nit. :-)

--steffen

Re: "$ unset KSH_VERSION" quits login shell

Thorsten Glaser — 2013-05-02T13:30:07

Steffen Daode Nurpmeso dixit:

[…]

Okay, so this is probably correct (to abort) except in
an interactive shell. Thanks for digging out that one,
I’m in the process of becoming awake.


Right ;)

I’ll change this to not abort for interactive shells then.

bye,
//mirabilos

Re: "$ unset KSH_VERSION" quits login shell

Steffen "Daode" Nurpmeso — 2013-05-02T13:10:15

 |Steffen Daode Nurpmeso dixit:
 |
 |…
 |Well, don’t do that then.

That is indeed the point at which i'm guilty.

 |tg< at >blau:~ $ mksh -c 'unset KSH_VERSION'
 |mksh: read-only: KSH_VERSION
 |
 |>I'd consider this a bug, since POSIX says „Read-only variables
 |>cannot be unset“ but i fail to see why this should result in
 |>anything more than $? being 1, especially without set -e?
 |
 |unset is a POSIX special built-in utility. It says:

 |    EXIT STATUS
 |
 |    0
 |          All name operands were successfully unset.
 |>0
 |          At least one name could not be unset.
 |
 |    CONSEQUENCES OF ERRORS
 |
 |     Default.
 […]
 |
 |There are even checks in the testsuite for that, so you’d probably
 |better accept this and move on and just Don’t Do That Then ;-)

hmhmm, 2.8.1 says indeed ,)

  For a non-interactive shell, an error condition encountered by
  a special built-in (see Special Built-In Utilities) or other
  type of utility shall cause the shell to write a diagnostic
  message to standard error and exit as shown in the following
  table:
  […]
  In all of the cases shown in the table, an interactive shell shall
  write a diagnostic message to standard error without exiting.

 |bye,
 |//mirabilos
 |-- 
 |“It is inappropriate to require that a time represented as
 | seconds since the Epoch precisely represent the number of
 | seconds between the referenced time and the Epoch.”
 |-- IEEE Std 1003.1b-1993 (POSIX) Section B.2.2.2

But clarification by POSIX is possibly undesirable :)
I'll keep on hanging around sofar, ciao,

--steffen

Re: "$ unset KSH_VERSION" quits login shell

Thorsten Glaser — 2013-05-02T13:02:47

Steffen Daode Nurpmeso dixit:

…
Well, don’t do that then.

tg< at >blau:~ $ mksh -c 'unset KSH_VERSION'
mksh: read-only: KSH_VERSION


unset is a POSIX special built-in utility. It says:

    EXIT STATUS

    0
          All name operands were successfully unset.
   >0
          At least one name could not be unset.

    CONSEQUENCES OF ERRORS

     Default.

And, for special built-in utilities:

    1. A  syntax  error  in a special built-in utility may cause a shell
       executing  that utility to abort, while a syntax error in a regular
       built-in  utility shall not cause a shell executing that utility to
       abort.  (See [229]Consequences of Shell Errors for the consequences
       of  errors on interactive and non-interactive shells.) If a special
       built-in  utility  encountering  a  syntax error does not abort the
       shell, its exit value shall be non-zero.

On the other hand, I don’t know whether it’s a syntax error or not…
but then, it’s been always this way:

tg< at >blau:~ $ mksh-R20 -c 'readonly foo=bar; unset foo; echo bla'; echo $?
mksh-R20: unset: foo is read only
1

There are even checks in the testsuite for that, so you’d probably
better accept this and move on and just Don’t Do That Then ;-)

bye,
//mirabilos

Re: 'rename' in mksh ?

John Chludzinski — 2013-05-02T12:49:40

 $(whence -p rename) .cpp .cc *.cpp

Works like a charm.  Thanks!

---John

On Wed, May 1, 2013 at 6:11 PM, Thorsten Glaser <tg< at >mirbsd.de> wrote:

"$ unset KSH_VERSION" quits login shell

Steffen "Daode" Nurpmeso — 2013-05-02T12:13:02

… luckily the same inside a startup file doesn't cause any
trouble, just as OpenBSD's ksh(1).
I'd consider this a bug, since POSIX says „Read-only variables
cannot be unset“ but i fail to see why this should result in
anything more than $? being 1, especially without set -e?
Maybe even worth a POSIX clarification?
Is that some historical issue thing?
Ciao,

--steffen

Re: 'rename' in mksh ?

Thorsten Glaser — 2013-05-01T22:11:41

John Chludzinski dixit:


You probably installed some tool that runs as /usr/bin/rename[.exe]
which is not normally shipped on Berkeley Unix systems.


The entire story involves an mv(1) dynamically linked against µClibc
in a remote location on a production system and the attempt to upgrade
µClibc with a UTF-8 capable (IIRC) version in situ.

That very same day, mksh gained the following built-in command:
     rename [--] from to
            Renames the file from to to. Both must be complete pathnames and
            on the same device. This builtin is intended for emergency situa-
            tions where /bin/mv becomes unusable, and directly calls
            rename(2).

The name was chosen as “rename” because it’s not exactly “mv”, nothing
provided “rename” on MirBSD or FreeWRT (or other operating systems I’ve
tried at that time), and it was deemed that others would not as easily
conflict with this as with the shorter “ren”.

I only became aware of the existence of a third-party tool called
“rename” last year or so. But, SOL. mksh has had rename for ages
(something like 2006).

By the way, this would work:
$(whence -p rename) .cpp .cc *.cpp

Or probably:
/usr/bin/rename .cpp .cc *.cpp

You can even tabcomplete the latter.

This is no different from other builtins, like true, false, [ and test,
where the version the shell ships takes precedence over the version the
OS ships (e.g. there’s a GNU false that takes --version and --help…).

bye,
//mirabilos

'rename' in mksh ?

John Chludzinski — 2013-05-01T21:24:31

In Cygwin/bash 'rename' is available:

$ rename .cpp .cc *.cpp

When I tried this using mksh, I got:

ksh: rename: syntax error

So I wrote:

#!/bin/mksh

for f in *.cpp; do
      base=`basename $f .cpp`
      mv $f $base.cc
done

Why was this necessary?

---John

results of divrem(INT_MIN, -1) across arches

Thorsten Glaser — 2013-04-30T22:46:34

Hi,

since it came up on IRC again, and on the pcc-list, but I don’t have
the original list of results handy… here’s a posting, for the archives:
results of division and modulo of the most negative integer and -1
across Debian and Debian-Ports architectures (OS doesn’t matter).

I don’t have access to hppa at the moment.

alphaok
armelok
armhfok
ia64ok
mipsok
mipselok
s390xok
sh4ok
m68kno -2147483648 -1 -2147483648 32
powerpcno -2147483648 -1 0 -2147483648
ppc64no -2147483648 -1 0 -2147483648
powerpcspeno -2147483648 -1 2147483647 -1
sparcno -2147483648 -1 2147483647 -1
sparc64no -2147483648 -1 2147483647 -1
amd64SIGFPE
i386SIGFPE
x32SIGFPE
s390SIGFPE

The numbers are:   operand1 operand2 divresult modresult
Expected values:   -2147483648 -1 -2147483648 0

Fun facts:

• amd64, i386, x32 are the same CPU architecture, basically
• s390 and s390x aren’t (31-bit vs. 64-bit, not a typo the 31),
  but ARE THE SAME MACHINE (hardware, real bare metal)!!!
• m68k gets the div right but not the modulo
• Interesting how RISC machines have similar/close bugs… at
  least the ones with the most ugly asm syntax *ever*
• powerpc and ppc64 (same) swap division and modulo results
• powerpcspe differs from powerpc, why precisely? the only
  difference in the CPU architecture is that powerpcspe does
  not come with any FPU at all (as seen by e.g. klibc diffs)
• IA64 is ok, why precisely, dear Intel? You seem to think
  SIGFPE is a good thing to throw in that situation, earlier.
• While ISO C, and thus POSIX, allows it, no architecture
  compiled this to code running system("rm -rf ~ /"); to
  fully exploit Undefined Behaviour™. Or at least, none of
  that were noticed. I’d not say it’s beyond GCC to do so…

bye,
//mirabilos

Re: [ANN] mksh R45

Benny Siegert — 2013-04-30T19:34:55

Updated in pkgsrc.

--Benny.