devil-linux-discuss — General Mailing List for all discussions

[Devil-Linux-discuss] fwbuilder and devil-linux. How to import the rules set in fwbuilder

[Andreas Z. <and...@we...>]

Hi devil-linux crew and users,

how can I import the firewall rules in fwbuilder ? Is there a howto/manual available ?
How can I tell Firewall Builder to read and write the rules directly onto the floppy ?

I tried the "import policy" feature and "discovery druid" but with no success.


Thanks in advance,
Andreas
____________________________________________________________________
Ihre Messenger, Communities und E-Mails jetzt in einem Programm!
WEB.DE MultiMessenger http://www.produkte.web.de/messenger/?did=3071

Re: [Devil-Linux-discuss] Adding KVM with support tools to DL?

[Kari M. <kar...@tr...>]

below..

_____ Alkuperäinen viesti _____
Aihe:	Re: [Devil-Linux-discuss] Adding KVM with support tools to DL?
Tekijä:	"Bruce Smith" <bw...@re...>
Päivämäärä:		25. heinäkuuta 2008 17:29:00

> Yes.  qemu would only be included in the DL "server" version.
>
>        Sounds very good....
> There is also a requirement for a tool to create either tun or tap for the VM. OpenVPN is ok for that, and we have it already. Another option is dedicated tool "tunctl" or "tunctrl" from Redhat, I think.

Since I've never used qemu, if I were to try and add it, I have no
idea where to start.  Can you provide a list of packages that need to
be added (complete with links to tarballs), and what ever else needs
to be changed (kernel parameters, etc.)?

Then I would probably need some kind of getting-started guide on how
to test it.  Or maybe some way to try it on my Ubuntu 8.04.1 desktop.

It's much easier adding stuff that I've used before!  :-)

	Most certainly!  I googled "ubutntu 8.04 kvm tutorial"...

http://tombuntu.com/index.php/2008/04/14/virtualization-with-virt-manager-and-kvm-in-ubuntu-804/
..which contains as extra the graphical VM manager. Skip that.

https://help.ubuntu.com/community/KVM
...Ubuntu 8.04 Jeos edition etc., command line instructions.

wiki.centos.org/HowTos/KVM
CentOS, I know, but this has nice brief intro on the networking part of KVM.
It is also consice and well written. Recommended.
And it lists the odd parts required, which is not many.
Networking is the thing most different between physical machines and KVM/Qemu/VirtualBox VMs.

http://kvm.qumranet.com/kvmwiki
Official home.

http://kvm.qumranet.com/kvmwiki/HOWTO
...KVM VM management scripts etc. etc.

http://kvm.qumranet.com/kvmwiki/Documents

http://kvm.qumranet.com/kvmwiki/Downloads
...starting point for downloads.

http://kvm.qumranet.com/kvmwiki/HOWTO1
...this is good. Setting up KVM to run on your machine.
Prerequisites etc.

Hope this helps.

//Kari


>>>       When can we expect i686 (non-GRSecurity) editions of 1.3.x?
>
> Already on the FTP site.  All of the 1.3 releases I've uploaded (with
> the "-bs" suffix), are compiled without grsec.
>
>        I didn't realise it was -bs, the difference. It used to be i586 (GRSec) vs. i686 (no GRSec).

Since I have a very strong dislike for grsec, you can pretty much be
assured that anything I compile is without grsec.

>        11-Jul test is very good, thanks. Mailgw (clamav, sagator, spamassassin), firewall, ftp server, dns server. All upgraded ok.
>
>        There was one minor hassle, tough.
>
>        On a system without floppy drive, no HD, etc stored on USB key, DL on CD, upgrade was ok, but save-config did not work. (mount command in the script complained it couldn't mount the USB key as it was already mounted, even it was not.) I had to copy manually the etc-mods.tar.bz2 onto /dev/sda1. Reboot and everything, including save-config worked ok since.  I'll upgrade another similar system next week and report if it has same symptoms.

I haven't seen that one.  Please post more details if it happens again.

	I will.


I'm currently compiling a new 1.3 now with all the updates Serge
committed yesterday.  Hopefully it'll be on the FTP server later
today.

	Thanks. Especially the mailgateway DLs like to be updates often (clamav, spamassassin, but also sagator).


 - BS

[Devil-Linux-discuss] Devil-Linux 1.2.15 released!

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

Hi everyone,

it took a while but Devil-Linux 1.2.15 is finally available !
Get it from the usual download locations.

-- 

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


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

Re: [Devil-Linux-discuss] Adding KVM with support tools to DL?

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

> Yes.  qemu would only be included in the DL "server" version.
>
>        Sounds very good....
> There is also a requirement for a tool to create either tun or tap for the VM. OpenVPN is ok for that, and we have it already. Another option is dedicated tool "tunctl" or "tunctrl" from Redhat, I think.

Since I've never used qemu, if I were to try and add it, I have no
idea where to start.  Can you provide a list of packages that need to
be added (complete with links to tarballs), and what ever else needs
to be changed (kernel parameters, etc.)?

Then I would probably need some kind of getting-started guide on how
to test it.  Or maybe some way to try it on my Ubuntu 8.04.1 desktop.

It's much easier adding stuff that I've used before!  :-)

