Search Results: "ag"

11 April 2007

Eddy Petrișor: finally, I can get rid of filelight!

The desktop enviroment is not a religious thing for me. IMHO, they all (3 of them) have missing parts which are present in the others. I never really used Xfce.

OTOH, I have been switching back and forth between GNOME and KDE during my time as a GNU/Linux user. Since I always found that one of the environments was missing things which were present in the other, I think I have switched at least 3 times both ways by now.

Now, with the release of GNOME 2.18, I will have one less reason to think to move away from GNOME, which is the current desktop environment. One of the apps I was missing in GNOME was a filelight-like application that would show usage in a very intuitive graphical way. Now it seems that baobab (commonly known as Disk Usage Utility) has a ring chart similar to filelight's. Yay!

Now, if somebody would take the task of rewriting granslator, I would be more than glad to drop kbabel...

Note: I was disapointed that GNOME Space Chart never made it to public... that disappointment lasted until now.

Stefano Zacchiroli: post etch frenzy

Post-Etch Frenzy: Ocamlnet 2.2.7 in Unstable Ok ok, ..., I admit it, I'm yet another victim of the post-release frenzy: right now I'm uploading to unstable the long overdue packages of Ocamlnet, 2.2.x series. Since the former upload to experimental there were 3 micro releases (now we are at 2.2.7), which also added support for the apache connector for CGIs (which unfortunately doesn't yet build cleanly with Debian's apache2 :-/ I'll have a look at it in the near future). In the meantime the post-etch madness continues: with the help of other fellow DDs from the Debian OCaml Task Force (thanks for your help Ralf!) I'm working on the packaging of the beta of OCaml 3.10.0. Expect an upload to experimental in the next few days. All this is tiresome though, enough for today, time for some good old sci-fi book ...

Jordi Mallach: The big Debian news I missed last weekend

I've been a bit offline during the last two weeks due to being in the middle of a ISP switch at home, which took me offline for a longer time than expected. Additionally, when I finally got the connection up, it was Easter time, and I ended up going to Vall, after cancelling a cycling trip with some friends down the Via Verda Ojos Negros (but this time, not during the night and spending a few days to complete the route) in the last minute, due to the horrid weather forecast. It apparently was a good idea: the river that goes along Vall overflowed, and for some reason the mobile phone service went down for more than 3 days. On Monday night I came back to Val ncia, and I figured that the DPL election results would be out by the time. When I opened Debian's webpage, I found out some other big news: Debian 4.0 was released the day before! Soon after, I looked for the vote results, to find Sam, my candidate of choice, was the winner, very closely followed by uncle Steve. Congrats Sam, no nos falles! And congratulations to the rest of the Debian project for yet another successful, well done release. Reading comments on news sites gives a fuzzy warm feeling. Even though we were slightly delayed, people show how etch is going to make their lives easier, or how trustable Debian is at work and at home. That's the kind of stuff that keeps me and many Debian people going. I'm pondering improvising some Etch Release Party (as the release managers deprived me of a IRC party by secretly releasing while I wasn't looking) this weekend in Barcelona, where I will be visiting, after giving up on being able to be in A Coru a for DudesConf. Anyone up for it?

Luk Claes: No Mail

Something went wrong with my mailserver (configuration?) today. So if you got a bounce or are wondering why I didn't answer a mail you sent today, feel free to resend the message as I changed the forwarding to another email address for the time being.

Simon Richter: automake for the win

I wonder what on Flying Spaghetti Monster's green earth compels people to write their own build systems for no good reason. And yet, you still can do worse: you can adapt someone else's system to the point where it works for you. Which is why busybox shows "kernel source is at (path to busybox source)" when beginning to compile. And the pain only grows from there.

Kai Hendry: Webconverger 2.4

Korean Webconverger split 2.4 I’ve just released Webconverger (Web kiosk) USB&ISO versions built with stable Debian etch. Webconverger has received some good feedback and press. I would like to thank Daniel Bauman for his rather excellent Debian Live work on which Webconverger is based. I was hoping that Webconverger could support every locale, now it looks like I need to produce a separate ISO/IMG (or at least apt-get hooks) for every locale. One reason is that Iceweasel/Firefox extensions don’t scale very well. Try install every locale and dictionary extension. I dare you. :) Sidenote: I wonder why no one has packaged the dictionaries for Iceweasel. In other news, I’ve been playing around with scim (keyboard switcher) and Korean locales. It seems to work though the title bar didn’t render hangul characters right in dwm. After some investigation I discovered there isn’t such a thing as a single “generic” Unicode font. This came as a shock to me. :) Typical ttf only have 65536 glyphs, so no one font will do. Jeff Zhang also informed me about free Unicode fonts. Though I think especially in CJK environments proprietary fonts are unfortunately more common. Or I don’t know why microsoft-gulim isn’t in msttcorefonts. Anyway the Korean version of Webconverger turned out OK, though I doubt any Koreans will be using it. It’s all sadly ActiveX out there. My package wordpress 2.0.10 didn’t quite make it to etch in time as I was waiting for CVEs! 2.0.10 will be coming soon though… It always amazes me how much work can get done in breaks like Easter. It’s great that etch is out. And whoa, the weather is great.

