date:20131003

On 13-10-03 8:21 PM, Parker Mackenzie wrote:

Thanks Bruce,

That got me further. I added a comment to the video on YouTube which might help
others which stumble across the presentation.

Now I get the following error
ERROR: Function failed: do_rootfs

Which points me to a log file which indicates the following failed:

Note: adding Smart RPM DB channel

Note: to be installed: packagegroup-core-tools-debug@beagleboard
kernel-dev@beagleboard rpm-postinsts@all packagegroup-core-boot@beagleboard
libstdc++6@armv7a_vfp_neon
Loading cache...
Updating cache... [100%]

Computing transaction...error: Can't install
kernel-dev-3.4.43+git0+1bab5bd090948b4cc4c4ed57c834603a3cf9f235_c994390cfa28339cbc1ec3b56eeec83a5fa75bb7-r4.4@beagleboard:
no package provides /usr/bin/python

Saving cache...

ERROR: Function failed: do_rootfs (see
/home/parker/Projects/beagleboard/yocto/poky-dylan-9.0.2/build/tmp/work/beagleboard-poky-linux-gnueabi/core-image-minimal/1.0-r0/temp/log.do_rootfs.61003
for further information)

However :
[parker@jasper build]$ which python
/usr/bin/python

That would be your build host's python. The kernel module is pulling it
in as a dependency for the target, so it needs to be part of the rootfs
packages.

Check that your have python in your dependencies/image install lists,
which bitbake -e will dump ... among many other
things :)

Which image type are you building ? core-image-minimal ? Try adding this
to your local.conf: IMAGE_INSTALL_append = " python"

Cheers,

Bruce

I have gone through the documentation; however, feel free to point me at a
resource if this is a silly new-guy question. An internet search did bring up
the following nugget; patch 2/3 sounds related, however, I am not sure how to
proceed.
http://comments.gmane.org/gmane.comp.handhelds.openembedded.core/34245

Thanks in advance,
Parker
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Cross Compile Kernel Modules

2013-10-03 Thread Parker Mackenzie

Thanks Bruce,

That got me further. I added a comment to the video on YouTube which might help 
others which stumble across the presentation.

Now I get the following error
ERROR: Function failed: do_rootfs

Which points me to a log file which indicates the following failed:


Note: adding Smart RPM DB channel

Note: to be installed: packagegroup-core-tools-debug@beagleboard 
kernel-dev@beagleboard rpm-postinsts@all packagegroup-core-boot@beagleboard 
libstdc++6@armv7a_vfp_neon
Loading cache...
Updating cache...  [100%]

Computing transaction...error: Can't install 
kernel-dev-3.4.43+git0+1bab5bd090948b4cc4c4ed57c834603a3cf9f235_c994390cfa28339cbc1ec3b56eeec83a5fa75bb7-r4.4@beagleboard:
 no package provides /usr/bin/python

Saving cache...

ERROR: Function failed: do_rootfs (see 
/home/parker/Projects/beagleboard/yocto/poky-dylan-9.0.2/build/tmp/work/beagleboard-poky-linux-gnueabi/core-image-minimal/1.0-r0/temp/log.do_rootfs.61003
 for further information)


However :
[parker@jasper build]$ which python
/usr/bin/python


I have gone through the documentation; however, feel free to point me at a 
resource if this is a silly new-guy question. An internet search did bring up 
the following nugget; patch 2/3 sounds related, however, I am not sure how to 
proceed.
http://comments.gmane.org/gmane.comp.handhelds.openembedded.core/34245

Thanks in advance,
Parker
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Cross Compile Kernel Modules


On 13-10-03 04:08 PM, Parker Mackenzie wrote:

I have been researching a way to build loadable kernel modules outside of Yocto 
for a while. I was excited to find a presentation from the Yocto Developer's 
Day 2013 which implied I code do this by adding the following line to my 
local.conf:
IMAGE_INSTALL_append = " kernel_dev"

However, when I ran bitbake for my beagleboard target I get the following 
error. Any help in understanding what is wrong and how to achieve my goal would 
be most helpful.


Try "kernel-dev"

Bruce



Kind Regards,
Parker Mackenzie



[parker@jasper build]$ bitbake core-image-minimal
Parsing recipes: 100% |#| Time: 00:03:55
Parsing of 814 .bb files complete (0 cached, 814 parsed). 1121 targets, 43 
skipped, 0 masked, 0 errors.

Build Configuration:
BB_VERSION= "1.18.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING   = "Fedora-17"
TARGET_SYS= "arm-poky-linux-gnueabi"
MACHINE   = "beagleboard"
DISTRO= "poky"
DISTRO_VERSION= "1.4.2"
TUNE_FEATURES = "armv7a vfp neon"
TARGET_FPU= "vfp-neon"
meta
meta-yocto
meta-yocto-bsp= ":"

NOTE: Resolving any missing task queue dependencies
ERROR: Nothing RPROVIDES 'kernel_dev' (but 
/home/parker/Projects/beagleboard/yocto/poky-dylan-9.0.2/meta/recipes-core/images/core-image-minimal.bb
 RDEPENDS on or otherwise requires it)
NOTE: Runtime target 'kernel_dev' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['kernel_dev']
ERROR: Required build target 'core-image-minimal' has no buildable providers.
Missing or unbuildable dependency chain was: ['core-image-minimal', 
'kernel_dev']

Summary: There were 2 ERROR messages shown, returning a non-zero exit code. 

___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto



___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Cross Compile Kernel Modules

2013-10-03 Thread Parker Mackenzie

I have been researching a way to build loadable kernel modules outside of Yocto 
for a while. I was excited to find a presentation from the Yocto Developer's 
Day 2013 which implied I code do this by adding the following line to my 
local.conf:
IMAGE_INSTALL_append = " kernel_dev"

However, when I ran bitbake for my beagleboard target I get the following 
error. Any help in understanding what is wrong and how to achieve my goal would 
be most helpful.

Kind Regards,
Parker Mackenzie



[parker@jasper build]$ bitbake core-image-minimal
Parsing recipes: 100% |#| Time: 00:03:55
Parsing of 814 .bb files complete (0 cached, 814 parsed). 1121 targets, 43 
skipped, 0 masked, 0 errors.

Build Configuration:
BB_VERSION        = "1.18.0"
BUILD_SYS         = "x86_64-linux"
NATIVELSBSTRING   = "Fedora-17"
TARGET_SYS        = "arm-poky-linux-gnueabi"
MACHINE           = "beagleboard"
DISTRO            = "poky"
DISTRO_VERSION    = "1.4.2"
TUNE_FEATURES     = "armv7a vfp neon"
TARGET_FPU        = "vfp-neon"
meta              
meta-yocto        
meta-yocto-bsp    = ":"

NOTE: Resolving any missing task queue dependencies
ERROR: Nothing RPROVIDES 'kernel_dev' (but 
/home/parker/Projects/beagleboard/yocto/poky-dylan-9.0.2/meta/recipes-core/images/core-image-minimal.bb
 RDEPENDS on or otherwise requires it)
NOTE: Runtime target 'kernel_dev' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['kernel_dev']
ERROR: Required build target 'core-image-minimal' has no buildable providers.
Missing or unbuildable dependency chain was: ['core-image-minimal', 
'kernel_dev']

Summary: There were 2 ERROR messages shown, returning a non-zero exit code. 
  
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Fwd: OpenSSH pre login banner

Sorry for the typo mistake ,its sshd_config only
In fact I didn't create this file ,its already existing file which I just
modified.


On Thu, Oct 3, 2013 at 11:40 AM, Bryan Evenson wrote:

