Return-Path: 
 <hdfs-dev-return-396-apmail-hadoop-hdfs-dev-archive=hadoop.apache.org@hadoop.apache.org>
Delivered-To: apmail-hadoop-hdfs-dev-archive@minotaur.apache.org
Received: (qmail 52611 invoked from network); 12 Oct 2009 15:34:28 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3)
  by minotaur.apache.org with SMTP; 12 Oct 2009 15:34:28 -0000
Received: (qmail 26763 invoked by uid 500); 12 Oct 2009 15:34:28 -0000
Delivered-To: apmail-hadoop-hdfs-dev-archive@hadoop.apache.org
Received: (qmail 26716 invoked by uid 500); 12 Oct 2009 15:34:28 -0000
Mailing-List: contact hdfs-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:hdfs-dev-help@hadoop.apache.org>
List-Unsubscribe: <mailto:hdfs-dev-unsubscribe@hadoop.apache.org>
List-Post: <mailto:hdfs-dev@hadoop.apache.org>
List-Id: <hdfs-dev.hadoop.apache.org>
Reply-To: hdfs-dev@hadoop.apache.org
Delivered-To: mailing list hdfs-dev@hadoop.apache.org
Received: (qmail 26706 invoked by uid 99); 12 Oct 2009 15:34:27 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 12 Oct 2009 15:34:27 +0000
X-ASF-Spam-Status: No, hits=-4.0 required=10.0
	tests=RCVD_IN_DNSWL_MED,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: domain of awittenauer@linkedin.com
 designates 69.28.149.25 as permitted sender)
Received: from [69.28.149.25] (HELO esv4-mav03.corp.linkedin.com)
 (69.28.149.25)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 12 Oct 2009 15:34:16 +0000
DomainKey-Signature: s=prod; d=linkedin.com; c=nofws; q=dns;
  h=X-IronPort-AV:Received:User-Agent:Date:Subject:From:To:
   Message-ID:Thread-Topic:Thread-Index:In-Reply-To:
   Mime-version:Content-type:Content-transfer-encoding;
  b=OH1Hvp5HL1yCvOAMhW6aRADnXRBhWHYg7TeLOAXXLv1OYi2721BFxZw6
   WrQ42vIexInaaBC8TyzUX1VR6JLLCRlIlaBk2ItI7q464gB04t92agGjs
   45M1L6gnN8jz2za;
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple;
  d=linkedin.com; i=awittenauer@linkedin.com; q=dns/txt;
  s=proddkim; t=1255361656; x=1286897656;
  h=from:sender:reply-to:subject:date:message-id:to:cc:
   mime-version:content-transfer-encoding:content-id:
   content-description:resent-date:resent-from:resent-sender:
   resent-to:resent-cc:resent-message-id:in-reply-to:
   references:list-id:list-help:list-unsubscribe:
   list-subscribe:list-post:list-owner:list-archive;
  z=From:=20Allen=20Wittenauer=20<awittenauer@linkedin.com>
   |Subject:=20Re:=20HDFS=20Client=20under=20Windows|Date:
   =20Mon,=2012=20Oct=202009=2008:33:57=20-0700|Message-ID:
   =20<C6F89A75.C80%awittenauer@linkedin.com>|To:=20<hdfs-de
   v@hadoop.apache.org>|Mime-version:=201.0
   |Content-transfer-encoding:=207bit|In-Reply-To:=20<4AD24D
   77.9030909@byte23.de>;
  bh=jgku9hzj4++wRyey+32fuK7+pKKcH1ULn8/Dn5GEAS8=;
  b=vYyHL/Ob+UXOWji5jTKbW9Ok2H503vks+hsZn4ouUjkf42JPpD8lryJr
   DY+e+mQVlhjUtq5jZSgjufBoEKzW994SITi51kJqGTlLbt1b+LVQUSdpD
   TDua2C1AupdRM7Q;
X-IronPort-AV: E=Sophos;i="4.44,546,1249282800";
   d="scan'208";a="8985298"
Received: from 172.18.36.81 ([172.18.36.81]) by CORP-MAIL.linkedin.biz
 ([172.18.46.135]) via Exchange Front-End Server mail-access.linkedin.biz
 ([172.18.46.133]) with Microsoft Exchange Server HTTP-DAV ;
 Mon, 12 Oct 2009 15:33:55 +0000
User-Agent: Microsoft-Entourage/12.10.0.080409
Date: Mon, 12 Oct 2009 08:33:57 -0700
Subject: Re: HDFS Client under Windows
From: Allen Wittenauer <awittenauer@linkedin.com>
To: <hdfs-dev@hadoop.apache.org>
Message-ID: <C6F89A75.C80%awittenauer@linkedin.com>
Thread-Topic: HDFS Client under Windows
Thread-Index: AcpLUWmfO+1t9xj91kyqECRdbCjG8A==
In-Reply-To: <4AD24D77.9030909@byte23.de>
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-Virus-Checked: Checked by ClamAV on apache.org




On 10/11/09 2:26 PM, "Tobias N. Sasse" <tobi@byte23.de> wrote:
> I am planning to integrate the HDFS libraries into a program, which runs
> on a variety of platforms.

Be aware that HDFS (or MR for that matter) is not wire compatible with
itself across versions.