Search Results: "ag"

16 September 2009

Dann Frazier: Controlling Power on a USB Hub

Andrew, I bought those wootoff lights as well, and have them connected to a hub on my mythtv system so I can activate them with a remote. I use the hub-ctrl.c utility from this page with this simple wrapper script that searches for the hub:
#!/bin/sh
bus=$(lsusb   grep TUSB2046   cut -d' ' -f2)
dev=$(lsusb   grep TUSB2046   cut -d' ' -f4   sed 's/:$//')
port=4
hubctrl=/home/dannf/hub-ctrl
if $hubctrl -b "$bus" -d "$dev" -v   grep "Port $ port :"   grep -q power; then
  toggle=0
else
  toggle=1
fi
$hub-ctrl -b "$bus" -d "$dev" -P "$port" -p "$toggle"
Note that not all hubs implement the port power feature - but luckily I had an unused one laying around that does. Unfortunately, one of my lights won't spin unless the physical power switch on the light is toggled - hopefully that's not true for yours.

Matthew Palmer: Oh Firefox...

What are you doing in that the 1.1GB of resident memory (1357m of virtual memory) you have decided to consume in order to display three web pages? All fairly basic pages -- no flash, no excessive Javascript, and I haven't even done anything particularly exciting in the browser -- just loaded the pages up and let them sit for a few days. Time to look at Conkeror on the Netbook, I suppose. I'm unlikely to be needing Firebug on there any time soon.

Matthew Palmer: Vimoutliner... finally!

I am, at best, a vim dilettante, preferring joe for most of my day-to-day text-editing needs. However, I do like using vimoutliner for notes, plans, todo lists, and calendaring (more on that some other time). However, the Debian vimoutliner package (in combination with the awesomely undocumented vim-addons mess) is an absolute pain to get going, requiring far more swearing and prodding than seems necessary. Since I don't do it often enough, too, I keep forgetting how, and today things came to an absolute head when I very nearly flung my netbook across the room as it singularly refused to do my outliner bidding. Finally, however, after much swearing (and even installing vimoutliner's upstream package to see if it worked -- it did -- and what it was doing differently -- just a small, crucial addition to .vimrc), I got the magical recipe. No doubt someone with an acheing need to make sure that vim stays as user-hostile as possible will immediately spring into action to make sure this doesn't work for squeeze, but at least for the life of lenny, here's how to get vimoutliner working:
 # apt-get install vim-vimoutliner vim-addon-manager vim
 $ vim-addons install vimoutliner
 $ echo "filetype plugin indent on" >> ~/.vimrc
May it help someone avoid putting their laptop through a wall.

Matthew Palmer: "Tx unit hang" in e1000 driver

In the "blogging it so I don't forget about it" category, and also to try and give Google some hints, here's one from the vault I recently came across again... Older e1000 chips (specifically the 82573(V/L/E)) have firmware which enables the (buggy) power management functionality in the chips. Although this shouldn't occur with hardware shipped in the last several years (the updated firmware was released ages ago), I just came across it recently in a supposedly-new server, so who knows what's going on there... The problem manifests itself as flaky or unstable network performance, combined with the kernel / log messages:
	Detected Tx Unit Hang
	NETDEV WATCHDOG: ethX: transmit timed out
The fix is as described in the "82573(V/L/E) TX Unit Hang Messages" section of the Intel Linux driver documentation for the e1000 driver. The reason I'm blogging about it is that the top Google results point to either the now-dead e1000.sf.net wiki (which used to have all the necessary info, but now doesn't), or else forum posts which point to the now-dead e1000.sf.net wiki. Either way, it's not trivial to find a working location for the fix, so... linky love time!

Jeroen van Wolffelaar: How I'm going to recall the Dunc-Tank saga

