Search Results: "ag"

26 January 2008

Martin F. Krafft: Thai massage lesson learnt

Here s an important lesson I learnt today: if you are in Thailand and still feel the effects of a not-so-recent knee and wrist injury, you should, before the massage, learn how to say in Thai: please, go easy on my knee and my wrist. The rest of my body likes brutal Thai massages (well, learnt to like them), but when the knee is bent and twisted and my face inadvertedly morphes in agony, the typical massagist will apologise furiously and take it easier from now on not what I want, at all. Three Thai hanging out on the street, asked individually, could not translate I like it rough but my knee does not. Instead, they just giggled and wanted to know where I was from and where I was going and whether I wanted a massage or attend porn shows or buy drugs or well, that about lists it all. No blame for the average Thai s broken English, it s still better than my command of their language.

Matthew Palmer: Looking Behind The Proprietary Curtain

It's interesting to compare the "marketing features" of proprietary version control systems and the FOSS equivalents. For example, I happened to stumble across SourceGear Vault, and I have to say that the feature list, as given, doesn't impress me particularly. When the most impressive features you can think to mention are things like "All repository data is stored in a SQL Server database" and "the checkin operation is atomic", I'm thinking you're probably not a serious competitor against some of the truly state-of-the-art systems that are commonly used in the open source world. Based on the advertised features, I'd say that Vault probably doesn't compare favourably to SVN, let alone bzr or darcs. Overall, I don't think we're doing so badly in the innovation stakes. <grin>

Julien Danjou: Moving old projects to git

I finally did it. Most of my small and personal projects (telak, sysrqd and mod_defensible) were maintained in my home-svn-repository. This had the side effect that I did not have a good overview of the current status of the project, and that I never though about tagging releases. I used git-svnimport to move this stuff to git, with great success. Now, I see that only one release on three is tagged correctly, bad me. They are now on my git server. But with a better tool like git I'm sure I will be more precise when I will work on that source code, so it was time to switch. And now my source code is public, which is far better than before.

Aigars Mahinovs: In a quest for perfect sweet buns

Sweet bread
Recipe in the image description. Got up at 7 and made a surprise batch of sweet buns for breakfast at 9. Girlfriend was very impressed. :D

25 January 2008

Martin F. Krafft: Singing: One Day in Bangkok

After a few amazingly efficient days at home, working on netconf (but not getting to where I wanted) and preparing the presentation I deliver on Thursday at LCA 2008, and tying up other loose ends, I found myself in front of a television set Friday morning to witness the beginning of Federer s defeat in the Australian Open half finals. Unfortunately, I had to leave at the start of the third set and no-one in the airport knew of the game, so I had to call a friend from the plane to get the final result: 7:5, 6:3, 7:6, Djokovic won. I like Federer, and enjoy the Swiss fandom from everywhere, but his tennis wasn t up to his normal level, a true shame. Djokovic has been my favourite for about a year now, so I am excited by the result, but it would have been better to see a bit more of a battle between the two. I trust he ll win on Sunday and cross my fingers! It kind of bites to arrive in Melbourne on the day of the finals, knowing that I would have had a chance to get a ticket and could have travelled a day earlier. Oh well So I am sitting here in a crap Bangkok Internet cafe, finishing off my presentations. In addition to the netconf talk, I am also talking twice at the Debian Miniconf on Monday: first, the State of the Debian project address , which I agreed to do very short notice but knew that I could count on my colleagues to help (don t read the thread before the talk ); second, I also have a slot to talk about version control systems and Debian packaging, a topic that has been on my mind for almost three years now, resulting in elaborate workflows and many discussions. It s also becoming more and more of a hot topic for the entire project. I am tired. We landed at 5:30 and I was shattered, not having been able to shut an eye throughout the ten hours of flight. Fortunately, they let me into the lounge in the arrival area, where I crashed in one of their slumber rooms and got close to four hours of sleep, successfully ignoring the chatter from outside why did Thai Airways lay out their lounge in such a way that the slumber rooms are right next to the staff rooms with the squeaky doors? One thing about living in Asia, where space is scarce, is that people here never seem to mind about noise and sleep through anything. So I did too. I took a shower, ate some breakfast and headed into the city. I was impressed by the new Bangkok airport Suvarnabhumi , which definitely is a step up from the old, horrific one. However, I tend to doubt their claim that they could scale from the current 45 million passengers per year to 110 million. The walkways are too narrow, there are way too few toilets around, and immigration is painfully slow despite the large number of open alleys. Now in downtown Bangkok, I am biding my time. I have been here a few times before and have a number of routine stops, such as visiting the retail manager of the Jim Thompson Company, a loveable lady who speaks fluent English and is very fun to talk to. I met her during my last trip to Southeast Asia, but have since not been in touch. I now plan to head to a massage place, where they deliver merciless (and thus excellent) Thai massages, and then on to some market or Chinatown for food. I ve been training myself on chili ( Thai chocolate ) consumption for this moment: to walk up to a food stall, order a curry, and answer Thai hot when they ask for the degree of spicyness, given that I m a foreigner. At midnight, my plane leaves for Melbourne to arrive on Sunday afternoon. I have little clue as to what awaits me. I ve been to quite a number of conferences, but always perceived LCA to be somewhat special. I am definitely looking forward!

