eftychia: Me in kilt and poofy shirt, facing away, playing acoustic guitar behind head (Default)
posted by [personal profile] eftychia at 05:26am on 2009-11-06
Mark Danner:   I call this in the book the Athenian problem. Which is how do you have--
 
Bill Moyers:   Athenian meaning Athens of Greece, right?
 
Mark Danner:  

Exactly. How do you have a democratic empire, how do you have an imperial foreign policy built on a democracy polity. It's like some sort of strange mythical beast that's part lion, part dragon. You know at the bottom is a democracy, and then it's an imperial power around the world.

And the problem is that the things demanded by an empire, which is staying power, ruthlessness, the ability and the willingness to use its power around the world, it's something that democracies tend to be quite skeptical about. And this is a political factor that looms obviously very large in [Obama's] calculations.

-- from the PBS television program, Bill Moyers Journal, 2009-10-16

eftychia: Me in kilt and poofy shirt, facing away, playing acoustic guitar behind head (Default)

Uh, did somebody just buy me a gift subscription to Science News? A copy of the current issue just arrived in today's mail ... and I did recently mentioned (and a little less recently) mention having been a reader of it in the past.

If so, thank you. A lot. I've missed it. It's a bit thicker now than I remember.

I could probably get all the same news from the web nowadays, but someties it's just easier -- feels more relaxed and recreational -- to read stuff like that on paper. And by just turning pages instead of scrolling up and down and then deciding which links to click next. (I love the web, but I'm glad we still have dead-trees publications as well.)


Poll #1630 Command-Line Interfaces
Open to: Registered Users, detailed results viewable to: All, participants: 4


For folks who use command-line tools: if a command has both a "display version number" option and a "more verbose output" option, which of these is more intuitive (and/or less likely to be annoying)?

View Answers

-v = version; -V = verbose
1 (25.0%)

-V = version; -v = verbose
3 (75.0%)

Doesn't matter; either is good
0 (0.0%)

Ew, both suck; use getopt_long() and spell it out
0 (0.0%)

Er, what? Ooh, clicky!
0 (0.0%)

People still bother with command-line interfaces? (warning: I may mock you if you click this)
0 (0.0%)

If some combinations of command-line arguments might produce not-completely-obvious results, but those combinations are potentially useful so they should merely be warned about rather than disallowed, which of these seems more useful?

View Answers

-w to turn on warnings for the least obvious dangers; -W to add warnings just for folks not yet acclimated to the joys of Unixy deliciousness
1 (25.0%)

-w to turn on wanrnings of all possibly confusing combinations detected; -W to warn only about severe gotchas
0 (0.0%)

All warnings on by default, with "did you really mean that?" prompts, unless the user turns them off with an "I know what I'm doing" option
1 (25.0%)

Only warn about data-destroying potential-gaffes, and treat mere potential-inconveniences as "they probably meant to do that
1 (25.0%)

I'm not sure ... but ooh, clicky!
1 (25.0%)

Let's say you have a bunch of files in a directory (say, "arbeau.abc", "machaut.abc", and "frtrad.abc" in a directory named "french") and some or all are hard-links to (not copies of) entries in another directory (perhaps "french/arbeau.abc" also appears as "dance/arbeau.abc" and "french/machaut.abc" is the same file as "songs/machaut.abc") ... and you decide to modify all the files in that directory ("french") in a batch, using a tool that replaces files with edited versions and optionally saves backups (named *.bak or *~). Which of these sounds like the most correct behaviour (most likely to be desired, least likely to induce cursing)?

View Answers

Copy each file to its backup-name, then overwrite the original with the edited version (so dance/arbeau.abc is still linked to french/arbeau.abc and thus reflects the changes). This is what links are for.
2 (50.0%)

Heck, not only that, but it should try to ensure that symbolic links behave as much like hard links as possible in cases like this.
1 (25.0%)

Rename each file to its backup-name, then create a new file with the original name for the edited version (dance/arbeau.abc is now linked to french/arbeau.bak, and french.abc is a completely new file with no other links to it).
0 (0.0%)

