devil-linux-develop Mailing List for Devil-Linux (Page 36)

Bruce Smith wrote:
> I ran a fresh compile after the latest updates, and nagios-plugins
> aborted.  Compatibility problem with the new kernel?  Anyone else have
> this problem?

I've started fresh compile and try to find out the reason.

--
Serge

I ran a fresh compile after the latest updates, and nagios-plugins
aborted.  Compatibility problem with the new kernel?  Anyone else have
this problem?

 - BS

I just booted up with devil-linux-1.3.5-2008-05-02-i586 without any bother.  No 
intervention at all! I hope not too good to be true.

The copy to ram works.

The only issue I have is the hotplug delay. If I run the /etc/hotplug/*rc 
scripts I get about 15s delay with usb.rc and about twice that with pci.rc.
I've no idea what they're doing.

Isn't hotplug depricated now there's udev; do we actually need to run the 
hotplug scripts?

Dick

Hello,

Serge Leschinsky wrote:

> Probably I found out a bug in procinfo (not critical, of course)
> 
> root@Devil:~ # uptime
>  04:17:40 up 65 days, 20:44,  1 user,  load average: 0.00, 0.00, 0.00
> root@Devil:~ # procinfo | grep uptime
> uptime:   1d  5:47:06.00         context :235715659     interrupts: 29951675
> 

root@Devil:~ # uptime
 05:38:42 up 74 days, 22:05,  1 user,  load average: 0.00, 0.00, 0.00
root@Devil:~ # /tmp/procinfo | grep uptime
uptime:  74d 22:05:37.29         context :245915561     interrupts: 30975704

Patched procinfo shows uptime correctly. I borrowed the patches from Fedora
project and going to add them to DL.

--
Serge

> > OK, I packaged up the latest 1.3.5 I've been working on (all bugs fixed
> > that I know about), and uploaded it to the FTP server.
> 
> Brilliant! Something to play with over the weekend!
> 
> What's the ftp server?  I usually use Linjection but it takes a while to 
> get there.

Why, ftp.devil-linux.org of course!  :-)

The mirrors should be updated in the next day or so.

 - BS

Bruce Smith wrote:
> OK, I packaged up the latest 1.3.5 I've been working on (all bugs fixed
> that I know about), and uploaded it to the FTP server.

Brilliant! Something to play with over the weekend!

What's the ftp server?  I usually use Linjection but it takes a while to 
get there.

Dick

Take a look at the kernel sources.
Documentation/fb/fbcon.txt
Documentation/console/console.txt

I skimmed over it, sounds like making vesafb and including vbetool may  
do the trick.

-- 

Regards
   Heiko Zuerker
   http://www.devil-linux.org



Quoting Bruce Smith <br...@ar...>:

>> >> Maybe there's a program out there which can be used to change the
>> >> resolution after the system is booted up.
>> >
>> > That would be a good option.  What's the name of the program?
>>
>> The name is "Maybe there's a program out there..." ;-)
>> No clue if there really is such a thing, it's just a hope, ask Google.
>
> http://asm.sourceforge.net/articles/fb.html
>
> ... "vesafb supports only a subset of all fb device operations
> i.e. you can't change the resolution or color depth after boot." ...
>
> Oh well, at least the default for the server version is 1024x768 now! :)
>
>  - BS
>
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
> Don't miss this year's exciting event. There's still time to save $100.
> Use priority code J8TL2D2.
> http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
> _______________________________________________
> Devil-linux-develop mailing list
> Dev...@li...
> https://lists.sourceforge.net/lists/listinfo/devil-linux-develop
>



----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

> >> Maybe there's a program out there which can be used to change the
> >> resolution after the system is booted up.
> >
> > That would be a good option.  What's the name of the program?
> 
> The name is "Maybe there's a program out there..." ;-)
> No clue if there really is such a thing, it's just a hope, ask Google.

http://asm.sourceforge.net/articles/fb.html

... "vesafb supports only a subset of all fb device operations 
i.e. you can't change the resolution or color depth after boot." ...

Oh well, at least the default for the server version is 1024x768 now! :)

 - BS

Bruce,

> I would like to be able to change the default for the resolution, so it
> remembers it for future boots.  i.e. I want to be select "3" (1024x768)
> and have it remember that setting so I don't have to type 3 every boot.
> 
> Does anyone know if that's possible with a "better menu system"?

Problem is, as you know, that it's set in the isolinux config which is on ro 
media. For usb users there is an opportunity to preset the default as the files 
are copied to the usb stick.  I'm not sure that solution is worth the effort. 
My DL system typically runs 6mths between reboots.

> If not, what would happen if I changed the official "server release" to
> default to 1024x768? And I REALLY get sick of trying to catch the boot prompt
> and typing "3" when I'm rebooting a lot during development.

I'm right with you here!  Let the legacy boys do the running :-)

Dick

> > While I'm at it, do you care if I add options for 1280x1024 and
> > 1600x1200 to the boot menu?
> 
> Does this mean I have to buy a bigger display now?

And a better video card too!  :-)

> No go ahead and add it.

OK, I added them, and much to my surprise, neither mode is supported in
VMware ESX-3i.

However ... both gave me the message about invalid mode, press ENTER to
see the modes available, or wait 30 seconds.

I waited 30 seconds, and it booted up in standard VGA mode without any
manual intervention.  So, I'm going to also change the default on the
server release to "3" 1024x768.

And for the impatient, I'll check in the changes SOON!  :-)

 - BS

Quoting Bruce Smith <bw...@ar...>:

>> > > If not, what would happen if I changed the official "server release" to
>> > > default to 1024x768?  I know some hardware doesn't support higher
>> > > resolutions, but would it prevent the system from booting without manual
>> > > intervention, or would the system just print an warning and continue
>> > > booting at a lower resolution?  I don't think I have any old hardware to
>> > > test this on.  And I REALLY get sick of trying to catch the boot prompt
>> > > and typing "3" when I'm rebooting a lot during development.
>> >
>> > Set vga=2137 or some other invalid value and see what the system does.
>>
>> OK, I'll give it a try.  Thanks!
>
> While I'm at it, do you care if I add options for 1280x1024 and
> 1600x1200 to the boot menu?

Does this mean I have to buy a bigger display now?

No go ahead and add it.

-- 

Regards
   Heiko Zuerker
   http://www.devil-linux.org



----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

> > > If not, what would happen if I changed the official "server release" to
> > > default to 1024x768?  I know some hardware doesn't support higher
> > > resolutions, but would it prevent the system from booting without manual
> > > intervention, or would the system just print an warning and continue
> > > booting at a lower resolution?  I don't think I have any old hardware to
> > > test this on.  And I REALLY get sick of trying to catch the boot prompt
> > > and typing "3" when I'm rebooting a lot during development.
> > 
> > Set vga=2137 or some other invalid value and see what the system does.
> 
> OK, I'll give it a try.  Thanks!

While I'm at it, do you care if I add options for 1280x1024 and
1600x1200 to the boot menu?

 - BS

Quoting Bruce Smith <bw...@ar...>:

>> >> Should I check it in with only -fno-stack-protector ?
>> >> Or is there any other options that should go with it?
>> >
>> > No, I would just stick with that.
>>
>> When are you planning to check in the changes, since I would like to
>> start a compile.
>
> How about yesterday afternoon?  Is that soon enough?  ;-)
>
>
> root@lx1:/data/build# less scripts/php
> #!/bin/bash
> # $Source: /cvsroot/devil-linux/build/scripts/php,v $
> # $Revision: 1.18 $
> # $Date: 2008/04/30 15:45:57 $
> ...
>      make CC="gcc -fno-stack-protector" $PMAKE all || exit 1
> ...
>
> root@lx1:/data/build# cvs_sf diff scripts/php
> root@lx1:/data/build#
>
>
> root@lx1:/data/build# less CHANGES
> ...
> - fixed php file upload bug (bs)
> ...
>
> root@lx1:/data/build# cvs_sf diff CHANGES
> root@lx1:/data/build#
>

Darn.... ;-)

-- 

Regards
   Heiko Zuerker
   http://www.devil-linux.org





----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

> >> Maybe there's a program out there which can be used to change the
> >> resolution after the system is booted up.
> >
> > That would be a good option.  What's the name of the program?
> 
> The name is "Maybe there's a program out there..." ;-)
> No clue if there really is such a thing, it's just a hope, ask Google.

Sorry, missed the "maybe" the first time around ...

 - BS

> >> Should I check it in with only -fno-stack-protector ?
> >> Or is there any other options that should go with it?
> >
> > No, I would just stick with that.
> 
> When are you planning to check in the changes, since I would like to  
> start a compile.

How about yesterday afternoon?  Is that soon enough?  ;-)


root@lx1:/data/build# less scripts/php 
#!/bin/bash
# $Source: /cvsroot/devil-linux/build/scripts/php,v $
# $Revision: 1.18 $
# $Date: 2008/04/30 15:45:57 $
...
     make CC="gcc -fno-stack-protector" $PMAKE all || exit 1
...

root@lx1:/data/build# cvs_sf diff scripts/php 
root@lx1:/data/build# 


root@lx1:/data/build# less CHANGES
...
- fixed php file upload bug (bs)
...

root@lx1:/data/build# cvs_sf diff CHANGES
root@lx1:/data/build# 


 - BS

Quoting Bruce Smith <bw...@ar...>:

>> > I would like to be able to change the default for the resolution, so it
>> > remembers it for future boots.  i.e. I want to be select "3" (1024x768)
>> > and have it remember that setting so I don't have to type 3 every boot.
>> >
>> > Does anyone know if that's possible with a "better menu system"?
>>
>> Well we do not have an option to save the setting.
>> BUT
>> Maybe there's a program out there which can be used to change the
>> resolution after the system is booted up.
>
> That would be a good option.  What's the name of the program?

The name is "Maybe there's a program out there..." ;-)
No clue if there really is such a thing, it's just a hope, ask Google.

>> > If not, what would happen if I changed the official "server release" to
>> > default to 1024x768?  I know some hardware doesn't support higher
>> > resolutions, but would it prevent the system from booting without manual
>> > intervention, or would the system just print an warning and continue
>> > booting at a lower resolution?  I don't think I have any old hardware to
>> > test this on.  And I REALLY get sick of trying to catch the boot prompt
>> > and typing "3" when I'm rebooting a lot during development.
>>
>> Set vga=2137 or some other invalid value and see what the system does.
>
> OK, I'll give it a try.  Thanks!
>


-- 

Regards
   Heiko Zuerker
   http://www.devil-linux.org


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

> > I would like to be able to change the default for the resolution, so it
> > remembers it for future boots.  i.e. I want to be select "3" (1024x768)
> > and have it remember that setting so I don't have to type 3 every boot.
> >
> > Does anyone know if that's possible with a "better menu system"?
> 
> Well we do not have an option to save the setting.
> BUT
> Maybe there's a program out there which can be used to change the  
> resolution after the system is booted up.

That would be a good option.  What's the name of the program?

> > If not, what would happen if I changed the official "server release" to
> > default to 1024x768?  I know some hardware doesn't support higher
> > resolutions, but would it prevent the system from booting without manual
> > intervention, or would the system just print an warning and continue
> > booting at a lower resolution?  I don't think I have any old hardware to
> > test this on.  And I REALLY get sick of trying to catch the boot prompt
> > and typing "3" when I'm rebooting a lot during development.
> 
> Set vga=2137 or some other invalid value and see what the system does.

OK, I'll give it a try.  Thanks!

 - BS

Quoting Heiko Zuerker <he...@zu...>:

>
> Quoting Bruce Smith <bw...@ar...>:
>
>>> >> You can turn it off globally via menuconfig (requires are mrproper) or
>>> >> for specific programs by adding
>>> >> CC="gcc -fPIC -fno-stack-protector -U_FORTIFY_SOURCE -nonow -nopie" to
>>> >> the make statement.
>>> > Assuming that works, any idea what option(s) are most likely to solve
>>> > the problem on PHP, so I can try them first?
>>>
>>> Try the fortify source first, then I'd play with the pie stuff
>>
>> OK, I tried just -U_FORTIFY_SOURCE first.  No good.
>> Then I added -nopie and compiled php again.  No good.
>> Then I added -fno-stack-protector.  And it worked (with all three).
>>
>> Then I removed the first two options and compiled with ONLY
>> -fno-stack-protector.  And ... it still works.
>>
>> Should I check it in with only -fno-stack-protector ?
>> Or is there any other options that should go with it?
>
>
> No, I would just stick with that.

When are you planning to check in the changes, since I would like to  
start a compile.

-- 

Regards
   Heiko Zuerker
   http://www.devil-linux.org


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

Quoting Bruce Smith <bw...@ar...>:

>> This unfortunately won't work, since we're booting of a CD.
>> ISOLinux has a lot of improvements in the menu systems in the latest
>> release, somebody wants to send in a patch for a better menu system
>> during boot?
>
> Since we're looking at boot improvements, here's what I'd like:
>
> I would like to be able to change the default for the resolution, so it
> remembers it for future boots.  i.e. I want to be select "3" (1024x768)
> and have it remember that setting so I don't have to type 3 every boot.
>
> Does anyone know if that's possible with a "better menu system"?

Well we do not have an option to save the setting.
BUT
Maybe there's a program out there which can be used to change the  
resolution after the system is booted up.

> If not, what would happen if I changed the official "server release" to
> default to 1024x768?  I know some hardware doesn't support higher
> resolutions, but would it prevent the system from booting without manual
> intervention, or would the system just print an warning and continue
> booting at a lower resolution?  I don't think I have any old hardware to
> test this on.  And I REALLY get sick of trying to catch the boot prompt
> and typing "3" when I'm rebooting a lot during development.

Set vga=2137 or some other invalid value and see what the system does.

-- 

Regards
   Heiko Zuerker
   http://www.devil-linux.org



----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

> This unfortunately won't work, since we're booting of a CD.
> ISOLinux has a lot of improvements in the menu systems in the latest  
> release, somebody wants to send in a patch for a better menu system  
> during boot?

Since we're looking at boot improvements, here's what I'd like:

I would like to be able to change the default for the resolution, so it
remembers it for future boots.  i.e. I want to be select "3" (1024x768)
and have it remember that setting so I don't have to type 3 every boot.

Does anyone know if that's possible with a "better menu system"?

If not, what would happen if I changed the official "server release" to
default to 1024x768?  I know some hardware doesn't support higher
resolutions, but would it prevent the system from booting without manual
intervention, or would the system just print an warning and continue
booting at a lower resolution?  I don't think I have any old hardware to
test this on.  And I REALLY get sick of trying to catch the boot prompt
and typing "3" when I'm rebooting a lot during development.

 - BS

Quoting "ee...@fr..." <ee...@fr...>:

> hi,
>
> Bruce Smith a écrit :
>> Oliver,
>>
>>
>>> btw. There is a "big" discussion about Union FS.
>>> I use different USB-sticks for my purposes:
>>> I plug stick #1 in, if i need DL for monitoring and
>>> #2 if i need a firewall.
>>>
>>> What if i could use config #1 as default and #2 on demand?
>>> Everything is stored on the same device?
>>> That would be useful for me, what's your opinion??
>>
>>
>> I looked at the source, and that functionality already exists.
>> It's kind of documented in the F1 / F2 / F3 help boot screens
>> (where you change the boot resolution for the console).
>>
>> I tested it by copying:
>> /floppy/etc-mods.tar.bz2 to /floppy/test.tar.bz2
>>
>> rebooting, and at the first boot prompt, typing:
>>
>>
>> 3 DL_config=/dev/fd0:test.tar.bz2
>>
>>
>
> Maybe using grub and having /boot/grub/menu.lst a symlink to e.g.
> /etc/grub/menu.lst could add some "comfort" ...

This unfortunately won't work, since we're booting of a CD.
ISOLinux has a lot of improvements in the menu systems in the latest  
release, somebody wants to send in a patch for a better menu system  
during boot?

-- 

Regards
   Heiko Zuerker
   http://www.devil-linux.org



----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

hi,

Bruce Smith a écrit :
> Oliver,
> 
> 
>> btw. There is a "big" discussion about Union FS.
>> I use different USB-sticks for my purposes:
>> I plug stick #1 in, if i need DL for monitoring and
>> #2 if i need a firewall.
>>
>> What if i could use config #1 as default and #2 on demand?
>> Everything is stored on the same device?
>> That would be useful for me, what's your opinion??
> 
> 
> I looked at the source, and that functionality already exists.
> It's kind of documented in the F1 / F2 / F3 help boot screens
> (where you change the boot resolution for the console).
> 
> I tested it by copying:
> /floppy/etc-mods.tar.bz2 to /floppy/test.tar.bz2
> 
> rebooting, and at the first boot prompt, typing:
> 
> 
> 3 DL_config=/dev/fd0:test.tar.bz2
> 
> 

Maybe using grub and having /boot/grub/menu.lst a symlink to e.g. 
/etc/grub/menu.lst could add some "comfort" ...


MaNU

> (where the "3" is the 1024x768 resolution)
> and it booted using my "test" config.
> 
> - BS
> 
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
> Don't miss this year's exciting event. There's still time to save $100. 
> Use priority code J8TL2D2. 
> http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
> _______________________________________________
> Devil-linux-develop mailing list
> Dev...@li...
> https://lists.sourceforge.net/lists/listinfo/devil-linux-develop
> 

Quoting Bruce Smith <bw...@ar...>:

>> >> You can turn it off globally via menuconfig (requires are mrproper) or
>> >> for specific programs by adding
>> >> CC="gcc -fPIC -fno-stack-protector -U_FORTIFY_SOURCE -nonow -nopie" to
>> >> the make statement.
>> > Assuming that works, any idea what option(s) are most likely to solve
>> > the problem on PHP, so I can try them first?
>>
>> Try the fortify source first, then I'd play with the pie stuff
>
> OK, I tried just -U_FORTIFY_SOURCE first.  No good.
> Then I added -nopie and compiled php again.  No good.
> Then I added -fno-stack-protector.  And it worked (with all three).
>
> Then I removed the first two options and compiled with ONLY
> -fno-stack-protector.  And ... it still works.
>
> Should I check it in with only -fno-stack-protector ?
> Or is there any other options that should go with it?


No, I would just stick with that.

>> (now I'm getting hungry).
>
> <homer simpson voice>
> Ummmmm, pie ...
> </duh!>   :-)
>
> But the "pie stuff" didn't work, so NO PIE FOR YOU!  ;-)
> </variation on Seinfeld soup episode>

Oh man....

> Hey, you started it!  :-)

Yeah I have a tendency of doing things like that.

Heiko

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

Oliver,


> btw. There is a "big" discussion about Union FS.
> I use different USB-sticks for my purposes:
> I plug stick #1 in, if i need DL for monitoring and
> #2 if i need a firewall.
> 
> What if i could use config #1 as default and #2 on demand?
> Everything is stored on the same device?
> That would be useful for me, what's your opinion??


I looked at the source, and that functionality already exists.
It's kind of documented in the F1 / F2 / F3 help boot screens
(where you change the boot resolution for the console).

I tested it by copying:
/floppy/etc-mods.tar.bz2 to /floppy/test.tar.bz2

rebooting, and at the first boot prompt, typing:


3 DL_config=/dev/fd0:test.tar.bz2


(where the "3" is the 1024x768 resolution)
and it booted using my "test" config.

- BS

> >> You can turn it off globally via menuconfig (requires are mrproper) or
> >> for specific programs by adding
> >> CC="gcc -fPIC -fno-stack-protector -U_FORTIFY_SOURCE -nonow -nopie" to
> >> the make statement.
> > Assuming that works, any idea what option(s) are most likely to solve
> > the problem on PHP, so I can try them first?
> 
> Try the fortify source first, then I'd play with the pie stuff

OK, I tried just -U_FORTIFY_SOURCE first.  No good.
Then I added -nopie and compiled php again.  No good.
Then I added -fno-stack-protector.  And it worked (with all three).

Then I removed the first two options and compiled with ONLY
-fno-stack-protector.  And ... it still works.

Should I check it in with only -fno-stack-protector ?
Or is there any other options that should go with it?


> (now I'm getting hungry).

<homer simpson voice>
Ummmmm, pie ...
</duh!>   :-)

But the "pie stuff" didn't work, so NO PIE FOR YOU!  ;-)
</variation on Seinfeld soup episode>

Hey, you started it!  :-)

 - BS