Clint Adams: And everyone was pervy, oh yeah, and the message was spread

The New York Post is such a fine periodical.

Erich Schubert: System init - part #2

Yesterday, I wrote about our init actually being /bin/sh, since all sysvinit does it start a single shell script. Today, I'm going a bit into how services are brought up with sysv-style init. I won't be writing much about runlevels, since most users will not make use of multiple runlevels anyway. So what does a typical init script in /etc/init.d do? If you want to find out yourself, consider looking at /etc/init.d/skeleton, which is a template for init scripts. A modern init script should (as required by the LSB) start with a formatted comment with metadata such as dependencies and description. This is already trying to address some shortcomings of sysv-style init, but no actual code. The first thing most init scripts do is to check if their application is actually still installed. Init scripts are sometimes created by users, or are not automatically uninstalled since being treated as 'configuration files'; so it occurs often that the init script is still around even when the service was uninstalled. So they test if they're installed and executable. Next they probably read a configuration file, usually named /etc/default/packagename, with user settings (people used to do such changes in the init script itself, but for upgrading it proved to be a lot better to put all settings the user might want to modify there). The third step is to do the requested user action, which usually is one of 'start', 'stop', 'reload' and 'restart'. Some init scripts also have extra actions such as 'status'; not all init scripts support 'reload'. Doing such an action usually means to print out a status message and launching the service in the background (usually using the 'start-stop-daemon' daemon helper, which offers functionality to e.g. record the process PID in a file or forcing applications into the background that don't do so on their own), or locating the service (usually via a PID file, again this is commonly done using start-stop-daemon) and reloading or stopping it. Upon success, they again print a status message. An init script could be as simple as:
#!/bin/sh
if [ "$1" = "start" ]; then
  /usr/local/sbin/mycheapdaemon &
fi
There are many good reasons not to do it that way, but it will work. Some characteristics of sysv-style init scripts: Keep your eyes open for the next part of this series, where I'll show how some init systems improve on these issues.

Erich Schubert: System init - part #2

Yesterday, I wrote about our init actually being /bin/sh, since all sysvinit does it start a single shell script.Today, I'm going a bit into how services are brought up with sysv-style init. I won't be writing much about runlevels, since most users will not make use of multiple runlevels anyway.So what does a typical init script in /etc/init.d do?If you want to find out yourself, consider looking at /etc/init.d/skeleton, which is a template for init scripts.A modern init script should (as required by the LSB) start with a formatted comment with metadata such as dependencies and description. This is already trying to address some shortcomings of sysv-style init, but no actual code.The first thing most init scripts do is to check if their application is actually still installed. Init scripts are sometimes created by users, or are not automatically uninstalled since being treated as 'configuration files'; so it occurs often that the init script is still around even when the service was uninstalled. So they test if they're installed and executable.Next they probably read a configuration file, usually named /etc/default/packagename, with user settings (people used to do such changes in the init script itself, but for upgrading it proved to be a lot better to put all settings the user might want to modify there).The third step is to do the requested user action, which usually is one of 'start', 'stop', 'reload' and 'restart'. Some init scripts also have extra actions such as 'status'; not all init scripts support 'reload'. Doing such an action usually means to print out a status message and launching the service in the background (usually using the 'start-stop-daemon' daemon helper, which offers functionality to e.g. record the process PID in a file or forcing applications into the background that don't do so on their own), or locating the service (usually via a PID file, again this is commonly done using start-stop-daemon) and reloading or stopping it. Upon success, they again print a status message.An init script could be as simple as:
#!/bin/sh
if [ "$1" = "start" ]; then
  /usr/local/sbin/mycheapdaemon &
fi
There are many good reasons not to do it that way, but it will work.Some characteristics of sysv-style init scripts: Keep your eyes open for the next part of this series, where I'll show how some init systems improve on these issues.[Update: next part]

Lars Wirzenius: Debian: Etch release party in Helsinki

To celebrate the etch release in Helsinki, come have a few beers in bar Teerenpeli in Kamppi after 17 on Friday, the 13th. Everyone is welcome, this is not just a developer event. See the etch release party wiki page for updates.

Holger Levsen: joy and pain

