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

-- 

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


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

Quoting "Serge Leschinsky" <fi...@in...>:

> Hello,
>
> Fred Frigerio wrote:
>> I am having a problem with postfix wanting to have a /var/lib/postfix
>> directory that is missing from the ISO. Postfix keeps a master.lock file
>> there. That is blocking postfix starting up. Creating the directory with
>> postfix:root access solves the problem. Maybe on your next build you can
>> check and add it to the bootcd.iso?
>>
> I looked into the build-install script and added several lines in order to
> create missed dir and to modify data_dir.
>
> What do you think if we will change our "per file" installation script to
> internal postfix-install? I think it will be much easier to maintain...
>
> I suggest to use the following line....
>
> bash postfix-install -non-interactive -package install_root=$TMPDIR

Good idea, let's give this a try.

-- 

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


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

Hello,

Fred Frigerio wrote:
> I am having a problem with postfix wanting to have a /var/lib/postfix
> directory that is missing from the ISO. Postfix keeps a master.lock file
> there. That is blocking postfix starting up. Creating the directory with
> postfix:root access solves the problem. Maybe on your next build you can
> check and add it to the bootcd.iso?
> 
I looked into the build-install script and added several lines in order to
create missed dir and to modify data_dir.

What do you think if we will change our "per file" installation script to
internal postfix-install? I think it will be much easier to maintain...

I suggest to use the following line....

bash postfix-install -non-interactive -package install_root=$TMPDIR

--
Serge

Hi,

	Can you add siproxd to the list of apps that need updating please.  Not urgent.

current-version: 0.5.13  latest version:  0.7.1

Thanks

Dick

I ran a fresh server compile last night with the latest changes Serge
made to install-on-usb and the kernel for the SATA CD drive boot
problem.  Please download and test out these changes.

This build is on the FTP server, under /pub/devel/testing

 - BS

Hello,

I've developed a piece of code in order to load ata/sata/scsi modules from
initrd (sata/scsi hdd and cdroms support, actually). It has pushed me to become
acquainted with sysfs architecture :-). So, the code takes information from
sysfs in order to be independent from busybox's realization of mdev. Also I
found a problem during my testing - the dependencies of ATA/SATA/SCSI modules
were resolved not completely. So, I've added a trivial check for modules
dependencies to be sure _any_ modules may be loaded from initrd.  But there is a
small problem - I have not enough hardware to test the changes, only one box
with NVIDIA system logic.

So, it'll be very appreciated if you can help me with testing DL from SATA/SCSI
devices.

And, as usual, any feedbacks are welcome!

--
Sincerely
Serge

Bruce,

It's my fault. I think we already can turn it on for both profiles. I'll do it.

--
Serge

Bruce Smith wrote:
> Serge, should the newly added flowtools be turned on in the
> default/server profiles?
> 
> Currently "CONFIG_FLOWTOOLS" is not set in any profile.
> 
>  - BS

Serge, should the newly added flowtools be turned on in the
default/server profiles?

Currently "CONFIG_FLOWTOOLS" is not set in any profile.

 - BS

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

>>> But then what?  I haven't been able to find any docs about how to
>>> compile it.  I'm guessing I need to add something to PHP's
>>> ./configure, but I'm not sure what.  Something like "--with-http" or
>>> "--with-pecl_http" or ... but what exactly?  I've searched the
>>> ./configure source, but don't see any references to this extension.
>>
>> Unpack the file and then look into the config*.m4 files.
>> In the top part of the files you'll see the additional configure parameters.
>
> Cool, thanks!
>
> When I unpacked it in an empty directory, I get:
>
> -rw-r--r-- 1 bruce bruce 12820 2008-07-23 04:28 package.xml
> -rw-r--r-- 1 bruce bruce 22175 2008-07-23 04:28 package2.xml
> drwxr-xr-x 6 root  root   4096 2008-08-22 10:47 pecl_http-1.6.1
>
> Are the two xml files in the local directory going to be a problem?
> (will they overwrite or conflict with other pecl extenstions?)

No clue.
I would just try it the way it is and see what happens.


-- 

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


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

