Menu
▾
▴
devil-linux-develop — developer discussions
You can subscribe to this list here.
| 2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(55) |
Oct
(44) |
Nov
(156) |
Dec
(123) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2002 |
Jan
(130) |
Feb
(156) |
Mar
(162) |
Apr
(171) |
May
(97) |
Jun
(127) |
Jul
(58) |
Aug
(81) |
Sep
(86) |
Oct
(45) |
Nov
(41) |
Dec
(84) |
| 2003 |
Jan
(71) |
Feb
(87) |
Mar
(133) |
Apr
(152) |
May
(151) |
Jun
(232) |
Jul
(320) |
Aug
(237) |
Sep
(271) |
Oct
(536) |
Nov
(301) |
Dec
(393) |
| 2004 |
Jan
(393) |
Feb
(184) |
Mar
(314) |
Apr
(225) |
May
(139) |
Jun
(77) |
Jul
(87) |
Aug
(75) |
Sep
(139) |
Oct
(50) |
Nov
(8) |
Dec
(28) |
| 2005 |
Jan
(66) |
Feb
(63) |
Mar
(14) |
Apr
(14) |
May
(8) |
Jun
(23) |
Jul
(21) |
Aug
(6) |
Sep
(29) |
Oct
(55) |
Nov
(38) |
Dec
(8) |
| 2006 |
Jan
(5) |
Feb
(10) |
Mar
(1) |
Apr
(15) |
May
(32) |
Jun
(44) |
Jul
(11) |
Aug
(8) |
Sep
(9) |
Oct
(14) |
Nov
(4) |
Dec
(3) |
| 2007 |
Jan
(3) |
Feb
(3) |
Mar
(2) |
Apr
|
May
|
Jun
|
Jul
(35) |
Aug
(49) |
Sep
(8) |
Oct
(42) |
Nov
(44) |
Dec
(7) |
| 2008 |
Jan
(2) |
Feb
(7) |
Mar
(8) |
Apr
(80) |
May
(74) |
Jun
(29) |
Jul
(5) |
Aug
(7) |
Sep
(6) |
Oct
(1) |
Nov
|
Dec
|
| 2009 |
Jan
(8) |
Feb
(19) |
Mar
(3) |
Apr
(24) |
May
(22) |
Jun
(23) |
Jul
(8) |
Aug
(23) |
Sep
(8) |
Oct
(27) |
Nov
(52) |
Dec
(27) |
| 2010 |
Jan
(36) |
Feb
(29) |
Mar
(17) |
Apr
(28) |
May
(21) |
Jun
(4) |
Jul
|
Aug
(28) |
Sep
(18) |
Oct
(6) |
Nov
(34) |
Dec
(16) |
| 2011 |
Jan
(18) |
Feb
(12) |
Mar
|
Apr
|
May
(9) |
Jun
(1) |
Jul
(5) |
Aug
(5) |
Sep
(7) |
Oct
(16) |
Nov
(26) |
Dec
(17) |
| 2012 |
Jan
(6) |
Feb
(34) |
Mar
(52) |
Apr
(10) |
May
(3) |
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
(4) |
Nov
(1) |
Dec
(4) |
| 2013 |
Jan
(5) |
Feb
|
Mar
|
Apr
(5) |
May
(4) |
Jun
|
Jul
|
Aug
(14) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2014 |
Jan
|
Feb
(2) |
Mar
(5) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(3) |
Dec
(11) |
| 2015 |
Jan
(5) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
(1) |
Oct
(1) |
Nov
|
Dec
|
| 2016 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(2) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2017 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2018 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Oliver N. <ol...@rh...> - 2012-01-13 10:49:31
|
Hi! This was the first time i had the need for cmake to compile a software for my custom cd. I knew that there is no cmake in DL, so i decided to add cmake first into the build-system. This went more or less straight forward. Then i was not sure, if cmake is useful in general. I needed cmake only for building - not for the final iso. I want to ask the developers, if they think that cmake is useful in general, or a bit to special for DL? If you think cmake is useful i can provide the necessary script(s) to include this into the build-system and for the final iso if you want. cheers, Oliver |
|
From: Andrzej O. <an...@ma...> - 2012-01-02 12:56:45
|
Heiko, > Thanks for submitting the patches. > Is the realms patch really needed by some people? It has been many quagga > releases since it was created the first time, but never made it into the > mainstream code. I do not use realms. I need Quagga to BGP, since one my connection to Internet is dual-hommed. But I'm not a provider and do not transit. Soon I'm going to check, how will work on BGP xorp and bird. But a few years ago contacted me a guy who googled that I talked about quagga on our list. He knew that I build DL and just asked me about realms. Apparently, this mechanism enables control of the internal structure of the autonomic system. I answered him that you compile Quagga with realms. Since that time, I understand that the realms sometimes may be needed and upgrading to 0.99.20 I adopted realms patch. Regards -- Andrzej Odyniec |
|
From: Heiko Z. <he...@zu...> - 2011-12-31 14:12:38
|
Andrzej, Thanks for submitting the patches. Is the realms patch really needed by some people? It has been many quagga releases since it was created the first time, but never made it into the mainstream code. -- Regards Heiko Zuerker http://www.devil-linux.org -----Original Message----- From: Andrzej Odyniec [mailto:an...@ma...] Sent: Friday, December 30, 2011 7:05 PM To: dev...@li... Subject: Re: [Devil-linux-develop] Devil-Linux 1.6.0-RC1 released Heiko, This is a set of patches to Quagga for realmss. I adopted it from the previous set v.0.99.17, when I struggled with the inconsistencies between the Quagga, new kernels and the new Shorewall. The update did not solve my problems, I found the only workaround in shorewall. But the set of patches remained. I'm not using realms in my installations and never tested, so I'm sure that is good, but I did carefully adaptive correction, comparing several versions of Quagga patched to realms and improving those few places where the old patches were rejected. So far in my compilations I'm using quagga 0.99.20 with these patches and my BGP (without realms) works well. Happy New Year -- Andrzej Odyniec |
|
From: Andrzej O. <an...@ma...> - 2011-12-31 01:06:02
|
Heiko, This is a set of patches to Quagga for realmss. I adopted it from the previous set v.0.99.17, when I struggled with the inconsistencies between the Quagga, new kernels and the new Shorewall. The update did not solve my problems, I found the only workaround in shorewall. But the set of patches remained. I'm not using realms in my installations and never tested, so I'm sure that is good, but I did carefully adaptive correction, comparing several versions of Quagga patched to realms and improving those few places where the old patches were rejected. So far in my compilations I'm using quagga 0.99.20 with these patches and my BGP (without realms) works well. Happy New Year -- Andrzej Odyniec |
|
From: Heiko Z. <he...@zu...> - 2011-12-30 16:30:00
|
Hello DL Community! I'm happy to announce that the first release candidate of Devil-Linux 1.6 is now available for download. This release bring the Linux kernel 3.1.6, glibc 2.12, 64 bit support, and many other updates. Please read the changelog for details. Please support the project and donate. Every little bit helps! http://www.devil-linux.org/sitetools/donatedl.php Report any new bugs or submit patches here: http://www.devil-linux.org/support/bugs.php -- Regards Heiko Zuerker http://www.devil-linux.org ------------------------------------------------------------------------------ Write once. Port to many. Get the SDK and tools to simplify cross-platform app development. Create new or port existing apps to sell to consumers worldwide. Explore the Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev _______________________________________________ Devil-linux-announce mailing list Dev...@li... https://lists.sourceforge.net/lists/listinfo/devil-linux-announce |
|
From: Heiko Z. <he...@zu...> - 2011-12-21 21:16:12
|
I'm uploading it right now, it should be done in ~30 minutes. Heiko Quoting Dominic Raferd <dl...@ed...>: > Thanks Heiko, can we have a 32-bit server version of the latest testing I'm uploading it right now, it should be done in ~30 minutes. -- Regards Heiko Zuerker http://www.devil-linux.org |
|
From: Dominic R. <dl...@ed...> - 2011-12-21 11:06:09
|
Thanks Heiko, can we have a 32-bit server version of the latest testing release? On 20/12/2011 13:55, Heiko Zuerker wrote: > Hello DL Community! > > Before I talk about the new testing release, I have a request: > As many of you are probably aware, Devil-Linux is entirely financed > out of my own pocket. Many of you save a great deal of money by using > free software like DL. I just spent a good chunk of money to update my > build and test environment for DL and was hoping to get your monetary > support. If everybody donates just a few dollars, it would help me a > lot! > Donating is easy: just go to > http://www.devil-linux.org/sitetools/donatedl.php and use Paypal. > Thank you for your support! > > Now that I'm done whining about money, here are the good news and more > requests for your help: > I just uploaded a new testing version of the new 1.6 release. It's not > a final release candidate yet, but we're getting very close! I'm > kindly requesting your help in more testing and fixing the last > remaining issues. All known issues are documented in Mantis (like > getting grub working for install-on-usb). > > You can download the testing version here (or tomorrow on the mirrors): > ftp://ftp.devil-linux.org/pub/devel/testing/ > > Please report any new bugs or submit patches here: > http://www.devil-linux.org/support/bugs.php > |
|
From: Heiko Z. <he...@zu...> - 2011-12-20 13:55:11
|
Hello DL Community! Before I talk about the new testing release, I have a request: As many of you are probably aware, Devil-Linux is entirely financed out of my own pocket. Many of you save a great deal of money by using free software like DL. I just spent a good chunk of money to update my build and test environment for DL and was hoping to get your monetary support. If everybody donates just a few dollars, it would help me a lot! Donating is easy: just go to http://www.devil-linux.org/sitetools/donatedl.php and use Paypal. Thank you for your support! Now that I'm done whining about money, here are the good news and more requests for your help: I just uploaded a new testing version of the new 1.6 release. It's not a final release candidate yet, but we're getting very close! I'm kindly requesting your help in more testing and fixing the last remaining issues. All known issues are documented in Mantis (like getting grub working for install-on-usb). You can download the testing version here (or tomorrow on the mirrors): ftp://ftp.devil-linux.org/pub/devel/testing/ Please report any new bugs or submit patches here: http://www.devil-linux.org/support/bugs.php -- Regards Heiko Zuerker http://www.devil-linux.org |
|
From: Heiko Z. <he...@zu...> - 2011-12-16 13:44:19
|
DONE Heiko Quoting Serge Leschinsky <ser...@gm...>: > Hi Heiko, > > On 12/15/2011 06:00 AM, Heiko Zuerker wrote: >> Serge, >> >> cvs status cd_cleanup >> smi...@de...'s password: >> =================================================================== >> File: cd_cleanup Status: Up-to-date >> >> Working revision: 1.19 >> Repository revision: 1.19 >> /cvsroot/devil-linux/build/scripts/cd_cleanup,v >> Sticky Tag: (none) >> Sticky Date: (none) >> Sticky Options: (none) >> >> Did you try doing a "cvs update -d -P" ? > > yes, I did. The most confusing for me thing is "Status: Up-to-date". It looks > like CVS does verification, but sees only version 1.17 > > cvs status scripts/cd_cleanup > sma...@de...'s password: > =================================================================== > File: cd_cleanup Status: Up-to-date > > Working revision: 1.17 > Repository revision: 1.17 > /cvsroot/devil-linux/build/scripts/cd_cleanup,v > > Probably it will be better if you push the change, because me > environment seems > to be not correct. > > Serge > > > > > ------------------------------------------------------------------------------ > Learn Windows Azure Live! Tuesday, Dec 13, 2011 > Microsoft is holding a special Learn Windows Azure training event for > developers. It will provide a great way to learn Windows Azure and what it > provides. You can attend the event by watching it streamed LIVE online. > Learn more at http://p.sf.net/sfu/ms-windowsazure > _______________________________________________ > Devil-linux-develop mailing list > Dev...@li... > https://lists.sourceforge.net/lists/listinfo/devil-linux-develop -- Regards Heiko Zuerker http://www.devil-linux.org |
|
From: Serge L. <ser...@gm...> - 2011-12-16 06:12:54
|
Hi Heiko,
On 12/15/2011 06:00 AM, Heiko Zuerker wrote:
> Serge,
>
> cvs status cd_cleanup
> smi...@de...'s password:
> ===================================================================
> File: cd_cleanup Status: Up-to-date
>
> Working revision: 1.19
> Repository revision: 1.19
> /cvsroot/devil-linux/build/scripts/cd_cleanup,v
> Sticky Tag: (none)
> Sticky Date: (none)
> Sticky Options: (none)
>
> Did you try doing a "cvs update -d -P" ?
yes, I did. The most confusing for me thing is "Status: Up-to-date". It looks
like CVS does verification, but sees only version 1.17
cvs status scripts/cd_cleanup
sma...@de...'s password:
===================================================================
File: cd_cleanup Status: Up-to-date
Working revision: 1.17
Repository revision: 1.17 /cvsroot/devil-linux/build/scripts/cd_cleanup,v
Probably it will be better if you push the change, because me environment seems
to be not correct.
Serge
|
|
From: Heiko Z. <he...@zu...> - 2011-12-15 14:00:55
|
Serge,
cvs status cd_cleanup
smi...@de...'s password:
===================================================================
File: cd_cleanup Status: Up-to-date
Working revision: 1.19
Repository revision: 1.19
/cvsroot/devil-linux/build/scripts/cd_cleanup,v
Sticky Tag: (none)
Sticky Date: (none)
Sticky Options: (none)
Did you try doing a "cvs update -d -P" ?
Heiko
Quoting Serge Leschinsky <ser...@gm...>:
> Heiko,
>
> can you help me with CVS ? I don't understand what I do wrong ...
>
> CVS_RSH=ssh cvs -d
> :ext:sma...@de...:/cvsroot/devil-linux status
> scripts/cd_cleanup
> sma...@de...'s password:
> ===================================================================
> File: cd_cleanup Status: Up-to-date
>
> Working revision: 1.17
> Repository revision: 1.17
> /cvsroot/devil-linux/build/scripts/cd_cleanup,v
> Sticky Tag: (none)
> Sticky Date: 2011.12.13.21.00.00
> Sticky Options: (none)
>
> .......
>
> but I see that the latest version is 1.19. Is it a
> replication/update problem or
> we work in the branch? :(
>
> Serge
>
> On 12/14/2011 02:19 PM, Serge Leschinsky wrote:
>
>> Let me do that... But for some reason I cannot get the latest
>> changes from CVS.
>> I see only the previous ones. I'll wait a little bit.
>>
>
>
>
> ------------------------------------------------------------------------------
> 10 Tips for Better Server Consolidation
> Server virtualization is being driven by many needs.
> But none more important than the need to reduce IT complexity
> while improving strategic productivity. Learn More!
> http://www.accelacomm.com/jaw/sdnl/114/51507609/
> _______________________________________________
> Devil-linux-develop mailing list
> Dev...@li...
> https://lists.sourceforge.net/lists/listinfo/devil-linux-develop
--
Regards
Heiko Zuerker
http://www.devil-linux.org
|
|
From: Serge L. <ser...@gm...> - 2011-12-15 04:53:01
|
Heiko,
can you help me with CVS ? I don't understand what I do wrong ...
CVS_RSH=ssh cvs -d
:ext:sma...@de...:/cvsroot/devil-linux status
scripts/cd_cleanup
sma...@de...'s password:
===================================================================
File: cd_cleanup Status: Up-to-date
Working revision: 1.17
Repository revision: 1.17 /cvsroot/devil-linux/build/scripts/cd_cleanup,v
Sticky Tag: (none)
Sticky Date: 2011.12.13.21.00.00
Sticky Options: (none)
.......
but I see that the latest version is 1.19. Is it a replication/update problem or
we work in the branch? :(
Serge
On 12/14/2011 02:19 PM, Serge Leschinsky wrote:
> Let me do that... But for some reason I cannot get the latest changes from CVS.
> I see only the previous ones. I'll wait a little bit.
>
|
|
From: Serge L. <ser...@gm...> - 2011-12-14 22:20:10
|
On 12/14/2011 01:11 PM, Heiko Zuerker wrote: >>>> # fix for python config file >>>> mkdir -p $CDDIR/$(ls -d /usr/include/python2.?) >>>> cp /usr/include/python2.?/pyconfig.h $CDDIR/usr/include/python2.?/ >>> >>> Is this the only file we really need? >>> Right now the whole python2.7 folder is included >> >> Yes, the only one file we need to use python is pyconfig.h. Other files are >> necessary on compilation stage only. > > I like your solution better. > Do you want to undo mine and add yours, or should I do it? Let me do that... But for some reason I cannot get the latest changes from CVS. I see only the previous ones. I'll wait a little bit. Serge |
|
From: Heiko Z. <he...@zu...> - 2011-12-14 21:12:02
|
Quoting Serge Leschinsky <ser...@gm...>: > On 12/14/2011 11:25 AM, Heiko Zuerker wrote: >> >> Quoting Serge Leschinsky<ser...@gm...>: >>> Hi Andrzej, >>> >>> I have it in scripts/cd_cleanup: >>> >>> >>> # fix for python config file >>> mkdir -p $CDDIR/$(ls -d /usr/include/python2.?) >>> cp /usr/include/python2.?/pyconfig.h $CDDIR/usr/include/python2.?/ >> >> Is this the only file we really need? >> Right now the whole python2.7 folder is included > > Yes, the only one file we need to use python is pyconfig.h. Other files are > necessary on compilation stage only. I like your solution better. Do you want to undo mine and add yours, or should I do it? -- Regards Heiko Zuerker http://www.devil-linux.org |
|
From: Serge L. <ser...@gm...> - 2011-12-14 21:03:05
|
On 12/14/2011 11:25 AM, Heiko Zuerker wrote: > > Quoting Serge Leschinsky<ser...@gm...>: >> Hi Andrzej, >> >> I have it in scripts/cd_cleanup: >> >> >> # fix for python config file >> mkdir -p $CDDIR/$(ls -d /usr/include/python2.?) >> cp /usr/include/python2.?/pyconfig.h $CDDIR/usr/include/python2.?/ > > Is this the only file we really need? > Right now the whole python2.7 folder is included Yes, the only one file we need to use python is pyconfig.h. Other files are necessary on compilation stage only. Serge |
|
From: Heiko Z. <he...@zu...> - 2011-12-14 19:25:56
|
Quoting Serge Leschinsky <ser...@gm...>: > Hi Andrzej, > > I have it in scripts/cd_cleanup: > > > # fix for python config file > mkdir -p $CDDIR/$(ls -d /usr/include/python2.?) > cp /usr/include/python2.?/pyconfig.h $CDDIR/usr/include/python2.?/ Is this the only file we really need? Right now the whole python2.7 folder is included -- Regards Heiko Zuerker http://www.devil-linux.org |
|
From: Heiko Z. <he...@zu...> - 2011-12-14 19:10:26
|
I fixed it this morning in CVS, along with a few other things.
Heiko
Quoting Serge Leschinsky <ser...@gm...>:
> Hi Andrzej,
>
> I have it in scripts/cd_cleanup:
>
>
> # fix for python config file
> mkdir -p $CDDIR/$(ls -d /usr/include/python2.?)
> cp /usr/include/python2.?/pyconfig.h $CDDIR/usr/include/python2.?/
>
> Serge
>
> On 12/14/2011 09:26 AM, Andrzej Odyniec wrote:
>> Dear Heiko,
>>
>> Now kernel is booting, but...
>>
>> new Python 2.7 is not working:
>>> # python
>>> Traceback (most recent call last):
>>> File "/usr/lib/python2.7/site.py", line 563, in<module>
>>> main()
>>> File "/usr/lib/python2.7/site.py", line 545, in main
>>> known_paths = addusersitepackages(known_paths)
>>> File "/usr/lib/python2.7/site.py", line 278, in addusersitepackages
>>> user_site = getusersitepackages()
>>> File "/usr/lib/python2.7/site.py", line 253, in getusersitepackages
>>> user_base = getuserbase() # this will also set USER_BASE
>>> File "/usr/lib/python2.7/site.py", line 243, in getuserbase
>>> USER_BASE = get_config_var('userbase')
>>> File "/usr/lib/python2.7/sysconfig.py", line 520, in get_config_var
>>> return get_config_vars().get(name)
>>> File "/usr/lib/python2.7/sysconfig.py", line 419, in get_config_vars
>>> _init_posix(_CONFIG_VARS)
>>> File "/usr/lib/python2.7/sysconfig.py", line 298, in _init_posix
>>> raise IOError(msg)
>>> IOError: invalid Python installation: unable to open
>>> /usr/include/python2.7/pyconfig.h (No such file or directory)
>>
>> I have such an effect in the 32- and 64-bit version. Now try to
>> build a clean,
>> without my modifications, but they absolutely do not apply to Python and
>> should not impact on him.
>>
>> Best Regards :)
>>
>
>
> ------------------------------------------------------------------------------
> Cloud Computing - Latest Buzzword or a Glimpse of the Future?
> This paper surveys cloud computing today: What are the benefits?
> Why are businesses embracing it? What are its payoffs and pitfalls?
> http://www.accelacomm.com/jaw/sdnl/114/51425149/
> _______________________________________________
> Devil-linux-develop mailing list
> Dev...@li...
> https://lists.sourceforge.net/lists/listinfo/devil-linux-develop
--
Regards
Heiko Zuerker
http://www.devil-linux.org
|
|
From: Serge L. <ser...@gm...> - 2011-12-14 17:52:33
|
Hi Andrzej,
I have it in scripts/cd_cleanup:
# fix for python config file
mkdir -p $CDDIR/$(ls -d /usr/include/python2.?)
cp /usr/include/python2.?/pyconfig.h $CDDIR/usr/include/python2.?/
Serge
On 12/14/2011 09:26 AM, Andrzej Odyniec wrote:
> Dear Heiko,
>
> Now kernel is booting, but...
>
> new Python 2.7 is not working:
>> # python
>> Traceback (most recent call last):
>> File "/usr/lib/python2.7/site.py", line 563, in<module>
>> main()
>> File "/usr/lib/python2.7/site.py", line 545, in main
>> known_paths = addusersitepackages(known_paths)
>> File "/usr/lib/python2.7/site.py", line 278, in addusersitepackages
>> user_site = getusersitepackages()
>> File "/usr/lib/python2.7/site.py", line 253, in getusersitepackages
>> user_base = getuserbase() # this will also set USER_BASE
>> File "/usr/lib/python2.7/site.py", line 243, in getuserbase
>> USER_BASE = get_config_var('userbase')
>> File "/usr/lib/python2.7/sysconfig.py", line 520, in get_config_var
>> return get_config_vars().get(name)
>> File "/usr/lib/python2.7/sysconfig.py", line 419, in get_config_vars
>> _init_posix(_CONFIG_VARS)
>> File "/usr/lib/python2.7/sysconfig.py", line 298, in _init_posix
>> raise IOError(msg)
>> IOError: invalid Python installation: unable to open /usr/include/python2.7/pyconfig.h (No such file or directory)
>
> I have such an effect in the 32- and 64-bit version. Now try to build a clean,
> without my modifications, but they absolutely do not apply to Python and
> should not impact on him.
>
> Best Regards :)
>
|
|
From: Andrzej O. <an...@ma...> - 2011-12-14 17:27:02
|
Dear Heiko,
Now kernel is booting, but...
new Python 2.7 is not working:
> # python
> Traceback (most recent call last):
> File "/usr/lib/python2.7/site.py", line 563, in <module>
> main()
> File "/usr/lib/python2.7/site.py", line 545, in main
> known_paths = addusersitepackages(known_paths)
> File "/usr/lib/python2.7/site.py", line 278, in addusersitepackages
> user_site = getusersitepackages()
> File "/usr/lib/python2.7/site.py", line 253, in getusersitepackages
> user_base = getuserbase() # this will also set USER_BASE
> File "/usr/lib/python2.7/site.py", line 243, in getuserbase
> USER_BASE = get_config_var('userbase')
> File "/usr/lib/python2.7/sysconfig.py", line 520, in get_config_var
> return get_config_vars().get(name)
> File "/usr/lib/python2.7/sysconfig.py", line 419, in get_config_vars
> _init_posix(_CONFIG_VARS)
> File "/usr/lib/python2.7/sysconfig.py", line 298, in _init_posix
> raise IOError(msg)
> IOError: invalid Python installation: unable to open /usr/include/python2.7/pyconfig.h (No such file or directory)
I have such an effect in the 32- and 64-bit version. Now try to build a clean,
without my modifications, but they absolutely do not apply to Python and
should not impact on him.
Best Regards :)
--
Andrzej Odyniec
|
|
From: Heiko Z. <he...@zu...> - 2011-11-29 13:28:11
|
Quoting Andrzej Odyniec <an...@ma...>: > I wrote: > >> D-L with kernel 3.1.2 built from scratch with last CVS sources on >> Debian base system (as for now >> 64-bit) and with default settings (only x86_64 and grsecurity off) >> does not loads kernel. I think, >> this is issue for 32-bit too. >> >> There is possible, that kernel is broken or Your changes in scripts >> (especially string 3.0 changed >> to 3.x --- in some places this is error, i.e. in grsecurity >> script... yes, I know, I switched off >> grsecurity, but...). >> >> But I can not boot build with kernel 3.1. I will experiment with >> next kernel. > > Dear Heiko, > > I have first 3.1.1-grsec 32-bit bootable (after adopting grsecurity name to > "3.x" pattern) but I'm not sure why this, because in desperation I ran 4 > parallel builds with different experiments and only one result is > bootable. So > I will build more systematically. Maybe kernel-patches are inadequate... Okay, keep me posted. I'm still struggling with gcc, so I'm not sure when I'll be able to run a test myself. -- Regards Heiko Zuerker http://www.devil-linux.org |
|
From: Andrzej O. <an...@ma...> - 2011-11-29 11:43:22
|
I wrote: > D-L with kernel 3.1.2 built from scratch with last CVS sources on Debian base system (as for now > 64-bit) and with default settings (only x86_64 and grsecurity off) does not loads kernel. I think, > this is issue for 32-bit too. > > There is possible, that kernel is broken or Your changes in scripts (especially string 3.0 changed > to 3.x --- in some places this is error, i.e. in grsecurity script... yes, I know, I switched off > grsecurity, but...). > > But I can not boot build with kernel 3.1. I will experiment with next kernel. Dear Heiko, I have first 3.1.1-grsec 32-bit bootable (after adopting grsecurity name to "3.x" pattern) but I'm not sure why this, because in desperation I ran 4 parallel builds with different experiments and only one result is bootable. So I will build more systematically. Maybe kernel-patches are inadequate... Regards -- Andrzej Odyniec |
|
From: Andrzej O. <an...@ma...> - 2011-11-28 01:34:11
|
Heiko, > Don't use grsecurity if you want to use it as a build host for DL. It will > more than likely interfere with the compile. Yes. I know. This is the reason, why I first time run build without grsecurity. > All the kernel patches are usually at least a couple of days behind the main > kernel version. I just saw 3.1.3 is out and the grsec patch for it too. I saw this patches too. But anyway... D-L with kernel 3.1.2 built from scratch with last CVS sources on Debian base system (as for now 64-bit) and with default settings (only x86_64 and grsecurity off) does not loads kernel. I think, this is issue for 32-bit too. There is possible, that kernel is broken or Your changes in scripts (especially string 3.0 changed to 3.x --- in some places this is error, i.e. in grsecurity script... yes, I know, I switched off grsecurity, but...). But I can not boot build with kernel 3.1. I will experiment with next kernel. Regards Andrzej Odyniec |
|
From: Heiko Z. <he...@zu...> - 2011-11-27 14:36:01
|
Hey, > -----Original Message----- > From: Andrzej Odyniec [mailto:an...@ma...] > Sent: Saturday, November 26, 2011 5:51 PM > To: dev...@li... > Subject: Re: [Devil-linux-develop] Can not boot 3.1 kernel > > Heiko, > > Are you using the version with grsecurity? > > If yes, try updating the patch: > > http://grsecurity.net/test/grsecurity-2.2.2-3.1.1-201111201943.patch > > I tried compilation without grsecurity, because I need D-L as base to following > builds. This not loading builds was done on last 3.0.9 D-L base. So I now return > again to 64-bit Debian as base and run again build of last 3.1.1 on this Debian. > If this will load, problem is with D-L as base. If not, problem is maybe with > kernel compiling process or with 3.1.1 kernel. Don't use grsecurity if you want to use it as a build host for DL. It will more than likely interfere with the compile. > > I can't upload another test version right now to verify it's not your > > build host, since I'm having trouble all the sudden to get gcc compiled.... > > It's understandable. But there is no problem. I can pull grsecurity, if kernel > compiled without will load. It is interesting that the kernel.org address the > last stable as 3.1.2, but the last grsecurity test is targeted to kernel 3.1.1. It > may indeed be a problem with that kernel 3.1.1? All the kernel patches are usually at least a couple of days behind the main kernel version. I just saw 3.1.3 is out and the grsec patch for it too. -- Regards Heiko Zuerker http://www.devil-linux.org |
|
From: Andrzej O. <an...@ma...> - 2011-11-26 23:51:31
|
Heiko, > Are you using the version with grsecurity? > If yes, try updating the patch: > http://grsecurity.net/test/grsecurity-2.2.2-3.1.1-201111201943.patch I tried compilation without grsecurity, because I need D-L as base to following builds. This not loading builds was done on last 3.0.9 D-L base. So I now return again to 64-bit Debian as base and run again build of last 3.1.1 on this Debian. If this will load, problem is with D-L as base. If not, problem is maybe with kernel compiling process or with 3.1.1 kernel. > I can't upload another test version right now to verify it's not your build > host, since I'm having trouble all the sudden to get gcc compiled.... It's understandable. But there is no problem. I can pull grsecurity, if kernel compiled without will load. It is interesting that the kernel.org address the last stable as 3.1.2, but the last grsecurity test is targeted to kernel 3.1.1. It may indeed be a problem with that kernel 3.1.1? Regards Andrzej Odyniec |
|
From: Heiko Z. <he...@zu...> - 2011-11-26 13:53:22
|
Andrzej, Are you using the version with grsecurity? If yes, try updating the patch: http://grsecurity.net/test/grsecurity-2.2.2-3.1.1-201111201943.patch I can't upload another test version right now to verify it's not your build host, since I'm having trouble all the sudden to get gcc compiled.... -- Regards Heiko Zuerker http://www.devil-linux.org > -----Original Message----- > From: Andrzej Odyniec [mailto:an...@ma...] > Sent: Friday, November 25, 2011 8:17 PM > To: dev...@li... > Subject: [Devil-linux-develop] Can not boot 3.1 kernel > > Dear Heiko, > > I'm unable to boot the 3.1 kernel in 32-bit nor 64-bit version. Immediately > after the syslinux/isolinux menu, I have a black console screen. No matter > which VGA mode I choose (80x25 too). Compilation was with default settings > from scratch too. > > All 3.0.9 builds are booting ok. > > Mayby I need special config settings? > > Rgds > > Andrzej Odyniec > > ---------------------------------------------------------------------------- -- > All the data continuously generated in your IT infrastructure contains a > definitive record of customers, application performance, security threats, > fraudulent activity, and more. Splunk takes this data and makes sense of it. IT > sense. And common sense. > http://p.sf.net/sfu/splunk-novd2d > _______________________________________________ > Devil-linux-develop mailing list > Dev...@li... > https://lists.sourceforge.net/lists/listinfo/devil-linux-develop |
35 messages has been excluded from this view by a project administrator.
