Search Results: "ag"

2 May 2007

Steve McIntyre: Apparently...

... the number 09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0 is magic somehow. Keep it safe, you never know when you might need it.

MJ Ray: Software Patents

james wrote:
"I came across your page. I wanted to suggest adding a link to http://www.FreePatentsOnline.com This is a free patent searching site with PDF downloading, world patent searching, alerts, and other account functions -- all free. It is a great resource for intellectual property professionals, reearchers, students, small businesses, and anyone else who needs such legal or scientific information."
I thought the idea was that we shouldn't search for invalid patents, because ignorant infringement is punished less severely than wilful infringement?

MJ Ray: Moving slickly from ranting to advertising

I love email newsletters that move slickly from ranting to advertising. Here's one from Gossypium:
"We believe that something is critically wrong with all those head in the sand neoclassical giant companies, that have been built on economical models that we would now consider antique and even dangerous for the human evolution. New business models like Gossypium have managed to rebalance the relationships between the economy, society and the environment. It is now accepted by all that we will need to change and that there is no turning back. We as a brand are trying to make this easier by offering positive alternatives. So here is our great T-shirt collection"
Source I just wish I could do that in such an amusing way. But I can't, so I'm currently shuffling a few things around to make my Business feed a bit more work-relevant. If you are subscribed to my Business-only feed for the Media items, please switch to the Hacks feed. Meanwhile, Webmastering articles will change from the Hacks feed to the Business one. And there's some more changes which I'm still working out. Watch this space.

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?

Amaya Rodrigo: The no impact man^Wfamily

If everybody on the whole planet decided to commit suicide, which in a way, they have, would it be the right thing to do to not join in? What s so great about trying to be right if it keeps you separate? It seems like there is something precious that has to do with holding yourself above or not just joining in and being part of. I don t know. I m suddenly realizing that this whole project could be pretty damn hard.

The No impact man is a family s project to try not to cause any environmental impact on the planet for one year. It involves a very radical change in their lifestyle, as they live in Manhattan. The blog describes their struggles as they gradually move from one goal to another, from reducing their trash generation to absolutely none, declaring war to tree-killing junk mail and plastic bags, only eating local produce, thus giving up coffee and sugar (which the wife specially resents), no cars, buses or elevators, being hit by a car while riding his second-hand new bike (no new purchases are allowed)... to composting their own waste and giving up all throwaway products, including toilet paper. All this in Manhattan, with a toddler!

