Search Results: "ag"

17 January 2008

Wouter Verhelst: ... in sickness and in health ...

That's how I'm passing this week. What? No, I'm not getting married. It just feels like my body isn't quite sure whether it wants to be sick or not. On monday, I got down with influenza, mostly in the stomach area. Not only does that hurt and feel awfully bad, it also involves your yesterday's lunch reversing direction halfway through the digestive system, and finding the wrong way out. Some people call that puking. Being restless, doing nothing, I tried to do some work for Debian. Bad idza. Now usually, when I get sick, I get really sick. For one day. The next day, I can work again. That doesn't mean I'm at my best, but at least I can handle some stuff. So on tuesday, I went to work, since I had this appointment on wednesday and I still had to prepare some stuff for that. I made the mistake, however, of not dressing warmer than usual. With my body still recovering, and with the extra bad weather in the evening, I caught a bad cold. So on wednesday, I stayed at home. Lucky for me, customer had asked to postpone the appointment on wednesday to thursday, since he wasn't going to get everything ready in time otherwise. Me, I was still feeling the leftover sickness from the influenza, and now this cold was tearing me down. But as before, after one day I felt much better, so I thought I'll just dress much better this time, go to that appointment, and make the best of it. I figured it couldn't be that bad. Except that in a data center, the temperature is optimized for computers, not for sick human beings; and nobody cares about the noise, or about the fact that trying to yell above said noise isn't a very good idea if your voice is having issues because of some virus. I guess the only nice thing that happened this week was that nice lady on the train who gave me a clean handkerchief when my own was... well... you don't want to know. Tomorrow, I guess I'll just stay in bed. And on saturday, and perhaps even sunday, too. Get this week over with.

Norbert Tretkowski: Some packages up for adption

Due to lack of time and interest these packages are up for adoption: dog (bugs), lslk (bugs), nast (bugs), newsgate (bugs), nullmailer (bugs) and pyblosxom (bugs).

Drop me a mail if you're interested in taking over one of these packages.

Ingo Juergensmann: SA Basics

As there are some threads on the lists of enhancing Debian from time to time in various aspects and the upcoming DPL election period in some weeks, I found some memorable quotes in the book I'm reading at the moment:

Note: SA = System Administrator

The number-one attitude problem among SAs is a blatant disrespect for the people whom they are hired to serve. It is surprising how often we remind SAs that their users are not "lusers" or "pests with requests." They are the reasons why SAs have jobs. SAs are there to serve but, more important, to advocate for these people. [...]
We advocate that SAs stop using the termin users and replace it with the term customers. This becomes a reminder that SAs are in a service industry, supporting the needs of these people instead of "pests" who make request all day.

(From: The Practice of Network and System Administration, Limoncelli, Hogan, Chalup, Second Edition, page 756)


Communication:

  • I will communicate with management, users, and colleagues about computer matters of mutual interest.

  • I will strive to listen to and understand the needs of all parties.


(From: The System Administrator's Code of Ethics in The Practice of Network and System Administration, Limoncelli, Hogan, Chalup, Second Edition, page 325)

SAs do many tasks, but often, customers see only the parts that involve responding to their requests, not all the back-office work, and shouldn't have to see it. Therefore, how well you respond to customer requests is critical to maintaining an organizations reputation.

(From: The Practice of Network and System Administration, Limoncelli, Hogan, Chalup, Second Edition, page 364)

I don't know whether someone read this book as well lately or received another a proper christmas gift, but apparently someone found the time, finally, to fix the access to incoming.d.o for m68k buildds.

Thanks for giving access back! Yay! :-)


John Goerzen: DjVu: Almost Awesome

Earlier today, I started reading about the DjVu family of document formats. It really sounds slick: file sizes much smaller than PNG (and incredibly smaller than TIFF or PDF) for lossless data with the DjVuText format, file sizes much smaller than JPEG with equivalent quality for the DjVuPhoto format, and an advanced DjVuDocument format that separates the background photo from the foreground text and produces a quite nice output. There are wonderful plugins for browsers on all platforms, and server-side support already in Debian for sending pages incrementally as needed by clients.

