From: Chris Plasun <chrispl78@yahoo.com>
To: linuxppc-dev@ozlabs.org
Subject: Re: Accessing NTFS Shares from Freescale MPC8313
Date: Mon, 18 May 2009 11:38:24 -0700 [thread overview]
Message-ID: <4A11AB20.7020207@yahoo.com> (raw)
In-Reply-To: <c384c5ea0905181118g34896cc3s1e77b9ba22c4e164@mail.gmail.com>
Hi Leon,
Leon Woestenberg wrote:
> Hello Chris,
>
> On Mon, May 18, 2009 at 8:06 PM, Chris Plasun <chrispl78@yahoo.com> wrote:
>> Scott Wood wrote:
>>> On Sun, May 17, 2009 at 01:45:30AM -0700, Chris Plasun wrote:
>>>> (I haven't found any answers in the archives)
>>>> How would I access a NTFS shared directory from a Freescale MPC8313?
>>>> Will Samba run on a Freescale MPC8313?
>>> It should (and if it doesn't, file a bug with them).
>>> Userspace is pretty much the same at the source-code and user-interface
>>> level -- the answer to "how do I do X on this PPC board" is generally the
>>> same as the answer to "how do I do X on Linux", other than that you may
>>> need to compile some packages manually if they don't come with whatever
>>> distribution you're using.
>> Thanks Scott.
>>
>> I did some more reading on the board and it appears that it's not as limited
>> as I thought. The "custom" Linux we're running is very limited (so it
>> appears) and I interpreted the board to be so as well.
>>
>
> To build your own fully-open Linux for this board, I can recommend
> both these projects:
>
> LTIB (http://www.bitshrine.org/)
> OpenEmbedded (http://www.openembedded.org/)
>
> We use the latter in an industrial setting with much success,
Thanks Leon. I'll definitely be back to ask for help to get these
distributions running =)
cp
prev parent reply other threads:[~2009-05-18 18:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-17 8:45 Accessing NTFS Shares from Freescale MPC8313 Chris Plasun
2009-05-18 17:10 ` Scott Wood
2009-05-18 18:06 ` Chris Plasun
2009-05-18 18:18 ` Leon Woestenberg
2009-05-18 18:38 ` Chris Plasun [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=4A11AB20.7020207@yahoo.com \
--to=chrispl78@yahoo.com \
--cc=linuxppc-dev@ozlabs.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.