Percentage of Debian Developers preferring new elections to having AJ as DPL in March/April: 17.3%. Percentage of Debian Developers preferring new elections to having AJ as DPL in October: 14.8% That's right. contrary to what one would expect from merely reading the mailinglists, an even larger majority now finds AJ acceptable as DPL. This does not render the objections of the couple dozen DDs irrelevant though, diversity is a great good. However, diversity can easily escalate to divisiveness when different opinions or more accurately the ways they are voiced start to severely hinder activity by others. I myself have been quite demotived by the whole discussion, as has happened to me multiple times before. We Developers do not seem to be able to have constructive discussion without getting extremely heated up. I believe that this inability to hold discussions about tricky subjects is way more hurting the project than any of the "tricky subjects" themselves. Actually, the tidbit in my DPL-elections platform about Communication among Debian contributors is still equally relevant. Several potential improvements have been proposed in the past, including debating by wiki, debating inside a smaller taskforce, or even having a representative democracy. Let's explore the representative democracy principle a bit further: In general, I consider making decisions by GR (or to draw a parallel to country government, referendum) bad: A majority of voters doesn't have adequate and balanced information to make a reasonable decision, that takes doing quite some research. Instead, any discussion (vote winning?) is going to be significantly depending on emotions. Take the voting-down of the European constitution by France and the Netherlands: Hardly anyone has adequate information to really make a tradeoff, still quite a number of people voted, and supposedly one of most prevalent considerations was fear of this "Europe" thingy. Therefore, I'd really prefer that issues like firmware are dealt with by smallish team of people who really can look into the issue well, consider all arguments either way, and make a decision. As with every decision in Debian, it can be overturned by GR, but still. Note that we don't need any consitutional change for this, the DPL already has the power to delegate a person or group of people to make some decision nobody else specifically is responsible for already. A complicating factor is though that it's hard to compose such a taskforce that will have the project's support once a discussion is 'heated up'. In other news, rumour has it that -private has blown up today. I'm so looking forward to opening that mailfolder.

Jeroen van Wolffelaar: Phase change

It's done: today I heard about the last (passing) mark for the last course I need to follow for my Master in Applied Computing Science, at Utrecht University: a paper about RFID security and privacy as part of the Cryptography course. Besides some small paper still due for (ahum) my Bachelor, the only thing left is my thesis with associated research. Today I got an invitation for my first working day at ORTEC in Gouda, next month, where I'll be doing research (and implementation) on some exciting new route planning algorithms. It'll require some getting used to it, five days a week, 8 hours a day, for the rest of the year. One of the biggest challenges will be getting up in time every single day, but I'm sure I'll be fine with that eventually. I have confidence that the interesting research will make up for it completely! Already this Friday I'll be going to FOSDEM with Thijs, partly by train, and partly hitchhiking a ride from Joost. Too bad my laptop practically died... But reading mail etc. not the most important thing in FOSDEM, you can do that at home too I hope to meet yet again a whole lot of old and new Debian people over there. For the first time in 3 years no talk from me, other duties took too much time lately. I'll need to discover how much time I'll be able to spend on Debian as a full-time employee, but I think it'll make it easier for me to divide my time: I really missed doing Debian stuff from time to time, and I need to fix up a number of neglected areas real soon now. Good night!

Jeroen van Wolffelaar: Summer of Code

June is the last month before summer holidays, and at this phase in my study, courses take a lot of time: practical assignments, seminars to give, multiple exams. And mid-June, I'll be attending DebConf in Edinburgh, including delivering a talk about Mole, the subject of my Google Summer of Code project. In the period of April/May students participating in the Summer of Code project had the time to get more familiar with the project they were going to work for. Because I'm already somewhat familiar with Debian, I opted to organize an Etch release party together with some friends, because, well, what better way is there to get to know the community? During the past two weeks I've been really starting with the project. I updated the wiki page, added a new development page where I keep track of my work listing the subtasks I'm working on and their status. The first month will be mostly work on the internals, but starting with the second month I'll also be working on the web interface, meaning that there should be some stuff to show off. At the moment I'm refactoring some bits of Mole that are currently implemented in a hacky way, in order to make it all as extensible as it should be. This includes defining a config file format for mole tables, so that it's no longer necessary to modify the python code for new tables. It also involves some better way of stacking tables to each other, so that the package file extraction code can be moved away from the core of mole into a separate worker to keep mole itself pure and simple and generally applicable. I'll post irregular updates to my blog. I'm looking forward to seeing a lot of you again this Thursday, when I'll arrive in EDI!

