| Fellow Ramblers 20 most recent entries |
"My wardrobe is threefold: Things I wear during sex, Things I wear to have more sex and most importantly, 'I don't give a shit.'" -- Twitter user VaginaDrum, 2009-10-26 post a comment
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.) [Note: primary copy of this poll is at Dreamwidth -- that's where the copies of this entry on sites where I can't post polls will link to.] Poll #4558 Command-Line InterfacesOpen to: All, results viewable to: All 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 -V = version; -v = verbose Doesn't matter; either is good Ew, both suck; use getopt_long() and spell it out Er, what? Ooh, clicky! People still bother with command-line interfaces?
(warning: I may mock you if you click this) 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 -w to turn on wanrnings of all possibly confusing
combinations detected; -W to warn only about severe
gotchas 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 Only warn about data-destroying potential-gaffes,
and treat mere potential-inconveniences as "they
probably meant to do that I'm not sure ... but ooh, clicky! 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. 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. 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). Make it yet another command-line option, to choose between copy/overwrite and rename/create, and/or prompt the user to choose. 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. Wait, what's a "hard link"? Is that like an alias?[*] [*] 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
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. post a comment
Tweets copied by twittinesis.com post a comment
(1914-1991) Happy birthday, Mom. post a comment
( and this is what I think about ... ) post a comment
-- from the PBS television program, Bill Moyers Journal, 2009-10-16 post a comment
Simba (l) and Lucy (r) enjoy their new digs. We couldn't coax Lucy out of the box last night, so we just made sure there was food, water, sand box and Simba in the enclosure with her. We left the door slightly open so our crew could sniff and be sniffed but no fighting. Made for a noisy night, but not too bad. Gave them each a box of their own, and a scratch post.
And the figurehead has a good question: So, internets, if you were sailing from Mumbai to Gdansk what would be your route: I agree. I think we should navigate by the coolest route. But what does the navigator say? What we did in Mumbai
11 comments | post a comment
Tweets copied by twittinesis.com post a comment
"With the impending release of the new movie, The Men Who Stare at Goats on November 6, 2009, questions about the paranormal will surely be cropping up in popular culture again."
"I do not like this word 'bomb'. It is not a bomb; it is a device which is exploding." -- French ambassador Jacques Le Blanc (sometime in 1995?) [My ISP where the QotD script runs was installing a new file server last night/this morning ... I'm guessing that has something to do with the script not being executed this morning, since its scheduled run was in the middle of the maintenance window.] post a comment
They have been rescued from the jerk who thought they were decorations, and are being comforted by Alison. She said they are reasonably good shape, but shy, and if anyone knows now Bengals are, that is not normal. I'm sure with enough patience and care, they will return to their usual rambunctious selves.
When I ordered Season 1 of Sanctuary, I decided to enter the contest that EzyDVD was having. The prize was a signed by Amanda Tapping copy of Season 1. We had to describe in 25 words or less, what creature would you like to see on Sanctuary and why.
Tweets copied by twittinesis.com post a comment
Today we have two movies about nosy reporters getting up to their elbows in other people's business for the sake of the public good, and I have some criticisms of both of them. Call Northside 777 (1948) ( Pieces never make the wrong picture. Maybe you're looking at them from the wrong angle. ) All the President's Men (1976) ( think of it as the bicentennial picture ) post a comment |
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||