Search Results: "ag"

15 April 2007

Martin Zobel-Helas: Advantage of murphy being down

… it is quiet in my INBOX…. :-) No Tags

Kai Hendry: Opensource Web applications

olpc web browser pointing to Webconverger Whilst downloading, installing and running Debian packages is easy, fun and “free”, most Web applications aren’t. I can’t be the only one that thinks there is a problem somewhere as for example, where are the all the Web applications listed on Freshmeat? I have an idea for a Web application though I thought it would be cool to make it as Free software though it can be a pain. I think there is a few more “barriers to entry” problems running a Web application as a free software project. Web hosting is generally quite poor and a lot of the Web centric deployment/packaging tools aren’t up to scratch. Though there are a couple of amazing examples of “open source” Web sites, like the stuff My Society do. Nonetheless I would like to see Debian as an even better Web application platform.

Kai Hendry: Opensource Web services

olpc web browser pointing to Webconverger Whilst downloading, installing and running Debian packages is easy, fun and “free”, most Web application services aren’t. I can’t be the only one that thinks there is a problem somewhere as for example, where are the all the free software Web services listed on Freshmeat? I have an idea for a Web application though I thought it would be cool to make it as Free software though it can be a pain.
  1. Getting a reliable host
  2. Host has to be Debian and probably unstable to get the bleeding edge stuff :)
  3. You probably want to have root, hence dedicated
  4. It is probably expensive and you might have to watch bandwidth
  5. You have to create accounts, where your colleagues also want root.
  6. You could use sudo though you’ll probably get frustrated with it and end up with “ALL = NOPASSWD: ALL” and no one checks the logs ;)
  7. You’re probably want Xen and a few IPs
  8. Since Web application packaging with current tools is near impossible with all the different httpds and DBMSes, you’ll probably have to use some odd hand crafted setup.
  9. You will probably want a DBA sooner or later, to figure WTF is going on with your DBMS ;)
  10. You’ll probably end up with a several step build&deployment process (that’s bad)
  11. Testing (if you ever get that far) will probably be a kludge
  12. To lower the barrier of entry, you will probably go for PHP which is great to deploy. Scary to secure.
  13. Though non-PHP avenues will probably require FastCGI. And FastCGI on Apache last time I checked is PAIN.
  14. Your developers probably can’t run the Web application locally as it such a pain to setup (esp. forget offline)
  15. You might have some “privacy policy” that makes sharing log or database data difficult amongst developers.
  16. Your Web application will probably need mail server access and all the pain that comes with that.
  17. Your application will have to deal with difficult abuse problems like spam that ordinary applications don’t usually deal with.
  18. If your project’s site becomes popular you’ll have a ton of maintenance and scalability head aches that will probably require money to be thrown at the problem.
  19. Someone will think your Web design stinks. Then if you use some “designer”, he creates some awful XHTML template and some fixed px style sheet with images replacing text. ;)
I think there is a few more “barriers to entry” problems running a Web application service as a free software project. Web hosting is generally quite poor and a lot of the Web centric deployment/packaging tools aren’t up to scratch. Though there are a couple of amazing examples of “open source” Web services, like the stuff My Society do. Any other good examples? Nonetheless I would like to see Debian serve as an even better Web application platform. Update: I think “services” makes more sense than “application” in this context… I hope you’ll agree.

14 April 2007

Thomas Viehmann: Cyrus IMAPd 2.3 and ANNOTATEMORE

Cyrus IMAPd implements annotations to mailboxes and the server. As shipped (in 2.3.7, the current upstream release, the Debian maintenance team on Alioth has preliminary packaging in their SVN, thanks!), the valid annotations are hardcoded. Having run an unpatched IMAPd since my own virtual domain patches were obsoleted by upstream supporting it, I've decided to write up a quick patch to make annotations runtime-configurable.

Thomas Viehmann: VoIP via SIP

