devil-linux-develop — developer discussions

Re: [Devil-linux-develop] Last minute stuff for 1.2 - and MySQL question.

[Friedrich L. <fl...@fl...>]

Bruce Smith wrote on 14.04.2004 16:37 MET:
> I'm working on adding PostgreSQL server now, and am about done except
> for testing and creating an init.d script.
> 
> Looking at the MySQL build/install script makes me ask why is the client
> and server are separate options in menuconfig?  According to the install
> script, the server binaries are being installed even if _only_ the
> client option is selected.

That's what I would definitely call a bug.

> All the server option gains you is to copy
> the init.d script and echo a couple lines in /etc/sysconfig/config.
> 
> So, unless I hear a strong objection really soon, I'm going to combine
> the "MySQL server" and "MySQL Client" menuconfig options into a single
> "MySQL" option.
> 
> Likewise, PostgreSQL is only going to have one option in menuconfig.

In a real "firewall-only" profile I would only want the postgres client 
side as I would want ipac-ng to send accounting data to the db server.

So I would urge you to rather fix the "problem" so there is really a 
separation between the client- and the server part of both MySQL and 
PostgreSQL.

-- 
MfG / Regards
Friedrich Lobenstock
____________________________________________________________________
Friedrich Lobenstock                       Linux Services Lobenstock
URL: http://www.lsl.at/                         Email: fl...@fl...
____________________________________________________________________

Re: [Devil-linux-develop] Last minute stuff for 1.2 - and MySQL question.

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

> I'm working on adding PostgreSQL server now, and am about done except
> for testing and creating an init.d script.
>
> Looking at the MySQL build/install script makes me ask why is the client
> and server are separate options in menuconfig?  According to the install
> script, the server binaries are being installed even if _only_ the
> client option is selected.  All the server option gains you is to copy
> the init.d script and echo a couple lines in /etc/sysconfig/config.
>
> So, unless I hear a strong objection really soon, I'm going to combine
> the "MySQL server" and "MySQL Client" menuconfig options into a single
> "MySQL" option.

When I recall it correctly, it's all done via the configure script.
You can basically say compile the client only.

> Likewise, PostgreSQL is only going to have one option in menuconfig.

I don't know if PostgreSQL even has a similar option. I would prefer if we
could de-select the server part.

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

[Devil-linux-develop] Last minute stuff for 1.2 - and MySQL question.

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

I'm working on adding PostgreSQL server now, and am about done except
for testing and creating an init.d script.

Looking at the MySQL build/install script makes me ask why is the client
and server are separate options in menuconfig?  According to the install
script, the server binaries are being installed even if _only_ the
client option is selected.  All the server option gains you is to copy
the init.d script and echo a couple lines in /etc/sysconfig/config.

So, unless I hear a strong objection really soon, I'm going to combine
the "MySQL server" and "MySQL Client" menuconfig options into a single
"MySQL" option.

Likewise, PostgreSQL is only going to have one option in menuconfig.

 - BS

Re: [Devil-linux-develop] [PATCH] ez-ipupdate init script

[Zsiros Z. <zs...@ma...>]

2004-04-14, sze keltez=E9ssel 02:45-kor Friedrich Lobenstock ezt =EDrta:
> Dear Mr./Mrs. Unknown!
>=20
> zszs wrote on 13.04.2004 21:41 MET:
> >
> > I have created the missing ez-ipupdate init script.
> > It has been derived from noip_updater init sript.
> > I have tested it and it works fine on my config, but it
> > would be better if someone else could do some testing.
>=20
> First thanks for your contribution.
> Second if possible send new files as attachment.
> Third please for changes to existing files run
>     diff -u script.before script   (that is then a real patch!)

The "script.before" is missing. This is a new file. I can only make a
diff on an empty file:

# diff -u emptyfile ez-ipupdate >ez-ipupdate.patch

I attach this kind of patch too.

> Forth please use your real name.

Sorry, my name is Zsolt Zsiros.

> I have to corret you here, it's as simple as running:
>    insserv ez-ipupdate