My plan for coming home yesterday evening was simple: go to init 1 on my laptop and do a full backup while I sleep, followed by a reinstall with fai in the morning. That part of the plan worked pretty well: after less than then an hour of work, aeh, actually waiting and having breakfast, my laptop is 100% setup as it was yesterday, running shiny beryl on etch and all the configuration is the same as it was yesterday. Yay! Looks, feels and is the same system, but the installation is 60min old. So much for the joy.

The pain also started when I came home yesterday: the datacenter where my server is hosted had a huge power outtage yesterday evening and this morning there were and currently still are some hundred customers getting their machines up again. I wonder what exactly happend to turn off the power for a whole datacenter (they have megawatt sized diesel generators for power backup) but at least I'm happy it's not a hardware failure on my server. And while my server and services is up again since more than an hour, www.aol.de, which is also hosted there, is still down ;-) Update: The power was only gone for 40min, the rest of outtage is still a bit of a mystery to me: outgoing connections worked fine, incoming not at all. So I'm not really convinced that it wasn't coincidence that the reboot fixed my server...

MJ Ray: Satellite TV and Media Links for 2007-04-11

Ofcom publishes research on media literacy
Analysis of a research report: "Certainly a useful document to have on hand, if only to deconstruct."
Karen Bremner - The Apprentice Series 2
A new art form: go on a reality TV show, start blogging to raise profile, get hired by Old Media, then leave the site to bit-rot. How many of these "reality TV star headstones" sites are there now?
predicts problems and confusion for consumers
If anyone doubts how much big media gets bad PR from trying to use their big influence to direct the market (such as making their films only available in their format), check the first comment: "I'm waiting for the corporate idiots to decide"
xmltv, was: [Debian-uk] Getting wired in Manchester
Another thing on my "must try that when I get my DVR built" list.
theLargePrint.com The New Media Landscape and the BBC's Lost Horizon
Nice criticism of BBC's link-up with anti-competitors. I recently wrote about the BBC-Google link, which raises some similar problems.
BBC NEWS Business Fewer charges for website content
Figures from 2006 (I'll do media linkposts more often in future).
Time to read the papers?
I only get time to read one paper per week, unless I'm travelling.
Number 10: Tony Blair Interview with Stephen Fry
Fantasy TV shows number 10: A bit of Fry and Blairie.
BBC NEWS Technology Broadband switching set to ease
They say new rules came in on 14 February, but sites like moneySavingExpert.com are still full of tales of woe.
We the undersigned petition the Prime Minister to ban tv competitions/quizzes which charge extortionate caller rates (eg The Mint).
Sign this to clear UK digital TV of all these scam quizzes. I see that after just a taste of humble pie, itv play is back on air overnight on itv1.

Roger So: Debian etch released!

etch is finally out of the door! Hooray! Congratulations to everyone involved, forget about what the /. crowd is saying, this looks likely to be a very solid release. If you happen to be in Hong Kong, there will be a Debian etch release party this Sunday afternoon. Please do come along, it’ll be fun. :) I’ve also translated the etch release announcement into Chinese, but it seems a bit more work needs to be done before it will appear on the Debian website. In the meantime following is a copy of the Chinese translation: (more…)
Tag:

Russell Coker: Xen and SE Linux - EWeek review of RHEL5

The online magazine EWeek has done a review of RHEL5. It's quite a positive review which can be summarised as "good support for Xen as service (not an appliance), better value than previous versions with the licenses for multiple guests included, and SE Linux briefly got in the way but the Troubleshooting tool fixed it quickly and easily".

The problem they had is that the SE Linux policy expects Xen images to be in /var/lib/xen/images, but the Xen configuration tools apparently didn't adequately encourage them to use that directory. They stored the images somewhere else and SE Linux stopped it from working. The Troubleshooting tool did something that they didn't describe and then it all worked.

Generally a very positive review of RHEL5 and a moderately positive review of SE Linux in RHEL5.


PS You might have to turn off JavaScript to view the link, the page has broken JavaScript code that takes an unreasonable amount of CPU time.

MJ Ray: Webmastering: Translation

hair transplant commented:
"to blog in different languages, we need and on line translator, I think"
in reply to my old question about multilingual blogging. Like many multilanguage speakers I know, I don't hold out much hope of machine translation becoming useful any time soon. Systems like systrans can be useful for getting the basics of a message when you're totally stuck, but babelfishisms are a well-known danger (or comedy source, depending on what you're doing with it). So we're left with the question of how to blog in multiple languages without annoying the hell out of everyone. Do aggregators support content-negotiation? Should we use bertilow-style consecutive translation? Or simply run multiple blogs? I'm still only blogging in English. I probably should experiment. What's the state of this art now?

MJ Ray: Online Banking: What works with GNU/Linux? (12)

Added: Banco R o, ING Bank l ski, mBank, Sparkasse I notice that Jonathan's earth.li presence: Planned bank outages notes Cahoot's good approach and asks about others. I've sometimes seen announcements on the web pages of NPBS and Co-operative Bank, but no email unless it appears in their routine email newsletters. How about others? (I've posted this comment here because the presence is a login-to-comment site.)

