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

Hey,

yes I have the same version.
I checked my config file and I already had the entries commented out,
that's probably why it worked.

Maybe we should comment it out in our default config (do you have time to
do it?).

Heiko

On Tue, October 30, 2007 13:34, Bruce Smith wrote:
>>> I have it setup with the standard 2NIC firewall, running a DHCP
>>> server on the internal network.  NAT works fine, as I can connect to
>>> the internet with my laptop, using the 1.3 DL box as my firewall.
>>>
>>> I am having a weird problem with networking.  sshd wouldn't start.
>>> It
>>> kept complaining that the port 0.0.0.0:22 was already in use.  I
>>> changed the port it listens on to a high number, and it still gave the
>>> same error (with the new port number).  'netstat -aepn' shows NO TCP
>>> connections listening at all, only UDP and RAW listening for dhcpd.
>>>
>>> I changed sshd_config to manually specify the IP addresses of both
>>> NIC's
>>> and now sshd starts fine.
>>>
>>> I removed IPV6 routing from the config, with no difference.
>>>
>>>
>>> Something is really weird ...  Ideas???
>>>
>>
>> I'm using samba and ssh on my virtual machine which is running DL 1.3,
>> no such trouble. Although I don't have the firewall enabled.
>>
>> Can you disconnect the box from the web and try without firewall?
>>
>
> I just tried starting sshd in my VMware copy (brand new default config),
> and got the same error in tty10:
>
> Bind to port 22 on 0.0.0.0 failed: Address already in use.
>
>
> I did learn that if I uncomment this line in sshd_config, it works:
>
>
> ListenAddress ::
>
>
> OR, if I add this line in sshd_config (instead), it works:
>
>
> AddressFamily inet
>
>
> OpenSSH problem?
> Are you running the same version of ssh in your DL 1.3 (4.7p1)?
>
>
> - BS
>
>
>
>
> -------------------------------------------------------------------------
>  This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> Devil-linux-develop mailing list
> Dev...@li...
> https://lists.sourceforge.net/lists/listinfo/devil-linux-develop
>
>


-- 

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

> > OK, I have the latest 1.3 running on a real PC, connected to the
> > Internet with a static IP.  It didn't have any problem finding my IDE
> > CDROM drive (/dev/hdc).
> /dev/hdc ? Are you sure ? I'm requesting because PATA devices which work through
>  libata represent themselvs as SCSI (SATA) /dev/sdx...

It says hdc when it boots, and so does 'df' (copy/paste):

root@Devil:~ # df
Filesystem           1K-blocks      Used Available Use% Mounted on
rootfs                  266046    266046         0 100% /
none                    257504      9132    248372   4% /shm
/dev/hdc                266046    266046         0 100% /
none                    257504      9132    248372   4% /dev
root@Devil:~ # cat /DEVIL-LINUX  
1.3.4-2007-10-30
root@Devil:~ # uname -a
Linux Devil 2.6.23.1 #1 SMP Tue Oct 30 08:32:52...

 - BS

> > I have it setup with the standard 2NIC firewall, running a DHCP server
> > on the internal network.  NAT works fine, as I can connect to the internet
> > with my laptop, using the 1.3 DL box as my firewall.
> >
> > I am having a weird problem with networking.  sshd wouldn't start.  It
> > kept complaining that the port 0.0.0.0:22 was already in use.  I changed
> > the port it listens on to a high number, and it still gave the same error
> > (with the new port number).  'netstat -aepn' shows NO TCP
> > connections listening at all, only UDP and RAW listening for dhcpd.
> >
> > I changed sshd_config to manually specify the IP addresses of both NIC's
> > and now sshd starts fine.
> >
> > I removed IPV6 routing from the config, with no difference.
> >
> > Something is really weird ...  Ideas???
> 
> I'm using samba and ssh on my virtual machine which is running DL 1.3, no
> such trouble. Although I don't have the firewall enabled.
> 
> Can you disconnect the box from the web and try without firewall?

I just tried starting sshd in my VMware copy (brand new default config),
and got the same error in tty10:

Bind to port 22 on 0.0.0.0 failed: Address already in use.

I did learn that if I uncomment this line in sshd_config, it works:

  ListenAddress ::

OR, if I add this line in sshd_config (instead), it works:

  AddressFamily inet

OpenSSH problem?  
Are you running the same version of ssh in your DL 1.3 (4.7p1)?

 - BS

Hi Bruce,

