devil-linux-develop — developer discussions

Re: [Devil-linux-develop] Re: glibc-2.3.2 build error (DL 1.2 )

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

Eric Cartman wrote:

> From: Heiko Zuerker <heiko@zu...>
> *Re: glibc-2.3.2 build error (DL 1.2 )*
> 2005-02-17 02:29
>
> Michal Weinfurtner wrote:
>
> 
>
> >Hello, 
>
> >
>
> >i have a problem with build my own DL. I tried to build my own system
>
> >but something goes wrong. What i did : 
>
> >
>
> >1) get and untar this file 
>
> >lfssystem-for-DL-1.0_and_up/lfssystem-cvs-20030127-i486-stripped.tar.bz2
>
> >
>
> >2) run those commands in lfssystem/data/ directory 
>
> >cvs -d:pserver:anonymous@cv...:/cvsroot/devil-linux login
>
> >cvs -z3 -d:pserver:anonymous@cv...:/cvsroot/devil-linux co -r
>
>rel-1-2-patches build
>
> >cvs update -d -P 
>
> >
>
> >3) than run 
>
> >chroot /root/DL/lfssystem/ /usr/bin/env -i HOME=/root TERM=$TERM /bin/bash -login
>
> >
>
> >4) run 
>
> >./update_src 
>
> >
>
> >5) run 
>
> >make unpack 
>
> >make menuconfig ( save defalt config profile )
>
> >make prepare build install iso dist 
>
> >
>
> >Than I got this error message 
>
> >executing glibc with option build (in /data/build/tmp/glibc-2.3.2)
>
> >ERROR
>
> >/data/build/scripts/glibc build failed
>
> >check log file /data/build/tmp/LOGS/build/glibc for details
>
> >make: *** [build] Error 1
>
> >
>
> >In /data/build/tmp/LOGS/build/glibc I found this: 
>
> >
>
> >gcc -nostdlib -nostartfiles -o
>
> >/data/build/tmp/glibc-build/sunrpc/rpcinfo 
>
> >-Wl,-dynamic-linker=/lib/ld-linux.so.2   -Wl,-z,combreloc
>
> >/data/build/tmp/glibc-build/csu/crt1.o
>
> >/data/build/tmp/glibc-build/csu/crti.o `gcc
>
> >--print-file-name=crtbegin.o`
>
> >/data/build/tmp/glibc-build/sunrpc/rpcinfo.o 
>
> 
>
>>-Wl,-rpath-link=/data/build/tmp/glibc-build:/data/build/tmp/glibc-build/math:/data/build/tmp/glibc-build/elf:/data/build/tmp/glibc-build/dlfcn:/data/build/tmp/glibc-build/nss:/data/build/tmp/glibc-build/nis:/data/build/tmp/glibc-build/rt:/data/build/tmp/glibc-build/resolv:/data/build/tmp/glibc-build/crypt:/data/build/tmp/glibc-build/linuxthreads
>
>/data/build/tmp/glibc-build/libc.so.6 /data/build/tmp/glibc-build/libc_nonshared.a -lgcc
>
>`gcc --print-file-name=crtend.o` /data/build/tmp/glibc-build/csu/crtn.o
>
> >CPP="gcc -E -x c-header"  /data/build/tmp/glibc-build/elf/ld-linux.so.2
>
> >--library-path
>
> 
>
>>/data/build/tmp/glibc-build:/data/build/tmp/glibc-build/math:/data/build/tmp/glibc-build/elf:/data/build/tmp/glibc-build/dlfcn:/data/build/tmp/glibc-build/nss:/data/build/tmp/glibc-build/nis:/data/build/tmp/glibc-build/rt:/data/build/tmp/glibc-build/resolv:/data/build/tmp/glibc-build/crypt:/data/build/tmp/glibc-build/linuxthreads
>
>/data/build/tmp/glibc-build/sunrpc/rpcgen -Y ../scripts -c rpcsvc/bootparam_prot.x -o
>
>/data/build/tmp/glibc-build/sunrpc/xbootparam_prot.T
>
> >FATAL: kernel too old
>
> >make[3]: *** [/data/build/tmp/glibc-build/sunrpc/xbootparam_prot.stmp]
>
> >Error 1
>
> >make[3]: Leaving directory `/data/build/tmp/glibc-2.3.2/sunrpc"
>
> >make[2]: *** [sunrpc/others] Error 2
>
> >make[2]: Leaving directory `/data/build/tmp/glibc-2.3.2"
>
> >make[1]: *** [all] Error 2
>
> >make[1]: Leaving directory `/data/build/tmp/glibc-build"
>
> >
>
> >
>
> >Anybody know what i"m doing wrong ? 
>
> >
>
> >  
>
> >
>
> The build system currently requires Host OS with Kernel 2.4.22 or newer.
>
> 
>
> 
>
> -- 
>
> 
>
> Regards
>
>   Heiko Zuerker
>
>   http://www.devil-linux.org
>
> 
>
>Hi Heiko
>
> 
>
>I’ve a similar problem, the error is the same but in log file I found:
>
> 
>
>checking for strings.h... yes
>
>checking for inttypes.h... yes
>
>checking for stdint.h... yes
>
>checking for unistd.h... yes
>
>checking for long double... yes
>
>checking size of long double... configure: error: cannot compute sizeof (long double), 77
>
>See `config.log' for more details.
>
> 
>
>My Kernel version is 2.4.26(Slackware), and gcc 3.3.4
>
> 
>
>May you help me?
>
>Thanks
>
> 
>
>Matteo
>
> 
>
> 
>