Accentuation of foreign language by combination with acronyms and general technical idom. So now I can use the linphone software telephone in order to get cheaper rates for calls to a country where they speak yet another langue étrangère. The service provider only mentions kphone, but I had some problems getting the sound to work properly. Also, disabling the esound daemon esd works better than using esddsp as far as latency is concerned. Maybe I'll do a better writeup later.

Ben Hutchings: ACCU Conference

I've been meaning to attend the ACCU Conference for some years and finally decided to pay my own way for a couple of days this year. It was an opportunity to hear world experts on C++ and other programming topics and to a smaller extent to meet and socialise with other professional programmers. I attended the following sessions: Keynote: Improving Collaboration in Open Source Projects, Mark Shuttleworth This was a somewhat surprising choice of speaker and subject since I think most attendees work on proprietary software, but I think any sensible developer in the proprietary world will try to build on free libraries under non-copyleft licences, where appropriate. Mark talked about governance and leadership in "open source" projects (actually praising Debian for having a clear constitution) and about the need for good communication between projects, for example about release schedules. He seems to have accepted that Launchpad cannot be a single hub, and called for standard formats for, for example, exchanging information about related bugs between bug trackers. But it doesn't sound like he's ready to take the lead on that. Choose your Poison: Exceptions or Error Codes, Andrei Alexandrescu Andrei looked at the strengths and weaknesses of various error reporting mechanisms in C++ and introduced a technique for making error handling more flexible. Normally a function is designed either to indicate errors through its return value or to throw an exception on error. If a function returns an error indicator, it's easy for callers to ignore it. If it throws an exception on error, then a caller that provokes errors more often than the called function's author anticipated pays a high cost in processing time for those errors. Andrei's solution involves a class template Likely<typename T> whose instances hold either a return value of type T or an exception. A function that can fail has a specialisation of this template as its return type. The caller can check for failure if it knows how to handle it, or it can ignore it - in which case the conversion to T or the destructor will throw the exception. This is clever but doesn't seem to be entirely satisfactory. The destructor which throws does first check that no exception is already being processed, avoiding collision of the two exceptions and consequent abrupt termination of the program, but this can result in errors being unexpectedly ignored. Introduction to Component-Level Testing, John Lakos A marathon 3-hour talk on designing and testing software, particularly C++ programs (the subject of his well-known book) as a set of well-defined components. Lakos first defined these components as being "physical" i.e. sets of source files - normally a header file defining an interface, an implementation file, and a test driver file. They may also include metadata for the build system. He talked about the value of reusable components (as if this wasn't obvious!) and the risk of introducing circular dependencies - which essentially turn many components into one and reduce reusability - if we fail to keep track of dependencies. Software built out of components can be viewed as a hierarchy or stack defined by dependencies. In a large system, components with similar dependencies and dependents can be grouped together into packages or package groups to simplify a view of these dependencies. He explained that the test driver's dependencies count just as much as the implementation's, because we cannot reasonably test a component until we have tested its dependencies. Test drivers should also be written to avoid depending on environmental settings and configuration, so far as possible. Finally, and perhaps most importantly, he spent a long time talking about how to construct test cases and test data. I might try to summarise this in a later entry if anyone's interested. The Appliance of Science: Things in Computer Science that every practitioner should know, Andrei Alexandrescu Andrei began by complaining that OpenOffice Impress was even worse than PowerPoint, but being able to use Linux (specifically Ubuntu) more than made up for the pain. He briefly presented four key ideas that he believes programmers should understand and be ready to make use of: Writing for ACCU (BoF) I think I've been convinced to write an article about standardisation of multithreading in C++. C++ Threads, Lawrence Crowl Crowl gave an overview (similar to this) of the extensive work that's been done on standardisation of multithreading in the C++ language and library. This is one of the most important features in C++0x due to the increased parallelism mentioned above. The current semantics of multithreaded programs are not standardised, resulting in subtle but potentially serious differences between current C++ implementations that support multiple threads, and in the need for assembly-language code in programs that use lockless synchronisation. Much of this is also relevant to C and is being considered by the C standard committee. C++0x Initialisation: Lists and a Uniform Syntax, Bjarne Stroustrup Stroustrup recapped the 4 forms of syntax for initialising objects in C++, some inherited from C and some necessarily invented for C++, none of which are entirely generic. He noted the lack of a simple syntax to initialise the elements of containers, which violates the general principle that class types should have the same status as built-in types in C++. He then introduced a new initialiser syntax that he and others have defined for C++0x, which is a brace-enclosed comma-separated list of values, similar to that used for arrays and C-style structures (aggregates). Container types can define a constructor with a parameter of type const std::initializer_list<T> & and when constructed with this new form of initialiser they will receive this wrapper for a constant array of element values. For types that do not, the values in the list are treated as arguments to some other constructor, if one matches. Otherwise, for compatibility, this may be treated as aggregate initialisation. C++ Standard Library report, Alisdair Meredith There was far too much information here for me to even begin to summarise. Suffice to say there are lots of good things coming bu the library committee will have its work cut out to get them all properly specified in time for the Committe Draft coming late this year.
I also met old friends and new, put faces to names from newsgroups and books, and got too little sleep.