Jeroen van Wolffelaar: 40 minutes

Yesterday I had one of the more stressful and eventful 40 minutes of my life... events basicly initiated by the fact that I arrived at Schiphol airport 40 minutes before my plane was scheduled to take off. The first thing I noticed was that the queue for security extended beyond the check-in desks next to it, so just that bit would probably take more than fourty minutes. Oops. What are all those people doing flying out on friday noons? Second thing I couldn't help to notice is that the check-in desk was actually already closed, double-oops. Well, the lady that was sitting there anyone concluded after a phonecall that my bag was fine as hand luggage and so that I could still make it. She also queue-jumped me straight to the security X-ray machine and ordered me to run from there on. Well, not so fast, running through security isn't appreciated. Actually, since I planned to check-in this bag, I kind of violated this whole anti-liquor^Wliquid silliness with no less than 7 items. The guy that unpacked my luggage let me keep my lenses fluid, and forgot to notice 3 of the items, so damage was limited, and I proceeded with my explosives, I mean, toothpaste and such, to the gate. In my hurry to run to the gate, I put my boarding pass in my pocket... and upon arrival at the gate, I noticed my boarding pass was gone, so I went ask some lady at the desk there about it... and overheard the guy next to her, who was on the phone, mention my last name. "Someone found your passport". Turns out they also had my boarding pass, but I appreciated knowing where my passport was anyway, since obviously I didn't have it on me anymore either. So within a minute I was running off again to a different gate to pick up those two sort-of-important items. You'd say that after having once seen my plane taxi away from an empty gate upon returning there from picking up my boarding pass from lost&found for the second time that very morning would've taught me a lesson... But apparantly not. Back at the gate I was getting past the boarding pass checkpoint, and the person over there saw my pass, and said "Hey, so you're that guy that a bit ago lost this and that at the security checkpoint?" Since that happened at the other end of the airport, gossip must be going pretty fast at Schiphol... At least I've never showed up at the airport at the wrong date (unlike two of my friends I'm meeting over here managed to do each independently)... Yet.

Pete Nuttall: Fun in the Afternoon

Fun in the afternoon is a designed to be a relaxed programming semair, and being bored I went along. It was pretty good, with all the talks being quite relaxed and interesting. Phil Wadler's Talk was of some interest, since I hate PHP and the other web programming things I have tried, including haskell-html and Kaya arent quite ready yet. The other three talks were quite good. All discussed new things, and there was a lot of "I don't quite know" in reply to the tough questions. The Metatheory stuff was fun, though I haven't done anything like enough type theory to need it. The Version Control stuff was quite cool, and it would be nice to see that become a real tool, similar to darcs. Andrew Kennedy's take on C# was interesting, though he admitted beforehand that he didn't quite belive it himself. It lead to a lot of muttering between Edwin and Myself as to what a functional langauge really was. Its interesting how all the academics revert back to their undergrad days: reading the paper, talking, playing on laptops, being late, sitting at the back and eating. It was also nice to put some faces to names, including Neil Mitchell and Conor McBride Its also nice to see how many people were there, and that people wanted to go have a drink afterwards. That evening I caught up with Dan, and its nice to see he is settling into his new job well. I caught the train home in the morning, getting in at three, and managed to watch the rugby before sleeping for 15 hours, a result of not sleeping week for 8 days before that.

Pete Nuttall: Turning off planet

For a while now, the last four or five months at least, I have been using planetplanet for RSS and Atom aggregation, or in english, reading a bunch of websites on one page. Planet is a bit of a hog, mainly in the disk acresses. This is a bit of a problem on hades, whose disk's aren't wonderful. Dan has been nagging me to use rawdog for a while, so this morning it floated to the top of the todo list, and stealing his config and one line of shell gave me a sorta working instance with the same feeds:
grep "^\[h" ~/usr/planet/lupin/config.ini   sed "s/\[//"   sed "s/\]//"
  awk ' printf("feed 1h %s\n", $1) ' >> .rawdog/config