While I completely relate to their goal, and being myself quite picky about the way I consume, having changed my most used light bulbs to low energy ones (even though I hate the resulting light colour and quality), turning off all electronics that have a led while not in use, not owning a car, avoiding public transportation in favour of walking as often as possible, and being obsessive about recycling, I keep a 24x7 powered on desktop and laptop, my lights are turned on much often than the average house (my place is very dark), I drink tea that comes all the way from Africa (Rooibos), I want to fly all over to Hamburg every weekend (but I can't afford to), and I have not gotten around to insulating my electrical water heater.

Yet, I live alone, in a small place, and my use of resources is still quite rational, for a geek. (Take a look at the WWF Footprint Calculator: I am living as if we had 2.52 planets to support us. Although I am below some of the world average figures, we obviously only have the one!).

It is both inspiring and off-putting to see this family s effort, as it looks like an interesting experiment that I am surely going to follow, but one I would myself not be able to attempt. Many people believe their small little efforts will not change anything, but I disagree. Every little effort makes a difference when you look at the global picture, still this problem is not easy at all.

In case you need some motivation to rethink the way you live, watch Who Killed the Electric Car?, An Inconvenient Truth, The End of Suburbia or Darwin's Nightmare.

To quote the no impact man in Deeper sickness, better cure: A psychiatrist friend, Stephan Quentzel, went so far as to suggest in conversation that environmentalism could be like a new religion that binds us together with a sense of common purpose and greater meaning .

Miriam Ruiz: [Gnash-dev] YouTube seems to be working now

A mail from strk to Gnash development mailing lists announces what many of us were waiting for. I’ve put some newer packages available, built against Etch, in case someone wants to try them. I’ve changed the renderer to AGG instead of OpenGL, which is preferable, and the media player to GStreamer instead of FFmpeg, because FFmpeg is still giving some problems. It seems that we’re closer to the next release!

Chris Lamb: April s search strings

This is clearly a meme now.

1 May 2007

Cord Beermann: Debian Weekly News is late? - Blame listmasters!

Hi.

We were notified that German DWN, and the Original DWN weren't sent out. Investigation showed that Diplomats (in German translation Diplomaten) matched the bad word 'Diploma', so it is dropped in our spambox.

I resent German DWN yesterday and the Original DWN some minutes ago.

sorry for the inconvinience.

Simon Richter: Perl

Yesterday, I needed a small script to process a tiny text file, just a little too complex to do it in bash. So perl should be my Swiss Army Chainsaw tool of choice. Since then, I have been diving into the madness that is a language without a way to express "map from string to array of strings". It can map strings to references, which requires a great deal of working around warnings about uninitialised references and lots of other interesting nasty effects. This language needs templates.

Mike Hommey: Google Keywords - Apr 2007

“adding the iceweasel branding to firefox windows” - coming soon
“asa dotzler sucks” - Blake Ross again ?
“booh debian” - apt-get moo
“ca passe” - ou a casse
“dumb ass 2″ - the return
“fix fucked up partition table” - you should try parted
“good variables to test” - foo ? bar ?
“hate soccer” - me too
“i could not agree less” - can’t say disagree ?
“plus c’est gros mieux a passe” - this also applies to what Sarkozy says
“shaking laptop while in use” - not convenient to type
“us consumer protection versus firefox” - Stella award in progress ?

Jose Carlos Garcia Sogo: Ubuntu preloaded in Dell Computers

As old news say, Dell will sell computers preloaded with Ubuntu. The move to sell computers preloaded with Linux was very wise, listening to their customers, and I think that at the end they will also see some kind of benefit from this. And now we see that the distribution chosen is Ubuntu. This is important for Canonical, and Debian should benefit from this as well. But anyway, Linux as a whole will improve, as Dell is going to chose devices that can have a driver in Linux, and write or push for it to be written. So, if that happens, device manufacturers will have an incentive when designing a new device: if they want it to be sold by Dell, it will have to work in Linux. Perhaps this is a bit of an utopia, but it is very important the feeling the market can have about this issue. From year to year I am learning that a very important factor in markets are feeling. Update: BTW; I own a Dell laptop, which I buyed two years ago. With this change, if someday I have the need to buy a new one, I will go agin for Dell.

Enrico Zini: index

Debtags paper for Debconf 7 Paper contents:

Evan Prodromou: 11 Flor al CCXV

Wow! I'm so thrilled this morning to find out that Wikitravel won the Webby Award for Best Travel Site. How great is that? tags:

Isaac Clerencia: Back from the States + so it turns out I m celiac

Hi there! I’m back :P I spent a really nice time in the United States with my friends. We stayed two weeks in Boston and New York, and basically did everything we had planned to do and more … We visited the MIT at Boston, went to several comedy shows, ice skated in Central Park, spent a whole day in the Barnes and Noble book megastore, went to an NBA basketball game, saw Monty Python’s Spamalot musical, discussed politics with fellow Americans, visited the Delaware Water Gap waterfalls, enjoyed an helicopter ride, even watched The Grindhouse in its first day in the cinemas, and well, did lots of other stuff. Now for the celiac thing … I was somewhat sick during the whole trip, I felt weary the whole day without any reason, so as soon as I got back to Spain I went to the doctor and after some tests that spanned over a week and a quick visit to the hospital they diagnosed me with celiac disease. That means that I can’t ever eat anything containing gluten, a protein present in wheat, barley and rye. It’s quite an inconvenient illness, but nothing more than that, as just following an strict gluten-free diet is enough to keep it at bay. The main drawback is that you have to be really careful when you go out for dinner. I have already been in sick leave for three weeks because I had lost weight and was a bit anemic, but I’m quite ok again, and I expect to be back at work really soon now :)

Russell Coker: LUG talks today

