Search Results: "tar"

17 June 2007

Meike Reichle: Just when you are about to give up ...

It actually seemed as though I wouldn't be going to DebConf this year. I didn't get to work much the last two months, since I wanted to spend all my time on the near completion of my thesis so I didn't have the money to pay for a flight (or train) to EDI and back myself. Due to that same thesis I also didn't have the time to prepare a talk this year so I was also not a speaker. Since I am also neither a DD nor in NM I was pretty sure I wouldn't be eligible for travel sponsorship this year. And, as expected, I was indeed very far down the queue, so when I still hadn't heard anything about being sponsored until about a week before DebConf was starting I had pretty much given up on the whole thing and resigned to the fact that this year's DebConf would happen without me. However, on 10 June I had a mail in my Inbox. Subject: "Your travel cost sponsorship request for DebConf7". It seems the DebConf team was able to dig up some more money and do another run on the sponsorship queue. This was three days before I had to get my thesis to the print shop and I wasn't really doing anything else except for frantically going over my proof readers' annotations, doing last minute additions, changes etc. and occasionally lie down for a few hours of rather uneasy sleep. So my first reaction was something along the lines of "What?! Now?! I don't have time for this now! Go away!" and I was pretty close to answering the mail saying "Thank's but that's too short notice. I won't be coming, have fun, see you all next year." Luckily Tolimar prevented this though and actually managed to find a flight for me that not only goes on the actual days that I had originally planned to arrive and leave but that is also not far over my travel sponsorship! So, long story short, I'll be flying to EDI on Wednesday. It'll only be for the very last few days and I am probably already missing out on lots and lots of stuff, but at least I'll be able to attend for a few days. And in time for debian-women's third birthday! :) I just hope everything will go well, it seems there's a lot of trouble with flying to DebConf this year, at least judging from what I read on planet and heard on irc. See you all soon!

16 June 2007

David Moreno Garza: Stuck on my way to Edinburgh

So, here I am in Jamaica, NY, near the JFK airport. Flyglobspan’s flight to Liverpool was cancelled and scheduled until next Monday. This simply sucks and I don’t have any energy left for flaming anybody, I just did it too much during the afternoon. Just as Christine, I shouldn’t have booked with this crappy company, due to my previous feelings about this. A lady was flying on Tuesday, and they rescheduled her itinerary to today, and they simply re-rescheduled now for Monday. Also, I already had an scheduled train from Liverpool to Edinburgh and an open return. If I don’t get my way to the UK on Monday, I’ll simply won’t be able to make it for DebConf, since I had planned to get back from Edinburgh to Liverpool on Friday night or Saturday morning, Raquel could join me in NYC before of what we had planned (Saturday evening). At least, the airline is paying for a hotel. So, I’m stuck here, with two bottles of tequila, one of mezcal, a bottle of extra-spicy Valentina, a pack of ping initos, which all were presents for buddies, and all energy I wanted to spend with friends in Edinburgh. Such is life. I’m going out right now actually. I’ll see if I can catch some jazz somewhere in NYC. If any Debianer or Perler is around the neighborhood, feel free to call/text to +525529009939.

Michael Janssen: Ask the Interwebs #1

Lately I have been thinking about switching source code management systems. In years gone by, I have used CVS, Subversion, arch, and most recently bazaar-ng for managing all the source code that I have to change. Lately I have been unhappy with the speed that bazaar takes to get some things done, and after watching a Google talk by Linus about Git, I thought I would give it a look.

I was surprised to find out that it actually models the way that I work normally slightly better than the bazaar model does. The main thing is that a repository holds a bunch of branches, but the working directory only has one of those branches checked out at any point in time. I use bazaar with about 4-5 branches per project, and only work on one of them at once (normally, sometimes I want to transport a bug across a couple branches) - so the "working space replaced by branch you want to work on" actually works out OK for me. I also need to collaborate with a bunch of projects at school and work that use other systems including CVS and Subversion, which Git seems to make it easy to do.