Jaldhar Vyas: youw haiw is ewewywhewe scweaming infidewities

Shailu's new glasses Shailaja got new glasses. She needs to work on the frown though.

Meike Reichle: Look Ma I'm on Podcast!

I recently had my first podcast experience, when I was approached by Mario Heide of the German podcast pofacs.de ("Podcast für alternative Computer Systeme") who asked me for an interview. To be true, I first had to read up a bit on podcasts, but after a little research I was very happy to accept his invitation. We did the interview via Sykpe, which wasn't exactly optimal sound-wise but still very nice. We talked mostly about Debian, primarily from a first time user point of view. The (German) interview is online now and will, as I just heard, also be included on the next LinuxUser magazine CD. If you do understand German also have a look at the other podcasts there and thanks again to Mario for giving me the opportunity to brag a bit about Debian.

Patrick Winnertz: subfolder support for mutt-patched

I've written some days ago a patch for the mutt sidebar patch in order to enable subfolder support there. The big issue was that if there were folders as "Debian/mc/commits" they were displayed as "commits". So everything before the last / is cutted of. In order to fix this I've to replace this piece of code:
 const char *basename (const char *f)
 
  const char *p = strrchr (f, '/');
  if (p)
    return p + 1;
  else
    return f;
 

with this piece of code:
char *sidebar_foldername(const char *folder)  
  char *p = strstr (folder, NONULL(Spoolfile));
  if ( (p) && !strcmp(folder, p) )
    return p + strlen(NONULL(Spoolfile)) + 1;
  else  
    p = strrchr (folder, '/');
    if (p)
      return p + 1;
   
  return folder;
 

and (of course) fix the function call in draw_sidebar ;-). And hey.. subfolders are displayed correctly now in the sidebar. I've send the patch to the debian maintainer and I'll hope that he like it. :)

Dann Frazier: Etch and a half

For those unfamiliar with the project, etch-and-a-half has the goal of making the existing etch release work on more hardware, but with minimal risk to existing etch users. This will be done by *adding* new kernel packages to the existing release. Kernel selection isn't final yet - the kernel team would like to use 2.6.24 if it proves itself stable in time; 2.6.22 is the backup choice. etch-and-a-half isn't restricted to kernel updates by-definition; new X drivers, or proven-safe X driver updates are reasonable candidates as well (though at this point, no changes have been proposed). An oft-asked question is around updating desktop packages, e.g. new versions of GNOME/KDE. This is beyond the scope of etch-and-a-half because it introduces a great deal more change than just additional hardware support, its wouldn't be a transparent upgrade to existing etch users, and we cannot say with a high level of confidence that it wouldn't introduce regressions for existing users. That said - a localized change to a package that adds support for new hardware and clearly doesn't break existing hardware is a valid candidate for any stable release. Such requests should be submitted to the SRM team like any other stable update request. The current plan for etch and a half is to release as part of a point release. 4.0r4 is the planned point release, since 4.0r3 is planned to have a quick turnaround to fix issues with 4.0r2. This means that pre-release bits will be made available via proposed-updates - testers are greatly appreciated. There is no plan to add support for etch-and-a-half to the etch branch of d-i. Rather, support will likely be added in a beta of the lenny installer. A wiki page exists here, and a coordination list has been setup on teams.debian.net.

