devil-linux-develop — developer discussions

[Devil-linux-develop] [ devil-linux-Bugs-799495 ] ISO clean-up

[SourceForge.net <no...@so...>]

Bugs item #799495, was opened at 2003-09-02 19:43
Message generated for change (Settings changed) made by smiley73
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=410643&aid=799495&group_id=34096

Category: Configuration / Scripts
Group: None
>Status: Closed
>Resolution: Fixed
Priority: 5
Submitted By: Heiko Zuerker (smiley73)
>Assigned to: Heiko Zuerker (smiley73)
Summary: ISO clean-up

Initial Comment:
There are a lot of unnecessary files/directories on the
ISO image.
E.g. /usr/man , /usr/include, /usr/lib/*.a *.la


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=410643&aid=799495&group_id=34096

[Devil-linux-develop] [ devil-linux-Bugs-819423 ] ignoreip patch for djbdns

[SourceForge.net <no...@so...>]

Bugs item #819423, was opened at 2003-10-07 12:07
Message generated for change (Settings changed) made by smiley73
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=410643&aid=819423&group_id=34096

Category: Package
Group: None
>Status: Closed
>Resolution: Fixed
Priority: 5
Submitted By: Heiko Zuerker (smiley73)
>Assigned to: Heiko Zuerker (smiley73)
Summary: ignoreip patch for djbdns

Initial Comment:
http://tinydns.org//djbdns-1.05-ignoreip.patch

This patch changes djbdns's dnscache program so that 
it will ignore the
IP address given in the IGNOREIP environment variable.  
I wrote this
patch because of Verisign's oh-so helpful wildcard A 
records for *.COM
and *.NET.  Install the patch like this:
    patch <djbdns-1.05-ignoreip.patch
    svc -d /service/dnscache
    make setup check
    svc -u /service/dnscache

Configure it to ignore Verisign's wildcard record like this:
    echo 64.94.110.11 >/service/dnscache/env/IGNOREIP
    svc -t /service/dnscache

If IGNOREIP isn't found in the environment variable 
space, nothing is
ignored.



----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=410643&aid=819423&group_id=34096

Re: [Devil-linux-develop] 1.0RC1 - Notes from installation.

[Heiko Z. <he...@zu...>]

Dean Nedelman wrote:

>>>>Then you're probably willing to do some research on this:
>>>>Can you check if it is possible to resize the shmfs ?
>>>>The problem is that we can't umount it, because when you do that, it's
>>>>automatically emptied. :-((
>>>>        
>>>>
>>>I'll see what I can find out...
>>>      
>>>
>>See if the mount -oremount option works without emptying it.
>></guess>
>>    
>>
OK I added a new parameter (CHANGE_SHMFS_SIZE) to the boot script.
If defined the system will change the size of the ramdisk.

It will be included in 1.0.

cya
  Heiko

Re: [Devil-linux-develop] Squid.

[Heiko Z. <he...@zu...>]

Bruce Smith wrote:

>>>I need to replace a squid proxy server at work, and thought I'd try
>>>running it under DL.  After a little testing, squid runs fine, but I
>>>need an authorization module that is not compiled.
>>>
>>>Do you care if I enable all the basic authorization modules in the
>>>./configure statement in the squid build script in the 1.0 tree (all it
>>>does is add a few more binaries in /usr/bin)?  Or is it too frozen?
>>>      
>>>
>>You're allowed to fix bugs only !
>>
>>But when Squid is not installed completely (missing modules), it's a bug,
>>isn't it? ;-)
>>    
>>
>
>What if one of the missing modules needs a program not in DL?  :-)
>(module yp_auth needs ypbind)
>  
>
Do it for 1.11, I don't want to risk/delay the 1.0.
There's no problem for you to use a CVS version at the company.

cya
  Heiko

Re: [Devil-linux-develop] new branch

[Heiko Z. <he...@zu...>]

Heiko Zuerker wrote:

> Hey,
>
> so that we can start the development on 1.1, I created the cvs branch 
> rel-1-0-patches
>
> All changes/fixes to 1.0 have to be done in this branch !
> You can check it out with :
> cvs co  -r rel-1-0-patches build
>
> The main branch will hold the development version.
>
> Don't forgett that the FTP is not updated yet !

The FTP Server is updated, you can use it again.

Heiko

RE: [Devil-linux-develop] 1.0RC1 - Notes from installation.

[Dean N. <di...@ti...>]

>> >Then you're probably willing to do some research on this:
>> >Can you check if it is possible to resize the shmfs ?
>> >The problem is that we can't umount it, because when you do that, it's
>> >automatically emptied. :-((
>>
>> I'll see what I can find out...
>
>See if the mount -oremount option works without emptying it.
></guess>

Well, according to the research I've done so far - tmpfs (which is listed as
the shmfs replacement?) does allow the remount option to change the size on
the fly.  However, it also states that space used by the tmpfs is NOT
eligible for reclamation by the Out-Of-Memory recovery procedures.  And yes,
mount -o remount, size= does work.

On a side issue, I took a look at what was using the space (remember - this
is -with- Postfix, and -without- SAGATOR and ClamAV at this point).  Here is
the -brief- results:
Total Space: 30MB
Total Space Used: 20MB
Amount used by Postfix: 16MB
Amount used by Postfix's lib directory (/var/spool/postfix/lib): 14MB

So to me, this brings up an obvious question:
How come most of these "jails" can't be prebuilt and reside on the CDROM?
It seems to me that there are there "types" of files, and that some of these
could be built and reside on the CDROM:
o Files copied from /etc.  These can't be on the CDROM, because they didn't
come from the CDROM :-)
o Files from /lib, /usr, /dev, /bin, etc.  These could certainly be prebuilt
and reside on the CDROM.
o Files that are created dynamically.  Normally these are created by the
application.

Just my thoughts.

Dean Nedelman
TimeLord Consulting

Re: [Devil-linux-develop] Squid.

[Bruce S. <bw...@ar...>]

> >I need to replace a squid proxy server at work, and thought I'd try
> >running it under DL.  After a little testing, squid runs fine, but I
> >need an authorization module that is not compiled.
> >
> >Do you care if I enable all the basic authorization modules in the
> >./configure statement in the squid build script in the 1.0 tree (all it
> >does is add a few more binaries in /usr/bin)?  Or is it too frozen?
> 
> You're allowed to fix bugs only !
> 
> But when Squid is not installed completely (missing modules), it's a bug,
> isn't it? ;-)

What if one of the missing modules needs a program not in DL?  :-)
(module yp_auth needs ypbind)

 - BS

Re: [Devil-linux-develop] Squid.

[Heiko Z. <hz...@pr...>]

On 10/08/2003 04:09:57 PM Bruce Smith wrote:
>I need to replace a squid proxy server at work, and thought I'd try
>running it under DL.  After a little testing, squid runs fine, but I
>need an authorization module that is not compiled.
>
>Do you care if I enable all the basic authorization modules in the
>./configure statement in the squid build script in the 1.0 tree (all i=
t
>does is add a few more binaries in /usr/bin)?  Or is it too frozen?

You're allowed to fix bugs only !

But when Squid is not installed completely (missing modules), it's a bu=
g,
isn't it? ;-)

cya
  Heiko
=

[Devil-linux-develop] Squid.

[Bruce S. <bw...@ar...>]

I need to replace a squid proxy server at work, and thought I'd try
running it under DL.  After a little testing, squid runs fine, but I
need an authorization module that is not compiled.

Do you care if I enable all the basic authorization modules in the
./configure statement in the squid build script in the 1.0 tree (all it
does is add a few more binaries in /usr/bin)?  Or is it too frozen?

 - BS

RE: [Devil-linux-develop] 1.0RC1 - Notes from installation.

[Bruce S. <bw...@ar...>]

> >Then you're probably willing to do some research on this:
> >Can you check if it is possible to resize the shmfs ?
> >The problem is that we can't umount it, because when you do that, it's
> >automatically emptied. :-((
> 
> I'll see what I can find out...

See if the mount -oremount option works without emptying it.
</guess>

 - BS

RE: [Devil-linux-develop] 1.0RC1 - Notes from installation.

[Dean N. <di...@ti...>]

>>>>2) For some reason, I can no longer scroll backwards through the
>>console
>>>>messages on VC/1.  I noticed this when I wanted to scroll back and
>>get a
>>>>GRSec error and couldn't. I am using the "default" (non-framebuffer)
>>option
>>>>on boot
>>>>
>>>SHIFT + PGUP doesn't work?
>>>I just checked it on VMWare, it worked fine.
>>>Unfortunately I don't have any computers which don't support the VESA
>>mode.
>>
>>It is whatever option 0 (the non-framebuffer option) is.  I'm sure the
>>machine supports VESA - I just don't like the framebuffer modes.
>
>That was the version I tried.
>Are you sure that you didn't switch to another console and then back?
>Can you try it again?

You are right - when I tried it again, I had no errors.  So, it must have
been something I did that prevented me from going back (though I haven't a
clue as to what.)

>[...]
>Then you're probably willing to do some research on this:
>Can you check if it is possible to resize the shmfs ?
>The problem is that we can't umount it, because when you do that, it's
>automatically emptied. :-((

I'll see what I can find out...

Dean

Re: [Devil-linux-develop] 1.0RC1 - Notes from installation.

[Heiko Z. <hz...@pr...>]

On 10/08/2003 11:18:13 AM Bruce Smith wrote:
>> >On my latest ISO w/o memtest86, it shows on the menu but doesn't
>work.
>> >
>> >Looks like it's because you do this line UNCONDITIONALLY:
>> >
>> >echo -n -e "  M - MEMTEST86\r\n\r\n" >> $CDDIR/boot/message
>> >
>> >You only check for memtest when creating isolinux.cfg.
>>
>> OOPS
>
>I'll let you fix it, since I'm not sure where my changes go
>if I commit something now ...   :-)

It will go into 1.1
You have to checkout rel-1-0-patches for the 1.0 branch

Heiko
=

Re: [Devil-linux-develop] 1.0RC1 - Notes from installation.

[Bruce S. <bw...@ar...>]

> >On my latest ISO w/o memtest86, it shows on the menu but doesn't work.
> >
> >Looks like it's because you do this line UNCONDITIONALLY:
> >
> >echo -n -e "  M - MEMTEST86\r\n\r\n" >> $CDDIR/boot/message
> >
> >You only check for memtest when creating isolinux.cfg.
> 
> OOPS

I'll let you fix it, since I'm not sure where my changes go 
if I commit something now ...   :-)

 - BS

Re: [Devil-linux-develop] 1.0RC1 - Notes from installation.

[Heiko Z. <hz...@pr...>]

On 10/08/2003 09:53:15 AM Bruce Smith wrote:
>> >> >> 1) Memtest works!  Though I couldn't use 'M' (as the option
>> >> >indicated), but
>> >> >> rather 'm'.
>> >> >
>> >> >I recommend changing the install script for memtest.  If it's no=
t
>> >> >selected in menuconfig, the option should not be offered on boot=
.
>> >>
>> >> That's the way it is, isn't it?
>> >> It's done in the build-iso script.
>> >
>> >Ah, OK.  I was looking in scripts/memtest86 and didn't see it there=
.
>>
>> It had to be in there, because we create the isolinux.cfg dynamicall=
y.
>
>On my latest ISO w/o memtest86, it shows on the menu but doesn't work.=

>
>Looks like it's because you do this line UNCONDITIONALLY:
>
>echo -n -e "  M - MEMTEST86\r\n\r\n" >> $CDDIR/boot/message
>
>You only check for memtest when creating isolinux.cfg.

OOPS

Heiko
=

Re: [Devil-linux-develop] 1.0RC1 - Notes from installation.

[Bruce S. <bw...@ar...>]

> >> >> 1) Memtest works!  Though I couldn't use 'M' (as the option
> >> >indicated), but
> >> >> rather 'm'.
> >> >
> >> >I recommend changing the install script for memtest.  If it's not
> >> >selected in menuconfig, the option should not be offered on boot.
> >>
> >> That's the way it is, isn't it?
> >> It's done in the build-iso script.
> >
> >Ah, OK.  I was looking in scripts/memtest86 and didn't see it there.
> 
> It had to be in there, because we create the isolinux.cfg dynamically.

On my latest ISO w/o memtest86, it shows on the menu but doesn't work.

Looks like it's because you do this line UNCONDITIONALLY:

 echo -n -e "  M - MEMTEST86\r\n\r\n" >> $CDDIR/boot/message

You only check for memtest when creating isolinux.cfg.

 - BS

Re: [Devil-linux-develop] 1.0RC1 - Notes from installation.

[Heiko Z. <hz...@pr...>]

On 10/08/2003 08:58:10 AM Bruce Smith wrote:
>> >> 1) Memtest works!  Though I couldn't use 'M' (as the option
>> >indicated), but
>> >> rather 'm'.
>> >
>> >I recommend changing the install script for memtest.  If it's not
>> >selected in menuconfig, the option should not be offered on boot.
>>
>> That's the way it is, isn't it?
>> It's done in the build-iso script.
>
>Ah, OK.  I was looking in scripts/memtest86 and didn't see it there.

It had to be in there, because we create the isolinux.cfg dynamically.

Heiko
=

Re: [Devil-linux-develop] Different release download options.

[Bruce S. <bw...@ar...>]

> >Wow, if I did the math right, this is just under 128MB!!!  :-)
> 
> Until the next DL release ;-)

One release at a time ...   :-)

> >-rw-r--r--    1 root     root     133332992 Oct  7 15:51 bootcd.iso
> >
> >My .config file is attached if you want to see my selections.
> 
> For a pure firewall, you could reduce it even more.
> I.e. No man pages and no documentation.
> I'm pretty sure you can also remove some more binaries.

That was only a quick first try to get a rough idea of the ISO size.
I can fine tune it more now.

 - BS

Re: [Devil-linux-develop] 1.0RC1 - Notes from installation.

[Bruce S. <bw...@ar...>]

> >> 1) Memtest works!  Though I couldn't use 'M' (as the option
> >indicated), but
> >> rather 'm'.
> >
> >I recommend changing the install script for memtest.  If it's not
> >selected in menuconfig, the option should not be offered on boot.
> 
> That's the way it is, isn't it?
> It's done in the build-iso script.

Ah, OK.  I was looking in scripts/memtest86 and didn't see it there.

I'll take it out of my "firewall only" .config and make sure it works.

 - BS

Re: [Devil-linux-develop] 1.0RC1 - Notes from installation.

[Heiko Z. <hz...@pr...>]

On 10/08/2003 08:31:02 AM Bruce Smith wrote:
>> 1) Memtest works!  Though I couldn't use 'M' (as the option
>indicated), but
>> rather 'm'.
>
>I recommend changing the install script for memtest.  If it's not
>selected in menuconfig, the option should not be offered on boot.

That's the way it is, isn't it?
It's done in the build-iso script.

Heiko
=

Re: [Devil-linux-develop] 1.0RC1 - Notes from installation.

[Bruce S. <bw...@ar...>]

> 1) Memtest works!  Though I couldn't use 'M' (as the option indicated), but
> rather 'm'.

I recommend changing the install script for memtest.  If it's not
selected in menuconfig, the option should not be offered on boot.

 - BS

[Devil-linux-develop] [ devil-linux-Feature Requests-819940 ] add l7-filer

[SourceForge.net <no...@so...>]

Feature Requests item #819940, was opened at 2003-10-08 07:15
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=410646&aid=819940&group_id=34096

Category: Base System
Group: None
Status: Open
Priority: 5
Submitted By: Heiko Zuerker (smiley73)
Assigned to: Nobody/Anonymous (nobody)
Summary: add l7-filer

Initial Comment:
http://l7-filter.sourceforge.net/

We (Justin Levandoski, Ethan Sommer and Matthew 
Strait) have created a filter (or classifier) to classify 
packets based on application (or layer 7) data in the 
connections they belong to. This means that we can 
classify packets as HTTP, FTP, Gnucleus, etc, 
regardless of what port the services are run on. Our 
filter complements existing filters that classify based on 
route, port numbers and so on.



----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=410646&aid=819940&group_id=34096

RE: [Devil-linux-develop] 1.0RC1 - Notes from installation.

[Heiko Z. <hz...@pr...>]

On 10/07/2003 10:03:19 PM "Dean Nedelman" wrote:
>>>2) For some reason, I can no longer scroll backwards through the
>console
>>>messages on VC/1.  I noticed this when I wanted to scroll back and
>get a
>>>GRSec error and couldn't. I am using the "default" (non-framebuffer)=

>option
>>>on boot
>>>
>>SHIFT + PGUP doesn't work?
>>I just checked it on VMWare, it worked fine.
>>Unfortunately I don't have any computers which don't support the VESA=

>mode.
>
>It is whatever option 0 (the non-framebuffer option) is.  I'm sure the=

>machine supports VESA - I just don't like the framebuffer modes.

That was the version I tried.
Are you sure that you didn't switch to another console and then back?
Can you try it again?

>>>3) I am still getting the grsec resource errors.  I believe they are=

>comming
>>>from /etc/sysconfig/network/scripts/dhcpcd.exe - and yes, even if I
>use
>the
>>>distrubted one:
>>>
>>>Starting DHCP client daemon on interface eth0
>>>grsec: attempted resource overstep by requesting 37695488 for
>RLIMIT_STACK
>>>against limit 8388608 by (pidof:381) UID(0) EUID(0), parent
>(S05network:370)
>>>UID(0) EUID(0)
>>>grsec: attempted resource overstep by requesting 77271040 for
>RLIMIT_STACK
>>>against limit 8388608 by (pidof:381) UID(0) EUID(0), parent
>(S05network:370)
>>>UID(0) EUID(0)
>>>
>>I don't use DHCP and I couldn't reproduce the problem with my test
>config.
>>Can you send me your /etc/dhcpd.conf ?
>
>I'm not running the dhcp server (which is what /etc/dhcpd.conf is
>for.)  For
>the dhcp CLIENT, the only changes I made to the distributed config fil=
e
>(/etc/sysconfig/network/dhcp) is the following:
>o set DHCLIENT_DEBUG to "no"
>o set DHCLIENT_MODIFY_RESOLV_CONF to "no"
>o set DHCLIENT_HOSTNAME_OPTION to ""
>
>The error messages refer to the program "pidof" - and I believe the
>complaint is about the one in /etc/sysconfig/network/scripts/dhcpcd.ex=
e.

I'll check on the client part tonight.
But this should be a commonly used option.....

>>>5) Starting SAGATOR fails with:
>>>
>>>creating chroot jail for SAGATOR.....cp: writting
>>>`/var/spool/vscan/lib/libc-2.3.2.so': No space left on device
>>>And similar cp: errors for another 9 files
>>>...
>>>.sed: Couldn't flush stdout: No space left on device
>>>Warning: no source refers to internal message, they'll go to /dev/nu=
ll
>>>
>>You need more RAM. ;-)
>
>I have 64MB!

We're waisting it, arent we? ;-)

>>[...]
>>Since the shmfs was eating up more space then it should have, we (I)
>>switched to the default which is RAM / 2
>>You really should upgrade to at least 128 MB, this helps a lot. ;-)
>
>Right now, such an expenditure is not an option (been unemployed for t=
he
>last 18 months!)

That really sucks !
Then you're probably willing to do some research on this:
Can you check if it is possible to resize the shmfs ?
The problem is that we can't umount it, because when you do that, it's
automatically emptied. :-((

>>>6) PowerOFF WORKED!
>>>
>>>
>>Finally!
>>This time I would have mailed you a bomb or something... ;-)
>
>After 18 months of employment - a bomb would have made for welcome
>change

Would be more like a mail-bomb or so. ;-)

cya
  Heiko
=

[Devil-linux-develop] [fmII] distcc 2.11.1 released (Default branch)

[<no...@fr...>]

This email is to inform you about the release of version '2.11.1' of
'distcc' through freshmeat.net. All URLs and other useful information can
be found at

    http://freshmeat.net/projects/distcc/

The changes in this release are as follows:
Some error handling, portability, and documentation  bugs were fixed.
The graphical monitor can now  optionally be built with just GTK+ and
not GNOME. 

Project description:
distcc is a parallel build system that distributes compilation of
C/C++/ObjC code across machines on a network. It can be set up in
just a few minutes and makes builds up to ten times faster. It does
not require machines to share a filesystem or have the same libraries
or header files, and installation does not need superuser privileges. 

If you would like to cancel subscription to releases of this project,
login to freshmeat.net and choose 'home' from the personal menubar at the
top of the page. You'll be presented with a list of projects you're
subscribed to in the right column, which you may cancel by highlighting
the project in question and clicking the 'delete' button.

Sincerely,
freshmeat.net 

RE: [Devil-linux-develop] 1.0RC1 - Notes from installation.

[Dean N. <di...@ti...>]

>>2) For some reason, I can no longer scroll backwards through the console
>>messages on VC/1.  I noticed this when I wanted to scroll back and get a
>>GRSec error and couldn't. I am using the "default" (non-framebuffer)
option
>>on boot
>>
>SHIFT + PGUP doesn't work?
>I just checked it on VMWare, it worked fine.
>Unfortunately I don't have any computers which don't support the VESA mode.

It is whatever option 0 (the non-framebuffer option) is.  I'm sure the
machine supports VESA - I just don't like the framebuffer modes.

>>3) I am still getting the grsec resource errors.  I believe they are
comming
>>from /etc/sysconfig/network/scripts/dhcpcd.exe - and yes, even if I use
the
>>distrubted one:
>>
>>Starting DHCP client daemon on interface eth0
>>grsec: attempted resource overstep by requesting 37695488 for RLIMIT_STACK
>>against limit 8388608 by (pidof:381) UID(0) EUID(0), parent
(S05network:370)
>>UID(0) EUID(0)
>>grsec: attempted resource overstep by requesting 77271040 for RLIMIT_STACK
>>against limit 8388608 by (pidof:381) UID(0) EUID(0), parent
(S05network:370)
>>UID(0) EUID(0)
>>
>I don't use DHCP and I couldn't reproduce the problem with my test config.
>Can you send me your /etc/dhcpd.conf ?

I'm not running the dhcp server (which is what /etc/dhcpd.conf is for.)  For
the dhcp CLIENT, the only changes I made to the distributed config file
(/etc/sysconfig/network/dhcp) is the following:
o set DHCLIENT_DEBUG to "no"
o set DHCLIENT_MODIFY_RESOLV_CONF to "no"
o set DHCLIENT_HOSTNAME_OPTION to ""

The error messages refer to the program "pidof" - and I believe the
complaint is about the one in /etc/sysconfig/network/scripts/dhcpcd.exe.

>>
>>5) Starting SAGATOR fails with:
>>
>>creating chroot jail for SAGATOR.....cp: writting
>>`/var/spool/vscan/lib/libc-2.3.2.so': No space left on device
>>And similar cp: errors for another 9 files
>>...
>>.sed: Couldn't flush stdout: No space left on device
>>Warning: no source refers to internal message, they'll go to /dev/null
>>
>You need more RAM. ;-)

I have 64MB!

>[...]
>Since the shmfs was eating up more space then it should have, we (I)
>switched to the default which is RAM / 2
>You really should upgrade to at least 128 MB, this helps a lot. ;-)

Right now, such an expenditure is not an option (been unemployed for the
last 18 months!)

>>6) PowerOFF WORKED!
>>
>>
>Finally!
>This time I would have mailed you a bomb or something... ;-)

After 18 months of employment - a bomb would have made for welcome change
:-)

Dean Nedelman
TimeLord Consulting

[Devil-linux-develop] new branch

[Heiko Z. <he...@zu...>]

Hey,

so that we can start the development on 1.1, I created the cvs branch 
rel-1-0-patches

All changes/fixes to 1.0 have to be done in this branch !
You can check it out with :
cvs co  -r rel-1-0-patches build

The main branch will hold the development version.

Don't forgett that the FTP is not updated yet !

cya
  Heiko