I tried this out a bit and indeed it looks great on monochrome scans, and I made a quick try of DjVuPhoto as well. That part looks great.

So here's the bad news.

Debian has no nice way to generate DjVuDocument files. There is a PS/PDF-to-DjVu converter that uses a djvu driver for Ghostscript. But Debian does not include that driver. Though, strangely, the program that depends on this driver is actually in Debian main. (Bug filed.) That program actually will make background-separated images, but only if they are separate objects in the input.

All Debian has is a program csepdjvu, which requires you to somehow manually separate the foreground and background images. Ugh.

So there is no way using software in Debian to produce DjVuDocument files with automatic separation, either from scans or from a digital source. It appears that there may not be Free Software to do this from scans either. This fact is not made clear at all in the DjVu documentation that is around.

Francesco P. Lovergine: Vlogger with a named pipe

In an old post I dealt with the nice mod_chroot module to secure your multisite server. I also adopted recently vlogger in order to manage better apache logs for virtual hosts, when you have dozens or hundreds of them. Unfortunately the suggested way to use it (a simple piped command) does not work nicely with mod_chroot, because the piped command has to run in the chroot jail.

Of course, it is not a good idea installing the whole perl intepreter and all required modules in a minimized jail, so I adopted an oldish classic trick (the old things are always the best) to solve the issue: using a named pipe. You basically need to do something like the following:

mkfifo -m 600 /var/run/apache2/logger && chown www-logs /var/run/apache2/logger

cat /var/run/apache2/logger /usr/sbin/vlogger -u www-logs -g nogroup -s access.log /var/log/vlogger >/dev/null 2>&1 &

/etc/init.d/apache2 start


Of course your log directives will be something like:

LogFormat "%v %h %l %u %t \"%r\" %>s %b \"% Referer i\" \"% User-Agent i\"" vcombined
CustomLog "/var/run/apache2/logger" vcombined

You absolutely need to run the reader before the writer, else the init script would hang for ever. It is easy adding a simple init script to run vlogger before apache and it has also the big advantage of not requiring re-fork a perl intepreter at every damn log action. Piping rocks.

Stefano Zacchiroli: debian enhancement proposal SPAM

Debian Enhancement Proposals (DEPs): wanna comment? Ok, ok, you're right, I was late, but a good old rule of SPAM is: the more, the better. So, if you care about decision management (or, better, tracking) in Debian and you've always wondered why don't we have something like PEPs? please take part in this discussion: a nice "by product" of the Extremadura Debian QA meeting by Dato, Lars, and myself.

16 January 2008

Kyle McMartin: first post.

I’ve climbed up above the tagclouds and appear to be back in the “blogosphere” whatever that is. I hate that “blog” word. I also hate the word “prosumer.” Spent last weekend in Raleigh at FUDCon which was a lot of fun. I doff my fedora to the organizers. It was great to finally have the opportunity to meet a lot of my coworkers who I haven’t yet had a chance to run into at conferences. Poked a bit at btrfs in my idle cycles… managed to make it fall-over-go-boom on parisc64. Fixing that up should keep me busy in my spare time for the next little while… Oh. And if anyone would like to make me a new disembodied head^W^Whackergotchi, I’d very much appreciate it.

Andrew Pollock: [tech] Linux software RAID hates me