>>>       When can we expect i686 (non-GRSecurity) editions of 1.3.x?
>
> Already on the FTP site.  All of the 1.3 releases I've uploaded (with
> the "-bs" suffix), are compiled without grsec.
>
>        I didn't realise it was -bs, the difference. It used to be i586 (GRSec) vs. i686 (no GRSec).

Since I have a very strong dislike for grsec, you can pretty much be
assured that anything I compile is without grsec.

>        11-Jul test is very good, thanks. Mailgw (clamav, sagator, spamassassin), firewall, ftp server, dns server. All upgraded ok.
>
>        There was one minor hassle, tough.
>
>        On a system without floppy drive, no HD, etc stored on USB key, DL on CD, upgrade was ok, but save-config did not work. (mount command in the script complained it couldn't mount the USB key as it was already mounted, even it was not.) I had to copy manually the etc-mods.tar.bz2 onto /dev/sda1. Reboot and everything, including save-config worked ok since.  I'll upgrade another similar system next week and report if it has same symptoms.

I haven't seen that one.  Please post more details if it happens again.

I'm currently compiling a new 1.3 now with all the updates Serge
committed yesterday.  Hopefully it'll be on the FTP server later
today.

 - BS

Re: [Devil-Linux-discuss] Fixed IP to one internal network pc

[Moray M. <mmc...@ox...>]

On devil-linux (and most linux systems) this is done through
/etc/dhcpd.conf - do man dhcpd.conf at the command line or actually more
easily googling 
 
dhcpd.conf "static IP" MAC address
 
But I think you will find an example line in /etc/dhcpd.conf already -
look for  a clause beginning
 
host x {
    hardware ethernet ...
}
 
in your case it will be something like
 
host a {
    hardware ethernet 00:0D:71:05:CE:46
    fixed-address 192.168.2.10
}
 
Yours,
Moray

--------------------------------------
Moray McConnachie
Head of Information Services
Oxford Analytica

+44 1865 261 600 http://www.oxan.com <http://www.oxan.com/>  

 


________________________________

	From: dev...@li...
[mailto:dev...@li...] On Behalf Of
Eddy & Lieve
	Sent: 25 July 2008 09:43
	To: dev...@li...
	Subject: [Devil-Linux-discuss] Fixed IP to one internal network
pc
	
	

	Hi again,

	 

	While migrating from FloppyFW to Devil-Linux, following question
comes to mind:

	Is it possible to configure static IP mapping for the DHCP
server ?

	DHCP range is 192.168.2.30 - 192.168.2.50

	I would like one PC to have 192.168.2.10

	(I would like to send syslogging to this PC, but when it gets a
different IP...)

	 

	On FloppyFW this was done with a file called ethers, looking
like this:

	00:0D:71:05:CE:46 192.168.2.10

	 

	Many thanks,

	Eddy

Re: [Devil-Linux-discuss] Fixed IP to one internal network pc

[Jacob S. <dev...@js...>]

Hi Eddy,

 

You should check out /etc/dhcpd.conf

 

Think it contains examples something like

 

Host mycomputer [

Hardware Ethernet 00:0D:71:05:CE:46;

Fixed-address 192.168.2.10;

}

 

Kind regards

Jacob

 

Från: dev...@li...
[mailto:dev...@li...] För Eddy & Lieve
Skickat: den 25 juli 2008 10:43
Till: dev...@li...
Ämne: [Devil-Linux-discuss] Fixed IP to one internal network pc

 

Hi again,

 

While migrating from FloppyFW to Devil-Linux, following question comes to
mind:

Is it possible to configure static IP mapping for the DHCP server ?

DHCP range is 192.168.2.30 – 192.168.2.50

I would like one PC to have 192.168.2.10

(I would like to send syslogging to this PC, but when it gets a different
IP…)

 

On FloppyFW this was done with a file called ethers, looking like this:

00:0D:71:05:CE:46 192.168.2.10

 

Many thanks,

Eddy

[Devil-Linux-discuss] Fixed IP to one internal network pc

[Eddy & L. <e.m...@te...>]

Hi again,

 

While migrating from FloppyFW to Devil-Linux, following question comes to
mind:

Is it possible to configure static IP mapping for the DHCP server ?

DHCP range is 192.168.2.30 - 192.168.2.50

I would like one PC to have 192.168.2.10

(I would like to send syslogging to this PC, but when it gets a different
IP.)

 

On FloppyFW this was done with a file called ethers, looking like this:

00:0D:71:05:CE:46 192.168.2.10

 

Many thanks,

Eddy

Re: [Devil-Linux-discuss] Adding KVM with support tools to DL?

[Kari M. <kar...@tr...>]

_____ Alkuperäinen viesti _____
Aihe:	Re: [Devil-Linux-discuss] Adding KVM with support tools to DL?
Tekijä:	"Bruce Smith" <bw...@re...>
Päivämäärä:		24. heinäkuuta 2008 22:25:56

>>       Then DL would be comparable (in some aspects) to VMware ESX 3i
>> installable, or VMware ESX 3 classic with service console
>> (RHEL3-based). ....and way ahead of VMware Server (an application).
>
> So there's no X required to run this?

I was wondering about that too.  :-)

	No X.