I did run into some questions that I don't really have a good answer to, however, therefore the new segment on the blog: Ask the interwebs. Normally I would just ask on some IRC channel, but the Minneapolis public library doesn't seem to allow anything but HTTP out. On to the question!

When using Git, how do you manage having multiple computers (at multiple locations) that you work on? I have approximately 5 different computers that I use regularly. Luckily I have enough space to have git installed on all of them, and I also have a web server that I can use WebDAV on if necessary. What I would like to have is a repository that I can pull from before I start work (if I am connected) and then push to when I finish so that the next computer I sit down at I can just pull again and get everyting. I would like this to include any branches I may have made on the first computer. Is this possible, hard, or easy for Git users? How much do I need to worry about slowdown? My WebDAV server is in the cloud, and I would prefer to be able to get up and go on say, a minute's notice.

I'm also interested on what your workflow is like even if it doesn't match the model I just described. I'm open to changing - the bazaar-ng to git change is big enough that I can probably incorporate a new workflow as well.

Comments: (8) Trackbacks: (1)

Comments
  1. adrian: hi, i'm a just a newbie so can't help much.
    You can host your push repository in http://repo.or.cz.
    If you prefer to do it your own you have git-daemon (Have a look to tutorials). Good luck!
  2. Michael Janssen: I looked at the public repo.or.cz, but decided against it, because while I want my branches to be available at some point, I'd rather not all of them at the same time. People randomly finding them is okay, but I'm sure I'll check in unworkable/uncompilable code in this state, because I would basically be using git as an easy sync between computers at times.

    I'm just really interested in how other people deal with this issue of needing semi-location-independent access to the branches.
  3. mike: Sounds already good for you to use git.

    Enjoy!
  4. R mi Vanicat: I haven't answer to the synchronization problem on my blog post because it is one I don't have. Still, you can make a git repository that can be pull and push from, and git can use https/dav or ssh or its on git protocol for this.

    Just read man git-remote, man git-push, man git-pull and man git
  5. JM Ibanez: Just upload a bare git repository (e.g. copy /.git in particular) to a server you have ssh access to. Then, in your working copy in git 1.5:

    <br />
      $ git remote add upstream git+ssh:///path/to/bare/git<br />
     


    You can then

    <br />
      $ git pull upstream .<br />
     


    or
    <br />
      $ git pull upstream/some-upstream-branch my-local-branch<br />
     


    or
    <br />
      $ git push upstream/some-upstream-branch<br />
     
  6. Josh Triplett: A followup to that: you can do the same thing without ssh access, by using WebDAV. See Documentation/howto/setup-git-server-over-http.txt in the Git source (also available various other places in other formats).
  7. Steven Walter: Whenever I want to create a non-local git repository for push, whether for sharing the code or just backing it up on another system, I follow this procedure:

    ssh remoteserver
    mkdir myproject.git
    cd myproject.git
    git --bare init --shared=all # world readable, group writeable
    chgrp -R git .
    vi description
    exit
    # back on local system
    git remote add origin git+ssh://remoteserver/path/to/git
    git push origin master:master
    git push origin branch2:branch2 # repeat for other branches

    You may then want to re-create your local branches so that they "track" the remote branches. "man git-branch" for more details on this.

    Hope that helps!
  8. brian m. carlson: For your workflow, you can try this:
    [geshi lang=sh]
    # first time on each machine only (you can use DAV, too)
    git remote add server git+ssh://server-hostname/path/project.git

    # every time
    git push server
    ssh anothermachine
    git fetch server
    git pull server branch-on-server-to-merge-from
    # merge happens; continue working
    # start over again from the push
    [/lang]
Trackbacks
  1. How I use git
    Michael Janssen ask about workflow and git, so I will explain mine. I have three types of git repositories: git-svn repositories where I don’t have write access on the upstream subversion repositories. git-svn repositories where I do have write ...

Stefano Zacchiroli: debcamp excitement

