Search Results: "Martin"

15 May 2007

Martin F. Krafft: Death is just the Beginning

I picked up the sampler Death... is just the Beginning Volume IV the other day, practically for free. On it, there are a few songs by bands I've come to like recently, so I expect to find a few more good tunes that way. Opening the case, I notice that it's not the standard jewel case but rather a unique mixture between paper and plastic. But it's not plastic as the case boldly asserts. It's a NaturePac no plastic biodegradable. Well, first off, I am glad that environmental consciousness is spreading. Next, I wonder whether the producers of the sampler expect me to get rid of it soon, or why they chose biodegradable packaging. And last, since we already know that heavy metal is for gifted kids, I can now boldly assert that all listeners of death metal are environmentally conscious. Or was it the other way around? NP: Man on Fire: The Undefined Design

14 May 2007

MJ Ray: Planet Debian Editorial Policy (Reader Comments)

Kevin Mark commented:
"Hear hear! I was waiting to read about the Eurovision results! But I'm sure AJ and Martin want a let's take the fun out of Debian planet debian tech and I'm sure someone can make them a custom feed for the cost of a reasonable bounty!
Nice to know I'm not alone. (Why mention AJ?) Joachim Breitner wrote:
"I once tried to start a German planet Debian because the official only allows English postings. Maybe it would be nice to have some kind of tagging standard that works across aggregators. This way, we could allow any kind of posts on p.d.o, and allow various sets to chose from, based on tags. I, for example, would choose (german OR english), others might chose (english AND tech), or ((french OR english) AND debian). Some (NOT politics). And some just (jokes) :-)"
Why didn't German planet debian work? I think there's a sort-of standard in dc:subject and xml:lang, but we'd need to agree a tag dictionary. And I think planetplanet generates files, so we'd need some cached or database solution. Update: Joachim Breitner replied:
"To be correct, I tried setting up an international planet debian on gluck with no language restrictions, but interest was rather low and planet (the software) is not really maintenance-free, so I stopped after a while. A German planet was tried by someone around Christmas, I think, but AFAIR he lost interest while trying to make it look pretty. I guess I should follow up on that. :-) (PS: Can you make the comment form store the information in a cookie? Would save some typing.)"
Sorry, these pages are static html at the moment. You could try using Saved Forms in Iceweasel/Firefox, which may be configured at Edit: Preferences: Privacy: Saved Forms or similar.

12 May 2007

MJ Ray: Planet Debian Editorial Policy

Apparently, it is fine by him if others flood planet debian with repeats because they screwed an upgrade, post questionable career advice or misleading documentation links, make fun of unrelated computer companies, or discuss the weather or traffic, but I posted about Eurovision and Martin Zobel-Helas unlinked my entries and sent me a rude email. Isn't planet debian a planet of debian developers, not just a planet of debian development? Even if you only write about debian, please don't force that on everyone else. I like reading about the other stuff developers do - even the loony political views that I don't agree with... Didn't someone put up a Planet Debian Tech a while ago? Maybe that's what Martin Zobel-Helas should read. Whatever happened to it?

Martin F. Krafft: Seeking a decorative closet for servers

Dear Lazyweb: we are looking for a decorative closet to house two servers in our flat. What I have in mind is a closet of about 60x60cm base area and around 1.3 metres height. The outer casing should look good, so a butt-ugly-computer-grey casing is out of the question. Rather, we would like a black case with a darkened glass door in the front. We do not need to mount 19" cases, so the inside just has to accomodate two 46x66x22cm towers and a few appliances, such as backup tape drive, switch, and cable modem. We're looking to spend around 300 , at most. I have been looking around on the web and on auction sites, but without any luck. Do you have any pointers? Please let me know! Thanks. NP: Dredg: Catch Without Arms

11 May 2007

Martin Michlmayr: GCC 4.3 related build problems: pedantic preprocessor warnings in C++

GCC 4.3 changed pedantic preprocessor warnings in C++ code into errors, in line with the C++ front-end. Because of this change, preprocessor warnings are now errors. This leads to a number of errors that are in my opinion too strict and I've started a discussion about this problem on the GCC mailing list. I hope this change will be reverted, or that some of these errors are downgraded to warnings again, but users of current gcc-snapshot package might encounter these errors. I haven't filed bugs about these issues since I'm waiting for a census from GCC developers. Nevertheless, it makes sense to fix these problems if they are present in one's package. This change has caused at least the three following errors which are all fairly common. error: "xxx" redefined It's not allowed to #define something twice, as in this example:
#define TEST "foo"
#define TEST "bar"
This code will lead to the following error:
test2.cc:2:1: error: "TEST" redefined
test2.cc:1:1: error: this is the location of the previous definition
Most typically, this occurs because something is defined in a header that is included and then redefined in the current source file. It can also happen when a #define is put in the code but also on the command line, e.g. via -DTEST="bar". This will lead to:
test2.cc:1:1: error: "TEST" redefined
<command line>:1:1: error: this is the location of the previous definition
The correct solution is to avoid redefinitions directly or to use #ifndef to make sure that something has not been defined already. extra tokens at end of #endif directive While an #ifdef obviously needs a second parameter, it's not allowed to give one to #else and #endif. Unfortunately, this is commonly done as a reminder for what is being tested for:
#ifdef TEST
#endif TEST
This code will lead to the following error:
test3.cc:2:8: error: extra tokens at end of #endif directive
missing newline The last line of a source file has to end with a newline. If this is not the case, the following error is now shown:
test4.cc:1:19: error: no newline at end of file

