devil-linux-develop — developer discussions

Re: [Devil-linux-develop] Adding mount points to /var?

[Tim T. <t....@co...>]

Heiko Zuerker wrote:

>>hzu...@ra... wrote:
>>
>>    
>>
>>>On 05/03/2004 10:31:14 PM Tim Tait wrote:
>>>
>>>
>>>      
>>>
>>>>I am using an IMAP server on my DL box, but I don't want to store the
>>>>IMAP stuff on the devil-linux vg because I want it to be on my RAID1 vg.
>>>>So I have a mount entry in fstab to mount over that point... but, if
>>>>there is no imap lv in the devil-linux vg, then devil-linux doesn't
>>>>autocreate a mount point... so my mount fails.
>>>>
>>>>Is there an easy way to create the mount points on-the-fly without
>>>>modifying scripts all the time, ie as you mount?
>>>>
>>>>If not, can we add the mount points for the usual devil-linux vg
>>>>automounts in /var so that they can easily be mounted elsewhere if
>>>>desired?
>>>>
>>>>
>>>>        
>>>>
>>>Actually the mount points get created dynamically, you can name the VGs
>>>however you want to.
>>>(Or in other words, there are no default VGs names anymore  (since 1.1))
>>>
>>>This you wont have any other option then modifying the init scripts.
>>>
>>>Heiko
>>>
>>>      
>>>
>>So I can put 'tmp' on a different vg than 'imap' and both will be
>>auto-mounted with the current DL setup?
>>    
>>
>
>Only the stuff in the devil-linux VG will be automounted.
>  
>
(Light dawns) So for any lv in the devil-linux vg, a mount point of the 
same name as the lv will be created in /var, and then mounted?

Tim

Re: [Devil-linux-develop] Adding mount points to /var?

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

> hzu...@ra... wrote:
>
>>On 05/03/2004 10:31:14 PM Tim Tait wrote:
>>
>>
>>>I am using an IMAP server on my DL box, but I don't want to store the
>>>IMAP stuff on the devil-linux vg because I want it to be on my RAID1 vg.
>>>So I have a mount entry in fstab to mount over that point... but, if
>>>there is no imap lv in the devil-linux vg, then devil-linux doesn't
>>>autocreate a mount point... so my mount fails.
>>>
>>>Is there an easy way to create the mount points on-the-fly without
>>>modifying scripts all the time, ie as you mount?
>>>
>>>If not, can we add the mount points for the usual devil-linux vg
>>>automounts in /var so that they can easily be mounted elsewhere if
>>>desired?
>>>
>>>
>>
>>Actually the mount points get created dynamically, you can name the VGs
>>however you want to.
>>(Or in other words, there are no default VGs names anymore  (since 1.1))
>>
>>This you wont have any other option then modifying the init scripts.
>>
>>Heiko
>>
> So I can put 'tmp' on a different vg than 'imap' and both will be
> auto-mounted with the current DL setup?

Only the stuff in the devil-linux VG will be automounted.

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

Re: [Devil-linux-develop] Adding mount points to /var?

[Tim T. <t....@co...>]

hzu...@ra... wrote:

>On 05/03/2004 10:31:14 PM Tim Tait wrote:
>  
>
>>I am using an IMAP server on my DL box, but I don't want to store the
>>IMAP stuff on the devil-linux vg because I want it to be on my RAID1 vg.
>>So I have a mount entry in fstab to mount over that point... but, if
>>there is no imap lv in the devil-linux vg, then devil-linux doesn't
>>autocreate a mount point... so my mount fails.
>>
>>Is there an easy way to create the mount points on-the-fly without
>>modifying scripts all the time, ie as you mount?
>>
>>If not, can we add the mount points for the usual devil-linux vg
>>automounts in /var so that they can easily be mounted elsewhere if
>>desired?
>>    
>>
>
>Actually the mount points get created dynamically, you can name the VGs
>however you want to.
>(Or in other words, there are no default VGs names anymore  (since 1.1))
>
>This you wont have any other option then modifying the init scripts.
>
>Heiko
>
So I can put 'tmp' on a different vg than 'imap' and both will be 
auto-mounted with the current DL setup?

Tim

Re: [Devil-linux-develop] Adding mount points to /var?

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