Debcamp is productive Shame on me for having underestimated the productiveness of DebCamp/DebConf. This year I'm overwhelmed by things to do and the first (for me) 2 days of DebCamp have really been productive. Yesterday the Zenoss packaging has taken off. We have already implemented (thanks to Fabio) the needed changes in dzhandle to properly handle ZEO databases, added user management for the zenoss system user, updated the documentation and we started working on the dbconfig-common stuff (we also have just noticed that Seanius, dbconfig-common author, is arriving tomorrow at DebConf, what a great occasion!). Today I've worked more on the OCaml packaging side. A first working version of OCaml 3.10.0 is now available in experimental .. ehm, oops, I meant in the NEW queue; CamlP4 available in there has been finally properly split into (huge) pieces and people can start rebuilding OCaml packages against it. Next day, actually hour, exciting adventures for me include: Wow, I'm overwhelmed, but it's actually soooo fun!

Neil Williams: Arrived in EDI

OK, after fighting with the Edinburgh traffic / roadworks, I'm finally in-situ and online. Just going to go and find the venue, get badge, etc., ready for the full start tomorrow. (My first DebConf!)

Steve Langasek: Did you hear that etch is out?

One of the reasons I tend not to blog very much is that I don't have much to say to the Planet Debian audience (the only place I know my blog is syndicated) that hasn't been said a dozen times before. But the world's best release party (the one good enough to cross an ocean for) gave me food for thought, and for once I'm inspired in the true spirit of blogging to write even if nobody cares what I have to say. Even if it has taken me until two months after the release to write it... Folks within the Debian community have been asking for years whether it's really still worthwhile for Debian to do stable releases, or if we're better off focusing on our "core competency" of testing and unstable and leaving stable releases to derivatives. For me, the answer to this question is an unqualified: yes, it's worthwhile. Of course that's the answer you'd expect from a release manager. Who would want to believe after committing as much time as the release team does that their efforts had been wasted? But the investment I've made in the etch release wasn't done without reflection; I recognize that the level of involvement required to be a release manager has come at some personal cost to me, as it does for each member of the release team, and I have made the investment anyway because I believe in Debian's philosophy, its goals, and its community. Even outside of a stable release, Debian packages really are great; in spite of the bugs and library transitions that we as release managers spend our time on in unstable and testing, and figures showing that within a month of the etch release we already had some 500 RC bugs identified for lenny, both unstable and testing do a great job of meeting the needs of many of our users. And package maintainers are constantly improving their packages in unstable, fixing bugs and adding new features. Unstable is a flowing river, vibrant and vital, never the same twice -- and only rarely are people dragged to their deaths by the undertow. ;) Maintainers often don't get to choose the version of their package that goes into stable. When it comes to a stable release, the bug you know is quite often better than the bug you don't. But although the release team is charged with chasing out the release-critical issues in preparation of a stable release, it isn't just the release team who deserves credit for etch. Etch is a monument to the work of all Debian maintainers, who have each helped shape the release with their contributions. "Stable" doesn't mean "perfect", but it does mean "lasting": in etch we have not only created what I think is the highest-quality OS I've ever had the privilege to be involved in, we have created something permanent that will be burned to thousands or millions of disks, something that users will continue to use and install for years to come. Far from standing in opposition to unstable, it is a perfect complement, letting us share everything that's great about Debian with users for whom tracking a constantly-changing testing or unstable simply isn't an option. I had decided well before etch was finished that it was time for me to move on from serving as release manager, but I still look forward to great things from Debian stable for lenny and releases beyond. With last weekend's release team meeting in Juelich, and the wonderful collaboration that's sure to take place this week at DebConf 7, I think we're off to a great start. The grumbling on IRC about broken packages and missing builds and uncoordinated library transitions is already in full swing for lenny -- and I'm no small contributor to that myself even now -- but we shouldn't let that blind us to what a great achievement etch has been for the Debian community, and what a great achievement lenny will be when it's released exactly on schedule next year.

15 June 2007

DebConf team: Streams are up (Posted by Holger Levsen)

