For those interested in the politics of science, or to be more specific, how science is flagrantly twisted to keep important facts and findings about our public health from public view, this book
Doubt is Their Product: How Industry’s Assault on Science Threatens Your Health by
David Micahels looks like a must read. For those wanting a little
here is a review of the book.. In short, the author shows how occlusion comes from the need to secure and protect profits, and is achieved with what he calls the alchemy of twisting numbers and facts:
“It’s quite easy to take a positive result [showing harmful effects] and turn it falsely negative. This epidemiological alchemy is used widely.”
The problem runs deep as this other article from Slate magazine
also indicates. But there are some good sources to get and evaluate your science and health news and
health news review seems like one important place to go.
How to generate bootable USB keys with simple-cdd
simple-cdd is a
lovely piece of software that builds a custom
D-I image with the
package selection and preseeding of your choice.
Today I was asked to build a bootable USB key with the
simple-cdd image. Here is how; the general case is described
in the
d-i manual:
General USB key preparation:
- download
vmlinuz and initrd.img from
hd-media
apt-get install syslinux mtools mbr
- Partition the USB key as needed (from now on, I'll assume the
usb key is in the device
/dev/sdb1)
- Format it as FAT:
mkdosfs /dev/sdb1
- Put the boot loader in it:
syslinux /dev/sdb1
- Put the MBR in it:
install-mbr /dev/sdb
- Mount it:
mount /dev/sdb1 /mnt
- Copy kernel and initrd:
cp vmlinuz initrd.img
/mnt/
simple-cdd specific part:
- Run
build-simple-cdd as usual
- Copy the ISO file generated by
build-simple-cdd in
the USB key. Any name will do, as long as it ends in
.iso the installer will find it
- Configure the boot loader, fetching the kernel command line out
of the cdrom boot loader generated by simple-cdd:
echo default vmlinuz > /mnt/syslinux.cfg
grep append tmp/cd-build/etch/boot1/isolinux/isolinux.cfg
head -1 sed -e 's/^\t//' -e 's/ initrd=[^ ]*/
initrd=initrd.gz/' >> /mnt/syslinux.cfg
This is it, it works nicely, perfectly scriptable, tested
today.
DSA-1571 is totally embarrassing. But I disagree with
Julien BLACHE: we don’t need a new openssl maintainer. Mistakes sometimes happen to people who do things. That sucks, but it’s unavoidable, no matter how many levels of checking you add. Kurt has done a lot of excellent work on Debian in the past years, and I’m sure he will continue.
Of course, it’s a lot easier and less risky to write
tons of stupid blog posts.
By the way, Julien, there’s an
RFH bug for openssl open for more than 2 years. What about getting involved and helping Kurt yourself?
On a more constructive side: it’s not the first time that a Debian-specific change broke something (I can think of a recent grep change …). It might be useful to provide a simpler way to review those changes (reading the diff.gz files is not really user-friendly). We could have something like http://patches.ubuntu.com/ (or even something nicer :-).

So far, if you want to use KDE 4 under Debian, you need to install them from experimental. Under the ground, we prepared up-to-date packages from trunk (soon uploaded) and I took a snapshot of my current desktop:

We didn’t know yet if Lenny will be shipped with KDE 4 but we hope it will be in good shape to have it. Everyday, improvements are done and the desktop is enough stable/solid to be used on a day to day basis.
On other side, I reported a bug on plasma panel alignment isn’t saved and some hours later, Marco Martin (mart) fixed the issue \o/
Tips: if you want to have a transparent panel, you need to enable compositing.

