Slashdot Mirror

theodp writes "In 1919, Nora Bayes sang, "How ya gonna keep 'em down on the farm after they've seen Paree?" In 2013, discussing User Culture Versus Programmer Culture, CS Prof Philip Guo poses a similar question: 'How ya gonna get 'em down on UNIX after they've seen Spotify?' Convincing students from user culture to toss aside decades of advances in graphical user interfaces for a UNIX command line is a tough sell, Guo notes, and one that's made even more difficult when the instructors feel the advantages are self-evident. 'Just waving their arms and shouting "because, because UNIX!!!" isn't going to cut it,' he advises. Guo's tips for success? 'You need to gently introduce students to why these tools will eventually make them more productive in the long run,' Guo suggests, 'even though there is a steep learning curve at the outset. Start slow, be supportive along the way, and don't disparage the GUI-based tools that they are accustomed to using, no matter how limited you think those tools are. Bridge the two cultures.'" Required reading.

chrb writes "Linux Journal points out PLAYterm, an interesting project that offers up recordings of Linux command line sessions, with the aim of helping viewers to improve their skills by watching gurus at work." And there's no bad excuse to link to Neal Stephenson's excellent (and free-to-download in delicious zipped-text form) In the Beginning was the Command Line.

Max Tardiveau writes "I just finished reading Neal Stephenson's latest novel, Anathem. I was awaiting it with some anticipation because I absolutely loved Stephenson's best-known novels: Snow Crash, The Diamond Age, and Cryptonomicon. One of Stephenson's non-fiction pieces, called In the beginning was the command line, simply wowed me when I read it. The man can write. A few years ago, I got really excited when I heard that he was writing a whole cycle of novels (the Baroque cycle). But I read the first book of the cycle — Quicksilver — and I was somewhat disappointed, so I skipped the rest of the cycle. I realize that many people enjoyed these novels, but I was hoping that Stephenson would get back his old style and inspiration. So, when Anathem was announced, I was full of anticipation — was this going to be the one? Would he find his mark again?" Keep reading for Max's impressions of Anathem Anathem author Neal Stephenson pages 935 publisher HarperCollins rating 6 reviewer Max Tardiveau ISBN 9780061474095 summary Action and philosophical exploration in an Earth-like future The first impression of this book is its heft---at 935 pages in the hardback edition, you'll need strong arms, or a good support, just to read the thing. But otherwise, this is a sharply printed, well-bound book. The official retail price is $30, but you can find it for around $24, less if you buy it used.

Anathem is set on a fictional planet called Arbre, which is very similar to Earth, in a fairly distant future. Much has happened, as we discover during the course of the story. World wars, revolutions, climate change, etc... During all these tribulations, religious orders have provided a certain amount of continuity, and have pursued theoretical scientific research. They still live like monks and nuns, even though there are occasional glimpses of highly advanced technology (materials, genetics, etc...).

In a monastery, ruled by an ancient Discipline, our hero is a young monk who is inquisitive, smart but not brilliant, and brave but not foolhardy. We see most of the action through his eyes.

Not much happens in the first 100 pages or so, which can be a bit trying, but soon we learn that mysterious events are in progress, and the narrative picks up the pace after that. I can't say much more without spoilers.

As usual with Stephenson, there are many neat ideas, and a few mind-twisters. The writing is usually clear, the action can be stimulating, the characters can be engaging. And yet...

It's not that Anathem isn't interesting. It's just that it feels ... self-indulgent. It's a 935-page novel that should be 600 pages or less. Perhaps Stephenson's fame and success make it difficult for editors to stand up to him. That would be his loss (and ours). A good editing job would have turned a good novel into one that is worthy of him.

Why do I say that?

First, the story is replete with made-up words that add very little to the story, the atmosphere, the narration, or anything at all. They just stand in the way. I'm not opposed to a judicious use of this device, but here it feels gratuitous and pointless and, yes, at times irritating.

I know it's not supposed to be Earth, but at least half of this gobbledygook could have been skipped without any detrimental effect. I'm afraid I have to invoke Munroe's Law, which states: "The probability of a book being good is inversely proportional to the number of made-up words it contains". In fact, XKCD had a strip about this specifically aimed at Anathem.

There is a lot of dialog and action that adds little or nothing to the narrative. One feels, at times, like Stephenson is filling time. This is where a good editor should step in and tighten things up. One senses that the entire book was published as delivered by the author, with no critical paring, no condensing. I'm sure I'm wrong about that, but the feeling is there nonetheless.

We meet a very large cast of characters, many of whom seem unnecessary. Names appear and disappear, and the reader is left to ponder why they were introduced at all. Is there some ulterior motive? Will they have some sort of meaning later in the book? But alas, most don't, and we feel like we have invested time and emotion in vain.