To say it again and upfront: streaming is optional. While we do try to make them work as best as we can, we also want to state again, that our priority is to preserve DebConf7 for eternity and not for the viewing pleasure of those few, who can’t wait :-D That said, http://streams.video.debconf.org:8000 is up and running. Yay! Yay! This time also with a lolstream over night. That announced, we’re still sorting out minor and not so minor glitches. So, I’ll stop blogging now. And we’re still looking for more servers in Australia, Asia, Africa and Antarctica :-) And now let’s hope everything will work out in the real world! Have fun at DebConf or watching on your sofa, if you’re lucky :-)

David Moreno Garza: Call for Gathering of the Indigenous People of the Americas

Transcript of the call for participation on the Gathering of the Indigenous People of the Americas. If you don’t mind, feel free to skip it. Considering that 515 years after the first invasion of our ancestral territories, the war of conquest, the plunder, and capitalist exploitation have not altered their course, but rather have become a new war of extermination, a war designed for the destruction and utter plunder of all the original peoples of the Americas; Considering that the long history of wars of independence and numerous revolutions that have taken place on our continent have not yet changed the condition of colonized people, nor have they allowed for a full recognition of our rights in the nation states that formed in the last two centuries; Considering that despite a long history of domination, our resistance has sustained itself and that our people continue to live and struggle, and that this struggle has been encouraged by the uprising of the Zapatista National Liberation Front (EZLN) in the first days of 1994; Considering that the strategies of the national governments of the Americas have always sought the division of our people through the establishment of borders, reservations, and legislation designed to fragment us and to neutralize our efforts of autonomy; Considering that the strengthening and the unity of the struggles of liberation of the indigenous people of the Americas will be possible as our peoples meet and come to know each other; Considering that for our people it has proven necessary that their struggles be made known world wide in order to be supported by all honest movements that struggle for a society effectively just, free, and democratic; All indigenous communities, tribes, and nations of the Americas are called to

THE GATHERING OF THE INDIGENOUS PEOPLE OF THE AMERICAS Which will take place the 11st, 12nd, 13rd, and 14th days of October, 2007 in the community of V cam, Yaqui Territory, Municipality of Guaymas, State of Sonora, Mexico, to address the following

TOPICS 1 The war of capitalist conquest in the indigenous communities in the Americas.
2 The resistance of the indigenous peoples of the Americas and our defense of
mother earth, our territories, and our cultures.
3 Why do we, the indigenous peoples of the Americas, struggle?

ORGANIZATIONAL PRINCIPLES 1st Principal. Delegates, observers, and communications media workers attending the Gathering will abide by the regulations of the Yaqui Tribe devised by their Traditional Authorities in order to govern their presence while in attendance.
2nd Principal. All participating indigenous communities, tribes, and nations are invited to demonstrate their clothing, songs, dances, and other traditional forms of expression.
3rd Principal. Authorities and Representatives of indigenous communities, tribes, and nations of the Americas are invited to participate as delegates with voice and vote.
4th Principal. Individuals and members of social movements and civil organizations in solidarity with the struggles of indigenous peoples of the Americas invited by the organizing commission will be able to participate as observers.
5th Principal. National and international communications media workers that are accredited by the organizing commission will be able to cover the event.
6th Principal. All agreements adopted at the Gathering will be made by consensus of the participants and not through the method of voting.
7th Principal. Organization of the Gathering, the national and international distribution of its publicity, as well as accreditation of participating delegates, invitees, and any unforeseen issues will be resolved only by the organizing commission in conformity with the Traditional Authorities of the Community of V cam, Yaqui Tribe, The National Indigenous Congress (CNI), and the Sixth Commission of the Zapatista National Liberation Front. Information: 1. Office of the Sixth Commission of the EZLN, located on Zapotecos St. No 7 Col.Obrera, C.P. 06800 Mexico, D.F. Telephone: (01 or 011) 55 67 61 42 36 Monday thru Friday, 10 AM 8 PM., Saturday, 10 AM 6 PM.
webpage: www.encuentroindignea.org e-mail: informes@encuentroindigena.org
2. Official Precinct Office of the Traditional Guard of the Yaqui Tribe, Vicam Station ,Colonia Yaqui, Municipio de Guaymas, Sonora, Mexico. Telephone: (045 or 001) 64 49 98 94 08.
3. Office of the Organization of Indigenous and Campesino Communities, de Tuxpan, Jalisco, in Nicolas Bravo, No. 65 , Tuxpan, Jalisco,. Telephone: (01 or 011) 371 41 764 15 from Monday Saturday, 10 AM 8 PM. e-mail: comunidad_tuxpan@hotmail.com Written - April 22nd, 2007 in Tohono O Odham Territory of the Tohono O Odham Nation, Sonora, Mexico. Attentively,