Martin Zobel-Helas: Mark Shuttleworth Interview in the recent German LinuxMagazin

While reading the newest print version of the German LinuxMagazin i found an interview with Mark Shuttleworth, which made me partly wonder. There he says: “Bei vielen Sachen, die einen gro en Einfluss auf Systeme wie den Kernel, X.org oder Open Office haben, bernehmen wir die F hrungsrolle, wir stellen die Pakete und viele gelangen so zu Debian. Also sind wir in vielen F llen der Upstream von Debian.” (english: On many things, which do have a great influence on systems like kernel, X.org or Open Office, we take the leadership role, we supply the packages and many of those getting into Debian this way. Therefore we are the upstream of Debian in many cases.) I know of certain packages, like python, gcc, apt and maybe X.org, which are mainly maintained by Ubuntu developers. But is this really true: Is Ubuntu really upstream of many Debian packages? Can someone please enlighten me, and give me some statistics where Ubuntu is upstream of Debian, and where Debian is upstream of Ubuntu? I would really like to know the facts. No Tags

Martin Michlmayr: GCC 4.3 related build problems: extra semicolons

After I described yesterday that GCC rejects semicolons after functions, Ben Hutchings pointed out that semicolons are actually allowed according to the standard. I regularly complain to the GCC people for introducing new errors, but when this was was introduced I assumed there was a good reason and didn't want to complain yet another time. Turns out that I should have. Fortunately, somone else must have noticed the problem because GCC has been changed in SVN and this code is no longer rejected.

Martin Michlmayr: GCC 4.3 related build problems: extra semicolons

One mistake which some C++ programmers make which GCC 4.3 rejects is to put semicolons after functions. While a semicolon is needed to terminate a class, struct and enum it must not be used after functions. The following code is invalid because of an extra semicolon (in bold):
class Test  
    Test()  ;
 ;
GCC 4.3 will reject this code with the following error message:
test.cc:2: error: extra ';'
The obvious solution is to remove the spurious semicolon.

10 May 2007

Simon Richter: gcc 4.3

Martin writes about semicolons after functions being an error now. This makes life difficult if you want your code to also compile on Visual Studio 2005 (probably 2003 as well, haven't tested) and you use "function-try-block"s in C++, because there is a compiler bug that makes it actually require semicolons after some functions.

Martin Michlmayr: GCC 4.3 related build problems: missing #include

In GCC 4.3 the C++ header dependencies have been cleaned up. In the past, compilation would often be quite slow because including a simple header would indirectly include a lot of other headers, even if they were not needed to compile the current code. Many headers have now been cleaned up with the result that compilation is quicker. The downside is that programmers cannot rely on indirect inclusion of headers they may need anymore. Instead, everything that is needed has to be directly referenced with an #include. Typical errors look like these:
error: 'find' is not a member of 'std'
error: 'exit' was not declared in this scope
Below is a table showing which header needs to be included for a number of common functions:
Functions and definesHeader
find, for_each, sortalgorithm
isalnum, touppercctype
INT_MIN, RAND_MAXclimits
printfcstdio
atoi, free, randcstdlib
EXIT_FAILUREcstdlib
auto_ptrmemory
fd_set, mode_tsys/types.h
typeidtypeinfo

Martin Michlmayr: GCC 4.3: common build failures

Even though GCC 4.2 has seen many delays and still hasn't been released (although it's finally getting close), a lot of development has already been done on trunk for the release of GCC 4.3. I started testing 4.3 in March and in addition to finding and reporting compiler issues I have filed bugs on packages that fail to build with GCC 4.3. The idea is to give people an advance warning and to be ready for GCC 4.3 when it will be released. We have almost 500 bugs related to GCC 4.3 already, mostly due to a clean-up of C++ headers in GCC that has exposed sloppy programming in many programs. Fortunately, these bugs are easy to fix. As I'm finding common mistakes in packages, I will document these problems and way to make sure a program is ready for GCC 4.3. Common problems

Martin F. Krafft: Drying ducks

