opensnoop didn’t really cut it, so here we go:
syscall::open*:entry
{
printf(”%s %s”, execname, copyinstr(arg0));
}
syscall::stat*:entry
{
printf(”%s %s”, execname, copyinstr(arg0));
}
The Apple Mac OS mouse cursor speed is one of those “love it, or hate it” domains. Personally I find the default speed already way too slow, always falling asleep on a fresh Mac install, or at the login window.
The max used to be barely endurable, so far, e.g. with the Mighty Mouse - until I got the Magic Mouse the other day. Directly compared the Magic Mouse moves way slower with at the same setting. No idea how Apple got this inconsistency in their own, few products. I also have no idea why mouse pointer movements can possibly be that slow. Not only the default, but also the maximal configuration value, …
Fortunately there is no limit behind the back, so you can tune it with:
defaults write -g com.apple.mouse.scaling -float 8
The 10.6.2 maximal UI value appears to be 3, …
Update: Some more review: The slowness aside, the Magic Mouse is pretty decent. The biggest improvement over the Mighty Mouse is the touch sensitive cover. The former microscopic scroll ball was prone to accumulate dirt inside and near to impossible to clean. (To really clean and remove dust and dirt from the ball axes one hat to cut(!!!) the glued mouse housing and disassemble it fully, …). So from this usability standpoint it’s a great improvement. The major downside is, that only a Bluetooth version is available. I personally find the weight of the two AA batteries too hefty - that was also already a problem with the Bluetooth Mighty Mouse. For my excessive workdays I would prefer a lighter, cabled version to reduce the wrist stress, …
Well, these days most news sites just publish the press releases of product announcements. Or re-tweet news from other sites. Personally I find really authentic, journalistic work such as the recent Tom’s Hardware video driver, 2D blitting vs. Windows 7 review particularly outstanding. Heck, they even wrote their own performance metric test utility for it!
With r35579 I just added the (very tine) required build script configuration and glue to let the T2 SDE (System Development Environment) build script use clang and clang++ as the default C and C++ compiler. And I just successfully compiled the first packages on a x86-64/T2/Linux test build:
-rw-r–r– 1 root root 3949 Feb 16 15:41 9-atop.log
-rw-r–r– 1 root root 21444 Feb 16 15:45 9-libelf.log
-rw-r–r– 1 root root 55854 Feb 16 15:45 9-fontconfig.log
-rw-r–r– 1 root root 3827 Feb 16 15:45 9-renderproto.log
-rw-r–r– 1 root root 34883 Feb 16 15:46 9-libxext.log
-rw-r–r– 1 root root 12765 Feb 16 15:46 9-libice.log
-rw-r–r– 1 root root 22070 Feb 16 15:46 9-libsm.log
-rw-r–r– 1 root root 31354 Feb 16 15:47 9-libxt.log
-rw-r–r– 1 root root 15357 Feb 16 15:47 9-libxmu.log
-rw-r–r– 1 root root 15243 Feb 16 15:47 9-libxpm.log
-rw-r–r– 1 root root 12157 Feb 16 15:48 9-libxrender.log
-rw-r–r– 1 root root 13854 Feb 16 15:48 9-libxft.log
-rw-r–r– 1 root root 13782 Feb 16 15:48 9-libxkbfile.log
-rw-r–r– 1 root root 135931 Feb 16 16:00 9-openssh.log
-rw-r–r– 1 root root 344112 Feb 16 16:05 9-openssl.log
-rw-r–r– 1 root root 17024 Feb 16 16:06 9-screen.log
The resulting ssh and screen even worked as expected (so far, anyway).
Your system keeps telling you a locale is not supported by your system’s C library? For example:
svn: warning: cannot set LC_CTYPE locale
svn: warning: environment variable LANG is en_US.UTF-8
svn: warning: please check that your locale name is correct
or:
firefox: (process:4376): Gtk-WARNING **: Locale not supported by C library.
Using the fallback ‘C’ locale.
or even while compiling software, such as:
setlocale(LC_CTYPE,”en_US.UTF-8″) failed!
make: *** [extra/locale/c8tables.h] Error 1
You can use “localdef” to add them to the cache from the verbose source definitions:
localedef -i en_US -c -f UTF-8 en_US.UTF-8
…, Clang is now self-hosting! Congratulation to the LLVM and Clang team around Chris Lattner.
Guess that’s the days where I should start making clang a system compiler option in T2, and leave GCC and it’s C days of the ’80s behind 
!
I only say: Subsidized, or near no margin for a “gold rush” thru content, App sales.
Well, the iSlate name rumor sounded really strange. iTablet? Oh well. iPad indeed makes a little more sense.
However, honestly, the “iPad” is not really what I’ve been waiting for. Having one device for a job is so from the 90th - where several manufactures wanted to sell a device per job: one for calculation, one for phoning, one for your music, etc. pp. Obviously that did not turn out to be accepted too well. The iPhone was such as success because it combine so many required things in one device: phone, email, photo, web, music.
So I got a Star Trek 11 Blue Ray Sunday. It already came with a strange “package insert”, indicating that if the disc was manufactured after the purchase of the Blue-ray player, a firmware “configuration update” may be required. Of course it was on my only Blue-ray player, which happens to be a Sony PlayStation 3. So normally I try to avoid firmware updates on the PS3, in order to use as much “out-of-spec” features under (T2) Linux, such as GPU access, as possible. However, well, now I had to bite that bitter pill.
Also very interesting how the parties speak about “configuration” instead of cryptographic key update, …
Fortunately others are currently hacking into the hypervisor for all the goods of it.
Let’s hope this also brings Linux onto the Slim
So I update my main workstation running Linux to the latest, greatest X.org release. To my surprise the already not so fast xf86-video-nv driver stopped working entirely. I get no video signal either on the laptop’s internal LVDS panel, nor the external, DVI port. As quick, even slower, fallback at least xf86-video-vesa still worked. Just on the internal display, of course. At least something. However, my biggest surprise was still ahead: The keyboard layout kept constantly changing! Between English(US) and German(DE) !!!! How am I supposed to type, work, that way, heh? Even entering my login password became a challenge only cut’n paste could solve, …
How the heck can software regress that majorly. Ok, well. Random hacking might explain it. Too many cooks spoil the broth. But really. ‘nough is ‘nough. The X.org machinery worked better 10 years ago in the days of XFree86 on my then 120MHz Intel Pentium, 233MHz IDT Winchip 2(a or so). Certainly some S3 Virge3D, later Matrox graphic cards.
Update: Good old modeline stuff segfaulting, yuck:
Program received signal SIGSEGV, Segmentation fault.
(gdb) bt
#0 0×0000000000000000 in ?? ()
#1 0×0000000000487813 in xf86CrtcSetModeTransform (crtc=0×7f3f80, mode=0×7f4068, rotation=1,
transform=0×3, x=0, y=0) at xf86Crtc.c:358
#2 0×0000000000487b65 in xf86SetDesiredModes (scrn=0×7f1de0) at xf86Crtc.c:2608
#3 0×00002b700de77b12 in AcquireDisplay (pScrn=0×7f1de0) at g80_driver.c:467
#4 0×00002b700de77eb3 in G80ScreenInit (scrnIndex=, pScreen=0×7f6f10,
argc=, argv= ) at g80_driver.c:894
#5 0×000000000044df45 in AddScreen (pfnInit=0×2b700de77b80, argc=1,
argv=0×7fff7bce36e8) at dispatch.c:4062
#6 0×0000000000478519 in InitOutput (pScreenInfo=0×7d3300, argc=1, argv=0×7fff7bce36e8)
at xf86Init.c:1043
#7 0×00000000004224e5 in main (argc=1, argv=0×7fff7bce36e8, envp=0×7fff7bce36f8) at main.c:204
Update 2: Not soo much good-old-modeline as guessed at first - more so newly added gamma fluff, …
X.org bug - so basically the whole X server setup is crashing in many combinations and cards since last November??? What a fun.