> On Tue, May 04, 2004 at 09:59:59AM -0400, hzu...@ra... wrote:
>> Actually the mount points get created dynamically, you can name the VGs
>> however you want to.
>> (Or in other words, there are no default VGs names anymore  (since 1.1))
>
> about this, where are the directories created for the mounting points?
> only on the make iso stage?

They are created dynamically on runtime, when "/etc/init.d/mountfs start"
is executed, which happens in /etc/init.d./boot.d

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

Re: [Devil-linux-develop] ipsec-tools 0.3.1 is available

[Oliver J. <oli...@mo...>]

On Tue, 2004-05-04 at 02:29, Heiko Zuerker wrote:
> Oliver Jehle wrote:
> > please replace on the ftp-site
> > 
> > http://sourceforge.net/projects/ipsec-tools/
> 
> DONE
> 
> Heiko
> 

thx
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by: Oracle 10g
> Get certified on the hottest thing ever to hit the market... Oracle 10g. 
> Take an Oracle 10g class now, and we'll give you the exam FREE. 
> http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
> _______________________________________________
> Devil-linux-develop mailing list
> Dev...@li...
> https://lists.sourceforge.net/lists/listinfo/devil-linux-develop

Re: [Devil-linux-develop] Adding mount points to /var?

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

On Tue, May 04, 2004 at 09:59:59AM -0400, hzu...@ra... wrote:
> Actually the mount points get created dynamically, you can name the VGs
> however you want to.
> (Or in other words, there are no default VGs names anymore  (since 1.1))

about this, where are the directories created for the mounting points? only on the make iso stage?

-- 
-- 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] NIC detection

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

On 05/04/2004 09:15:23 AM dld wrote:
>I believe one of the shortcomings of DL is that it is not able to scan
>for network cards and identify them.
>
>Have a look at www.ipcop.org (do the install yourself) and see how
>easily it detects the network card.
>
>No research and guessing which modules to load.
>
>It would be great to have such a feature in DL.

True.

We're still waiting for somebody who sends us a patch for this. ;-)

Heiko

Re: [Devil-linux-develop] Adding mount points to /var?

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

On 05/03/2004 10:31:14 PM Tim Tait wrote:
>I am using an IMAP server on my DL box, but I don't want to store the
>IMAP stuff on the devil-linux vg because I want it to be on my RAID1 vg.
>So I have a mount entry in fstab to mount over that point... but, if
>there is no imap lv in the devil-linux vg, then devil-linux doesn't
>autocreate a mount point... so my mount fails.
>
>Is there an easy way to create the mount points on-the-fly without
>modifying scripts all the time, ie as you mount?
>
>If not, can we add the mount points for the usual devil-linux vg
>automounts in /var so that they can easily be mounted elsewhere if
>desired?

Actually the mount points get created dynamically, you can name the VGs
however you want to.
(Or in other words, there are no default VGs names anymore  (since 1.1))

This you wont have any other option then modifying the init scripts.

Heiko

[Devil-linux-develop] NIC detection

[<dl...@nv...>]

Hi,

I believe one of the shortcomings of DL is that it is not able to scan for network cards and identify them.

Have a look at www.ipcop.org (do the install yourself) and see how easily it detects the network card.

No research and guessing which modules to load.

It would be great to have such a feature in DL.

Thanks

Nico

[Devil-linux-develop] Adding mount points to /var?

[Tim T. <t....@co...>]

I am using an IMAP server on my DL box, but I don't want to store the 
IMAP stuff on the devil-linux vg because I want it to be on my RAID1 vg. 
So I have a mount entry in fstab to mount over that point... but, if 
there is no imap lv in the devil-linux vg, then devil-linux doesn't 
autocreate a mount point... so my mount fails.

Is there an easy way to create the mount points on-the-fly without 
modifying scripts all the time, ie as you mount?

If not, can we add the mount points for the usual devil-linux vg 
automounts in /var so that they can easily be mounted elsewhere if desired?

Tim

Re: [Devil-linux-develop] 1.1 Freeze - too late to add?

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