Thanks, pixie, you made my day:
my very own duck towel
Now if only I could shower all by myself, I'd try it immediately. Or rather: I can shower alright, but still need someone to wrap my casted arms in plastic. And believe me, showering through plastic bags is really unsatisfying. Eleven days to go. Then those bloody things come off. I am looking forward that shower on 21 May even a bit more than I have at times craved the clean wetness during prolonged expeditions in the Alps or Asia. Now I am sure you didn't need to know all that. NP: Explosions in the Sky: The Earth is Not a Cold Dead Place

Martin Zobel-Helas: Packages considered for 4.0r1

As there are currently four persons working on the next stable release (Dann Frazier, Luk Claes, Julien Danjou and me), we decided to track all issues for the next stable release (4.0r1) also in the Debian BTS. So if you would like to look what we currently consider for 4.0r1, have a look here. Before adding a bug (eg. with the command bts user debian-release@lists.debian.org . usertag 420759 + SRM) please contact the stable release team first, or even better, let the stable release team add your bug there on their own. Also, not all uploaded packages to proposed-updates will automatically considered for the next stable release. Update: With “contact the stable release team first” i do mean, please send requests to debian-release@lists.d.o, not contacting release team members in private over IRC or direct eMail. And NO, h01ger, cellphone is also not an option!!!1!!!elf!!!!

8 May 2007

Martin F. Krafft: Linux pains #517: unregistering network devices

Somehow my network device does not want to recognise that it actually has a carrier. This being Linux (and not Windows), I thus decide to reload the driver, after taking down the network interface:
lapse:~# ip l dev eth0
2: eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast qlen 1000
    link/ether 00:0a:e4:30:43:16 brd ff:ff:ff:ff:ff:ff
# notice: not UP
lapse:~# rmmod e1000
lapse kernel: unregister_netdevice: waiting for eth0 to become free.
  Usage count = 1
lapse kernel: unregister_netdevice: waiting for eth0 to become free.
  Usage count = 1
[...]
# goes on forever, uninterruptible; thus new shell:
lapse:~# ps u -C rmmod
USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
root      5624  0.0  0.0   1656   480 pts/2    D+   00:02   0:00 rmmod e1000
As we all well know, state 'D' uninterruptible sleep means: reboot. Especially since I cannot ssh into the box anymore (doh!), and su and sudo just end up in state 'D' as well, if I try them. So, on to reboot. Or wait, that doesn't work as the shutdown process will hang long before the filesystems get unmounted. Great. It's become impossible to argue that Linux is the more stable operating system Update: a few people responded with workarounds, ranging from use of watchdog to automate the reboot (this is my laptop, so it's not really necessary) to various combinations of flags to /sbin/shutdown or the use of sysrq to force the system to reboot without cleaning up or unmounting filesystems essentially the same as pressing the reset button. Ben Hutchings says:
I think this happens when the driver repeatedly attempts to fix an error condition and keeps scheduling future work (retaining a reference to the device) rather than giving up.
I thus ended up filing a bug against the kernel.

Martin F. Krafft: Starting netconf development

This message just went out to the debian-devel mailinglist:
Even though I am still somewhat physically limited, my brain today decided to start on the netconf development. And since we all know that the waterfall model is the One True Model and that Extreme Programming no solution, I started by drafting a document, nothing formal, just thoughts on how to implement the various parts of netconf. And open questions I already know need to be answered. I shall be posting this document to the netconf-devel mailing list sometime soon and am looking for comments (and answers and helpers). The purpose of this message is to get interested people to subscribe. Please do so that we can keep debian-devel free of this and so that I can get more feedback (and potentially help). If you don't know what I am talking about, check out the wiki page and slides from my last talk. Then subscribe.
Thanks for your attention; that is all. NP: Trentem ller: The Last Resort

Martin F. Krafft: A lesson learnt

I am installing my first Ubuntu computer, a laptop for a friend who just wants to use the Internet. Even though I am not entirely sure whether to ridicule the installation process it took the installer 2:47 hours to produce the first user dialog on this PIII 600MHz with 256Mb of RAM, so I had to use the alternative text-mode installer or be impressed by the desktop that eventually filled the screen with more-or-less everything working out of the box, I think I did learn a lesson today, as trivial as it may sound. The screen of this laptop stays blank throughout the boot sequence even though Ubuntu put so much effort into a flashy splash screen. Thus, I logged on to #ubuntu and found someone who had time to help:
< madduck> i just installed feisty on a laptop and now when i start, after
           grub, it says "Starting up" and then has a black screen until gdm
           has started
< madduck> where is the fancy splash?
< someone> madduck: the splash screen uses a standard VESA mode which,
           apparently, your system doesn't support. Remove the "quiet
           splash" options from menu.lst to see boot messages in text mode.
< someone> madduck: you can try fixing the VESA mode with the vga= kernel
           boot option. Start with 'vga=ask' and enter 'scan' at the prompt
           at boot time.
But I still had no success when someone apparently typed into the wrong window and triggered the childish area of my brain:
< someone_else> ls
< someone_else> clear
< madduck> rm -rf ~
< someone> madduck: what was the purpose of that?
< madduck> someone: EWIN :)
< someone> madduck: I'm not prepared to support you if you go around telling
           people to delete their home directories, however funny you think
           that is.
