Moderate Activity

News

  Analyzed 5 days ago based on code collected 7 days ago.
 
Posted about 2 years ago by Harri Haataja
xtl's status on Saturday, 02-Apr-11 10:08:40 UTC
Posted about 2 years ago by t...@mirbsd.org (MirOS Developer tg)
mksh-current has just gained an
experimental recursive parser for command substitutions, fixing
RedHat
BZ#496791 and decades-old complaints about the pdksh codebase,
compared to AT&T ksh93. (GNU bash could also do the example ... [More] , but not
some other things mksh(1) parses fine now.)

This means that things like the following work now.

# POSIX, should “always” work
echo $(case 1 in (1) echo yes;; (2) echo no;; esac)
# POSIX optional, works now in mksh, works in GNU bash
echo $(case 1 in 1) echo yes;; 2) echo no;; esac)
# GNU bash seems to choke on comments ending with backslash
# a comment with " ' \
x=$(
echo yes
# a comment with " ' \
)
# No non-recursive COMSUB parser can pass all of the above
# tests and these below at the same time (some extensions)
echo $(typeset -i10 x=16#20; echo $x)
echo $(typeset -Uui16 x=16#$(id -u)
) .
echo $(c=1; d=1
typeset -Uui16 a=36#foo; c=2
typeset -Uui16 b=36 #foo; d=2
echo $a $b $c $d)
# the ‘#’ is especially tricky, that’s why the above cases

Next on my TODO is the complete rewrite of the
read built-in command, as well as its documentation. I think that the
(reduced) goals for mksh R40 will have been met by then, except porting
to LynxOS and MPE, but we’re working on it, and re-testing Syllable and
Plan 9). Of course, a release implies testing on a lot of the
supposedly supported platforms, so it won’t be out “immediately”. Though,
associative arrays have been removed from the R40 goals, so that I can
at least get a new release out. Note that Debian and OpenSuSE Buildservice
users have been provided with somewhat well-tested mksh-current snapshots
for a while already, and Gentoo users can use the “live ebuild”; there’s
always compiling from source too… [Less]
Posted about 2 years ago by t...@mirbsd.org (MirOS Developer tg)
Warning: this is a rant against BSD (specifically FreeBSD®, but don’t let
me get started on DragonFly, who think it’s wise to drop all shells except
ash from the base system and rely on pkgsrc® – yay let’s compile a dozen
... [More] packages just to get a shell with tab completion, not to mention boxen with
no network access – for the task – although others seem to go into that
direction too…; you know, there’s BSD, and then there’s FreeBSD…) – don’t
like, don’t read.

If you want to change something in the BSD world, you gotta fork your
own BSD – no other way around the thickheads. Ok, back then, I ran into
a particularily thick one, but others tend to not be much better. Users
share the thickness. If you want to change something in the GNU/Linux
world, just make a package, have someone upload it, prod (or pay, Hanno
got a Radler) people to do it, or just upload it yourself.

At the BSD booth at FOSDEM, despite me bringing the Windows® Mobile
6 Professional devive, strictly for Geocaching mind you, Macintosh boxen
had a share of more than 50% – I didn’t manage to tip the scale. At the
Debian booth, almost everyone had a “I want to buy a new laptop some day,
but it just keeps on working and doesn’t break” pre-Lenovo IBM laptop.
No hyping of Google either. (Last year’s CLT saw BSD people advocating
pro-Schily – the guy with the broken encoding in his name – shockingly.)

Honestly, tcsh, FreeBSD® people? Sorry. While I agree that there is
merit on having the same script and interactive shell, as someone has
pointed out (copy-paste examples into the command line), there’s those
zsh users who use mksh or GNU bash
for scripting. Or just POSIX shell. And that’s with an interactive shell
which can be used for scripting. On
the other hand, the
C shell (both csh and tcsh) cannot.

And what’s with pretending the accent
gravis is non-combining, called “backtick” (such a thing does not
exist); and advocating it? Sorry, if your csh/tcsh doesn’t handle the
POSIX $(…) you should just drop it. (By the way, there is
a convention that example command lines are prefixed with %  for
csh and $  for sh (or #  but we write $ sudo 
instead, these days). Use it. Or leave it. If you have examples that
substitute another process’ output, be specific.) It’s funny to see how
one person tries to defuse my arguments against csh by telling me “it’s
just an interactive shell”, while the other argues that people copy-paste
between them, to which that was my response. Read the thread!

And please, get your facts right. “I would prefer that the standard shell
be at least Bourne-compatible.” You don’t want Bourne (“^” instead of “|”
for pipes), you want POSIX. That GNU bash is called the Bourne-Again Shell
in one of their usual semi-bad puns doesn’t help the global perception of
such things any. Also, the root shell and /bin/sh are disjunct.

(Plus, why change the root shell, use sudo(8), plain and simple.)