I have no idea what could cause this problem and I don't really have any 
experience with Slackware.
Is Slackware using any security features like exec-shield ?

What's the CPU in your machine? RAM ? Do you have enough disk space ?

-- 

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

Re: [Devil-linux-develop] Idea for 1.3 ...

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

Bruce Smith wrote:

>>>My idea is to expand menuconfig, and the install process for some
>>>software, to include a third option.  Instead of just Y/N to select the
>>>package to be installed (or not), include a third option of "P" to build
>>>the software as a "package" that could be optionally installed to the
>>>hard drive.  That would produce a tarball and an install script on the
>>>CD  Then the software could be optionally installed on the hard drive
>>>(instead of installing in the CDROM tree).
>>>...
>>>There are a lot of details we'd have to work out, like where to install
>>>on the hard drive, but let's see what everyone thinks about the basic
>>>idea before we get lost in too many details.
>>>      
>>>
>>Hmmmmm......
>>We could certainly make something out of this idea.
>>    
>>
>
>OK, let's hash this out and see if it might work.
>
>First we need some partition on the hard drive to install software.
>I don't care what it's named, so let's install under /opt until someone
>has a better idea.
>
>Most software now gets installed under tmp/tmp/... and then copied to
>the CD tree.  Instead of copying it to the CD tree, the "P" (package)
>menuconfig option tells the install script to tar up tmp/tmp/... and put
>the tar file(s) on the CD under the /packages directory (or whatever you
>want to call it).
>
>I'm thinking we should probably create two tar files, one for /etc files
>and one for hard drive files.  That way people could upgrade to a new
>version of Apache (or whatever) by simply "rm -fr /opt/apache2/" and
>untaring the new package, without changing their config files.
>
>We have to worry about $PATH and libraries.  I'm thinking we could
>probably add the library path to ld.so.conf when needed and add paths
>in /etc/profile.d/apache2.
>
>How's that for a start?  :-)
>  
>

(sorry for the late response)

It actually sounds pretty straight forward.
I'm a little afraid of how many  DL version we would have to release.

Some people would prefer having everything on their CD because it's more 
secure, others would like the package option....

-- 

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

Re: [Devil-linux-develop] Idea for 1.3 ...

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

> > My idea is to expand menuconfig, and the install process for some
> > software, to include a third option.  Instead of just Y/N to select the
> > package to be installed (or not), include a third option of "P" to build
> > the software as a "package" that could be optionally installed to the
> > hard drive.  That would produce a tarball and an install script on the
> > CD  Then the software could be optionally installed on the hard drive
> > (instead of installing in the CDROM tree).
> > ...
> > There are a lot of details we'd have to work out, like where to install
> > on the hard drive, but let's see what everyone thinks about the basic
> > idea before we get lost in too many details.
> 
> Hmmmmm......
> We could certainly make something out of this idea.

OK, let's hash this out and see if it might work.

First we need some partition on the hard drive to install software.
I don't care what it's named, so let's install under /opt until someone
has a better idea.