Neil Williams: New uploads and embedded issues in Debian

I've got an upload of gpe-tetris pending - see 462306 - to provide a smaller version of the popular falling blocks game for embedded devices. One or two things crop up from this package:

  1. popcon - a lot of maintainers put a lot of store by popcon results but the popularity-contest package is perl and perl is not available in Emdebian (it is thrown out along with "Essential: yes" for space reasons). Writing a replacement for popcon may not be particularly sensible either because embedded devices, although often left running for long periods in a "low power" mode, often have rare and intermittent access to any form of internet connection. This could easily result in maintainers thinking that because a package has few (or even zero) popcon figures, it is not used. On the contrary, the package could simply be used on devices that either do not support perl (Emdebian) or which do not have the ability to file popcon reports despite being able to support perl. (With the probability that GPEPhone will be added to the GPE support already in Debian, users may not wish to have popcon "phoning home" because it would likely cost real money to do so - even if a C version of popcon was written.) So I'm posting this here so that I can refer back to this post if queries arise later on.

  2. GPE apps on Debian - gpe-tetris is inherently designed for small devices with small screens and relatively slow processors, just like the majority of GPE. gpe-tetris is also designed to be usable on a handheld device where the lack of a normal keyboard can make game play awkward. As a result, playing gpe-tetris on an average Debian box is likely to appear trivially easy and the "progression" between levels would appear very slow in comparison with the tetris available in GNOME or KDE. This is deliberate and is expressly intended to allow the game to be playable on embedded hardware that has fiddly little keys. (I'll be adding this to the manpage and a brief summary of this to debian/control.) This does give the opportunity for a little sleight-of-hand such that a device could be provided with a highscore file created on a much more powerful device and so preventing any new highscores being set, but please don't do that - play nicely!

  3. small apps != bad code - Yes, lots of GPE packages are very small, some were clearly written originally as "demos" or during the process of learning how to write larger packages. This does not necessarily mean the packages contain bad code. I will feed back sensible patches to upstream to resolve flaws in the code but please do not think ill of the packages merely because the source code looks "trivial" compared to a GNOME package.

  4. dpkg-shlibdeps - one issue that I must begin to track after Fosdem will be to aggregate the "foo should not be linked against" messages from dpkg-shlibdeps in GPE packages and try to build a complete picture, in case there is a real possibility of completely dropping some packages that always seem to appear in that list due to the pkg-config --libs gtk+-2.0 listing. If so, I'll begin discussions with upstream about manually specifying the GTK_LIBS variable whilst retaining the PKG_CHECK_MODULES macro that ensures that the -dev package is available in the cross-building environment. This is likely to be some form of database-query mechanism - feeding data in from grepping the build logs, building a query from the list of packages to be used for a specific Emdebian root filesystem (machine/variant specific) and then spitting out whether particular package sets can have particular targets removed. If anyone fancies working on that already, the Debian version of the information is already available via the buildd network and the Emdebian cross-build results will not differ greatly from those at this stage.

Other uploads include updates of libgpeschedule, gpe-calendar and gpe-clock if gpe-announce makes it through NEW as expected. Updates for emdebian-tools and apt-cross and likely new releases for QOF, gpe-expenses and pilot-qof.
debcheckout compliance
In other developments, I've worked out how to specify Vcs-Cvs correctly such that debcheckout can find the repository data correctly. Sadly, vim syntax highlighting does not help with the CVS version but the CVS syntax is:

Vcs-Browser: http://alioth.debian.org/plugins/scmcvs/cvsweb.php/dpkg-view/?cvsroot=dpkg-view
Vcs-Cvs: :pserver:anonymous@cvs.alioth.debian.org:/cvsroot/dpkg-view dpkg-view

Note the colon prefix to pserver and the space between the repository login location and the module name. Remember to omit the "-d" - debcheckout will add that for you (and won't check to see if you have already specified it).

Benjamin Mako Hill: Planet Debian Searching

In the "bits from the Planet Debian maintainer" department... Steve Kemp has been running a little index and search script for Planet Debian for a couple years now that lets you search for old entries that have showed up on Planet Debian. He was going to take his system offline but, since it was in use by a variety of people, he opted to move it into the default Planet Debian instead. You should be able to see and use the search box in the sidebar on Planet Debian now. Feedback is welcome, I'm sure. Thanks to Steve for the fantastic addition to our aggregator.

Cord Beermann: Today i kicked 560 Mailaddresses off lists.debian.org ...

... because they are bouncing.

In my ongoing attempt to investigate and fix problems of our mailinglist-server, i found that we only had a working bounce-detection for lists starting debian-* minus debian-private and the three digest-lists.

So i rewrote some parts of the bounce detection:

We now have four categories of lists:


for these four categories we calculate a spam-rate depending on the number of distributed messages and the number of bounces in the timerange of 24 hours for 'high' lists, 7 days for 'medium' lists, 30 days for 'low' lists and 90 days for 'very-low' lists.

If the Spamrate exceeds 80% for unmoderated, and 60% for moderated lists, and bounces have been seen for more than 24 hours we kick. (these rates are subject to change, when we have implemented the warning mechanism)

So these changes implemented a bounce-detection for debian-changes-digest and today we reached the level of 60% bounces for more than 500 subscribers.

So what next?

To finish the bounce-detection, i want to implement something which tries to notify subscribers about bouncing mails. This is useless for 'hard'-bouncers, but people with some smaller problems like mail2news-gatewayers this could be helpful. I also want to implement something which sends out unsubscription notices for three weeks after the kick, so kicked out people can resubscribe after they have sorted out the problems.

Both should fire once a week per address.

What do you think?

Neil Williams: collaborative maintenance, source packages, patches and other disagreements

Firstly, I haven't been following debian-devel as closely as in recent months and some things have passed me by. Secondly, I am rather pre-occupied with my own small world of Embedded Debian. One result of this is that I wasn't really paying attention to arguments over the source package format and took longer than I expected to respond to a request to take a look at tslib - a touchscreen library for embedded devices. When I did start work on it I managed to upset Joey Hess by implementing dpatch support which he had recently decried as unhelpful. I also added some extra fuel by getting myself in a two-and-eight over svn-buildpackage and it's broken bias towards native packages.
I happen to disagree with the idea that maintainers should alter upstream files directly, merely relying on the .diff.gz or some weird $RCS runes. Instead, I seek to ensure that the .diff.gz contains no changes outside the debian/ directory. I'm not happy keeping the entire upstream source in yet another RCS (for any reason) and would much rather make updates to my Debian packages by simply copying the debian/ contents into an unpacked pristine upstream source (preferably via uscan). I find it really useful to simply check out the latest CVS/SVN/$RCS, dump debian/ into place and call 'debuild' when testing various upstream development issues. Maybe this is because I have relatively few Debian packages that need debian/patches/* and certainly few that need more than a couple of patch files. It certainly has a lot to do with my embedded work where I need to make changes to the contents of debian/ to make an Emdebian package whilst retaining the same upstream code as is used in existing embedded projects like Open Embedded and Familiar. I don't want to be chasing changes through the upstream source - I want all the changes in a single place so that I can create Emdebian patches against the Debian source. (I'd rather not have patches in the Debian source at all but this is only realistic for either my own packages or those released as part of GPE for various embedded-native compatibility reasons.) I certainly do not want any Debian $RCS to be lumbered with yet another set of upstream sources that will always be out of date compared to the real upstream sources.
I am also a great fan of CDBS - much to the horror of some in Debian - primarily for one very simple reason, it cross builds so easily. Considering my workload, it should not be a surprise that the ability to support cross building without requiring any changes to the Debian package is incredibly persuasive when selecting a build system for a package of my own. debhelper really is woeful at cross building - each package needs customised cross building support painstakingly devised and tested, making script-based mass bug filing impossible. CDBS shows that with a little wrapping, debhelper can support cross building in a clean and completely non-intrusive manner.
This means I can concentrate on those changes that are actually important - the changes that provide the benefits of cross-building and justify the effort of actually cross building the entire dependency chain: the ability to fully control Debian-specifics like "Essential: yes" and to disable, modify or adapt components of any package such that the installed system has a fraction of the dependencies of the Debian version of precisely the same package. TDeb support is good too but that can be implemented against any build, it doesn't need to be a cross build.
Sadly, the end result of all this for tslib is that it will be removed from collab-maint very soon, Joey does not wish to be associated with the new version because although it includes some features which he is happy to see implemented, my use of dpatch and the hacks I had to devise to workaround svn-buildpackage do not fit with his workload patterns. Once tslib is removed from collab-maint, these hacks become redundant and I can use my normal packaging methods. Equally, his methods (in particular the lack of debian/patches/*) do not fit with my workload patterns and although I do not have as many packages as Joey, I have enough (when the 200 Emdebian source packages are also considered) to make the issue into a blocker. The new version of tslib uses the upstream SONAME and adds a -dbg package so it will spend some time in NEW. I am also likely to migrate it to CDBS once removed from collab-maint.
I suspect these issues will be revisited during discussions at Fosdem 2008 where I'll be presenting two talks - one in the Debian developer room and one in the Embedded developer room. Feel free to harangue me if you feel strongly that there is a sane way of cross building that does a better job than CDBS. :-)

Biella Coleman: Berkman Center no longer seems to be hosting dvd-discuss

Before I post the longer version… I am looking for a full copy of the dvd-discuss archives. Does anyone have it?? The Berkman Center, who had been archiving them is no longer doing so!! (hard to believe), even though they have a broken link from this page. There are some archives I have found but they seem incomplete. If you have earlier mailing list archives, please please let me know! update: So thanks to some help I have the earlier archives on the wayback machine but they should be archived on the same spot, no?

Isaac Clerencia: A long time ago

… I used to write in this blog about random things. Let me check what I have done lately … well, first of all I spent 10 days in San Francisco in November, I had a really great time, we spent most of the time there but also paid a visit to the Googleplex, Stanford, Berkeley, … and went several days to the Yosemite National Park, a great trip overall :) Besides that I gave up one of my jobs (the boring and not challenging one …) two months ago (although it seems like it was ages ago) and started working full-time in my company. In addition, I spent New Year’s Eve in London to begin the year in a different way :) Right, that was all :P

Mohammed Sameer: I love KDE. It just works!

I have 2 laptops. My personal one at home and my work one at the office. Both are running testing. A month or two ago, I did a dist-upgrade on the home one. Later on I rebooted (DUH!) it for a reason I can't remember just to end up with very tiny fonts under GNOME. It took me some time to tweak them back again and play with the GNOME anti-aliasing dialog. Now if you know me well, you know that the last thing someone should do to me is to touch my font settings. I have a very sensitive eye (Because I have a very low vision) and I hardly tweak the fonts. All went somehow fine after that. Problem is I wasn't sure whether it was fglrx or GNOME who's responsible for that. read more

MJ Ray: Links for 2008-01-25

Nick Leeson: The financial storm is not over yet
Surreal to see his byline on an article the same day as a rogue trader comes to light... "Cutting interest rates has stemmed the flow for now, but 2008 will see higher energy costs, higher food costs and higher importing costs which will damage consumer confidence. Right now we can only look to Davos and hope that the global economic leaders can keep positive and stop the markets from spiralling further downwards"
SFinfo TV Schedule for Sunday
SFinfo is carrying some of the Davos meeting live again (where corporations tell governments how to direct their populations). Only interesting thing left in my opinion is the Climate Change forum on Sunday morning. Watch and see where our glorious overlords will be taking us.
How to block all Facebook application and message spam
Practical freedom from Matt Lee's Exploring Freedom.
Valuing Users by Allowing Comments : David Lee King
It makes sense - you know it does.
Internet Psychology: Podcasting? That's old-fashioned - video is the online future by Graham Jones, Internet Psychologist
Maybe I just forgot the obvious, or maybe we haven't really seen what people can do with podcasting yet.
Gaba en San Pancho Blog Archive what things to check when buying an used car
Worst used car I ever saw had a split hose leaking petrol from the carb feed onto the engine block - switching that one off when I asked was the fastest I ever saw a car salesman move!
Modern Communicator: Imarco Activ-Media have been acquired
Personally, I find one of the benefits of working in cooperatives is that it's very difficult for us to be acquired and good collaboration is much more common than merging.
sab39 ... O noes, somebody I don't like did something I agree with!
I feel the point about the bozo bit is well-made. Is one of the few features of my weak memory a low probability that I keep the bozo bit set in the long term?
How You Can Fine-Tune Your Blogger Personality Perception
How do you repair a broken perception? Can you repair it, or is it time to delete the blog and start again at a new address? Can you start again, or does web.archive mean past mistakes will hurt you forever?
robmyers - My Ogg Player
I never succeeded in accessing anything besides basic file upload/removal on my YP-U2 and Samsung Support broke promises they made to me.
another blog is possible Give cyclists a break
"Those of you drive should read this article and change your behavior towards cyclists. You may not like cyclists in the road, but they have every right to be there."

Steve Kemp: Painted wings and giant rings make way for other toys.

This week has mostly involved me getting my live mail filtering site up and running with a guineapig or two. This uses a custom user interface to allow users to manage the filtering settings for an entire domain: In terms of implementation this is an SMTP proxy which is built upon the qpsmtpd framework. I've got both the user interface and a collection of plugins reading all data from an MySQL database. The practical upshot is that if you use the service you'll get less spam, and anything that has been rejected will appear in an online browsable quarantine for a period of times allowing you to view mistakes/rejected mails. Any mail you didn't want, providing you've got the spam-filtering plugin enabled for your domain, you may send back to be trained as spam. It scales nicely, doesn't appear to have lost any mail ever in real-world testing, and could be useful.

Stefano Zacchiroli: bts followup

New bts command: followup In Debian I'm pretty sure we have many perfectionists. Sadly, I'm one of them: I can't help loosing lots of time fixing silly things totally useless with respect to a more important task which is waiting to be completed. An example? Following up on BTS bugs. If I have the original bug report in my mailbox that's easy, I just hit r on mutt and reply as usual (ok, I will still loose some time getting rid of unneeded quoted text, but that's not too much). If I don't have it ... tragedy! I then have to open the bug log in the browser and compose from scratch a new mail including several information which I have to manually grab from the bug log web page: (Yeah, I know, it looks like I'm hopeless, but I'm confident some of the people reading do actually share this and similar dramas.) Missing (or maybe overlooking) a tool helping me out on this, I've patched devscripts's bts to automate the above steps. Now I can do:
bts followup 430986

to end up in a mutt mail composing session with proper (according to the definition of "proper" above) recipients, headers, and quoted text:
From: Stefano Zacchiroli <zack@debian.org>
To: 430986@bugs.debian.org, 430986-submitter@bugs.debian.org
Cc: 
Bcc: 
Subject: Re: when reporting bugs by maintainer, please include Uploaders
Reply-To: 
In-Reply-To: <20070628174236.13848.57178.reportbug@aquarium.takhisis.invalid>
On Thu, 28 Jun 2007 19:42:36 +0200, Stefano Zacchiroli wrote:
> Package: bugs.debian.org
> Severity: wishlist
> 
> Browsing bugs by maintainer (and with this I mean something like
> http://bugs.debian.org/cgi-bin/pkgreport.cgi?maint=zack@debian.org, or
> it shorter form http://bugs.debian.org/zack@debian.org) used to be
> terribly useful as a TODO list. Using that I used to have a simple entry
> point for knowing what I have to do "for Debian" regarding my packages.
> 
> This usefulness has diminished a lot with the spreading of team
> maintenance. To know all bugs that apply to me indeed I know have to
> repeat browse by maintainer for each team I'm a member of.
> 
> It would be terribly useful to include bugs which apply to packages in
> which I'm mentioned as an Uploader in the report by maintainer pages.
<snip>

Now I just need to actually perform the original task, the problem now being that in the meantime I've forgotten what was it about ...
Try it out: Comments?
Anyone else find this useful? If so I can just go ahead and commit it to devscripts mainline ...
Update: some changes to the code, thanks to Adam Barrat for the feedback.
Changelog:

Wouter Verhelst: Samba v2

samba.grep.be. This machine has been my trusty publically-accessible server for about four years now. It runs my website, including this blog, is my primary MX, contains my subversion repositories, and my gallery. For slightly less than the first year of Planet Grep, it was the only machine running that site (it has now been migrated to two machines running in two different data centers, to cope with the ever-increasing bandwidth usage of that site). It runs the bacula-director for our backup system, and it contains the modem behind our fax number, allowing us both to receive faxes and to log in using PPP to our local network. Most importantly, I've been using it as an SSH jumphost and IRC box to allow me to connect to other machines whenever I'm behind an overly paranoid firewall. But now it's time to retire the machine. The high number of services combined with the, to today's standards, low number of available system resources, is beginning to be a problem. A few times now, already, I've had to reboot the machine because a load spike was making it unresponsive. So it has to go. Many people will be shocked to find out that the machine powering samba up to now was an IBM SurePos 500. No, really. The reasons are long and complex, but suffice to say that there was a point in time where I wanted to set up a server for myself, and I had an idle, never-to-be-used-anymore, 2000+ priced, machine standing by. So there I went, usurped this machine as server, and have given it near-100% uptime. If you want to know just how near-100% that is:
  9 Power_On_Hours          0x0032   058   058   000    Old_age   Always       -       31170
[...]
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       99
Or, in plain English: according to SMART, the hard disk has seen just 99 power cycles in four years. This machine was never designed to do that. Side note: yes, that is a touch screen on top of that box. The new machine is much, much better. We're going from this:
model name	: Intel(R) Celeron(TM) CPU                1200MHz
to this:
model name	: Dual-Core AMD Opteron(tm) Processor 1210
which is much, much better. The box actually containing this processor is also much, much better. However, there was one problem: the old processor was a PentiumIV-class processor, requiring Debian's i386 port, whereas the new one (obviously) contains a processor that will allow me to run the amd64 port; and I did intend to do this. Additionally, I wanted to migrate from a simple "root-on-partitions" system to a "root-on-LVM" system, with Xen somewhere in between. As such, simply rsync'ing the entire hard disk on the old system over to the new system (my usual way to migrate a non-critical server) wasn't going to work. Luckily Debian isn't too hard to migrate from one machine to the other, however. Or, well, that was the idea. Because I forgot about one silly detail: if I wanted to make everything work out correctly, I would have had to keep UID numbers in synch. Unfortunately, I forgot about that; and as a result, a number of files were created with the wrong owner. This made all kinds of things fail horribly; and rather than stop and think about it, which would have made me copy the old passwd file over from the old installation, add some extra lines for users that were on the old server but were not yet created on the new one, and then finally leave it at that, everything would've been fixed. Instead, I started to change ownership of files all over the filesystem, creating a mess of things. Silly me. But, well, in the end I did get everything to work correctly; even if it took me longer than expected. No worries.

Next.

Previous.