error

error

[B. Zhang]

error: wait_for_sysfs needs an update to handle the device
'/class/pcmcia_socket/pcmcia_socket1' properly, please report to
<linux-hotplug-devel@lists.sourceforge.net>

error: wait_for_sysfs needs an update to handle the device
'/class/pcmcia_socket/pcmcia_socket0' properly, please report to
<linux-hotplug-devel@lists.sourceforge.net>

error: wait_for_sysfs needs an update to handle the device
'/class/nvidia/nvidiactl' properly, please report to
<linux-hotplug-devel@lists.sourceforge.net>

error: wait_for_sysfs needs an update to handle the device
'/class/ppp/ppp' properly, please report to
<linux-hotplug-devel@lists.sourceforge.net>

error: wait_for_sysfs needs an update to handle the device
'/class/net/ppp0' properly, please report to
<linux-hotplug-devel@lists.sourceforge.net>



-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

Re: error

[Greg KH]

On Tue, Oct 12, 2004 at 09:01:58AM +0200, B. Zhang wrote:
> error: wait_for_sysfs needs an update to handle the device
> '/class/pcmcia_socket/pcmcia_socket1' properly, please report to
> <linux-hotplug-devel@lists.sourceforge.net>
> 
> error: wait_for_sysfs needs an update to handle the device
> '/class/pcmcia_socket/pcmcia_socket0' properly, please report to
> <linux-hotplug-devel@lists.sourceforge.net>
> 
> error: wait_for_sysfs needs an update to handle the device
> '/class/nvidia/nvidiactl' properly, please report to
> <linux-hotplug-devel@lists.sourceforge.net>
> 
> error: wait_for_sysfs needs an update to handle the device
> '/class/ppp/ppp' properly, please report to
> <linux-hotplug-devel@lists.sourceforge.net>
> 
> error: wait_for_sysfs needs an update to handle the device
> '/class/net/ppp0' properly, please report to
> <linux-hotplug-devel@lists.sourceforge.net>

With what version of udev is this?  The 035 release should fix these
errors.

thanks,

greg k-h


-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

Re: error

[B. Zhang]

On Tue, 2004-10-12 at 09:10, Greg KH wrote:
> On Tue, Oct 12, 2004 at 09:01:58AM +0200, B. Zhang wrote:
> > error: wait_for_sysfs needs an update to handle the device
> > '/class/pcmcia_socket/pcmcia_socket1' properly, please report to
> > <linux-hotplug-devel@lists.sourceforge.net>
> > 
> > error: wait_for_sysfs needs an update to handle the device
> > '/class/pcmcia_socket/pcmcia_socket0' properly, please report to
> > <linux-hotplug-devel@lists.sourceforge.net>
> > 
> > error: wait_for_sysfs needs an update to handle the device
> > '/class/nvidia/nvidiactl' properly, please report to
> > <linux-hotplug-devel@lists.sourceforge.net>
> > 
> > error: wait_for_sysfs needs an update to handle the device
> > '/class/ppp/ppp' properly, please report to
> > <linux-hotplug-devel@lists.sourceforge.net>
> > 
> > error: wait_for_sysfs needs an update to handle the device
> > '/class/net/ppp0' properly, please report to
> > <linux-hotplug-devel@lists.sourceforge.net>
> 
> With what version of udev is this?
034

>   The 035 release should fix these
> errors.
OK. Thanks.

Benoit
> 
> thanks,
> 
> greg k-h


-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

error

[MAILER-DAEMON]

The original message was received at Mon, 11 Mar 2019 11:44:43 +0800
from lists.01.org [32.243.43.235]

----- The following addresses had permanent fatal errors -----
<linux-nvdimm@lists.01.org>



_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm

error

[MAILER-DAEMON]

The original message was received at Mon, 11 Mar 2019 11:44:43 +0800
from lists.01.org [32.243.43.235]

----- The following addresses had permanent fatal errors -----
<linux-nvdimm-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org>

error

[Mail Administrator]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=us-ascii, Size: 657 bytes --]

Óxv›Vië'Æq²‘.s$¦1
Q1Û˜OÅÉ5ÙèŸ9mY'жÒqƒµæ?Ì*Ÿ× >œ6·_ìþ{>D`‰á %9½u#›s:Zéì«Î"p}]Ä_<z}¹¢g<›öý%n)­M[ASIˆ›
Žà’Uý½½K»5põàá3µ‡.æ…Ü>0ƒpsæ¼Èl¯\Œ`nän4àÑâq„F-ƒ:Eß.ªÜÜp¿½"bR›³ß6¼¾!ãapïâ%jd¦ÇŸ‘‡ÇêÅx®^“ËËÀiS°\¥ÛÊø(Œ½*áš2›í«IÚœû‚œy¢0¯Z¥°{»olöänN
®<UŸ{ïúpѵÆbP6³HmÑªò×ÂE{>ˆú5ª´"˜ÏîõGK>ov4ŒGͯoÊT\ça˜Vô_c<¸x‰ |–Õ¡¼­Y
D”’…ß‘Ktk²ˆ
À5/zê–‘XLü±m´àËÖÖÁË›…Šm_¤ iðþÜd8¡[àòj›Ñ¯n^ÞP„²ËjJkFÃÕÛBú´[Ø"ŒâëÕ#ÏÁÏÜԐò¯¤²döy%XÇÌk¿°Žow}¡Ó]ì¬o»™†|0›¯Ë¥Ìí|tKKï
úY<Ÿ‘„›§Êi(Å`‘X‹ˆ¢ê×£Dv‰§6i?xR¶“õmZr¤ñ1âgnR±Ž¾hã‰h©xÂðw¶ýÀ.ÎÙY]ÆvàV…øŸ±WÂW2G¹„xá‘.ê]{÷éæÙ:^‰3…ç¯òwULÔ±È%ü‰xüÖLÃ>„FI}èU°-¤Ç"p;%¥U”ÅÉënyL,­<`ïÀ®¼ú–WÍÝÂi%&ñPÏ%ÙЯ_V©ÓaÈ嘦füeÛZN¯ ÃÜ…ùANºÌxkce‘£]t¹…Å…>gVŽKw$x"/©Œ„lŒ¾&]º