I have to learn DL ;-)

>=20
> > 2. Add two lines to /etc/sysconfig/config:
> >
> > # Start EZIP_UPDATE?
> > START_EZIP_UPDATE=3Dyes

I attach this as patch (config.patch)

Regards,
Zsolt

Re: [Devil-linux-develop] [PATCH] eagle-usb init script

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

Philippe Midol-Monnet wrote:
> Heiko Zuerker wrote:
> 
>> Philippe Midol-Monnet wrote:
>>
>>> Here is a little patch for the eagle-usb init script
>>
>>
>>
>> The patch doesn't apply.
>>
> 
> I create it with the "cvs diff -u "...
> 
>> notebook:/lfssystem/data/build # patch -p1 -i ../eagle-usb.patch  -R
>> patching file scripts/eagle-usb
> 
> 
> Take care it's a patch for the file :
> lfssystem/data/build/scripts/scripts/eagle-usb
> 
> and not for:
> lfssystem/data/build/scripts/eagle-usb
> 
> May be it will works with : path -p0
> 
> I send you the new version.

DONE

Heiko

Re: [Devil-linux-develop] [PATCH] ez-ipupdate init script

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

Friedrich Lobenstock wrote:
> Dear Mr./Mrs. Unknown!
> 
> zszs wrote on 13.04.2004 21:41 MET:
> 
>>
>> I have created the missing ez-ipupdate init script.
>> It has been derived from noip_updater init sript.
>> I have tested it and it works fine on my config, but it
>> would be better if someone else could do some testing.
> 
> 
> First thanks for your contribution.
> Second if possible send new files as attachment.

Yes as a attachment is best, please re-send it.

Thanks

Heiko

Re: [Devil-linux-develop] [PATCH] ez-ipupdate init script

[Friedrich L. <fl...@fl...>]

Dear Mr./Mrs. Unknown!

zszs wrote on 13.04.2004 21:41 MET:
> 
> I have created the missing ez-ipupdate init script.
> It has been derived from noip_updater init sript.
> I have tested it and it works fine on my config, but it
> would be better if someone else could do some testing.

First thanks for your contribution.
Second if possible send new files as attachment.
Third please for changes to existing files run
    diff -u script.before script   (that is then a real patch!)
Forth please use your real name.

> ...
> ------------
> Two more things to modify:
> 1. Make links
> 
> # cd /etc/init.d/rc3.d
> # ln -s ../ez-ipupdate K11ez-ipupdate
> # ln -s ../ez-ipupdate S10ez-ipupdate
> # cd /etc/init.d/rc5.d
> # ln -s ../ez-ipupdate K11ez-ipupdate
> # ln -s ../ez-ipupdate S10ez-ipupdate

I have to corret you here, it's as simple as running:
   insserv ez-ipupdate


> 2. Add two lines to /etc/sysconfig/config:
> 
> # Start EZIP_UPDATE?
> START_EZIP_UPDATE=yes


-- 
MfG / Regards
Friedrich Lobenstock
____________________________________________________________________
Friedrich Lobenstock                       Linux Services Lobenstock
URL: http://www.lsl.at/                         Email: fl...@fl...
____________________________________________________________________

[Devil-linux-develop] [PATCH] ez-ipupdate init script

[zszs <zs...@ma...>]

Hi,

I have created the missing ez-ipupdate init script.
It has been derived from noip_updater init sript.
I have tested it and it works fine on my config, but it
would be better if someone else could do some testing.

Here it is:

#!/bin/bash

### BEGIN INIT INFO
# Provides:       ez-ipupdate
# Required-Start: $network $syslog
# Required-Stop:  $network $syslog
# Default-Start:  3 5
# Default-Stop:   0 1 6
# Description:    starts ez-ipupdate
### END INIT INFO

# settings
source /etc/sysconfig/config