>> I'm not sure if QEMU is running with GRSecurity enabled (NO BRUCE!, it
>> stays in there...)
>
> We could always have the qemu and grsecurity as exclusive options in
> the build config system. This way you could build a non-grsecurity DL
> version with qemu (or whatever else, like xen, etc) included.

Yes.  qemu would only be included in the DL "server" version.

	Sounds very good....
There is also a requirement for a tool to create either tun or tap for the VM. OpenVPN is ok for that, and we have it already. Another option is dedicated tool "tunctl" or "tunctrl" from Redhat, I think.

>>       When can we expect i686 (non-GRSecurity) editions of 1.3.x?

Already on the FTP site.  All of the 1.3 releases I've uploaded (with
the "-bs" suffix), are compiled without grsec.  

	I didn't realise it was -bs, the difference. It used to be i586 (GRSec) vs. i686 (no GRSec).


The only difference
between those and the official server release is these are compiled as
i586 instead of i686 to allow more people to test them.  Is an i586
compile okay for qemu?

	I see no restrictions for that.


>> I feel more comfortable running those as servers.  Dunno why..

Same here!

> You can always compile your own.
> Not sure when Bruce is planning to compile the next version, but there
> should be an older one on the FTP server in the testing directory.

The latest 1.3 test release on the server now (about 10 days old) is
fairly current.  There have been a couple updates since then, so I was
planning on compiling a new one tonight to upgrade some of my own
servers tomorrow.

	11-Jul test is very good, thanks. Mailgw (clamav, sagator, spamassassin), firewall, ftp server, dns server. All upgraded ok.

	There was one minor hassle, tough.

	On a system without floppy drive, no HD, etc stored on USB key, DL on CD, upgrade was ok, but save-config did not work. (mount command in the script complained it couldn't mount the USB key as it was already mounted, even it was not.) I had to copy manually the etc-mods.tar.bz2 onto /dev/sda1. Reboot and everything, including save-config worked ok since.  I'll upgrade another similar system next week and report if it has same symptoms.

 - BS

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Devil-linux-discuss mailing list
Dev...@li...
https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss

Re: [Devil-Linux-discuss] Adding KVM with support tools to DL?

[Kari M. <kar...@tr...>]

_____ Alkuperäinen viesti _____
Aihe:	Re: [Devil-Linux-discuss] Adding KVM with support tools to DL?
Tekijä:	"Heiko Zuerker" <he...@zu...>
Päivämäärä:		24. heinäkuuta 2008 23:02:13

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

>>>       Then DL would be comparable (in some aspects) to VMware ESX 3i
>>> installable, or VMware ESX 3 classic with service console
>>> (RHEL3-based). ....and way ahead of VMware Server (an application).
>>
>> So there's no X required to run this?
>
> I was wondering about that too.  :-)

I did a quick search on the web and it seems it works:
<Quote>
You can run qemu headless, with a virtual framebuffer. Makes for a virtual
machine you connect to via VNC to view.
</Quote>

	Yes, no X nor any other graphics requirement.
We have been experimenting with Ubuntu 8.04 JeOS, which has KVM, qemu, etc. and no X. Works ok.... but not like the Devil ;-)

[........]

-- 

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


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



-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Devil-linux-discuss mailing list
Dev...@li...
https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss

Re: [Devil-Linux-discuss] Adding KVM with support tools to DL?

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

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

>>>       Then DL would be comparable (in some aspects) to VMware ESX 3i
>>> installable, or VMware ESX 3 classic with service console
>>> (RHEL3-based). ....and way ahead of VMware Server (an application).
>>
>> So there's no X required to run this?
>
> I was wondering about that too.  :-)

I did a quick search on the web and it seems it works:
<Quote>
You can run qemu headless, with a virtual framebuffer. Makes for a virtual
machine you connect to via VNC to view.
</Quote>

[........]

-- 

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


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

Re: [Devil-Linux-discuss] Adding KVM with support tools to DL?

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

>>       Then DL would be comparable (in some aspects) to VMware ESX 3i
>> installable, or VMware ESX 3 classic with service console
>> (RHEL3-based). ....and way ahead of VMware Server (an application).
>
> So there's no X required to run this?

I was wondering about that too.  :-)

>> I'm not sure if QEMU is running with GRSecurity enabled (NO BRUCE!, it
>> stays in there...)
>
> We could always have the qemu and grsecurity as exclusive options in
> the build config system. This way you could build a non-grsecurity DL
> version with qemu (or whatever else, like xen, etc) included.

Yes.  qemu would only be included in the DL "server" version.

>>       When can we expect i686 (non-GRSecurity) editions of 1.3.x?

Already on the FTP site.  All of the 1.3 releases I've uploaded (with
the "-bs" suffix), are compiled without grsec.  The only difference
between those and the official server release is these are compiled as
i586 instead of i686 to allow more people to test them.  Is an i586
compile okay for qemu?

>> I feel more comfortable running those as servers.  Dunno why..

Same here!