Just the other day I was wondering about what release of Debian a specific version
of a package was in, and I knew it was older than oldstable. But searching the Packages
files of
archive.debian.org was tedious and
I thought that there has to be better way. So I quickly set up a packages.debian.org
instance for archive.debian.org at
archive.debian.net
I guess this isn't really interesting for the day-to-day use, but maybe someone can ocassionally
profit from it.
Caveats:
- There are no binary files on archive.d.o for rex and buzz, so currently no information
is available about them.
- There are no Sources files available for rex, buzz and bo, only Packages, so no information
about the source packages can be presented.
- The two above point of course mean together that there is no usable information at all about
rex and buzz. If someone would create the missing indices and convince the ftp-masters to
put them on archive.debian.org, I will gladly configure archive.debian.net to use them.
- Changelogs and copyright files are currently only available for pool-using releases, since
the extraction script has some assumptions that depend on that. On archive.debian.org,
the only release that uses
pool/ is woody.
Feel free to help me improve that site, preferably by sending patches against the
archive-master
branch of
git://git.debian.org/git/webwml/packages.git.
I won't repeat it here, but there's
DSA-1571-1 waiting for your attention,
especially if you made some material out of
openssl over the last couple of
years or so. Yes, you read it right: COUPLE.
Upgrading to the new OpenSSL is easy. Generating new keys is another story.
To save (or add to, depending on how you handle this) your pain, there is a
simple checker that can currently see if your OpenSSH or OpenVPN public
keys are weak enough to warrant replacement. I await a version that can handle
X.509 certificates too (though I only just generated a new one today, before
the announcement, so that means I have to do it again (and get its CSR to
CACert for signing, etc.)
And yeah, if you're running
openssh-server, consider regenerating your
host RSA and DSA keys, e.g.:
# mv /etc/ssh/ssh_host_ dsa,rsa _key* /some/place/else
# dpkg-reconfigure -plow openssh-server
That should regenerate your keys
and restart openssh-server once the new keys
are installed to
/etc/ssh.
The
hard part (of making sure all the keys of your systems are updated and
tested) is still up to you, however.
UPDATE:
The Debian wiki has up-to-date information regarding other
packages that generate SSH/SSL keys at postinst. Please refer to that while
the
key-rollover page isn't up yet.
UPDATE 2:
openssh-server is updated (with corresponding
DSA-1576-1) that is linked to the updated OpenSSL library. Be sure to
upgrade! The new package also pulls in
openssh-blacklist, a new package
that contains the database needed by the new
ssh-vulnkey for checking SSH
public keys.
NOT.
Also see #363516.
Genius.
Now regenerating every single SSH key, SSL certificate and whatever else I can identify that’s been produced by one of the Valgrind-clean openssl. Also expiring and changing every single password I’ve ever typed in a vulnerable SSH session (be it at login or in the session).
Updating the packages on the machines was fun already.
Worst Debian day ever since the 2003 compromise. And that was a BAD one.
I guess we need a new openssl maintainer, we obviously cannot trust the current one(s).
A little off-topic exercise conducted in the "eye of the storm", when
Ilenia and Helen were still in the hospital:
A
post on Seth Robert's blog brings up the idea that many Chinese restaurants were opened as a way to go into business without competing with native male workers. The post made the rounds of several
other online journals.
That was the push I needed to get up and go collect a few statistics of my own, regarding an idea I've been kicking around for a while. My theory is that the number of restaurants of a given type, divided by the number of immigrants from that country might be an interesting way of guaging the popularity of the cuisine in question.
In order to simplify things just a bit, I actually used data from Italy, for the following reasons:
- Most immigration to Italy is pretty recent, so it's not necessary to account for the length of time different immigrant groups have been present, and the effects that may have had on the diffusion of a given cuisine.
- Immigration statistics were readily available: http://demo.istat.it/str2006/index.html
- Italian the language almost completely corresponds to Italy the country (outside of a chunk of Switzerland, San Marino, and the Vatican), something that makes things that much easier.
- I speak Italian, so it was easy to find out all the information I needed
Unfortunately, finding out the number of restaurants of various types is far from an exact measurement, and since this is a quick fun project, I just went for Yahoo search (they deserve credit for keeping their search API open when Google's was closed) results on terms like "Ristorante Turco" (Turkish), "Ristorante Messicano" (Mexican), and so on. This was the most expedient means of gathering information quickly, but this approach does present a number of obvious problems, listed here in the hope that someone without diapers to change and a business to run might come up with some good answers:
- Some hits likely come from people talking about a restaurant that happens to be in a country, like "ristorante americano". "Nel tipico ristorante americano, ...." or in other words, "In a typical American restaurant", rather than an American-style restaurant in Italy, which is what we were looking for in the first place. This is probably also true of countries close to Italy, where people go on vacation and thus have occasion to write about their experiences in a "ristorante tedesco" (German), rather than going to eat in a German restaurant in Italy. Perhaps the search query could be improved in an attempt to eliminate this sort of false positive.
- Some restaurants probably are not known as, nor brand themselves with a country name, but instead utilize titles like "Middle Eastern", "Arab", "South American", "African", or others that do not correspond with any one country in particular. It would be possible to group countries together with other adjectives, and get statistics for these clusters as well.
- Measuring hits is measuring what people are talking about, rather than simply restaurants that exist, so if restaurants from a certain country are more talked about than others, that would muddy the statistics a bit. However, it seems reasonable that people would mostly talk about restaurants in proportion to their popularity, and I don't see a particular reason why there would be more talk of Vietnamese restaurants, say, than Thai restaurants, compared to the actual numbers.
That said, for a quick project, this approach seemed to work out ok, and the results appear credible. Obviously, the results also reflect people discussing certain cuisines, rather than an actual number of restaurants, but since it does reflect
interest, we'll use the number in any case.
Since the number of restaurants/interest in a type of restaurant was clearly not correlated directly with the number of immigrants, other factors must come into play. For instance, "ristorante giapponese" turns up 125,000 hits, but the stats say only 6873 Japanese nationals live in Italy. As above, hits don't mean actual restaurants, but clearly Japanese cuisine is not being popularized through immigration.
Here's my guess: these statistics show, to some degree, what people in the host country actually like to eat. Food that tastes good means more restaurants. Things that aren't that popular mean few restaurants, even if there are many immigrants. To pick on one country, there are many Philippino immigrants in Italy, but very few search hits - and anecdotally, I've never seen a Philippino restaurant in Italy either, whereas even smaller towns like Padova have Chinese, Mexican (well, it's called that, even if it's a shadow of the real thing), Japanese, various Arab and middle eastern restaurants, and even a few less common things like Eritrean. And I know that many native and foreign restaurants employ Philippino cooks.
Below is the chart I whipped up showing the number of Yahoo hits per immigrant. The Italian names shouldn't be too hard to figure out. A few tricky ones: Giordano-Jordanian, Giamaicano-Jamaican, Spagnolo-Spanish. If you're interested in numbers or source code, contact me.
Imagine, for a moment, that you are a young man in your 20s, trying to make your way in the world. You are married and have a young daughter, just old enough to start to talk. You live in a run-down neighborhood, long passed-over by any economic advances. What schools you had access to barely taught anyone much. The few jobs you can reach have fierce competition, even though the pay is low. You worry about your health, but even more about that of your wife and child. Finding food is a constant concern. Although you are still healthy now, and you are willing and able to be a hard worker, there is simply nobody hiring people in your area. Not to mention the gunfights that erupt between gangs or drug dealers. Oh, and did I mention that your wife is 4 months pregnant?
Your top priority is to do your best to keep your family safe. You're afraid that your whole family will starve, or be killed by an errant bullet. You've tried for a long time -- it seems like forever -- to do everything you can think of, with no success. Finally, you decide that the only way you can have the hope for a better life is to move somewhere where the economy is better, and the drug dealers are fewer.
But moving hundreds or thousands of miles away is no easy task when you have no money to move. Somehow, with some luck, ingenuity, and tenacity, you have finally managed to find a way. You have no job offer in your new town, but conditions are so bleak at home that you just can't risk staying there. So the three of you move 1500 miles away.
You arrive with no money, no apartment, and don't know anybody. But you're a hard worker, and have talked yourself into a job. It pays what passes for minimum wage in your new home, but it's a fortune compared to what you made before. It's backbreaking work, and you work long hours. But soon you can afford a cramped apartment, and keep your refrigerator stocked with food. What a luxury!
Pretty soon your new baby son is born. You can afford to feed him, your daughter, your wife, and yourself, every day. When you're really lucky, you even have some money left over to send to your brother back home, who is still struggling to make ends meet there. You seem to have climbed the first rung on the American Dream ladder.
Years pass. Your old home becomes a memory; your daily life revolves around new struggles now. Your oldest child is in school, your wife finds part-time work sometimes too, cleaning houses for rich people. You've been laid off several times, your income isn't guaranteed, and the others in your new home don't take kindly to strangers -- and they still think you're one. But it's better than flying bullets and never knowing where your next meal will come from.
Then one day, while you are at work, federal agents show up. You are arrested and taken to jail. Agents show up at home, too, arresting your wife. It turns out that they realized you entered the country illegally from Ecuador those years ago. Meanwhile, your wife wonders what will happen to your son that was playing in a neighbor's yard while she was arrested, or to your daugther that was at school.
After months in jail, with little contact with each other, and poor medical care, the government decides to deport you to Mexico. Why Mexico? Well, it's cheaper, and there's no documentation showing where you came from. Apparently you "look" Mexican, and they don't believe your story.
After months in jail with no income, you are once again bankrupt. A government bus takes you to Mexico and drops you down someplace there, with your wife and your oldest child. Your younger child was born in the United States, and so is an American citizen and can't be deported. But the government isn't going to give him a free ride on a prison bus (and Mexico wouldn't take him anyway, since everyone knows he's American). You have no idea where he is. You have no idea how you're going to find food in Mexico, no idea how to find your son, no idea where to find refuge from the ever more prevalent drug dealers. Meanwhile, the Americans think you're scum because you wanted to protect your family, and it's going to be much more difficult to get back in to try to reunite your family.
This story is based on true events.
It's truly easy to demonize illegal immigrants, isn't it? Easy to round them up by the thousands, easy to build a bigger fence, easy to lock them away.
Sometimes it seems like this nation built on freedom, supposedly on Christian values, has lost sight of compassion for the lowly. In this country, we would throw in jail parents that didn't do everything humanly possible to find food for their children. We also throw in jail parents that grew up in other countries that are just doing the same.
How sad that we have people going on TV, suggesting we round up millions of Americans that happened to come here illegally, breaking up millions of families, creating an immense foster child problem, a human tragedy on a mass scale. How incredible that some of these people on TV wear the title "senator" or "candidate for president". How stupid do they think we are, suggesting that a poor South American family would somehow be able to navigate the arcane American immigration system and wait the 15 years to get here legally, if they manage to come up with all the necessary money somehow?
Politicians have been pushing our buttons for too long. We aren't a nation of selfish hoarders; we came together through tough times, survived the Depression, put in place the Berlin Airlift that saved countless lives in West Berlin. But the thought of someone with darkish skin coming to this country and building highways is enough to send some people looking for a rifle.
I hope that we will someday do better.
Mark Shuttleworth has written an interesting post about Ubuntu release dates [1]. He claims that free software distributions are better able to meet release dates than proprietary OSs because they are not doing upstream development. The evidence that free software distributions generally do a reasonable job of meeting release dates (and Ubuntu does an excellent job) is clear.
But the really interesting part of his post is where he offers to have Ubuntu collaborate with other distributions on release dates. He states that if two out of Red Hat (presumably Enterprise Linux), Novell (presumably SLES), and Debian will commit to the same release date (within one month) and (possibly more importantly) to having the same versions of major components then he will make Ubuntu do the same.
This is a very significant statement. From my experience working in the Debian project and when employed by Red Hat I know that decisions about which versions of major components to include are not taken lightly, and therefore if the plan is to include a new release of a major software project and that project misses a release date then it forces a difficult decision about whether to use an older version or delay the release. For Ubuntu to not merely collaborate with other distributions but to instead follow the consensus of two different distributions would be a massive compromise. But I agree with Mark that the benefits to the users are clear.
I believe that the Debian project should align it’s release cycles with Red Hat Enterprise Linux. I believe that RHEL is being released in a very sensible manner and that the differences of opinion between Debian and Red Hat people about how to manage such things are small. Note that it would not be impossible to have some variations of version numbers of components but still stick mostly to the same versions.
If Debian, Ubuntu, and RHEL released at about the same time with the same versions of the kernel, GCC, and major applications and libraries then it would make it much easier for users who want to port software between distributions and run multiple distributions on the same network or the same hardware.
The
Debian Social Contract [2] states that “Our priorities are our users and free software“. I believe that by using common versions across distributions we would help end-users in configuring software and maintaining networks of Linux systems running different distributions, and also help free software developers by reducing the difficulty in debugging problems.
It seems to me that the best way of achieving the goal that Mark advocates (in the short term at least) is for Debian to follow Red Hat’s release cycle. I think that after getting one release with common versions out there we could then discuss how to organise cooperation between distributions.
I also believe that a longer support cycle would be a good thing for Debian. I’m prepared to do the necessary work for the packages that I maintain and would also be prepared to do some of the work in other areas that is needed (EG back-porting security fixes).
Share This

We've had two serious bugs on the NSLU2 recently that both caused the
system not too boot anymore. The
first one was related to
initramfs-tools. Kevin Price reported that after upgrading to
initramfs-tools 0.92 the system would hang during boot waiting for the root
filesystem. When I booted my NSLU2 and looked at the output, I noticed
that no root device was set. When I mentioned this to maks, the maintainer
of the initramfs-tools package, he immediately knew what was wrong and
uploaded a fix. On the NSLU2, the boot loader doesn't pass a root device
to the kernel so we set one in the initramfs itself. The code that loads
this config variable is not used by many devices so nobody noticed that
this got broken in 0.92 until the package moved to testing.
The
second problem, reported
on Saturday by Paul Collins and diagnosed today with some help from Kevin
Price is also related to the strange way the NSLU2 boots. The NSLU2 has 6
MB available for the ramdisk but due to a
bug in APEX (the second stage loader
used on the NSLU2 by Debian) only 4 MB are actually used. When you write a
ramdisk that is larger than 4 MB but smaller than 6 MB, flash-kernel will
happily write the full image, but APEX will only tell the kernel about the
first 4 MB. As it turns out, everything works fine on arm with 2.6.25, but
on armel some additional SCSI modules are enabled that result in the
ramdisk becoming too large. The short term solution is to disable these
modules, but really APEX should finally be fixed (patches have been
available for quite a while thanks to Gordon Farquharson). Fortunately
2.6.25 hasn't moved to testing yet and this problem only occurs on armel,
so few people were impacted.
The nice thing about the NSLU2 is that you can write a new flash image via
the network, so you can flash a good image in case your machine no longer
boots. Nevertheless, we have to make sure such serious bugs don't occur in
the future or that they are at least caught very early. Special thanks go
to testers like Kevin Price.

Yesterday I completed the first successful installation of Debian on a
QNAP TS-209 using a custom debian-installer image with 2.6.25 from
unstable. I made the installer image for QNAP TS-109 and TS-209
available as an
experimental
developer release and today I also uploaded images for the TS-409.
More on my plans to support the QNAP TS-109/TS-209 and TS-409 in the
upcoming release of Debian (starting with beta3 of debian-installer)
soon.
My slug was temporarily bricked for a few days due to a mistake on my part. Fortunately, numerous write-ups by Martin Michlmayr and others helped me. Here I am adding one more source of the same information!The following assumes that you have a
backup.img which contains bootable Debian firmware for the slug but has the
wrong kernel and initrd. One can probably use the Debian firmware that is the Debian Installer image otherwise ---
but I have not tested this!Moreover, I also assume that you have the full system installed on a USB disk which you have mounted on your regular desktop at
/mnt.
Copy the kernel and initrdWe just create an new "recovery" directory and copy boot/ over from the mounted USB disk.mkdir recover; cd recover
cp -a /mnt/boot .
At this point you can un-mount the USB disk and keep it ready to connect it to the slug.

27km...that's what Google Maps says, while my podometer says 28km (2/3 of
a marathon). Anyway, I'm happy again as I pushed my limits slightly
and ran that distance on Saturday. The former record was 24km. More happily, I could run another
20km today, 2 days later, and finished it very easily (the 27km run was
much harder at the end but also had much steeper slopes).
Long week-ends are good, indeed, to improve my running skills.
For Dirk: the pace is currently 9:36 after converting things to your
odd units...:)...so, I'm still far far away from your performances..:)