> Amit,
>
> ** **
>
> Did you name the file sshd-config or sshd_config?  Because it should be
> sshd_config.
>
> ** **
>
> -Bryan
>
> ** **
>
> *From:* Amit Tomer [mailto:amittome...@gmail.com]
> *Sent:* Thursday, October 03, 2013 2:36 PM
>
> *To:* Bryan Evenson
> *Cc:* yocto@yoctoproject.org
> *Subject:* Re: [yocto] Fwd: OpenSSH pre login banner
>
> ** **
>
> Yes Brayan
>
> ** **
>
> I did the whole process again and  looked into Target filesystem /etc/ssh.
> I can see the banner file with my content is there
>
> /etc/ssh/banner
>
> ** **
>
> Then I see the /etc/ssh/sshd-config with Banner variable to set to
> /etc/ssh/sshd-config
>
> ** **
>
> But still, when I do ssh IP_address, I did not see any Banner message .***
> *
>
> ** **
>
> I restarted the sshd service without any luck
>
> ** **
>
> I have connected to board using putty on serial line /dev/ttyUSB1 .
>
> ** **
>
> What could be the problem here?? 
>
> ** **
>
> On Thu, Oct 3, 2013 at 10:17 AM, Bryan Evenson 
> wrote:
>
> Amit,
>
>  
>
> To me it looks like it did not take your sshd_config file.  Maybe try
> adding it to the SRC_URI in your bbappend?
>
>  
>
> Instead of running the updated package on your target board, you can open
> up the newly created package and verify the file you want is where it
> should be.  Ipks are basically a tar.gz file, so you can open their
> contents with any unpacking tool that can read tar.gz (file-roller is what
> I use).  In the .ipk, open up the etc/ssh/sshd_config file and verify it
> matches the one with your modifications.  If not, then Bitbake isn’t
> grabbing your modified sshd_config.  If you’re using RPM or DEB packages, I
> believe something similar can be done.
>
>  
>
> -Bryan
>
>  
>
> *From:* Amit Tomer [mailto:amittome...@gmail.com]
> *Sent:* Thursday, October 03, 2013 10:41 AM
> *To:* Bryan Evenson; yocto@yoctoproject.org
>
>
> *Subject:* Re: [yocto] Fwd: OpenSSH pre login banner
>
>  
>
> Fine Bryan,Thanks for your Suggestion
>
>  
>
> Not sure should I Share it with you or not but I have seen very weird
> behaviour on my Targer board regarding Openssh Banner.
>
>  
>
> When I login to my Hardware Board(after freash boot) and do ssh
> some_ip_address ,I am able to see Banner message
>
> But in /etc/ssh/sshd_config file 
>
>  
>
> #Banner is set to nothing
>
>  
>
> Then when I do ssh some_ip_address again ,I could not see any banner as it
> is expected behaviour.
>
>  
>
> Hope you would provide any pointer on the same .
>
>  
>
> Thanks 
>
> Amit 
>
>  
>
>  
>
>  
>
>  
>
> On Thu, Oct 3, 2013 at 7:40 PM, Bryan Evenson 
> wrote:
>
> Amit,
>
>  
>
> Good to hear you got your recipe in order.  Best way to learn more about
> the Yocto Project and the Poky distribution is through watching this
> mailing list and the Poky mailing list (p...@yoctoproject.org) to see how
> other people solve their problems they come across.  And, by reading the
> documentation over at http://www.yoctoproject.org/documentation/current/.*
> ***
>
>  
>
> -Bryan 
>
>  
>
> *From:* Amit Tomer [mailto:amittome...@gmail.com]
> *Sent:* Thursday, October 03, 2013 10:03 AM
>
>
> *To:* Bryan Evenson
> *Cc:* yocto@yoctoproject.org
> *Subject:* Re: [yocto] Fwd: OpenSSH pre login banner
>
>  
>
> Thanks again Bryan for your kind response 
>
>  
>
> The reason for having the PRINC ="4" is becaue when I started modifying
> this already existing file
>
> value of PRINC is set 3 ,so for my changes I Incremented it to One.
>
>  
>
> Change
>
> SRC_URI = “file://banner”
>
> To
>
> SRC_URI += “file://banner“
>
>  
>
> I am really feeling bit stupid here ,I just in hurry forgot to put + sign*
> ***
>
> Though I learned a new point 
>
>  
>
> "With your line, you are overriding all the SRC_URI for the entire openssh
> recipe and the openssh recipe will only include the banner file ".
>
>  
>
> Change
>
> FILESEXTRAPATHS_prepend := "${THISDIR}/openssh-6.1p1:"
>
> to
>
> FILESEXTRAPATHS_prepend := "${THISDIR}:"
>
>  
>
> We already had openssh-6.1p1 folder where our sshd_config file is placed
> ,So I guess it won't harm
>
> much if I put FILESEXTRAPATHS_prepend := "${THISDIR}/openssh-6.1p1:" with
> banner file in openssh-6.1p1 folder
>
>  
>
> One more point wanted from your end,what is best way to learn Yocto
>
> How can improve my knowledge in Yocto?
>
>  
>
> Thanks 
>
> Amit.
>
>  
>
>  
>
>  
>
>  
>
> On Thu, Oct 3, 2013 at 7:05 PM, Bryan Evenson 
> wrote:
>
> Amit,
>
>  
>
> First, I suggest you change
>
> P

Re: [yocto] Fwd: OpenSSH pre login banner

2013-10-03 Thread Matthew Weigel


On 10/03/2013 01:36 PM, Amit Tomer wrote:

Yes Brayan

I did the whole process again and  looked into Target filesystem
/etc/ssh. I can see the banner file with my content is there
/etc/ssh/banner

Then I see the /etc/ssh/sshd-config with Banner variable to set to
/etc/ssh/sshd-config


Is the file named "sshd-config" with a hyphen or "sshd_config" with an 
underscore?  That might be the problem.

--
 Matthew Weigel


___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Fwd: OpenSSH pre login banner

Amit,

Did you name the file sshd-config or sshd_config?  Because it should be 
sshd_config.

-Bryan

From: Amit Tomer [mailto:amittome...@gmail.com]
Sent: Thursday, October 03, 2013 2:36 PM
To: Bryan Evenson
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] Fwd: OpenSSH pre login banner

Yes Brayan

I did the whole process again and  looked into Target filesystem /etc/ssh. I 
can see the banner file with my content is there
/etc/ssh/banner

Then I see the /etc/ssh/sshd-config with Banner variable to set to 
/etc/ssh/sshd-config

But still, when I do ssh IP_address, I did not see any Banner message .

I restarted the sshd service without any luck

I have connected to board using putty on serial line /dev/ttyUSB1 .

What could be the problem here??

On Thu, Oct 3, 2013 at 10:17 AM, Bryan Evenson 
mailto:beven...@melinkcorp.com>> wrote:
Amit,

To me it looks like it did not take your sshd_config file.  Maybe try adding it 
to the SRC_URI in your bbappend?

Instead of running the updated package on your target board, you can open up 
the newly created package and verify the file you want is where it should be.  
Ipks are basically a tar.gz file, so you can open their contents with any 
unpacking tool that can read tar.gz (file-roller is what I use).  In the .ipk, 
open up the etc/ssh/sshd_config file and verify it matches the one with your 
modifications.  If not, then Bitbake isn't grabbing your modified sshd_config.  
If you're using RPM or DEB packages, I believe something similar can be done.

-Bryan

From: Amit Tomer [mailto:amittome...@gmail.com]
Sent: Thursday, October 03, 2013 10:41 AM
To: Bryan Evenson; yocto@yoctoproject.org

Subject: Re: [yocto] Fwd: OpenSSH pre login banner

Fine Bryan,Thanks for your Suggestion

Not sure should I Share it with you or not but I have seen very weird behaviour 
on my Targer board regarding Openssh Banner.

When I login to my Hardware Board(after freash boot) and do ssh some_ip_address 
,I am able to see Banner message
But in /etc/ssh/sshd_config file

#Banner is set to nothing

Then when I do ssh some_ip_address again ,I could not see any banner as it is 
expected behaviour.

Hope you would provide any pointer on the same .

Thanks
Amit

On Thu, Oct 3, 2013 at 7:40 PM, Bryan Evenson 
mailto:beven...@melinkcorp.com>> wrote:
Amit,

Good to hear you got your recipe in order.  Best way to learn more about the 
Yocto Project and the Poky distribution is through watching this mailing list 
and the Poky mailing list (p...@yoctoproject.org) 
to see how other people solve their problems they come across.  And, by reading 
the documentation over at http://www.yoctoproject.org/documentation/current/.

-Bryan

From: Amit Tomer [mailto:amittome...@gmail.com]
Sent: Thursday, October 03, 2013 10:03 AM

To: Bryan Evenson
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] Fwd: OpenSSH pre login banner

Thanks again Bryan for your kind response

The reason for having the PRINC ="4" is becaue when I started modifying this 
already existing file
value of PRINC is set 3 ,so for my changes I Incremented it to One.

Change
SRC_URI = "file://banner"
To
SRC_URI += "file://banner"

I am really feeling bit stupid here ,I just in hurry forgot to put + sign
Though I learned a new point

"With your line, you are overriding all the SRC_URI for the entire openssh 
recipe and the openssh recipe will only include the banner file ".

Change
FILESEXTRAPATHS_prepend := "${THISDIR}/openssh-6.1p1:"
to
FILESEXTRAPATHS_prepend := "${THISDIR}:"

We already had openssh-6.1p1 folder where our sshd_config file is placed ,So I 
guess it won't harm
much if I put FILESEXTRAPATHS_prepend := "${THISDIR}/openssh-6.1p1:" with 
banner file in openssh-6.1p1 folder

One more point wanted from your end,what is best way to learn Yocto
How can improve my knowledge in Yocto?

Thanks
Amit.

On Thu, Oct 3, 2013 at 7:05 PM, Bryan Evenson 
mailto:beven...@melinkcorp.com>> wrote:
Amit,

First, I suggest you change
PRINC = "4"
to
PRINC := "${@int(PRINC) + 1}"

This way your bbappend will always increment the PR to one more than the PR 
called out by the main recipe.  So if the openssh recipe would get updated and 
increment the PR, you do not have to change your bbappend.

Change
SRC_URI = "file://banner"
To
SRC_URI += "file://banner"

The += appends your banner file to the SRC_URI for the openssh recipe.  With 
your line, you are overriding all the SRC_URI for the entire openssh recipe and 
the openssh recipe will only include the banner file.  I've taken to the habit 
of writing the SRC_URI as follows:

SRC_URI += " \
file://banner \
"
just to ensure that words aren't joined together when my SRC_URI is appended to 
the existing one.  I don't know if this is strictly necessary, but it's not a 
bad habit.

Change
FILESEXTRAPATHS_prepend := "${THISDIR}/openssh-6.1p1:"
to
FILESEXTR

Re: [yocto] Fwd: OpenSSH pre login banner

Yes Brayan

I did the whole process again and  looked into Target filesystem /etc/ssh.
I can see the banner file with my content is there
/etc/ssh/banner

Then I see the /etc/ssh/sshd-config with Banner variable to set to
/etc/ssh/sshd-config

But still, when I do ssh IP_address, I did not see any Banner message .

I restarted the sshd service without any luck

I have connected to board using putty on serial line /dev/ttyUSB1 .

What could be the problem here??


On Thu, Oct 3, 2013 at 10:17 AM, Bryan Evenson wrote:

> Amit,
>
> ** **
>
> To me it looks like it did not take your sshd_config file.  Maybe try
> adding it to the SRC_URI in your bbappend?
>
> ** **
>
> Instead of running the updated package on your target board, you can open
> up the newly created package and verify the file you want is where it
> should be.  Ipks are basically a tar.gz file, so you can open their
> contents with any unpacking tool that can read tar.gz (file-roller is what
> I use).  In the .ipk, open up the etc/ssh/sshd_config file and verify it
> matches the one with your modifications.  If not, then Bitbake isn’t
> grabbing your modified sshd_config.  If you’re using RPM or DEB packages, I
> believe something similar can be done.
>
> ** **
>
> -Bryan
>
> ** **
>
> *From:* Amit Tomer [mailto:amittome...@gmail.com]
> *Sent:* Thursday, October 03, 2013 10:41 AM
> *To:* Bryan Evenson; yocto@yoctoproject.org
>
> *Subject:* Re: [yocto] Fwd: OpenSSH pre login banner
>
> ** **
>
> Fine Bryan,Thanks for your Suggestion
>
> ** **
>
> Not sure should I Share it with you or not but I have seen very weird
> behaviour on my Targer board regarding Openssh Banner.
>
> ** **
>
> When I login to my Hardware Board(after freash boot) and do ssh
> some_ip_address ,I am able to see Banner message
>
> But in /etc/ssh/sshd_config file 
>
> ** **
>
> #Banner is set to nothing
>
> ** **
>
> Then when I do ssh some_ip_address again ,I could not see any banner as it
> is expected behaviour.
>
> ** **
>
> Hope you would provide any pointer on the same .
>
> ** **
>
> Thanks 
>
> Amit 
>
> ** **
>
> ** **
>
> ** **
>
> ** **
>
> On Thu, Oct 3, 2013 at 7:40 PM, Bryan Evenson 
> wrote:
>
> Amit,
>
>  
>
> Good to hear you got your recipe in order.  Best way to learn more about
> the Yocto Project and the Poky distribution is through watching this
> mailing list and the Poky mailing list (p...@yoctoproject.org) to see how
> other people solve their problems they come across.  And, by reading the
> documentation over at http://www.yoctoproject.org/documentation/current/.*
> ***
>
>  
>
> -Bryan 
>
>  
>
> *From:* Amit Tomer [mailto:amittome...@gmail.com]
> *Sent:* Thursday, October 03, 2013 10:03 AM
>
>
> *To:* Bryan Evenson
> *Cc:* yocto@yoctoproject.org
> *Subject:* Re: [yocto] Fwd: OpenSSH pre login banner
>
>  
>
> Thanks again Bryan for your kind response 
>
>  
>
> The reason for having the PRINC ="4" is becaue when I started modifying
> this already existing file
>
> value of PRINC is set 3 ,so for my changes I Incremented it to One.
>
>  
>
> Change
>
> SRC_URI = “file://banner”
>
> To
>
> SRC_URI += “file://banner“
>
>  
>
> I am really feeling bit stupid here ,I just in hurry forgot to put + sign*
> ***
>
> Though I learned a new point 
>
>  
>
> "With your line, you are overriding all the SRC_URI for the entire openssh
> recipe and the openssh recipe will only include the banner file ".
>
>  
>
> Change
>
> FILESEXTRAPATHS_prepend := "${THISDIR}/openssh-6.1p1:"
>
> to
>
> FILESEXTRAPATHS_prepend := "${THISDIR}:"
>
>  
>
> We already had openssh-6.1p1 folder where our sshd_config file is placed
> ,So I guess it won't harm
>
> much if I put FILESEXTRAPATHS_prepend := "${THISDIR}/openssh-6.1p1:" with
> banner file in openssh-6.1p1 folder
>
>  
>
> One more point wanted from your end,what is best way to learn Yocto
>
> How can improve my knowledge in Yocto?
>
>  
>
> Thanks 
>
> Amit.
>
>  
>
>  
>
>  
>
>  
>
> On Thu, Oct 3, 2013 at 7:05 PM, Bryan Evenson 
> wrote:
>
> Amit,
>
>  
>
> First, I suggest you change
>
> PRINC = “4”
>
> to
>
> PRINC := "${@int(PRINC) + 1}"
>
>  
>
> This way your bbappend will always increment the PR to one more than the
> PR called out by the main recipe.  So if the openssh recipe would get
> updated and increment the PR, you do not have to change your bbappend.
>
>  
>
> Change
>
> SRC_URI = “file://banner”
>
> To
>
> SRC_URI += “file://banner“
>
>  
>
> The += appends your banner file to the SRC_URI for the openssh recipe.
> With your line, you are overriding all the SRC_URI for the entire openssh
> recipe and the openssh recipe will only include the banner file.  I’ve
> taken to the habit of writing the SRC_URI as follows:
>
>  
>
> SRC_

Re: [yocto] Fwd: OpenSSH pre login banner

Amit,

To me it looks like it did not take your sshd_config file.  Maybe try adding it 
to the SRC_URI in your bbappend?

Instead of running the updated package on your target board, you can open up 
the newly created package and verify the file you want is where it should be.  
Ipks are basically a tar.gz file, so you can open their contents with any 
unpacking tool that can read tar.gz (file-roller is what I use).  In the .ipk, 
open up the etc/ssh/sshd_config file and verify it matches the one with your 
modifications.  If not, then Bitbake isn't grabbing your modified sshd_config.  
If you're using RPM or DEB packages, I believe something similar can be done.

-Bryan

From: Amit Tomer [mailto:amittome...@gmail.com]
Sent: Thursday, October 03, 2013 10:41 AM
To: Bryan Evenson; yocto@yoctoproject.org
Subject: Re: [yocto] Fwd: OpenSSH pre login banner

Fine Bryan,Thanks for your Suggestion

Not sure should I Share it with you or not but I have seen very weird behaviour 
on my Targer board regarding Openssh Banner.

When I login to my Hardware Board(after freash boot) and do ssh some_ip_address 
,I am able to see Banner message
But in /etc/ssh/sshd_config file

#Banner is set to nothing

Then when I do ssh some_ip_address again ,I could not see any banner as it is 
expected behaviour.

Hope you would provide any pointer on the same .

Thanks
Amit




On Thu, Oct 3, 2013 at 7:40 PM, Bryan Evenson 
mailto:beven...@melinkcorp.com>> wrote:
Amit,

Good to hear you got your recipe in order.  Best way to learn more about the 
Yocto Project and the Poky distribution is through watching this mailing list 
and the Poky mailing list (p...@yoctoproject.org) 
to see how other people solve their problems they come across.  And, by reading 
the documentation over at http://www.yoctoproject.org/documentation/current/.

-Bryan

From: Amit Tomer [mailto:amittome...@gmail.com]
Sent: Thursday, October 03, 2013 10:03 AM

To: Bryan Evenson
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] Fwd: OpenSSH pre login banner

Thanks again Bryan for your kind response

The reason for having the PRINC ="4" is becaue when I started modifying this 
already existing file
value of PRINC is set 3 ,so for my changes I Incremented it to One.

Change
SRC_URI = "file://banner"
To
SRC_URI += "file://banner"

I am really feeling bit stupid here ,I just in hurry forgot to put + sign
Though I learned a new point

"With your line, you are overriding all the SRC_URI for the entire openssh 
recipe and the openssh recipe will only include the banner file ".

Change
FILESEXTRAPATHS_prepend := "${THISDIR}/openssh-6.1p1:"
to
FILESEXTRAPATHS_prepend := "${THISDIR}:"

We already had openssh-6.1p1 folder where our sshd_config file is placed ,So I 
guess it won't harm
much if I put FILESEXTRAPATHS_prepend := "${THISDIR}/openssh-6.1p1:" with 
banner file in openssh-6.1p1 folder

One more point wanted from your end,what is best way to learn Yocto
How can improve my knowledge in Yocto?

Thanks
Amit.




On Thu, Oct 3, 2013 at 7:05 PM, Bryan Evenson 
mailto:beven...@melinkcorp.com>> wrote:
Amit,

First, I suggest you change
PRINC = "4"
to
PRINC := "${@int(PRINC) + 1}"

This way your bbappend will always increment the PR to one more than the PR 
called out by the main recipe.  So if the openssh recipe would get updated and 
increment the PR, you do not have to change your bbappend.

Change
SRC_URI = "file://banner"
To
SRC_URI += "file://banner"

The += appends your banner file to the SRC_URI for the openssh recipe.  With 
your line, you are overriding all the SRC_URI for the entire openssh recipe and 
the openssh recipe will only include the banner file.  I've taken to the habit 
of writing the SRC_URI as follows:

SRC_URI += " \
file://banner \
"
just to ensure that words aren't joined together when my SRC_URI is appended to 
the existing one.  I don't know if this is strictly necessary, but it's not a 
bad habit.

Change
FILESEXTRAPATHS_prepend := "${THISDIR}/openssh-6.1p1:"
to
FILESEXTRAPATHS_prepend := "${THISDIR}:"

so Bitbake can find your banner file and sshd_config that you have in the same 
directory as the bbappend.

I can't remember if you get a warning if Bitbake can't find the license file at 
all or if it fails on each attempt through the filepath.  Since your new path 
is first, it won't find LICENCE in your layer since you didn't copy it.  Once 
way to quiet this warning would be to copy the license file to your directory.

-Bryan

From: Amit Tomer [mailto:amittome...@gmail.com]
Sent: Thursday, October 03, 2013 8:23 AM
To: Bryan Evenson
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] Fwd: OpenSSH pre login banner

Hi Brayan