William Gilmore wrote:
> Heiko et al,
> 
> Is it too late to request an add for 1.2.  I would like to have the following perl modules added.
> 
> IO-stringy-2.109.tar.gz  
> MailTools-1.62.tar.gz  
> MIME-tools-5.411a.tar.gz
> 
> Their addition will not require a script change only their addition to the  src/perl-ext directory and a recompile of perl.
> 
> The scripts are needed by sa-wrapper.pl script from http://jousset.org/pub/sa-postfix.en.html.  This script allows one to remotely train the Spamassassin Bayes filter by sending e-mail to the postfix server.  
> 
> This is use for those of us who do not run Linux based mail servers (Yes I am holding my head in shame as I accept my paycheck ;)  
> 
> Thanks for the consideration.

DONE

Heiko

Re: [Devil-linux-develop] LFTP

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

Bruce Smith wrote:
>>>If we include lftp in the lfssystem (if it's not already), then the docs
>>>should be modified telling people how to make the chroot env network
>>>(creating /etc/resolv.conf and ... anything else?).
>>
>>Just update the docs. ;-)
> 
> 
> I should download the software and learn how to do that sometime.
> 
> But since lftp isn't included in the lfssystem, there is no need, 
> and I can procrastinate a little while longer ...  ;->

Sometimes I would wish I could say: lazy ass
but that wouldn't be nice... ;-)

Heiko

Re: [Devil-linux-develop] apcuspd not created?

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

Roland Pabel wrote:
> On Friday 30 April 2004 09:50, Roland Pabel wrote:
> 
>>On Friday 30 April 2004 06:40, Tim Tait wrote:
>>
>>>My build from the latest on 4/28 failed to make apcupsd though it was
>>>selected. Log shows errors but it did not halt the build.
>>
>>strange...the build doesn't succeed but neither does it fail...the script
>>looks sane to me, every command in the build section is followed by '||
>>exit 1'
>>I'll test if reverting to 3.10.12 helps or if it's related to the kernel
>>update
> 
> ok, there are three bugs here:
> 1) why was the build succesful although it obviously failed - i don't know
> 2) there is a struct introduced 2.4.26 in include/linux/include/hiddev.h which 
> uses an undefined constant HID_MAX_USAGES, because it is actually defined in 
> drivers/usb/hid.h
> This needs to be fixed for any version of apcupsd. (apcupsd doesn't use the 
> struct which uses HID_MAX_USAGES, it's just the compiler complaining).
> Google shows this has been reported to LKML, but for some reason it was not 
> fixed...Please add linux-2.4.26-hiddev-rp.diff to kernel-patches-2.4.tar.bz2
> 3) Even when that is fixed, the build fails because Makefile targets can't be 
> found in several Makefiles. These vanish when using 'make all' instead of 
> 'make $PMAKE all', looks like apcupsd doesn't like parallel builds now...but 
> I'd recommend keeping 3.10.13, it got tons of bugfixes
> Please test my patches, they worked for me(tm)...

DONE

Heiko

Re: [Devil-linux-develop] Update kernel to 2.6.5 (testing)

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