I'm going to leave it for a bit to see if I like it, and to sort how I want it laid out, but its now in cronand planet isn't, so the worse abuser of hades should be gone.

Pete Nuttall: How Random is xkcd?

I was reading xkcd by clicking on the random link when I noticed that the same cartoons were coming up again and again. I was wondering if this was Confirmation bias on my part or a duff random number generator on the server's part. Randall Munroe is a science geek, and I figured what he would do is test this idea... One python script and 12,000 (approx) requests later, I had a file full of numbers and started trying to remember some statisics. I threw together a quick bit of python to work out the mean and standard deviation (its here). The mean value is 97.4155602788 and the standard deviation is 171.040683155. If they are uniformly distributed from 1 to 361, the expected mean would be 104.211323761 and the standard deviation would be 181.0. So I was lost in thought for a while. However, the following quick check threw some light on the difference.
>>> data = [int(x) for x in open('numbers.data')]
>>> for x in xrange(0, 361):
...   if x not in data:
...     print x
... 
0
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
So comics numbered about 338 don't appear. And recomputing the mean and standard deviation for 1 to 337 gives a mean of 97.2830920561 and a standard deviation of 169.0, which is about the mean and standard deviation the data gives. I'm now waiting for someone who actually knows stats correcting me in where I went wrong. The conclusion? I suffer from confirmation bias :-(. For those who like pretty pictures, here is one, courtesy of the Google charts API and pygooglechart: chart of freq against comic number code here

MJ Ray: SPI September 2009

Once again, the monthly board meeting of Software in the Public Interest will take place on irc.oftc.net #spi tonight (Wed 16 Sep) at 20:00 UTC. The meeting announcement was posted and there s a proposal for an extra bank account and two projects up for association: Path64 and OSUNIX. The big change for current members is the proposal for contributing membership expiry:
Any contributing member who does not cast a ballot in an annual Board member election shall be considered to be inactive and downgraded to a non-contributing member.
Yet another demonstration of how member ballots are not secret yet. Even if they re not secret like they should be, is it a good idea to feed the ballot data to the membership process? Should Further Discussion be added to the SPI board election, to give members a way to abstain? Should this dramatic change proposal be considered this meeting when it wasn t mentioned in the meeting announcement?

Ingo Juergensmann: Problems with xrandr/krandr

For some time now I'm using a dual monitor setup with my Radeon 9200 SE (RV280). Basically this works quite well, except that I need to enter these commands manually:

CODE:
xrandr --output VGA-0 --mode 1280x1024
xrandr --output DVI-0 --auto
xrandr --output DVI-0 --primary
xrandr --output DVI-0 --right-of VGA-0


Without these settings krandr is unable as well to detect both monitors properly. And it's not remembering the settings when I close/save the session by logging out. I tried to add the above code lines in ~/xinitrc as well as in /etc/X11/xinit/xinitrc, but they are not executed as after a restart of X I end up with the wrong monitor being the primary instead of the DVI display.

My xorg.conf is this:

CODE:
Section "ServerLayout"
Identifier "X.org Configured"
Screen 0 "Screen0" 0 0
Screen 1 "Screen2" LeftOf "Screen0"
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection

#Section "ServerFlags"
# Option "Xinerama" "off"
#EndSection

Section "Files"
ModulePath "/usr/lib/xorg/modules"
FontPath "/usr/share/fonts/X11/misc"
FontPath "/usr/share/fonts/X11/cyrillic"
FontPath "/usr/share/fonts/X11/75dpi/:unscaled"
FontPath "/usr/share/fonts/X11/100dpi/:unscaled"
FontPath "/usr/share/fonts/X11/Type1"
FontPath "/usr/share/fonts/X11/75dpi"
FontPath "/usr/share/fonts/X11/100dpi"
FontPath "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType"
EndSection

Section "Module"
Load "dbe"
Load "dri"
Load "extmod"
Load "glx"
Load "record"
Load "dri2"
EndSection

Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
EndSection

Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/input/mice"
Option "ZAxisMapping" "4 5 6 7"
EndSection

Section "Monitor"
#DisplaySize 430 270 # mm
Identifier "DVI-0"
VendorName "SAM"
ModelName "SyncMaster"
HorizSync 30.0 - 81.0
VertRefresh 56.0 - 75.0
Option "DPMS"
Option "Enable" "true"
Option "PreferredMode" "1680x1050@60"
EndSection

Section "Monitor"
#DisplaySize 430 270 # mm
Identifier "VGA-0"
VendorName "HP"
ModelName "L1925"
HorizSync 30.0 - 81.0
VertRefresh 56.0 - 75.0
Option "DPMS"
#Option "Enable" "true"
Option "LeftOf" "DVI-0"
#Option "PreferredMode" "1280x1024@60"
EndSection

Section "Device"

Identifier "Card0"
Driver "radeon"
VendorName "ATI Technologies Inc"
BoardName "RV280 [Radeon 9200 SE]"
BusID "PCI:1:0:0"
Option "Monitor-DVI" "DVI-0"
#Option "Monitor-VGA" "VGA-0"
Screen 0
EndSection

Section "Device"
Identifier "Card1"
Driver "radeon"
VendorName "ATI Technologies Inc"
BoardName "RV280 [Radeon 9200 SE]"
BusID "PCI:1:0:1"
Screen 1
EndSection

Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "DVI-0"
SubSection "Display"
Viewport 0 0
Depth 1
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 4
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 8
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 15
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 16
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
Virtual 2960 1050
Option "InitPrimary" "true"
EndSection

Section "Screen"
Identifier "Screen2"
Device "Card1"
Monitor "VGA-0"
SubSection "Display"
Viewport 0 0
Depth 1
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 4
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 8
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 15
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 16
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
Virtual 2960 1050
EndSection


So, dear lazyweb, what's wrong with this setup and how can I fix it?

Muammar El Khatib: Exchange

Well, I was so tired of my mini hp 2133 that I decided to exchange it or selling it. The main reason of this is the lack of Linux support from VIA (No 3d acceleration, no free driver for Wifi, etc). I was looking at http://www.mercadolibre.com.ve/ and I found a guy who was selling/exchanging a G1. When I saw that, I thought: this could be the chance to get a G1 without using the credit card :-P. So I contact this guy, I met him at La Vereda del Lago de Maracaibo and after checking both devices we made the exchange.

I have to say that I am happy with the exchange because I was using a Motorola w180 which is a fuckin' shame of phone. Besides, the G1 is in very good shape.

The G1 is a very amused phone. I had to reset it. Such a process was very easy. I followed the procedure at http://www.androidcentral.com/factory-reset-tmobile-g1/

It's time to go to bed now, or I hope so ;-). I think I have done a good exchange, don't you think so?

Robert Collins: Back from hiatus


Well, the new blog seems to be up and running and gathering modest numbers of comments already. Woo. I ve a bunch of mail about test suite performance to gather and refine into a follow up post, but that can wait a day or two. In bzr we suffer from a long test suite, which we let grow while we had some other very pressing performance concerns. 2.0 fixes these concerns, and we re finding the odd moment to address our development environment a little now. One of the things I want to do is to radically reduce the cost of testing inside bzr; code coverage is a great way to get a broad picture of what is tested. Rather than reinvent the wheel (and I ve written one to throw away, so far) are there tools out there that can:
  • build a per-test coverage map
  • do it quickly
  • don t include setUp/tearDown/cleanUp code paths in the map
  • report on the difference between two such maps (at the suite level)
The third point is possibly contentious, so I should expand on it. While code that is executed by code within the test s run() method is from the outside all part-of-the-test, its not (by definition) the focus of the test. And I find focused tests substantially easier to analyse failures in, because they tend to check preconditions, poke at object state etc. As I want this coverage map to help preserve coverage as we refactor the test suite, I don t want to include accidental coverage in the map.

Steve McIntyre: Helsinki in the autumn

I arranged a weekend trip for me and Jo at short notice when other plans for the weekend didn't happen. And I'm glad I did, we both had an excellent time! :-) We met up with Lars and Soile for dinner at their place on Saturday when we arrived, and they were great hosts. We hit the sauna then went back to our hotel, tired from the travel but happy. I had promised Jo that we would find some reindeer for her, so on Sunday we went overboard. First of all, a trip to the natural history museum in the middle of Helsinki where we got to see models of reindeer and reindeer skeletons (amongst other things!)... Bones... Then we went to the Zetor Tractor Bar for lunch, including (of course!) reindeer to eat. Then on to the zoo to see various animals including big cats and ... reindeer! *grin* We headed back to the centre of Helsinki and met up with a bunch of the locals for drinks and some dinner. It was excellent to meet up with these folks; I'd not met some of them in a couple of years! Droidy after a few drinks Finally, last thing that night, I surprised Jo with a trip to the Ice Bar in the middle of the city. She had no idea where we were going, and when we got there the look on her face was wonderful! Brrrr.... We both loved the trip, and we'll have to go back again soon.