Meike Reichle: Spring

Chucks in a shelf

After wearing heavy shoes and army boots all winter, the first day wearing regular chucks again feels like walking barefoot.

It's spring! :)

Yves-Alexis Perez: Xfce 4.4.1

Ok, so Xfce 4.4.1 (bugfix release) is out since some days. I've packaged this new version, which is mostly ready in our svn. So 4.4.0 won't be uploaded to unstable at all, and we will upload directly 4.4.1 in sid in some days. The thing which blocked us to upload to unstable was gtk2.10, and it has been uploaded yesterday, so nothing is blocking now and we should be able to upload really soon.

The packages are available from my repository for ppc and sparc. I've changed the layout to add an UNRELEASED branch, so people using it are warned that those packages are even more unstable than unstable. Those packages are packages which have not been uploaded to debian, and thus may be unusable.

Alway prefer packages coming from pure Debian repositories, but if you want to test and help us correct mistakes, you can use the repository (and report bugs to our mailing list).

For etch users, I'll prepare 4.4.1 backports, but as I don't have hardware access, they will be only ppc and sparc binaries. Maybe other will be able to build backports for other arches.

Clint Adams: No stray snails in this picture

[rene@torre]

Adam Rosi-Kessel: Google Reader is the Solution

I was a long-time hold-out user of standalone RSS aggregators (SharpReader for Windows and Straw on GNU/Linux, both of which have been somewhat stagnant over the last couple of years). I’ve finally thrown in the towel and switched to Google Reader. It was a great decision. The key factor is mobility. I check email and blogs from my personalGoogle Mobile Image laptop; our kitchen computer; my office workstation; and, perhaps most significantly for Google Reader, from my cell phone. The Google Reader cell phone app is quite good (handy “keyboard” shortcuts, efficient presentation), and allows me to catch up during time that is difficult to use for other purposes: waiting for the train, standing in line at Starbucks, on the elevator. The only real downside is the lack of offline support (although I don’t think it would take a rocket scientist to create it), but this is far outweighed by the mobile functionality. As “access anywhere” becomes more important than “offline access,” I predict we’ll see more users of all applications make this sort of switch.

Junichi Uekawa: Booting from USB disks and why that's interesting.

