All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Mark Gollahon" <golly@stellarwerx.com>
To: openembedded-devel@lists.openembedded.org
Subject: Building Distros Directly To HD (Was: Re: OE Booth during fosdem)
Date: Thu, 15 Feb 2007 13:46:09 -0500 (EST)	[thread overview]
Message-ID: <1171565169.18829@gatekeeper.stellarwerx.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 3084 bytes --]

Jim Thompson wrote ..
> 
> On Feb 14, 2007, at 1:17 PM, gerwin van der kruis wrote:
> 
> > Op woensdag 14-02-2007 om 12:53 uur [tijdzone -1000], schreef Jim
> > Thompson:
> >
> >> And I'm willing to throw cash, hardware and time at this.
> >>
> >> Yes, we sell WRAP boards, but I'm not looking to get a bunch-o-free
> >> development out of the process.  (We sell a Gateworks ixp42x board
> >> too, just to be perfectly honest.)
> >>
> >> Years ago, I ran (and owned) 'musenki' (google for it or look here:
> >> http://he-colo.netgate.com/~jim/Musenki/.  We had build a  set of
> >> Motorola 8245/8241 boards, and I'd made linux run on them.  I
> >> remember spending a horrific amount of time with a (very) early
> >> version of "buildroot".  OE is so much more sophisticated that I'm a
> >> bit taken aback.
> >>
> >> The OE learning curve is still quite steep, but I think it would be
> >> less steep with a) a bit more documentation and b) an EZ way to start
> >> creating "little distros" that
> >> run on PCs using it.
> >
> > I remember we had this discussion before , the problem is the
> > bootloader, for example grub requires some extra handlings to get
> > installed probarly.
> 
> There appears to be a decent start on "here are the set of steps"  
> here: http://kbarr.net/bochs
> 
> (I've only recently discovered this.)

I've done this "a million times" when I was building Gentoo for WRAPs and Routerboards.  Its not hard to throw files onto a HD or CF, chroot into the "image", and push grub to install itself.  The three things needed were:

(1) x86-based PC that had a Pentium or better processor,
(2) IDE connection for the target media (i.e. CF-to-IDE adapter board for CF cards to be recognized as IDE HDs in the afore-mentioned PC), and
(3) the Linux<->grub drive mapping (usually very easy to figure out, but there are situations...).

Trying to do the grub install via a USB reader/external HD was touchy, but I did manage to figure out how to DD grub's stage 1 and 1.5 and make it work.  However, the CF-to-IDE adapter was much more reliable (but had the down-side of rebooting to change the CF card).

I'll see if I can dig up the instructions and post them.

> > I think if you write a script which automate the installation of for
> > example grub and than copies automatically the files over to cf you 
> > are
> > finished , I did it once long time ago for an embedded voip pabx.
> 
> I once made 'lilo' work with a buildroot-based system.  The makefile  
> is attached.
> 
> I never could get 'grub' to do the same thing, though I prefer grub  
> to lilo.

The scripts I had did all of the work except for the grub part.  Shouldn't be too difficult to resurrect the DD instructions for grub, though.

> > As Koen said I am working on x86 projects like wifi-radio (with a
> > mini-itx board and some small additions) a set top box and a thin
> > client.So we are working on it !!
> 
> Is the wifi-radio tree available anywhere?

Yea, I'd like to see that, too.

Regards,
-Mark Gollahon

             reply	other threads:[~2007-02-15 18:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-15 18:46 Mark Gollahon [this message]
2007-02-16  4:25 ` Building Distros Directly To HD (Was: Re: OE Booth during fosdem) Roderick Taylor
2007-02-16  7:35   ` Marcin Juszkiewicz

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=1171565169.18829@gatekeeper.stellarwerx.com \
    --to=golly@stellarwerx.com \
    --cc=openembedded-devel@lists.openembedded.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.