Wa-a itom yo Lutu-ria yoribetchibo, intoka a Wiutinepo Amani
(Por el respeto a nuestros usos y costumbres, nuestra identidad y cultura y nuestra verdad que permanezcan en el tiempo y no se olviden)

Never Again, a Mexico Without Us ~ Liberty, Justice, and Democracy

 

Nde Cultural Historical Organization
(Organizaci n Cultural e Hist rica de la Naci n Nde/Apache)

 

Tierra y Libertad / Chicana Indigenous Organization, Tucson, Arizona
(Tierra y Libertad / Organizaci n Xicana Ind gena, Tucson, Arizona

 

Native and Immigrant Indigenous Development Organization
(Desarrollo de Los Pueblos Indios Inmigrantes y Nativos, A.C.)

 

Michelle Cook (Dene Nation)
(Nacion Dene/Navajo)

 

Tohono O Odham Nation Mexico United States
(Nacion Tohono O Odham M xico - Los Estados Unidos de America)

 

Traditonal Authorities of Vicam Community, Yaqui Tribe
(Autoridades Tradicionales del Pueblo V cam, Tribu Yaqui)

 

National indigenous Congress (Congreso Nacional Ind gena)

 

Clandestine Revolutionary Committee, General Command of
the Zapatista National Liberation Army (EZLN)
(Comit Clandestino Revolucionario Ind gena-Comandancia General del
Ej rcito Zapatista de Liberaci n Nacional)

Anthony Towns: Men in Skirts

Well, made it to Edinburgh, via a forty hour stopover in Singapore. Picked up a tie and kilt in the Debian tartan. Sadly Edinburgh in midsummer isn’t as warm as Singapore in summer, or even as Brisbane in winter, so there’s good odds my knees are going to be shaking as well as visible all to soon. Oh well, there’s reports that there might be scattered sunshine by Monday – fingers crossed. The dak BOF’s been delayed until tomorrow (Saturday 3pm, Edinburgh localtime) so Andi and Steve can sit in. Bit weird having something that technical on Debian day, I guess, but hey, whatever. It’s scheduled for a 2hr session, but I’m hoping it’ll be pretty informal and hacky rather than slides and lecturing or whatever. I’m hoping people will arrive with some ideas on what cool things that dak ought to be handling, and we can spend the time actually making dak support as many of those things as possible. Some of the ideas I like are in the BOF proposal. It might also be worth having a look at the video (or audio) of Robert Collins’ talk (“…Release always?”) at the Debian miniconf at linux.conf.au earlier this year, particular related to some of the ideas about setting up separate GNOME or KDE or libstdc++ staging areas for getting major updates ready for unstable rather than mixing them all up in experimental. Anyway, feel free to plan on arriving or leaving anytime during the BOF, unstructured is just another word for freedom! Yesterday I had a quick chat with Frans about getting debootstrap officially incorporated into the d-i subversion repo, so that it’s officially team maintained, and there’s a convenient central place for hacking on it. Given the recent discussion (while I was flying to debconf, in fact – how inconsiderate!) hopefully that’ll mean we’ll get a couple of cleanups there too. Oh, also got informed that Eben Moglen will be giving a free lecture in Edinburgh on Tuesday after debconf (the 26th) courtesy of the Scottish Society for Computers and Law. Sounds interesting if you’re into the whole theory of law and the effects of modern technology thereon:
In this lecture, Professor Moglen considers how private legislation is replacing public law as the organising intellectual structure for software and the technology industries, with far-reaching social consequences and theoretical implications.
Not sure if he’ll arrive in time to drop by during DebConf proper or not.

Reinhard Tartler: create-chroot

I’ve crafted a small perl script for (re)creating chroots on lvm snapshots. You can find it on create-chroot. I’m not very used to program in perl, and I don’t enjoy it that much. This was a small test to get used to it, so if you have suggestions and/or improvments, feel free to edit it straight away. Perhaps it is a useful addition to the devscripts package?

Isaac Clerencia: Stephen Colbert about Don t ask, don t tell policy

I’ve just watched this awesome video from the Colbert Report about gay people in the military. It bashes the shameful Don’t ask, don’t tell policy in its usual satirical way. Watch it!

Adrian von Bidder: /me waves to EDI

I'm not in EDI, I'm dead tired, the temperature outside dropped by 10 C since I went out of the house this morning, it's started to rain heavily, and I notice that I didn't take any form of coat against the rain. I think I'd even risk the deep fried Mars bar at this point. (OTOH my wife came back from China early this morning and we're going on a 2 weeks vacation tomorrow, so all is not lost.)