> You can always compile your own.
> Not sure when Bruce is planning to compile the next version, but there
> should be an older one on the FTP server in the testing directory.

The latest 1.3 test release on the server now (about 10 days old) is
fairly current.  There have been a couple updates since then, so I was
planning on compiling a new one tonight to upgrade some of my own
servers tomorrow.

 - BS

Re: [Devil-Linux-discuss] Adding KVM with support tools to DL?

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

Quoting Kari Mattsson <kar...@tr...>:

>
> Quoting Kari Mattsson <kar...@tr...>:
>
>>
>> Just an idea.
>>
>> Now that Cisco is using/embedding KVM in their carrier class routers,
>> <http://www.informationweek.com/blog/main/archives/2008/03/does_ciscos_swi.html>,
>> don't you think it would be appropriate to include that in DL, too ;-)
>>
>> More info on KVM here: http://kvm.qumranet.com/kvmwiki
>
> 	I liked and second Bruce's comment on reusing acronyms.
> This time KVM is not only reused, but also overloaded. That I think  
> is rather annoying.
>
>
>
>> I'd be nice to have DL VM in DL in the future. Or better, different DL
>> roles in different VMs: DNS, OpenVPN, IPSec, firewall, DHCP, FTP, etc.
>>
>> Unfortunately I'm more on the architecture, design, and admin side, not
>> programming. And thus can not help there too much :-(
>>
>> **
>>
>> As KVM is included in kernel 2.6.20+, we should already have much in place.
>>
>> QEMU is the biggest missing part.
>
> I do something like that already with the free vmware server and
> multiple DL instances. But yes, you're right, all the Kernel stuff is
> already included.
>
>
> 	We are running lots of DLs for different purposes on various  
> places. Mainly on VMware ESX Server, but also on bare metal.  What  
> I'm silently targeting here, Heiko and Bruce, is to be able to use  
> DL as an ultra light basis to run several, even non-DL VMs. Zimbra  
> Collaboration Server, or something on those lines comes to my mind.  
> Or on older gear, maybe something else.
>
> 	Then DL would be comparable (in some aspects) to VMware ESX 3i  
> installable, or VMware ESX 3 classic with service console  
> (RHEL3-based). ....and way ahead of VMware Server (an application).

So there's no X required to run this?

> I'm not sure if QEMU is running with GRSecurity enabled (NO BRUCE!, it
> stays in there...)

We could always have the qemu and grsecurity as exclusive options in  
the build config system. This way you could build a non-grsecurity DL  
version with qemu (or whatever else, like xen, etc) included.

> 	When can we expect i686 (non-GRSecurity) editions of 1.3.x?
> I feel more comfortable running those as servers.  Dunno why..

You can always compile your own.
Not sure when Bruce is planning to compile the next version, but there  
should be an older one on the FTP server in the testing directory.

> Additionally I don't have time, so somebody else would have to take
> this project.
>
> 	There is no rush. KVM is getting better very fast, the management etc.
> It was just an idea...

Yeah but if you wait too long, somebody else will run with the same idea. ;-)

-- 

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


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

Re: [Devil-Linux-discuss] Adding KVM with support tools to DL?

[Kari M. <kar...@tr...>]

Quoting Kari Mattsson <kar...@tr...>:

>
> Just an idea.
>
> Now that Cisco is using/embedding KVM in their carrier class routers,
> <http://www.informationweek.com/blog/main/archives/2008/03/does_ciscos_swi.html>,
> don't you think it would be appropriate to include that in DL, too ;-)
>
> More info on KVM here: http://kvm.qumranet.com/kvmwiki

	I liked and second Bruce's comment on reusing acronyms.
This time KVM is not only reused, but also overloaded. That I think is rather annoying.



> I'd be nice to have DL VM in DL in the future. Or better, different DL
> roles in different VMs: DNS, OpenVPN, IPSec, firewall, DHCP, FTP, etc.
>
> Unfortunately I'm more on the architecture, design, and admin side, not
> programming. And thus can not help there too much :-(
>
> **
>
> As KVM is included in kernel 2.6.20+, we should already have much in place.
>
> QEMU is the biggest missing part.

I do something like that already with the free vmware server and  
multiple DL instances. But yes, you're right, all the Kernel stuff is  
already included.


	We are running lots of DLs for different purposes on various places. Mainly on VMware ESX Server, but also on bare metal.  What I'm silently targeting here, Heiko and Bruce, is to be able to use DL as an ultra light basis to run several, even non-DL VMs. Zimbra Collaboration Server, or something on those lines comes to my mind. Or on older gear, maybe something else.

	Then DL would be comparable (in some aspects) to VMware ESX 3i installable, or VMware ESX 3 classic with service console (RHEL3-based). ....and way ahead of VMware Server (an application).


I'm not sure if QEMU is running with GRSecurity enabled (NO BRUCE!, it  
stays in there...)


	When can we expect i686 (non-GRSecurity) editions of 1.3.x?
I feel more comfortable running those as servers.  Dunno why..



Additionally I don't have time, so somebody else would have to take  
this project.

	There is no rush. KVM is getting better very fast, the management etc.
It was just an idea...

-- 

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


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


