immutable flag on files

locked files got you down? might be immutable. see “chflags”

uchg set the user immutable flag (owner or super-user only)

The chflags command is your friend.

Fonts in GLterm

GLTerm is a very nice Terminal replacement, the only one which runs mc flawlessly. Unfortunately, the choice of fonts is quite limited. To use custom fonts in GLTerm you need:

1. Installed X11 from Apple or through fink 2. The getbdf utility (click here to download)

Choose a font visible to X11 (the fontname should look like ‘-adobe-utopia-bold-i-normal-‘. These names may be found in the fonts.dir and fonts.alias files under /usr -> X11R6 -> lib -> X11 -> fonts). You may try ‘fixed’ or ‘lucidasanstypewriter-12’ aliases to get the default X console font or Lucida, as well.

Start X11, go to the xterm window. You can see if your font name is correct by executing /usr/xterm -fn [fontname]. If you see no error message and you like the font in the new xterm window, you may proceed. Execute getbdf -font [fontname] > [newfontname].bdf in xterm.

Note the redirection (>), getbdf outputs to stdout by default. Copy the resulting .bdf file to /Applications -> GLterm.app -> Contents -> fonts (if your GLterm is in /Applications), either in the console or through Control-Click and Show Package Contents in the Finder. Restart GLterm, go to Preferences -> Appearance, and your custom font should be available in the list.

[Editor’s note: I tested this hint, and it works as expected, although it’s a bit more complex than expected. The one thing that threw me at first is that there are subdirectories in the “fonts” folder, and it’s those subdirectories that hold the fonts.dir and fonts.alias files. To find all the files easily, just type:

% cd /usr/X11R6/lib/X11/fonts % find . -name “fonts.*”

This will list all the fonts.dir and fonts.alias files in the various subdirectories. When you’re looking in those files, the names of the font is quite long. For example, in the fonts.dir file in the “misc” subdirectory, a random font name is:

-misc-fixed-medium-r-normal–14-130-75-75-c-70-iso10646-1

You need to use that entire string as the name of your font in order for this to work. When you use the redirect, give it a nice short name!]

Screen Shot Format

Apple’s Cocoa Development mailing list archives contain an interesting snippet that explains how to change the default screenshot (command-shift-3 and -4) format from TIFF to JPEG, PICT or PNG. The original article can be seen here (read the dialog box for the username and password), but it’s basically a one-line terminal command:
defaults write NSGlobalDomain AppleScreenShotFormat imageFormat

Replace imageFormat with one of JPEG, TIFF, PNG, or PICT to change the format of the screenshot

Disable Specific Software Updates

found on Mac OS X Hints…

In the midst of playing around with the newly discovered Software Update log file (see the recent hint), I also found out how to remove those annoying notices that pop-up when you try to quit Software Update without installing all the updates. In my case, it’s the AirPort update on my desktop G4. It shows up every time, and when I quit the updater application, I get a warning dialog about “are you sure you want to do this even though you haven’t installed this update?”

Like a few others published this week, this tip is probably blatantly obvious to many people, but I’d never previously looked at the menubar in Software Update. If I had, I would have seen the Update -> Make Inactive option. If you simply highlight the package you’d like to ignore and then select this menu item, you’ll get a dialog box warning you that you won’t be able to update this package while its inactive. Click on Make Inactive and that’s the end of the warnings when you quit Software Update.

If you ever wish to update the inactive package, select Update -> Show Inactive Updates and then reactivate the package(s) you are wish to update.

Again, my apologies if this was obvious to everyone but me, but I had no idea you could ignore updates!

Welcome

Replacing the Manila site with a Movable Type site…doing it all by hand.

CALCULATING THE VALUE OF IT

CALCULATING THE VALUE OF IT

By Bob Lewis

Posted February 07, 2003 12:00 Pacific Time

“Imagination is the only weapon in the war against reality.” — Jules de Gautier

Gartner has achieved fame and fortune through the publicity it generates from regular publication of outrageous “TCO (total cost of ownership)” calculations. It’s time for Gartner to share the fame if not the fortune.
Continue reading “CALCULATING THE VALUE OF IT”

SCHEV – An Example Information Source

SCHEV – An Example Information Source

The State Council of Higher Education for Virginia (SCHEV) is the Commonwealth’s coordinating body for higher education. SCHEV was established by the Governor and General Assembly in 1956. Then as now, our mission, which is outlined in the Code of Virginia, is “to promote the development of an educationally and economically sound, vigorous, progressive, and coordinated system of higher education” in Virginia.

Future Information Environment

From John Wilson –

This could be a chance to put the “I” in CIO in a meaningful way. To do so, we need to address real Information issues, not just technology and transaction systems issues. These might include, in increasing order of complexity and scope:

Addressing the real overlaps on information providing among DAPS, UIS, PSOS, HR, FRS, etc. (essentially an expansion of the Sander memo idea to where there is duplication and confusion as distinguished from ignorance).

Addressing the real information needs of the management of the institution and what to do about them. DAPS began a series of interviews with deans and other administrators but it kind of got side-tracked by events.

Addressing the lack of a university sense of what is required to have an effective information environment for management, process improvement (e.g., determining the key factors in student success by discipline), etc.

Continue reading “Future Information Environment”

XML — Where Do We Go From Here?

XML — Where Do We Go From Here?

Jon Bosak – What XML cannot do is to magically solve the problem of data interoperability. XML just provides a framework within which interested groups can work out agreements about the vocabularies and data structures to be used in a given domain. The widespread adoption of XML has created a wonderful infrastructure of standardized tools and products to support the creation and implementation of such agreements, but deep down, the job of semantic definition requires the same grinding committee work that standards groups have been engaged in for more than a century.

Given that as a caveat, analysts, marketeers, and engineers talk about XML after 5 years.