Bruce Smith wrote:
> OK, I have the latest 1.3 running on a real PC, connected to the
> Internet with a static IP.  It didn't have any problem finding my IDE
> CDROM drive (/dev/hdc).
/dev/hdc ? Are you sure ? I'm requesting because PATA devices which work through
 libata represent themselvs as SCSI (SATA) /dev/sdx...

....
> I tried starting apache2 (std config).  It started and I can connect to
> it w/Firefox.  However a 'netstat -aepn' doesn't show it listening on
> port 80, but instead shows a STREAM listening for httpd.
> 
> I removed IPV6 routing from the config, with no difference.
> 
> Something is really weird ...  Ideas???
No ideas yet. I'll check it tomorrow.

-- 
Sincerely,
Serge Leschinsky

On Tue, October 30, 2007 13:09, Bruce Smith wrote:
> OK, I have the latest 1.3 running on a real PC, connected to the
> Internet with a static IP.  It didn't have any problem finding my IDE
> CDROM drive (/dev/hdc).
>
>
> I have it setup with the standard 2NIC firewall, running a DHCP server
> on the internal network.  NAT works fine, as I can connect to the internet
> with my laptop, using the 1.3 DL box as my firewall.
>
> I am having a weird problem with networking.  sshd wouldn't start.  It
> kept complaining that the port 0.0.0.0:22 was already in use.  I changed
> the port it listens on to a high number, and it still gave the same error
> (with the new port number).  'netstat -aepn' shows NO TCP
> connections listening at all, only UDP and RAW listening for dhcpd.
>
> I changed sshd_config to manually specify the IP addresses of both NIC's
> and now sshd starts fine.
>
> I tried starting apache2 (std config).  It started and I can connect to
> it w/Firefox.  However a 'netstat -aepn' doesn't show it listening on port
> 80, but instead shows a STREAM listening for httpd.
>
>
> I removed IPV6 routing from the config, with no difference.
>
>
> Something is really weird ...  Ideas???

I'm using samba and ssh on my virtual machine which is running DL 1.3, no
such trouble. Although I don't have the firewall enabled.

Can you disconnect the box from the web and try without firewall?

-- 

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

OK, I have the latest 1.3 running on a real PC, connected to the
Internet with a static IP.  It didn't have any problem finding my IDE
CDROM drive (/dev/hdc).

I have it setup with the standard 2NIC firewall, running a DHCP server
on the internal network.  NAT works fine, as I can connect to the
internet with my laptop, using the 1.3 DL box as my firewall.

I am having a weird problem with networking.  sshd wouldn't start.  It
kept complaining that the port 0.0.0.0:22 was already in use.  I changed
the port it listens on to a high number, and it still gave the same
error (with the new port number).  'netstat -aepn' shows NO TCP
connections listening at all, only UDP and RAW listening for dhcpd.

I changed sshd_config to manually specify the IP addresses of both NIC's
and now sshd starts fine.

I tried starting apache2 (std config).  It started and I can connect to
it w/Firefox.  However a 'netstat -aepn' doesn't show it listening on
port 80, but instead shows a STREAM listening for httpd.

I removed IPV6 routing from the config, with no difference.

Something is really weird ...  Ideas???

 - BS

Heiko,

Heiko Zuerker wrote:

>>> Should we include all the new PATA and SATA drivers directly in the
>>> kernel? Then it would be like 1.2, where only the SCSI drivers are
>>> modules.
>> It's a way... Basically, I think it will be better to invent possibility
>> to load modules from linuxrc.
> 
> Actually the problem I think already solved itself.
> When we initialize mdev (the busybox udev version), it seems to auto load
> all the required modules. We could give it a try and move all the IDE
> drivers to a module, this may save us quite a bit kernel space.
I can be wrong, but I think mdev creates devices after scanning /sys. I checked
/sys when was investigating why my box didn't boot. There was no information
about HDD or CD, so mdev didn't create devices.

As I have rebuilt the kernel I can't reproduce the problem. Just now my box is
busy by building the system with recent changes and I hope I'll send the main
parts of logs/system settings tomorrow.

-- 
Sincerely
Serge Leschinsky

On Tue, October 30, 2007 08:23, Serge Leschinsky wrote:
> Heiko,
>
>
> Heiko Zuerker wrote:
>
>> On Tue, October 30, 2007 05:32, Serge Leschinsky wrote:
>>
>
>> The 1.3 is running stable in my system.
>>
> If I boot the system it works ok. Crashes usually arise during initrd
> phase.

Hmmm