I've decided I wanted to try running Debian on nc4000 (laptop PC by HP).I didn't want to erase what is already there, so I needed some external USB HDD to do that.Since I didn't feel like hunting around for a USB CD-ROM drive and creating bootable USB, or configuring PXE, I decided to install using qemu to install to the USB HDD and use that installation on the machine.It was surprisingly simple.I connected my USB-HDD to my desktop machine, which recognized the disk as /dev/sda, and I used qemu to install Debian on it. qemu -hda /dev/sda -cdrom XXXX -boot d.Note that you really need kqemu or kvm for speed.Then, I selected LVM, and installed.After initial reboot within qemu, I changed the kernel to a 686 kernel since a k7 kernel was installed, but that's the only package I changed.After reconnecting the USB HDD to nc4000, I managed to boot from the USB disk.Initially, it failed to boot since vgscan ran before USB disk was recognized, and could not find the root device.Looking at the source, I found initramfs will probably re-try after 3 minutes. But reading further, I found that the timing can be improved by specifying rootdelay= boot option to the kernel.I specified rootdelay=15 for the kernel option in grub,and voila, it found the root filesystem on LVM.The /boot filesystem was /dev/hda1 inside qemu, but it is now /dev/sda1 on the nc4000; and boot stopped at fsck on /dev/hda1.It was trivial to fix after dropping into the command-line.LVM is able to work around device name change, which is nice to know.For the graphics card, qemu and nc4000 have different cards, and I had to dpkg-reconfigure xserver-xorg.Okay, so I have Debian running on my notebook via USB HDD, now what ?

13 April 2007

Jose Carlos Garcia Sogo: TomTom Go 510... a Linux device!

TomTom Go 510 A couple of weeks ago my girlfriend buyed me a Tom Tom Go 510 a very popular car GPS navigation system here in Spain (mostly because goverment installed tons of radars for speed control). Today, searching for some info to see if it was possible to update the device using Linux, I discovered that the device runs Linux! So, without knowing, I have an embbeded device running Linux, and more than one million people have also a device running Linux. This clearly shows how Linux can be nice a solution for an embbeded commercial solution.

Meike Reichle: Sugar Eggs

Tolimar: It's okay! Some else took care of it! :D

a
package full of sweets

Thanks, aba!

Ingo Juergensmann: Should m68k drop the Debian distribution?

Debian Etch has been released lately, as you may know, and the work on Debian Lenny is already starting. For some of the DDs the work is way much different than for the rest of the DDs: the good ol' brave porters of m68k.
Stephen Marenka asked on debian-release what is needed to get back and be able to release with Lenny?
The answers are shaking:

1. To get back to testing: Basically, the release team didn't mind the
state we had with m68k in testing recently - basically, we just ignored
it, but it was still there. The release team didn't asked for full
dropping from testing, we just didn't mind either way. We also wouldn't
mind for m68k to be back in testing - as long as we can just continue to
ignore it.

2. To get released (or a realistic chance to): Basically, make sure that
the toolchain works (see the other mails), and get really fast buildds
(otherwise, the security team would probably veto the inclusion). The
second might happen with Coldfire, but - the how is your part, not ours
(i.e. if you do it some other way, that's ok as well of course).

Having said that, I can understand if the ftp-masters don't want to have
an architecture be in testing unless there is reason to believe it is
possible to include it in the next stable release, but that's not the
domain of the release team.


ad 1)
Ah, ok... as long as we are ignored, everything is fine. But how will testing m68k get updated when the testing scripts ignore m68k? Pardon me, but isn't this a little bit strange, at least?

ad 2)
Getting really fast buildds - good joke, indeed! Or is this a Friday, 13th habit like April Fools Day?

Conclusion)
Let's summarize: we can release with Lenny, when we get back in shape - but testing is needed for this, where we're ignored for. And without faster buildds for an arch such as m68k, there's simply no way back to make it into a release again - because of this.
Describing Coldfire as such a possibility for faster machine seems a little bit strange to me. CF is totally new, there's not progress yet on the CF front to my knowledge and a combined m68k/CF port may introduce other drawbacks, which nobody can predict for sure today. Do you really believe that ftp-masters or release team will allow such a port to get released? I don't.
Getting faster buildd in a reasonable amount of time is illusory for m68k. We can get more buildds online, but not "really fast buildds". Despite one older blog post of me, I'll receive just another '060 m68k soon (to be hosted by a fellow DD). A few days ago, two other m68k buildds were added to the m68k buildd rotation list. That will make 3 more buildds for the m68k.