Most software now gets installed under tmp/tmp/... and then copied to
the CD tree.  Instead of copying it to the CD tree, the "P" (package)
menuconfig option tells the install script to tar up tmp/tmp/... and put
the tar file(s) on the CD under the /packages directory (or whatever you
want to call it).

I'm thinking we should probably create two tar files, one for /etc files
and one for hard drive files.  That way people could upgrade to a new
version of Apache (or whatever) by simply "rm -fr /opt/apache2/" and
untaring the new package, without changing their config files.

We have to worry about $PATH and libraries.  I'm thinking we could
probably add the library path to ld.so.conf when needed and add paths
in /etc/profile.d/apache2.

How's that for a start?  :-)

 - BS

Re: [Devil-linux-develop] Idea for 1.3 ...

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

> The talk about "su" vs. "ksu" and such gave me a hair brained idea about
> something new we could do in 1.3 (maybe).
>
> This idea makes one assumption:  There are certain packages on DL that
> don't make sense to run without a hard drive.  For example, these
> packages might fit into that category:  Apache, vsftp, Samba, MySQL,
> Postgresql, Postfix, Cyrus (and other mail servers), heimdal?, and
> probably other software ...
>
> My idea is to expand menuconfig, and the install process for some
> software, to include a third option.  Instead of just Y/N to select the
> package to be installed (or not), include a third option of "P" to build
> the software as a "package" that could be optionally installed to the
> hard drive.  That would produce a tarball and an install script on the
> CD  Then the software could be optionally installed on the hard drive
> (instead of installing in the CDROM tree).
>
> This would also give us the ability to update some individual packages
> without a whole new CD.  And would give people an easier way to install
> their own software on DL.
>
> It would also enhance security, as these tarballs would only be readable
> by root, so uninstalled software would not be accessible to ordinary
> users.  (heimdal could not be installed by default, and it's "su" not
> accessible to anyone)
>
> There are a lot of details we'd have to work out, like where to install
> on the hard drive, but let's see what everyone thinks about the basic
> idea before we get lost in too many details.

Hmmmmm......
We could certainly make something out of this idea.

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

[Devil-linux-develop] Idea for 1.3 ...

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

The talk about "su" vs. "ksu" and such gave me a hair brained idea about
something new we could do in 1.3 (maybe).

This idea makes one assumption:  There are certain packages on DL that
don't make sense to run without a hard drive.  For example, these
packages might fit into that category:  Apache, vsftp, Samba, MySQL,
Postgresql, Postfix, Cyrus (and other mail servers), heimdal?, and
probably other software ...

My idea is to expand menuconfig, and the install process for some
software, to include a third option.  Instead of just Y/N to select the
package to be installed (or not), include a third option of "P" to build
the software as a "package" that could be optionally installed to the
hard drive.  That would produce a tarball and an install script on the
CD  Then the software could be optionally installed on the hard drive
(instead of installing in the CDROM tree).

This would also give us the ability to update some individual packages
without a whole new CD.  And would give people an easier way to install
their own software on DL.

It would also enhance security, as these tarballs would only be readable
by root, so uninstalled software would not be accessible to ordinary
users.  (heimdal could not be installed by default, and it's "su" not
accessible to anyone)

There are a lot of details we'd have to work out, like where to install
on the hard drive, but let's see what everyone thinks about the basic
idea before we get lost in too many details.

 - BS

Re: [Devil-linux-develop] chroot error

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

> Eric Cartman wrote:
>
>> Hi all,
>>
>> I’m trying to create a DL cd, but when I try to execute the chroot
>> command:
>>
>> *chroot /matteo/espe/lfssystem /usr/bin/env -i HOME=/root TERM=$TERM
>> /bin/bash –login*
>>
>> * *
>>
>> an error occur
>>
>> *cannot** set up thread-local storage: set_thread_area failed when
>> setting up thread-local storage*
>>
>> * *
>>
> Try to use a recent linux kernel like a 2.6 (with a Redhat Fedora Core 3)
> I had the same problem with an old kernel..
> Regards,

You only need this if you build the current development release (1.3). I'm
not sure if this is really your intention, since it is considered
un-stable.

For production systems, please use 1.2.x

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

Re: [Devil-linux-develop] chroot error

