Menu
▾
▴
devil-linux-discuss — General Mailing List for all discussions
You can subscribe to this list here.
| 2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(59) |
Sep
(57) |
Oct
(5) |
Nov
(45) |
Dec
(21) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2002 |
Jan
(13) |
Feb
(22) |
Mar
(14) |
Apr
(7) |
May
(33) |
Jun
(57) |
Jul
(25) |
Aug
(40) |
Sep
(53) |
Oct
(58) |
Nov
(75) |
Dec
(22) |
| 2003 |
Jan
(101) |
Feb
(101) |
Mar
(103) |
Apr
(125) |
May
(85) |
Jun
(57) |
Jul
(62) |
Aug
(42) |
Sep
(76) |
Oct
(214) |
Nov
(290) |
Dec
(274) |
| 2004 |
Jan
(187) |
Feb
(172) |
Mar
(313) |
Apr
(209) |
May
(169) |
Jun
(147) |
Jul
(118) |
Aug
(193) |
Sep
(227) |
Oct
(125) |
Nov
(246) |
Dec
(191) |
| 2005 |
Jan
(244) |
Feb
(175) |
Mar
(165) |
Apr
(130) |
May
(217) |
Jun
(122) |
Jul
(188) |
Aug
(235) |
Sep
(165) |
Oct
(133) |
Nov
(209) |
Dec
(88) |
| 2006 |
Jan
(66) |
Feb
(89) |
Mar
(108) |
Apr
(91) |
May
(29) |
Jun
(45) |
Jul
(64) |
Aug
(42) |
Sep
(44) |
Oct
(81) |
Nov
(64) |
Dec
(9) |
| 2007 |
Jan
(24) |
Feb
(122) |
Mar
(55) |
Apr
(50) |
May
(84) |
Jun
(13) |
Jul
(80) |
Aug
(70) |
Sep
(78) |
Oct
(45) |
Nov
(56) |
Dec
(42) |
| 2008 |
Jan
(65) |
Feb
(3) |
Mar
(51) |
Apr
(151) |
May
(54) |
Jun
(72) |
Jul
(73) |
Aug
(47) |
Sep
(55) |
Oct
(123) |
Nov
(16) |
Dec
(4) |
| 2009 |
Jan
(23) |
Feb
(39) |
Mar
(27) |
Apr
(36) |
May
(35) |
Jun
(51) |
Jul
(11) |
Aug
(14) |
Sep
(40) |
Oct
(67) |
Nov
(38) |
Dec
(13) |
| 2010 |
Jan
(15) |
Feb
(35) |
Mar
(40) |
Apr
(11) |
May
(26) |
Jun
(10) |
Jul
(5) |
Aug
(50) |
Sep
(86) |
Oct
(67) |
Nov
(36) |
Dec
(11) |
| 2011 |
Jan
(50) |
Feb
(6) |
Mar
(13) |
Apr
(13) |
May
(29) |
Jun
(27) |
Jul
(26) |
Aug
(27) |
Sep
(21) |
Oct
(7) |
Nov
(27) |
Dec
(4) |
| 2012 |
Jan
(11) |
Feb
(20) |
Mar
(48) |
Apr
(18) |
May
(8) |
Jun
(19) |
Jul
|
Aug
(15) |
Sep
(3) |
Oct
(4) |
Nov
(5) |
Dec
(1) |
| 2013 |
Jan
(13) |
Feb
(7) |
Mar
(4) |
Apr
(25) |
May
(2) |
Jun
(8) |
Jul
(4) |
Aug
(8) |
Sep
(7) |
Oct
|
Nov
(5) |
Dec
(10) |
| 2014 |
Jan
|
Feb
|
Mar
(6) |
Apr
(20) |
May
(5) |
Jun
|
Jul
(2) |
Aug
|
Sep
(8) |
Oct
(21) |
Nov
(4) |
Dec
(7) |
| 2015 |
Jan
(10) |
Feb
(9) |
Mar
(4) |
Apr
|
May
|
Jun
|
Jul
|
Aug
(5) |
Sep
(11) |
Oct
|
Nov
(17) |
Dec
(32) |
| 2016 |
Jan
(10) |
Feb
(15) |
Mar
(4) |
Apr
(7) |
May
(10) |
Jun
(11) |
Jul
(15) |
Aug
(26) |
Sep
(13) |
Oct
(10) |
Nov
(16) |
Dec
(6) |
| 2017 |
Jan
(9) |
Feb
(3) |
Mar
|
Apr
(2) |
May
(2) |
Jun
|
Jul
|
Aug
(3) |
Sep
(3) |
Oct
(6) |
Nov
(8) |
Dec
|
| 2018 |
Jan
(12) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(4) |
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Heiko Z. <he...@zu...> - 2007-09-10 20:26:12
|
On Mon, September 10, 2007 12:04, Dietmar Rieder wrote: > 2007/8/31, Heiko Zuerker <he...@zu...>: > >> >> On Fri, August 31, 2007 06:23, Dietmar Rieder wrote: >> >>> 2007/8/23, Oliver Niesner <dig...@gm...>: >>> >>> >>>> Hi, Heiko! >>>> >>>> >>>> >>>> No good news from the new testing release - it crashed after the >>>> bootmenu on my PIII 500 intel 440BX board with an "unable to handle >>>> kernel paging request at virtual address d0000000" error and hangs. >>>> My >>>> own iso crashed with the same error - it seems that the new kernel >>>> doesn't like older hardware. On an slightly more modern PC (P4) it >>>> starts like normal. >>> >>> The same happens here. After loading the initrd it crashes on my PIII >>> 1000 (were it should finally run on). >>> On a P4 or on my vmware it works. I build an iso for 486 and one for >>> 686 but it doesn't make a difference... >>> >> >> Can you swap out the memory on your PIII for a test? >> > > Ok, I was able to get some spare memory modules. I tested it with two > different ones, but DL doesn't boot up. DL 1.2.13 works fine on this > machine. > > But I found out that on another P III (866) the new release works. > Unfortunately I can't use the second machine because it is in use for > another VPN gateway. That's weird. It may be related to another patch, like the grsecurity. Can you try building a server version and see if it behaves better? It is really hard to track these issues down. -- Regards Heiko Zuerker http://www.devil-linux.org |
|
From: Heiko Z. <he...@zu...> - 2007-09-10 20:24:10
|
On Mon, September 10, 2007 12:14, Dietmar Rieder wrote: > 2007/9/3, Dietmar Rieder <die...@gm...>: > >> 2007/8/28, Dietmar Rieder <die...@gm...>: >> >>> Am 28.08.07 schrieb "Rudner, Björn" <br...@ba...>: >>> >>>> Hi Didi, >>>> >>>> >>>> I've updated shorewall to Version 4.0.2 in DL 1.2.x and DL 1.3.x >>>> >>> >>> Thank you so much >>> >> >> BTW 4.0.3 is out :-) >> Shorewall-perl now requires the FindBin Perl module >> > > I made a custom DL cd which includes shorewall 4.0.3 with all patches > from the errata. It works find here, but I had to remove the comment from > "extra/pptp-conntrack-nat" in built/scripts/config in oder to get > shorewall running. Since nobody complained we're probably removing pptp-conntrack-nat from the standard install. -- Regards Heiko Zuerker http://www.devil-linux.org |
|
From: Heiko Z. <he...@zu...> - 2007-09-10 17:45:53
|
On Sun, September 9, 2007 23:48, Marc wrote: > Hi, > > > I am having a look at DL and the first issue I am running into is hard > disk support under VMware ESX server. > > I created a Virtual Machine that boots from the DL .iso file. My VM also > has a 64MB hard disk, connected to a virtual LSI Logic SCSI controller. > After > booting the VM, I type "fdisk -l", but there is no output. Am I correct to > assume DL does not recognise the hard disk and if so, what can be done > so that it does see this disk? > > Thank you in advance for any suggestions. Did you load the appropriate module for the scsi controller? I'm not sure which one hyou need for the LSI Logic, the Buslogic would be BusLogic. You have to add it to the /etc/sysconfig/config file, there's a paramater INITRD_MODULES (or similar to this). -- Regards Heiko Zuerker http://www.devil-linux.org |
|
From: Dietmar R. <die...@gm...> - 2007-09-10 17:14:07
|
2007/9/3, Dietmar Rieder <die...@gm...>: > 2007/8/28, Dietmar Rieder <die...@gm...>: > > Am 28.08.07 schrieb "Rudner, Bj=F6rn" <br...@ba...>: > > > Hi Didi, > > > > > > I've updated shorewall to Version 4.0.2 in DL 1.2.x and DL 1.3.x > > > > Thank you so much > > BTW 4.0.3 is out :-) > Shorewall-perl now requires the FindBin Perl module I made a custom DL cd which includes shorewall 4.0.3 with all patches from the errata. It works find here, but I had to remove the comment from "extra/pptp-conntrack-nat" in built/scripts/config in oder to get shorewall running. Didi |
|
From: Dietmar R. <die...@gm...> - 2007-09-10 17:12:23
|
2007/9/9, Heiko Zuerker <he...@zu...>: > > On Thu, September 6, 2007 14:21, Jasper Siepkes wrote: > > Hi all, > > > > > > I noted that OpenSwan was recently replaced by StrongSwan. Out of > > curiosity; Why was this ? I saw an other thread on the mailinglist which > > stated that strongswan was built on top of openswan with extra features. > > As far as I know, this is not the case and were both forked from the > > freeswan project (I Could be missing something tough..). > > > > I'm by no means a *Swan expert, but this comparison looks to be leaning > > to Openswan: http://wiki.openswan.org/index.php/Openswan/FeatureComparison > > > > > > Yes its on the openswan page :-) But StrongSwan > > http://www.strongswan.org/ linkes to the feature comparison. I doubt > > they would link to it if they would find it unfair. > > Unfortunately OpenSwan 3.0 (which is the base for this comparison) is not > released yet: > > Quote from http://www.openswan.org/code/ : > ---------------- > Openswan 3.0.xx should be consider highly experimental and very unstable. > Do not use it. > ---------------- I'm running the new (custom made) testing release using strongswan in a site-2-site tunnel mode (strongswan-cisco) and I had no problem sofar. Didi BTW: I had to remove the comment from "extra/pptp-conntrack-nat" in built/scripts/config in oder to get shorewall running. |
|
From: Dietmar R. <die...@gm...> - 2007-09-10 17:04:34
|
2007/8/31, Heiko Zuerker <he...@zu...>: > > On Fri, August 31, 2007 06:23, Dietmar Rieder wrote: > > 2007/8/23, Oliver Niesner <dig...@gm...>: > > > >> Hi, Heiko! > >> > >> > >> No good news from the new testing release - it crashed after the > >> bootmenu on my PIII 500 intel 440BX board with an "unable to handle > >> kernel paging request at virtual address d0000000" error and hangs. My > >> own iso crashed with the same error - it seems that the new kernel > >> doesn't like older hardware. On an slightly more modern PC (P4) it > >> starts like normal. > > > > The same happens here. After loading the initrd it crashes on my PIII > > 1000 (were it should finally run on). > > On a P4 or on my vmware it works. I build an iso for 486 and one for > > 686 but it doesn't make a difference... > > Can you swap out the memory on your PIII for a test? Ok, I was able to get some spare memory modules. I tested it with two different ones, but DL doesn't boot up. DL 1.2.13 works fine on this machine. But I found out that on another P III (866) the new release works. Unfortunately I can't use the second machine because it is in use for another VPN gateway. Didi |
|
From: Dom <dl...@ed...> - 2007-09-10 13:49:14
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Heiko Zuerker wrote:
<blockquote
cite="mid:496...@ww..."
type="cite">
<blockquote type="cite">
<pre wrap="">I've updated my instructions page which is really for my own benefit but
might help others here: <a class="moz-txt-link-freetext" href="http://www.edendevelopments.co.uk/dlsetup">http://www.edendevelopments.co.uk/dlsetup</a>
</pre>
</blockquote>
<pre wrap=""><!---->
I added a link to this How-To to the website.
It should show up tomorrow.
</pre>
</blockquote>
I am flattered and honoured! Of course I would be happy to receive any
suggestions for corrections or improvements. The How-To is focused on
setting up Devil-Linux from scratch to work as a Samba Server - because
this is how I use it.<br>
<br>
Dom<br>
</body>
</html>
|
|
From: Marc <1m...@gm...> - 2007-09-10 04:48:37
|
Hi, I am having a look at DL and the first issue I am running into is hard disk support under VMware ESX server. I created a Virtual Machine that boots from the DL .iso file. My VM also has a 64MB hard disk, connected to a virtual LSI Logic SCSI controller. After booting the VM, I type "fdisk -l", but there is no output. Am I correct to assume DL does not recognise the hard disk and if so, what can be done so that it does see this disk? Thank you in advance for any suggestions. Regards, /|/|arc. |
|
From: Heiko Z. <he...@zu...> - 2007-09-09 14:19:27
|
On Thu, September 6, 2007 14:21, Jasper Siepkes wrote: > Hi all, > > > I noted that OpenSwan was recently replaced by StrongSwan. Out of > curiosity; Why was this ? I saw an other thread on the mailinglist which > stated that strongswan was built on top of openswan with extra features. > As far as I know, this is not the case and were both forked from the > freeswan project (I Could be missing something tough..). > > I'm by no means a *Swan expert, but this comparison looks to be leaning > to Openswan: http://wiki.openswan.org/index.php/Openswan/FeatureComparison > > > Yes its on the openswan page :-) But StrongSwan > http://www.strongswan.org/ linkes to the feature comparison. I doubt > they would link to it if they would find it unfair. Unfortunately OpenSwan 3.0 (which is the base for this comparison) is not released yet: Quote from http://www.openswan.org/code/ : ---------------- Openswan 3.0.xx should be consider highly experimental and very unstable. Do not use it. ---------------- -- Regards Heiko Zuerker http://www.devil-linux.org |
|
From: Heiko Z. <he...@zu...> - 2007-09-09 14:15:31
|
> I've updated my instructions page which is really for my own benefit but > might help others here: http://www.edendevelopments.co.uk/dlsetup I added a link to this How-To to the website. It should show up tomorrow. -- Regards Heiko Zuerker http://www.devil-linux.org |
|
From: Heiko Z. <he...@zu...> - 2007-09-09 14:05:59
|
Peter, I took a quick look at the Strongswan 4.1 documentation and there's a parameter you have to set. Here's the extract from the doc: ------------- 11.1 Environment variables in the updown script strongSwan makes the following environment variables available in the updown script indicated by the leftupdown parameter: ------------- I'm not sure about the routes, it's quite a while since I used xxxxxSWAN Heiko On Tue, September 4, 2007 01:13, PeterJannesen, Visiq wrote: > Hi Heiko, > > > I did a small test on the new testing release (from 1.2.14-2007-05-24 to > 2007-08-23) > > > I read earlier that openswan is replaced by strongswan and it seems that > IPSec is not working anymore. > It seams that the tunnels are comming up but the routes are not created. > > > Furher it seems that /usr/lib/ipsec/_updown is not supporting > /etc/sysconfig/pluto_updown anymore. > I use pluto_updown to put the route in a different table with rules. I > my first impression is that strongswan is not supporting pluto_updown. This > is a problem because you can't change the standard /usr/lib/ipsec/_updown > script with out creating a custom build. > > -- Peter > > > -----Original Message----- > From: dev...@li... > [mailto:dev...@li...] On Behalf Of > Heiko Zuerker > Sent: donderdag 23 augustus 2007 16:49 > To: dev...@li... > Subject: [Devil-Linux-discuss] new testing release > > > Hey everyone, > > > I just uploaded a new testing release for 1.2.14 > ftp://ftp.devil-linux.org/pub/devel/testing > > > Would be great if some of you could test the latest updates. > > > Thx > > > -- > > > Regards > Heiko Zuerker > http://www.devil-linux.org > > > > > ------------------------------------------------------------------------ > - > 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-discuss mailing list > Dev...@li... > https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss > > > ------------------------------------------------------------------------- > 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-discuss mailing list > Dev...@li... > https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss > > -- Regards Heiko Zuerker http://www.devil-linux.org |
|
From: Heiko Z. <he...@zu...> - 2007-09-09 14:02:50
|
Hi, the thing we need in order to add it to the standard DL, are the scripts which integrate into the DL build system (build/mptlinux build/configuration/mptlinux etc.). Here's a description on sending in a patch. http://www.devil-linux.org/documentation/1.2.x/ch03s03.html Heiko On Tue, September 4, 2007 16:49, Jasper Siepkes wrote: > Well Patch is perhaps a big word :-) > > > Since I'm still a real noob with the DL buildsystem, I don't know if I > implemented the 'patch' correctly. I say 'patch' because it's not really a > patch, it just extracts the source tar ball in the correct location like > the docs state: http://www.lsi.com/support/downloads/mptlinux.txt > > I've got the tarball with drivers' source here: > http://www.siepkes.nl/jfire/mptlinux-2.06.65.00-src.tar.gz > > > You can also pull the drivers from here: > http://www.lsi.com/storage_home/products_home/host_bus_adapters/sas_hbas/l > si sas3801x/index.html?remote=1&locale=EN . That provides a tarball with > the source, RPM, SRPM, etc. > > Let me know if I need to change something about it. > > > Kind regards, > > > Jasper > > > -----Original Message----- > From: dev...@li... > [mailto:dev...@li...] On Behalf Of > Heiko Zuerker > Sent: dinsdag 4 september 2007 0:37 > To: dev...@li... > Subject: Re: [Devil-Linux-discuss] IPTables NAT module broken in DL 1.2 ? > > > Send in the patch. > > > Heiko > > > On Mon, September 3, 2007 17:26, Jasper Siepkes wrote: > >> The drivers in the kernel tarball itself are indeed not that update to >> date. However, most major hardware vendors still provide 2.4 driver >> support. >> >> My case with an LSI SAS Controller (MPT drivers) is a good example of >> this; They even have 2.2 driver support ! :-). I can confirm that >> everything works really well on a brand new HP Proliant DL140 G4. It >> makes an excellent (and cheap) gateway device. >> >> Is it possible for me to submit a patch with the updated MPT drivers >> for DL, >> or do you guys rather keep the kernel as Vanilla as possible ? It would >> certainly come in handy for everyone who wants to install DL on a HP >> Proliant, all SATA models use LSI controllers. >> >> >> >> -----Original Message----- >> From: dev...@li... >> [mailto:dev...@li...] On Behalf Of >> Heiko Zuerker >> Sent: maandag 3 september 2007 22:43 >> To: dev...@li... >> Subject: Re: [Devil-Linux-discuss] IPTables NAT module broken in DL 1.2 >> ? >> >> >> >> >> On Mon, September 3, 2007 15:04, Jasper Siepkes wrote: >> >> >>> Hmmmm... >>> >>> >>> >>> >>> Well I'm going to use DL as a firewall/gateway (shorewall, *Swan, >>> Squid, >>> etc.). And IMHO 2.6 is more volatile then 2.4. Take this for example: >>> http://www.debian.org/security/2007/dsa-1356 . Don't get me wrong; I >>> use 2.6 for plenty of production servers. But for the hub of my network >>> I prefer >>> 2.4. I want something rocksolid and I don't need any of the new >>> features in 2.6. So I ask myself (and you guys :-) ) what is the gain >>> for me ? >>> >>> >>> Of course I could be terribly ignorant :) So please share any >>> opinions you guys have on this subject. >> >> I fully agree with you. >> Our main problem which is coming up more and more is hardware >> compatibility. The 2.4 Kernel is rock solid, but the drivers are getting >> a little outdated. Don't get me wrong, it'll be a while until we have DL >> 1.3 where we want >> it, so 1.2 will be around for a little bit. >> >> -- >> >> >> >> Regards >> Heiko Zuerker >> http://www.devil-linux.org >> >> >> >> >> >> ----------------------------------------------------------------------- >> -- >> 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-discuss mailing list >> Dev...@li... >> https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss >> >> >> >> >> ----------------------------------------------------------------------- >> -- >> 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-discuss mailing list >> Dev...@li... >> https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss >> >> >> > > > -- > > > Regards > Heiko Zuerker > http://www.devil-linux.org > > > > > ------------------------------------------------------------------------- > 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-discuss mailing list > Dev...@li... > https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss > ------------------------------------------------------------------------- > 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-discuss mailing list > Dev...@li... > https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss > > -- Regards Heiko Zuerker http://www.devil-linux.org |
|
From: John J. <jo...@jo...> - 2007-09-07 21:11:49
|
Hi all, I too was surprised to see this, I'm in the middle of trying to implement a= VPN tunnel using L2TP/IPSEC to an Microsoft ISA firewall, and came across = the same web pages. One feature I noticed was: Feature strongswan-4.1.5 openswan-3.0.00 Windows IKE support No yes I confess to not knowing anything about IKE or IPSEC, but it can't be a bad= thing if I need to interact with Microsoft products... Would it be possible to know more about why DL is converting to strongswan = instead of openswan? Regards, John Jore From: dev...@li... [mailto:devil-linux= -dis...@li...] On Behalf Of Jasper Siepkes Sent: 6. september 2007 20:22 To: Devil Linux Subject: [Devil-Linux-discuss] StrongSWAN vs OpenSwan Hi all, I noted that OpenSwan was recently replaced by StrongSwan. Out of curiosity= ; Why was this ? I saw an other thread on the mailinglist which stated that= strongswan was built on top of openswan with extra features. As far as I k= now, this is not the case and were both forked from the freeswan project (I= Could be missing something tough..). I'm by no means a *Swan expert, but this comparison looks to be leaning to = Openswan: http://wiki.openswan.org/index.php/Openswan/FeatureComparison Yes its on the openswan page :-) But StrongSwan http://www.strongswan.org/ = linkes to the feature comparison. I doubt they would link to it if they wou= ld find it unfair. Kinds regards, Jasper |
|
From: Jasper S. <ja...@si...> - 2007-09-06 19:21:55
|
Hi all, I noted that OpenSwan was recently replaced by StrongSwan. Out of curiosity; Why was this ? I saw an other thread on the mailinglist which stated that strongswan was built on top of openswan with extra features. As far as I know, this is not the case and were both forked from the freeswan project (I Could be missing something tough..). I'm by no means a *Swan expert, but this comparison looks to be leaning to Openswan: http://wiki.openswan.org/index.php/Openswan/FeatureComparison Yes its on the openswan page :-) But StrongSwan http://www.strongswan.org/ linkes to the feature comparison. I doubt they would link to it if they would find it unfair. Kinds regards, Jasper |
|
From: Dom <dl...@ed...> - 2007-09-05 12:01:19
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Heiko Zuerker wrote:
<blockquote
cite="mid:542...@ww..."
type="cite">
<pre wrap="">On Mon, September 3, 2007 13:35, Dom wrote:
</pre>
<blockquote type="cite">
<pre wrap="">My DL-based samba server has worked like a dream for several years, now
it is on a serious go slow. Also I seem to have a lost an LVM logical
volume /var/data (filesystem ext2) - at boot there are messages something
like this: ---------------------------
fsck.ext2: Attempt to read block from filesystem resulted in short read
while trying to open /.../devil-linux/data Could this be a zero-length
partition? Mounting /var/data mount: you must specify the filesystem type
[FAILED]
---------------------------
But AFAIK I have never used /var/data so this shouldn't matter. The
other LVs (/home, /var/log, /opt, swap) seem to load OK but there are
usually transaction replays on /home (which is the important one with the
data) and /var/log.
And the samba server is running very slow. It has always been fast
before though I noticed a couple of months ago that it was occasionally
very slow accessing one sub-folder which had some very large files in it.
I have a very simple setup and haven't made any significant changes
recently. What is happening? My current theory is that the hard disk is
failing. I plan to (try to) migrate my data to a new RAID 1 two-disk array
and hope this gives me back the performance and gives better protection in
the event of failure.
But I am far out of my depth here. If anyone has any suggestions I would
be grateful to hear them!
</pre>
</blockquote>
<pre wrap=""><!---->
Your theory is most likely right, I would also point to the hard disk.
Make sure you got a good backup of everything, the disk may just stop
working completely soon or you may experience data loss.
Can you see anything in the syslog or on tty10 (alt + F10) ?
</pre>
</blockquote>
Thanks for your reply Heiko, and for confirming the diagnosis. You were
right about messages appearing on the local display - a series of
messages like this appeared on at least one occasion:<br>
end_request: I/O error, dev 03:00 (hda), sector 0<br>
<br>
So I:<br>
- took delivery of 2 new IDE PATA 160GB hard disks<br>
- configured them as software RAID1 following the DL instructions
(chapter 1 part 6), created a devil-linuz VG with the same LVs as the
existing disk [hardest bit for me was discovering the full name of the
RAID device to create the VG (<b>'</b>vgcreate -s 8M devil-linuz
/dev/md/0', because LVM1's vgcreate cannot use the /dev/md0 (or
/dev/hda etc)], checked this was all working okay. During this time the
old disk was still being used.<br>
- renamed the existing VG as devil-linux-old and renamed the new VG to
devil-linux (old disk no longer in use from this point of course as it
disappears from samba), rebooted<br>
- new devil-linux LVs are all auto-mounted, I manually mounted the old
home LV and then copied all files over to the new home LV<br>
<br>
Several hours later all seems to be working perfectly. I still don't
know quite what the original problem was, but it seems sorted and I
have more protection now (because of RAID1) against future hard disk
failure.<br>
<br>
I made one mistake (I now realise). I established the RAID1 device
directly off the drives not off the primary partitions. I typed:<br>
<span><b class="command"> mdadm --create /dev/md0 --chunk=64
--level=raid0 --raid-devices=2 /dev/hdb /dev/hdd<br>
</b><span class="command">instead of:<br>
</span></span><span><b class="command"> mdadm --create /dev/md0
--chunk=64 --level=raid0 --raid-devices=2 /dev/hdb1 /dev/hdd1<br>
</b><span class="command"><br>
I had created the partitions before doing this - I just got the typing
in the mdadm wrong (hdb instead of hdb1, hdd instead of hdd1). cat
/proc/mdstat reports:<br>
<br>
md0 : active raid1 ide/host0/bus0/target1/lun0/disc[0]
ide/host0/bus1/target1/lun0/disc[1]<br>
<br>
It all works fine but 'fdisk -l' reports that there are no partitions
on either of these drives (hdb or hdd). It seems to me that mdadm has
destroyed the partitions I created and is using the drives in some sort
of 'raw' unpartitioned state. Is this likely to cause me big problems
in the future? I'm uneasy that in the future someone (probably me)
might accidentally reformat one of these unpartitioned drives, not
realising that they are part of the RAID array. How would I undo this
(i.e. change the RAID device so it lies over partitions and not over
raw drives)? I presume that if I create partitions on the drives now I
will just destroy the information. But perhaps I can do it for one
drive/partition at a time and mdadm will rebuild the info?<br>
<br>
I've updated my instructions page which is really for my own benefit
but might help others here: <a class="moz-txt-link-freetext" href="http://www.edendevelopments.co.uk/dlsetup">http://www.edendevelopments.co.uk/dlsetup</a><br>
<br>
Thanks again!<br>
<br>
Dom<br>
</span></span>
</body>
</html>
|
|
From: Jasper S. <ja...@si...> - 2007-09-04 21:49:07
|
Well Patch is perhaps a big word :-) Since I'm still a real noob with the DL buildsystem, I don't know if I implemented the 'patch' correctly. I say 'patch' because it's not really a patch, it just extracts the source tar ball in the correct location like the docs state: http://www.lsi.com/support/downloads/mptlinux.txt I've got the tarball with drivers' source here: http://www.siepkes.nl/jfire/mptlinux-2.06.65.00-src.tar.gz You can also pull the drivers from here: http://www.lsi.com/storage_home/products_home/host_bus_adapters/sas_hbas/lsi sas3801x/index.html?remote=1&locale=EN . That provides a tarball with the source, RPM, SRPM, etc. Let me know if I need to change something about it. Kind regards, Jasper -----Original Message----- From: dev...@li... [mailto:dev...@li...] On Behalf Of Heiko Zuerker Sent: dinsdag 4 september 2007 0:37 To: dev...@li... Subject: Re: [Devil-Linux-discuss] IPTables NAT module broken in DL 1.2 ? Send in the patch. Heiko On Mon, September 3, 2007 17:26, Jasper Siepkes wrote: > The drivers in the kernel tarball itself are indeed not that update to > date. However, most major hardware vendors still provide 2.4 driver > support. > > My case with an LSI SAS Controller (MPT drivers) is a good example of > this; They even have 2.2 driver support ! :-). I can confirm that > everything works really well on a brand new HP Proliant DL140 G4. It makes > an excellent (and cheap) gateway device. > > Is it possible for me to submit a patch with the updated MPT drivers for > DL, > or do you guys rather keep the kernel as Vanilla as possible ? It would > certainly come in handy for everyone who wants to install DL on a HP > Proliant, all SATA models use LSI controllers. > > > -----Original Message----- > From: dev...@li... > [mailto:dev...@li...] On Behalf Of > Heiko Zuerker > Sent: maandag 3 september 2007 22:43 > To: dev...@li... > Subject: Re: [Devil-Linux-discuss] IPTables NAT module broken in DL 1.2 ? > > > > On Mon, September 3, 2007 15:04, Jasper Siepkes wrote: > >> Hmmmm... >> >> >> >> Well I'm going to use DL as a firewall/gateway (shorewall, *Swan, >> Squid, >> etc.). And IMHO 2.6 is more volatile then 2.4. Take this for example: >> http://www.debian.org/security/2007/dsa-1356 . Don't get me wrong; I >> use 2.6 >> for plenty of production servers. But for the hub of my network I prefer >> 2.4. I want something rocksolid and I don't need any of the new >> features in 2.6. So I ask myself (and you guys :-) ) what is the gain >> for me ? >> >> >> Of course I could be terribly ignorant :) So please share any opinions >> you guys have on this subject. > > I fully agree with you. > Our main problem which is coming up more and more is hardware > compatibility. The 2.4 Kernel is rock solid, but the drivers are getting a > little outdated. Don't get me wrong, it'll be a while until we have DL > 1.3 where we want > it, so 1.2 will be around for a little bit. > > -- > > > Regards > Heiko Zuerker > http://www.devil-linux.org > > > > > ------------------------------------------------------------------------- > 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-discuss mailing list > Dev...@li... > https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss > > > > ------------------------------------------------------------------------- > 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-discuss mailing list > Dev...@li... > https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss > > -- Regards Heiko Zuerker http://www.devil-linux.org ------------------------------------------------------------------------- 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-discuss mailing list Dev...@li... https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss |
|
From: Martin H. <ma...@ho...> - 2007-09-04 07:18:52
|
> -----Original Message----- > From: dev...@li... [mailto:devil- > lin...@li...] On Behalf Of Jasper Siepkes > Sent: Monday, September 03, 2007 10:04 PM > To: dev...@li... > Subject: Re: [Devil-Linux-discuss] IPTables NAT module broken in DL 1.2 ? >=20 (...) > So I ask myself (and you guys :-) ) what is the gain for me ? Hardware compatibility. We use new hardware (not only for DL) - and not old PII boxes. Mostly we'd need SATA harddrive support w/o the need of special hardware. > Of course I could be terribly ignorant :) So please share any opinions you > guys have on this subject. hth, martin |
|
From: PeterJannesen, V. <P.J...@vi...> - 2007-09-04 06:13:37
|
Hi Heiko, I did a small test on the new testing release (from 1.2.14-2007-05-24 to 2007-08-23) I read earlier that openswan is replaced by strongswan and it seems that IPSec is not working anymore. It seams that the tunnels are comming up but the routes are not created. Furher it seems that /usr/lib/ipsec/_updown is not supporting /etc/sysconfig/pluto_updown anymore. I use pluto_updown to put the route in a different table with rules. I my first impression is that strongswan is not supporting pluto_updown. This is a problem because you can't change the standard /usr/lib/ipsec/_updown script with out creating a custom build. -- Peter=20 -----Original Message----- From: dev...@li... [mailto:dev...@li...] On Behalf Of Heiko Zuerker Sent: donderdag 23 augustus 2007 16:49 To: dev...@li... Subject: [Devil-Linux-discuss] new testing release Hey everyone, I just uploaded a new testing release for 1.2.14 ftp://ftp.devil-linux.org/pub/devel/testing Would be great if some of you could test the latest updates. Thx --=20 Regards Heiko Zuerker http://www.devil-linux.org ------------------------------------------------------------------------ - 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-discuss mailing list Dev...@li... https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss |
|
From: Heiko Z. <he...@zu...> - 2007-09-03 22:37:04
|
Send in the patch. Heiko On Mon, September 3, 2007 17:26, Jasper Siepkes wrote: > The drivers in the kernel tarball itself are indeed not that update to > date. However, most major hardware vendors still provide 2.4 driver > support. > > My case with an LSI SAS Controller (MPT drivers) is a good example of > this; They even have 2.2 driver support ! :-). I can confirm that > everything works really well on a brand new HP Proliant DL140 G4. It makes > an excellent (and cheap) gateway device. > > Is it possible for me to submit a patch with the updated MPT drivers for > DL, > or do you guys rather keep the kernel as Vanilla as possible ? It would > certainly come in handy for everyone who wants to install DL on a HP > Proliant, all SATA models use LSI controllers. > > > -----Original Message----- > From: dev...@li... > [mailto:dev...@li...] On Behalf Of > Heiko Zuerker > Sent: maandag 3 september 2007 22:43 > To: dev...@li... > Subject: Re: [Devil-Linux-discuss] IPTables NAT module broken in DL 1.2 ? > > > > On Mon, September 3, 2007 15:04, Jasper Siepkes wrote: > >> Hmmmm... >> >> >> >> Well I'm going to use DL as a firewall/gateway (shorewall, *Swan, >> Squid, >> etc.). And IMHO 2.6 is more volatile then 2.4. Take this for example: >> http://www.debian.org/security/2007/dsa-1356 . Don't get me wrong; I >> use 2.6 >> for plenty of production servers. But for the hub of my network I prefer >> 2.4. I want something rocksolid and I don't need any of the new >> features in 2.6. So I ask myself (and you guys :-) ) what is the gain >> for me ? >> >> >> Of course I could be terribly ignorant :) So please share any opinions >> you guys have on this subject. > > I fully agree with you. > Our main problem which is coming up more and more is hardware > compatibility. The 2.4 Kernel is rock solid, but the drivers are getting a > little outdated. Don't get me wrong, it'll be a while until we have DL > 1.3 where we want > it, so 1.2 will be around for a little bit. > > -- > > > Regards > Heiko Zuerker > http://www.devil-linux.org > > > > > ------------------------------------------------------------------------- > 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-discuss mailing list > Dev...@li... > https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss > > > > ------------------------------------------------------------------------- > 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-discuss mailing list > Dev...@li... > https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss > > -- Regards Heiko Zuerker http://www.devil-linux.org |
|
From: Jasper S. <ja...@si...> - 2007-09-03 22:26:04
|
The drivers in the kernel tarball itself are indeed not that update to date. However, most major hardware vendors still provide 2.4 driver support. My case with an LSI SAS Controller (MPT drivers) is a good example of this; They even have 2.2 driver support ! :-). I can confirm that everything works really well on a brand new HP Proliant DL140 G4. It makes an excellent (and cheap) gateway device. Is it possible for me to submit a patch with the updated MPT drivers for DL, or do you guys rather keep the kernel as Vanilla as possible ? It would certainly come in handy for everyone who wants to install DL on a HP Proliant, all SATA models use LSI controllers. -----Original Message----- From: dev...@li... [mailto:dev...@li...] On Behalf Of Heiko Zuerker Sent: maandag 3 september 2007 22:43 To: dev...@li... Subject: Re: [Devil-Linux-discuss] IPTables NAT module broken in DL 1.2 ? On Mon, September 3, 2007 15:04, Jasper Siepkes wrote: > Hmmmm... > > > Well I'm going to use DL as a firewall/gateway (shorewall, *Swan, Squid, > etc.). And IMHO 2.6 is more volatile then 2.4. Take this for example: > http://www.debian.org/security/2007/dsa-1356 . Don't get me wrong; I use > 2.6 > for plenty of production servers. But for the hub of my network I prefer > 2.4. I want something rocksolid and I don't need any of the new features > in 2.6. So I ask myself (and you guys :-) ) what is the gain for me ? > > > Of course I could be terribly ignorant :) So please share any opinions > you guys have on this subject. I fully agree with you. Our main problem which is coming up more and more is hardware compatibility. The 2.4 Kernel is rock solid, but the drivers are getting a little outdated. Don't get me wrong, it'll be a while until we have DL 1.3 where we want it, so 1.2 will be around for a little bit. -- Regards Heiko Zuerker http://www.devil-linux.org ------------------------------------------------------------------------- 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-discuss mailing list Dev...@li... https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss |
|
From: Heiko Z. <he...@zu...> - 2007-09-03 20:45:08
|
On Mon, September 3, 2007 13:35, Dom wrote: > My DL-based samba server has worked like a dream for several years, now > it is on a serious go slow. Also I seem to have a lost an LVM logical > volume /var/data (filesystem ext2) - at boot there are messages something > like this: --------------------------- > fsck.ext2: Attempt to read block from filesystem resulted in short read > while trying to open /.../devil-linux/data Could this be a zero-length > partition? Mounting /var/data mount: you must specify the filesystem type > [FAILED] > --------------------------- > But AFAIK I have never used /var/data so this shouldn't matter. The > other LVs (/home, /var/log, /opt, swap) seem to load OK but there are > usually transaction replays on /home (which is the important one with the > data) and /var/log. > > And the samba server is running very slow. It has always been fast > before though I noticed a couple of months ago that it was occasionally > very slow accessing one sub-folder which had some very large files in it. > > > I have a very simple setup and haven't made any significant changes > recently. What is happening? My current theory is that the hard disk is > failing. I plan to (try to) migrate my data to a new RAID 1 two-disk array > and hope this gives me back the performance and gives better protection in > the event of failure. > > But I am far out of my depth here. If anyone has any suggestions I would > be grateful to hear them! Your theory is most likely right, I would also point to the hard disk. Make sure you got a good backup of everything, the disk may just stop working completely soon or you may experience data loss. Can you see anything in the syslog or on tty10 (alt + F10) ? -- Regards Heiko Zuerker http://www.devil-linux.org |
|
From: Heiko Z. <he...@zu...> - 2007-09-03 20:42:43
|
On Mon, September 3, 2007 15:04, Jasper Siepkes wrote: > Hmmmm... > > > Well I'm going to use DL as a firewall/gateway (shorewall, *Swan, Squid, > etc.). And IMHO 2.6 is more volatile then 2.4. Take this for example: > http://www.debian.org/security/2007/dsa-1356 . Don't get me wrong; I use > 2.6 > for plenty of production servers. But for the hub of my network I prefer > 2.4. I want something rocksolid and I don't need any of the new features > in 2.6. So I ask myself (and you guys :-) ) what is the gain for me ? > > > Of course I could be terribly ignorant :) So please share any opinions > you guys have on this subject. I fully agree with you. Our main problem which is coming up more and more is hardware compatibility. The 2.4 Kernel is rock solid, but the drivers are getting a little outdated. Don't get me wrong, it'll be a while until we have DL 1.3 where we want it, so 1.2 will be around for a little bit. -- Regards Heiko Zuerker http://www.devil-linux.org |
|
From: Jasper S. <ja...@si...> - 2007-09-03 20:03:49
|
Hmmmm... Well I'm going to use DL as a firewall/gateway (shorewall, *Swan, Squid, etc.). And IMHO 2.6 is more volatile then 2.4. Take this for example: http://www.debian.org/security/2007/dsa-1356 . Don't get me wrong; I use 2.6 for plenty of production servers. But for the hub of my network I prefer 2.4. I want something rocksolid and I don't need any of the new features in 2.6. So I ask myself (and you guys :-) ) what is the gain for me ? Of course I could be terribly ignorant :) So please share any opinions you guys have on this subject. Kind regards, Jasper -----Original Message----- From: dev...@li... [mailto:dev...@li...] On Behalf Of Heiko Zuerker Sent: maandag 3 september 2007 15:52 To: dev...@li... Subject: Re: [Devil-Linux-discuss] IPTables NAT module broken in DL 1.2 ? On Mon, September 3, 2007 08:46, Martin Hotze wrote: > I'd put the energy in a DL w/Kernel 2.6 ... but this is only me. Quite a few people are currently working on it (DL 1.3 that is), including me. I'm sure things will be progressing faster once summer is over and people get bored. ;-) I will like to release a new 1.2 version in the next couple of weeks but we need to make a decision on this issue first. -- Regards Heiko Zuerker http://www.devil-linux.org ------------------------------------------------------------------------- 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-discuss mailing list Dev...@li... https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss |
|
From: Dom <dl...@ed...> - 2007-09-03 19:38:46
|
My DL-based samba server has worked like a dream for several years, now it is on a serious go slow. Also I seem to have a lost an LVM logical volume /var/data (filesystem ext2) - at boot there are messages something like this: --------------------------- fsck.ext2: Attempt to read block from filesystem resulted in short read while trying to open /.../devil-linux/data Could this be a zero-length partition? Mounting /var/data mount: you must specify the filesystem type [FAILED] --------------------------- But AFAIK I have never used /var/data so this shouldn't matter. The other LVs (/home, /var/log, /opt, swap) seem to load OK but there are usually transaction replays on /home (which is the important one with the data) and /var/log. And the samba server is running very slow. It has always been fast before though I noticed a couple of months ago that it was occasionally very slow accessing one sub-folder which had some very large files in it. I have a very simple setup and haven't made any significant changes recently. What is happening? My current theory is that the hard disk is failing. I plan to (try to) migrate my data to a new RAID 1 two-disk array and hope this gives me back the performance and gives better protection in the event of failure. But I am far out of my depth here. If anyone has any suggestions I would be grateful to hear them! Dom |
|
From: Bruce S. <bw...@ar...> - 2007-09-03 17:45:14
|
>>>> No good news from the new testing release - it crashed after the >>>> bootmenu on my PIII 500 intel 440BX board with an "unable to handle >>>> kernel paging request at virtual address d0000000" error and hangs. My >>>> own iso crashed with the same error - it seems that the new kernel >>>> doesn't like older hardware. On an slightly more modern PC (P4) it >>>> starts like normal. >>>> >>> The same happens here. After loading the initrd it crashes on my PIII >>> 1000 (were it should finally run on). >>> On a P4 or on my vmware it works. I build an iso for 486 and one for >>> 686 but it doesn't make a difference... >>> >> Can you swap out the memory on your PIII for a test > > If you tell me how to do that, I'll try... > You could just test your memory, instead of replacing it. >From the first Devil Linux boot prompt, select "Memtest" (M), and let the test run for a couple days. Check the monitor for errors. - BS |
50 messages has been excluded from this view by a project administrator.