>> But then what?  I haven't been able to find any docs about how to
>> compile it.  I'm guessing I need to add something to PHP's
>> ./configure, but I'm not sure what.  Something like "--with-http" or
>> "--with-pecl_http" or ... but what exactly?  I've searched the
>> ./configure source, but don't see any references to this extension.
>
> Unpack the file and then look into the config*.m4 files.
> In the top part of the files you'll see the additional configure parameters.

Cool, thanks!

When I unpacked it in an empty directory, I get:

-rw-r--r-- 1 bruce bruce 12820 2008-07-23 04:28 package.xml
-rw-r--r-- 1 bruce bruce 22175 2008-07-23 04:28 package2.xml
drwxr-xr-x 6 root  root   4096 2008-08-22 10:47 pecl_http-1.6.1

Are the two xml files in the local directory going to be a problem?
(will they overwrite or conflict with other pecl extenstions?)

  - BS

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

> I'd like to add "pecl_http" to PHP on DL 1.3, but I'm stuck.
> http://www.php.net/http
> http://pecl.php.net/package/pecl_http
>
> I think I need to add pecl_http-1.6.1.tgz to src/pecl/ and it should
> get unpacked in tmp/php-5.../ext/

Correct, just throw it in src/pecl

> But then what?  I haven't been able to find any docs about how to
> compile it.  I'm guessing I need to add something to PHP's
> ./configure, but I'm not sure what.  Something like "--with-http" or
> "--with-pecl_http" or ... but what exactly?  I've searched the
> ./configure source, but don't see any references to this extension.

Unpack the file and then look into the config*.m4 files.
In the top part of the files you'll see the additional configure parameters.

-- 

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


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

I'd like to add "pecl_http" to PHP on DL 1.3, but I'm stuck.
http://www.php.net/http
http://pecl.php.net/package/pecl_http

I think I need to add pecl_http-1.6.1.tgz to src/pecl/ and it should
get unpacked in tmp/php-5.../ext/

But then what?  I haven't been able to find any docs about how to
compile it.  I'm guessing I need to add something to PHP's
./configure, but I'm not sure what.  Something like "--with-http" or
"--with-pecl_http" or ... but what exactly?  I've searched the
./configure source, but don't see any references to this extension.

  - BS

Hello,

Geir Inge wrote:

> Installing the 1.3.6 release on a usb stick with the included
> install-on-usb script gives the same problems as the 1.5.12 release
> (run on a ubuntu hardy machine) :
> 
> 1) selecting lilo as the bootloader, the script fails:
> ...
The script tries to copy the files which are absent in the system. I don't know
if it's a recently added to the script bug or differences between 1.3 and 1.2
systems. I'll look.

> 
> 2) selecting syslinux as bootloader, the script fails:
> 
> Installing syslinux MBR
> 0+1 records in
> 0+1 records out
> 404 bytes (404 B) copied, 0.00895628 s, 45.1 kB/s
> installing SysLinux boot sector
> umount: /tmp/syslinux.mnt.4674.0: device is busy
> umount: /tmp/syslinux.mnt.4674.0: device is busy
> Install failed!
> syncing and unmounting (this could take a while)
I've checked it from DL and it looks working.

	This will install DL on "/dev/hda" using the "syslinux" bootloader.
	All data on device /dev/hda2 will be lost, continue ?  (y/n) y

	Last chance, do you really want to continue ?  (y/n) y
	Installing syslinux MBR
	0+1 records in
	0+1 records out
	404 bytes (404 B) copied, 0.0128979 s, 31.3 kB/s
	installing SysLinux boot sector
	copying files
	copying image of CD in /dev/hdc to device mounted on 				
/tmp/tmp-install2usb/disk-mnt/bootcd.iso
	153320+0 records in
	153320+0 records out
	313999360 bytes (314 MB) copied, 79.4215 s, 4.0 MB/s
	syncing and unmounting (this could take a while)

Maybe it's the consequence of previous unsuccessful attempts? If not, and you
are able to reproduce the error may I  ask you to gather debug information?