[-- Attachment #2: Type: text/plain, Size: 178 bytes --]

_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org
https://lists.01.org/mailman/listinfo/linux-nvdimm

Error

[MAILER-DAEMON]

The original message was received at Thu, 14 Sep 2017 17:51:10 +0800
from lists.01.org [115.243.99.229]

----- The following addresses had permanent fatal errors -----
<linux-nvdimm@lists.01.org>

----- Transcript of session follows -----
  while talking to lists.01.org.:
>>> MAIL From:"MAILER-DAEMON" <noreply@lists.01.org>
<<< 501 "MAILER-DAEMON" <noreply@lists.01.org>... Refused



_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm

Error

[MAILER-DAEMON]

The original message was received at Thu, 14 Sep 2017 17:51:10 +0800
from lists.01.org [115.243.99.229]

----- The following addresses had permanent fatal errors -----
<linux-nvdimm-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org>

----- Transcript of session follows -----
  while talking to lists.01.org.:
>>> MAIL From:"MAILER-DAEMON" <noreply-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org>
<<< 501 "MAILER-DAEMON" <noreply-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org>... Refused

error

[Prabhod Bangera]

[-- Attachment #1.1: Type: text/plain, Size: 1134 bytes --]


nf17esx2362lnx03 kernel: sysctl: The scan_unevictable_pages sysctl/node-interface has been disabled for lack of a legitimate use case.  If you have one,
[Majesco]<http://www.majesco.com/>
Thanks and Regards,
Prabhod Bangera / Assistant Manager- Unix
prabhod.bangera@majesco.com<mailto:prabhod.bangera@majesco.com> /Cell: +91-9820395134 /Ext: 1370, VoIP: 1370
Majesco/MNDC, MBP-P-136, 136A, Mahape, Navi Mumbai, Maharashtra 400710
http://www.majesco.com<http://www.majesco.com/>












CONFIDENTIALITY NOTICE: THE CONTENTS OF THIS EMAIL MESSAGE AND ANY ATTACHMENTS ARE INTENDED SOLELY FOR THE ADDRESSEE(S) AND MAY CONTAIN CONFIDENTIAL AND/OR PRIVILEGED INFORMATION AND MAY BE LEGALLY PROTECTED FROM DISCLOSURE. IF YOU ARE NOT THE INTENDED RECIPIENT OF THIS MESSAGE OR THEIR AGENT, OR IF THIS MESSAGE HAS BEEN ADDRESSED TO YOU IN ERROR, PLEASE IMMEDIATELY ALERT THE SENDER BY REPLY EMAIL AND THEN DELETE THIS MESSAGE AND ANY ATTACHMENTS. IF YOU ARE NOT THE INTENDED RECIPIENT, YOU ARE HEREBY NOTIFIED THAT ANY USE, DISSEMINATION, COPYING, OR STORAGE OF THIS MESSAGE OR ITS ATTACHMENTS IS STRICTLY PROHIBITED.

[-- Attachment #1.2: Type: text/html, Size: 6441 bytes --]

[-- Attachment #2: image001.jpg --]
[-- Type: image/jpeg, Size: 19294 bytes --]

Re: error

[Jeff King]

[re-adding git@vger to the cc; please keep conversations on the list so
 everybody can benefit from the answers]

On Tue, Oct 04, 2016 at 01:13:16PM -0300, Luciano Schillagi wrote:

> I ran the command
> 
> Luko ~ $ git config --global --unset push.default
> 
> 
> and it gives me the following
> 
> warning: push.default has multiple values

Ah, OK. "--unset-all" would do the trick, but it may only be one
instance that you want to get rid of...

> I can access my file .gitconfig
> 
> I send attached...
> [...]
>
> [push]
> 	default = upstream
> 	default = aguas

Yep. Deleting the second line there will make your problem go away, and
presumably the first is a config setting you'd want to keep. That still
doesn't answer the question of how the "aguas" line got there, but I can
guess that at some point you might have set "push.default" instead of
"remote.pushdefault".

-Peff

Re: error

[Jeff King]

On Thu, Sep 22, 2016 at 08:02:35PM -0300, Luciano Schillagi wrote:

> please, what should I do to fix this error? thanks
> 
> Luko ~ $ git init
> error: malformed value for push.default: aguas
> error: Must be one of nothing, matching, simple, upstream or current.
> fatal: bad config variable 'push.default' in file '/Users/imac/.gitconfig' at line 16
> -bash: __git_ps1: command not found

Your config file has a bogus value in it.  Try:

  git config --global --unset push.default

Or you may want to simply edit /Users/imac/.gitconfig by hand. It is not
clear where the bogus value came from, but possibly the file is
corrupted in some way (so you are better off examining it first before
asking git to blindly change it).

-Peff

error

[Luciano Schillagi]

Hi,

please, what should I do to fix this error? thanks


Luko ~ $ git init
error: malformed value for push.default: aguas
error: Must be one of nothing, matching, simple, upstream or current.
fatal: bad config variable 'push.default' in file '/Users/imac/.gitconfig' at line 16
-bash: __git_ps1: command not found

Error

[MAILER-DAEMON]

The original message was received at Wed, 7 Sep 2016 12:32:58 +0530
from [155.78.86.25]

----- The following addresses had permanent fatal errors -----
<linux-nvdimm@lists.01.org>

----- Transcript of session follows -----
... while talking to 178.149.45.141:
554 <linux-nvdimm@lists.01.org>... Mail quota exceeded
554 <linux-nvdimm@lists.01.org>... Service unavailable

_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm

Error

[MAILER-DAEMON]

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

Spam detection software, running on the system "blaine.gmane.org",
has identified this incoming email as possible spam.  The original
message has been attached to this so you can view it or label
similar future email.  If you have any questions, see
@@CONTACT_ADDRESS@@ for details.

Content preview:  The original message was received at Wed, 7 Sep 2016 12:32:58
   +0530 from [155.78.86.25] ----- The following addresses had permanent fatal
   errors ----- <linux-nvdimm-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org> ----- Transcript of session follows
   ----- ... while talking to 178.149.45.141: 554 <linux-nvdimm-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org>...
   Mail quota exceeded 554 <linux-nvdimm-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org>... Service unavailable
   [...] 

Content analysis details:   (5.2 points, 5.0 required)

 pts rule name              description
---- ---------------------- --------------------------------------------------
 0.0 URIBL_BLOCKED          ADMINISTRATOR NOTICE: The query to URIBL was blocked.
                            See
                            http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block
                             for more information.
                            [URIs: 01.org]
 0.8 RCVD_IN_SORBS_WEB      RBL: SORBS: sender is an abusable web server
                            [103.204.166.162 listed in dnsbl.sorbs.net]
-0.0 RCVD_IN_DNSWL_NONE     RBL: Sender listed at http://www.dnswl.org/, no
                            trust
                            [198.145.21.10 listed in list.dnswl.org]
 0.1 RCVD_IN_SBL            RBL: Received via a relay in Spamhaus SBL
                            [103.204.166.162 listed in zen.spamhaus.org]
-0.6 RP_MATCHES_RCVD        Envelope sender domain matches handover relay domain
-1.9 BAYES_00               BODY: Bayes spam probability is 0 to 1%
                            [score: 0.0053]
 2.2 AXB_XMAILER_MIMEOLE_OL_024C2 No description available.
 2.6 MSOE_MID_WRONG_CASE    No description available.
 1.9 FORGED_MUA_OUTLOOK     Forged mail pretending to be from MS Outlook



[-- Attachment #2: original message before SpamAssassin --]
[-- Type: message/rfc822, Size: 2933 bytes --]

From: "MAILER-DAEMON" <MAILER-DAEMON-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org>
To: linux-nvdimm-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org
Subject: Error
Date: Wed, 7 Sep 2016 12:32:58 +0530
Message-ID: <20160907070317.200A01A1E55-y27Ovi1pjclAfugRpC6u6w@public.gmane.org>

The original message was received at Wed, 7 Sep 2016 12:32:58 +0530
from [155.78.86.25]

----- The following addresses had permanent fatal errors -----
<linux-nvdimm-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org>

----- Transcript of session follows -----
... while talking to 178.149.45.141:
554 <linux-nvdimm-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org>... Mail quota exceeded
554 <linux-nvdimm-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org>... Service unavailable

_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org
https://lists.01.org/mailman/listinfo/linux-nvdimm

Error

[live]

The original message was received at Fri, 26 Aug 2016 12:39:58 +0530 from 40.160.8.253

----- The following addresses had permanent fatal errors -----
linux-nvdimm@lists.01.org

----- Transcript of session follows -----
... while talking to server lists.01.org.:
>>> MAIL FROM:live@lapin.com
<<< 505 live@lapin.com... Refused

_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm

Error

[live-CLLoK8F55wEAvxtiuMwx3w]

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

Spam detection software, running on the system "blaine.gmane.org",
has identified this incoming email as possible spam.  The original
message has been attached to this so you can view it or label
similar future email.  If you have any questions, see
@@CONTACT_ADDRESS@@ for details.

Content preview:  The original message was received at Fri, 26 Aug 2016 12:39:58
   +0530 from 40.160.8.253 ----- The following addresses had permanent fatal
   errors ----- linux-nvdimm-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org ----- Transcript of session follows
   ----- ... while talking to server lists.01.org.: >>> MAIL FROM:live-CLLoK8F55wEAvxtiuMwx3w@public.gmane.org
   <<< 505 live-CLLoK8F55wFUi4FbrNnSJA@public.gmane.org Refused [...] 

Content analysis details:   (6.4 points, 5.0 required)

 pts rule name              description
---- ---------------------- --------------------------------------------------
 0.0 URIBL_BLOCKED          ADMINISTRATOR NOTICE: The query to URIBL was blocked.
                            See
                            http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block
                             for more information.
                            [URIs: 01.org]
 0.8 RCVD_IN_SORBS_WEB      RBL: SORBS: sender is an abusable web server
                            [103.204.166.162 listed in dnsbl.sorbs.net]
-0.0 RCVD_IN_DNSWL_NONE     RBL: Sender listed at http://www.dnswl.org/, no
                            trust
                            [198.145.21.10 listed in list.dnswl.org]
-0.6 RP_MATCHES_RCVD        Envelope sender domain matches handover relay domain
 0.0 T_HEADER_FROM_DIFFERENT_DOMAINS From and EnvelopeFrom 2nd level mail
                            domains are different
-0.5 BAYES_05               BODY: Bayes spam probability is 1 to 5%
                            [score: 0.0172]
 2.2 AXB_XMAILER_MIMEOLE_OL_024C2 No description available.
 2.6 MSOE_MID_WRONG_CASE    No description available.
 1.9 FORGED_MUA_OUTLOOK     Forged mail pretending to be from MS Outlook



[-- Attachment #2: original message before SpamAssassin --]
[-- Type: message/rfc822, Size: 2863 bytes --]

From: live-CLLoK8F55wEAvxtiuMwx3w@public.gmane.org
To: linux-nvdimm-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org
Subject: Error
Date: Fri, 26 Aug 2016 12:39:58 +0530
Message-ID: <20160826071047.C5BCD1A1DFE-y27Ovi1pjclAfugRpC6u6w@public.gmane.org>

The original message was received at Fri, 26 Aug 2016 12:39:58 +0530 from 40.160.8.253

----- The following addresses had permanent fatal errors -----
linux-nvdimm-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org

----- Transcript of session follows -----
... while talking to server lists.01.org.:
>>> MAIL FROM:live-CLLoK8F55wEAvxtiuMwx3w@public.gmane.org
<<< 505 live-CLLoK8F55wFUi4FbrNnSJA@public.gmane.org Refused

_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org
https://lists.01.org/mailman/listinfo/linux-nvdimm

error

[Returned mail]

Message could not be delivered

_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm

error

[Returned mail]

Message could not be delivered

Error

[Daniel Pavel]

Hello, I am new to Yocto and trying to build an Image for Pandaboard 
using this guy's guidelines :

http://maniacbug.wordpress.com/2012/08/03/pandayocto/

and encountered the following error when building. Here's my log :

NOTE: make -j 4
   2 Making all in lib
   3 make[1]: Entering directory 
`/home/daniel/Karanka-ntfs3g/yocto/poky-denzil-7.0/poky-denzil-7.0-build/tmp/work/x86_64-linux/automake-native-1.11.2-r3/automake-1.11.2/lib'
   4 cd .. && make  am--refresh
   5 make[2]: Entering directory 
`/home/daniel/Karanka-ntfs3g/yocto/poky-denzil-7.0/poky-denzil-7.0-build/tmp/work/x86_64-linux/automake-native-1.11.2-r3/automake-1.11.2'
   6 make[2]: Leaving directory 
`/home/daniel/Karanka-ntfs3g/yocto/poky-denzil-7.0/poky-denzil-7.0-build/tmp/work/x86_64-linux/automake-native-1.11.2-r3/automake-1.11.2'
   7 cd .. && make  am--refresh
   8 make[2]: Entering directory 
`/home/daniel/Karanka-ntfs3g/yocto/poky-denzil-7.0/poky-denzil-7.0-build/tmp/work/x86_64-linux/automake-native-1.11.2-r3/automake-1.11.2'
   9 make[2]: Entering directory 
`/home/daniel/Karanka-ntfs3g/yocto/poky-denzil-7.0/poky-denzil-7.0-build/tmp/work/x86_64-linux/automake-native-1.11.2-r3/automake-1.11.2'
  10 make[2]: Leaving directory 
`/home/daniel/Karanka-ntfs3g/yocto/poky-denzil-7.0/poky-denzil-7.0-build/tmp/work/x86_64-linux/automake-native-1.11.2-r3/automake-1.11.2'
  11 make[2]: Leaving directory 
`/home/daniel/Karanka-ntfs3g/yocto/poky-denzil-7.0/poky-denzil-7.0-build/tmp/work/x86_64-linux/automake-native-1.11.2-r3/automake-1.11.2'
  12 Making all in Automake
  13 make[2]: Entering directory 
`/home/daniel/Karanka-ntfs3g/yocto/poky-denzil-7.0/poky-denzil-7.0-build/tmp/work/x86_64-linux/automake-native-1.11.2-r3/automake-1.11.2/lib/Automake'
  14 cd ../.. && make  am--refresh
  15 make[3]: Entering directory 
`/home/daniel/Karanka-ntfs3g/yocto/poky-denzil-7.0/poky-denzil-7.0-build/tmp/work/x86_64-linux/automake-native-1.11.2-r3/automake-1.11.2'
  16 make[3]: Leaving directory 
`/home/daniel/Karanka-ntfs3g/yocto/poky-denzil-7.0/poky-denzil-7.0-build/tmp/work/x86_64-linux/automake-native-1.11.2-r3/automake-1.11.2'
  17 cd ../.. && make  am--refresh
  18 make[3]: Entering directory 
`/home/daniel/Karanka-ntfs3g/yocto/poky-denzil-7.0/poky-denzil-7.0-build/tmp/work/x86_64-linux/automake-native-1.11.2-r3/automake-1.11.2'
  19 make[3]: Entering directory 
`/home/daniel/Karanka-ntfs3g/yocto/poky-denzil-7.0/poky-denzil-7.0-build/tmp/work/x86_64-linux/automake-native-1.11.2-r3/automake-1.11.2'
  20 make[3]: Leaving directory 
`/home/daniel/Karanka-ntfs3g/yocto/poky-denzil-7.0/poky-denzil-7.0-build/tmp/work/x86_64-linux/automake-native-1.11.2-r3/automake-1.11.2'
  21 make[3]: Leaving directory 
`/home/daniel/Karanka-ntfs3g/yocto/poky-denzil-7.0/poky-denzil-7.0-build/tmp/work/x86_64-linux/automake-native-1.11.2-r3/automake-1.11.2'
  22 Making all in .
  23 make[3]: Entering directory 
`/home/daniel/Karanka-ntfs3g/yocto/poky-denzil-7.0/poky-denzil-7.0-build/tmp/work/x86_64-linux/automake-native-1.11.2-r3/automake-1.11.2/lib/Automake'
  24 cd ../.. && make  am--refresh
  25 make[4]: Entering directory 
`/home/daniel/Karanka-ntfs3g/yocto/poky-denzil-7.0/poky-denzil-7.0-build/tmp/work/x86_64-linux/automake-native-1.11.2-r3/automake-1.11.2'
  26 make[4]: Leaving directory 
`/home/daniel/Karanka-ntfs3g/yocto/poky-denzil-7.0/poky-denzil-7.0-build/tmp/work/x86_64-linux/automake-native-1.11.2-r3/automake-1.11.2'
  27 cd ../.. && make  am--refresh
  28 make[4]: Entering directory 
`/home/daniel/Karanka-ntfs3g/yocto/poky-denzil-7.0/poky-denzil-7.0-build/tmp/work/x86_64-linux/automake-native-1.11.2-r3/automake-1.11.2'
  29 make[4]: Entering directory 
`/home/daniel/Karanka-ntfs3g/yocto/poky-denzil-7.0/poky-denzil-7.0-build/tmp/work/x86_64-linux/automake-native-1.11.2-r3/automake-1.11.2'
  30 make[4]: Leaving directory 
`/home/daniel/Karanka-ntfs3g/yocto/poky-denzil-7.0/poky-denzil-7.0-build/tmp/work/x86_64-linux/automake-native-1.11.2-r3/automake-1.11.2'
  31 make[4]: Leaving directory 
`/home/daniel/Karanka-ntfs3g/yocto/poky-denzil-7.0/poky-denzil-7.0-build/tmp/work/x86_64-linux/automake-native-1.11.2-r3/automake-1.11.2'
  32 rm -f Config.tmp Config.pm
  33 in=`echo Config.pm | sed 's/\.[^.]*$//'`; sed -e 
's,[@]APIVERSION[@],1.11,g' -e 's,[@]PACKAGE[@],automake,g' -e 
's,[@]PACKAGE_BUGREPORT[@],bug-automake@gnu.org,g' -e 
's,[@]PERL[@],/usr/bin/perl,g' -e 's    ,[@]PERL_THREADS[@],1,g' -e 
's,[@]SHELL[@],/bin/bash,g' -e 's,[@]VERSION[@],1.11.2,g' -e 
"s,[@]configure_input[@],Generated from $in.in; do not edit by hand.,g" 
-e 's,[@]datadir[@],/home/daniel/Karanka- 
ntfs3g/yocto/poky-denzil-7.0/poky-denzil-7.0-build/tmp/sysroots/x86_64-linux/usr/share,g' 
./Config.in >Config.tmp
  34 chmod +x Config.tmp
  35 chmod a-w Config.tmp
  36 mv -f Config.tmp Config.pm
  37 make[3]: Leaving directory 
`/home/daniel/Karanka-ntfs3g/yocto/poky-denzil-7.0/poky-denzil-7.0-build/tmp/work/x86_64-linux/automake-native-1.11.2-r3/automake-1.11.2/lib/Automake'
  38 Making all in tests
  39 make[3]: Entering directory 
`/home/daniel/Karanka-ntfs3g/yocto/poky-denzil-7.0/poky-denzil-7.0-build/tmp/work/x86_64-linux/automake-native-1.11.2-r3/automake-1.11.2/lib/Automake/tests'
  40 cd ../../.. && make  am--refresh
  41 make[4]: Entering directory 
`/home/daniel/Karanka-ntfs3g/yocto/poky-denzil-7.0/poky-denzil-7.0-build/tmp/work/x86_64-linux/automake-native-1.11.2-r3/automake-1.11.2'
  42 make[4]: Leaving directory 
`/home/daniel/Karanka-ntfs3g/yocto/poky-denzil-7.0/poky-denzil-7.0-build/tmp/work/x86_64-linux/automake-native-1.11.2-r3/automake-1.11.2'
  43 cd ../../.. && make  am--refresh
  44 make[4]: Entering directory 
`/home/daniel/Karanka-ntfs3g/yocto/poky-denzil-7.0/poky-denzil-7.0-build/tmp/work/x86_64-linux/automake-native-1.11.2-r3/automake-1.11.2'
  45 make[4]: Entering directory 
`/home/daniel/Karanka-ntfs3g/yocto/poky-denzil-7.0/poky-denzil-7.0-build/tmp/work/x86_64-linux/automake-native-1.11.2-r3/automake-1.11.2'
  46 make[4]: Leaving directory 
`/home/daniel/Karanka-ntfs3g/yocto/poky-denzil-7.0/poky-denzil-7.0-build/tmp/work/x86_64-linux/automake-native-1.11.2-r3/automake-1.11.2'
  47 make[4]: Leaving directory 
`/home/daniel/Karanka-ntfs3g/yocto/poky-denzil-7.0/poky-denzil-7.0-build/tmp/work/x86_64-linux/automake-native-1.11.2-r3/automake-1.11.2'
  48 make[3]: Nothing to be done for `all'.
  49 make[3]: Leaving directory 
`/home/daniel/Karanka-ntfs3g/yocto/poky-denzil-7.0/poky-denzil-7.0-build/tmp/work/x86_64-linux/automake-native-1.11.2-r3/automake-1.11.2/lib/Automake/tests'
  50 make[2]: Leaving directory 
`/home/daniel/Karanka-ntfs3g/yocto/poky-denzil-7.0/poky-denzil-7.0-build/tmp/work/x86_64-linux/automake-native-1.11.2-r3/automake-1.11.2/lib/Automake'
  51 Making all in am
  52 make[2]: Entering directory 
`/home/daniel/Karanka-ntfs3g/yocto/poky-denzil-7.0/poky-denzil-7.0-build/tmp/work/x86_64-linux/automake-native-1.11.2-r3/automake-1.11.2/lib/am'
  53 cd ../.. && make  am--refresh
make[3]: Entering directory 
`/home/daniel/Karanka-ntfs3g/yocto/poky-denzil-7.0/poky-denzil-7.0-build/tmp/work/x86_64-linux/automake-native-1.11.2-r3/automake-1.11.2'
  55 make[3]: Leaving directory 
`/home/daniel/Karanka-ntfs3g/yocto/poky-denzil-7.0/poky-denzil-7.0-build/tmp/work/x86_64-linux/automake-native-1.11.2-r3/automake-1.11.2'
  56 cd ../.. && make  am--refresh
  57 make[3]: Entering directory 
`/home/daniel/Karanka-ntfs3g/yocto/poky-denzil-7.0/poky-denzil-7.0-build/tmp/work/x86_64-linux/automake-native-1.11.2-r3/automake-1.11.2'
  58 make[3]: Entering directory 
`/home/daniel/Karanka-ntfs3g/yocto/poky-denzil-7.0/poky-denzil-7.0-build/tmp/work/x86_64-linux/automake-native-1.11.2-r3/automake-1.11.2'
  59 make[3]: Leaving directory 
`/home/daniel/Karanka-ntfs3g/yocto/poky-denzil-7.0/poky-denzil-7.0-build/tmp/work/x86_64-linux/automake-native-1.11.2-r3/automake-1.11.2'
  60 make[3]: Leaving directory 
`/home/daniel/Karanka-ntfs3g/yocto/poky-denzil-7.0/poky-denzil-7.0-build/tmp/work/x86_64-linux/automake-native-1.11.2-r3/automake-1.11.2'
  61 make[2]: Nothing to be done for `all'.
  62 make[2]: Leaving directory 
`/home/daniel/Karanka-ntfs3g/yocto/poky-denzil-7.0/poky-denzil-7.0-build/tmp/work/x86_64-linux/automake-native-1.11.2-r3/automake-1.11.2/lib/am'
  63 make[2]: Entering directory 
`/home/daniel/Karanka-ntfs3g/yocto/poky-denzil-7.0/poky-denzil-7.0-build/tmp/work/x86_64-linux/automake-native-1.11.2-r3/automake-1.11.2/lib'
  64 cd .. && make  am--refresh
  65 make[3]: Entering directory 
`/home/daniel/Karanka-ntfs3g/yocto/poky-denzil-7.0/poky-denzil-7.0-build/tmp/work/x86_64-linux/automake-native-1.11.2-r3/automake-1.11.2'
  66 make[3]: Leaving directory 
`/home/daniel/Karanka-ntfs3g/yocto/poky-denzil-7.0/poky-denzil-7.0-build/tmp/work/x86_64-linux/automake-native-1.11.2-r3/automake-1.11.2'
  67 cd .. && make  am--refresh
  68 make[3]: Entering directory 
`/home/daniel/Karanka-ntfs3g/yocto/poky-denzil-7.0/poky-denzil-7.0-build/tmp/work/x86_64-linux/automake-native-1.11.2-r3/automake-1.11.2'
  69 make[3]: Entering directory 
`/home/daniel/Karanka-ntfs3g/yocto/poky-denzil-7.0/poky-denzil-7.0-build/tmp/work/x86_64-linux/automake-native-1.11.2-r3/automake-1.11.2'
  70 make[3]: Leaving directory 
`/home/daniel/Karanka-ntfs3g/yocto/poky-denzil-7.0/poky-denzil-7.0-build/tmp/work/x86_64-linux/automake-native-1.11.2-r3/automake-1.11.2'
  71 make[3]: Leaving directory 
`/home/daniel/Karanka-ntfs3g/yocto/poky-denzil-7.0/poky-denzil-7.0-build/tmp/work/x86_64-linux/automake-native-1.11.2-r3/automake-1.11.2'
  72 make[2]: Nothing to be done for `all-am'.
  73 make[2]: Leaving directory 
`/home/daniel/Karanka-ntfs3g/yocto/poky-denzil-7.0/poky-denzil-7.0-build/tmp/work/x86_64-linux/automake-native-1.11.2-r3/automake-1.11.2/lib'
  74 make[1]: Leaving directory 
`/home/daniel/Karanka-ntfs3g/yocto/poky-denzil-7.0/poky-denzil-7.0-build/tmp/work/x86_64-linux/automake-native-1.11.2-r3/automake-1.11.2/lib'
  75 Making all in .
  76 make[1]: Entering directory 
`/home/daniel/Karanka-ntfs3g/yocto/poky-denzil-7.0/poky-denzil-7.0-build/tmp/work/x86_64-linux/automake-native-1.11.2-r3/automake-1.11.2'
  77 rm -f automake automake.tmp
  78 rm -f aclocal aclocal.tmp
  79 sed -e 's,[@]APIVERSION[@],1.11,g' -e 's,[@]PACKAGE[@],automake,g' 
-e 's,[@]PACKAGE_BUGREPORT[@],bug-automake@gnu.org,g' -e 
's,[@]PACKAGE_URL[@],http://www.gnu.org/software/automake/,g' -e 
's,[@]PATH_SE    PARATOR[@],:,g' -e 's,[@]PERL[@],/usr/bin/perl,g' -e 
's,[@]PERL_THREADS[@],1,g' -e 's,[@]SHELL[@],/bin/bash,g' -e 
's,[@]am_AUTOCONF[@],autoconf,g' -e 's,[@]am_AUTOM4TE[@],autom4te,g' -e 
's,[@]VERSION[@]    ,1.11.2,g' -e 's,[@]configure_input[@],Generated 
from automake.in; do not edit by hand.,g' -e 
's,[@]datadir[@],/home/daniel/Karanka-ntfs3g/yocto/poky-denzil-7.0/poky-denzil-7.0-build/tmp/sysroots/x86_64 
-linux/usr/share,g' ./automake.in >automake.tmp
  80 sed -e 's,[@]APIVERSION[@],1.11,g' -e 's,[@]PACKAGE[@],automake,g' 
-e 's,[@]PACKAGE_BUGREPORT[@],bug-automake@gnu.org,g' -e 
's,[@]PACKAGE_URL[@],http://www.gnu.org/software/automake/,g' -e 
's,[@]PATH_SE    PARATOR[@],:,g' -e 's,[@]PERL[@],/usr/bin/perl,g' -e 
's,[@]PERL_THREADS[@],1,g' -e 's,[@]SHELL[@],/bin/bash,g' -e 
's,[@]am_AUTOCONF[@],autoconf,g' -e 's,[@]am_AUTOM4TE[@],autom4te,g' -e 
's,[@]VERSION[@]    ,1.11.2,g' -e 's,[@]configure_input[@],Generated 
from aclocal.in; do not edit by hand.,g' -e 
's,[@]datadir[@],/home/daniel/Karanka-ntfs3g/yocto/poky-denzil-7.0/poky-denzil-7.0-build/tmp/sysroots/x86_64- 
linux/usr/share,g' ./aclocal.in >aclocal.tmp
  81 chmod +x aclocal.tmp
  82 chmod a-w aclocal.tmp
  83 mv -f aclocal.tmp aclocal
  84 chmod +x automake.tmp
  85 chmod a-w automake.tmp
  86 mv -f automake.tmp automake
  87 make[1]: Leaving directory 
`/home/daniel/Karanka-ntfs3g/yocto/poky-denzil-7.0/poky-denzil-7.0-build/tmp/work/x86_64-linux/automake-native-1.11.2-r3/automake-1.11.2'
  88 Making all in doc
  89 make[1]: Entering directory 
`/home/daniel/Karanka-ntfs3g/yocto/poky-denzil-7.0/poky-denzil-7.0-build/tmp/work/x86_64-linux/automake-native-1.11.2-r3/automake-1.11.2/doc'
  90 cd .. && make  am--refresh
  91 make[2]: Entering directory 
`/home/daniel/Karanka-ntfs3g/yocto/poky-denzil-7.0/poky-denzil-7.0-build/tmp/work/x86_64-linux/automake-native-1.11.2-r3/automake-1.11.2'
  92 make[2]: Leaving directory 
`/home/daniel/Karanka-ntfs3g/yocto/poky-denzil-7.0/poky-denzil-7.0-build/tmp/work/x86_64-linux/automake-native-1.11.2-r3/automake-1.11.2'
  93 cd .. && make  am--refresh
  94 make[2]: Entering directory 
`/home/daniel/Karanka-ntfs3g/yocto/poky-denzil-7.0/poky-denzil-7.0-build/tmp/work/x86_64-linux/automake-native-1.11.2-r3/automake-1.11.2'
  95 make[2]: Entering directory 
`/home/daniel/Karanka-ntfs3g/yocto/poky-denzil-7.0/poky-denzil-7.0-build/tmp/work/x86_64-linux/automake-native-1.11.2-r3/automake-1.11.2'
  96 make[2]: Leaving directory 
`/home/daniel/Karanka-ntfs3g/yocto/poky-denzil-7.0/poky-denzil-7.0-build/tmp/work/x86_64-linux/automake-native-1.11.2-r3/automake-1.11.2'
make[2]: Leaving directory 
`/home/daniel/Karanka-ntfs3g/yocto/poky-denzil-7.0/poky-denzil-7.0-build/tmp/work/ERROR: 
Function failed: do_compile (see 
/home/daniel/Karanka-ntfs3g/yocto/poky-denzil-7.0/pok 
y-denzil-7.0-build/tmp/work/x86_64-linux/automake-native-1.11.2-r3/temp/log.do_compile.17789 
for further information)
  98 x86_64-linux/automake-native-1.11.2-r3/automake-1.11.2'
  99 PATH="`pwd`/../tests:$PATH" && export PATH && /bin/bash 
/home/daniel/Karanka-ntfs3g/yocto/poky-denzil-7.0/poky-denzil-7.0-build/tmp/work/x86_64-linux/automake-native-1.11.2-r3/automake-1.11.2/lib/missin 
g --run help2man --output=automake-1.11.1 automake-1.11
100 WARNING: `help2man' is missing on your system.  You should only need 
it if
101          you modified a dependency of a manual page.  You may need the
102          `Help2man' package in order for those modifications to take
103          effect.  You can get `Help2man' from any GNU archive site.
104 Updating ./version.texi
105 restore=: && backupdir=".am$$" && \
106         am__cwd=`pwd` && CDPATH="${ZSH_VERSION+.}:" && cd . && \
107         rm -rf $backupdir && mkdir $backupdir && \
108         if (/bin/bash 
/home/daniel/Karanka-ntfs3g/yocto/poky-denzil-7.0/poky-denzil-7.0-build/tmp/work/x86_64-linux/automake-native-1.11.2-r3/automake-1.11.2/lib/missing 
--run makeinfo --version) >/dev/    null 2>&1; then \
109           for f in automake.info automake.info-[0-9] 
automake.info-[0-9][0-9] automake.i[0-9] automake.i[0-9][0-9]; do \
110             if test -f $f; then mv $f $backupdir; restore=mv; else 
:; fi; \
111           done; \
112         else :; fi && \
113         cd "$am__cwd"; \
114         if /bin/bash 
/home/daniel/Karanka-ntfs3g/yocto/poky-denzil-7.0/poky-denzil-7.0-build/tmp/work/x86_64-linux/automake-native-1.11.2-r3/automake-1.11.2/lib/missing 
--run makeinfo   -I . \
115          -o automake.info automake.texi; \
116         then \
117           rc=0; \
118           CDPATH="${ZSH_VERSION+.}:" && cd .; \
119         else \
120           rc=$?; \
121           CDPATH="${ZSH_VERSION+.}:" && cd . && \
122           $restore $backupdir/* `echo "./automake.info" | sed 
's|[^/]*$||'`; \
123         fi; \
124         rm -rf $backupdir; exit $rc
125 automake.texi:13043: @itemx must follow @item
126 automake.texi:13060: @itemx must follow @item
127 automake.texi:13066: @itemx must follow @item
128 make[1]: *** [automake.info] Error 1
129 make[1]: Leaving directory 
`/home/daniel/Karanka-ntfs3g/yocto/poky-denzil-7.0/poky-denzil-7.0-build/tmp/work/x86_64-linux/automake-native-1.11.2-r3/automake-1.11.2/doc'
130 make: *** [all-recursive] Error 1
131 ERROR: oe_runmake failed


Googled a bit about this error and found something that looks fairly 
similar :

https://www.dream-multimedia-tv.de/board/index.php?page=Thread&threadID=18118

However I don't know how to configure the particular package.

Can you guys help me ?
Thank you in advance.

Error

[Himanshu Pandey]

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

Hi,
I am constantly getting these errors while compiling my net-snmp receipe. Please find my receipe below.
ERROR: QA Issue: non -staticdev package contains static .a library: net-snmp path '/work/x86_64-poky-linux/net-snmp/1.0-r8/packages-split/net-snmp/opt/net-snmp/lib/libnetsnmpagent.a'ERROR: QA Issue: non -dev/-dbg/-nativesdk package contains symlink .so: net-snmp path '/work/x86_64-poky-linux/net-snmp/1.0-r8/packages-split/net-snmp/opt/net-snmp/lib/libnetsnmp.so'ERROR: QA Issue: non -staticdev package contains static .a library: net-snmp path '/work/x86_64-poky-linux/net-snmp/1.0-r8/packages-split/net-snmp/opt/net-snmp/lib/libnetsnmptrapd.a'ERROR: QA Issue: non -dev/-dbg/-nativesdk package contains symlink .so: net-snmp path '/work/x86_64-poky-linux/net-snmp/1.0-r8/packages-split/net-snmp/opt/net-snmp/lib/libnetsnmptrapd.so'ERROR: QA Issue: non -staticdev package contains static .a library: net-snmp path '/work/x86_64-poky-linux/net-snmp/1.0-r8/packages-split/net-snmp/opt/net-snmp/lib/libnetsnmphelpers.a'ERROR: QA Issue: non -staticdev package contains static .a library: net-s
 nmp path '/work/x86_64-poky-linux/net-snmp/1.0-r8/packages-split/net-snmp/opt/net-snmp/lib/libnetsnmpmibs.a'ERROR: QA Issue: non -dev/-dbg/-nativesdk package contains symlink .so: net-snmp path '/work/x86_64-poky-linux/net-snmp/1.0-r8/packages-split/net-snmp/opt/net-snmp/lib/libnetsnmpagent.so'ERROR: QA Issue: non -dev/-dbg/-nativesdk package contains symlink .so: net-snmp path '/work/x86_64-poky-linux/net-snmp/1.0-r8/packages-split/net-snmp/opt/net-snmp/lib/libnetsnmphelpers.so'ERROR: QA Issue: non -dev/-dbg/-nativesdk package contains symlink .so: net-snmp path '/work/x86_64-poky-linux/net-snmp/1.0-r8/packages-split/net-snmp/opt/net-snmp/lib/libnetsnmpmibs.so'ERROR: QA Issue: non -staticdev package contains static .a library: net-snmp path '/work/x86_64-poky-linux/net-snmp/1.0-r8/packages-split/net-snmp/opt/net-snmp/lib/libnetsnmp.a'ERROR: QA run found fatal errors. Please consider fixing them.ERROR: Function failed: do_package_qaERROR: Logfile of failure stored in: /home/
 yocto/poky-dora-10.0.0/build/tmp/work/x86_64-poky-linux/net-snmp/1.0-r8/temp/log.do_package.9029ERROR: Task 727 (/home/yocto/poky-dora-10.0.0/meta-msc/recipes-msc/msc/net-snmp.bb, do_package) failed with exit code '1'
My receipe is as follows:
SUMMARY = "Simple Network Management Protocol"HOMEPAGE = "http://www.net-snmp.org/"LICENSE = "CLOSED"PR = "r8"DEPENDS = "openssl libnl pciutils"INHIBIT_PACKAGE_DEBUG_SPLIT = "1"INHIBIT_PACKAGE_STRIP = "1"ALLOW_EMPTY_${PN} = "1"INSANE_SKIP_{PN} = "dev-so"SRC_URI = "http://jaist.dl.sourceforge.net/project/net-snmp/net-snmp/5.7.2.1/net-snmp-5.7.2.1.zip"
SRC_URI[md5sum] = "a2c83518648b0f2a5d378625e45c0e18"SRC_URI[sha256sum] = "ac9105539971f7cfb1456a86d479e18e8a8b3712212595ad40504347ba5843da"
S = "${WORKDIR}/net-snmp-5.7.2.1"inherit autotools
LDFLAGS= "-L/home/yocto/poky-dora-10.0.0/build/tmp/work/genericx86_64-poky-linux/core-image-msc/1.0-r0/rootfs/lib/"
do_configure() {
./configure --build=x86_64-linux --host=x86_64-poky-linux --target=x86_64-poky-linux --prefix=$(D)/opt/net-snmp --exec_prefix=$(D)/opt/net-snmp --bindir=$(D)/opt/net-snmp/bin --sbindir=$(D)/opt/net-snmp/sbin --libexecdir=$(D)/opt/net-snmp/lib/ --datadir=$(D)/opt/net-snmp/share --sysconfdir=$(D)/opt/net-snmp/etc --sharedstatedir=$(D)/com --localstatedir=$(D)/opt/net-snmp/var --libdir=$(D)/opt/net-snmp/lib --mandir=$(D)/opt/net-snmp/share/man --disable-embedded-perl --with-perl-modules=no --disable-manuals --enable-shared         oe_runmake}
PACKAGES = "${PN} ${PN}-dbg ${PN}-doc ${PN}-dev ${PN}-staticdev ${PN}-static"FILES_${PN}-dev += "/opt/net-snmp/lib/ ${includedir}"FILES_${PN}-dbg += "/opt/net-snmp/lib/"FILES_${PN} += "/opt/net-snmp/"FILES_${PN}-staticdev += "/opt/net-snmp/lib/"FILES_${PN}-static += "/opt/net-snmp/lib/"BBCLASSEXTEND = "native"
Please help to resolve the issue.
Thanks & Regards,Himanshu Pandey 

[-- Attachment #2: Type: text/html, Size: 6408 bytes --]

Error

[Himanshu Pandey]

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

Hi, 

I am getting this error when I run bitbake command:

Error: busybox not found in the base feeds (genericx86_64 x86_64 noarch any all).   

How to resolve this?

Regards,
Himanshu


[-- Attachment #2: Type: text/html, Size: 2001 bytes --]

Re: Error

[Konstantin Khomoutov]

On Tue, 9 Jul 2013 20:30:37 -0500
Chanakya Vattikuti <gk2cveragon1@gmail.com> wrote:

> I get this error message when trying to create a shared ssh key in
> Mac osx Lion

This problem has nothing to do with Git as it purely is about
transferring a public part of your SSH key to another host.
So try asking on the OS support channels.

> scp .ssh/id_rsa.pub cvattiku@cook.cs.uno.edu:~/
> ssh_exchange_identification: Connection closed by remote host
> lost connection

Since the public part of your key is not transferred to that remote host
yet, and it is not registered as a trusted key there, you have to use
an SSH authentication method other than "publickey".  Or, if you have
another SSH key which is registered as trusted on the remote host, you
might try to use it explicitly using the "-i <private_key_file_>"
command-line option to `scp`.

If this fails or not applicable, at least try to run `scp` with
multiple "-v" command-line options (like `scp -vvvv ...`) to get
extensive details about authentication protocols it tried with the
server and which of them were agreed upon by both sides and tried.

It might turn out that the server only accepts publickey authentication
mechanism, and so you are not able to upload and register your public
key yourself (chicken and egg problem).  In that case, contact the
server's system administrator for assistance.

If the server has certain "Git hosting" solution like Gitlab, you might
need to try registering your key using some other means like logging to
your Git account via some web interface and pasting the key there --
just like you'd do this on github.

If studying that information won't help you, provide it when you will
be asking this question on the Mac OS support channels.

Error

[Chanakya Vattikuti]

I get this error message when trying to create a shared ssh key in Mac osx Lion

scp .ssh/id_rsa.pub cvattiku@cook.cs.uno.edu:~/
ssh_exchange_identification: Connection closed by remote host
lost connection

RE: error

[Paul Amodio]

ERROR

[eokerson]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="Windows-1252", Size: 1483 bytes --]

““ŽÙÌP‡i›#Aç_ë¬8ÎNRÈÎÉ꣰È"©vÕ.µ23DýˆÜ>X2{¡cßTŽÉk1*Òø—E«à>ȇJ­©Ò‹ïÌ£ˆ«î'‘l”v}P#›áŽßM.U{®"á¹¢0y›¸‘Ù™80…P)L
ùyEöTYU¼?Ÿ´¢8à´Œ*˺ÑÖ>»OÐØlMÕE6'Ì][‚l²…•òbo̺…˜è!ŠßŒuä•_ÈR<ѵ¦§“ŽÊ’©Yº³Z¤¤‚î!ê{ïÀ§žúÒ:ðo¦ø•ïušyuá|[>ç›ÏNté>ý{æKGœç$ËŸ”KüIU<™l-°ÈÎZ•±
!»sŸCPIÏîï4Ùó~a—ÂÚë·‘q}zÙdºÏB†ˆà™eÖoµ?æÉŽò%Ýu°ýMÓP·Iy;Uìï-Èä~;OÏÎiNYïêµ- {ëÑß MH- ú™Î’Žm'ï
÷³&Ý*Åa«mȾ…]ÞõæÖQ˜ë8›øe³ËPF®UNÆ>DH"\g;fÏFrœS,r¦¹ý¡˜åŽÑâ¿x
C“û½làµ-óyz4HOvÁÓñ‰Sò
·`œtRWÙЦómôÂ&¹*áj¬
šcQÐX-4MñLe›>¬¡úÊü7˜k!ÑN(aýÀ¨-
êqÙn-ƒ}µÅ½‹•Ÿ…¼%ž—¸ñ˜X [‘Švw„]ŽaUýÐ( a’ï5¦‡³[Ðè7'©CLüÆÁµË‡½¡Š>”I8¿÷žAK먐ÛÖiŸúro(&ÛŒDMXË>µ“‘M3ëv~«yzPÞ aÓ«PJâÀçÓº8¡{QåÝ
¬~¸³¶TÅÔ
e֝ólÊsJá<žva/†V*:¢™ÚÐÁu8Vfñ^1õkÝ™-KT¾ÛH¼×
H7ÏSJUGD"$ƒa!0ÅöT‡«ÅÏÆgA,HoýdÇ /’.ÔFÃHÕ¥ÃM%›Ü!²%
ËkÊ–i•÷†ë¼8¶¹–5pC™Ž:F¹ý³jÀL¾X¸ŽïÀ¼nÄXådò~„[!ÌÅÆðRXÚÍ´líÙ­&׺i/RÏ&C71*^q.ÍÅ‘ýÁ§j2&µUÚä6I‚Ë…Õ"ÁiÒŠÚ|¹ðÝŽv.Hãŵ`ã>Tte\13cS5-xß9u»ôс>É(ÞŒlCœ¢Ó'qû0;Щ]“Õ*žš\çÓ.kÏ›
ý~ò-šB¹µ1l-íä¢z
óԐlmîíÄtC Âm‘LÞ4éyídI6ͦ!/áxâ´8<˜¡Ðö$ÀѯÃì_Œmòþ¡_cO¤þ˜Ð¨q#,ä6Yí>¿úA9ªÕEJ¢°ãô.ÐWwˆŽ±Ìpîi!ÝÝ̧Áä“d§à·iä¼ø'ä9È•_³™nÄ Ö´B“§Y¤a^¹„‰¤×g¥-¸é‹>ŽÛ¤ƒœƒøUû¹‘?óEWzŒ~éü0yù\`?îuÆÜä«àµqAŒú“ŒJk9L0NÌdÊÙ溾žãoZà‹¼tyœhý}4^lz§©ÌˆüK±äë-…Cœ^ž0óy
ïb¤%2,lÇ,
9O.‡ã
!i¤YÈw¦’a½u›*•üñþ9[ê‡IŒ³ÅpÝOŽƒš½‹¦ñ´FöQÞ¤6”|žtÍÇ
É_ƒÔm³ežŒ[s®|·©ÆP:_vøì_iò聊nÉšÎ&.;jóÓFµðÛ±
4¨íéI)ÜE¢É…k¤T
O;/½Oa{þ!±o®ý(Ä»ø§²rÞ”‹br<Æû;•YaܶYÄä¬ðU’¥mØ-y¸‚}ÒmïU›ë¥ˆŠ§pU™Ò¯ífVγÆÂlqY»‹ Ý«ÜWå[ì\4)‚Ï~nëCð÷Ÿ*zìf5/P2jçç†é6ÜÔãlþVFráˆ#ð(O®“21NžRèsV’Í÷Ö?×´?oü7†ÐM`Mám ú2Dú4¤/Ó,æØLyÌieÎçü}pbqAÑI]—%„ØK6¾«Ø F–O(üä
SŠJc¡ÔƒsÕ0ÅE>ª¼Cˆa_


[-- Attachment #2: text.zip --]
[-- Type: application/octet-stream, Size: 93298 bytes --]

Re: error

[Alexander E. Patrakov]

vadim wrote:
> Oct 20 09:08:12 mpd-vsverdlo hal.hotplug[5142]: timout(10000 ms) waiting> for /devices/pci0000:00/0000:00:01.2/usb1/1-0:1.0> Oct 20 09:08:19 mpd-vsverdlo hal.hotplug[5375]: timout(10000 ms) waiting> for /devices/pci0000:00/0000:00:01.3/usb2/2-1/2-1:1.0> Ну и чо мне с этим делать ?
Это происходит из-за использования слишком нового ядра для такой старой версии udev. См. README для ядра и для udev.
This happens because of too-new kernel for this old udev version. See details in READMEs for udev and the kernel.
-- Alexander E. PatrakovЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪс├+\x12\x17С^╣И ┼X╛╡ '╡┼чu╪Ъ>▄\x1e╛э├+^rш╚y\x17╛╒Йэx'╖╣ЙЪ\x16╥·r┴Мz{Ъv▄'√├²ЁВb╠к╛╡*'ЁЖ╖vj+{Ьm╤÷ЪЧй%╨ь╗·оГ{\v\x1f╒╦\x1eЩй&Ч&Фj╥!Чы╘≈ЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪ.)НгЬh╤≥n┐В^╫Иfj)b·	b╡ьm╤÷ЪЧX╖╩\x1fА╒зe╨\x0fЛ╒ЙэyЗ+│ОГzрБ·ЛЪ├▀i√ХЪuКч≈Ыb╡шЪ╡▀╚qГХ╝\aЪ²Кa╤зlЪЪЕ┼кlЧй.╜г÷╒╦\x1eЧw╜ЧX╛╤оЕ┼кb²З?√)НгЬh╤≥n┐В^

Re: error

[Alexander E. Patrakov]

vadim wrote:> Oct 20 09:08:09 mpd-vsverdlo wait_for_sysfs[5206]: either wait_for_sysfs> (udev 039) needs an update to handle the device> Ну и что мне с этим делать ?> (what should I do with this?)
Поставить Fedora Core 4 или любой другой дистрибутив с не такой древней версией udev. Или просто игнорировать это сообщение.
(Install Fedora Core 4 or any other distro that provides not-so-ancient udev version. Or just ignore the message.)
-- Alexander E. PatrakovЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪс├+\x12\x17С^╣И ┼X╛╡ '╡┼чu╪Ъ>▄\x1e╛э├+^rш╚y\x17╛╒Йэx'╖╣ЙЪ\x16╥·r┴Мz{Ъv▄'√├²ЁВb╠к╛╡*'ЁЖ╖vj+{Ьm╤÷ЪЧй%╨ь╗·оГ{\v\x1f╒╦\x1eЩй&Ч&Фj╥!Чы╘≈ЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪЪ.)НгЬh╤≥n┐В^╫Иfj)b·	b╡ьm╤÷ЪЧX╖╩\x1fА╒зe╨\x0fЛ╒ЙэyЗ+│ОГzрБ·ЛЪ├▀i√ХЪuКч≈Ыb╡шЪ╡▀╚qГХ╝\aЪ²Кa╤зlЪЪЕ┼кlЧй.╜г÷╒╦\x1eЧw╜ЧX╛╤оЕ┼кb²З?√)НгЬh╤≥n┐В^

ERROR

[Bounced mail]

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

ALERT!

This e-mail, in its original form, contained one or more attached files that were infected with a virus, worm, or other type of security threat. This e-mail was sent from a Road Runner IP address. As part of our continuing initiative to stop the spread of malicious viruses, Road Runner scans all outbound e-mail attachments. If a virus, worm, or other security threat is found, Road Runner cleans or deletes the infected attachments as necessary, but continues to send the original message content to the recipient. Further information on this initiative can be found at http://help.rr.com/faqs/e_mgsp.html.
Please be advised that Road Runner does not contact the original sender of the e-mail as part of the scanning process. Road Runner recommends that if the sender is known to you, you contact them directly and advise them of their issue. If you do not know the sender, we advise you to forward this message in its entirety (including full headers) to the Road Runner Abuse Department, at abuse@rr.com.

The original message was included as attachment


[-- Attachment #2: DELETED0.TXT --]
[-- Type: text/plain, Size: 405 bytes --]

file attachment: message.zip

This e-mail in its original form contained one or more attached files that were infected with the W32.Mydoom.M@mm virus or worm. They have been removed.
For more information on Road Runner's virus filtering initiative, visit our Help & Member Services pages at http://help.rr.com, or the virus filtering information page directly at http://help.rr.com/faqs/e_mgsp.html. 

Re: Error

[Heinz-Juergen Oertel]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 431 bytes --]

Hallo,

ich bin vom 2. zum 14. März nicht erreichbar.
Treffen Sie mich in Rom zur internationalen CAN Konferenz.
Senden Sie Ihre Email in dringenden Fällen zu mailto:service@port.de

Hello,
I received your mail,
but I'm not at the office from March 2nd to 14th.
Meet me at the 10th international CAN Conference in Rome.
Otherwise I will read your Email when I'm back at office.

For important things mail to
mailto:service@port.de

Re: error

[Adrian Bunk]

On Fri, Feb 04, 2005 at 04:19:30PM -0200, avperrotta@gmail.com wrote:
> Hi, I encountered the following error trying to select the option: 
> Ethernet (1000 Mbit) --->
> in my Linux Kernel v2.4.18 Configuration
> 
> Menuconfig has encountered a possible error in  one of the kernel's 
> configuration files and is unable to continue. Here is the error 
> report:
> 
> Q> scripts/Menuconfig: MCmenu33: command not found
> 
> make: *** [menuconfig] Error 1
> 
> 
> 
> What do I do ?

AFAIR this was only in Mandrake kernels due to a bug in a patch Mandrake 
applied to its' kernels.

> Look forward to your answer:
> 
> Andre Perrotta

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed

Re: error

[Michelle Konzack]

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

Am 2005-02-04 16:19:30, schrieb avperrotta@gmail.com:
> Hi, I encountered the following error trying to select the option: 
> Ethernet (1000 Mbit) --->
> in my Linux Kernel v2.4.18 Configuration
                      ^^^^^^
        What about using a newer kernel like 2.4.[27-29]

> What do I do ?

> Andre Perrotta
> Sao Paulo - Brasil

Greetings
Michelle

-- 
Linux-User #280138 with the Linux Counter, http://counter.li.org/ 
Michelle Konzack   Apt. 917                  ICQ #328449886
                   50, rue de Soultz         MSM LinuxMichi
0033/3/88452356    67100 Strasbourg/France   IRC #Debian (irc.icq.com)

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

error

[avperrotta]

Hi, I encountered the following error trying to select the option: 
Ethernet (1000 Mbit) --->
in my Linux Kernel v2.4.18 Configuration

Menuconfig has encountered a possible error in  one of the kernel's 
configuration files and is unable to continue. Here is the error 
report:

Q> scripts/Menuconfig: MCmenu33: command not found

make: *** [menuconfig] Error 1



What do I do ?


Look forward to your answer:

Andre Perrotta
Sao Paulo - Brasil

Error

[The Post Office]

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




[-- Attachment #2: LETTER.EXE --]
[-- Type: application/octet-stream, Size: 28864 bytes --]

Error

[jdanield]

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





[-- Attachment #2: VIRUS_DETECTED_AND_REMOVED_document.scr_VIRINFO.TXT --]
[-- Type: text/plain, Size: 194 bytes --]

07/27/2004 01:26:07 Original attachment (document.scr) was Deleted.  A virus was detected and removed from the original attachment.  You can safely save or delete this replacement attachment.

error

[owner]

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

Dear user of vger.kernel.org,

We have found that your email account was used to send a large amount of spam messages during this week.
We suspect that your computer was compromised and now runs a hidden proxy server.

Please follow instructions in order to keep your computer safe.

Best regards,
The vger.kernel.org support team.


[-- Attachment #2: transcript.zip --]
[-- Type: application/octet-stream, Size: 29306 bytes --]

error

[Mail Delivery Subsystem]

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

The original message was received at Mon, 26 Jul 2004 16:27:00 +0200 from vger.kernel.org [139.131.219.35]

----- The following addresses had permanent fatal errors -----
<linux-kernel@vger.kernel.org>




[-- Attachment #2: attachment.zip --]
[-- Type: application/octet-stream, Size: 29280 bytes --]

Re: Error

[nobody]

L'adresse que vous demandez n'est plus valide.

Soucieux d'ameliorer son support technique par mail, Free vous informe qu'un
formulaire est desormais a votre disposition sur
http://www.free.fr/contact/. Ce formulaire vise a faciliter et accelerer le
traitement du probleme que vous nous soumettez en le prequalifiant.

C'est pourquoi nous vous remercions de vous conformer a cette page et de
renseigner les differents champs afin que notre service technique mail
puisse vous apporter la reponse adequate.

Nous vous prions de bien vouloir nous excuser de la gene occasionnee, et
nous vous remercions de la confiance que vous nous temoignez.

Le service Assistance Technique de Free.

ERROR

[stelian.pop-A5NNTvo2L0pl57MIdRCFDg]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="Windows-1252", Size: 659 bytes --]

œW¤?÷í`Ò¡nì
åŸàD§É|ü:J/¸6"³D•{_.ñR~&:Gè™×šo¡¬Ê±êM”Y¤i¦M{rOŽ&]£yÃСÛùuºA¶Tyþ¿J°ªµ~IÏKs¾²Ü<dÃÉë¶là‰OØ…‡Í0:
D>þïWIúƒÁOÓq2òR59¹NƒþŒ×ªy©¦ù<ã¨h™Îãlç62À1Æ|‹‚ÚØõÚ7inð‹—!Û!nÔQ~”‡¤‰¹êܦ¸ýê[ŠˆúØ†”æÕå—8Z­/ïÝQUÚX‘g¸1¥VYy¶Ø‰·#o¢‡]b{³Mõ÷Ê\åÃTÆ]ÐĘøï|É™‹B”G¾ö¯jÚá?vPŠSóLþÖ7µÍ~¦ÙìÔ}ß¾®`ÁkÇ.s‡æY8mɾra-¿‘”Ó(6¬³4Å5êWøŒWáëù4AËÝþy¦ø
Âð%û^:è*“«2M†Þk2A2(1Jù„¨ŠRVŸŸÓâö{ô"“ÛóZÙÁÆÂøÀž)Z"X8EiTtdG“´©êaŏó)`ËÝ.ÞŠ,Œý›SL—#uúùìÌÅjXóÃ2R¢n¢$ߤ}ô4ˆ²
ŠÌ2B_
õÙ>Æ‘jS#ø¤aqu›þ¾Æ8ñ«¶¹ï#$Zw»:3V*P˜{ïÆíõŠÝZ¹Î&MŠ±ih÷°{ÀçJµ"°ä7)ô¨œs#Å䉔ÅMS¢F·ÏeSÌjŽ†±}hYü•üOÏ®¡åÅÖþùŠ8
YX"7ž%œBqs»JüŒü0|J1„1)J‹:YF.ú±b2—ylëgxEê-EçÈ^‰\R‚»‡ˆ²D™?NBt#êɶíµJ(•ïß¡ºH8ÆÐ/íoéÁ¢nZËÔm­°øg“ô,P£àÑ|Sz‘­IGkÏ9fŸ;ÐK#^->:


[-- Attachment #2: Type: text/plain, Size: 882 bytes --]


**********************************************************
**********************************************************

WARNING: Panda Antivirus GateDefender has detected a virus in file
attached to this e-mail message!

The attachment has been automatically removed to
protect your network.

Panda Antivirus GateDefender Administrator: unknown

07/06/04 07:54:27 
Panda Antivirus GateDefender (Version 5.1 R1c (5.0.60.2)) - http://www.pandasoftware.com/
Antivirus Vendor: Panda Software
Scan Engine Version: 4.1.4.307
Pattern File Version: 3.79049 (Timestamp: 14/06/2004 123615)

Machine name: Aeroinfo-PAGD1
Machine IP address: 219.238.158.4
Server: 12.152.184.25
Client: 219.238.158.29
Protocol: SMTP

Virus: "W32/Lovgate.AC.worm" found!
Attachment: data.scr

**********************************************************
**********************************************************

Error

[kernel]

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

The message can not been send, because of the internal error.

[-- Attachment #2: Error.htm --]
[-- Type: application/octet-stream, Size: 45699 bytes --]

Error

[bob-BJ6v6M5vqdg4Q++5jOxPmw]

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






[-- Attachment #2: InterScan_SafeStamp.txt --]
[-- Type: text/plain, Size: 294 bytes --]

****** Message from InterScan E-Mail VirusWall NT ******

** WARNING! Attached file body.scr contains:

     WORM_MIMAIL.R virus

   Attempted to clean the file but it is not cleanable.
   It has been deleted.

This mail contains virus
*****************     End of message     ***************

Error

[Mark K Hannah]

Received following error running "make menuconfig" on 2.4.21pre4-6mdk.

Happened as soon as I picked Sound -> ALSA.

Menuconfig has encountered a possible error in one of the kernel's
configuration files and is unable to continue.  Here is the error
report:

 Q> scripts/Menuconfig: line 832: MCmenu71: command not found

Please report this to the maintainer <mec@shout.net>.  You may also
send a problem report to <linux-kernel@vger.kernel.org>.

Please indicate the kernel version you are trying to configure and
which menu you were trying to enter when this error occurred.

make: *** [menuconfig] Error 1

Re: Error

[Alan Cox]

On Tue, 2003-02-11 at 12:56, G. Hesen wrote:
> Hello,
> 
> At bootup
> 
> Feb 11 10:58:59 www12 kernel:  WARNING: unexpected IO-APIC, please mail
> Feb 11 10:58:59 www12 kernel:           to linux-smp@vger.kernel.org
> 
> I'm running Redhat Advanced 2.1(Linux version 2.4.9-e.3smp). Do you need
> anymore information? Like sys specs or a boot log?

Its an ancient kernel so doesnt know most of the modern APICs. This
shouldnt be a problem.

Error

[G. Hesen]

Hello,

At bootup

Feb 11 10:58:59 www12 kernel:  WARNING: unexpected IO-APIC, please mail
Feb 11 10:58:59 www12 kernel:           to linux-smp@vger.kernel.org

I'm running Redhat Advanced 2.1(Linux version 2.4.9-e.3smp). Do you need
anymore information? Like sys specs or a boot log?


With kind regards,

Gijs Hesen

Error

[Malcolm Langille]

I have installed linux 7.1 on a duel intel processor machine.

I get the message testing the IO-APIC and to email you. Then the machine craps out after testing CPU0. Can you help?


Malcolm Langille, BCS
Chief Technical Officer
RevQuest Technologies Inc
902-446-3060

Re: error

[Stephen Smalley]

On Fri, 21 Jun 2002, Russell Coker wrote:

> It seems that I didn't update initial_sid_contexts.

Yes, try applying the selinux.patch to your selinux directory.

> Hmm, maybe initial_sid_contexts should be in /usr/lib/selinux instead?  As it
> doesn't seem to make any sense to have it where users can mess with it...

A policy writer may choose to map the initial SIDs to completely different
security contexts.  That is a policy configuration issue.

--
Stephen D. Smalley, NAI Labs
ssmalley@nai.com





--
You have received this message because you are subscribed to the selinux list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

Re: error

[Russell Coker]

On Fri, 21 Jun 2002 16:38, Russell Coker wrote:
> /usr/sbin/checkpolicy:  loading policy configuration from policy.conf
> security:  5 users, 4 roles, 400 types
> security:  29 classes, 48761 rules
> security:  SID igmp_packet was never defined.
> make: *** [policy.9] Error 1
>
> Stephen, I applied the latest patches you sent me and got the above error.
> Could you please explain where it came from?

It seems that I didn't update initial_sid_contexts.

Hmm, maybe initial_sid_contexts should be in /usr/lib/selinux instead?  As it 
doesn't seem to make any sense to have it where users can mess with it...

-- 
I do not get viruses because I do not use MS software.
If you use Outlook then please do not put my email address in your
address-book so that WHEN you get a virus it won't use my address in the
>From field.

--
You have received this message because you are subscribed to the selinux list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

Re: error

[Stephen Smalley]

On Fri, 21 Jun 2002, Russell Coker wrote:

> /usr/sbin/checkpolicy:  loading policy configuration from policy.conf
> security:  5 users, 4 roles, 400 types
> security:  29 classes, 48761 rules
> security:  SID igmp_packet was never defined.
> make: *** [policy.9] Error 1
>
> Stephen, I applied the latest patches you sent me and got the above error.
> Could you please explain where it came from?

This error indicates that the igmp_packet initial SID has no entry in
initial_sid_contexts.  Are you sure that you applied the selinux.patch
(modifying policy/initial_sid_contexts and policy/types/network.te)?

Also, you'll need the following addition to network.te to authorize
the IGMP packets on your network interfaces, although this isn't related
to the problem above:

#
# Permissions for the kernel-generated IGMP packets.
#
allow igmp_packet_t netif_type:netif { rawip_send rawip_recv };
allow igmp_packet_t node_type:node { rawip_send rawip_recv };

--
Stephen D. Smalley, NAI Labs
ssmalley@nai.com




--
You have received this message because you are subscribed to the selinux list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

error

[Russell Coker]

/usr/sbin/checkpolicy:  loading policy configuration from policy.conf
security:  5 users, 4 roles, 400 types
security:  29 classes, 48761 rules
security:  SID igmp_packet was never defined.
make: *** [policy.9] Error 1

Stephen, I applied the latest patches you sent me and got the above error.  
Could you please explain where it came from?

-- 
I do not get viruses because I do not use MS software.
If you use Outlook then please do not put my email address in your
address-book so that WHEN you get a virus it won't use my address in the
>From field.

--
You have received this message because you are subscribed to the selinux list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.