# parameters
NAME="ez-ipupdate dynamic DNS update service"
CONFIGNAME=EZIP_UPDATE
DAEMON=/usr/bin/ez-ipupdate
CONFIGFILE="/etc/ez-ipupdate/ez-ipupdate.conf"
PARAMETER="-c $CONFIGFILE -F /var/run/ez-ipupdate.pid"

# source function library
source /etc/init.d/functions

eval START=\$START_$CONFIGNAME

# Determine the base and follow a runlevel link name.
base=${0##*/}
link=${base#*[SK][0-9][0-9]}

# Force execution if not called by a runlevel directory.
test $link = $base && START=yes
test "$START" = "yes" || exit 0

if [ ! -e $DAEMON ]; then
                echo
        echo "$DAEMON not found. Did you install the package?"
        exit 1
fi

if [ ! -f $CONFIGFILE ]; then
                echo
        echo "Configuration: $CONFIGFILE not found."
        exit 1
fi

case "$1" in
        start)
                echo -n "Starting $NAME: "
                loadproc $DAEMON $PARAMETER
                ;;
        stop)
                echo -n "Shutting down $NAME: "
                killproc $DAEMON
                ;;
        restart)
                $0 stop
                sleep 1
                $0 start
                ;;
        *)
                echo "Usage: $0 {start|stop|restart}"
                exit 1
                ;;
esac

------------
Two more things to modify:
1. Make links

# cd /etc/init.d/rc3.d
# ln -s ../ez-ipupdate K11ez-ipupdate
# ln -s ../ez-ipupdate S10ez-ipupdate
# cd /etc/init.d/rc5.d
# ln -s ../ez-ipupdate K11ez-ipupdate
# ln -s ../ez-ipupdate S10ez-ipupdate

2. Add two lines to /etc/sysconfig/config:

# Start EZIP_UPDATE?
START_EZIP_UPDATE=yes

-- 
ZsZs

Re: [Devil-linux-develop] Problems with Bison Test on Fedora Core 1

[Friedrich L. <fl...@fl...>]

Diego Torres wrote on 13.04.2004 01:35 MET:
> On Mon, Apr 12, 2004 at 09:31:05PM +0200, Friedrich Lobenstock wrote:
> 
>>BTW just a wild guess, but have you tried assigning more swap space?
> 
> more? i'm using 512mb ram without swap and running dl compilation fine...

I have compile host with 1GB RAM and 2GB Swap so I did not know what the 
max. needed memory really is - it somehow doesn't matter ;-)

-- 
MfG / Regards
Friedrich Lobenstock
____________________________________________________________________
Friedrich Lobenstock                       Linux Services Lobenstock
URL: http://www.lsl.at/                         Email: fl...@fl...
____________________________________________________________________

Re: [Devil-linux-develop] Problems with Bison Test on Fedora Core 1

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

> > I tried to rm -rF the ./lfssystem  directory; however, it couldn't
> > be totally removed because of some permission in proc that I 
> > couldn't overcome. 
> 
> You have to unmount lfssystem/proc first!

Or if you're forgetful (like me), inside the LFSsystem, in /root, create
a file named ".bash_logout" and put the line "umount /proc" in the file.

Heiko:  IMO that would be a good addition to the standard LFS tarball.

I also have a script that creates a fresh LFS for me, first moving the
/root and /data directories before wiping the old system, and moving
them back after untaring the new system.  My standard procedure is:

  newlfs
  dl
  make mrproper && time make unpack prepare build install iso

(not including  cvs_sf update -d -P, update_src, make menuconfig, etc.)

 - BS

Re: [Devil-linux-develop] Problems with Bison Test on Fedora Core 1

[Diego T. <dt...@an...>]

On Mon, Apr 12, 2004 at 09:31:05PM +0200, Friedrich Lobenstock wrote:
> 
> BTW just a wild guess, but have you tried assigning more swap space?

more? i'm using 512mb ram without swap and running dl compilation fine...

-- 
-- gnupg keyfingerprint -- 48AF 5BF9 8F54 2966 64CC  2327 7CD0 DD91 B09D 5799
-- Use of a keyboard or mouse may be linked to serious injuries or disorders.
Diego Torres - dtorres at anthalia dot org - Madrid / España