Thanks for your help

The way I modify .bbapend file is below

PRINC = "4"
SRC_URI = "file://banner"
FILESEXTRAPATHS_prepend := "${THISDIR}/openssh-6.1p1:"
do_install_append() {

In

Re: [yocto] Install Kernel Modules in rootfs

Bruce, I don't know if i did the correct thing but works.

I found in my tmp some thing about kernel 3.8 fslc and I deleted it.



/tmp$ find . -name "*3.8*" | grep fslc
./stamps/imx28evk-poky-linux-gnueabi/linux-fslc/3.8+gitAUTOINC+72053409242244eaa59497e665945ddeea69c397-r5.do_cleansstate.sigdata.fff4fea9e1722790f7eb22d5d464b82a
./stamps/imx28evk-poky-linux-gnueabi/linux-fslc/3.8+gitAUTOINC+72053409242244eaa59497e665945ddeea69c397-r5.do_cleansstate.fff4fea9e1722790f7eb22d5d464b82a
./work/imx28evk-poky-linux-gnueabi/linux-fslc/3.8+gitAUTOINC+72053409242244eaa59497e665945ddeea69c397-r5
./work/imx28evk-poky-linux-gnueabi/core-image-minimal/1.0-r0/rootfs/lib/modules/3.8.13-fslc+g7205340
./work/imx28evk-poky-linux-gnueabi/core-image-minimal/1.0-r0/rootfs/boot/uImage-3.8.13-fslc+g7205340
./work/imx28evk-poky-linux-gnueabi/core-image-minimal/1.0-r0/rootfs/etc/rpm-postinsts/kernel-image-3.8.13-fslc+g7205340
./buildstats/virtual/kernel-imx28evk/201310011528/linux-fslc-3.8+gitAUTOINC+72053409242244eaa59497e665945ddeea69c397-r5


After that I returned my prefered kernel version for 3.8, and did a bitbake
cleanall virtual/kernel.

And change again my kernel version for default 2.6.35 and works perfect.

Thanks For all help, did you help me a lot!



On Thu, Oct 3, 2013 at 11:22 AM, Bruce Ashfield <
bruce.ashfi...@windriver.com> wrote:

> On 13-10-03 10:09 AM, Raul Rosetto Munoz wrote:
>
>> Look all the time the modules of kernel 3.8 come.
>>
>> My /lib/modules is like this:
>>
>
> That's where ? In your booted target ? What BSP are you using, how did
> you install the image ?
>
> Answering that question, will likely get you your answer. If you previously
> generated a rootfs and installed it. You'd need to do the same thing
> and do it with a clean install with the new kernel to remove all
> remnants of the old package.
>
> (That's assuming you aren't using package management on the target,
> or package feeds. I don't, so manually look after this sort of thing).
>
> Cheers,
>
> Bruce
>
>
>> /lib/modules$ ll
>> total 16
>> drwxr-xr-x 4 raul raul 4096 Oct  3 10:09 ./
>> drwxr-xr-x 7 raul raul 4096 Oct  3 10:09 ../
>> drwxr-xr-x 2 raul raul 4096 Oct  3 10:09 2.6.35.3-1.1.0+yocto+g914558e/
>> drwxr-xr-x 3 raul raul 4096 Oct  1 15:45 3.8.13-fslc+g7205340/
>>
>>
>> /lib/modules$ ll 2.6.35.3-1.1.0+yocto+g914558e/
>> total 36
>> drwxr-xr-x 2 raul raul 4096 Oct  3 10:09 ./
>> drwxr-xr-x 4 raul raul 4096 Oct  3 10:09 ../
>> -rw-r--r-- 1 raul raul   45 Oct  3 10:09 modules.alias
>> -rw-r--r-- 1 raul raul   12 Oct  3 10:09 modules.alias.bin
>> -rw-r--r-- 1 raul raul0 Oct  3 10:09 modules.builtin.bin
>> -rw-r--r-- 1 raul raul0 Oct  3 10:09 modules.dep
>> -rw-r--r-- 1 raul raul   12 Oct  3 10:09 modules.dep.bin
>> -rw-r--r-- 1 raul raul   52 Oct  3 10:09 modules.devname
>> -rw-r--r-- 1 raul raul  131 Oct  3 10:09 modules.softdep
>> -rw-r--r-- 1 raul raul   49 Oct  3 10:09 modules.symbols
>> -rw-r--r-- 1 raul raul   12 Oct  3 10:09 modules.symbols.bin
>>
>> /lib/modules$ ll 3.8.13-fslc+g7205340/
>> total 24
>> drwxr-xr-x 3 raul raul 4096 Oct  1 15:45 ./
>> drwxr-xr-x 4 raul raul 4096 Oct  3 10:09 ../
>> drwxr-xr-x 6 raul raul 4096 Oct  1 15:45 kernel/
>> -rw-r--r-- 1 raul raul 5153 Oct  1 15:45 modules.builtin
>> -rw-r--r-- 1 raul raul  391 Oct  1 15:45 modules.order
>>
>> I have no idea how to remove the remains of the kernel 3.8.
>>
>> I dont want to delete all the /tmp
>>
>> =/
>>
>> Take so much time.
>>
>>
>>
>>
>>
>>
>>
>>
>> On Thu, Oct 3, 2013 at 10:58 AM, Bruce Ashfield
>> > >
>> wrote:
>>
>>
>> On 13-10-03 09 :32 AM, Raul Rosetto Munoz wrote:
>>
>> I think that I found my problem,
>>
>> I tryed to use the kernel 3.8 before in this build system, but I
>> decided
>> to go back to the 2.6.35.3.
>>
>> But now I did bitbake -c cleanall virtual/kernel, I tryed to
>> delete
>> every thing about kernel 3.8 but the modules that are instaled in
>> my
>> /lib/modules/ still be the modules of kernel 3.8.
>>
>> How I clean the modules and force to use no 2.6.35.3 again.
>>
>> Which package or command do that?
>>
>>
>> If you reconstruct your image, the old module package shouldn't be
>> re-used, since you would now have a dependency on the 2.6.35.x kernel.
>>
>> How exactly are they installed in /lib/modules ? Did you do anything
>> in particular ?
>>
>> Bruce
>>
>>
>> Thanks for all Help.
>>
>>
>> On Thu, Oct 3, 2013 at 9:38 AM, Bruce Ashfield
>> > > >
>> 
>> 
>> >>
>> wrote:
>>
>>
>>  On 13-10-03 08  :34
>>
>> AM, Raul Rosetto Munoz wrote:
>>
>>  Hello All,
>>
>>  I'm Trying to install the kernel modules inside my
>> rootfs but I
>>

Re: [yocto] Fwd: OpenSSH pre login banner

Fine Bryan,Thanks for your Suggestion

Not sure should I Share it with you or not but I have seen very weird
behaviour on my Targer board regarding Openssh Banner.

When I login to my Hardware Board(after freash boot) and do ssh
some_ip_address ,I am able to see Banner message
But in /etc/ssh/sshd_config file

#Banner is set to nothing

Then when I do ssh some_ip_address again ,I could not see any banner as it
is expected behaviour.

Hope you would provide any pointer on the same .

Thanks
Amit





On Thu, Oct 3, 2013 at 7:40 PM, Bryan Evenson wrote:

> Amit,
>
> ** **
>
> Good to hear you got your recipe in order.  Best way to learn more about
> the Yocto Project and the Poky distribution is through watching this
> mailing list and the Poky mailing list (p...@yoctoproject.org) to see how
> other people solve their problems they come across.  And, by reading the
> documentation over at http://www.yoctoproject.org/documentation/current/.*
> ***
>
> ** **
>
> -Bryan 
>
> ** **
>
> *From:* Amit Tomer [mailto:amittome...@gmail.com]
> *Sent:* Thursday, October 03, 2013 10:03 AM
>
> *To:* Bryan Evenson
> *Cc:* yocto@yoctoproject.org
> *Subject:* Re: [yocto] Fwd: OpenSSH pre login banner
>
> ** **
>
> Thanks again Bryan for your kind response 
>
> ** **
>
> The reason for having the PRINC ="4" is becaue when I started modifying
> this already existing file
>
> value of PRINC is set 3 ,so for my changes I Incremented it to One.
>
> ** **
>
> Change
>
> SRC_URI = “file://banner”
>
> To
>
> SRC_URI += “file://banner“
>
> ** **
>
> I am really feeling bit stupid here ,I just in hurry forgot to put + sign*
> ***
>
> Though I learned a new point 
>
> ** **
>
> "With your line, you are overriding all the SRC_URI for the entire openssh
> recipe and the openssh recipe will only include the banner file ".
>
> ** **
>
> Change
>
> FILESEXTRAPATHS_prepend := "${THISDIR}/openssh-6.1p1:"
>
> to
>
> FILESEXTRAPATHS_prepend := "${THISDIR}:"
>
>  
>
> We already had openssh-6.1p1 folder where our sshd_config file is placed
> ,So I guess it won't harm
>
> much if I put FILESEXTRAPATHS_prepend := "${THISDIR}/openssh-6.1p1:" with
> banner file in openssh-6.1p1 folder
>
> ** **
>
> One more point wanted from your end,what is best way to learn Yocto
>
> How can improve my knowledge in Yocto?
>
> ** **
>
> Thanks 
>
> Amit.
>
> ** **
>
> ** **
>
> ** **
>
> ** **
>
> On Thu, Oct 3, 2013 at 7:05 PM, Bryan Evenson 
> wrote:
>
> Amit,
>
>  
>
> First, I suggest you change
>
> PRINC = “4”
>
> to
>
> PRINC := "${@int(PRINC) + 1}"
>
>  
>
> This way your bbappend will always increment the PR to one more than the
> PR called out by the main recipe.  So if the openssh recipe would get
> updated and increment the PR, you do not have to change your bbappend.
>
>  
>
> Change
>
> SRC_URI = “file://banner”
>
> To
>
> SRC_URI += “file://banner“
>
>  
>
> The += appends your banner file to the SRC_URI for the openssh recipe.
> With your line, you are overriding all the SRC_URI for the entire openssh
> recipe and the openssh recipe will only include the banner file.  I’ve
> taken to the habit of writing the SRC_URI as follows:
>
>  
>
> SRC_URI += “ \
>
> file://banner \
>
> “
>
> just to ensure that words aren’t joined together when my SRC_URI is
> appended to the existing one.  I don’t know if this is strictly necessary,
> but it’s not a bad habit.
>
>  
>
> Change
>
> FILESEXTRAPATHS_prepend := "${THISDIR}/openssh-6.1p1:"
>
> to
>
> FILESEXTRAPATHS_prepend := "${THISDIR}:"
>
>  
>
> so Bitbake can find your banner file and sshd_config that you have in the
> same directory as the bbappend.
>
>  
>
> I can’t remember if you get a warning if Bitbake can’t find the license
> file at all or if it fails on each attempt through the filepath.  Since
> your new path is first, it won’t find LICENCE in your layer since you
> didn’t copy it.  Once way to quiet this warning would be to copy the
> license file to your directory.
>
>  
>
> -Bryan
>
>  
>
> *From:* Amit Tomer [mailto:amittome...@gmail.com]
> *Sent:* Thursday, October 03, 2013 8:23 AM
> *To:* Bryan Evenson
> *Cc:* yocto@yoctoproject.org
> *Subject:* Re: [yocto] Fwd: OpenSSH pre login banner
>
>  
>
> Hi Brayan
>
>  
>
> Thanks for your help
>
>  
>
> The way I modify .bbapend file is below
>
>  
>
> PRINC = "4"
>
> SRC_URI = "file://banner"
>
> FILESEXTRAPATHS_prepend := "${THISDIR}/openssh-6.1p1:"
>
> do_install_append() {
>
>  
>
> Install -m 755 ${WORKDIR}/banner ${D}${sysconfdir}/ssh
>
> }
>
>  
>
>  
>
>  
>
> But it gives me 
>
>  
>
> Below problem
>
>  
>
> WARNING:
> /tmp/work/cortexa15hf-vfp-neon-poky-linux-gnueabi/openssh/6.1p1-r3/openssh-6.1p1/LICENCE
> could not be copied for s

Re: [yocto] Install Kernel Modules in rootfs

On 13-10-03 10:09 AM, Raul Rosetto Munoz wrote:

Look all the time the modules of kernel 3.8 come.

My /lib/modules is like this:

That's where ? In your booted target ? What BSP are you using, how did
you install the image ?

Answering that question, will likely get you your answer. If you previously
generated a rootfs and installed it. You'd need to do the same thing
and do it with a clean install with the new kernel to remove all
remnants of the old package.

(That's assuming you aren't using package management on the target,
or package feeds. I don't, so manually look after this sort of thing).

Cheers,

Bruce

/lib/modules$ ll
total 16
drwxr-xr-x 4 raul raul 4096 Oct  3 10:09 ./
drwxr-xr-x 7 raul raul 4096 Oct  3 10:09 ../
drwxr-xr-x 2 raul raul 4096 Oct  3 10:09 2.6.35.3-1.1.0+yocto+g914558e/
drwxr-xr-x 3 raul raul 4096 Oct  1 15:45 3.8.13-fslc+g7205340/

/lib/modules$ ll 2.6.35.3-1.1.0+yocto+g914558e/
total 36
drwxr-xr-x 2 raul raul 4096 Oct  3 10:09 ./
drwxr-xr-x 4 raul raul 4096 Oct  3 10:09 ../
-rw-r--r-- 1 raul raul   45 Oct  3 10:09 modules.alias
-rw-r--r-- 1 raul raul   12 Oct  3 10:09 modules.alias.bin
-rw-r--r-- 1 raul raul0 Oct  3 10:09 modules.builtin.bin
-rw-r--r-- 1 raul raul0 Oct  3 10:09 modules.dep
-rw-r--r-- 1 raul raul   12 Oct  3 10:09 modules.dep.bin
-rw-r--r-- 1 raul raul   52 Oct  3 10:09 modules.devname
-rw-r--r-- 1 raul raul  131 Oct  3 10:09 modules.softdep
-rw-r--r-- 1 raul raul   49 Oct  3 10:09 modules.symbols
-rw-r--r-- 1 raul raul   12 Oct  3 10:09 modules.symbols.bin

/lib/modules$ ll 3.8.13-fslc+g7205340/
total 24
drwxr-xr-x 3 raul raul 4096 Oct  1 15:45 ./
drwxr-xr-x 4 raul raul 4096 Oct  3 10:09 ../
drwxr-xr-x 6 raul raul 4096 Oct  1 15:45 kernel/
-rw-r--r-- 1 raul raul 5153 Oct  1 15:45 modules.builtin
-rw-r--r-- 1 raul raul  391 Oct  1 15:45 modules.order

I have no idea how to remove the remains of the kernel 3.8.

I dont want to delete all the /tmp

=/

Take so much time.

On Thu, Oct 3, 2013 at 10:58 AM, Bruce Ashfield
mailto:bruce.ashfi...@windriver.com>> wrote:

On 13-10-03 09 :32 AM, Raul Rosetto Munoz wrote:

I think that I found my problem,

I tryed to use the kernel 3.8 before in this build system, but I
decided
to go back to the 2.6.35.3.

But now I did bitbake -c cleanall virtual/kernel, I tryed to delete
every thing about kernel 3.8 but the modules that are instaled in my
/lib/modules/ still be the modules of kernel 3.8.

How I clean the modules and force to use no 2.6.35.3 again.

Which package or command do that?

If you reconstruct your image, the old module package shouldn't be
re-used, since you would now have a dependency on the 2.6.35.x kernel.

How exactly are they installed in /lib/modules ? Did you do anything
in particular ?

Bruce

Thanks for all Help.

On Thu, Oct 3, 2013 at 9:38 AM, Bruce Ashfield
mailto:bruce.ashfi...@windriver.com>
>> wrote:

 On 13-10-03 08  :34
AM, Raul Rosetto Munoz wrote:

 Hello All,

 I'm Trying to install the kernel modules inside my
rootfs but I
 couldn't
 find an especific information that help me to do that!

 I have in my /tmp/images/ the tgz with all the modules
that I need.

 modules--2.6.35.3-r32.23-imx28evk-20131002210958.tgz

 I just want that this tzg was extracted inside my rootfs
 /lib/modules.

 Please some one can help me with this?

 Does your image type have a RDEPENDS on "kernel-modules",
or do you
 have IMAGE_INSTALL_append = " kernel-modules", in your
local.conf ?

 If you do either of the above, the entire set of built
modules will
 be installed.

 You can also install / require individual modules via
 kernel-module-.

 The Yocto docs should have details on this as well.

 Cheers,

 Bruce

 Thanks so much.

 --
 *Raul Rosetto Muñoz*

 ___
 yocto mailing list
yocto@yoctoproject.org 
__>
https://lists.yoctoproject.org/listinfo/yocto

 >

--
*Raul Rosetto Muñoz*

--
*Raul Rosetto Muñoz*

___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Install Kernel Modules in rootfs

Look all the time the modules of kernel 3.8 come.

My /lib/modules is like this:

/lib/modules$ ll
total 16
drwxr-xr-x 4 raul raul 4096 Oct  3 10:09 ./
drwxr-xr-x 7 raul raul 4096 Oct  3 10:09 ../
drwxr-xr-x 2 raul raul 4096 Oct  3 10:09 2.6.35.3-1.1.0+yocto+g914558e/
drwxr-xr-x 3 raul raul 4096 Oct  1 15:45 3.8.13-fslc+g7205340/


/lib/modules$ ll 2.6.35.3-1.1.0+yocto+g914558e/
total 36
drwxr-xr-x 2 raul raul 4096 Oct  3 10:09 ./
drwxr-xr-x 4 raul raul 4096 Oct  3 10:09 ../
-rw-r--r-- 1 raul raul   45 Oct  3 10:09 modules.alias
-rw-r--r-- 1 raul raul   12 Oct  3 10:09 modules.alias.bin
-rw-r--r-- 1 raul raul0 Oct  3 10:09 modules.builtin.bin
-rw-r--r-- 1 raul raul0 Oct  3 10:09 modules.dep
-rw-r--r-- 1 raul raul   12 Oct  3 10:09 modules.dep.bin
-rw-r--r-- 1 raul raul   52 Oct  3 10:09 modules.devname
-rw-r--r-- 1 raul raul  131 Oct  3 10:09 modules.softdep
-rw-r--r-- 1 raul raul   49 Oct  3 10:09 modules.symbols
-rw-r--r-- 1 raul raul   12 Oct  3 10:09 modules.symbols.bin

/lib/modules$ ll 3.8.13-fslc+g7205340/
total 24
drwxr-xr-x 3 raul raul 4096 Oct  1 15:45 ./
drwxr-xr-x 4 raul raul 4096 Oct  3 10:09 ../
drwxr-xr-x 6 raul raul 4096 Oct  1 15:45 kernel/
-rw-r--r-- 1 raul raul 5153 Oct  1 15:45 modules.builtin
-rw-r--r-- 1 raul raul  391 Oct  1 15:45 modules.order

I have no idea how to remove the remains of the kernel 3.8.

I dont want to delete all the /tmp

=/

Take so much time.








On Thu, Oct 3, 2013 at 10:58 AM, Bruce Ashfield <
bruce.ashfi...@windriver.com> wrote:

> On 13-10-03 09:32 AM, Raul Rosetto Munoz wrote:
>
>> I think that I found my problem,
>>
>> I tryed to use the kernel 3.8 before in this build system, but I decided
>> to go back to the 2.6.35.3.
>>
>> But now I did bitbake -c cleanall virtual/kernel, I tryed to delete
>> every thing about kernel 3.8 but the modules that are instaled in my
>> /lib/modules/ still be the modules of kernel 3.8.
>>
>> How I clean the modules and force to use no 2.6.35.3 again.
>>
>> Which package or command do that?
>>
>
> If you reconstruct your image, the old module package shouldn't be
> re-used, since you would now have a dependency on the 2.6.35.x kernel.
>
> How exactly are they installed in /lib/modules ? Did you do anything
> in particular ?
>
> Bruce
>
>
>> Thanks for all Help.
>>
>>
>> On Thu, Oct 3, 2013 at 9:38 AM, Bruce Ashfield
>> > >
>> wrote:
>>
>>
>> On 13-10-03 08 :34 AM, Raul Rosetto Munoz wrote:
>>
>> Hello All,
>>
>> I'm Trying to install the kernel modules inside my rootfs but I
>> couldn't
>> find an especific information that help me to do that!
>>
>> I have in my /tmp/images/ the tgz with all the modules that I
>> need.
>>
>> modules--2.6.35.3-r32.23-__**imx28evk-20131002210958.tgz
>>
>>
>> I just want that this tzg was extracted inside my rootfs
>> /lib/modules.
>>
>> Please some one can help me with this?
>>
>>
>> Does your image type have a RDEPENDS on "kernel-modules", or do you
>> have IMAGE_INSTALL_append = " kernel-modules", in your local.conf ?
>>
>> If you do either of the above, the entire set of built modules will
>> be installed.
>>
>> You can also install / require individual modules via
>> kernel-module-.
>>
>> The Yocto docs should have details on this as well.
>>
>> Cheers,
>>
>> Bruce
>>
>>
>> Thanks so much.
>>
>> --
>> *Raul Rosetto Muñoz*
>>
>>
>> __**___
>> yocto mailing list
>> yocto@yoctoproject.org 
>> https://lists.yoctoproject.__**org/listinfo/yocto
>>
>> 
>> 
>> >
>>
>>
>>
>>
>>
>> --
>> *Raul Rosetto Muñoz*
>>
>
>


-- 
*Raul Rosetto Muñoz*
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Fwd: OpenSSH pre login banner

Amit,

Good to hear you got your recipe in order.  Best way to learn more about the 
Yocto Project and the Poky distribution is through watching this mailing list 
and the Poky mailing list (p...@yoctoproject.org) 
to see how other people solve their problems they come across.  And, by reading 
the documentation over at http://www.yoctoproject.org/documentation/current/.

-Bryan

From: Amit Tomer [mailto:amittome...@gmail.com]
Sent: Thursday, October 03, 2013 10:03 AM
To: Bryan Evenson
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] Fwd: OpenSSH pre login banner

Thanks again Bryan for your kind response

The reason for having the PRINC ="4" is becaue when I started modifying this 
already existing file
value of PRINC is set 3 ,so for my changes I Incremented it to One.

Change
SRC_URI = "file://banner"
To
SRC_URI += "file://banner"

I am really feeling bit stupid here ,I just in hurry forgot to put + sign
Though I learned a new point

"With your line, you are overriding all the SRC_URI for the entire openssh 
recipe and the openssh recipe will only include the banner file ".

Change
FILESEXTRAPATHS_prepend := "${THISDIR}/openssh-6.1p1:"
to
FILESEXTRAPATHS_prepend := "${THISDIR}:"

We already had openssh-6.1p1 folder where our sshd_config file is placed ,So I 
guess it won't harm
much if I put FILESEXTRAPATHS_prepend := "${THISDIR}/openssh-6.1p1:" with 
banner file in openssh-6.1p1 folder

One more point wanted from your end,what is best way to learn Yocto
How can improve my knowledge in Yocto?

Thanks
Amit.

On Thu, Oct 3, 2013 at 7:05 PM, Bryan Evenson 
mailto:beven...@melinkcorp.com>> wrote:
Amit,

First, I suggest you change
PRINC = "4"
to
PRINC := "${@int(PRINC) + 1}"

This way your bbappend will always increment the PR to one more than the PR 
called out by the main recipe.  So if the openssh recipe would get updated and 
increment the PR, you do not have to change your bbappend.

Change
SRC_URI = "file://banner"
To
SRC_URI += "file://banner"

The += appends your banner file to the SRC_URI for the openssh recipe.  With 
your line, you are overriding all the SRC_URI for the entire openssh recipe and 
the openssh recipe will only include the banner file.  I've taken to the habit 
of writing the SRC_URI as follows:

SRC_URI += " \
file://banner \
"
just to ensure that words aren't joined together when my SRC_URI is appended to 
the existing one.  I don't know if this is strictly necessary, but it's not a 
bad habit.

Change
FILESEXTRAPATHS_prepend := "${THISDIR}/openssh-6.1p1:"
to
FILESEXTRAPATHS_prepend := "${THISDIR}:"

so Bitbake can find your banner file and sshd_config that you have in the same 
directory as the bbappend.

I can't remember if you get a warning if Bitbake can't find the license file at 
all or if it fails on each attempt through the filepath.  Since your new path 
is first, it won't find LICENCE in your layer since you didn't copy it.  Once 
way to quiet this warning would be to copy the license file to your directory.

-Bryan

From: Amit Tomer [mailto:amittome...@gmail.com]
Sent: Thursday, October 03, 2013 8:23 AM
To: Bryan Evenson
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] Fwd: OpenSSH pre login banner

Hi Brayan

Thanks for your help

The way I modify .bbapend file is below

PRINC = "4"
SRC_URI = "file://banner"
FILESEXTRAPATHS_prepend := "${THISDIR}/openssh-6.1p1:"
do_install_append() {

Install -m 755 ${WORKDIR}/banner ${D}${sysconfdir}/ssh
}

But it gives me

Below problem

WARNING: 
/tmp/work/cortexa15hf-vfp-neon-poky-linux-gnueabi/openssh/6.1p1-r3/openssh-6.1p1/LICENCE
 could not be copied for some reason. It may not exist. WARN for now.

And my build process is really got slow and sometimes I am getting the error 
also

What could be the reason for above??

On Thu, Oct 3, 2013 at 5:49 PM, Bryan Evenson 
mailto:beven...@melinkcorp.com>> wrote:
Amit,

>From your message, I'm assuming you have a bbappend file for openssh.  
>Following the example in section of 5.1.4 of the Mega Manual (located at 
>http://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#using-bbappend-files)
> and from personal experience, put the following in your bbappend file:

FILESEXTRAPATHS_prepend := " ${THISDIR}: "
SRC_URI += " file://banner "
FILES_${PN} += " /etc/ssh/banner "

do_install_append() {
install -d ${D}${sysconfdir}/ssh
install -m 0644 ${WORKDIR}/banner ${D}${sysconfdir/ssh/banner
}
PRINC := "${@int(PRINC) + 1}"

then place your banner file and sshd_config in the same directory as your 
bbappend.  When openssh gets built, Bitbake will find your sshd_config first 
and use and install that file instead of the one from the main layer.  The 
recipe also tells it how to handle the new banner file that is not part of the 
original recipe; you do not need to put these rules in place for sshd_config 
because that is already part of the original rec

Re: [yocto] Fwd: OpenSSH pre login banner

Thanks again Bryan for your kind response

The reason for having the PRINC ="4" is becaue when I started modifying
this already existing file
value of PRINC is set 3 ,so for my changes I Incremented it to One.

Change

SRC_URI = “file://banner”

To

SRC_URI += “file://banner“


I am really feeling bit stupid here ,I just in hurry forgot to put + sign

Though I learned a new point


"With your line, you are overriding all the SRC_URI for the entire openssh
recipe and the openssh recipe will only include the banner file ".


Change

FILESEXTRAPATHS_prepend := "${THISDIR}/openssh-6.1p1:"

to

FILESEXTRAPATHS_prepend := "${THISDIR}:"

**

We already had openssh-6.1p1 folder where our sshd_config file is placed
,So I guess it won't harm

much if I put FILESEXTRAPATHS_prepend := "${THISDIR}/openssh-6.1p1:" with
banner file in openssh-6.1p1 folder


One more point wanted from your end,what is best way to learn Yocto

How can improve my knowledge in Yocto?


Thanks

Amit.






On Thu, Oct 3, 2013 at 7:05 PM, Bryan Evenson wrote:

> Amit,
>
> ** **
>
> First, I suggest you change
>
> PRINC = “4”
>
> to
>
> PRINC := "${@int(PRINC) + 1}"
>
> ** **
>
> This way your bbappend will always increment the PR to one more than the
> PR called out by the main recipe.  So if the openssh recipe would get
> updated and increment the PR, you do not have to change your bbappend.
>
> ** **
>
> Change
>
> SRC_URI = “file://banner”
>
> To
>
> SRC_URI += “file://banner“
>
> ** **
>
> The += appends your banner file to the SRC_URI for the openssh recipe.
> With your line, you are overriding all the SRC_URI for the entire openssh
> recipe and the openssh recipe will only include the banner file.  I’ve
> taken to the habit of writing the SRC_URI as follows:
>
> ** **
>
> SRC_URI += “ \
>
> file://banner \
>
> “
>
> just to ensure that words aren’t joined together when my SRC_URI is
> appended to the existing one.  I don’t know if this is strictly necessary,
> but it’s not a bad habit.
>
> ** **
>
> Change
>
> FILESEXTRAPATHS_prepend := "${THISDIR}/openssh-6.1p1:"
>
> to
>
> FILESEXTRAPATHS_prepend := "${THISDIR}:"
>
> ** **
>
> so Bitbake can find your banner file and sshd_config that you have in the
> same directory as the bbappend.
>
> ** **
>
> I can’t remember if you get a warning if Bitbake can’t find the license
> file at all or if it fails on each attempt through the filepath.  Since
> your new path is first, it won’t find LICENCE in your layer since you
> didn’t copy it.  Once way to quiet this warning would be to copy the
> license file to your directory.
>
> ** **
>
> -Bryan
>
> ** **
>
> *From:* Amit Tomer [mailto:amittome...@gmail.com]
> *Sent:* Thursday, October 03, 2013 8:23 AM
> *To:* Bryan Evenson
> *Cc:* yocto@yoctoproject.org
> *Subject:* Re: [yocto] Fwd: OpenSSH pre login banner
>
> ** **
>
> Hi Brayan
>
> ** **
>
> Thanks for your help
>
> ** **
>
> The way I modify .bbapend file is below
>
> ** **
>
> PRINC = "4"
>
> SRC_URI = "file://banner"
>
> FILESEXTRAPATHS_prepend := "${THISDIR}/openssh-6.1p1:"
>
> do_install_append() {
>
> ** **
>
> Install -m 755 ${WORKDIR}/banner ${D}${sysconfdir}/ssh
>
> }
>
> ** **
>
> ** **
>
> ** **
>
> But it gives me 
>
> ** **
>
> Below problem
>
> ** **
>
> WARNING:
> /tmp/work/cortexa15hf-vfp-neon-poky-linux-gnueabi/openssh/6.1p1-r3/openssh-6.1p1/LICENCE
> could not be copied for some reason. It may not exist. WARN for now.
>
> ** **
>
> And my build process is really got slow and sometimes I am getting the
> error also
>
> ** **
>
> What could be the reason for above??
>
> ** **
>
> ** **
>
> ** **
>
> ** **
>
> ** **
>
> ** **
>
> On Thu, Oct 3, 2013 at 5:49 PM, Bryan Evenson 
> wrote:
>
> Amit,
>
>  
>
> From your message, I’m assuming you have a bbappend file for openssh.
> Following the example in section of 5.1.4 of the Mega Manual (located at
> http://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#using-bbappend-files)
> and from personal experience, put the following in your bbappend file:
>
>  
>
> FILESEXTRAPATHS_prepend := " ${THISDIR}: "
>
> SRC_URI += “ file://banner ”
>
> FILES_${PN} += “ /etc/ssh/banner ”
>
>  
>
> do_install_append() {
>
> install –d ${D}${sysconfdir}/ssh
>
> install –m 0644 ${WORKDIR}/banner
> ${D}${sysconfdir/ssh/banner
>
> }
>
> PRINC := "${@int(PRINC) + 1}"
>
>  
>
> then place your banner file and sshd_config in the same directory as your
> bbappend.  When openssh gets built, Bitbake will find your sshd_config
> first and use and install that file instead of the one from the main
> layer.  The recipe also tells it how to handle the new banner file that is
> not part of the original recipe; you do not need to put these rules in
> place for sshd_config because that is

Re: [yocto] Install Kernel Modules in rootfs


On 13-10-03 09:32 AM, Raul Rosetto Munoz wrote:

I think that I found my problem,

I tryed to use the kernel 3.8 before in this build system, but I decided
to go back to the 2.6.35.3.

But now I did bitbake -c cleanall virtual/kernel, I tryed to delete
every thing about kernel 3.8 but the modules that are instaled in my
/lib/modules/ still be the modules of kernel 3.8.

How I clean the modules and force to use no 2.6.35.3 again.

Which package or command do that?


If you reconstruct your image, the old module package shouldn't be
re-used, since you would now have a dependency on the 2.6.35.x kernel.

How exactly are they installed in /lib/modules ? Did you do anything
in particular ?

Bruce



Thanks for all Help.


On Thu, Oct 3, 2013 at 9:38 AM, Bruce Ashfield
mailto:bruce.ashfi...@windriver.com>> wrote:

On 13-10-03 08 :34 AM, Raul Rosetto Munoz wrote:

Hello All,

I'm Trying to install the kernel modules inside my rootfs but I
couldn't
find an especific information that help me to do that!

I have in my /tmp/images/ the tgz with all the modules that I need.

modules--2.6.35.3-r32.23-__imx28evk-20131002210958.tgz

I just want that this tzg was extracted inside my rootfs
/lib/modules.

Please some one can help me with this?


Does your image type have a RDEPENDS on "kernel-modules", or do you
have IMAGE_INSTALL_append = " kernel-modules", in your local.conf ?

If you do either of the above, the entire set of built modules will
be installed.

You can also install / require individual modules via
kernel-module-.

The Yocto docs should have details on this as well.

Cheers,

Bruce


Thanks so much.

--
*Raul Rosetto Muñoz*


_
yocto mailing list
yocto@yoctoproject.org 
https://lists.yoctoproject.__org/listinfo/yocto






--
*Raul Rosetto Muñoz*


___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Fwd: OpenSSH pre login banner

Amit,

First, I suggest you change
PRINC = "4"
to
PRINC := "${@int(PRINC) + 1}"

This way your bbappend will always increment the PR to one more than the PR 
called out by the main recipe.  So if the openssh recipe would get updated and 
increment the PR, you do not have to change your bbappend.

Change
SRC_URI = "file://banner"
To
SRC_URI += "file://banner"

The += appends your banner file to the SRC_URI for the openssh recipe.  With 
your line, you are overriding all the SRC_URI for the entire openssh recipe and 
the openssh recipe will only include the banner file.  I've taken to the habit 
of writing the SRC_URI as follows:

SRC_URI += " \
file://banner \
"
just to ensure that words aren't joined together when my SRC_URI is appended to 
the existing one.  I don't know if this is strictly necessary, but it's not a 
bad habit.

Change
FILESEXTRAPATHS_prepend := "${THISDIR}/openssh-6.1p1:"
to
FILESEXTRAPATHS_prepend := "${THISDIR}:"

so Bitbake can find your banner file and sshd_config that you have in the same 
directory as the bbappend.

I can't remember if you get a warning if Bitbake can't find the license file at 
all or if it fails on each attempt through the filepath.  Since your new path 
is first, it won't find LICENCE in your layer since you didn't copy it.  Once 
way to quiet this warning would be to copy the license file to your directory.

-Bryan

From: Amit Tomer [mailto:amittome...@gmail.com]
Sent: Thursday, October 03, 2013 8:23 AM
To: Bryan Evenson
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] Fwd: OpenSSH pre login banner

Hi Brayan

Thanks for your help

The way I modify .bbapend file is below

PRINC = "4"
SRC_URI = "file://banner"
FILESEXTRAPATHS_prepend := "${THISDIR}/openssh-6.1p1:"
do_install_append() {

Install -m 755 ${WORKDIR}/banner ${D}${sysconfdir}/ssh
}

But it gives me

Below problem

WARNING: 
/tmp/work/cortexa15hf-vfp-neon-poky-linux-gnueabi/openssh/6.1p1-r3/openssh-6.1p1/LICENCE
 could not be copied for some reason. It may not exist. WARN for now.

And my build process is really got slow and sometimes I am getting the error 
also

What could be the reason for above??

On Thu, Oct 3, 2013 at 5:49 PM, Bryan Evenson 
mailto:beven...@melinkcorp.com>> wrote:
Amit,

>From your message, I'm assuming you have a bbappend file for openssh.  
>Following the example in section of 5.1.4 of the Mega Manual (located at 
>http://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#using-bbappend-files)
> and from personal experience, put the following in your bbappend file:

FILESEXTRAPATHS_prepend := " ${THISDIR}: "
SRC_URI += " file://banner "
FILES_${PN} += " /etc/ssh/banner "

do_install_append() {
install -d ${D}${sysconfdir}/ssh
install -m 0644 ${WORKDIR}/banner ${D}${sysconfdir/ssh/banner
}
PRINC := "${@int(PRINC) + 1}"

then place your banner file and sshd_config in the same directory as your 
bbappend.  When openssh gets built, Bitbake will find your sshd_config first 
and use and install that file instead of the one from the main layer.  The 
recipe also tells it how to handle the new banner file that is not part of the 
original recipe; you do not need to put these rules in place for sshd_config 
because that is already part of the original recipe.  Then in the future every 
time you make a change to the openssh package in your layer, increment the 
PRINC so your package management tools will see it as an upgrade.  For example, 
if you change the contents of the banner file, then change the "+ 1" to "+ 2".

-Bryan

From: yocto-boun...@yoctoproject.org 
[mailto:yocto-boun...@yoctoproject.org] 
On Behalf Of Amit Tomer
Sent: Thursday, October 03, 2013 7:05 AM
To: yocto@yoctoproject.org
Subject: [yocto] Fwd: OpenSSH pre login banner

-- Forwarded message --
From: Amit Tomer mailto:amittome...@gmail.com>>
Date: Thu, Oct 3, 2013 at 1:50 PM
Subject: OpenSSH pre login banner
To: "yocto-requ...@yoctoproject.org" 
mailto:yocto-requ...@yoctoproject.org>>
I am new to OpenEmbedded Yocto and have a requirement where OpenSSH pre login 
banner
should come when do ssh from target board

Now I know I have to create a simple .txt file(banner) and put my banner in to 
it and add the following to sshd_config

Banner /etc/ssh/banner

But now  wanted to know where should I keep my banner file in yocto so that 
Yocto build infrastructure will pack banner file  to /etc/ssh/banner into final 
image.

I do have receipes for openssh in meta-xyz/recipes-connectivity/openssh  folder

Thanks
Amit

___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Install Kernel Modules in rootfs

I think that I found my problem,

I tryed to use the kernel 3.8 before in this build system, but I decided to
go back to the 2.6.35.3.

But now I did bitbake -c cleanall virtual/kernel, I tryed to delete every
thing about kernel 3.8 but the modules that are instaled in my
/lib/modules/ still be the modules of kernel 3.8.

How I clean the modules and force to use no 2.6.35.3 again.

Which package or command do that?

Thanks for all Help.


On Thu, Oct 3, 2013 at 9:38 AM, Bruce Ashfield  wrote:

> On 13-10-03 08:34 AM, Raul Rosetto Munoz wrote:
>
>> Hello All,
>>
>> I'm Trying to install the kernel modules inside my rootfs but I couldn't
>> find an especific information that help me to do that!
>>
>> I have in my /tmp/images/ the tgz with all the modules that I need.
>>
>> modules--2.6.35.3-r32.23-**imx28evk-20131002210958.tgz
>>
>> I just want that this tzg was extracted inside my rootfs /lib/modules.
>>
>> Please some one can help me with this?
>>
>
> Does your image type have a RDEPENDS on "kernel-modules", or do you
> have IMAGE_INSTALL_append = " kernel-modules", in your local.conf ?
>
> If you do either of the above, the entire set of built modules will
> be installed.
>
> You can also install / require individual modules via
> kernel-module-.
>
> The Yocto docs should have details on this as well.
>
> Cheers,
>
> Bruce
>
>
>> Thanks so much.
>>
>> --
>> *Raul Rosetto Muñoz*
>>
>>
>> __**_
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.**org/listinfo/yocto
>>
>>
>


-- 
*Raul Rosetto Muñoz*
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Install Kernel Modules in rootfs


On 13-10-03 08:34 AM, Raul Rosetto Munoz wrote:

Hello All,

I'm Trying to install the kernel modules inside my rootfs but I couldn't
find an especific information that help me to do that!

I have in my /tmp/images/ the tgz with all the modules that I need.

modules--2.6.35.3-r32.23-imx28evk-20131002210958.tgz

I just want that this tzg was extracted inside my rootfs /lib/modules.

Please some one can help me with this?


Does your image type have a RDEPENDS on "kernel-modules", or do you
have IMAGE_INSTALL_append = " kernel-modules", in your local.conf ?

If you do either of the above, the entire set of built modules will
be installed.

You can also install / require individual modules via 
kernel-module-.


The Yocto docs should have details on this as well.

Cheers,

Bruce



Thanks so much.

--
*Raul Rosetto Muñoz*


___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto



___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Install Kernel Modules in rootfs

Hello All,

I'm Trying to install the kernel modules inside my rootfs but I couldn't
find an especific information that help me to do that!

I have in my /tmp/images/ the tgz with all the modules that I need.

modules--2.6.35.3-r32.23-imx28evk-20131002210958.tgz

I just want that this tzg was extracted inside my rootfs /lib/modules.

Please some one can help me with this?

Thanks so much.

-- 
*Raul Rosetto Muñoz*
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Fwd: OpenSSH pre login banner

Hi Brayan

Thanks for your help

The way I modify .bbapend file is below

PRINC = "4"
SRC_URI = "file://banner"
FILESEXTRAPATHS_prepend := "${THISDIR}/openssh-6.1p1:"
do_install_append() {

Install -m 755 ${WORKDIR}/banner ${D}${sysconfdir}/ssh
}



But it gives me

Below problem

WARNING:
/tmp/work/cortexa15hf-vfp-neon-poky-linux-gnueabi/openssh/6.1p1-r3/openssh-6.1p1/LICENCE
could not be copied for some reason. It may not exist. WARN for now.

And my build process is really got slow and sometimes I am getting the
error also

What could be the reason for above??







On Thu, Oct 3, 2013 at 5:49 PM, Bryan Evenson wrote:

> Amit,
>
> ** **
>
> From your message, I’m assuming you have a bbappend file for openssh.
> Following the example in section of 5.1.4 of the Mega Manual (located at
> http://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#using-bbappend-files)
> and from personal experience, put the following in your bbappend file:
>
> ** **
>
> FILESEXTRAPATHS_prepend := " ${THISDIR}: "
>
> SRC_URI += “ file://banner ”
>
> FILES_${PN} += “ /etc/ssh/banner ”
>
> ** **
>
> do_install_append() {
>
> install –d ${D}${sysconfdir}/ssh
>
> install –m 0644 ${WORKDIR}/banner
> ${D}${sysconfdir/ssh/banner
>
> }
>
> PRINC := "${@int(PRINC) + 1}"
>
> ** **
>
> then place your banner file and sshd_config in the same directory as your
> bbappend.  When openssh gets built, Bitbake will find your sshd_config
> first and use and install that file instead of the one from the main
> layer.  The recipe also tells it how to handle the new banner file that is
> not part of the original recipe; you do not need to put these rules in
> place for sshd_config because that is already part of the original recipe.
> Then in the future every time you make a change to the openssh package in
> your layer, increment the PRINC so your package management tools will see
> it as an upgrade.  For example, if you change the contents of the banner
> file, then change the “+ 1” to “+ 2”.
>
> ** **
>
> -Bryan
>
> ** **
>
> *From:* yocto-boun...@yoctoproject.org [mailto:
> yocto-boun...@yoctoproject.org] *On Behalf Of *Amit Tomer
> *Sent:* Thursday, October 03, 2013 7:05 AM
> *To:* yocto@yoctoproject.org
> *Subject:* [yocto] Fwd: OpenSSH pre login banner
>
> ** **
>
> ** **
>
> -- Forwarded message --
> From: *Amit Tomer* 
> Date: Thu, Oct 3, 2013 at 1:50 PM
> Subject: OpenSSH pre login banner
> To: "yocto-requ...@yoctoproject.org" 
>
> 
>
> I am new to OpenEmbedded Yocto and have a requirement where OpenSSH pre
> login banner
>
> should come when do ssh from target board
>
> ** **
>
> Now I know I have to create a simple .txt file(banner) and put my banner
> in to it and add the following to sshd_config
>
> ** **
>
> Banner /etc/ssh/banner 
>
> ** **
>
> But now  wanted to know where should I keep my banner file in yocto so
> that Yocto build infrastructure will pack banner file  to /etc/ssh/banner
> into final image.
>
> ** **
>
> I do have receipes for openssh in meta-xyz/recipes-connectivity/openssh
>  folder
>
> ** **
>
> Thanks 
>
> Amit 
>
>  
>
> ** **
>
> ** **
>
> ** **
>
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Fwd: OpenSSH pre login banner

Amit,

>From your message, I'm assuming you have a bbappend file for openssh.  
>Following the example in section of 5.1.4 of the Mega Manual (located at 
>http://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#using-bbappend-files)
> and from personal experience, put the following in your bbappend file:

FILESEXTRAPATHS_prepend := " ${THISDIR}: "
SRC_URI += " file://banner "
FILES_${PN} += " /etc/ssh/banner "

do_install_append() {
install -d ${D}${sysconfdir}/ssh
install -m 0644 ${WORKDIR}/banner ${D}${sysconfdir/ssh/banner
}
PRINC := "${@int(PRINC) + 1}"

then place your banner file and sshd_config in the same directory as your 
bbappend.  When openssh gets built, Bitbake will find your sshd_config first 
and use and install that file instead of the one from the main layer.  The 
recipe also tells it how to handle the new banner file that is not part of the 
original recipe; you do not need to put these rules in place for sshd_config 
because that is already part of the original recipe.  Then in the future every 
time you make a change to the openssh package in your layer, increment the 
PRINC so your package management tools will see it as an upgrade.  For example, 
if you change the contents of the banner file, then change the "+ 1" to "+ 2".

-Bryan

From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On 
Behalf Of Amit Tomer
Sent: Thursday, October 03, 2013 7:05 AM
To: yocto@yoctoproject.org
Subject: [yocto] Fwd: OpenSSH pre login banner


-- Forwarded message --
From: Amit Tomer mailto:amittome...@gmail.com>>
Date: Thu, Oct 3, 2013 at 1:50 PM
Subject: OpenSSH pre login banner
To: "yocto-requ...@yoctoproject.org" 
mailto:yocto-requ...@yoctoproject.org>>

I am new to OpenEmbedded Yocto and have a requirement where OpenSSH pre login 
banner
should come when do ssh from target board

Now I know I have to create a simple .txt file(banner) and put my banner in to 
it and add the following to sshd_config

Banner /etc/ssh/banner

But now  wanted to know where should I keep my banner file in yocto so that 
Yocto build infrastructure will pack banner file  to /etc/ssh/banner into final 
image.

I do have receipes for openssh in meta-xyz/recipes-connectivity/openssh  folder

Thanks
Amit




___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Fwd: OpenSSH pre login banner