There are also a lot of uncompleted story lines and plot holes. Perhaps the novel is simply too ambitious, and tries to broach too many topics. Time and time again, Stephenson introduces an interesting concept, or an intriguing subplot, only to drop it without any follow-up. This is most unsatisfying.

This is a surprise, because I am under the impression that Stephenson's audience is in large part made of people like me — somewhat geeky, interested in science, and therefore prone to paying close attention to details of the story. In this respect, this book simply fails. The reader is left with so many open questions, so many unfinished lines of inquiry, that the whole thing feels unfinished, even rushed. The ending is bland and appallingly predictable, worthy of a Bruce Willis action movie--harsh words, I know, but I am not using them lightly.

I was expecting more intellectual stimulation, a significantly faster pace, and more storytelling rigor from Stephenson, and I have to admit to being disappointed. The book is certainly not without redeeming qualities, I was just expecting quite a bit more.

I would not recommend this book as an introduction to Stephenson. If you're a real fan, you'll probably read it no matter what, but otherwise you can safely skip it. If you've never read anything by Stephenson, then you owe it to yourself to read the three novels I mentioned at the beginning of this article. They are truly excellent. Anathem, sadly, is not cut of the same cloth.

You can purchase Anathem from amazon.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

sympleko (Matthew Leingang) writes "In Neal Stephenson's manifesto In the Beginning was the Command Line , he writes about his favorite command-line utility: wc. As simple as can be, wc counts characters, words, and lines in a file. There's no GUI analogue, perhaps because anybody tempted to make one would add too many "features" that cluttered its ease of use. Think: do you know how to count the words in a Word file? BBEdit is a little easier, if you know the button to click." Read on for Leingang's review of Learning Unix for Mac OS X Panther, which seeks to reconcile the conception of user friendliness in OS X's Aqua with the sometimes-denigrated command line. Learning Unix for Mac OS X Panther author Dave Taylor and Brian Jepson pages 168 publisher O'Reilly rating 8/10 reviewer Matthew Leingang ISBN 0596006179 summary Nice and Easy

You can do a tremendous amount of stuff in Mac OS X Panther without ever touching the command line. This includes editing files, transferring them to remote locations, running a web server, and writing programs. Legend has it that some Apple developers wanted to ship OS X without a command-line application because it's anathema to the Mac "experience." But as Unix geeks will tell you, there are tasks which are much better suited to the command line. Routine, repeated, and automated tasks are some, as well as quick-and-easy access to files and directories.

This book is for the skilled Mac user who would like to know a little more about the operating system behind the scenes. There's also information about the Mac's brand of Unix, so someone familiar with Unix but new to the Mac will also find stuff to learn. For those confident in their Mac and Unix skills, however, there's not much new in the book's 168 pages. That's not to say it's a bad book; I found it quite enjoyable to read, and it's a good title to keep in mind to recommend to a Unix novice.

The book begins with an introduction to Terminal.app, the Mac's Unix terminal program. From the very basic (how to find with the Finder) to the fun (how to change the text and background colors) to the useful (how to save terminal sessions into double-clickable .term files), there's much that Terminal has to offer. There's even the cryptic echo '^[]2;My-Window-Title^G' command to change the title of Terminal's window.

The authors then introduce a few simple commands like date and who, and show how to manipulate the terminal's prompt. There's also alias which creates command shortcuts. For instance, if you always run ls with the -F flag, a command alias ls "ls -F" will save you some typing.

Each chapter has two sections which stand out. The "Practice" section gives a list of exercises to try, and the "Problem Checklist" is there to diagnose and fix unexpected behavior.

It's important (especially for those used to other OSes) to understand that in Unix, everything is a file, and all files are organized in the filesystem. This includes plain files, which might be Word documents or system logs; directories, which break up the filesystem into a tree; links, which allow file reuse with different names; devices, drives, etc. All these building blocks of the operating system are discussed. There are also a few pages on vi (which I found quite useful as my vi knowledge up to that point consisted of :q!.) and pico.

Printing on Mac OS X is much like printing on any Unix operating system; you can use pr to format text for line printing, enscript to format for PostScript printing, and lpr to actually queue a printer job. The addition that the Mac provides is a CLI to AppleTalk printers. You can use at_cho_prn to choose an AppleTalk printer and atprint to print to one.

One of Unix's biggest features is its ability to put together small programs to do many different tasks. To count how many files under your home directory are named foo, you can do find ~ -type f -name "foo" | wc -l. By breaking down a problem into components, you only need one-counting program, one file-finding program, etc. The book has a good chapter on this input/output redirection, and how to use those magic top-row characters |, >, >>, and <. Grep (and some light regular expressions) and sort are mentioned as tools for examining text. I thought sed would make a nice addition to this chapter, but perhaps it would lengthen the book too much.