Re: [Devil-linux-develop] Problems with Bison Test on Fedora Core 1

[Friedrich L. <fl...@fl...>]

William Gilmore wrote on 13.04.2004 01:06 MET:
> Ok, I have made some headway.  I tried to rm -rF the ./lfssystem directory; however, it couldn't be totally removed because of some permission in proc that I couldn't overcome. 

You have to unmount lfssystem/proc first!

> I mv the lfssystem lfssytem.old and then untarred the tarball.  I then updates the cvs to 1-0-5, updated source, ran make menuconfig and save the config without adding anything optional.  Make build is now well past bison. 
> 
> All of this was done with knoppix-std instead of fedora.  Heiko mentioned that there was a trick to knoppix that he couldn't remember and suggested that I check the discussion group.  I couldn't find anything there.  The only thing that I notice is that lftp isn't built into knoppix.  I built is specifying --path=./local at the same directory level as lfssystem.  I then added ./local/bin to the PATH environment variable.  This gave me a functional lftp and everything seems to be working fine.

If you copy /etc/hosts and /etc/resolv.conf to lfssystem/etc and
now you can run "update_src" from within the chrooted environment.
So you don't need lftp in your "normal" system.

> At this point, I don't know what caused the earlier problems.  I will repeat this exercise later with Fedora.

before your start with your experiment on Fedora please run
script log-build-system-on-fedora
...<do what you need to do>...
exit

Now send me (possibly also Heiko and Bruce) the file
log-build-system-on-fedora in a private mail.


-- 
MfG / Regards
Friedrich Lobenstock
____________________________________________________________________
Friedrich Lobenstock                       Linux Services Lobenstock
URL: http://www.lsl.at/                         Email: fl...@fl...
____________________________________________________________________

Re: [Devil-linux-develop] Problems with Bison Test on Fedora Core 1

[William G. <dl-...@gm...>]

Ok, I have made some headway.  I tried to rm -rF the ./lfssystem directory; however, it couldn't be totally removed because of some permission in proc that I couldn't overcome.  I mv the lfssystem lfssytem.old and then untarred the tarball.  I then updates the cvs to 1-0-5, updated source, ran make menuconfig and save the config without adding anything optional.  Make build is now well past bison. 

All of this was done with knoppix-std instead of fedora.  Heiko mentioned that there was a trick to knoppix that he couldn't remember and suggested that I check the discussion group.  I couldn't find anything there.  The only thing that I notice is that lftp isn't built into knoppix.  I built is specifying --path=./local at the same directory level as lfssystem.  I then added ./local/bin to the PATH environment variable.  This gave me a functional lftp and everything seems to be working fine.

At this point, I don't know what caused the earlier problems.  I will repeat this exercise later with Fedora.

William

=========================

I did just boot this system from a knoppix-std live cd and received the same error with it.  I am going to blow away the whole lfssystem and start from scratch using the knoppix-std this time and see if I can get it to work.  I must be doing something silly!

William

Re: [Devil-linux-develop] 1.2 ???

[Friedrich L. <fl...@fl...>]

Peter Frischknecht wrote on 10.04.2004 15:31 MET:
> I have succeeded in applying changes the necessary source files to
> support the following features:
> - ESFQ = enhanced Stochastic Fairness Queue
> - IMQ = Imtermediate Fairness Queue
> - IPP2P = iptables modules that automatically recognizes most networks
> of P2P traffic
> 
> IMQ was already partially implemented in the kernel, but there were
> patches missing from iptables and iproute2.

You might have to check if your patches still apply to iptables which I
just updated to the latest version.


> If there is interest by any other members, I will be submitting these
> patches in the next few days.

In general, if you created something please always create patches and
submit them on the mailinglist. If your patches are not accepted for
general inclusion at least the end up in the mailinglist archive and
other people can use them and give feedback.

Now about your patches, sounds interesting.

> Within the next week, I will be submitting patches for perl modules that
> allow for xml-rpc and SOAP server implementations.  Again,
> interest/feedback is welcome.