Oliver Jehle wrote:
> another little bit of improving :-) the kernel 2.6 support ... 
> upgrade to 2.6.5... but its in testing state.. but better then nothing
> 
> config_linux
> --------------
> 
> the config_linux is only a patch against my .config
> as i can see, was the old  config-linux file only a manually updated
> file, and there is a little bit a mess to merge them together... 
> 
> ideas are welcome !!!
> 
> pax-grsecurity
> --------------
> 
> http://pax.grsecurity.org/grsecurity-2.0-2.6.5.patch
> renamed to pax..... 
> 
> looks that only the grsecurity is available now.. must be activated
> as framework, else compile of pax not work... :-( have not time to
> do some investigations.. 
> 
> 
> exec-shield 2.6.5
> -----------------
> http://people.redhat.com/mingo/exec-shield/
> 
> 
> 
> prepare script
> --------------
> disable the patching for the net_sched in 2.6 ..... 
> 
> attached the changed config files and the patches against cvs
> 

I updated the prepare script  and the sources, but left the rest alone.

It looks like there are quite some changes to the kernel config, which 
we carefully have to add.

Heiko

Re: [Devil-linux-develop] LFTP

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

> > If we include lftp in the lfssystem (if it's not already), then the docs
> > should be modified telling people how to make the chroot env network
> > (creating /etc/resolv.conf and ... anything else?).
> 
> Just update the docs. ;-)

I should download the software and learn how to do that sometime.

But since lftp isn't included in the lfssystem, there is no need, 
and I can procrastinate a little while longer ...  ;->

 - BS

Re: [Devil-linux-develop] ipsec-tools 0.3.1 is available

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

Oliver Jehle wrote:
> please replace on the ftp-site
> 
> http://sourceforge.net/projects/ipsec-tools/

DONE

Heiko

Re: [Devil-linux-develop] LFTP

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

Bruce Smith wrote:
>>>>So we don't even need the lftp installed in the system. 
>>>
>>>Isn't that a chicken/egg problem?
>>>
>>>You need lftp to run update_src (which requires lftp) to get lftp ...
>>
>>If the lftp is already available in the chroot which you downloaded from 
>>our ftp-server you would just do the chroot and then run update_src. So no 
>>need for lftp to be installed in the system.
> 
> 
> OK, I misunderstood what you meant.  I thought you were talking about
> not needing lftp in the chroot (instead of the parent system).
> 
> 
>>After installing a new lfssystem I usually install lftp in there so I don't 
>>really need anything else than chroot and cvs and an editor from my base 
>>system.
> 
> 
> Is lftp included in the lfssystem tarball?  (I never looked)

Nope.

>>>>And btw the lftp build script could also always 
>>>>update the lftp of the chroot.
>>>
>>>I don't know why not.
>>>
>>>Of course, if the only reason we need lftp in the chroot is to run
>>>update_src, and it works now with the old version, maybe it'd be best 
>>>to leave well enough alone in case a newer version breaks update_src
>>>someday (parameter changes or something)?
>>
>>At least we should then update the lftp in the chroot with every new lfssystem.
> 
> 
> OK with me.
> 
> If we include lftp in the lfssystem (if it's not already), then the docs
> should be modified telling people how to make the chroot env network
> (creating /etc/resolv.conf and ... anything else?).

Just update the docs. ;-)

Heiko

Re: [Devil-linux-develop] LFTP

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

Bruce Smith wrote on 03.05.2004 21:59 MET:

>>After installing a new lfssystem I usually install lftp in there so I don't 
>>really need anything else than chroot and cvs and an editor from my base 
>>system.
> 
> 
> Is lftp included in the lfssystem tarball?  (I never looked)

I guess not. But my memory might be just bad ;-)


>>>Of course, if the only reason we need lftp in the chroot is to run
>>>update_src, and it works now with the old version, maybe it'd be best 
>>>to leave well enough alone in case a newer version breaks update_src
>>>someday (parameter changes or something)?
>>
>>At least we should then update the lftp in the chroot with every new lfssystem.
> 
> OK with me.
> 
> If we include lftp in the lfssystem (if it's not already), then the docs
> should be modified telling people how to make the chroot env network
> (creating /etc/resolv.conf and ... anything else?).

Copying /etc/resolv.conf and /etc/hosts to the chroot should probably do.


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

Re: [Devil-linux-develop] LFTP

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

> >>So we don't even need the lftp installed in the system. 
> > 
> > Isn't that a chicken/egg problem?
> > 
> > You need lftp to run update_src (which requires lftp) to get lftp ...
> 
> If the lftp is already available in the chroot which you downloaded from 
> our ftp-server you would just do the chroot and then run update_src. So no 
> need for lftp to be installed in the system.

OK, I misunderstood what you meant.  I thought you were talking about
not needing lftp in the chroot (instead of the parent system).

> After installing a new lfssystem I usually install lftp in there so I don't 
> really need anything else than chroot and cvs and an editor from my base 
> system.

Is lftp included in the lfssystem tarball?  (I never looked)

> >>And btw the lftp build script could also always 
> >>update the lftp of the chroot.
> > 
> > I don't know why not.
> > 
> > Of course, if the only reason we need lftp in the chroot is to run
> > update_src, and it works now with the old version, maybe it'd be best 
> > to leave well enough alone in case a newer version breaks update_src
> > someday (parameter changes or something)?
> 
> At least we should then update the lftp in the chroot with every new lfssystem.

OK with me.

If we include lftp in the lfssystem (if it's not already), then the docs
should be modified telling people how to make the chroot env network
(creating /etc/resolv.conf and ... anything else?).

 - BS

Re: [Devil-linux-develop] LFTP

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

Bruce Smith wrote on 03.05.2004 21:17 MET:

>>What if we installed lftp in the chroot? 
> 
> Then the chroot would have a newer version?  :-)
> 
> 
>>So we don't even need the lftp installed in the system. 
> 
> 
> Isn't that a chicken/egg problem?
> 
> You need lftp to run update_src (which requires lftp) to get lftp ...

If the lftp is already available in the chroot which you downloaded from 
our ftp-server you would just do the chroot and then run update_src. So no 
need for lftp to be installed in the system.

After installing a new lfssystem I usually install lftp in there so I don't 
really need anything else than chroot and cvs and an editor from my base 
system.

>>And btw the lftp build script could also always 
>>update the lftp of the chroot.
> 
> I don't know why not.
> 
> Of course, if the only reason we need lftp in the chroot is to run
> update_src, and it works now with the old version, maybe it'd be best 
> to leave well enough alone in case a newer version breaks update_src
> someday (parameter changes or something)?

At least we should then update the lftp in the chroot with every new lfssystem.

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

Re: [Devil-linux-develop] LFTP

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

> What if we installed lftp in the chroot? 

Then the chroot would have a newer version?  :-)

