|iris, and darwin tweaks
||[Jan. 12th, 2008|11:43 am]
Benjamin C. Wiley Sittler
i think iris might be starting to talk. the words are few, and the pronunciation odd enough that i'm never really sure, but i think i've been hearing "fish", "kitty", "guido" (one of the cats), and "no" used in more-or-less appropriate situations. rebbyribs is a bit more skeptical, but i'm sure iris will talk clearly and distinctly soon enough.
note: what follows is a discussion of scripts that modify your mac os x kernel. this is potentially very risky, as the kernel is what allows everything else to run. although i have made every attempt to ensure they are safe (and believe they are), i can't guarantee it or be held liable if things go wrong. in particular:
THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHOR OR ANY OTHER CONTRIBUTOR BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
also, this morning's project was to get the mac os x/darwin console vt100 alternate character set support to work and (closely related) to customize the mac os x/darwin console color palette. the end result is a pair of shell scripts that seem to work, and a lot of scratching my head — why didn't they
ⓐ ship with the VT100 positions filled in their font, or
ⓑ provide a simpler interface for switching the font and color palette at runtime (using, say, escape sequences or a sysctl.) oh and
ⓒ why does their console strip the eighth bit off of all output (despite the font [based on a design by zestyping] supporting the first 256 unicode/ucs code points), and finally
ⓓ why don't the function keys work?
update: it's probably worth explaining a bit more here:
On Intel and PowerPC platforms, Apple's Darwin operating system and Mac OS X use a full-screen system console derived from a NetBSD framebuffer console. It is an ANSI-style terminal, and is not really VT100 compatible.
Under Mac OS X (both PowerPC and Intel), this is the system console driver used while in single-user mode [reachable by holding down Command-S during the boot process] and when logged in using console mode [reachable by typing ">console" at the graphical login prompt.]
Under Mac OS X version 10.4, you'll need to enable the password dialog inside the System Preferences | Accounts | Login Options panel by disabling the "Automatically log in as" option and setting the "Display login window as" option to "Name and password"
The scripts require access to kernel memory. By default they enable the built-in
/dev/kmem by adding the
kmem=1 option to the
nvram boot-args — however, it may be possible to use them with Amit Singh's alternate implementation (not tested, though.)
The scripts need the
nm utility; get it from Xcode or odcctools
update: it looks like joey hagedorn made a truetype version of the darwin console font!