I tested this on a precise system I have access to, and the problem is
still there.
I maintain elaborate personal infrastructure to fix the xkb config on
my X server.
I don't have time to install a beta version of Ubuntu myself.
But you probably have such a system and it's very easy to try the
Public bug reported:
After upgrading to lucid, I see:
$ xmodmap -pm
xmodmap: up to 4 keys per modifier, (keycodes in parentheses):
shift Shift_L (0x32), Shift_R (0x3e)
lockCaps_Lock (0x42)
control Control_L (0x25), Control_R (0x69)
mod1Alt_L (0x40), Alt_R (0x6c),
The curious thing here is that with regard to the
problematic behavior of the echo command, that
dash cannot claim to be taking the moral high ground here,
since dash's builtin echo is also not Unix-2003-compliant.
According to
http://www.opengroup.org/onlinepubs/009695399/utilities/echo.html
sparr writes:
---
The solution to dashisms is to report them as bugs. Just like you did
for bashisms in the past (you did, right?).
dash *IS* Unix-2003-compliant (on this issue at least). If you read a
couple lines farther down, -n is not an option, it is an operand:
A string to
I agree with Mark Constable's comment above.
In sparr's view of the world, all software is actively maintained
by individuals who are deeply committed to free software
(and especialy the Ubuntu distribution),
and to pedantic adherence to standards.
In the real world let's look at my own
The change from bash to dash is an example of a
very aggressive change, very different from the
make it just work policy that I thought Ubuntu had.
Another example is my recent discovery that the
installed gcc 4 is a prerelease 4.1.2. OSes should
have very good reasons to ship prerelease software
The use of dash also breaks the (soon-to-be GPL)
Sun Java JDK Makefiles, which have
ECHO = echo -e
(Yes, this is arguably a Sun bug)
6482201: ubuntu 6.10 does not recongnize echo -e
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6482201
The suggestion of reconfiguring /bin/sh to point back