Michael Koch: Yesterday I was happy about SUN

Yesterday I was happy about SUN, because I saw an announcement that WTK 2.5.1 was released. And it includes a Linux version. The versions 2.3 and 2.5 were Windows only. The only available Linux version was 2.2. It worked nice but missed some features and had an annoying bug that signing of midlets were not possible. This bug was introduced in WTK 1.1 and fixed in WTK 2.5. Today I download WTK 2.5.1 for Linux and installed it. I tried to run a first midlet and got this error message:
java.lang.UnsatisfiedLinkError: /home/mkoch/local/WTK2.5.1/bin/sublime.so: /lib/tls/i686/cmov/libc.so.6: version  GLIBC_2.4' not found (required by /home/mkoch/local/WTK2.5.1/bin/sublime.so)
        at java.lang.ClassLoader$NativeLibrary.load(Native Method)
        at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1751)
        at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1647)
        at java.lang.Runtime.load0(Runtime.java:770)
        at java.lang.System.load(System.java:1005)
        at com.sun.kvem.Sublime.(Unknown Source)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
        at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
        at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
        at java.lang.Class.newInstance0(Class.java:355)
        at java.lang.Class.newInstance(Class.java:308)
        at com.sun.kvem.Lime.createLime(Unknown Source)
        at com.sun.kvem.KVMBridge.(Unknown Source)
        at com.sun.kvem.KVMBridge.getBridge(Unknown Source)
        at com.sun.kvem.midp.MIDP.run(Unknown Source)
        at com.sun.kvem.environment.EmulatorInvoker.runEmulatorImpl(Unknown Source)
        at com.sun.kvem.environment.EmulatorInvoker.main(Unknown Source)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at com.sun.kvem.environment.JVM.main(Unknown Source)
I run a pure Debian Etch system as my desktop. So its not too old. I know there are releasons for etch not to include Glibc 2.4. Thats really okay. But I really wonder why builds against Glibc 2.4? What feature introduced in Glibc 2.4 is needed? I guess none.
They are just stupid and built against a new, shiny Glibc without caring about their users. SUN: Please care about your users and release a new build against Glibc 2.3 soon. Not everyone will update his/her development machine just to be able to run WTK. When you release proprietary software, do it right. If you are not able to, make it open source, so the community can fix it.

Edd Dumbill: James Clark joins Planet XMLhack

The news that James Clark has started blogging has been universally and justifiably well received. I've now added him to Planet XMLhack for your XML-focused viewing pleasure.I'll be following eagerly. Clark has a refreshingly clear and considered viewpoint, free from many of the tribalist undercurrents polluting today's technology blogging. 

Maximilian Attems: Happy switch from bzr to git

The cardinal reason for the switch is collaboration: git scales. During my bzr usage time of the last year i observed the following shortcomings of bzr:
  • Speed - This improved a bit lately but not enough for my q&d usage.
  • Documentation - Beside the obvious "svn-style" commands the usage of the other commands isn't obvious and the man pages lack examples. git is not perfect in that regard, but you quickly find typical usage pattern on wiki tutorials or on many google hits.
  • Pager - On big diff output bzr doesn't pipe that to pager^Wless. I consider that as a big usability bug.
  • Branches - I recently learned that a bzr repository corresponds to a git repo with just one branch. This seems strangely complicated. I really love to have different branches ready to checkout in my pwd . This short-coming blocks cooperation as i'm not confident enough to fetch random changes from bug reporters in my own branch.
  • Minor Nitpicks:
    * Push command - Defaults on the non-obvious old sftp protocol. Worked with rsync on some very ancient version.
    * Repo format - Changes on every major upgrade.
    * Patchlevel - Probably for svn compat reason the chosen default patchlevel is -p0 not -p1.
  • Latest initramfs-tools repo is available at:
    git clone git://git.debian.org/git/kernel/initramfs-tools.git Thanks to tailor it is now possible to move from different version control systems. For git as target repository it is recommended to use latest upstream either directly via darcs or at least install the unstable version. The etch version throws strange python backtraces.

    Joey Hess: boring blog rearragement notice

    I've changed the urls of everything in my website, including the blog. Feeds are limited to displaying new items to avoid flooding aggregators. Old urls will continue to work thanks to rewriting, and the rss feed url didn't change at all for the main blog (though some of the minor feeds urls did change and will redirect). Nothing you haven't seen a million times before, move along..

    Next.

    Previous.