Today I gave three talks at my local LUG. The first was my latest SE Linux talk (I’ll put the notes online soon). The second was a talk about voting. I asked for a show of hands, who has already decided which party they will vote for at the next federal election (about 12 people put their hands up). I then asked people to put their hands down if they were not a member of the party that they intend to vote for, including myself there were only two raised hands in the room (including mine)! With the way party politics works nowadays the major parties are not very interested in representing their core voters. Why try to please for people who will vote for you anyway? Instead they try to appeal to swinging voters and pressure groups. If you have decided to vote for a party they have no reason to try and impress you. Therefore you should join the party and try and influence the policy decision making process from within. The issues that I believe are most important to the Linux community are free software use in government, sane intellectual property laws, the right to a fair trial, and not pandering to the US (which is related to the previous two points). If you have already decided who to vote for then you should join that party and make your vote count in the party room. One member of the audience said that he had been a member of one of the major parties but that the internal politics turned him off. If that is your experience then I think you should ask yourself whether you want to vote for a group of people that you can’t work with. The final talk I gave was about getting speakers for Linux Users’ Groups. There is always difficulty in finding speakers for clubs. Ideally we would have meetings planned a few months ahead of time so that they could be advertised in various ways. Newspapers often have columns dedicated to providing information about public meetings but the lead time is usually at least a week (and the meeting would have to be advertised at least two weeks in advance - so more than a month’s planning ahead is required). Getting a larger number and variety of speakers will attract new members, encourage existing members to attend more meetings, and inspire members in their Linux work. Talks can be given by almost anyone. There is a constant demand for speakers who have expert knowledge in the topic, but anyone who is a decent speaker and has the confidence to stand up at the podium can give a good talk. For expert speakers possibilities include academics, industry leaders, leaders of free software development projects, and journalists. But that’s not all, anyone who wants to spend the time researching a topic can give a talk on it. For example I’ve been learning about MySQL recently for my own servers and will probably offer a talk about MySQL aimed at sys-admins who don’t want to become DBAs but who just want to get a database running. I’m not a MySQL expert (and don’t plan to become one) but I believe that there are many people who want to do the things I do with MySQL and who could benefit from a talk that I might give. The best place to find speakers is a conference or trade-show. If they give a talk that works well you can suggest that they give it again for your local LUG. You can also find speakers at conferences that you can’t attend. If someone visits your country for a trade-show in a different city you could send them an email saying “unfortunately I can’t attend your talk, but if you are interested in visiting my city in the same trip then there will be an audience of X people interested in seeing you”. There’s no harm in asking, the worst that they can do is decline. Ask everyone who you think can do a good job. Also make sure that you don’t make any commitment (unless you are member of the LUG committee).

Miriam Ruiz: Debian multiple binary packages: example

I remember that when I started making Debian packages, one of the things I found more difficult was to get information about how multiple binary packages should be done. It’s quite an important topic when packaging games, as most of games often consist of a small arch-dependent binary executable and a big bunch of arch-independent data that includes images, maps, models, textures, sound, music, fonts and so on. I order to make it Debian-mirror-friendly, there’s no sense in multiplying all this arch-independent data by the number of architectures in Debian, and thus, most of the games shall be packaged as a small arch-dependent (any) package that includes the game itself, and a bigger arch-independent (all) one with all the data. I’ve made a small hello-world example to ilustrate how to achieve that. The example uses autotools (1, 2, 3) for building, and consists of a small program that reads an arch-independent text file and prints it to the screen. Small enough to be a nice example, and with all the features needed to show what i mean to. I won’t comment it in detail right now, but what rules do is to build the program with the default building system (./configure && make), install it in debian/tmp (make install DESTDIR= pwd /debian/tmp), and afterwards installing the files in their proper binary package directory. The resulting packages are described in debian/control. The example also includes menu and desktop descriptions and how to install an icon. We should still find a way to avoid having to release a newer version of the data (usually much bigger in size than the code) when only a change in the code is done, but I doubt if there’s a global solution for that, or if it should be done in an individual per-package way.
Files:

Joachim Breitner: A shelf for darcs

I recently did my first experiments with darcs: A friend of mine and I hacked on the same code, and by giving each other access to one s darcs repository, we could easily exchange our new code.One problem I had was that my friend recorded a patch that I did not want applied in my repository. Nothing else depended on it, so I could just say no everytime I use darcs pull , but it s still a hassle. Also, imagine that I m somewhere else and I suddently decide that I do want the patch?A similar problem would be if I created some patches that I temporarily don t want applied. I could branch, and then unpull them, but this is a bit too much work.In both cases a patch shelve would be handy. A seperate storage for patches in my repository that are available, but not applied. I d imagine that the darcs pull command would then allow me to pull and put on the shelf , and not offer me this patch again. There would also be put on shelf and get from shelf commands. So if anyone feels like hacking on darcs, this feature would be appreciated.Also filed as a withlist bug.

Enrico Zini: recovering-fat-partition