Anyway, in most cases your first impression is the correct one and my first impression of the Vancouver Massacre/Proposal was: this is a plan to drop m68k!
Well, the lastest incidents confirm this impression, IMHO.
After all, I think that the m68k port would be best served by dropping Debian instead of being dropped by the project. The m68k port - de facto - has been dropped already. I'm disappointed.

Luk Claes: Not getting into Spain

Waking up at 5am (I know, not a decent hour, though I don't choose when a plane leaves), cycling to the railway station with all my luggage (no buses drive that early...), taking the train (actually 3 trains as there are 2 stops) for 1.5h, arriving at the airport, hearing about some strike, checking in and being told strike will be over when my plane takes off (9am), waiting, plane being delayed till 10am, waiting, plane being delayed till 11am, waiting, plane being delayed to 1pm, eating, waiting, plane being delayed till 3pm, queueing for information (which was going to take ages), plane being cancelled. Apparantly some firemen didn't like that they didn't get food tickets nor paid overhours :-( I should have known that taking a plane to Spain is risky. My previous attempt: ... arriving in the airport, trying to be checked in, being told that tickets have been cancelled, making calls, being told that travel agency forgot to confirm a second time and that new tickets have been booked for 2 days later, going home, night before take off seeing that ticket to Spain has been cancelled (ticket back still valid), going to the airport anyway, being called that everything is ok, arriving at the airport, being told that I have 2 tickets for the same flight... Sorry to the people who expected me to be in Spain, I'm not going to try my luck again tomorrow, though I'll try to be happy on IRC :-)

Erich Schubert: DBus init changes

Just yesterday I mentioned that DBus contains an own set of init-like scripts. From todays new DBus package in unstable:
  * debian/dbus.init
    + Add functionality to start/stop dbus dependent services based on their
      LSB header.
      Instead of installing an init script into /etc/dbus-1/event.d, services
      depending on dbus should from now on install a regular sysv init script
      and add an LSB header with "Required-Start: dbus".
So the dbus init script now adds a 'workaround' (likely, since this is done in DBus, not in sysvinit) for the missing dependency handling in sysv-style init, by taking care of the restarting itself. This is good, because init scripts aren't distributed into two places anymore (soon).It probably highlights why we need to work on our init.

Sven Mueller: Init HackFest / New init systems in Debian

In his “Init followup” post, Erich posted a reference to his Debian-Wiki post about a proposed Debian HackFest after Etch was released (which would be about 5 days ago<smile />). Anyway, since that page at the wiki is protected, which means I can’t edit it, I’m posting my thoughts here. I agree with Erich and some other commentors at Gunnar Wolf’s blog post that it doesn’t make sense to add X init-script-only-packages for any daemon to support X init systems. Instead, each package containing one or more daemons should contain the meta information needed to create all init scripts. Basically, this would probably include script snippets which do the following operations: Additionally, some control information would be needed including, but probably not limited to: The script snippets listed above should allow basically any operation on a daemon, including the force-reload and try-restart commands not yet implemented by all current sysv-initscripts.

MJ Ray: Blog Tools 1: the Aggregator

I just rewrote my aggregator (schcyrssmerge2) which still works roughly on this algebra from 2004 (still the basic set theory rule of blog aggregate generation: aggregate_i+1 = (blogs/aggregate_i) u (aggregate_inblogs)) but now calculates agg1 a different way. First, there's agg0 - the items from the input RSS file - and I store only the post ids of agg0 as agg0i for speed. Previously, I was reading in all the blogs and doing the above set theory calculation in one go. With a couple of ill-behaved blogs (full-content feeds of a few hundred kb), mzscheme's memory usage was just getting silly, topping out at hundreds of megabytes to merge 4Mb of feeds into a 3Mb aggregate. I think some of the problems are PLT's - reading a 3Mb RSS file in with
"(define a (call-with-input-file "friends.rss" read-xml))"
seems to result in mzscheme (v352) holding 100Mb. What's with that? Anyway, now I've written a newitems function which extracts new items not listed in agg0i and old items which still appear in a blog and adds them to lists. Then, there's a function which tail-recurses over all the blog filenames, parsing the RSS, calling newitems on each one and building the lists of old and new items. Finally, agg1 is the new items appended to the old items. That is only calculated as it gets written out as a RSS file. I'll give it a few days of testing, then I'll publish a tarball. I use this to build my all.rss feed from my various source feeds, in case you didn't realise, as well as to run some planets for public and private use. Anyone got a suggestion how best to reduce the read-xml memory consumption? Upgrade? Switch dialect? I'd like some XML read/write functions and the SRFI list functions.

John Goerzen: And we're off!

Yesterday afternoon, we started our information meetings with employees about our Linux on the desktop project. We're underway on our migration.

But before I talk about that, I need to back up and describe what the project is.

We are converting approximately 80% of our 150 or so PC users to Linux desktops. They're Debian etch (4.0) running Gnome, Firefox (Iceweasel), Evolution, NFSv4, and SystemImager. Over the coming days and weeks, I'll be writing about why we're doing this, how we're making it happen, things we've run into along the way, and the technology behind it.

Today I'd like to start with a high-level overview of the reasons we started investigating this option.

It became apparent that Vista was going to be a problem for us. Most of our desktop PCs are not very old, but Vista meant a significant degradation in performance from the Windows XP Pro that most people were running. A performance dip so significant, in fact, that it would have created a significant negative impact on employee productivity.

We tend to buy PCs with Windows licenses from the vendor (Windows preinstalled). As such, we knew it wouldn't be long before XP-based machines would be hard to find. If we stuck with Windows, we'd be running a mixed-OS network -- which we knew from experience we did NOT want to do. The other option would be to replace all those old PCs. The direct costs of doing that, with the associated Vista and Office licenses, would have been more than $200,000.

So we started to look at other options -- changing the way we license Windows, sticking with XP for awhile, or switching away from Windows. This last option sounded the most promising.

I took a spare desktop-class machine, representative of the hardware most end users would have, and installed etch (then testing) on it. I spent a bit of time tweaking the desktop settings, making things as transparent to the user as possible. We liked what we saw and started pursuing it a bit more. We knew we had some Windows apps we couldn't discard, so we tested running them off a Windows terminal server with the Linux rdesktop client. That worked well -- and the appropriate Server 2003 licenses plus CALs would still be far cheaper than a mass migration to Vista.

To make a long story short, we are getting quite a few benefits out of all this. One of the most important is a single unified system image. Excepting a few files like /etc/fstab, every system gets a bit-for-bit identical installation from the server, updated using rsync. /home is mounted from the network using NFS (v4). So our users can sit down at any PC, log in, and have all their programs, settings, email, etc. available. A side benefit is that hardware problems become minor annoyances rather than major inconveniences; if your hard disk dies, we can just bring up a different PC. We had tried numerous times to make roaming profiles work in Windows, but never really achieved a reliable setup there -- perhaps because it seemed virtually impossible to assure that each Windows PC had the exact same set of software, in the exact same versions, installed.

More to come.

Joachim Breitner: Big Brother for your Window

I just read about this really cool hack: He installed the well known Unix-Tool xeyes in his window no, not Windows, window. The thing to look out of your room if the shades are not down. (Video available)The effect is that the innocent bywalkers on the street will feel, well, watched. Not like otherwise where they probably are watched and don t know about it. Might be a very cool gimmic for privacy related PR actions, or just to generally protest against state surveilliance...

Next.

Previous.