I _personally_ have no preferences about xml-rpc/SOAP but you are more
than welcome to post your patches. If the don't interfere with other
stuff then I would not speak against inclusion.

-- 
MfG / Regards
Friedrich Lobenstock
____________________________________________________________________
Friedrich Lobenstock                       Linux Services Lobenstock
URL: http://www.lsl.at/                         Email: fl...@fl...
____________________________________________________________________

Re: [Devil-linux-develop] Problems with Bison Test on Fedora Core 1

[Friedrich L. <fl...@fl...>]

William Gilmore wrote on 12.04.2004 17:14 MET:
> I have downloaded the lfssystem 1.0+ as well as both the CVS current sources and the 1.0.5 sources.  Both have the same problem.  When I issue the make build, bison builds without error.  However, when the bison tests execute, all test starting with test 4 fail.  Worse yet, the testsuite continues until finally the testsuite is aborted by the OS because it has exhausted all memory (512 MB Real with another 1024 MB virtual).  

BTW just a wild guess, but have you tried assigning more swap space?

dd if=/dev/zero of=/tmp/swapfile bs=1M count=512
mkswap /tmp/swapfile
swapon /tmp/swapfile

-- 
MfG / Regards
Friedrich Lobenstock
____________________________________________________________________
Friedrich Lobenstock                       Linux Services Lobenstock
URL: http://www.lsl.at/                         Email: fl...@fl...
____________________________________________________________________

RE: [Devil-linux-develop] Problems with Bison Test on Fedora Core 1

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

> I am using an AMD XP and tried initially with i686 but recieve the same
> error with i486. And no, I did not try parallel builds.
>
>>Did you select a higher CPU for the compilation then the one you have >in
>>your system? If yes, change to i486 for testing
>>Did you select parallel builds ? If yes, then turn off
>
> I did just boot this system from a knoppix-std live cd and received the
> same error with it.  I am going to blow away the whole lfssystem and start
> from scratch using the knoppix-std this time and see if I can get it to
> work.  I must be doing something silly!

Knoppix.... there was a problem with that, but also a solution.....
Check the mailinglist archives.

What also could be is, you sometime find problems with your hardware when
compiling DL, which didn't come up before.
Do you overclock your system?
Try default (slow) BIOS settings.
Can you replace the RAM?
Can you try it on another machine?
Can you send me all your money?

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

RE: [Devil-linux-develop] Problems with Bison Test on Fedora Core 1

[William G. <dl-...@gm...>]

I am using an AMD XP and tried initially with i686 but recieve the same error with i486. And no, I did not try parallel builds.

>Did you select a higher CPU for the compilation then the one you have >in
>your system? If yes, change to i486 for testing
>Did you select parallel builds ? If yes, then turn off

I did just boot this system from a knoppix-std live cd and received the same error with it.  I am going to blow away the whole lfssystem and start from scratch using the knoppix-std this time and see if I can get it to work.  I must be doing something silly!

William

RE: [Devil-linux-develop] Problems with Bison Test on Fedora Core 1

[<hzu...@ra...>]

On 04/12/2004 02:07:49 PM "William Gilmore" wrote:
>I am using
>ftp://ftp.devil-linux.org/pub/devel/sources/lfssystem-for-DL-1.0_and_up/
>lfssystem-cvs-20030127-i486-stripped.tar.bz2 which to my knowledge is
>the right tarball.
>

Yes this is the right one.

Did you select a higher CPU for the compilation then the one you have in
your system? If yes, change to i486 for testing
Did you select parallel builds ? If yes, then turn off

Heiko

RE: [Devil-linux-develop] Problems with Bison Test on Fedora Core 1

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

> I am using ftp://ftp.devil-linux.org/pub/devel/sources/lfssystem-for-DL-1.0_and_up/lfssystem-cvs-20030127-i486-stripped.tar.bz2 which to my knowledge is the right tarball.