15 September 2009

Joey Hess: Debian Installer USB partitioning

The Debian Installer has a USB boot image that is supposed to be written raw to the USB stick. Problem is that means the image has a fixed size, 256 MB, and all the other gigabytes on your typical USB stick are unusable after writing this image to it. It's a bit of a cheat for me to blog about this, since I'm slighly responsible for the thing that I'm working around. But still. The real problem is not the fixed size of the image, but that it is written to the USB stick as a "super floppy", without any partition table. If there were a partition table, you could make a second partition in the rest of the space of the USB stick, and use it to store files, etc. So, let's set that up. It's not really hard:
  1. Use your favorite partition tool to partition the USB stick. Make a 256 MB DOS partition, that will be used to hold the installer, and set it bootable. Make a second, or more partitions for your own use.
  2. Unplug and replug the USB stick so the device files show up, and write the installer image to the first partition (/dev/sda1 in this example). zcat boot.img >/dev/sda1
  3. Make the USB stick bootable by installing the mbr package, and running install-mbr /dev/sda
  4. Copy a Debian ISO image to the USB stick somewhere. You can put it on the first partition, as ususal, or if you prefer, can put it on one of the later, larger partitions. That's useful if you want to use a larger ISO than the netinst. The installer should find it anywhere.

David Welton: Tcl and the Tk Toolkit, 2nd edition

