From: Joshua Lock <josh@linux.intel.com>
To: yocto@yoctoproject.org
Subject: Re: Does my build disk's filesystem make a difference?
Date: Fri, 06 Jan 2012 16:01:01 -0800 [thread overview]
Message-ID: <4F078B3D.9020408@linux.intel.com> (raw)
In-Reply-To: <CA+YB3raMN09N4wGm-yLa-Kh3p_68vUs4NUqWQt05YEQF0f+4nw@mail.gmail.com>
On 06/01/12 15:53, Jeff Osier-Mixon wrote:
> I am creating a Yocto Project build system. For various reasons, it is a
> dual-boot system, win7 & linux (probably mint 12, haven't decided). I
> have a primary boot disk with both operating systems and a large
> secondary disk to use for build trees etc.
>
> Does the filesystem on the big secondary disk matter? Ideally I would
> like to be able to get to the large data disk from both operating
> systems. That would necessitate NTFS, as win7 does not speak ext4
> reliably, but I don't want to slow my builds down.
Erk! I'm not familiar with NTFS but the thought of this scares me, I
expect you'd be opening yourself up to a world of hurt as:
a) NTFS isn't a first class citizen of Linux.
b) according to wikipedia NTFS has a 255 character filename limit - I
don't know for certain this is a problem but I wouldn't be surprised if
it is.
Will you be storing anything on the disk that isn't build related? If
you anticipate doing a lot of builds you really want to a) use a
filesystem that is Linux native and b) tweak the filesystem to reduce
the number of writes made.
If you just want/need to be able to look at the build system pieces
under WinOS then you could try:
http://www.ext2fsd.com/
Cheers,
Joshua
--
Joshua Lock
Yocto Project "Johannes factotum"
Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-01-07 0:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-06 23:53 Does my build disk's filesystem make a difference? Jeff Osier-Mixon
2012-01-07 0:01 ` Joshua Lock [this message]
2012-01-07 1:50 ` Darren Hart
2012-01-07 15:16 ` autif khan
2012-01-09 9:15 ` Jack Mitchell
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=4F078B3D.9020408@linux.intel.com \
--to=josh@linux.intel.com \
--cc=yocto@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.