Recovering a corrupted FAT partition A friend has seen his FAT partition in his USB key become unmountable. Here's how I recovered it. Analysis:
  1. Make a dump: dd if=/dev/sdb1 of=partition.img
  2. Have a look. I like mc for this, as it has a nice hex viewer and editor (F3 to view, then F4 for hex view; F2 would then allow hex edit, if needed).
  3. Turns out that the initial part of the partition has been completely overwritten by 0xff bytes. After some point (around block 224), the 0xff bytes end and there seems to be a FAT structure (easy to identify because it contains sequences of increasing 16bit values).
It seems that the damage is only limited to filesystem structures. I should be able to recover most data by regenerating the filesystem data and hoping that at least the second FAT is still intact. Solution:
# Make a copy of the partition
cp partition.img partition1.img
# Reformat it: that gives us the bits of filesystem structures we need
mkdosfs partition1.img
# Graft together the two parts
dd if=partition1.img of=partition2.img count=224
dd if=partition.img of=partition2.img seek=224 skip=224
# Tidy up the result, telling dosfsck to use the 2nd FAT.
dosfsck -rw partition2.img
# Mount and check what's available
mount -o loop,ro partition2.img /mnt
Yo! Everything was there again. When I teach about standard Unix commands, it takes a while for people to realise all the powerful things you can easily do with them.

Russell Coker: more about Heartbeat

In a comment on my blog post “a Heartbeat developer comments on my blog post” Alan Robertson writes:


I got in a hurry on my math because of the emergency. So, there are even more assumptions (errors?) than I documented. In particular, the probability model I gave was for a particular node to fail. So the probability of either of two failing would be double that, and either of three failing would be triple that. Note that the probability of multiple simultaneous failures goes up as a power, but the probability of either of only goes up linearly. I really need to sit down and do the math carefully - but the idea of the simultaneous failures going up as a power is true. And the “any of” probability goes up linearly. That’s also true. This is why people can actually use larger HA clusters ;-). The 5 years figure is the industry standard quoted figure for an average Intel-based server to fail. The four hours to repair is a common high-quality of service response time from a hardware vendor. I admit that’s not the same as actual repair time, but if some “repairs” are just reboots, then it’s not a horrible number to start with - if your vendor has cached some spares nearby. I suppose I should sit down and do the math right, and make a spreadsheet of it. (I wonder if I remember that much math?) I assume disk failures are taken care of by hot swap disks, RAID, etc. and so in effect they “never fail” (at least not totally) so that these failures don’t have to be accounted for by the overall availability model. Here’s an intuitive way of thinking about it “from your gut”… If I took your whole data center and made a cluster out of it, what’s the chance that at least half of your servers would fail at once? Pretty darn small, is the short answer ;-). If it’s not pretty darn small, you need to buy better servers, and IBM has just the servers for you ;-). Or maybe they need to hire a better SysAdmin ;-) If you ask yourself “when is the last time at least half my machines in my data center couldn’t communicate with the other half”, then hopefully that’s also a “pretty darn small” chance too. If not, there are well-known methods for making networks highly reliable too. [I’m still ignoring “catastrophes” that you haven’t accounted for in your HA architecture]. I’m not saying this is free, and it can be pricey. One of my other favorite sayings is “Paranoia is an expensive hobby”. How much do you want to spend? You tell me how much you want to spend, and you can figure out how to spend it. I’ll make a separate comment on quorum models later. It’s getting late here.

My only comment in response to that is to say that I still believe the calculations of probability to be correct in my original post and I am interested to see someone prove otherwise. Another comment by Alan:


Data corruption, no doubt, is almost always much worse than loss of availability. And some kinds of data corruption are worse than others. For example, mounting a non-clustered shared disk filesystem twice simultaneously is usually much worse, than updating two replicas of the data simultaneously. In the first case, you have to restore to your previous backups and lose all data since then. In the second case, you only lose updates that were made to one of the sides, and you instantly have a working copy of the data which is nearly always much newer than your last backup (with the possibility of recovering them by significant effort). Typically you would only lose a few minutes of updates at worst - and depending on the kind of networking failure, you might not lose anything. Heartbeats certainly aren’t enough. You need to monitor the health of your servers and the health of your applications. Heartbeat monitors applications and can easily be informed of and act on the health of your servers (with release 2 style Linux-HA Heartbeat configurations).


Followed by:


Since data corruption is so serious, this is why cluster designers worry so much about split-brain, which is managed using the ideas of quorum and it’s sibling fencing. This is all about keeping bad things from happening. This post is really about quorum, since Russ had expressed interest in it. Quorum is the idea that you can uniquely choose a subcluster to represent the whole cluster in those cases where communication failure has caused the cluster to split into separate sub-clusters which cannot properly communicate with each other. In this way, only one of the subclusters continues on, and the others will sit on their hands and do nothing waiting for a person to fix things. Some of the kinds of quorum mentioned below are better than others. But, most importantly, they can be used in combination as described later. The most common kind of quorum is that Russ mentioned in his earlier post - the majority quorum. In this method, for a cluster of n nodes, you grant quorum to a sub-cluster which has more than INT(n/2) members. This means that if you have a 3-node cluster, you have to have two nodes to continue. If you have 4 nodes, you have to have 3 nodes to continue. For 5 nodes, you have to have 3 nodes, and so on. Other basic methods include disk reserve, so that you have reserve a disk to have quorum. In this case, if only one node survives and it can reserve the disk, it continues to run. However, the disk becomes a single point of failure. This may not be a problem if this single disk is required to run any of the cluster services, since they would fail without it anyway. [Heartbeat does not support this method]. An analagous method is to implement a software resource which grants quorum to one subcluster in a fashion analagous to the disk reserve method. This has the advantage of not requiring disk reserves, or a shared disk, but it has the same SPOF disadvantage as the disk reserve method. Heartbeat does support this method using the quorum daemon. It’s incredibly useful for those cases (like split-site clusters) where you cannot use fencing. Another method is to grant quorum to any subcluster which can ping a certain set of nodes, and not grant it to any which can’t access those nodes. This isn’t a wonderful method, and has obvious disadvantages with respect to uniqueness, and single points of failure. (Heartbeat doesn’t yet implement this one). Another method is to grant quorum to any node which is a member of a 2-node cluster. This is better than losing quorum and stopping when one node stops, but obviously completely ignores the uniqueness requirement of quorum. Another method is to ask a human being if you have quorum. This is hardly an ideal circumstance, but useful in some contexts as described below. (Heartbeat doesn’t yet implement this one). Perhaps you say, really the only one of these that’s really good is the first one - the majority vote method. And, I would generally agree with you. But, Heartbeat has the ability to use these in combination which makes some of those methods that seem flaky to be much more reasonable. Heartbeat has the ability to have multiple quorum modules declared, and they’re used in this way: Any module can return HAVEQUORUM, NOQUORUM, or TIE. If they return HAVEQUORUM or NOQUORUM, then no further quorum modules are consulted. However, if they return TIE, then the next quorum module is consulted for its opinion. If the last quorum module returns TIE, it is treated the same as NOQUORUM. This enables you to use one quorum module to break the tie declared by a previous quorum module. You could then use the quorumd to break the tie created by a voting module. Or you could use the quorumd instead of the “two-node” module. Or you could use the “pingable” module instead of the “two-node” module. Or you could at the end always tack on a “human” module, in case all else returns TIE. This is kind of cool, actually. My favorites for next implementation are the pingable and consult human modules. And, of course, if your cluster loses quorum due to real server failures failures, there are always ways to work around it, with a little human intervention. One method is to tell Heartbeat to ignore quorum. Another is to tell Heartbeat to remove certain nodes from the cluster, after you verify that they’re really dead. And, I’m sure that in a pinch, some new methods will be invented. And some of them might actually work ;-).


Regarding the quorumd, it seems that this is an extra server that will generally run on another machine separate from the rest of the cluster. So if we had a two-node cluster with a quorumd then it would effectively be a three-node cluster where one node is not configured to run any resources. It seems that the simpler approach in many cases would be to merely have a three-node cluster with resources not configured to run on one of the nodes. For example if I was running a mail server cluster for an ISP I might configure a three node cluster of the two mail server back-end machines and one other machine that is lightly loaded (EG a DNS server) and have it configured not to run MTA resoures on the DNS machine.

30 April 2007

Mark Brown: One step forward

It depresses me to see people thinking that the way to get changes affecting many packages done in Debian might be via general resolution or that a number of people seem to feel that getting something accepted into policy is a first step in getting anything big done. Debian may be big and prone to arguments but it’s a shame to see people in Debian who think we’re that dependent on process to get things done. This makes me all the more happy to see something like the Smith review project ticking away. It’s all being done on the basis of “Hey, this seems like a good idea - anyone object or want to help?” and by the time it’s done it will have touched every package in Debian which is getting on for as ambitious as it’s possible to be. So far it seems to be getting positive responses from maintainers - I’m sure there will be problems somewhere along the line but I’d be surprised if they were anything other than a tiny minority.

Next.

Previous.