Yes, that appears to be the correct one.  I ask because using the wrong
version of the LFSsystem has been a problem in the past for some people.
(including me when I first started with DL :)

> > Yes, I am working within the chrott environment.
> 
> And you downloaded the correct LFS system tarball?
> 
> > There is no additional security that I am aware of on Fedora; but, I
> > have only been working on it for about a month now and I may not have
> > run into it.  I have not had a problem building any other software on
> > it.
> 
> I ran Fedora briefly before switching to SuSE 9.0 and I didn't have any
> problems compiling DL.

RE: [Devil-linux-develop] Problems with Bison Test on Fedora Core 1

[William G. <dl-...@gm...>]

I am using ftp://ftp.devil-linux.org/pub/devel/sources/lfssystem-for-DL-1.0_and_up/lfssystem-cvs-20030127-i486-stripped.tar.bz2 which to my knowledge is the right tarball.

> Yes, I am working within the chrott environment.

And you downloaded the correct LFS system tarball?

> There is no additional security that I am aware of on Fedora; but, I
> have only been working on it for about a month now and I may not have
> run into it.  I have not had a problem building any other software on
> it.

I ran Fedora briefly before switching to SuSE 9.0 and I didn't have any
problems compiling DL.

 - BS




-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Devil-linux-develop mailing list
Dev...@li...
https://lists.sourceforge.net/lists/listinfo/devil-linux-develop

RE: [Devil-linux-develop] Problems with Bison Test on Fedora Core 1

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

> Yes, I am working within the chrott environment.

And you downloaded the correct LFS system tarball?
 
> There is no additional security that I am aware of on Fedora; but, I
> have only been working on it for about a month now and I may not have
> run into it.  I have not had a problem building any other software on
> it.

I ran Fedora briefly before switching to SuSE 9.0 and I didn't have any
problems compiling DL.

 - BS

RE: [Devil-linux-develop] Problems with Bison Test on Fedora Core 1

[William G. <dl-...@gm...>]

Yes, I am working within the chrott environment.
 
There is no additional security that I am aware of on Fedora; but, I have only been working on it for about a month now and I may not have run into it.  I have not had a problem building any other software on it.
 
William


--------------------------------------------------------------------------------
From: dev...@li... on behalf of hzu...@ra...
Sent: Mon 4/12/2004 10:21 AM
To: dev...@li...
Subject: Re: [Devil-linux-develop] Problems with Bison Test on Fedora Core 1




On 04/12/2004 11:14:18 AM "William Gilmore" wrote:
>All,
>
>Given that I don't have enough pain in my life :) , I am trying to
>learn how to build Devil Linux yet again.  I have had problems in the
>past and the production code timeline caught up with my needs and I
>haven't had to worry about this for some time.  Now, I would like to be
>able to run some scripts on my DL fireall that require some Perl
>Modules not in the current build.  So, I thought I would give building
>a try again.  But alas, like the last time, I am having problems.
>
>A word about my environment before I continue, I am trying to build DL
>using a fully updated version of Fedora Core 1.  I don't know if this
>is a supported build environment or not.  In searching the discussion
>list, I can find no references to anyone using Fedora as a development
>environment, but that is my Linux du jour at this point.
>
>I have downloaded the lfssystem 1.0+ as well as both the CVS current
>sources and the 1.0.5 sources.  Both have the same problem.  When I
>issue the make build, bison builds without error.  However, when the
>bison tests execute, all test starting with test 4 fail.  Worse yet,
>the testsuite continues until finally the testsuite is aborted by the
>OS because it has exhausted all memory (512 MB Real with another 1024
>MB virtual).
>
>When I first had the problem with the CVS version, I thought that may
>this was a bug in the current CVS code.  So, I deleted everything and
>decided I would get 1.0.5 working first.  After update with 1.0.5, I
>ran into the same problem.
>
>So almight Devil Linux Developers, please have pity on me and tell what
>I need to do to fix this;)

You are working inside the chroot, correct?

Doesn't Fedora use some new fancy (kernel based?) security features?

Heiko