I apologised (sincerely), and the person went on to help me, pointing me to more VESA modes and making me try them until I had a lead. No wonder Ubuntu gets the users. I am not saying that Debian is at the losing end in this scenario. Instead, I am preaching to the choir who sings back: "but Debian wouldn't be Debian without the flames." And I think to myself: "I wonder who actually engages their brains and continues to hold that view when they utter it." NP: The Young Gods - Kissing the Sun (Orange Mix) Update: without having to be told by anyone, I know there are people in Debian who try to be equally helpful and reasonable. In fact, Debian has gotten a lot better in the last years, in part (but not exclusively) thanks to Debian Women. This post does not try to discredit those who already make Debian a better place, or to piss anyone off. In fact, it's about a lesson I learnt, which may be obvious to many, but which hasn't been as obvious to me until today.

6 May 2007

Martin Zobel-Helas: Good thing of AJ been DPL

Advantage of the time AJ was DPL: Requests of the stable release team to the FTP-Admin team got processed quite fast. The stable release team is now waiting since a couple of weeks to get
#418639 fixed. Also AJ promised to semi-automate p-u-new processing, which didn’t happen since the release of etch. current mood: frustrated.

3 May 2007

Mario Iseli: LPI exams during Debconf

I already had the idea to get LPI certified - expensive fun. Thanks to Joerg and co. for organizing the cheap exams during Debconf, I already have signed-up for LPI101 in the morning and LPI102 in the afternoon and wrote our $$$-director of the comany a mail that I’d like to get 95 more at the end of this month. Finally a little reference to the blog of Martin F. Krafft - and especially “Why? I am a Debian developer”. I think this is just bullshit, sorry. LPI is dedicated for system administrators, BOFHs, techies, however. Not that stuff what a Debian developer is doing. I mean, a DD should have knowledge about Debian including knowledge about software development, documentation, how to build packages, write some scripts… But does he need to know how to manage iptables or know where you need to set the fontserver? I think no… LPI asks many questions about old stuff, like the XFS, ISA Cards, Analog modems usw. The normal user today doesn’t need to care about this things, even a Debian developer mustn’t. I think many DDs never have touched an ISA card. So, I will participate in the exams, please don’t blame me if I fail. :-)

Martin F. Krafft: LPI or not?

The Linux Professional Institute offers all its exams at a discounted price at debconf7. That's definitely good news and should earn Klaus Behrla another round of gratitude for his efforts (assuming he's behind this again). However, it also gets me thinking again: I've been meaning to complete my certifications for years but never could be bothered to spend the money (even at a discount) or actually devote the time to the exam itself. At FOSDEM 2007, I had signed up but then skipped the exams to do more important stuff. The reason? During the conference, someone responded with something like "LPI? Why? I am a Debian developer" when I brought up the subject. Good point. I think I could just sit down and pass the second and third stage exams (having contributed to the exams themselves), and do even better with a bit of studying for it. But is it worth it? Does the LPI certification actually prove something that isn't already obvious from my online track record. What do you think? I'd be interested specifically to hear from fellow developers who decided to take the exams. NP: Anekdoten - Monolith Update: thanks, Joerg, for your thoughts. I am not looking for employment, and if I was, I'd certainly not want to work at a company that thinks certifications are the true proof of capabilities. So I guess that leaves me with a 'no' still. But I also want to say that this post is not to discredit the LPI. I think their exams are fair and definitely not trivial. Even looking at some study notes for LPIC1, I learnt some new stuff, so I bet just preparing for LPIC2 and 3 would teach me things I did not know yet. Compared to other certifications by more commercial vendors, LPIC definitely ranks very high, so don't let my blog post discourage you: there are plenty of reasons to take the exams; I was just looking for reasons why I would want to continue taking them. Update: Mario, I would not be a DD if before I had not been and continue to be a system administrator. And I think you'll have problems finding a hand full of DDs who've never touched an ISA card.

2 May 2007

MJ Ray: Crackers

I'm installing Paul Martin's iptables ssh-rate-limiter on the public machines that I run, to reduce the amount of logfile rubbish that ssh-scanning crackers produce. I've also added an iptables-restore line to the pre-up of the relevant sections of /etc/network/interfaces So far, there doesn't seem to be any disadvantage to doing this. Is there one? If not, why doesn't everyone do this?

Next.

Previous.