<iframe frameborder="0" marginheight="0" marginwidth="0" scrolling="no" src="http://rcm.amazon.com/e/cm?lt1=_blank&amp;bc1=000000&amp;IS2=1&amp;bg1=FFFFFF&amp;fc1=000000&amp;lc1=0000FF&amp;t=dedasys-20&amp;o=1&amp;p=8&amp;l=as1&amp;m=amazon&amp;f=ifr&amp;md=10FE9736YVPPT7A0FBG2&amp;asins=032133633X" style="width:120px;height:240px; float: left; padding-bottom: 10px; padding-right: 10px;"></iframe> I'm not sure what I was expecting, but the news that "my" book is finally out is cause for excitement, anxiety, and relief. It's not actually "my" book at all; it was originally written by Dr. John Ousterhout, who created the Tcl programming language, and the Tk toolkit. And Ken Jones is listed as the co author of the 2nd edition, because he's the guy that pulled everything together and managed to actually bring the project to fruition. However, I did play a part a part in the project. About 5 years ago, I was doing a lot with Tcl, and then, as now, I thought it was a shame that the language was not promoted as well as it could be. It's not a perfect language, but at nearly 20 years old, it has stood the test of time, and it has a lot going for it. In any case, at the time, I had noticed that there was no good, publicly available tutorial. Tcl has always had an excellent set of man pages describing all of its various commands and subsystems, but did not ship with a tutorial that would help new users get started. I thought that that would be a good problem to solve in order to make the language more attractive to newcomers. However, writing a tutorial from scratch is no simple task, so I started looking around for material that might be adapted. One thing that sprung to mind was the first edition of "Tcl and the Tk Toolkit". At that point the book was nearly 10 years old, which in tech years is practically forever, and indeed, the material in the book, while good, was quite dated for some portions of Tcl. Figuring it couldn't hurt, I emailed Dr. Ousterhout to see what he thought of open sourcing the book, or at least the first part of it, with the idea of updating and utilizing that as a tutorial. He was actually ok with that idea, but the copyright belonged to the publisher rather than him, so he gave me a contact with the publisher, who I then sent my idea to. They weren't necessarily against the idea of releasing the material under an open license, but came back with another idea: why not update the book? That sounded like an interesting project in its own right. I don't recall all the details (this was in 2004), but the publisher ended up with Ken Jones as the guy to run the project, as he'd participated successfully in updating another popular Tcl book. In the end, there were several of us (Eric Foster-Johnson, Donal Fellows and Brian Griffin, in addition to Ken and myself), that worked on the project, divying things up by sections, with Ken coordinating. I am honored to have my name listed amongst such august company. Which brings me back to being nervous: the idea of having something I wrote "set in stone" is a source of some anxiety for someone like me used to working with such a malleable world as that of software. Also; I wrote most of my contribution (I focused on the C API) several years ago, and I hope it's still valid, and of course that there aren't any huge and glaring errors. For a while, the book seemed like it was in limbo - just when I thought it was dead, Ken would come back with an update. This was also a cause for concern, as I wanted the thing to either die a dignified death, and get on with my life, or appear in print. As for the tutorial, I did manage to make that happen as well. Clif Flynt, who authored a Tcl/Tk book of his own, was kind enough to donate some material from a tutorial of his own, which several of us hacked at to get it into shape. It's available here: http://www.tcl.tk/man/tcl/tutorial/tcltutorial.html In any case, I sincerely hope that the material I wrote manages to do justice to the years and years of work that have gone into the language and its implementation, and hope you find the book valuable if you pick up a copy.