After the debacle last time I tried to grow the size of my existing RAID1 when I put new disks in daedalus, I thought this time I'd do my homework. I did some research, I found out the way I should have done it. I did a practice run on a USB key. I fully planned how I was going to do it:
mdadm /dev/md2 --fail /dev/sdb3
<delete /dev/sdb3, recreate at new full size>
reboot
mdadm /dev/md2 --add /dev/sdb3
<wait for sync>
mdadm /dev/md2 --fail /dev/sda3
<delete /dev/sda3, recreate at new full size>
reboot
mdadm /dev/md2 --add /dev/sda3
<wait for sync>
mdadm --grow /dev/md2
<wait for sync>
pvresize /dev/md2
Everything went as planned, until I went to grow the RAID1 volume. It still thought the underlying device was the same size. There was nothing to grow. So at this point, I decided to do something similar to what I did last time to get around the failing disk, and should have done last time anyway. I broke the mirror, created a new degraded RAID1 using the full size of the new partition on the half I pulled out of the mirror, and did a pvmove from the old non-full-sized degraded mirror to the new full-sized degraded mirror. All of that went swimmingly until the pvmove was around 50% complete, when the kernel decided to oops spectacularly. I had to power cycle daedalus to get it back under control, and even in single-user mode, without me doing anything, the kernel started oopsing again. Dammit. I had to boot into emergency-mode (insert standard gripe about Debian's single-user mode being far too non-singular here), then I could resume the pvmove without any further oopsing. After that completed, I was able to ditch the old non-full-sized degraded RAID1 device and resync the new one onto the old partition. There was still some minor filesystem corruption, more likely because I had everything mounted at the time of the crash. Yes, I still haven't learned not to do this kind of thing in multi-user mode. It seems every time I try to minimise the size and duration of an outage, it bites me in the arse. Even though I should have been able to move open logical volumes between physical volumes, the kernel oops seemed to be in the dm_mirror code. daedalus is running a fairly old kernel. The annoying thing is that getting some additional disk space on board was the dependency for doing a general upgrade of all of the software on it. Argh. Anyway, it's done. I hope not to have to go through this again. I just have to sit through a potentially nail-biting remote upgrade of Debian now, and I should be good for a couple more years hopefully.

Michal &#268;iha&#345;: One year under my reign

One year ago, I took over Gammu maintenance. I think it time to summarize a bit what happened during that year. There were definitely good and bad releases in that time (especially strictness introduced to SMS parser in 1.13.0 took quite a lot of releases to fix various bugs), but generally I things Gammu is moving in a good way. What I would definitely call positive: There are also some bad things: Some statistics of last year (based on Ohloh):
ValueDec 2006Dec 2007Difference
Code Lines90,540101,687+12%
Comment Lines9,20415,336+67%
Comment Ratio9.2%13.0%+30%
All these changes were made in approximate 1200 commits. I hope next year will not be worse :-).

Annabelle Tully: #debian-offtopic

As one of the females in #d-o might I add that this is not at all a sexist channel. Sure, like all friggen channels on IRC, and not to speak of the internet in general, there will be jokes, about men, women, monkeys, MacGyver and politicians. If you walk into a channel as a stranger and immediately draw conclusions because one
of the known peers of the channel utters a joke, and ramble about it, publically slandering that this person or channel is sexist, you really have no friggen business on the internet. Sorry, but you don’t.
Everyone is made fun of on irc, in #debian-offtopic it’s definitely “friendly insults” at that, and women are no exception to this. If you are too sensitive to handle this, again, you really have no business on irc. Please stop slandering and causing excessive drama because you cannot handle a fucking joke, for the love of god. I’ll say it again, #debian-offtopic or ANY debian channel I have ever been to (which according to my whois is a whole fuckload) has never ever hit me as sexist, and if you hang around enough to see some of the cool people around in them, maybe, just MAYBE you’ll see that these simple insults are JOKES and meant to be FUNNY and SARCASTIC. If you are unable to handle JOKES and SARCASM, get your ass off the internet and leave the rest of us “sexist” and ”blasphemist” freaks alone, PLEASE.

Lior Kaplan: Who moved my PEs (or why does pvmove sucks on linux) ?


Yesterday I wanted to extend an existing LVM VG with some central storage disks. In the process, I notice the VG is built upon local & external disk, which isn’t according to my standards. So I decided to extend the VG with the external disks, and then use pvmove command to move all the PE from the internal disk before reducing the VG. The problem is, that on RHEL 4.4, the pvmove command hangs during it’s work, never returns to the prompt, and locks all the other LVM commands. Seems that for little amounts of PEs the command works, but for 10G disks it hangs. As nothing else helped, I was forced to hard boot the server using to power button. Running the command in single user also doesn’t effect the result, although non other user/services are running. RHEL 4.4 has LVM2 version 2.02.06, RHEL 4.5 has version 2.02.21 and RHEL 4.6 has version 2.02.27. Reading upstream’s changelog seems there isn’t any change regarding pvmove, although it’s still worth testing if upgrade helps. Version 2.02.29 has “Refactor pvmove allocation code” in its changelog, but it will take time before this version will be officially available for RHEL (fedora 8 only has 2.02.28). Hoepfully it will solve the problem, as my HP-UX colleagues are laughing on my expense… And that I have to invest more time in mimicking pvmove work manually.