> So we don't even need the lftp installed in the system. 

Isn't that a chicken/egg problem?

You need lftp to run update_src (which requires lftp) to get lftp ...

> And btw the lftp build script could also always 
> update the lftp of the chroot.

I don't know why not.

Of course, if the only reason we need lftp in the chroot is to run
update_src, and it works now with the old version, maybe it'd be best 
to leave well enough alone in case a newer version breaks update_src
someday (parameter changes or something)?

 - BS

Re: [Devil-linux-develop] LFTP

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

Bruce Smith wrote on 30.04.2004 21:35 MET:

>>>Someone point out to me privately that the lftp tarball in:
>>>ftp://ftp.devil-linux.org/pub/devel/sources/tools/
>>>is older than the one we compile in our src directory.
>>>And our docs reference that directory for needed tools:
>>>http://www.devil-linux.org/newdoc/ch03s01.html#d0e1068
>>>I'd be nice if we could just link it so we don't need 2 copies.
>>>Or change the docs to point to the latest lftp in our source
>>>and get rid for the tools directory entirely.
>>
>>It doesn't really matter. The lftp in the tools directory is in the case
>>your OS doesn't have it already.
>>We could just update it from time to time or write in our docs the URL of
>>the lfp homepage.
> 
> 
> I think we should get rid of the tools directory and changes the docs to
> point to the LFTP home page.  It'd be less confusing IMO.  (and I'd get
> fewer complaints :)
> 
> 
>>>Also...
>>>Checking the lftp homepage http://lftp.yar.ru/ the current version
>>>(3.0.3) is newer than any of our versions (2.6.12).  Is there any
>>>reason we shouldn't move to version 3.x.x?
>>
>>Somebody has to update  & test it, that's all.
>>You just volunteered. ;-)
> 
> 
> Oops.  :-)

What if we installed lftp in the chroot? So we don't even need the lftp 
installed in the system. And btw the lftp build script could also always 
update the lftp of the chroot.

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

Re: [Devil-linux-develop] LFTP

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

> > >Checking the lftp homepage http://lftp.yar.ru/ the current version
> > >(3.0.3) is newer than any of our versions (2.6.12).  Is there any
> > >reason we shouldn't move to version 3.x.x?
> >
> > Somebody has to update  & test it, that's all.
> > You just volunteered. ;-)
> 
> Oops.  :-)

Done.

 - BS

Re: [Devil-linux-develop] Shorewall update to V2

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

> Attached is a minor patch to update Shorewall firewall to V2.0.1
> 
> Please also download shorewall 2.0.1 from one of the listed sites in
> http://www.shorewall.net/download.htm

All done.

> and yes, I have tested it with the latest CVS.

Good, because I haven't (yet).  :-)

 - BS

Re: [Devil-linux-develop] Missing man pages?

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

> > Maybe we shouldn't be running copy_docs at all in these scripts?
> 
> Actually that would be the right fix.

Fixed.

 - BS