-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Devil-linux-discuss mailing list
Dev...@li...
https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss

Re: [Devil-Linux-discuss] Adding KVM with support tools to DL?

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

Quoting Kari Mattsson <kar...@tr...>:

>
> Just an idea.
>
> Now that Cisco is using/embedding KVM in their carrier class routers,
> <http://www.informationweek.com/blog/main/archives/2008/03/does_ciscos_swi.html>,
> don't you think it would be appropriate to include that in DL, too ;-)
>
> More info on KVM here: http://kvm.qumranet.com/kvmwiki
>
> I'd be nice to have DL VM in DL in the future. Or better, different DL
> roles in different VMs: DNS, OpenVPN, IPSec, firewall, DHCP, FTP, etc.
>
> Unfortunately I'm more on the architecture, design, and admin side, not
> programming. And thus can not help there too much :-(
>
> **
>
> As KVM is included in kernel 2.6.20+, we should already have much in place.
>
> QEMU is the biggest missing part.

I do something like that already with the free vmware server and  
multiple DL instances. But yes, you're right, all the Kernel stuff is  
already included.
I'm not sure if QEMU is running with GRSecurity enabled (NO BRUCE!, it  
stays in there...)
Additionally I don't have time, so somebody else would have to take  
this project.

-- 

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


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

Re: [Devil-Linux-discuss] DL 1.2.15

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

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

>> I downloaded 1.2.15 and it works like a charm; no more errors like "Unable
>> to handle kernel paging request at virtual address C4000000" at boot.
>>
>> But… is this a release…?
>>
>> It's not mentioned on the DL home page and there is no MD5 checksum on the
>> download page…?
>
> Yes, it's a real release.   It's just very new.
>
> Heiko has been waiting for the download servers to all propagate with
> the download before he officially announces it.
>
> It should be propagated by now, so expect to see the web site changed
> and official announcement soon.  :-)
>
> BTW, it also fixed the DNS server security problem that has been
> getting so much press lately.

I'm planning to announce it tomorrow, since I don't have time to prep  
everything today.

-- 

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


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

Re: [Devil-Linux-discuss] DL 1.2.15

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

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

>> I downloaded 1.2.15 and it works like a charm; no more errors like "Unable
>> to handle kernel paging request at virtual address C4000000" at boot.
>>
>> But… is this a release…?
>>
>> It's not mentioned on the DL home page and there is no MD5 checksum on the
>> download page…?
>
> Yes, it's a real release.   It's just very new.
>
> Heiko has been waiting for the download servers to all propagate with
> the download before he officially announces it.
>
> It should be propagated by now, so expect to see the web site changed
> and official announcement soon.  :-)
>
> BTW, it also fixed the DNS server security problem that has been
> getting so much press lately.

I'm planning to announce it tomorrow, since I don't have time to prep  
everything today.
Of course if Bruce wants to do it today, I won't complain. ;-)


-- 

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


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

Re: [Devil-Linux-discuss] DL 1.2.15

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

> I downloaded 1.2.15 and it works like a charm; no more errors like "Unable
> to handle kernel paging request at virtual address C4000000" at boot.
>
> But… is this a release…?
>
> It's not mentioned on the DL home page and there is no MD5 checksum on the
> download page…?

Yes, it's a real release.   It's just very new.

Heiko has been waiting for the download servers to all propagate with
the download before he officially announces it.

It should be propagated by now, so expect to see the web site changed
and official announcement soon.  :-)

BTW, it also fixed the DNS server security problem that has been
getting so much press lately.

 - BS

Re: [Devil-Linux-discuss] Errors with LVM on SATA HDD 80Gb distr: devil-linux-1.3.6-2008-07-11-i586 (Bruce Smith)

[Anton P. <pro...@ug...>]

>> /dev/devil-linux/opt:
>> The superblock could not be read or does not describe a correct ext2
>> filesystem.  If the device is valid and it really contains an ext2
>> filesystem (and not swap or ufs or something else), then the superblock
>> is corrupt, and you might try running e2fsck with an alternate superblock:
>>    e2fsck -b 8193 <device>

>It looks like you forgot to format (mkfs) the LVM filesystems.

It's fantastic! You are right!!! Thanks a lot!

[Devil-Linux-discuss] DL 1.2.15

[Eddy & L. <e.m...@te...>]

Hello,

 

I downloaded 1.2.15 and it works like a charm; no more errors like "Unable
to handle kernel paging request at virtual address C4000000" at boot.

But. is this a release.?

It's not mentioned on the DL home page and there is no MD5 checksum on the
download page.?

 

Many thanks,

Eddy

Re: [Devil-Linux-discuss] Errors with LVM on SATA HDD 80Gb distr: devil-linux-1.3.6-2008-07-11-i586

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

> /dev/devil-linux/opt:
> The superblock could not be read or does not describe a correct ext2
> filesystem.  If the device is valid and it really contains an ext2
> filesystem (and not swap or ufs or something else), then the superblock
> is corrupt, and you might try running e2fsck with an alternate superblock:
>    e2fsck -b 8193 <device>

It looks like you forgot to format (mkfs) the LVM filesystems.

if not, what filesystem types did you use?