Miriam Ruiz: Sexism? Hostility?

The story seems to have started with Damog supporting sexism and xenophobia in Debian, followed by Bernhard’s comment about that not being tolerable under Debian’s flag. Aigarius replied kinda shocked that stopping verbal abuses and violence would be censorship. AJ clearly explained the reasons why that shouldn’t be tolerated in Debian, but Aigarius seems to keep thinking that poor jerks are being discriminated when they’re not allowed to insult us. Wouter seems to be tired of the whole topic. Am I missing any chapter? Now my turn: We are on the right way. Since the Debian-Women project started, we have being able to achieve a friendly and non-sexist environment inside Debian, which is something that I’d really like to keep. It doesn’t really mind that a couple of people try to go back to a hostile environment. Trolls just do exist, I guess, but they are not representative of the general feeling of the people inside Debian. Damog, I won’t get the fuck out of here, like it or not. It seems to me that it’s just a couple of you who are happy to be in such an aggressive environment as the one you’re promoting. For what I know, most of Debian people are happy to live in peace. You don’t have social life? You don’t like it? That’s your problem, dude, but don’t ask us to leave ours. I respect you, you know I have always done. I’m just very disappointed with your comment. Really. Making fun of other people’s problems and traumas is simply bullying. I hope you think about it. For the rest of Debian, keep up the good job. Right now my feeling is that the level of sexism, racism, ageism, homophobia, hostility and unfriendliness in general inside Debian development’s world is below the average in the Free Software world. It’s nice to be there, and I’m really proud of belonging here, which is something I cannot say about every group in Free Software. I’d like to keep it that way. Sorry for the aggressiveness in this weblog entry.

Adeodato Sim : Interesting things happen when you put people together

Debian meetings are fun, there is no doubt, but they are also magic, because things happen that would not happen otherwise. I had this Debian Enhancement Proposals idea in my mind since late August 2006, but I had let it rot for various reasons. During the Extremadura QA meeting last December, some conversation happened that made my head pop out the idea, run it past some people, find the energy and, together with Lars and Zack, produce a draft. So, the bottom line of this post is: go to meetings and participate, or sponsor/organize them if you can, because there’s not telling what can come out of them!

Wouter Verhelst: Dear world,

I'm a Debian developer; therefore, I have a GPG key. Just because I do, doesn't mean I want every random message to me to be encrypted. Thank you for your attention.

Anand Kumria: We're back. And, we won.