Last weekend, Sarah and I went to the
Maker
Faire again. I love how I don't even have to negotiate with Sarah to go,
she loves it just for watching the Combot Cup, where the combat robots
destroy each other spectacularly.
Ever since Jon Oxer gave his
Hardware/Software
Hacking: Joining the Real and the Virtualtalk at Google about, I got
vaguely interested in electronics again. The
Arduino board seemed like a pretty cool
thing to hack on, and since it seemed like I'd need to get vaguely
electronically savvy to do a thing or two for the dream home we want to
build one day (which coincidentally seems to quite similar to what Jon's
currently building), I figured I'd
have to get my act together and learn the difference between an Ohm and an
Amp.
The last time I dabbled in electronics was as a kit, with the ubiquitous
Dick
Smith Funway 1 kit.
So the Maker Store at the Faire had copies of
Making Things Talk,
bundled with an Arduino starter kit, so I lashed out on one of them, a
BoArduino,
and a little breadboard-based electronics kit.
I've been flicking through the Making Things Talk book, and reading the
projects. The Arduino board seems really cool. The Processing/Wiring
language seems fairly straightforward.
I'd decided that my "project" would be a water monitor for the cat water
bowl. We have a dish with a little tank on it, not unlike the office water
cooler, and it usually lasts about 7 days. We typically refill it on a
Saturday as part of the weekend chores. Sometimes our schedule gets a bit
disrupted (we go away, we have visitors) and we forget. Or worse, we're
away, have a house sitter, and they completely forget to check it. It's only
happened a couple of times, but we really don't want to neglect the cats.
So I thought a water sensor would be a perfect project. One of the projects
in the book involves a Bluetooth modem, so I figured that as the MythTV box
has a Bluetooth adapter, and would be within range of the water bowl, I
could use it to monitor the water sensor (as well as stick a blinking light
on it). The end goal is to have the house call us (via Asterisk and eSpeak)
if the water bowl gets empty.
So I ordered a Bluetooth modem, the
exact
part number in the book, and it arrived on the weekend, and I got around
to playing with it today.
To cut a long story short, I was messing around with it attached to a USB to
TTL serial cable, and I was trying to get it to talk to my laptop, and
instead of swapping the TX and RX lines, I swapped the V
CC and
ground lines, and well, I let the magic blue smoke out.
What I discovered, after the fact, was that the
Bluetooth chipset had been
changed since the book had been written, and so the commands for the
chipset were different. So most of my second-guessing whether I had the TX
and RX round right way was because of that.
So I'm miffed with myself for frying the thing within hours of getting my
hands on it, and I'm miffed with the supplier for maintaining the same
product ID for a product that has changed componentry.
Chalk that one up to experience...
To add insult to injury, Spark Fun is out of stock of the (cheaper) item
that it turns out I want instead. I doubt I'll get my hands on it until
after we get back from Zurich, so it'll be another three weeks before I can
begin to make any progress. I guess I can try to prototype the water-sensing
part with the board connected to my laptop with the USB cable in the
meantime...