>> Should we include all the new PATA and SATA drivers directly in the
>> kernel? Then it would be like 1.2, where only the SCSI drivers are
>> modules.
> It's a way... Basically, I think it will be better to invent possibility
> to load modules from linuxrc.

Actually the problem I think already solved itself.
When we initialize mdev (the busybox udev version), it seems to auto load
all the required modules. We could give it a try and move all the IDE
drivers to a module, this may save us quite a bit kernel space.


-- 

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

Heiko,

Heiko Zuerker wrote:
> On Tue, October 30, 2007 05:32, Serge Leschinsky wrote:

> The 1.3 is running stable in my system.
If I boot the system it works ok. Crashes usually arise during initrd phase.

> Should we include all the new PATA and SATA drivers directly in the
> kernel? Then it would be like 1.2, where only the SCSI drivers are
> modules.
It's a way... Basically, I think it will be better to invent possibility to load
modules from linuxrc.


-- 
Sincerely
Serge Leschinsky

> > FYI: I've got an ISO and tried to boot it. There is a problem with PATA
> > devices (my test box is intel based with pata cdrom and hdd). The linuxrc
> > has no possibility to determine device type and load appropriate modules,
> > so I got error "Please check your Hardware!" after media searching. If I
> > am able to find configs I can use INITRD_MODULES config option, but how to
> > find configs.... As a workaround I did the following: - added
> > kernel/drivers/ata/* to initrd - added optional request for probing
> > SCSI/ATA controllers (if $CONFIG_SRC_LIST
> > is empty ) I've got kernel crash at least 3 times :-(
> > So, now I've rebuild kernel (with statically included drivers for intel)
> > and moved forward in my testing.
> 
> The 1.3 is running stable in my system.

I compiled a new 1.3 last night (after Heiko's latest updates), and it
booted fine in VMware-workstation this morning with a emulated IDE CD.

There were a bunch of udevd & modprobe errors, but it didn't stop it
from booting, and it appears to run fine.

I might burn a CD and run it on real hardware later.

> Should we include all the new PATA and SATA drivers directly in the
> kernel? Then it would be like 1.2, where only the SCSI drivers are
> modules.

IMO, it'd be best to leave them as modules, if possible.

 - BS

On Tue, October 30, 2007 05:32, Serge Leschinsky wrote:
> Hi,
>
>
> Heiko Zuerker wrote:
>
>
>>>
>>> I just completed a compile, then I did a build and install of ncftp
>>> manually (./build.sh build opt=ncftp) and it appeared to compile fine.
>>>
> Ok. I'll add ncftp to my test config file
> ...
>
>>> One other problem I ran into was I had to turn set "AOE6=n" since
>>> it's build aborted.
>>
>> Yes that's correct.
>> The package is lacking support for the latest kernel.
>>
> Yes. The support of 2.6.23rc3 only is declared. I'm going to write a
> message to the AoE list - may be the developers will help me with patch.
>
> FYI: I've got an ISO and tried to boot it. There is a problem with PATA
> devices (my test box is intel based with pata cdrom and hdd). The linuxrc
> has no possibility to determine device type and load appropriate modules,
> so I got error "Please check your Hardware!" after media searching. If I
> am able to find configs I can use INITRD_MODULES config option, but how to
> find configs.... As a workaround I did the following: - added
> kernel/drivers/ata/* to initrd - added optional request for probing
> SCSI/ATA controllers (if $CONFIG_SRC_LIST
> is empty ) I've got kernel crash at least 3 times :-(
> So, now I've rebuild kernel (with statically included drivers for intel)
> and moved forward in my testing.

The 1.3 is running stable in my system.
Should we include all the new PATA and SATA drivers directly in the
kernel? Then it would be like 1.2, where only the SCSI drivers are
modules.

-- 

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

Hi,

Heiko Zuerker wrote:

>>
>> I just completed a compile, then I did a build and install of ncftp
>> manually (./build.sh build opt=ncftp) and it appeared to compile fine.
Ok. I'll add ncftp to my test config file
...
>> One other problem I ran into was I had to turn set "AOE6=n" since it's
>> build aborted.
> 
> Yes that's correct.
> The package is lacking support for the latest kernel.
Yes. The support of 2.6.23rc3 only is declared. I'm going to write a message to
the AoE list - may be the developers will help me with patch.

FYI: I've got an ISO and tried to boot it. There is a problem with PATA devices
(my test box is intel based with pata cdrom and hdd). The linuxrc has no
possibility to determine device type and load appropriate modules, so I got
error "Please check your Hardware!" after media searching. If I am able to find
configs I can use INITRD_MODULES config option, but how to find configs.... As a
workaround I did the following:
- added kernel/drivers/ata/* to initrd
- added optional request for probing SCSI/ATA controllers (if $CONFIG_SRC_LIST
is empty )
I've got kernel crash at least 3 times :-(
So, now I've rebuild kernel (with statically included drivers for intel) and
moved forward in my testing.

--
Sincerely
Serge Leschinsky

Hey,

I'm moving this discussion to the develop mailinglist.

On Mon, October 29, 2007 18:41, Bruce Smith wrote:
> Serge Leschinsky wrote:
>
>> Thank you! If somebody wants to build custom iso from CVS, the
>> following options help him to avoid compilation errors ( all other
>> options may be enabled )
>>
>> CONFIG_ALSA=n
>> CONFIG_CLAMAV_PATCH=n
>> CONFIG_DISTCCD=n
>> CONFIG_EAGLE_USB=n
>> CONFIG_GRSECURITY=n
>> CONFIG_L2TPD=n
>> CONFIG_NCFTP=n
>> CONFIG_PORTSLAVE=n
>> CONFIG_RPM=n
>> CONFIG_USE_DISTCC=n
>>
>>
>
> Thanks for the tips.
>
>
> I just completed a compile, then I did a build and install of ncftp
> manually (./build.sh build opt=ncftp) and it appeared to compile fine.

Yeah most of the packages compile now.
These are the ones I have disabled:
CONFIG_ALSA=n
CONFIG_AOE6=n
CONFIG_CLAMAV_PATCH=n
CONFIG_DISABLELOGGING=n
CONFIG_DISTCCD=n
CONFIG_EAGLE_USB=n
CONFIG_GRSECURITY=n
CONFIG_L2TPD=n
CONFIG_LINUX_SYSRQ=n
CONFIG_PORTSLAVE=n
CONFIG_RPM=n
CONFIG_USE_DISTCC=n


> One other problem I ran into was I had to turn set "AOE6=n" since it's
> build aborted.

Yes that's correct.
The package is lacking support for the latest kernel.

I got a few updates I have to upload, I'll probably do that tonight.

-- 

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

> >> Check if sendfile is turned off in the httpd.conf.
> >
> > That fixed it, thanks!
> 
> It should have been turned off by our build script.
> Did you use the httpd.conf which came with DL ?

I probably kept my old one on the upgrade.
It was really old, and I wasn't using Apache before.

 - BS

On Tue, October 23, 2007 12:23, Bruce Smith wrote:
>> Check if sendfile is turned off in the httpd.conf.
>>
>
> That fixed it, thanks!

It should have been turned off by our build script.
Did you use the httpd.conf which came with DL ?

-- 

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

> Check if sendfile is turned off in the httpd.conf.

That fixed it, thanks!

 - BS

On Tue, October 23, 2007 10:53, Bruce Smith wrote:
> Is there some trick to getting Apache to run on the latest DL 1.2?
> (the DL I compiled last night -- server config)
>
>
> Using the default httpd.conf (with minor changes, like the root dir),
> .html files do NOT display.  They come up with a completely blank page,
> and a browser "display-source" shows NOTHING.  Graphics files will NOT
> serve up either (I tried .jpg .png and .gif files), they only display the
> URL to the graphics file in the browser.
>
>
> If I add PHP in the httpd.conf, then .php pages run OK, but .html
> and .jpg files still won't display.  Like it's missing the default engine
> to display stuff.
>
> It's probably some minor config file problem, but I can't find it.
> I made sure that the mime.types and magic files are there and set.
>
>
> Ideas?  Help!?!?  :-)

I updated php but didn't touch apache.

Check if sendfile is turned off in the httpd.conf.

-- 

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

Is there some trick to getting Apache to run on the latest DL 1.2?
(the DL I compiled last night -- server config)

Using the default httpd.conf (with minor changes, like the root dir), 
.html files do NOT display.  They come up with a completely blank page,
and a browser "display-source" shows NOTHING.  Graphics files will NOT
serve up either (I tried .jpg .png and .gif files), they only display
the URL to the graphics file in the browser.

If I add PHP in the httpd.conf, then .php pages run OK, but .html
and .jpg files still won't display.  Like it's missing the default
engine to display stuff.

It's probably some minor config file problem, but I can't find it.  
I made sure that the mime.types and magic files are there and set.

Ideas?  Help!?!?  :-)

 - BS

Heiko Zuerker wrote:
> On Tue, October 23, 2007 07:24, Serge Leschinsky wrote:
>> Hi,
>>
>>
>> May I ask for an advice for ipsec-tools compiling?
...
Ok, thank you!

--
Sincerely
Serge Leschinsky

On Tue, October 23, 2007 07:24, Serge Leschinsky wrote:
> Hi,
>
>
> May I ask for an advice for ipsec-tools compiling?
>
>
> Now we compile the package with CC="gcc -D_FORTIFY_SOURCE=0" and it's ok.
>  Compilation _with_ FORTIFY_SOURCE  fails, due to options '-Werror'
> (warnings are
> treated as errors). So my question is: what is preferable - to leave it as
> it is, or add FORTIFY_SOURCE and trivial patch for cutting '-Werror' from
> Makefiles?

I wouldn't worry about patches as long as we can specify CC="gcc
-D_FORTIFY_SOURCE=0" on the command line.
This is much easier for us to maintain.

> Another question is - I believe "copy_libs" should be the latest in
> install section. Yes?
>
> My build output:
>
>
> executing alsa-utils with option install (in
> /data/build/tmp/alsa-utils-1.0.2)
> executing cfg_runlevel with option install *executing copy_libs with option
> install executing devildoc with option install *executing ipsec-tools with
> option install (in /data/build/tmp/ipsec-tools-0.7) executing man-pages
> with option install (in /data/build/tmp/man-pages-1.65)

Yes you're right, that's wrong.
copy_libs should be at the end.

-- 

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

Hi,

May I ask for an advice for ipsec-tools compiling?

Now we compile the package with CC="gcc -D_FORTIFY_SOURCE=0" and it's ok.
Compilation _with_ FORTIFY_SOURCE  fails, due to options '-Werror' (warnings are
treated as errors). So my question is: what is preferable - to leave it as it
is, or add FORTIFY_SOURCE and trivial patch for cutting '-Werror' from Makefiles?


Another question is - I believe "copy_libs" should be the latest in install
section. Yes?

My build output:

 executing alsa-utils with option install (in /data/build/tmp/alsa-utils-1.0.2)
 executing cfg_runlevel with option install
*executing copy_libs with option install
 executing devildoc with option install
*executing ipsec-tools with option install (in /data/build/tmp/ipsec-tools-0.7)
 executing man-pages with option install (in /data/build/tmp/man-pages-1.65)


--
Sincerely
Serge Leschinsky

>> You know what, screw glibc 2.3.6
>>
>> I rather put my energy in DL 1.3
>>     
>
> Agree.  I'll run another 1.2 compile and see what happens.
>   

The glibc 2.3.2 compile finished without problem.

 - BS

> > Do you have glibc downgraded yet?  I'm getting an error on update_src:
> 
> I probably was still uploading when you tried. It's finished now, so give
> it another shot.

Yup, works now.

 - BS

On Mon, October 22, 2007 14:43, Bruce Smith wrote:
>> You know what, screw glibc 2.3.6
>>
>>
>> I rather put my energy in DL 1.3
>>
>
> Agree.  I'll run another 1.2 compile and see what happens.
>
>
> Do you have glibc downgraded yet?  I'm getting an error on update_src:

I probably was still uploading when you tried. It's finished now, so give
it another shot.

-- 

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

> You know what, screw glibc 2.3.6
> 
> I rather put my energy in DL 1.3

Agree.  I'll run another 1.2 compile and see what happens.

Do you have glibc downgraded yet?  I'm getting an error on update_src:


UPDATING from Devil-Linux FTP-Server       Luxembourg-Kirchberg
Transferring file `glibc-2.3.2.tar.bz2'                    
Mirroring directory
`perl-ext'                                            
Mirroring directory `pom-addon'                                      
Mirroring directory `special'                                           
Removing old file `glibc-2.3.6.tar.bz2'                              
Removing old file `glibc-linuxthreads-2.3.6.tar.bz2'
Removing old file `glibc-patches.tar.bz2'
Total: 4 directories, 557 files, 0 symlinks
New: 1 file, 0 symlinks
13377170 bytes transferred in 47 seconds (276.0K/s)
Removed: 0 directories, 3 files, 0 symlinks

Verifying md5 checksums
src/glibc-linuxthreads-2.3.2.tar.bz2: FAILED open or read
src/glibc-patches.tar.bz2: FAILED open or read