Daniel Leidert: Writing manual pages in GROFF (1)

I always wanted to write a short howto for Debian package maintainers, how to write a manual page in GROFF. This is useful for short documents (for longer documents, docbook/docbook-xsl can be a good choice). I already have written some parts. However, here is the first part of hints. More might follow later. The delimiter in the NAME section The name section is (probably) the only place, where exactly one hypen-minus \- must appear. The hyphen-minus is the delimiter between the command name and one-line description.
.SH NAME
foo-bar \- foos the template foo-what-bar
Typical mistakes regarding paragraphs Using a .PP macro directly following a .SH or .SS macro is useless. This macro should be used between paragraphs:
.SH OPTIONS
The program follows the usual GNU command line syntax, with long options starting with
two dashes ( \-').
.PP
A summary of options is included below.
Options/File descriptions To describe options or files it s usually useful to make use of the .TP macro.
.SH OPTIONS
.TP
.B \-f, \-\-force
Force the execution of the specified command.
.SH FILES
.TP
.I ~/.foobar
Per user configuration file.
To create more than one intended paragraph the .IP macro can be used.
.TP
.B \-f, \-\-force
Force the execution of the specified command.
.IP
This option has no effect in conjunction with \fB\-\-foo\fP.
Avoid hyphenation in URLs/URIs/paths Usually we don t want URLs or URIs to be hyphenated. This can be done using the \% sequence. Typical examples:
A short tutorial is available online at \fI\%http://foo.tld/some/path/here/manual.html\fP.
On a Debian system the complete text of the GNU General Public License
version 2 can be found in the file \fI\%/usr/share/common-licenses/GPL\-2\fP.
Referencing persons and their mail address The common markup is to write the person name in bold letters and the mail address in roman letters is put into angle brackets. It s usually a good idea to mark where the mail address starts and ends. We can use the \& sequence as shown in the following example:
\fBDaniel Leidert\fP <\&daniel.leidert@wgdd.de\&>

Mike Hommey: Would you like iceweasel 3.0 and 3.5 to be co-installable ?

Hi lazyweb, I m wondering if there a lot of demand for such a feature, being to be able to install 2 (or more) major releases of iceweasel on the same computer. If there is a strong demand, I may consider allowing it. Please reply in the comments on this blog with your feelings, for or against the implementation of this co-installability. Thanks. PS: you may also forward this query to other sites and send people back here to leave their opinion.

Next.

Previous.