From: "David H. Lynch Jr." <dhlii@dlasys.net>
To: linuxppc-embedded <linuxppc-embedded@ozlabs.org>
Subject: Re: ML403 Linux port questions
Date: Sat, 01 Mar 2008 23:19:19 -0500 [thread overview]
Message-ID: <47CA2AC7.50602@dlasys.net> (raw)
In-Reply-To: <fa686aa40802291246v676042davca91e21a08846846@mail.gmail.com>
Grant Likely wrote:
> On Fri, Feb 29, 2008 at 10:24 AM, Phil Hochstetler
> <Phil.Hochstetler@serveron.com> wrote:
>
>> I guess what I am looking for is advise on the lowest risk, easiest to set
>> up environment to setup that will just work. Also advise on which kernel to
>> use. I don't need a detailed tutorial but a high level direct that is
>> known to work. I am thinking of using either the secret lab tree or the
>> Xilinx tree as recommended in Grants wiki page. Should I just forget using
>> XP and install a Linux (x86 processor so I must use cross tools)? If so,
>> what is the recommend distro and what version?
>>
>
> Yes, absolutely. Going down the cygwin path is doable, but it is a
> path of pain. I strongly recommend using a Linux host. (I personally
> use Ubuntu, but you should have good success with any disto. Use what
> you're most comfortable with).
>
> The simplest approach to get running with a Linux box is to install
> either VirtualBox or VMware and create yourself a Linux virtual
> machine. That will get you up and running without having to obtain
> new hardware or risk breaking your XP setup.
>
Mostly I would agree - however, I would suggest something like
colinux rather than
virtualbox or vmware - If you must do development work on a windows
system.
Colinux is fairly trivial to get up and running.
It gives you real linux running as a process under windows.
There is no "virtualization" going on at all.
The only caveat is that all access to host hardware must go through
windows.
This is much less of a big deal than it sounds - if you are talking
about a development environment.
It is also useful because from colinux running under windows you can
have access to your windows filesystem.
This means that you can use REAL linux tool fairly transparently on
windows while still running windows.
I rarely run windows anymore. But when I do I run colinux, and I
write linux shell scripts that run under colinux
to preform tasks I find difficult to do under windows.
--
Dave Lynch DLA Systems
Software Development: Embedded Linux
717.627.3770 dhlii@dlasys.net http://www.dlasys.net
fax: 1.253.369.9244 Cell: 1.717.587.7774
Over 25 years' experience in platforms, languages, and technologies too numerous to list.
"Any intelligent fool can make things bigger and more complex... It takes a touch of genius - and a lot of courage to move in the opposite direction."
Albert Einstein
next prev parent reply other threads:[~2008-03-02 4:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-29 17:24 ML403 Linux port questions Phil Hochstetler
2008-02-29 18:13 ` Darcy Watkins
2008-02-29 20:46 ` Grant Likely
2008-03-02 4:19 ` David H. Lynch Jr. [this message]
2008-02-29 22:11 ` Brian Silverman
2008-03-02 22:58 ` David H. Lynch Jr.
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=47CA2AC7.50602@dlasys.net \
--to=dhlii@dlasys.net \
--cc=linuxppc-embedded@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 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).