> Selecting grub (no serial), the script fails (work ok on the 1.2.15
> release) with:
> 
> Configuring Grub boot sector and menu...
> Do you want to edit the grub menu file  (y/n) n
> Probing devices to guess BIOS drives. This may take a long time.
> ./install-on-usb: line 119:  5069 Segmentation fault      $grub_shell
> --batch --device-map=$device_map  > /dev/null <<-EOF
> root $root_drive
> setup $force_lba $install_drive
> quit
> EOF

PAX: From 10.1.6.104: execution attempt in: <anonymous mapping>,
4e0db000-4e4de000 4e0db000
PAX: terminating task: /sbin/grub(grub):2722, uid/euid: 0/0, PC: 4e144c0e, SP:
4e144ac8
PAX: bytes at PC: b9 f0 4b 14 4e e9 fc 22 f1 b9 08 4e 14 4e 00 4e 14 4e 68 b6
PAX: bytes at SP-4: 00000000 0804b685 00000001 00000000 00000200 4e144af4
0000003f 00000200 00000000 4e144e01 00000009 0000003e 4e14d200 00000200 00000000
00000001 4e144b44 0804cac5 00000080 00000001 00000000

So, it's grsecurity's side effect. I'm going to update grsecurity and PAX to the
latest version and check if the problem goes away.

--
Serge

Quoting Dick Middleton <di...@fo...>:

> Hello,
>
> 	I'm still using 1.3.5-2008-05-01.  I notice that the kernel module nbd
> exists but there is no nbd-server or nbd-client software.
>
> I think, but not 100% sure, that nbd module is only required for client.
>
> I've no idea if there is any demand for nbd on DL.

I'm not aware of anyone using it.
But that doesn't mean we can't include it. It all depends on someone  
adding it. ;-)

-- 

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


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

Hello,

	I'm still using 1.3.5-2008-05-01.  I notice that the kernel module nbd 
exists but there is no nbd-server or nbd-client software.

I think, but not 100% sure, that nbd module is only required for client.

I've no idea if there is any demand for nbd on DL.

Dick

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

>> are we ready for 1.2.15?
>
> I guess.  Unless you want to upload a release candidate for testing first.

I uploaded one last night.
I'll send out an email

-- 

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


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

> are we ready for 1.2.15?

I guess.  Unless you want to upload a release candidate for testing first.

 - BS

Hey,

are we ready for 1.2.15?

-- 

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


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

Quoting John Boden <sag...@gm...>:

> Hi Heiko,
>
> Thanks for letting me know :-)
>
> Yesterday, I got some sort of failure to load module when I tried
> to restart eth0 under 1.2.13. I've never seen such an error
> when restarting an eth0 under any linux.  I've used 1.2.13 for the past year,
> via the original image (bootcd.iso); this was under one of the  
> images I created
> that did boot. I wonder if there is a problem with the compression.of
> the disk image
> (mkzftree).

There shouldn't be a problem with that, since we didn't touch that  
code in ages.
You can simply turn it off and re-create the iso to confirm your suspicion.

-- 

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


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

Hi Heiko,

Thanks for letting me know :-)

Yesterday, I got some sort of failure to load module when I tried
to restart eth0 under 1.2.13. I've never seen such an error
when restarting an eth0 under any linux.  I've used 1.2.13 for the past year,
via the original image (bootcd.iso); this was under one of the images I created
that did boot. I wonder if there is a problem with the compression.of
the disk image
(mkzftree).

Chip

Hey,

not sure what the problem is.
I'm uploading the latest 1.3.6 version to the ftp server right now,  
get it from the testing directory about an hour after I sent this email.
Maybe that one works better.

Heiko

Quoting John Boden <sag...@gm...>:

> Hi Heiko or whomever,
>
> I had the same failure with the e100 module.
>
> Thanks,
> Chip
>
>
> On Mon, Jun 16, 2008 at 12:29 PM, Heiko Zuerker <he...@zu...> wrote:
>> Hey,
>>
>> Quoting John Boden <sag...@gm...>:
>>
>>> Hi Heiko,
>>>
>>>> did you set up the interface via the setup program?
>>> yes
>>>
>>>> It would also be helpful if you post your ifcfg-eth0 file here.
>>> I did not hand edit it, but I will gladly retype it here to avoid  
>>> ambiguity.
>>>
>>>> cat /etc/sysconfig/nic/ifcfg-eth0
>>>
>>> DEVICE=eth0
>>> ONBOOT=yes
>>> MODULE="eepro100"
>>> DHCP=yes
>>> IP=
>>> NETMASK=
>>> BROADCAST=""
>>>
>>> & lspci shows
>>> .. Intel Corporation 82557/8/9 Ethernet Pro 100 (rev 08)
>>
>> Use Intel's e100 module, that one should work.
>>
>> --
>>
>> Regards
>>   Heiko Zuerker
>>   http://www.devil-linux.org
>>
>>
>> ----------------------------------------------------------------
>> This message was sent using IMP, the Internet Messaging Program.
>>
>>
>>
>> -------------------------------------------------------------------------
>> Check out the new SourceForge.net Marketplace.
>> It's the best place to buy or sell services for
>> just about anything Open Source.
>> http://sourceforge.net/services/buy/index.php
>> _______________________________________________
>> Devil-linux-develop mailing list
>> Dev...@li...
>> https://lists.sourceforge.net/lists/listinfo/devil-linux-develop
>>
>
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> _______________________________________________
> Devil-linux-develop mailing list
> Dev...@li...
> https://lists.sourceforge.net/lists/listinfo/devil-linux-develop
>



-- 

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


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

Quoting John Boden <sag...@gm...>:

>> Which version are you trying to compile, 1.2 or 1.3 ?
>
> 1.3. I got the current development version a couple weeks ago.

okay make sure you use lfssystem-for-DL-1.3.4_and_up for this one.

>> Depending on which version you have to use a different lfssystem-xxxx
>> build environment. Which one are you using?
>
> I'll need to get back with you on that. I just followed the intructions.
> I should have emailed you sooner, when things were fresher in my mind.
>
>> And yes, the default configuration should build without any problems.
>> Did you select something with the parallel builds? If yes, set it down
>> to 1 and try again.
>
> It will prolly be about a week before I'll be able to get back to it.
> I'll keep you posted.

okay

-- 

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


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

> Which version are you trying to compile, 1.2 or 1.3 ?

1.3. I got the current development version a couple weeks ago.

> Depending on which version you have to use a different lfssystem-xxxx
> build environment. Which one are you using?

I'll need to get back with you on that. I just followed the intructions.
I should have emailed you sooner, when things were fresher in my mind.

> And yes, the default configuration should build without any problems.
> Did you select something with the parallel builds? If yes, set it down
> to 1 and try again.

It will prolly be about a week before I'll be able to get back to it.
I'll keep you posted.

Thank you!
Chip

Quoting John Boden <sag...@gm...>:

> Hi folks,
>
> I hope you folks don't mind so many posts from me.
>
> I kept getting compilation errors. I would go back to the
> menu-based system config to deselect problem packages or to select packages
> that appeared necessary for a dependency. After about 6 iterations and
> after hitting at least one package that would "make install" manually, but
> caused the overall make to stop, I took a break.
>
> Am I missing something.
> Is there a list of packages that do compile?
> Are the original settings of the system configution
> supposed to give a (relatively) straightforard, working
> "make"?

Which version are you trying to compile, 1.2 or 1.3 ?
Depending on which version you have to use a different lfssystem-xxxx  
build environment. Which one are you using?

And yes, the default configuration should build without any problems.
Did you select something with the parallel builds? If yes, set it down  
to 1 and try again.

-- 

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


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

Hi folks,

I hope you folks don't mind so many posts from me.

I kept getting compilation errors. I would go back to the
menu-based system config to deselect problem packages or to select packages
that appeared necessary for a dependency. After about 6 iterations and
after hitting at least one package that would "make install" manually, but
caused the overall make to stop, I took a break.

Am I missing something.
Is there a list of packages that do compile?
Are the original settings of the system configution
supposed to give a (relatively) straightforard, working
"make"?

Thank you,
Chip