[Jean-Luc P. <Jea...@ib...>]

Eric Cartman wrote:

> Hi all,
>
> I=92m trying to create a DL cd, but when I try to execute the chroot=20
> command:
>
> *chroot /matteo/espe/lfssystem /usr/bin/env -i HOME=3D/root TERM=3D$TER=
M=20
> /bin/bash =96login*
>
> * *
>
> an error occur
>
> *cannot** set up thread-local storage: set_thread_area failed when=20
> setting up thread-local storage*
>
> * *
>
Try to use a recent linux kernel like a 2.6 (with a Redhat Fedora Core 3)
I had the same problem with an old kernel..
Regards,
- pjluc

--=20
Jean-Luc Parouty - Phone: +33 4 387 823 90
Institut de Biologie Structurale-CNRS (UMR 5075)/CEA/UJF - IBS
41 Av. Jules Horowitz - 38027 Grenoble Cedex 1 - France

[Devil-linux-develop] chroot error

[Eric C. <mo...@gm...>]

 
 
Hi all,
I'm trying to create a DL cd, but when I try to execute the chroot
command:
chroot /matteo/espe/lfssystem /usr/bin/env -i HOME=/root TERM=$TERM
/bin/bash -login
 
an error occur
 
cannot set up thread-local storage: set_thread_area failed when setting
up thread-local storage
 
anyone knows where's my mistake?
 
Thanks a lot

Re: [Devil-linux-develop] glibc-2.3.2 build error (DL 1.2 )

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

Michal Weinfurtner wrote:

>Hello, 
>
>i have a problem with build my own DL. I tried to build my own system
>but something goes wrong. What i did : 
>
>1) get and untar this file 
>lfssystem-for-DL-1.0_and_up/lfssystem-cvs-20030127-i486-stripped.tar.bz2
>
>2) run those commands in lfssystem/data/ directory 
>cvs -d:pserver:ano...@cv...:/cvsroot/devil-linux login
>cvs -z3 -d:pserver:ano...@cv...:/cvsroot/devil-linux co -r rel-1-2-patches build
>cvs update -d -P 
>
>3) than run 
>chroot /root/DL/lfssystem/ /usr/bin/env -i HOME=/root TERM=$TERM /bin/bash -login
>
>4) run 
>./update_src 
>
>5) run 
>make unpack 
>make menuconfig ( save defalt config profile )
>make prepare build install iso dist 
>
>Than I got this error message 
>executing glibc with option build (in /data/build/tmp/glibc-2.3.2)
>ERROR
>/data/build/scripts/glibc build failed
>check log file /data/build/tmp/LOGS/build/glibc for details
>make: *** [build] Error 1
>
>In /data/build/tmp/LOGS/build/glibc I found this: 
>
>gcc -nostdlib -nostartfiles -o
>/data/build/tmp/glibc-build/sunrpc/rpcinfo 
>-Wl,-dynamic-linker=/lib/ld-linux.so.2   -Wl,-z,combreloc
>/data/build/tmp/glibc-build/csu/crt1.o
>/data/build/tmp/glibc-build/csu/crti.o `gcc
>--print-file-name=crtbegin.o`
>/data/build/tmp/glibc-build/sunrpc/rpcinfo.o 
>-Wl,-rpath-link=/data/build/tmp/glibc-build:/data/build/tmp/glibc-build/math:/data/build/tmp/glibc-build/elf:/data/build/tmp/glibc-build/dlfcn:/data/build/tmp/glibc-build/nss:/data/build/tmp/glibc-build/nis:/data/build/tmp/glibc-build/rt:/data/build/tmp/glibc-build/resolv:/data/build/tmp/glibc-build/crypt:/data/build/tmp/glibc-build/linuxthreads /data/build/tmp/glibc-build/libc.so.6 /data/build/tmp/glibc-build/libc_nonshared.a -lgcc `gcc --print-file-name=crtend.o` /data/build/tmp/glibc-build/csu/crtn.o
>CPP='gcc -E -x c-header'  /data/build/tmp/glibc-build/elf/ld-linux.so.2
>--library-path
>/data/build/tmp/glibc-build:/data/build/tmp/glibc-build/math:/data/build/tmp/glibc-build/elf:/data/build/tmp/glibc-build/dlfcn:/data/build/tmp/glibc-build/nss:/data/build/tmp/glibc-build/nis:/data/build/tmp/glibc-build/rt:/data/build/tmp/glibc-build/resolv:/data/build/tmp/glibc-build/crypt:/data/build/tmp/glibc-build/linuxthreads /data/build/tmp/glibc-build/sunrpc/rpcgen -Y ../scripts -c rpcsvc/bootparam_prot.x -o /data/build/tmp/glibc-build/sunrpc/xbootparam_prot.T
>FATAL: kernel too old
>make[3]: *** [/data/build/tmp/glibc-build/sunrpc/xbootparam_prot.stmp]
>Error 1
>make[3]: Leaving directory `/data/build/tmp/glibc-2.3.2/sunrpc'
>make[2]: *** [sunrpc/others] Error 2
>make[2]: Leaving directory `/data/build/tmp/glibc-2.3.2'
>make[1]: *** [all] Error 2
>make[1]: Leaving directory `/data/build/tmp/glibc-build'
>
>
>Anybody know what i'm doing wrong ? 
>
>  
>
The build system currently requires Host OS with Kernel 2.4.22 or newer.


-- 

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

[Devil-linux-develop] glibc-2.3.2 build error (DL 1.2 )

[Michal W. <wei...@se...>]

Hello, 

i have a problem with build my own DL. I tried to build my own system
but something goes wrong. What i did : 

1) get and untar this file 
lfssystem-for-DL-1.0_and_up/lfssystem-cvs-20030127-i486-stripped.tar.bz2

2) run those commands in lfssystem/data/ directory 
cvs -d:pserver:ano...@cv...:/cvsroot/devil-linux login
cvs -z3 -d:pserver:ano...@cv...:/cvsroot/devil-linux co -r rel-1-2-patches build
cvs update -d -P 

3) than run 
chroot /root/DL/lfssystem/ /usr/bin/env -i HOME=/root TERM=$TERM /bin/bash -login

4) run 
./update_src 

5) run 
make unpack 
make menuconfig ( save defalt config profile )
make prepare build install iso dist 

Than I got this error message 
executing glibc with option build (in /data/build/tmp/glibc-2.3.2)
ERROR
/data/build/scripts/glibc build failed
check log file /data/build/tmp/LOGS/build/glibc for details
make: *** [build] Error 1

In /data/build/tmp/LOGS/build/glibc I found this: 

gcc -nostdlib -nostartfiles -o
/data/build/tmp/glibc-build/sunrpc/rpcinfo 
-Wl,-dynamic-linker=/lib/ld-linux.so.2   -Wl,-z,combreloc
/data/build/tmp/glibc-build/csu/crt1.o
/data/build/tmp/glibc-build/csu/crti.o `gcc
--print-file-name=crtbegin.o`
/data/build/tmp/glibc-build/sunrpc/rpcinfo.o 
-Wl,-rpath-link=/data/build/tmp/glibc-build:/data/build/tmp/glibc-build/math:/data/build/tmp/glibc-build/elf:/data/build/tmp/glibc-build/dlfcn:/data/build/tmp/glibc-build/nss:/data/build/tmp/glibc-build/nis:/data/build/tmp/glibc-build/rt:/data/build/tmp/glibc-build/resolv:/data/build/tmp/glibc-build/crypt:/data/build/tmp/glibc-build/linuxthreads /data/build/tmp/glibc-build/libc.so.6 /data/build/tmp/glibc-build/libc_nonshared.a -lgcc `gcc --print-file-name=crtend.o` /data/build/tmp/glibc-build/csu/crtn.o
CPP='gcc -E -x c-header'  /data/build/tmp/glibc-build/elf/ld-linux.so.2
--library-path
/data/build/tmp/glibc-build:/data/build/tmp/glibc-build/math:/data/build/tmp/glibc-build/elf:/data/build/tmp/glibc-build/dlfcn:/data/build/tmp/glibc-build/nss:/data/build/tmp/glibc-build/nis:/data/build/tmp/glibc-build/rt:/data/build/tmp/glibc-build/resolv:/data/build/tmp/glibc-build/crypt:/data/build/tmp/glibc-build/linuxthreads /data/build/tmp/glibc-build/sunrpc/rpcgen -Y ../scripts -c rpcsvc/bootparam_prot.x -o /data/build/tmp/glibc-build/sunrpc/xbootparam_prot.T
FATAL: kernel too old
make[3]: *** [/data/build/tmp/glibc-build/sunrpc/xbootparam_prot.stmp]
Error 1
make[3]: Leaving directory `/data/build/tmp/glibc-2.3.2/sunrpc'
make[2]: *** [sunrpc/others] Error 2
make[2]: Leaving directory `/data/build/tmp/glibc-2.3.2'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/data/build/tmp/glibc-build'


Anybody know what i'm doing wrong ? 

Re: [Devil-linux-develop] [PATCH] siproxd

[Roland P. <rp...@ne...>]

On Friday 11 February 2005 23:42, Heiko Zuerker wrote:
> >> AFAIK, nobody has commited these patches. Anything wrong with it? If
> >> not, I have made some minor changes and would send the newer ones in
> >> again.
> >
> > I didn't commit the patches because I don't know anything about the
> > package.  I don't remember seeing Heiko commit them either, but I'm not
> > 100% sure about that.  (I'd send the new ones)
>
> I didn't have time yet to commit the patches.
> So just send us the updated ones.
here they come
cu
Roland
-- 
ICQ UIN 49339118	Linux Counter #88774
GPG-Key 1024D/59C6AFA6 2003-02-07 Roland Pabel <ro...@pa...>

Re: [Devil-linux-develop] please resend patches

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

2005-02-12, szo keltezéssel 04:10-kor Heiko Zuerker ezt írta:
> Hey everybody,
> 
> Please resend all patches since 01/29/05 , because I lost all emails
> after this date.
> 

Hi Heiko,

I've created a jail script for ntpd and a little patch for the xntpd
init script to start the daemon in chroot jail.
I attach the patch and the NTPD jail script.

Zsolt

Re: [Devil-linux-develop] Help

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

Bruce Smith wrote:

>>I know you form http://distrowatch.com/  I am BSD linux user. I would like
>>to learn build a small linux server from source code.  Can you give me
>>help?
>>
>>How to build kernel , bootloader, installer from source coder to ISO?
>>    
>>
>
>There is documentation on devil-linux.org about how to build Devil-Linux
>from source code.  Let us know if you have any specific questions.
>  
>

For you understanding of Devil-Linux, it would also be helpfull to take 
a look at http://www.linuxfromscratch.org .
The book explains how to create a basic Linux distribution yourself. 
Devil-Linux of course goes far behind this, but it sounds like you want 
to understand how everything works.

-- 

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

Re: [Devil-linux-develop] Help

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

> I know you form http://distrowatch.com/  I am BSD linux user. I would like
> to learn build a small linux server from source code.  Can you give me
> help?
> 
> How to build kernel , bootloader, installer from source coder to ISO?

There is documentation on devil-linux.org about how to build Devil-Linux
from source code.  Let us know if you have any specific questions.

 - BS

[Devil-linux-develop] Help

[<xu...@co...>]

Hi

I know you form http://distrowatch.com/  I am BSD linux user. I would like
to learn build a small linux server from source code.  Can you give me
help?

How to build kernel , bootloader, installer from source coder to ISO?

Can you give me help?

Best Regards
Man

[Devil-linux-develop] please resend patches

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

Hey everybody,

Please resend all patches since 01/29/05 , because I lost all emails 
after this date.

-- 

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

Re: [Devil-linux-develop] DL1.3 - usb difficulties

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

Jean-Luc Parouty wrote:

> Heiko Zuerker wrote:
>
>> Jean-Luc Parouty wrote:
>>
>>> Heiko Zuerker wrote:
>>>
>>>> Jean-Luc Parouty wrote:
>>>>
>>>>>
>>>>> Hello,
>>>>> I try to compile cvs current 1.3, but the glibc compilation failed...
>>>>> ... it seems that gcc receive too unknown options :
>>>>>    -no-pie
>>>>>    -fno-stack-protector-all
>>>>> (...)
>>>>
>>>>
>>
>> This was actually a bug in the build system.
>> Update from CVS and FTP and you should be OK.
>
>
> Ok, I rebuilt a full DL1.3, from scratch and the compilation was fine..
>
> But, I still have some little usb problems :
>
> - On vmware, the usb key is not found.
> I burned (a real) cd an test it and usb key was found, on /dev/sda1, 
> but on vmware the /dev/sda1 isn't in the list of search device...
> On 1.2.x, I never had any problem...
> vmware is more usefull than for simple tests:  it can give you a very 
> simple and usefull backup system... and for development, this is 
> really great...

This must be a problem with the kernel USB support.
There's also a performance issue with Kernel 2.6 and VMWare, so let's 
hope the kernel maintainers get that stuff fixed soon.

>
> - On the "real pc", the usb key is found and the configuration is 
> saved during the boot sequence, but the save-config, doesn't want to 
> mount the msdos filesystem of the key :
>
> Found configuration file location used by boot: /dev/sda1
> using device /dev/sda1
> mount unknown filesystem type 'msdfos'
> please insert Configuration Media in /dev/sda1
> (..)


I encountered the same problem when I did some testing.
We turned of msdos filesystem so the OS uses vfat per default. I guess 
we need to do some more testing/investigation here.
My time is very limited at the moment, it would be great if somebody 
else could own this task.

-- 

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

Re: [Devil-linux-develop] [PATCH] siproxd

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

>> AFAIK, nobody has commited these patches. Anything wrong with it? If
>> not, I have made some minor changes and would send the newer ones in
>> again.
>
> I didn't commit the patches because I don't know anything about the
> package.  I don't remember seeing Heiko commit them either, but I'm not
> 100% sure about that.  (I'd send the new ones)

I didn't have time yet to commit the patches.
So just send us the updated ones.

-- 

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

Re: [Devil-linux-develop] [PATCH] siproxd

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

> AFAIK, nobody has commited these patches. Anything wrong with it? If not, I 
> have made some minor changes and would send the newer ones in again.

I didn't commit the patches because I don't know anything about the
package.  I don't remember seeing Heiko commit them either, but I'm not
100% sure about that.  (I'd send the new ones)

 - BS

Re: [Devil-linux-develop] [PATCH] siproxd

[Roland P. <rp...@ne...>]

Hi,
AFAIK, nobody has commited these patches. Anything wrong with it? If not, I 
have made some minor changes and would send the newer ones in again.
cu
Roland
-- 
ICQ UIN 49339118	Linux Counter #88774
GPG-Key 1024D/59C6AFA6 2003-02-07 Roland Pabel <ro...@pa...>

[Devil-linux-develop] DL1.3 - usb difficulties

[Jean-Luc P. <Jea...@ib...>]

Heiko Zuerker wrote:

> Jean-Luc Parouty wrote:
>
>> Heiko Zuerker wrote:
>>
>>> Jean-Luc Parouty wrote:
>>>
>>>>
>>>> Hello,
>>>> I try to compile cvs current 1.3, but the glibc compilation failed...
>>>> ... it seems that gcc receive too unknown options :
>>>>    -no-pie
>>>>    -fno-stack-protector-all
>>>> (...)
>>>
>
> This was actually a bug in the build system.
> Update from CVS and FTP and you should be OK.

Ok, I rebuilt a full DL1.3, from scratch and the compilation was fine..

But, I still have some little usb problems :

- On vmware, the usb key is not found.
I burned (a real) cd an test it and usb key was found, on /dev/sda1, but 
on vmware the /dev/sda1 isn't in the list of search device...
On 1.2.x, I never had any problem...
vmware is more usefull than for simple tests:  it can give you a very 
simple and usefull backup system... and for development, this is really 
great...

- On the "real pc", the usb key is found and the configuration is saved 
during the boot sequence, but the save-config, doesn't want to mount the 
msdos filesystem of the key :

Found configuration file location used by boot: /dev/sda1
using device /dev/sda1
mount unknown filesystem type 'msdfos'
please insert Configuration Media in /dev/sda1
(..)

Regards,
    - pjluc

-- 
Jean-Luc Parouty - Phone: +33 4 387 823 90
Institut de Biologie Structurale-CNRS (UMR 5075)/CEA/UJF - IBS
41 Av. Jules Horowitz - 38027 Grenoble Cedex 1 - France

Re: [Devil-linux-develop] DL1.3: glibc compilation failed / -no-pie ? -fno-stack-protector-all ?

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

Jean-Luc Parouty wrote:

> Heiko Zuerker wrote:
>
>> Jean-Luc Parouty wrote:
>>
>>>
>>> Hello,
>>> I try to compile cvs current 1.3, but the glibc compilation failed...
>>> ... it seems that gcc receive too unknown options :
>>>    -no-pie
>>>    -fno-stack-protector-all
>>> I "hack" the scripts/glibc to remove them and it seems ok..
>>> Any ideas ?
>>

This was actually a bug in the build system.
Update from CVS and FTP and you should be OK.

-- 

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

Re: [Devil-linux-develop] DL-1.3 - usb detection problem..

[Jean-Luc P. <Jea...@ib...>]

ee...@fr... wrote:

> (...)
>
>as I understand, you expected a guest vmware OS to detect an usb stick plugged
>in his host system ?
>  
>
Of course :-)
It' works fine, I built and test many Devil like that ;-)

>What's you vmware version ? Your host OS ?
>  
>
I use a vmware workstation v 4.5.2, under a... xp sp2 (sorry ;-)

>Maybe have a look at that page :
>http://www.vmware.com/support/ws45/doc/devices_usb_ws.html#1040892
>or try some search in their knowledge base ... usb support seems "fragile" ...
>  
>
I known that, but I think that the problem isn't a vmware problem.
I tried to boot with a compiled 1.2.3 without any problem, with the same 
vmware and usb key...

Anyway I'll try to rebuilt a full new 1.3 and test it again next week.
If nobody had any usb problem, probably that the only gremlins is in my 
office ;-)

I'll be back thuesday, so don't worry about this if I'm the only one 
like that ;-)
Regards,
    - pjluc

-- 
Jean-Luc Parouty - Phone: +33 4 387 823 90
Institut de Biologie Structurale-CNRS (UMR 5075)/CEA/UJF - IBS
41 Av. Jules Horowitz - 38027 Grenoble Cedex 1 - France

Re: [Devil-linux-develop] DL1.3: glibc compilation failed / -no-pie ? -fno-stack-protector-all ?

[Jean-Luc P. <Jea...@ib...>]

Heiko Zuerker wrote:

> Jean-Luc Parouty wrote:
>
>>
>> Hello,
>> I try to compile cvs current 1.3, but the glibc compilation failed...
>> ... it seems that gcc receive too unknown options :
>>    -no-pie
>>    -fno-stack-protector-all
>> I "hack" the scripts/glibc to remove them and it seems ok..
>> Any ideas ?
>
>
>
> That should not be.
> Did you use the correct lfssystem? 1.3 needs a newer one, which you 
> can find on the ftp server.
>
I think, I used the "lfssystem-6.0-i686.tar", and tried to use 
differents usb token, and one type of them is used on 6 other Devil box, 
I recompiled before (1.2.1)

Anyway I'll try to rebuild another 1.3 as soon as possible ;-)

    - pjluc

-- 
Jean-Luc Parouty - Phone: +33 4 387 823 90
Institut de Biologie Structurale-CNRS (UMR 5075)/CEA/UJF - IBS
41 Av. Jules Horowitz - 38027 Grenoble Cedex 1 - France

Re: [Devil-linux-develop] DL-1.3 - usb detection problem..

[<ee...@fr...>]

Hi all,

Heiko Zuerker wrote:
> Jean-Luc Parouty wrote:
>
>> Hi,
>> Well... I compiled the 1.3 and had a bootcd.iso :-)
>> I tried to boot it with vmware, and it boot... :-)
>>
>> ...but usb keys are not detected :-(

as I understand, you expected a guest vmware OS to detect an usb stick pl=
ugged
in his host system ?

What's you vmware version ? Your host OS ?

Maybe have a look at that page :

 http://www.vmware.com/support/ws45/doc/devices_usb_ws.html#1040892

or try some search in their knowledge base ... usb support seems "fragile=
" ...

>> I had to add a virtual disk and I finished the boot session...

There is no problem, only solutions ;-)

Maybe at some point you can burn a CD-RW and test on real hardware ...

>> Sorry, I don't know anything about usb stuff, so I can just give you
>> the dmesg traces
>> but no patch...
>
>
> It doesn't detect the usb key at all.
> Does it work with a 1.2 CD on the same system?
> Can you try another usb key (best a different brand) ?
>

Regards

MaNU
--