Another advantage of Unix is its true multitasking. What may surprise newcomers to the command-line is that it is possible to run many jobs at once with a single interface. By running commands in the background, one can start large jobs and do other tasks while waiting. In the chapter on multitasking, the & modifier is covered, along with fg, bg, and kill to manipulate processes, and ps and top to report on them.

The command-line interface is lightweight enough that it can easily be extended by a network. This means it's easy (in fact, commonplace) to control a computer different from the one in front of which you're sitting. The authors cover the remote-shell commands ssh and its non-secure cousins, as well as other tools for accessing the internet such as ftp and curl.

The book closes with an introduction to the wealth of open-source software available for Macintosh, now that Macs run a functional Unix. The graphical Unix applications require an X server, which is easy to download and install. The authors show how to install Fink, the Macintosh open-source package manager, and a few big applications like OpenOffice.org and The Gimp.

The last chapter is both a resource list and suggestions for further directions. Those who learn a lot from this book may be interested in picking up shell programming or a scripting language such as Perl.

As I said at the beginning, the book is basic and well-written. Even if you feel it's beneath you, keep the title in mind when a newbie asks what the command-line is all about.

Matthew Leingang is a Preceptor in Mathematics at Harvard University. A funny sentence in the third person escapes him at the moment. You can purchase Learning Unix for Mac OS X Panther from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

dioscaido writes "Users of the Google Desktop Search software beware -- it indexes your files across all users on your PC, bypassing user protections. The Google cache feature allows all users to browse the contents of messages and files it has indexed, irrespective of who is logged in. 'This is not a bug, rather a feature,' says Marissa Mayer, Google's director of consumer Web products. 'Google Desktop Search is not intended to be used on computers that are shared with more than one person.'" Reminds me of a Neal Stephenson essay: "The Hole Hawg is dangerous because it does exactly what you tell it to. It is not bound by the physical limitations that are inherent in a cheap drill, and neither is it limited by safety interlocks that might be built into a homeowner's product by a liability-conscious manufacturer. The danger lies not in the machine itself but in the user's failure to envision the full consequences of the instructions he gives to it."