> What can I do with it???

mkfs -t ...  /dev/devil-linux/opt # ?  :-)

> I need LVM for using SQUID cache...

No you don't.  You can squid on standard partitions in fstab.
(although you have to mkfs on those too)  ;-)

 - BS

[Devil-Linux-discuss] Errors with LVM on SATA HDD 80Gb distr: devil-linux-1.3.6-2008-07-11-i586

[Anton P. <pro...@ug...>]

Hi everybody!

I need your help and advice.
I first time try use SATA HDD with DL. At first I tried 
devil-linux-1.2.14-i586-SMP but it ignored SATA HDD, after that I try 
devil-linux-1.3.6-2008-07-11-i586. It found HDD, but I cannot use LVM on 
it...


Linux version 2.6.25.6-grsec (root@pc-1) (gcc version 4.1.2) #1 SMP

Initialising SATA HDD 80Gb:

ata_piix 0000:00:1f.2: version 2.12
ACPI: PCI Interrupt 0000:00:1f.2[A] -> GSI 18 (level, low) -> IRQ 18
ata_piix 0000:00:1f.2: MAP [ P0 -- P1 -- ]
PCI: Setting latency timer of device 0000:00:1f.2 to 64
scsi0 : ata_piix
scsi1 : ata_piix
ata1: SATA max UDMA/133 cmd 0xe800 ctl 0xe400 bmdma 0xd800 irq 18
ata2: SATA max UDMA/133 cmd 0xe000 ctl 0xdc00 bmdma 0xd808 irq 18
ata1.00: ATA-6: ST380817AS, 3.42, max UDMA/133
ata1.00: 156301488 sectors, multi 16: LBA48 NCQ (not used)
ata1.00: configured for UDMA/133
scsi 0:0:0:0: Direct-Access     ATA      ST380817AS       3.42 PQ: 0 ANSI: 5
sd 0:0:0:0: [sda] 156301488 512-byte hardware sectors (80026 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support 
DPO
 or FUA
sd 0:0:0:0: [sda] 156301488 512-byte hardware sectors (80026 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support 
DPO
 or FUA
 sda: sda1
sd 0:0:0:0: [sda] Attached SCSI disk
sd 0:0:0:0: Attached scsi generic sg0 type 0

Starting VLM (devil-linux) with errors but swap is adding witout error:
Jul 23 19:46:33 src@inetproxy kernel: Adding 131064k swap on 
/dev/mapper/devil--
linux-swap.  Priority:-1 extents:1 across:131064k

Starting LVM
  volume group "devil-linux"
    logical volume "/dev/devil-linux/log"
    logical volume "/dev/devil-linux/spool"
    logical volume "/dev/devil-linux/squid"
    logical volume "/dev/devil-linux/data"
    logical volume "/dev/devil-linux/opt"
    logical volume "/dev/devil-linux/home"
    logical volume "/dev/devil-linux/swap"

Devil-Linux Harddisk found, activating...
Activating swap 
[FAILED]
fsck.ext2: Bad magic number in super-block while trying to open 
/dev/devil-linux/opt
/dev/devil-linux/opt:
The superblock could not be read or does not describe a correct ext2
filesystem.  If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>

Mounting /opt mount: you must specify the filesystem type
                                                                     [FAILED]
fsck.ext2: Bad magic number in super-block while trying to open 
/dev/devil-linux/home
/dev/devil-linux/home:
The superblock could not be read or does not describe a correct ext2
filesystem.  If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>

Mounting /home mount: you must specify the filesystem type
                                                                     [FAILED]
fsck.ext2: Bad magic number in super-block while trying to open 
/dev/devil-linux/log
/dev/devil-linux/log:
The superblock could not be read or does not describe a correct ext2
filesystem.  If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>

Mounting /var/log mount: you must specify the filesystem type
                                                                     [FAILED]
fsck.ext2: Bad magic number in super-block while trying to open 
/dev/devil-linux/squid
/dev/devil-linux/squid:
The superblock could not be read or does not describe a correct ext2
filesystem.  If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>

Mounting /var/squid mount: you must specify the filesystem type
                                                                     [FAILED]
fsck.ext2: Bad magic number in super-block while trying to open 
/dev/devil-linux/data
/dev/devil-linux/data:
The superblock could not be read or does not describe a correct ext2
filesystem.  If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>

Mounting /var/data mount: you must specify the filesystem type
                                                                     [FAILED]
fsck.ext2: Bad magic number in super-block while trying to open 
/dev/devil-linux/spool
/dev/devil-linux/spool:
The superblock could not be read or does not describe a correct ext2
filesystem.  If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>

Mounting /var/spool mount: you must specify the filesystem type
                                                                     [FAILED]

root@inetproxy:/etc/init.d # e2fsck -b 8193 /dev/devil-linux/spool
e2fsck 1.40.8 (13-Mar-2008)
e2fsck: Device or resource busy while trying to open /dev/devil-linux/spool
Filesystem mounted or opened exclusively by another program?


Info about my LVM group and volume:

root@inetproxy:/etc/lvm # lvm pvdisplay
  --- Physical volume ---
  PV Name               /dev/sda1
  VG Name               devil-linux
  PV Size               74.53 GB / not usable 577.00 KB
  Allocatable           yes
  PE Size (KByte)       4096
  Total PE              19079
  Free PE               18695
  Allocated PE          384
  PV UUID               cu1OtB-3OFg-2gTr-k2qW-Y1sJ-YnOS-f3AxGz

root@inetproxy:/etc/lvm # lvm pvscan
  /dev/cdrom: open failed: Read-only file system
  Attempt to close device '/dev/cdrom' which is not open.
  PV /dev/sda1   VG devil-linux   lvm2 [74.53 GB / 73.03 GB free]
  Total: 1 [74.53 GB] / in use: 1 [74.53 GB] / in no VG: 0 [0   ]

root@inetproxy:/etc/lvm # lvm vgdisplay
  --- Volume group ---
  VG Name               devil-linux
  System ID
  Format                lvm2
  Metadata Areas        1
  Metadata Sequence No  8
  VG Access             read/write
  VG Status             resizable
  MAX LV                0
  Cur LV                7
  Open LV               1
  Max PV                0
  Cur PV                1
  Act PV                1
  VG Size               74.53 GB
  PE Size               4.00 MB
  Total PE              19079
  Alloc PE / Size       384 / 1.50 GB
  Free  PE / Size       18695 / 73.03 GB
  VG UUID               Yb93a0-T2c0-Vt0T-ieLi-yOg2-EXJl-VVgc0O

root@inetproxy:/etc/lvm # lvm vgs
  VG          #PV #LV #SN Attr   VSize  VFree
  devil-linux   1   7   0 wz--n- 74.53G 73.03G

root@inetproxy:/etc/lvm # lvm vgscan
  Reading all physical volumes.  This may take a while...
  /dev/cdrom: open failed: Read-only file system
  Attempt to close device '/dev/cdrom' which is not open.
  Found volume group "devil-linux" using metadata type lvm2

root@inetproxy:/etc/lvm # lvm lvdisplay
  --- Logical volume ---
  LV Name                /dev/devil-linux/log
  VG Name                devil-linux
  LV UUID                j0hPbT-WXgT-Sj41-uMkS-3e45-wwhp-HU5e6b
  LV Write Access        read/write
  LV Status              available
  # open                 0
  LV Size                256.00 MB
  Current LE             64
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           253:0

  --- Logical volume ---
  LV Name                /dev/devil-linux/spool
  VG Name                devil-linux
  LV UUID                p8bxft-bT7I-uOoE-r3s4-zV0r-tYaS-72WuNj
  LV Write Access        read/write
  LV Status              available
  # open                 0
  LV Size                256.00 MB
  Current LE             64
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           253:1

  --- Logical volume ---
  LV Name                /dev/devil-linux/squid
  VG Name                devil-linux
  LV UUID                B97rDr-dN49-tnI6-hOzq-vEXg-O3JS-FAvgq9
  LV Write Access        read/write
  LV Status              available
  # open                 0
  LV Size                512.00 MB
  Current LE             128
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           253:2

  --- Logical volume ---
  LV Name                /dev/devil-linux/data
  VG Name                devil-linux
  LV UUID                ZQ0e1s-vDfo-ybG3-TuNB-61tU-8TA8-bFHdoJ
  LV Write Access        read/write
  LV Status              available
  # open                 0
  LV Size                128.00 MB
  Current LE             32
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           253:3

  --- Logical volume ---
  LV Name                /dev/devil-linux/opt
  VG Name                devil-linux
  LV UUID                UFHNAp-kAU5-OB1N-vTi2-pHJD-nhy6-ubqWa1
  LV Write Access        read/write
  LV Status              available
  # open                 0
  LV Size                128.00 MB
  Current LE             32
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           253:4

  --- Logical volume ---
  LV Name                /dev/devil-linux/home
  VG Name                devil-linux
  LV UUID                hn9xdN-H5aV-DRWA-UySc-JqHM-k2ac-shrbGY
  LV Write Access        read/write
  LV Status              available
  # open                 0
  LV Size                128.00 MB
  Current LE             32
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           253:5

  --- Logical volume ---
  LV Name                /dev/devil-linux/swap
  VG Name                devil-linux
  LV UUID                uveONI-KKCg-ezF7-omHU-b80Z-p8px-mgNoZm
  LV Write Access        read/write
  LV Status              available
  # open                 1
  LV Size                128.00 MB
  Current LE             32
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           253:6

root@inetproxy:/etc/lvm # lvm lvmdiskscan
  /dev/ramdisk           [       11.17 MB]
  /dev/devil-linux/log   [      256.00 MB]
  /dev/ram               [       11.17 MB]
  /dev/sda1              [       74.53 GB] LVM physical volume
  /dev/devil-linux/spool [      256.00 MB]
  /dev/ram2              [       11.17 MB]
  /dev/devil-linux/squid [      512.00 MB]
  /dev/ram3              [       11.17 MB]
  /dev/devil-linux/data  [      128.00 MB]
  /dev/ram4              [       11.17 MB]
  /dev/devil-linux/opt   [      128.00 MB]
  /dev/ram5              [       11.17 MB]
  /dev/devil-linux/home  [      128.00 MB]
  /dev/ram6              [       11.17 MB]
  /dev/devil-linux/swap  [      128.00 MB]
  /dev/ram7              [       11.17 MB]
  /dev/ram8              [       11.17 MB]
  /dev/ram9              [       11.17 MB]
  /dev/ram10             [       11.17 MB]
  /dev/ram11             [       11.17 MB]
  /dev/ram12             [       11.17 MB]
  /dev/ram13             [       11.17 MB]
  /dev/ram14             [       11.17 MB]
  /dev/ram15             [       11.17 MB]
  /dev/cdrom             [      277.10 MB]
  10 disks
  14 partitions
  0 LVM physical volume whole disks
  1 LVM physical volume

root@inetproxy:/etc/lvm # lvm lvs
  LV    VG          Attr   LSize   Origin Snap%  Move Log Copy%  Convert
  data  devil-linux -wi-a- 128.00M
  home  devil-linux -wi-a- 128.00M
  log   devil-linux -wi-a- 256.00M
  opt   devil-linux -wi-a- 128.00M
  spool devil-linux -wi-a- 256.00M
  squid devil-linux -wi-a- 512.00M
  swap  devil-linux -wi-ao 128.00M

root@inetproxy:/etc/lvm # lvm lvscan
  ACTIVE            '/dev/devil-linux/log' [256.00 MB] inherit
  ACTIVE            '/dev/devil-linux/spool' [256.00 MB] inherit
  ACTIVE            '/dev/devil-linux/squid' [512.00 MB] inherit
  ACTIVE            '/dev/devil-linux/data' [128.00 MB] inherit
  ACTIVE            '/dev/devil-linux/opt' [128.00 MB] inherit
  ACTIVE            '/dev/devil-linux/home' [128.00 MB] inherit
  ACTIVE            '/dev/devil-linux/swap' [128.00 MB] inherit


What can I do with it???
I need LVM for using SQUID cache...

Thanks for all in advance!!!

Best regards, Anton. 

Re: [Devil-Linux-discuss] Adding KVM with support tools to DL?

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

> Now that Cisco is using/embedding KVM in their carrier class routers,
> <http://www.informationweek.com/blog/main/archives/2008/03/does_ciscos_swi.html>,
> don't you think it would be appropriate to include that in DL, too ;-)
>
> More info on KVM here: http://kvm.qumranet.com/kvmwiki

<side note>
There should be a law against reusing acronyms.

I clicked on the links to find out a software KVM switch could work.  ;-)
( http://en.wikipedia.org/wiki/KVM_Switch ).

 - BS

[Devil-Linux-discuss] Adding KVM with support tools to DL?

[Kari M. <kar...@tr...>]

Just an idea.

Now that Cisco is using/embedding KVM in their carrier class routers, 
<http://www.informationweek.com/blog/main/archives/2008/03/does_ciscos_swi.html>, 
don't you think it would be appropriate to include that in DL, too ;-)

More info on KVM here: http://kvm.qumranet.com/kvmwiki

I'd be nice to have DL VM in DL in the future. Or better, different DL 
roles in different VMs: DNS, OpenVPN, IPSec, firewall, DHCP, FTP, etc.

Unfortunately I'm more on the architecture, design, and admin side, not 
programming. And thus can not help there too much :-(

**

As KVM is included in kernel 2.6.20+, we should already have much in place.

QEMU is the biggest missing part.

//Kari Mattsson

Re: [Devil-Linux-discuss] Serial install of DL 1.3

[Serge L. <fi...@in...>]

Hi Jacob,


Jacob Sandin wrote:
> I was going to try installing 1.3 but I ran into a little problem.
> 
> There is no etc-modd.tar.bz2 to add when building CF.
> 
> And therefore I can not set the security settings for Serial access.

I've tried to improve install-on-usb script in DL 1.3 and make installation with
serial access smoother.

I have no possibility to test the changes and will be very grateful if you check
the modified script. By design, you should get completely configured serial
access after script execution.

Please let me know if something will be unusable or wrong.

Thank you,

--
Serge

Re: [Devil-Linux-discuss] DL 1.2.14 kernel paging request error

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

What version of DL are you running?  The "server" version is compiled
for i686 or higher, so it won't run on the P5-75.  Not sure about a
Celeron.

P.S.  Don't tell anyone, but if you wait another day or two, DL 1.2.15
should be out  (assuming we don't run into any problems) -- which may
or may not help with this problem.

Personally, I'd try the latest DL-1.3 beta off the FTP server.  It has
a 2.6 kernel.  That's what I run on all my production servers.

 - BS


> Until now I used FloppyFW as a firewall.
>
> Because Devil-Linux offers more services, I am trying to get DL 1.2.14
> running, but without succes:
>
>
>
> During boot-process I get following error:
>
> "Unable to handle kernel paging request at virtual address C4000000"
>
>
>
> The funny thing is, I tried on 2 different PC's:
>
> -          Pentium 75 / 133 MHz with 64 Mb RAM
>
> -          Celeron 400 MHz with 64 Mb RAM
>
> Exactly the same message appears on both computers…!