This is the mail archive of the
cygwin-talk
mailing list for the cygwin project.
Re: Fixing the state of C++ in Cygwin
- From: Eric Blake <ebb9 at byu dot net>
- To: cygwin-talk at cygwin dot com
- Date: Mon, 17 Apr 2006 07:12:18 -0600
- Subject: Re: Fixing the state of C++ in Cygwin
- References: <041720060352.4350.444310E500004BAC000010FE22058861720A050E040D0C079D0A@comcast.net>
- Reply-to: The Cygwin-Talk Malingering List <cygwin-talk at cygwin dot com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
According to Eric Blake on 4/16/2006 9:52 PM:
> (and I was just about ready to upload bash-3.1-5 when my hard drive
> crashed yesterday; so when I respin it, I will make sure I catch this
> issue. Fortunately, I did not lose very mush else).
^^^^
s/mush/much/, although that was a rather humorous typo, since I sure felt
like mush. (I think that is also how I would feel were a hippo to be
dropped on me). On Saturday, after a brief power outage, I got a blue
screen of death claiming UNMOUNTABLE_ROOT_VOLUME when trying to boot;
nothing like that to induce sheer panic. Fortunately, the drive itself
was okay, it was just a filesystem crash; and running 'chkdsk /r' after
booting off the Windows CD solved the problem after several agonizing
hours of waiting. Now why can't windows use fsck, or even better, a
journaling file system that is immune to power glitches?
- --
Life is short - so eat dessert first!
Eric Blake ebb9@byu.net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.1 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFEQ5Qy84KuGfSFAYARApTDAJ9VcDOxe2+9ZHWMVJ8NnOxwQrR0AgCglu9x
xIHbYidSQ/Ej3XZOGvySBh4=
=1Dix
-----END PGP SIGNATURE-----