Our latest Slashdot interview victim... err... guest... is Neal Stephenson, author of (among others) Snow Crash, CRYPTONOMICON, the much-discussed essay, In the Beginning was the Command Line, and more recently a series of books he calls The Baroque Cycle. (Last month Slashdot reviewed the series' third volume, The System of the World.) Now you can ask Neal whatever you want. As usual, we'll send him 10 -12 of the highest-moderated questions and post his answers verbatim when we get them back.

Our latest Slashdot interview victim... err... guest... is Neal Stephenson, author of (among others) Snow Crash, CRYPTONOMICON, the much-discussed essay, In the Beginning was the Command Line, and more recently a series of books he calls The Baroque Cycle. (Last month Slashdot reviewed the series' third volume, The System of the World.) Now you can ask Neal whatever you want. As usual, we'll send him 10 -12 of the highest-moderated questions and post his answers verbatim when we get them back.

Two strongly contrary claims describe the usability of Unix and Unix-like operating systems. Roughly, these claims go like this: 1) "Unix is easy! With a few simple commands you can navigate the filesystem and manipulate text; for the rest, just read the fine manual." That's the viewpoint (painting with a broad brush) of technically literate technojunkies. 2) "Unix is a pain. Cryptic commands, confusing explanations -- when I can get them -- from my smug cousin Jim. And where is this so-called manual?" That's the viewpoint (same broad brush) of a lot of people who -- let's say -- aren't the ones rushing to upgrade their heatsink and overclock their RAM, but have given things Unixy a spin. Linux for Dummies has been around long enough to reach its recently published 5th edition (written by Dee-Ann LeBlanc); it aims to bridge the 'Way too Hard!' and 'All Perfectly Easy' schools of thought. Read on for my review of the book. Linux for Dummies, 5th Edition author Dee-Ann LeBlanc pages 382 publisher Wiley rating 8 reviewer timothy ISBN 0764543105 summary The large-print onslaught on Linux anxiety continues, with lucid explanations and examples for the non-guru.

Not everyone can Read The Fine Manual Wiley's "For Dummies" series tends to provoke polarized reactions, so here's fair warning: I love them more than I loathe them -- partly out of contrarianism, partly because I often fall well within their target demographic. If the folksy, self-deprecating tone of these books infuriates you as it does many people, most likely it's because you aren't part of the target audience. No one likes being talked down to. On the other hand, for many people who might otherwise be interested in switching to Linux (or at least playing with it more), being told to look at man pages is like being told to drive up a brick wall, and books like Linux for Dummies are a welcome resource both to learn from and to point out to others. (For more technically oriented novices and intermediate users, I might rather point out Jon Lasser's Think Unix! )

A series of bracketed command-line options (followed by terse explanations of what each one does) works perfectly, to those familiar enough to use them. Man pages are a great memory aid, reminder, and basis for experimentation ("Hmm, can I combine the -a and -v switches?"). What man pages aren't is consistently friendly and approachable; this book is. This is not a knock on man pages: the thing is, they're written by and for "computer people," which is not the same as everyone who wants to use a computer. Not everyone is a power-user, or wants to be, and on areas outside their usual domains, even power users can sometimes use a bit more hand-holding.

Promises, promises Linux for Dummies' back cover says it will teach the reader how to work with popular Linux distributions (specifically, Fedora, SUSE and Mandrake), choose an ISP and configure dialup access, understand bash syntax, install and use OpenOffice.org, and manage the Linux file system. It does all of these things, to a reasonable depth, but don't expect a heavy tutorial on any one of them: the whole point is naming and defusing common newbie problems. A DVD included with the book contains Red Hat's Fedora Core 1 and source code, making it a reasonable way to obtain that distro as well.

LeBlanc is a good instructor; since she does computer training professionally, it's not surprising this book is organized well for self-directed learning, albeit at a pace that readers installing Gentoo on obscure hardware would likely find boring -- Chapter 6, 82 pages in, is titled "Dip in those toes." To be fair, by that point the book has zipped right through readying a system for and then installing a Linux distribution, and booting up for the first time. Not bad, really.

The early chapters leading up to that toe-dipping fulfill parts of the back cover's promises, by going through a graphical Fedora installation step-by-step (showing the user how to fill in each blank and go on to the next stage), then adding in the next chapter Mandrake- and SUSE-specific differences, emphasizing the similarities more than the idiosyncrasies.

The book's later chapters cover connecting to the Internet (via ethernet or modem), using a number of commonly included programs for email, web-browsing, word-processing and other workaday tasks, manipulating several types of files (for plaintext, this book leans understandably toward vi over emacs, but where are pine or joe?), navigating and lightly tweaking both GNOME and KDE, playing music and video files, and securing and updating one's system. Since there's clearly no way one book can address all of these things to the satisfaction of an advanced reader in 360 pages of text, don't look at the book that way: instead, the text provides a chatty overview of big issues (a few hundred words on why to avoid unnecessarily running as root, say), links to websites around the net for longer explanations, and skips completely religious wars about text editors, licenses, and proper window management.

When it comes to applications, this book is oriented toward desktop use; Apache doesn't even make the index. Chapters 7, 8 and 9 cover connecting to and using the Internet. Chapter 7 is all about the technical side of this -- setting up a working connection (with a friendly, necessary warning that not all modems, and not all ISPs, are equally adept at handling anything other than Windows), assigning IP numbers (or using DHCP) and using tools like traceroute to verify that things are working right. 8 and 9 cover various Internet tools, leaning toward Mozilla and Evolution for web-browsing and email, respectively. (Konqueror gets a one-line mention as a web-browser here, which is a bit short considering its strong KDE integration and dual life as a file browser.)

Working with file permissions and directories (both with and without a GUI) occupies Chapter 10, while 11 goes strictly into working from the command line. It's no In the Beginning Was the Command Line , but it does an admirable job of introducing the most necessary command line tools without straying into esoterica: things like ls, cd, pwd, man, clear and kill, in other words, the ones without which it would be hard to get around a system.

Chapter 14 is solely about using OpenOffice.org; it covers the drawing, presentation, spreadsheet, math and word-processing modules well enough to get started with each one. While there's a lot to be said for Abiword (clean, quick) and KOffice (frame orientation is very useful), OO.org is probably the most sensible office software to focus on in a book aimed at a non-expert audience. (And for the moment, anyhow, I find it the most compatible with Microsoft's office suite, which lends it considerable power in the form of network effects.) The chapter provided does as much justice to the suite, with lucid first steps outlined for common tasks like writing a text document and doing simple calculations with the Math module, as roughly 30 pages can be expected to.

By contrast, Chapter 18, devoted to securing one's system by way of passwords, network management and use of SSH, is only 13 pages long. (For the moment, that may be enough for this book, but I suspect by the next edition it won't be.) Still, quick but workable explanations of connecting from the Linux desktop to remote machines via ssh, and connecting Windows clients via ssh to your new Linux box, at least close some of the most obvious security holes, as does the advice to close down unneeded ports and daemons.

Screenshots throughout (cleanly printed greyscale) are well-chosen; this is one of the improvements that this edition has over the 1st edition I gave to my father a few years ago. Most of the screenshots reflect the author's choice of GUI programs over terminals, including graphical utilities for things like setting security options. By choosing Fedora's, LeBlanc sidesteps arguments about KDE vs. GNOME aesthetics -- since the images use the default Bluecurve theme (which looks just about identical under both of the most common windowing environments), I'm not even sure which environment was used to create most of them.

