From: "Aman" <aman@mistralsoftware.com>
To: "linuxppc embedded" <linuxppc-embedded@lists.linuxppc.org>
Subject: PPC kernel tree download error
Date: Wed, 19 Mar 2003 23:43:18 +0530 [thread overview]
Message-ID: <001101c2ee43$3831ea10$370da8c0@aman> (raw)
Hi All
This the first time , I am downloading the linuxppc_2_4_devel tree from the
following site using Bitkeeper for PPC IBM 440 image
http://penguinppc.org/dev/kernel.shtml. I used the following command to
download the linuxppc_2_4 tree
bk clone -d http://ppc.bkbits.net/linux_2_4_devel
After some time I get the following error
==========================================================================
Sfio has detected a name conflict between
"include/linux/netfilter_ipv4/SCCS/s.i
pt_dscp.h" and "include/linux/netfilter_ipv4/SCCS/s.ipt_DSCP.h";
This usually happens when you transfer file from a case-sensitive file
system (e.g. Unix) to a case insensitive file system (e.g FAT, NTFS)
Please rename one of the files and retry (see also "bk helptool mv")
Note: You must do the rename in the sending repository.
==========================================================================
write on fd gzip_in gunzip2fd: Broken pipe
ERROR: process 1064 is exiting and it has left the repository at
. write locked!! This is the result of a process that has been
killed prematurely or is a bug.
socket2pipe: shutting down write socket
Administrator@WIN2KHOSTB ~
$ socket2pipe: reader error 2
Can anybody suggest , how to overcome this error
Thanking you in advance
Regards
Aman
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
reply other threads:[~2003-03-19 18:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='001101c2ee43$3831ea10$370da8c0@aman' \
--to=aman@mistralsoftware.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).