DebConf team: Some more streaming relays wanted (Posted by Holger Levsen)

It’s 24h until DebianDay, the day promoting Debian to the general public in Edinburgh, which is the preceeding event of DebConf7. The video setup is almost completly done now. It will allow us to publish the recordings shortly (within hours) afterwards, with very little manual work. Today we’ll be polishing it some more and test everything with three simultaneous streams. Yesterday we successfully tested mixing video from three cameras, which was recorded and streamed to the net. While recording has still the highest priority, the streaming setup this year will (hopefully) also really rock: thanks to the help of some friendly OFTC people we’ll use geoDNS, so that there will be one DNS name for all and the users will automatically be directed to the closest server. The problem is, there is only one server in Australia, and no servers in Asia, Africa and Antarctica. If you have a server in one of these regions, and if can open port 8000 in- and outgoing, please contact us, as described in this mail. Clients will use about 300 kbit/s each. As soon as the geoDNS is in place, I’ll blog again and publish the URL, so that you can watch us testing… :-)

Bernd Zeimetz: debcamp hacklab

debcamp hacklab Although we ve moved into a different room a few minutes ago, here s a little pano from yesterday, thanks to tokkee s cam, hugin, autopano-sift and gimp :-D Update: Here s another hackish pano of one of the hacklabs we re using since today. The stitching is not perfect again, I ll probably fix this when I m home again - or not ;-)

14 June 2007

Sergio Talens-Oliag: Pending sysadmin posts

Since some weeks ago I've been thinking that I'm not writing on my Blog for long periods, mainly because I don't have too much free time and generally I don't have interesting things to say. Anyway now I'm starting to believe that I should write more, at least about technical matters; I've been doing a lot of system administration tasks lately and probably it is a good idea to keep a log of the things I've tried and learnt on this Blog, as my notes can be useful to others or at least for myself. I'm going to bed now, but lets start by enumerating some of the things I must Blog about: The things I would like to look into, if I find the time: And the Operating System I'm using to test all those programs:

Joachim Breitner: screen-message uploaded to Debian

By popular request (if you consider Lunar to be a pupil) I have packaged my old hack vlshow as screen-message to Debian. The small program (called sm on when installed) starts and displays a given text as large as possible, in big bulky black letters on white background. You can change the text while the program is running. This might be useful to quickly send a message across the room, say something to people who think they are reading your screen unnoticed, for make-shift signs, to marvel at nice unicode characters and all kinds of other funny purposes.
I used this as a chance to try out darcs-buildpackage, which is very nice, especially as it makes the separation of upstream sources and Debian changes possible in a non-troublesome way. I attended Enrico s tutorial on autotools and autotoolized the package during that talk, which meant that I could use cdbs for building the package nice experience as well. Darcs s dist feature is very nice when using autotools, although it makes darcs-buildpackage slightly inconvenient. (While dpkg-buildpackage uses darcs dist on the upstream sources to build the orig.tar.gz, it does not check the predist command in _darcs/pref/pref when building the debian package, which fails then. It works fine if I run that command, in my case predist autoreconf -i && rm -rf autom4te.cache/, before running dpkg-buildpackage.)The package is currently in the NEW-queue, until it was accepted, you can find packages on people.debian.org. Thanks to Lunar for some patches. I m keen to hear interesting stories about how and where you used the program.

