All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Paul D. DeRocco" <pderocco@ix.netcom.com>
To: "'Martin Jansa'" <martin.jansa@gmail.com>
Cc: yocto@yoctoproject.org
Subject: Re: Samba server?
Date: Thu, 7 Mar 2013 10:22:54 -0800	[thread overview]
Message-ID: <96E98E10F7094D32B371FD84AFF0FFFC@PAULD> (raw)
In-Reply-To: <20130307104051.GH32228@jama.dyndns-home.com>

> From: Martin Jansa
> 
> Are you talking about openembedded as openembedded-classic or
> meta-openembedded?
> 
> Use samba from meta-openembedded.

That's what I tried first. It's not a layer, but a collection of layers, and
the layer that contains samba is called meta-oe. So I tried to include
meta-openembedded/meta-oe, and it barfed due to the absence of
fontcache.bbclass. But fontcache.bbclass is nowhere to be found in
meta-openembedded; it's contained in openembedded-core/meta. So I included
openembedded-core/meta, and got some other error message containing about a
dozen lines of Python script that had raised an exception. I tried including
openembedded instead/too, and got other error messages.

To someone who understands the shape of the universe, this is probably easy
to figure out. I might feel the trunk, or the tail, but I don't know it's an
elephant yet.

Since samba is a fairly common, standard module, I was hoping someone here
had already done this, and could tell me what buttons to push. I've read the
scant docs on bitbake, and pretty much the entire Yocto docs and
Openembedded docs, and my head is spinning. I don't mind learning some
stuff, but if I have to spend six months becoming an expert on something
just to get it to work, then this is an economically unviable project for
me.

Or maybe I should just build the system without samba, run it, manually
install samba just like any other user, and then use dd to save the modified
image for production use. Does that sound like a good idea?

-- 

Ciao,               Paul D. DeRocco
Paul                mailto:pderocco@ix.netcom.com 



  reply	other threads:[~2013-03-07 18:23 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-06 23:31 Samba server? Paul D. DeRocco
2013-03-07 10:40 ` Martin Jansa
2013-03-07 18:22   ` Paul D. DeRocco [this message]
2013-03-07 18:29     ` Martin Jansa
2013-03-07 22:29       ` Paul D. DeRocco
2013-03-07 22:42         ` Martin Jansa
2013-03-27  8:09           ` Paul D. DeRocco
2013-03-27  9:03             ` Anders Darander
2013-03-27 22:12               ` Paul D. DeRocco
2013-03-28  2:10                 ` ChenQi
2013-03-28  3:10                   ` Paul D. DeRocco
2013-03-28  3:24                     ` ChenQi
2013-03-28  5:55                     ` Anders Darander
2013-03-28  6:05                       ` Paul D. DeRocco
2013-04-01  9:32                     ` Paul Eggleton
2013-04-01 23:42                       ` Paul D. DeRocco
2013-04-02  7:13                         ` Paul Eggleton
2013-03-28 20:33                   ` Trevor Woerner
2013-03-28 21:35                     ` Paul D. DeRocco
2013-03-28 21:44                       ` Trevor Woerner

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=96E98E10F7094D32B371FD84AFF0FFFC@PAULD \
    --to=pderocco@ix.netcom.com \
    --cc=martin.jansa@gmail.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.