Make it yet another command-line option, to choose between copy/overwrite and rename/create, and/or prompt the user to choose.
0 (0.0%)

It doesn't matter, because the only users likely to be using links that way in the first place are going to try it out with a couple of dummy files first to find out which way you're doing it.
1 (25.0%)

Wait, what's a "hard link"? Is that like an alias?[*]
0 (0.0%)

[*] Not really, but it's related. A symbolic link is like an alias. A hard link is where a single file on disk has two names -- an occasionally useful error in an MS-DOS filesystem, an established, intentional feature in Unix -- and neither filename is any more or less "real" than the other. I don't know whether recent versions of Windows have added this feature or not, but in older versions you could force it to happen, at the risk of CHKDSK "repairing" it later.

I'm not sure whether I'll get back to the project that sparked the questions in that poll (see below), but the responses will pertain to some future project too, I'm sure.


Despite the welcome arrival of a copy of Science News, it's been a discouraging week. The Mac won't boot, and it died just as I was fine-tuning the interface for a program that was nearly ready to share, beautifully comment, with a man-page and everything ... that I had not yet copied elsewhere to try compiling on a different OS, or to post yet. There was a lot else not backed up, but most of that will merely annoy and inconvenience me; this bit is the "somebody kicked over my masterpiece sand castle just before I finished it" kick in the gut. (Hmm. Much of what was backed up was backed up to DVD. I'm not sure yet whether any of my other computers can handle that. Experiments to put on my to-do list.)

Couple that with the main Linux workstation -- the bedroom machine -- which I hadn't been using much since I was given the Mac, no longer talking to its monitor, and I've been getting by with an itty-bitty Windows XP machine with a tiny screen and a so-so X server on it for the past few days, and it's been really putting a dent in my enthusiasm. So, in the immortal word of Charlie Brown: AAAUUUUUUGH!

(The bedroom Linux machine shows the POST messages on the monitor -- which is itself having major problems, but I have an even larger monitor to use ifwhen I ever feel capable of getting it up the stairs -- but at some point the screen goes blank and nothing I do to the keyboard or mouse will light it up again. I can SSH to it, and throw X apps to the itty bitty XP screen (a VAIO that only works when plugged into the wall), but I don't get the benefit of the decent-sized screen or the larger keyboard.)

The small screen is fine for web surfing and email; not so good for editing source in one window, editing docs in another, looking stuff up in a third, and viewing output in a fourth, or comparing two PS/PDF pages side by side. Or maybe I'm just spoiled from having a Mac to use for the past several months.

I haven't had the heart to start reconstructing a week of coding from scratch (get a filter working: a couple hours; add enough comments that I won't be embarrassed if anybody else sees it, usefully robust command-line arguments and options, and somewhat reasonable user documentation: a week) -- and I'm still clinging to the faint hope that the files can be recovered -- so I tried to dive back into composing and arranging, and am finding the tiny screen even more annoying for that than for programming. Or maybe I'm just too acutely frustrated and discouraged to cope with even small inconveniences right now. Maybe I'll feel differently about this in a month. But right now, it sucks.


The plan is to head down to Virginia to see whether [info] justgus37, who has more Mac tools, more Mac experience, and OS install media, has any more success ressurecting the Mac than I've had. Wednesday I wasn't feeling well enough to drive that far; last night I got a late start and then ran into some kind of mess that turned I95 and the Beltway into obstacles instead of arteries, and turned back after it became clear I wouldn't get there at any sane hour. So: trying again tonight, if I'm up to it, which at the moment is iffy but I've still got an hour or so to decide. (By the time I got home again last night, it hurt to steer, and I've got power steering. But on the plus side, I got more sleep this morning than the past couple of days, so let's see what my body decides to do with that.)

I want my code back. I want my files back. I want my tools back. This business of knowing I need more backup media and a big disk for a live backup, but not being able to afford either ... well it's starting to wear me down.

Links

January

SunMonTueWedThuFriSat
1 2 3 4 5 6 7
8 9 10 11 12 13 14
15 16 17 18 19 20 21
22 23 24
 
25
 
26
 
27
 
28
 
29
 
30
 
31