We've been blessed with really wonderful neighbours in our apartment
building. We know four out of the seven households in our building really
well.
A while ago, we thought it'd be cool to rent a house and have a weekend away
together, so we booked it for this weekend, rented a
house in Rio Monte
on the Russian River, and hung out together for the weekend.
Eight adults, 3 kids, and we're all still talking to each other afterwards.
Trying to coordinate outings with 2 small kids nap schedules was tricky, so
we only made it to the
Korbel
winery, but we picked up some cheap champagne (an I thought you could
only call it champagne if it came from Champagne, France).
Sadly, because Gavin and Christina have a second son on the way, they've
bought a house up in greater Sacramento, and are moving out next weekend.
We'll miss having them and Aiden as next-door neighbours.
We've decided that we should make this an annual event, so there'll be an
annual "building 4" reunion.
Photos from the weekend are
here.

Really, really windy day. There was a tornado watch until 3, which I didn't
think much about until I was up on a ridge overlooping Slagle Hollow at
3:30, in one of the strongest winds I've experienced, blowing small branches
past me. And lost. That could have not turned out well, but I made the
right guesses at the turns, and it gave me the incentive to power-hike for
an hour to get down off the hill and back to Roosterfront.
Before that I found a beautiful long hollow full of mossy deadfalls and
trilliums, atonishingly close to the well-traveled trails.

If you look at the
po-debconf stats
pages, you'll see that, as of today, the French translators translated 9693 strings out of 9688...:-)
We are so clever!
This is actually an annoyance on the scripts that generate these pages. Sometimes, in packages, the debian/po/*.po files contain *more* strings than the debian/po/templates.pot files.
This happens when maintainers do not run "debconf-updatepo" in the
clean target of their debian/rules files. People, there is a lintian
warning for this...:)
We will try to correct this (actually, more Nicolas Fran ois than me, indeed) but that will make my stats less easy to do...
So, "sadly", we are indeed only about 99%...
That said, the NMU campaign is still going on. Portuguese is now ahead of Czech (ranked 3rd). Russian passed Swedish and is very close to Spanish for rank 7. And, among the most actives, Finnish and Basque are still climbing up quickly.