ObNote: in jupp (should I package that
for Debian, btw? rather upload, packages are ready…) the ‘`’ key is used
as præfix for Ctrl-X (`X) or to directly enter numerical (decimal,
octal, sedecimal/hexadecadic) ASCII, 8-bit or Unicode codepoints. Yay!
And even the FSF has seen the light; for a few releases already, GCC uses
“'…'” instead of “`…'” for quoting in messages, even without locales. Great
job there! (LC_MESSAGES=en_GB.UTF-8 usually works, too, though.)

ObDisclaimer: I have an (yes, Google…) Alert on the word “mksh”, so I know
when it’s being discussed. This obviously includes certain fora. Also, I’m a
shell implementer and bound to know a certain amount of details. Plus, mksh’s
build script runs with pretty much any Bourne/POSIX/Z Shell which has
functions and not too many bugs. I wrote it. Go figure. No lowly trolling.

FWIW, mksh(1) has the cat(1) builtin both because Android has no cat(1),
and as speed hack. Almost all other shells have worse speed hacks, like a
printf(1) builtin. And recently, builtins have become direct-callable, so
this actually reduces the overall system footprint. (Its inclusion also
provides for some other possibilities, internally.) And as two final side
notes, if you haven’t seen this: determine which shell we are run under (CVS)
and I still offer a prompt conversion service (send me any GNU bash or oksh
$PS1 and I’ll send that to you in mksh(1) syntax – optionally with
adjustments/improvements, like cwd uses only up to 1/3 of screen width). [Less]
Posted over 2 years ago by t...@mirbsd.org (MirOS Developer tg)
Eh. Why does mksh built with (a patched:
mkstemp(3) added) klibc work
suddenly, unexpectedly?

To reproduce, I just uploaded mksh_39.3.20110218-1.dsc and you can
run DEB_BUILD_OPTIONS=mksh-static=klibc,dietlibc,eglibc ... [More] dpkg-buildpackage
-rfakeroot to verify it, once you have mkstemp(3). (I will probably send
a smaller implementation of that in, later.) I have that and the open fix and
the m68k patch applied, nothing else… where did my bug go?

ObQuestion: what’s the legal (copyright/trademark) status of the Atari logo
(the one in rainbow colours, with three things going up, right and left “leg”
looking like an umbrella stand’s)? [Less]
Posted over 2 years ago by t...@mirbsd.org (MirOS Developer tg)
I just need to work more on bilocality. While I did find two geocaches,
one at the South/Noon Train Station (taalverwarringen…), one in the buurt
of the University, I did manage to miss the AW building completely and
utterly. Wow. ... [More] Except, that Haiku guy came over to talk for a bit (nice).
And I drew. An Atari logo with swirl, for that weird stuff I recently have
been found doing.

More mksh-current news coming soon,
stay tuned. In the meanwhile, I met bonsaikitten IRL (at FOSDEM, yes, too)
who kindly made a “live ebuild”, i.e. a source package building -current.

Finally let’s say a big thank you to the person mostly manning our booth,
gecko2, and to Benny for talking to people, getting That Other Packaging
Thingy working, and pimping the website a bit. [Less]
Posted over 2 years ago by blink
blinkkin's status on Wednesday, 02-Feb-11 23:05:48 UTC
Posted over 2 years ago by Thorsten Glaser
Posted over 2 years ago by t...@mirbsd.org (MirOS Developer tg)
The Android 3.0 (Honeycomb)
Preview [German news] comes with a much more sensible /system/bin/sh than previous
released versions… Android-x86 and AOSP have had it for a while, but
this sees the general adoption of mksh(1) as the only POSIX/Korn Shell
on the Android OS! Thanks to those who helped to make this reality.
Posted over 2 years ago by t...@mirbsd.org (MirOS Developer tg)
I’ve just prepared an ISO for FOSDEM Ⅺ
which we might export on BitTorrent soon.
Benny has provided an upgraded desktop background image, thanks.

The next mksh release… well I’ll bite
the sour apple and will release it ... [More] without associative arrays but hope I
get around to hack a few things (especially the read and sleep builtins)
before releasing. One lession learned, don’t brag with oh-so-big plans
when you haven’t got a deliverable yet. Real Life will interfere.
Oh, and Murphy, of course. (mksh R41 might have the associative arrays
then. But mksh-current has ${foo@#} which is hash($foo). [Less]
Posted over 2 years ago by t...@mirbsd.org (MirOS Developer tg)
❧ Who’s not? ☺ Same procedure as every year.

(okay, lolando prefers skiïng but…)

Anyway. A cow‐orker told me that Belgium again/still has no gouvernment,
and they have been asked to grow out their beards until they ... [More] do. I found
“evidence” on the ’net but won’t link it here, also it’s on German… anyway.
Let’s all join in. (Besides, I now have an excuse to not shave, maybe even
my grandmother will accept this one…)

RT said on IRC that mksh will probably
work on MSYS.

My Debian/m68k stuff is coming around nicely, but I still haven’t
gotten around to do everything planned, plus I need to grow a new kernel and
eglibc, after the latest uploads, and the 2.6.37 based one panics. Also I’ve
got to take care to not overwork myself. (And make a MirBSD ISO for FOSDEM.)
But hey, it’s been not working for some time and better now. And slow anyway
☺ yet we’re progressing. Does anyone know how to debug that a C programme
only calling res_init(3) segfaults?

Benny is apparently not just working on making NetBSD® pkgsrc® available
on MirOS BSD (picking up my work from 4+ years ago) but also replacing
The MirPorts Framework with it. Sad, as I got a request for a gajim MirPort
over a cocktail just this evening… [Less]
 

 
 

Creative Commons License Copyright © 2013 Black Duck Software, Inc. and its contributors, Some Rights Reserved. Unless otherwise marked, this work is licensed under a Creative Commons Attribution 3.0 Unported License . Ohloh ® and the Ohloh logo are trademarks of Black Duck Software, Inc. in the United States and/or other jurisdictions. All other trademarks are the property of their respective holders.