From: Jack Mitchell <ml@communistcode.co.uk>
To: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Does my build disk's filesystem make a difference?
Date: Mon, 09 Jan 2012 09:15:56 +0000 [thread overview]
Message-ID: <4F0AB04C.2060304@communistcode.co.uk> (raw)
In-Reply-To: <CADzUK1LC=XDuiC_kf_ScaZrb8A9VPq88OqxA0w1aVoW89F6amw@mail.gmail.com>
On 07/01/12 15:16, autif khan wrote:
> You are better off with one of the dual boot OSes in a virtual machine
> that a dual boot situation where you are trying to write to NTFS from
> linux or trying to work with ext2fs tools from windows.
>
> I do not even know if you can create equivalent of symlinks (used
> extensively in yocto) on an NTFS
>
> In theory, it might work, but NTFS was not built for linux, likewise,
> ext4 was not meant to be used for windows. It is a bad idea.
>
> You know - unless this happens to be your master's research thesis :-)
>
> On Fri, Jan 6, 2012 at 6:53 PM, Jeff Osier-Mixon<jefro@jefro.net> 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.
>>
>> --
>> Jeff Osier-Mixon http://jefro.net/blog
>> Yocto Project Community Manager @Intel http://yoctoproject.org
>>
>>
>> _______________________________________________
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
>>
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
I'm no expert in this either but I am unsure how NTFS handles file
permissions, something else that could horribly break!
If I were you I would do as suggested earlier and run Win7 in a virtual
machine then use a shared directory/network shares system.
Otherwise, you could format as ext3 and use the 3rd party drivers
available to Windows for reading. Again though I don't know how
permissions are handled or anything like that so it may be ok for
browsing but I wouldn't recommend major changes through it.
Jack.
prev parent reply other threads:[~2012-01-09 9:16 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
2012-01-07 1:50 ` Darren Hart
2012-01-07 15:16 ` autif khan
2012-01-09 9:15 ` Jack Mitchell [this message]
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=4F0AB04C.2060304@communistcode.co.uk \
--to=ml@communistcode.co.uk \
--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.