Actually I never went away, yes 22 months is a long time between blog entries, I just got distracted by travelling and working at AwayPhone. I'm still there and we are looking for one or two developers, principally in the US (Washington state) — but as a global company, not necessarily — so let us know (ASCII only, spell-checked, coherent English, etc.) if you are interested. I've been on (technically) holidays for the past few weeks, but I find myself awake, reviewing code at 02:45 (now 03:30) and trying to catch up on emails. I'm reminded of a friend of mine who always used to shout “RELAX!” whenever we went bar-hopping. I've been trying to apply that to a broader area of life than just bars but it appears that it just isn't how I'm wired to operate; for better or worse. That means, that whilst in Australia, I'm also rebuilding my mothers' IT infrastructure at her publishing company. I want it all to survive without any intervention for at least 2 years. So, I've been evaluating various pieces of kit. My conclusions:
NetGear
Switches, Modems (ADSL) and Wireless access points
Western Digital
Linux NAS boxes (they have Samba, rsync and SSH on pre-installed. I'd expect a firmware update from the makers to incorporate iSCSI and allow you to join a domain shortly).
HP
Desktops and Servers. Although I wish Bdale has some influence within HP and I did not have to taint the kernel of my servers. Seriously, it is because of that I re-do a price/functionality check everything time I go to purchase a machine. HP only just get it right.
Linksys / Cisco - snom
VoIP handsets. To be honest, this category is still being evaluated; but I'm leaning towards snom.
I realise everyone has probably been burnt but some of the vendors mentioned above but this is my experience of them. You'll notice nothing about laptops. I'm looking around for a decent vendor, I'll let you know if I find one. If you have been following along, you will notice that the Netgear ADSL modems (DM111P) runs Linux. The WD MyBook World Editions II's, run Linux (and I'd expect that they could be coaxed very easily into running generic Debian). The HP stuff (mostly) runs Linux. As does the Linksys and snom handsets. We won. Now, I've got to figure out how to setup Clonezilla so that the desktop Windows machines can be replaced when they fail. And I have less than 144 hours to do so. There is nothing like a deadline to concentrate your mind. P.S. I do have some half-finished entries for the intervening 22 months, I will clean them up and post them under their original dates in the next few weeks

Lucas Nussbaum: Help us get rid of dash build failures in Debian!

Following my rebuild of all packages using /bin/dash as /bin/sh, we now have a nice list of bugs. Those bugs are cool: So, if you want to get involved in Debian development, try to submit NMU patches for those bugs. If you want me to sponsor the upload, please Cc me when you submit the patch. And even if you don’t care about Debian, but only about Ubuntu (which is fondamentally wrong, as everybody knows that Ubuntu is based on Debian), fixing these bugs also helps Ubuntu a lot: all those bugs hurt Ubuntu, since Ubuntu uses dash as /bin/sh by default, and, even if the packages in Ubuntu have been patched, it’s still causing additional work every time a new package is uploaded to Debian, and has to imported in Ubuntu. If you have questions with the process, please ask them using the comments below. Notes:
I use the following process on those bugs, and it’s probably a good idea that you do the same if you intent to submit patches: If you submit NMU patches, please also have a look at the other bugs in the package, or at the lintian output. I don’t mind sponsoring small fixes for non-cosmetic/non-wishlist stuff at the same time.

Mark Brown: dpkg symbol versioning

About a month ago I added symbol version information to the zlib package, allowing dpkg-shlibdeps to calculate more relaxed dependencies for packages using the library. The results have been very satisfying so far - of the 1784 packages depending on zlib1g on amd64: Of course, zlib is a particularly good use case for this - both API and ABI are extremely stable and most of the changes in interface are in rarely used features - but it’s still good to see it working in practice. I don’t need to worry nearly so much as I would have done previously about keeping other packages out of testing. If you maintain a library written in C I would encourage you to take a look at implementing this, it’s very straightforward. Libraries written in other languages may cause more difficulty. There are some automatically generated symbol files in mole which provide a good starting point (I didn’t use them since upstream already had a more exact list of versions at which symbols were introduced) and support is already present in debhelper. The main things to watch out for when using the mole data are backwards compatible ABI changes which don’t just add new symbols (for example, if new values are accepted by a function) and variations between architectures. Kudos to Rapha l for all the work he’s put into this.

loldebian - Can I has a RC bug?: Why be an average guy any longer

Russell Coker: Differences between Distribution Kernels

It is not uncommon to run a Linux system with a kernel that was compiled for another distribution. One reason for doing this is the difficulty in compiling and testing a kernel to make sure it will do what you require. It’s not THAT difficult for someone who knows what they are doing, but if someone else has already done the work then it seems like a waste to re-invent the wheel. Sometimes it’s an issue of a driver that one distribution supports but not another, copying the entire kernel package from another distribution may be easier than compiling a new kernel with the extra driver. Sometimes it’s a kernel bug, if distribution A has fixed the bug and distribution B hasn’t, then it’s often easier to install a kernel package from distribution A when running distribution B. Another reason for running different distributions with the same kernel is Xen. If you have a Dom0 which hosts instances for different distributions as DomU’s then running the same kernel on all of them can make it easier to manage. Unfortunately it’s not uncommon for different distributions to have different kernel feature sets. One example I’m currently dealing with is the fact that the Debian/Etch kernel is compiled with CONFIG_AUDITSYSCALL disabled while RHEL and CentOS require it. So if you run a RHEL or CentOS system with a Debian kernel (EG running a Debian Xen server with a RHEL or CentOS DomU) then you see messages such as the following in your logs. crond[7824]: pam_loginuid(crond:session): set_loginuid failed opening loginuid The loginuid feature allows login and equivalent programs (which includes xdm and other graphical login programs, cron and every other program that runs a program on behalf of another user) to set the loginuid. This loginuid will be stored by the kernel, inherited across fork() and exec, and not be changed by running setuid or setgid programs. Therefore if you see some strange entries in your audit log indicating an attempted attack you can determine the original login UID of the person responsible. In terms of security features it’s not a really high priority. But it is really annoying when programs that work on RHEL don’t work properly with a Debian kernel and put many unwanted messages in the log files. For people who have less background knowledge about these things it may be more than annoying, and may even force them to change their deployment plans to make the message go away (not everyone knows which messages can be ignored or where to ask about such things). The fact that Etch has no user-space support for the auditing features in question (auditing system calls or setting the loginuid) was never a good reason for not enabling this feature (IMHO). Using the auditing system calls was simply a matter of copying the auditctl program from a RHEL, Fedora, or CentOS system (for those who didn’t feel inclined to compile the source). The loginuid required changes to PAM to enable it, but is actually a small part of the auditing layer. As a general rule minimising the differences between distribution kernels is going to benefit most people. Some people complain about kernel bloat, but there are worse candidates for that accusation and given that it seems impossible to buy a machine with less than 512M of RAM and a 900MHz CPU (the specs of the ASUS EeePC) adding a few extra kernel features seems unlikely to hurt anyone. It is of course always possible to compile your own kernel for the smallest machines. Finally I am in the process of back-porting SE Linux code and related security features to Etch, and having this already enabled in the kernel would make my work easier. I won’t do a 7 year support cycle for it unless someone pays, but supporting Etch past the release of Lenny with the latest SE Linux features (and the current features working properly) is my aim.

Aigars Mahinovs

AJ, if some blogs would support comments, I would leave my opinion there and not add noise to the planet. 1) Censorship does not stop being censorship just because the people doing the censoring don’t have the absolute power to censor the information everywhere and only block the information or opinion from the channels they can control. It can be called otherwise - editorial control, policy of political correctness, libel liability protection policy, Children-Safe Talk Initiative or Women Friendly Environment Collective. But at its heart it is still censorship of all official Debian-related channels of communication as the aim is to remove the objectionable content from all such channels. 2 and 3) Discriminating against jerks is also a discrimination against people or groups. Please do not get all DFSG-bendy on me here. DFSG is about use and distribution license of the software and not about the communication channels used to facilitate this process. I could actually counter you with a quote from the Social Contract that says that we will not hide problems. The discussion as such admits that some people consider sexism to be a problem in Debian (for example). Excluding sexist comments from Debian official channels will not make sexism magically disappear, it will be just hidden, swiped under the rag and said to sit quiet. The only problem is that the community that is tired of such hushing is much larger then anticipated. There are people that think that men and women are different. We checked. I can’t see anything bad in the example quoted on the planet so far. Yes, the depth of the discussion is weak - we can’t be genius all the time, but I really fail to see who is insulted in there. Lesbians? Don’t think so, they are compared to a threesome quite favorably. That is not a technical discussion about interrupt timings, but that’s why it is in offtopic. Doh! Relaxed chit-chat like this is typical in all healthy and tight-knit communities. Is it offensive to women to talk about sex??? Grow up and have a good 3 hour chit-chat with some real women. Women talk about sex even more than men. Especially on-line. Can someone really show what is the “OFFENDING BEHAVIOR” so obscene and dangerous that people want to censor out of Debian and explain what exactly they see as being so horribly bad to Debian that they see total censorship of all Debian communication channels as an acceptable countermeasure?

Next.

Previous.