-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Devil-linux-develop mailing list
Dev...@li...
https://lists.sourceforge.net/lists/listinfo/devil-linux-develop

Re: [Devil-linux-develop] Problems with Bison Test on Fedora Core 1

[<hzu...@ra...>]

On 04/12/2004 11:14:18 AM "William Gilmore" wrote:
>All,
>
>Given that I don't have enough pain in my life :) , I am trying to
>learn how to build Devil Linux yet again.  I have had problems in the
>past and the production code timeline caught up with my needs and I
>haven't had to worry about this for some time.  Now, I would like to be
>able to run some scripts on my DL fireall that require some Perl
>Modules not in the current build.  So, I thought I would give building
>a try again.  But alas, like the last time, I am having problems.
>
>A word about my environment before I continue, I am trying to build DL
>using a fully updated version of Fedora Core 1.  I don't know if this
>is a supported build environment or not.  In searching the discussion
>list, I can find no references to anyone using Fedora as a development
>environment, but that is my Linux du jour at this point.
>
>I have downloaded the lfssystem 1.0+ as well as both the CVS current
>sources and the 1.0.5 sources.  Both have the same problem.  When I
>issue the make build, bison builds without error.  However, when the
>bison tests execute, all test starting with test 4 fail.  Worse yet,
>the testsuite continues until finally the testsuite is aborted by the
>OS because it has exhausted all memory (512 MB Real with another 1024
>MB virtual).
>
>When I first had the problem with the CVS version, I thought that may
>this was a bug in the current CVS code.  So, I deleted everything and
>decided I would get 1.0.5 working first.  After update with 1.0.5, I
>ran into the same problem.
>
>So almight Devil Linux Developers, please have pity on me and tell what
>I need to do to fix this;)

You are working inside the chroot, correct?

Doesn't Fedora use some new fancy (kernel based?) security features?

Heiko

[Devil-linux-develop] Problems with Bison Test on Fedora Core 1

[William G. <dl-...@gm...>]

All,
 
Given that I don't have enough pain in my life :) , I am trying to learn how to build Devil Linux yet again.  I have had problems in the past and the production code timeline caught up with my needs and I haven't had to worry about this for some time.  Now, I would like to be able to run some scripts on my DL fireall that require some Perl Modules not in the current build.  So, I thought I would give building a try again.  But alas, like the last time, I am having problems.
 
A word about my environment before I continue, I am trying to build DL using a fully updated version of Fedora Core 1.  I don't know if this is a supported build environment or not.  In searching the discussion list, I can find no references to anyone using Fedora as a development environment, but that is my Linux du jour at this point.
 
I have downloaded the lfssystem 1.0+ as well as both the CVS current sources and the 1.0.5 sources.  Both have the same problem.  When I issue the make build, bison builds without error.  However, when the bison tests execute, all test starting with test 4 fail.  Worse yet, the testsuite continues until finally the testsuite is aborted by the OS because it has exhausted all memory (512 MB Real with another 1024 MB virtual).  
 
When I first had the problem with the CVS version, I thought that may this was a bug in the current CVS code.  So, I deleted everything and decided I would get 1.0.5 working first.  After update with 1.0.5, I ran into the same problem.
 
So almight Devil Linux Developers, please have pity on me and tell what I need to do to fix this;)
 
Thanks in advance,
 
William

Re: [Devil-linux-develop] Python Modules

[<hzu...@ra...>]

On 04/11/2004 08:51:46 PM Peter Frischknecht wrote:
>I noticed that Python has modules under:
>/build/tmp/Python-install/usr/lib/python2.3
>and
>/build/tmp/Python-2.3.3/Lib
>
>WHat is the correct location?  I need to add extra modules to Python.

Basicallty we install Python within the directory  /build/tmp/Python-2.3.3
For the python installation itself we have to do some tricks and just go
ahead and install it  into  /build/tmp/Python-install/usr/lib/python2.3

So anything which patches or copies into the python sources goes into the
source tree under /build/tmp/Python-2.3.3

Did I confuse you enough?

Heiko