Daniel Stone: avivo and donations

Just a quick note to say a huge thanks to everyone who's offered support (financial, hardware-wise, or just verbal) to the r5xx project -- we really appreciate it. A couple of FAQs:

  • Thanks! Where can I send money?
  • Sadly, money isn't the issue: we have jobs/university theses/lives to tend to. We just lack for time right now.

  • Thanks! Where can I send hardware?
  • If you have a card that you won't be needing back (we may lose or fry it), please email myself (daniel@fooishbar.org) and J r me (j.glisse@gmail.com), detailing what you have, and we'll get back to you if it'll be useful to us.

  • Will this work with the X2xxx cards (r6xx)?
  • Yeah, pretty much. It just needs someone to hack up the small amount of code to deal with it.

  • What's happening with X1650 and above (r530/r580)?
  • Most of the code is written, however, initialisation doesn't happen correctly for some reason.

  • What's happening with 3D support?
  • It should be relatively simple to implement from the existing driver, as the engine is believed to be extremely similar, but we want to get the basics working before we start attacking things like this.

  • Which tools do you guys use?
  • For tracing the video BIOS, we use a hacked version of xresprobe: vbetool will instrument the BIOS quite well. For tracing fglrx, we use a hacked version of valgrind: run it against the X server, making sure that it is not suid root. For getting impatient and playing with registers, we use avivotool.

  • Where does the development happen?
  • On IRC, #dri-devel seems to serve somewhat as the ATI development centre. This gets fairly well coalesced into The Irregular Radeon Development Companion, however, so you may prefer to just follow that.

  • Shouldn't all this be on a wiki page somewhere?
  • Yes, but I have to get up in less than four hours.

    Once again, thanks for the support, from all of us. It's been great.

    Gustavo Franco: debcamp updates - round III

    There's a lot more bits but I can't remember everything, oh I've also met siretart. :-)

    Stefano Zacchiroli: yay for debconf7

    Yay, I'm here Lot of things happened preventing me to post the obligatory "yay for debconf" on Planet earlier (just to mention one: my DSL provider was incredibly fast in disabling my connection, and godog who remained at home is probably thanking them for that as well...). Anyhow ... I'm here! Meeting again all of you guys is terribly cool, thanks you all!! Ah, by the way, since people are asking: no, I didn't come here by motorbike. Actually I started planning the trip a while ago and summing up the needed money. When, counting in euros, I reached the 4th digit I stopped counting and decided to came by plane :(

    Nico Golde: libacpi-0.1

    After asking for testers of a libacpi snapshot I got a fair amount of test mails. Thanks to all the people who tried it and helped me!!

    Now I finished with coding, testing and documenting everything and happy to release version 0.1 of libacpi.

    It is a general purpose shared library for programs gathering ACPI information. It fully implements information about fans, batteries, ac states and thermal zones (apart from trap points).

    Try it out on: http://www.ngolde.de/download/libacpi-0.1.tar.gz.

    There is also an online documentation (well doxygen generated) on http://www.ngolde.de/libacpi/doc/html/.
    test-libacpi.c is an example on how to write programs using libacpi.

    For more information download the tarball, have a look into the manual, test-libacpi.c, README and the doxygen documentation.

    The next step for me is to port yacpi to libacpi which was also the reason for libacpi since I first wanted to rewrite it and thought it might be useful to have the functionality in a library. There are not yet Debian packages for it because I am really busy at the moment so if you want to maintain it, feel free to do so.

    Next.

    Previous.