Two appendices close the book: the shorter (second) one lists the contents of the included DVD and system requirements; the longer one which precedes it provides a listing of common commands from alias to xxd (about which more below).

Along for the ride The included DVD is a compromise between audience (self-diagnosed computer dummies) and practicality (fitting six CDs' worth of Fedora into a book jacket with minimal fuss). The machine I set aside to play with Fedora doesn't have a DVD drive, so I used a standard download from Red Hat to play along with the examples. (I didn't bump into any contradictions between screen and page, but that's Situation Normal, since I used the same distribution.)

(Aside: though for various reasons Fedora does make a wise choice in a book like this, I hope future editions, or competing books in the non-expert-user niche, will use Live CDs such as Knoppix instead. That would open them up to users who want to mess around with Linux more before crossing their fingers and wiping a hard drive.)

There's one more freebie -- a single-sheet tear-out reference sheet listing common commands and a few of their options, including a list of the right commands to mount CDs under the Red Hat and Mandrake (identical) and SUSE (just slightly different enough to confuse). It only has to get used a few times to be worthwhile.

The gloss ceiling The same brief-and-breezy approach that makes the book worthwhile for some purposes (like not abandoning the audience) sometimes just makes it confusing; in several places the compromises necessary in boiling down a complex subject for a beginner audience made me itch to pencil in suggestions.

A few more pages worth of one-line summaries would have made the Appendix A, (the one on common Linux commands), far more valuable. As it is, LeBlanc lists a number of general categories (Printing, System Control, Communication, etc), summaries each category, and lists several built-in commands relevant to each.

Under the heading of 'Communication,' for example, she points out that sysadmins find the listed utilities "useful for providing information about users and communicating with them," then provides a handful of commands: finger, wall, write, and who. And while the section starts out with the advice to look up each command's man page if curious, this section strikes me as filler in its current configuration -- it could be struck to make more room discussing Live CDs, or vector drawing apps, or Mozilla's mail client as an alternative to Evolution.

Many applications are given short shrift simply because an adequate treatment of more window managers, graphics programs (two and a half pages dedicated to the GIMP is more than most programs get), music players and all the rest would have meant a far thicker book. I wish a few pages had been spared for at least capsule descriptions of pico and nano (my favorite text editors for Dummies -- err, "future experts" -- including me), Xchat, and gaim. Also on the wishlist: Wiley would commission LeBlanc to write a similar book aimed squarely at schools, in which applications like Scribus and some of the many Edutainment packages could be emphasized instead.

Since I've been dealing (arguing) with a wireless network in the time I've had this book, there's one other thing I wish this text didn't skip, which is a tutorial on connecting Linux systems via 802.11. The typical distro's autodetection abilities and set-up tools have improved to the point where this would be no more complicated to explain (and probably more useful) than the provided explanation of connecting through a modem.

The Upshot for Dummies Linux for Dummies isn't for everyone; it leaves out far more than it includes, leading to what would for advanced users be egregious omissions. However, for new, intermediate and merely rusty users, this book easily justifies its $30 pricetag -- as a confidence boost to the absolute beginner, and a refresher to everyone else. Linux, for various reasons of various worth, can certainly be cryptic (the same can be said of Windows and probably every OS under the sun), but a little bit of executive summarizing can inspire a would-be user, so he can actually enjoy and understand using it. Kudos to LeBlanc for providing that kind of catalyst.

You can purchase Linux for Dummies, 5th Edition from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, carefully read the book review guidelines, then visit the submission page.

Christina Schulman writes " Quicksilver, Volume One of the Baroque Cycle, is the new doorstop from Neal Stephenson, author of Snow Crash and Cryptonomicon . It's set in late-seventeenth-century Europe, and while it has a few links to Cryptonomicon, you don't need to read Cryptonomicon first. A bit of background reading about the English Civil War wouldn't hurt, though." Schulman's review (below) is enough to whet the appetite, without major spoilers -- perfect for those of us who've been waiting since the end of Cryptonomicon for another 900 pages. Quicksilver: Volume One of the Baroque Cycle author Neal Stephenson pages 944 publisher William Morrow rating 9 reviewer Christina Schulman ISBN 0380977427 summary More than you ever wanted to know about the English Restoration and the invention of calculus, with lots of explosions, syphilis, and piracy thrown in for good measure.

First, let's make it clear that Quicksilver is not science fiction. It's historical fiction, occasionally about science, for people who like science fiction, i.e. geeks. It has math, optics, and vivisection, but no computers, no code, and no high-speed pizza delivery.

This is also not a book that gets anywhere quickly. It's 900-plus pages, and it's not padded so much as it is fractal. Stephenson wanders down side tracks, stages elaborate adventures and morality plays, explores philosophical issues and geometric proofs, assembles obscure puns, and drags in all manner of famous people and events, purely for his own amusement. Either you sit back and enjoy the game, or you hurl the book (with effort) at the wall somewhere in the first few hundred pages.

Daniel Waterhouse is a seventeenth-century geek; his father's a prominent associate of Oliver Cromwell, but Daniel's more interested in Natural Philosophy than in decapitating kings and Catholics. At Cambridge, he befriends Isaac Newton; later he becomes sort of a grad student and chief bottle-washer to the Royal Society. He starts out as naive observer of London politics, but over a few decades, gravitates into the intrigues of both the Court and the European intelligentsia. Just as Lawrence Waterhouse befriended Turing in Cryptonomicon, Daniel Waterhouse orbits Newton and Leibniz. It seems to be the fate of Waterhouse men to be brilliant thinkers eclipsed by the geniuses of their age.

Jack Shaftoe is a legend in his own time, a thief and mercenary who propels himself around Europe on sheer balls and avarice. He bumbles into and out of ridiculous scrapes, including an ostrich-chase at the Siege of Vienna that results in his rescue of the slave-girl Eliza from a Turkish harem. Eliza's business savvy draws the pair back across Europe to Amsterdam, where Eliza becomes entwined in both the Dutch stock exchange and the court of Versailles.

Cryptonomicon readers will remember the improbably long-lived Enoch Root, who shows up occasionally to nudge the plot along. Most of the story takes place between 1655 and 1689, but it opens with Enoch in Massachusetts in 1713, interrupting Daniel's efforts to found MIT by presenting him with a summons from England. Daniel spends the next several weeks being chased around Plymouth Bay by the pirate Blackbeard, only to have his plot thread left dangling with no apologies. Either it will be picked up in the sequel, or Stephenson is attaining a new degree of sadism.

Where Cryptonomicon was about secrecy and deception, Quicksilver is about revealing the hidden and the unknown, and the free dispersal of ideas and money. Stephenson uses quicksilver as an unsubtle symbol of the scientific discovery that was beginning to percolate through the known world. He highlights the dichotomy between the religious viewpoint, of a world that began in perfect knowledge and order and has steadily decayed since the Fall, and the scientific viewpoint, of a chaotic world that is slowly being brought into order and the reach of understanding. Much of this understanding was accomplished through the efforts and correspondence of the Royal Society, which operated in a state of excitement, enthusiasm, and confidence that they would decipher the mechanisms of nature: an attitude not unlike that of the dot-com startup era, but fueled more by wonder and less by naked greed.

Lesser writers dump blocks of expository prose into the narrative; Stephenson shamelessly shovels it into his dialogue. As a result, much of the dialogue is stilted, and the banter is painfully odd. You get used to it. Some bits are more blatant than others, such as a dialogue between Waterhouse and Newton and a Jewish prism-merchant, in which Stephenson trots out a brief overview of European coinage of the time, while cycling through a catalogue of synonyms for "Jew."

So, is Quicksilver worth the effort? On the one hand, it's an insightful look at both the Scientific Revolution and the Glorious Revolution. On the other hand, it's got plague, pirates, astronomy, sex, explosions, daring rescues, religious strife, and the profound effect on European history of stockbrokers and syphilis. It's a terrific book, but don't expect it to resemble Stephenson's prior books in anything but ambition and length.

You can purchase Quicksilver from bn.com -- the official release date is September 23rd. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

PerlDiver writes: "Perl for Web Site Management by John Callender is for web professionals -- designers, editors, HTML jockeys -- who have never programmed before, but who now find themselves with the need to create their own site-management tools, automated web clients, and web-based applications. The title is an understatement; the book covers not just Perl programming but the bulk of what a novice needs to learn to function in a UNIX environment, from pwd and man to installing software packages from source tarballs. If you or anyone you know wants to cross the chasm from 'content' to 'code,' get this book." Read on for the rest of his review. Perl for Web Site Management author John Callender pages 528 publisher O'Reilly and Associates rating 8 reviewer perldiver ISBN 1565926471 summary Superb introduction to Perl for "accidental programmers"

In his preface, Callender describes his own transition from a writer and editor to the kind of one-man-band that, back in the '90's, we called a "webmaster". He characterizes himself and others in the same boat as "accidental programmers", and justly praises Larry Wall for creating a programming language that enables such novice coders to do useful things right away. "Like natural languages, one of the ways in which Perl makes easy things easy is that it is designed to let you get by using only a small subset of the language. As Larry puts it, Perl lets you talk baby talk, and in Perl such baby talk is officially okay."

For non-programmers, this is a better Learning Perl than Learning Perl. The latter title, by Schwartz and Phoenix, is explicitly intended for established programmers seeking to add Perl to their existing tool belt of languages. Perl for Web Site Management is for the folks Apple used to call "the rest of us". Callender assumes no knowledge on the part of his reader beyond some familiarity with HTML and the web; this starting-from-zero approach makes the book maximally inclusive, while his ability to convey a lot in a small space brings the newbies a long way in the space of a couple chapters. He provides thorough redirection to the standard sources of Perl and Internet lore (the perl* man pages, the standard Perl programming texts, and others).

Virgin programmers, when they're through with Perl for Web Site Management, will find themselves able to make effective use of Perl programs to automate a plethora of tasks, including mass manipulation and modification of a site's files; server log analysis (using Perl's powerful regular expression facility); link checking (using the LWP module); and auto-generating an annotated site map from the <META> tags in the site's HTML files. The latter part of the book introduces server-side web application programming using CGI (examples include coding a site Guestbook and integrating with the SWISH-E site search facility), along with more advanced lore like the CPAN code archive, Perl's object-oriented features, storing user data in DBM databases, and publishing modules for reuse by others. Along the way, the book teaches a respectable amount about UNIX, as well; the main text, as well as the many informative sidebars, contain concise and clear explanations of necessities like stdin/stdout redirection; chmod and file permissions; shell filename globbing; tab completion in bash; network troubleshooting with traceroute; and much more.

Callender's writing style provides the right mix of hand-holding, humor, and clarity for the book's target audience. He simplifies without dumbing down, and he proves that he picked up a considerable amount of hacker culture on his own journey up the learning curve, which he shares with his pupils, citing sources from Neal Stephenson's In the Beginning Was the Command Line to Jon Udell's Practical Internet Groupware. He also does a good job of evangelizing the culture of sharing and open systems that created Perl, Apache, and the Internet as we know it, giving abundant proper credit to the authors and creators of all the tools and references to which he refers his readers. He concludes by listing, and providing jumping-off points for, the wide variety of logical "next steps" that go beyond the scope of the book: Python and other programming languages for the web, Apache configuration, mod_perl, system administration, and relational database integration.

As you may have guessed by now, I recommend this book highly, especially for anyone who finds him- or herself with responsibility for maintaining a web site but feeling a bit underequipped to do so. The book has a limitation (which is not the same as a shortcoming): it's a tutorial, not a reference work; though the index is quite serviceable, this isn't the book to turn to when you need to remember the order of the arguments to substr. This is a book to sit down and read through, once or multiple times, to help build a framework of knowledge and begin populating it with pearls of wisdom that can be put to immediate use.

Additional information about the book, including code for the examples given, is available on the web at the author's web site, O'Reilly's page for the book, and at the online bookseller site of your choice. Table of Contents:

Preface

1. Getting Your Tools in Order
Open Source Versus Proprietary Software
Evaluating a Hosting Provider
Web Hosting Alternatives
Getting Started with SSH/Telnet
Meet the Unix Shell
Network Troubleshooting
A Suitable Text Editor

2. Getting Started with Perl
Finding Perl on Your System
Creating the "Hello, world!" Script
The Dot Slash Thing
Unix File Permissions
Running (and Debugging) the Script
Perl Documentation
Perl Variables
A Bit More About Quoting
"Hello, world!" as a CGI Script

3. Running a Form-to-Email Gateway
Checking for CGI.pm
Creating the HTML Form
The <FORM> Tag's ACTION Attribute
The mail_form.cgi Script
Warnings via Perl's -w Switch
The Configuration Section
Invoking CGI.pm
foreach Loops
if Statements
Filehandles and Piped Output
die Statements
Outputting the Message
Testing the Script

4. Power Editing with Perl
Being Careful
Renaming Files
Modifying HREF Attributes
Writing the Modified Files Back to Disk

5. Parsing Text Files
The "Dirty Data" Problem
Required Features
Obtaining the Data
Parsing the Data
Outputting Sample Data
Making the Script Smarter
Parsing the Category File
Testing the Script Again

6. Generating HTML
The Modified make_exhibit.plx Script
Changes to &parse_exhibitor
Adding Categories to the Company Listings
Creating Directories
Generating the HTML Pages
Generating the Top-level Page

7. Regular Expressions Demystified
Delimiters
Trailing Modifiers
The Search Pattern
Taking It for a Spin
Thinking Like a Computer

8. Parsing Web Access Logs
Log File Structure
Converting IP Addresses
The Log-Analysis Script
Different Log File Formats
Storing the Data
The "Visit" Data Structure

9. Date Arithmetic
Date/Time Conversions
Using the Time::Local Module
Caching Date Conversions
Scoping via Anonymous Blocks
Using a BEGIN Block

10. Generating a Web Access Report
The &new_visit and &add_to_visit Subroutines
Generating the Report
Showing the Details of Each Visit
Reporting the Most Popular Pages
Fancier Sorting
Mailing the Report
Using cron

11. Link Checking
Maintaining Links
Finding Files with File::Find
Looking for Links
Extracting
Putting It All Together
Using CPAN
Checking Remote Links
A Proper Link Checker

12. Running a CGI Guestbook
The Guestbook Script
Taint Mode
Guestbook Preliminaries
Untainting with Backreferences
File Locking
Guestbook File Permissions

13. Running a CGI Search Tool
Downloading and Compiling SWISH-E
Indexing with SWISH-E
Running SWISH-E from the Command Line
Running SWISH-E via a CGI Script

14. Using HTML Templates
Using Templates
Reading Fillings Back In
Rewriting an Entire Site

15. Generating Links
The Docbase Concept
The CyberFair Site's Architecture
The Script's Data Structure
Using Data::Dumper
Creating Anonymous Hashes and Arrays
Automatically Generating Links
Inserting the Links

16. Writing Perl Modules
A Simple Module Template
Installing the Module
The Cyberfair::Page Module

17. Adding Pages via CGI Script
Why Add Pages with a CGI Script?
A Script for Creating HTML Documents
Controlling a Multistage CGI Script
Using Parameterized Links
Building a Form
Posting Pages from the CGI Script
Running External Commands with system and Backticks
Race Conditions
File Locking
Adding Link Checking

18. Monitoring Search Engine Positioning
Installing WWW::Search
A Single-Search Results Tool
A Multisearch Results Tool
The map Function

19. Keeping Track of Users
Stateless Transactions
Identifying Individual Users
Basic Authentication
Automating User Registration
Storing Data on the Server
The Register Script
The Verification Script

20. Storing Data in DBM Files
Data Storage Options
The tie Function
A DBM Example Script
Blocking Versus Nonblocking Behavior
Storing Multilevel Data in DBM Files
An MLDBM-Using Registration Script
An MLDBM-Using Verification Script

21. Where to Go Next
Unix System Administration
Programming
Apache Server Administration and mod_perl
Relational Databases
Advocacy

Index

You can purchase Perl for Web Site Management from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

Wee writes "I just came across this interesting Yahoo interview with Bob Young in which he says that Linux won't rule the desktop but will instead focus on replacing legacy Unix systems and enhancing Linux's embedded presence. He makes some pretty good points. The oddest quote: "So our opportunity is not to replace Microsoft on the PC. If you've got a perfectly good working PC, why you would go through the angst of replacing it?". Not sure where to start answering that one. My wife (a dedicated Win32 user) liked his car analogy. I need to get her to read 'In the Beginning was the Command Line'..."

Swampper writes: "New Neal Stephenson novel Quicksilver is available for pre-order from Amazon UK. It's due out on March 7th. There is also another Stephenson book on the horizon; Interface. It will arrive May 2nd." Actually, Interface was previously offered through the psuedonym "Stephen Bury" Note the discussion of this book and others on the Cryptonomicon site.

mouthbeef writes: "The year 2000 Hugo Awards have been awarded. Cryptonomicon didn't win but A Deepness in the Sky did. And hey, so did I. AFAIK, this is the first first-person account of a Hugo win published on the Web, and I know for a fact that my acceptance speech was the only one to contain an URL."

Doran writes: "We interviewed Neal Stephenson this Wednesday morning for Digital Village and will be playing Part One of the tape this Saturday and Part Two on April 29th. We discussed his recent talk at CFP2000, his thoughts on Open Source vs. Everything Else, and how the cypherpunks have received latest effort. It starts a little slow (it was 6 a.m. for us, 9 a.m. for him) but once we got going, it was pretty interesting. For those of you not in Southern California, we'll be posting the program in RealAudio by Sunday evening. "

An amazing number of people wrote in to say that the link we posted in Tuesday's Quickies to Neal Stephenson's Essay was to cool to just be a quickie. I totally agree. So I've decided to give it its own story just to make sure that nobody misses out on this thing, and to give everyone a real chance to talk about it. Its long, but its really excellent.

r3drun sent us pictures of the first production empeg (the Linux based car MP3 player). Tom Porter hooked us up with interesting essay by Neal Stephenson that is pretty interesting. Worth a read. emad sent us a link to a Vote for your favorite RFC page. Cracked me up: You vote by number. wall sent us what appears to be the new SGI Logo. Next, I've been waiting for an excuse to link Space Ghost for awhile, and Visoblast sent one that I think us amusing as hell: Naked Pictures of Keith Richards do not affect wildlife. I'm probably only posting it because I listened to Some Girls and Beggers Banquet today. In other music news, RedOregon sent us amusing parody lyrics, Welcome to Berkeley California (you can guess the tune) And finally, GiMP wrote in to say that someone created the Slashdot dance. Hemos has never looked lovelier.