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...> - 2010-09-13 13:42:04
|
I was contemplating about it, but didn't do it yet since it just recently got released. On the other hand, dovecot has always released pretty stable software. Any opinions on this? Heiko > -----Original Message----- > From: Udo Lembke [mailto:udo...@al...] > Sent: Monday, September 13, 2010 8:09 AM > To: dev...@li... > Subject: [Devil-Linux-discuss] dovecot 2 > > Hi, > are there any plan to include Dovecot 2.0.x in the 1.4 release? > After a long beta phase dovecot 2 should be usable for production, or > not? > > Udo > > ------------------------------------------------------------------------ ------ > Start uncovering the many advantages of virtual appliances and start > using them to simplify application deployment and accelerate your shift > to cloud computing http://p.sf.net/sfu/novell-sfdev2dev > _______________________________________________ > Devil-linux-discuss mailing list > Dev...@li... > https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss |
|
From: Udo L. <udo...@al...> - 2010-09-13 13:28:04
|
Hi, are there any plan to include Dovecot 2.0.x in the 1.4 release? After a long beta phase dovecot 2 should be usable for production, or not? Udo |
|
From: mailing d. <mai...@gm...> - 2010-09-13 11:41:48
|
Thanks, I will use alias. Regards. 2010/9/13 Dominic Raferd <dl...@ed...>: > On your first question: it's become mailx instead of nail. You could > use an alias I think to ensure that all old code that expects nail runs > okay with mailx. > > Dominic > > On 13/09/2010 10:32, mailing dl2 wrote: >> Dear All, >> >> Just to tell you that /usr/bin/nail is missing in the testing release dl1.4rc5. >> >> Is there any way to make the beep working when using a "install-on-usb >> (with serial)" release? >> >> Regards. > > ------------------------------------------------------------------------------ > Start uncovering the many advantages of virtual appliances > and start using them to simplify application deployment and > accelerate your shift to cloud computing > http://p.sf.net/sfu/novell-sfdev2dev > _______________________________________________ > Devil-linux-discuss mailing list > Dev...@li... > https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss > |
|
From: Dominic R. <dl...@ed...> - 2010-09-13 09:37:55
|
On your first question: it's become mailx instead of nail. You could use an alias I think to ensure that all old code that expects nail runs okay with mailx. Dominic On 13/09/2010 10:32, mailing dl2 wrote: > Dear All, > > Just to tell you that /usr/bin/nail is missing in the testing release dl1.4rc5. > > Is there any way to make the beep working when using a "install-on-usb > (with serial)" release? > > Regards. |
|
From: mailing d. <mai...@gm...> - 2010-09-13 09:32:15
|
Dear All, Just to tell you that /usr/bin/nail is missing in the testing release dl1.4rc5. Is there any way to make the beep working when using a "install-on-usb (with serial)" release? Regards. |
|
From: Heiko Z. <he...@zu...> - 2010-09-04 13:12:16
|
DL 1.4 needs at least 64 MB. Heiko > -----Original Message----- > From: kor...@sb... [mailto:kor...@sb...] > Sent: Friday, September 03, 2010 7:56 AM > To: dev...@li... > Subject: Re: [Devil-Linux-discuss] RAM requirements > > OK, results on kvm machine and --memory=max showed me 64Mb not > enough. > 96Mb works ok. Going virtual costs practically nothing... > How about future DL releases and hardware RAM requirements? > > On 09/03/10 15:13, Heiko Zuerker wrote: > > Why are you trying it with 99%? > > 'max' is what works.... > > > > Heiko > > > > Quoting "kor...@sb..." <kor...@sb...>: > > > >> I'm trying with --memory=99%, "but 65 MiB would have been > needed" > >> > >> On 09/02/10 19:00, Heiko Zuerker wrote: > >>> Hey, > >>> > >>> edit the file /etc/man.conf > >>> Search for "unlzma" and edit the line so it looks like this: > >>> .lzma /usr/bin/unlzma --memory=max -c -d > >>> > >>> This will fix the issue. I'll add it to CVS. > >>> > >>> Heiko > >>> > >>> Quoting "kor...@sb..." <kor...@sb...>: > >>>> 128Mb box got good-old 1.2.14 release and went to work :) Here > >>>> comes tests with 64mb box: > >>>> #free > >>>> total used free shared buffers cached > >>>> Mem: 54496 52132 2364 0 8600 34716 > >>>> -/+ buffers/cache: 8816 45680 > >>>> Swap: 0 0 0 > >>>> > >>>> #man man > >>>> > >>>> /usr/bin/unlzma: /usr/share/man/man1/man.1.lzma: Memory > usage limit > >>>> reached > >>>> /usr/bin/unlzma: Limit was 21 MiB, but 65 MiB would have been > >>>> needed > >>>> fgets: No such file or directory > >>>> Error reading man page /usr/share/man/man1/man.1.lzma > >>>> /usr/bin/unlzma: /usr/man/man1/man.1.lzma: Memory usage limit > >>>> reached > >>>> /usr/bin/unlzma: Limit was 21 MiB, but 65 MiB would have been > >>>> needed > >>>> fgets: No such file or directory > >>>> Error reading man page /usr/man/man1/man.1.lzma No manual > entry for > >>>> man > >>>> > >>>> > >>>> The same result was with 128Mb box, but limit was about 56MiB I > run > >>>> no software. Not even sshd! > >>>> > >>>> On 09/02/10 16:29, Heiko Zuerker wrote: > >>>>> Hey, > >>>>> > >>>>> what else do you have running on this box? > >>>>> What's the output of the 'free' command? > >>>>> > >>>>> Heiko > >>>>> > >>>>> Quoting "kor...@sb..." <kor...@sb...>: > >>>>>> Hi! > >>>>>> > >>>>>> Seems like 1.4RC4-i686 requires more than 128 Mb RAM for lzma > >>>>>> compression. > >>>>>> Unable to read man pages. > >>>>>> Sad... > >>>>>> > >>>>>> > >>>>>> > >>>>>> ----------------------------------------------------------------- > >>>>>> ------------- This SF.net Dev2Dev email is sponsored by: > >>>>>> > >>>>>> Show off your parallel programming skills. > >>>>>> Enter the Intel(R) Threading Challenge 2010. > >>>>>> http://p.sf.net/sfu/intel-thread-sfd > >>>>>> _______________________________________________ > >>>>>> Devil-linux-discuss mailing list > >>>>>> Dev...@li... > >>>>>> https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss > >>>>>> > >>>> ------------------------------------------------------------------- > >>>> ----------- This SF.net Dev2Dev email is sponsored by: > >>>> > >>>> Show off your parallel programming skills. > >>>> Enter the Intel(R) Threading Challenge 2010. > >>>> http://p.sf.net/sfu/intel-thread-sfd > >>>> _______________________________________________ > >>>> Devil-linux-discuss mailing list > >>>> Dev...@li... > >>>> https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss > >>>> > >>> > >> > >> --------------------------------------------------------------------- > >> --------- This SF.net Dev2Dev email is sponsored by: > >> > >> Show off your parallel programming skills. > >> Enter the Intel(R) Threading Challenge 2010. > >> http://p.sf.net/sfu/intel-thread-sfd > >> _______________________________________________ > >> Devil-linux-discuss mailing list > >> Dev...@li... > >> https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss > >> > > > > > > > ------------------------------------------------------------------------ ------ > This SF.net Dev2Dev email is sponsored by: > > Show off your parallel programming skills. > Enter the Intel(R) Threading Challenge 2010. > http://p.sf.net/sfu/intel-thread-sfd > _______________________________________________ > Devil-linux-discuss mailing list > Dev...@li... > https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss |
|
From: Bradlee L. <bra...@gm...> - 2010-09-03 21:24:29
|
On Fri, Sep 3, 2010 at 10:42 AM, Bradlee Landis <bra...@gm...> wrote: > Is snort-inline working correctly? It looks like it's probably not working correctly, but I don't know for sure. It gives me this # snort -Qc /etc/snort/snort.conf -N -A console Enabling inline operation Running in IDS mode == CUT == *** interface device lookup found: bond0 *** Initializing Network Interface bond0 Decoding Ethernet on interface bond0 == CUT == Not Using PCAP_FRAMES So it says inline, but it also says using bond0, which it shouldn't have to initialize on an interface since it is getting the packets from iptables, right? It works without a QUEUE target in iptables, which is not what I was expecting. Anyways, any help would be appreciated. -- Thanks, Brad Landis |
|
From: Bradlee L. <bra...@gm...> - 2010-09-03 15:42:52
|
Is snort-inline working correctly? When I run these, it just seems to drop all packets: iptables -A INPUT -j QUEUE snort -QDc /etc/snort/snort.conf I downloaded the latest rules from snort, so maybe something is missing from my config, but I've searched and searched, and had no luck. -- Thanks, Brad Landis |
|
From: <kor...@sb...> - 2010-09-03 12:56:35
|
OK, results on kvm machine and --memory=max showed me 64Mb not enough. 96Mb works ok. Going virtual costs practically nothing... How about future DL releases and hardware RAM requirements? On 09/03/10 15:13, Heiko Zuerker wrote: > Why are you trying it with 99%? > 'max' is what works.... > > Heiko > > Quoting "kor...@sb..." <kor...@sb...>: > >> I'm trying with --memory=99%, "but 65 MiB would have been needed" >> >> On 09/02/10 19:00, Heiko Zuerker wrote: >>> Hey, >>> >>> edit the file /etc/man.conf >>> Search for "unlzma" and edit the line so it looks like this: >>> .lzma /usr/bin/unlzma --memory=max -c -d >>> >>> This will fix the issue. I'll add it to CVS. >>> >>> Heiko >>> >>> Quoting "kor...@sb..." <kor...@sb...>: >>>> 128Mb box got good-old 1.2.14 release and went to work :) >>>> Here comes tests with 64mb box: >>>> #free >>>> total used free shared buffers cached >>>> Mem: 54496 52132 2364 0 8600 34716 >>>> -/+ buffers/cache: 8816 45680 >>>> Swap: 0 0 0 >>>> >>>> #man man >>>> >>>> /usr/bin/unlzma: /usr/share/man/man1/man.1.lzma: Memory usage limit reached >>>> /usr/bin/unlzma: Limit was 21 MiB, but 65 MiB would have been needed >>>> fgets: No such file or directory >>>> Error reading man page /usr/share/man/man1/man.1.lzma >>>> /usr/bin/unlzma: /usr/man/man1/man.1.lzma: Memory usage limit reached >>>> /usr/bin/unlzma: Limit was 21 MiB, but 65 MiB would have been needed >>>> fgets: No such file or directory >>>> Error reading man page /usr/man/man1/man.1.lzma >>>> No manual entry for man >>>> >>>> >>>> The same result was with 128Mb box, but limit was about 56MiB >>>> I run no software. Not even sshd! >>>> >>>> On 09/02/10 16:29, Heiko Zuerker wrote: >>>>> Hey, >>>>> >>>>> what else do you have running on this box? >>>>> What's the output of the 'free' command? >>>>> >>>>> Heiko >>>>> >>>>> Quoting "kor...@sb..." <kor...@sb...>: >>>>>> Hi! >>>>>> >>>>>> Seems like 1.4RC4-i686 requires more than 128 Mb RAM for lzma >>>>>> compression. >>>>>> Unable to read man pages. >>>>>> Sad... >>>>>> >>>>>> >>>>>> >>>>>> ------------------------------------------------------------------------------ >>>>>> This SF.net Dev2Dev email is sponsored by: >>>>>> >>>>>> Show off your parallel programming skills. >>>>>> Enter the Intel(R) Threading Challenge 2010. >>>>>> http://p.sf.net/sfu/intel-thread-sfd >>>>>> _______________________________________________ >>>>>> Devil-linux-discuss mailing list >>>>>> Dev...@li... >>>>>> https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss >>>>>> >>>> ------------------------------------------------------------------------------ >>>> This SF.net Dev2Dev email is sponsored by: >>>> >>>> Show off your parallel programming skills. >>>> Enter the Intel(R) Threading Challenge 2010. >>>> http://p.sf.net/sfu/intel-thread-sfd >>>> _______________________________________________ >>>> Devil-linux-discuss mailing list >>>> Dev...@li... >>>> https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss >>>> >>> >> >> ------------------------------------------------------------------------------ >> This SF.net Dev2Dev email is sponsored by: >> >> Show off your parallel programming skills. >> Enter the Intel(R) Threading Challenge 2010. >> http://p.sf.net/sfu/intel-thread-sfd >> _______________________________________________ >> Devil-linux-discuss mailing list >> Dev...@li... >> https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss >> > > |
|
From: Heiko Z. <he...@zu...> - 2010-09-03 12:13:32
|
Why are you trying it with 99%? 'max' is what works.... Heiko Quoting "kor...@sb..." <kor...@sb...>: > I'm trying with --memory=99%, "but 65 MiB would have been needed" > > On 09/02/10 19:00, Heiko Zuerker wrote: >> Hey, >> >> edit the file /etc/man.conf >> Search for "unlzma" and edit the line so it looks like this: >> .lzma /usr/bin/unlzma --memory=max -c -d >> >> This will fix the issue. I'll add it to CVS. >> >> Heiko >> >> Quoting "kor...@sb..." <kor...@sb...>: >>> 128Mb box got good-old 1.2.14 release and went to work :) >>> Here comes tests with 64mb box: >>> #free >>> total used free shared buffers cached >>> Mem: 54496 52132 2364 0 8600 34716 >>> -/+ buffers/cache: 8816 45680 >>> Swap: 0 0 0 >>> >>> #man man >>> >>> /usr/bin/unlzma: /usr/share/man/man1/man.1.lzma: Memory usage limit reached >>> /usr/bin/unlzma: Limit was 21 MiB, but 65 MiB would have been needed >>> fgets: No such file or directory >>> Error reading man page /usr/share/man/man1/man.1.lzma >>> /usr/bin/unlzma: /usr/man/man1/man.1.lzma: Memory usage limit reached >>> /usr/bin/unlzma: Limit was 21 MiB, but 65 MiB would have been needed >>> fgets: No such file or directory >>> Error reading man page /usr/man/man1/man.1.lzma >>> No manual entry for man >>> >>> >>> The same result was with 128Mb box, but limit was about 56MiB >>> I run no software. Not even sshd! >>> >>> On 09/02/10 16:29, Heiko Zuerker wrote: >>>> Hey, >>>> >>>> what else do you have running on this box? >>>> What's the output of the 'free' command? >>>> >>>> Heiko >>>> >>>> Quoting "kor...@sb..." <kor...@sb...>: >>>>> Hi! >>>>> >>>>> Seems like 1.4RC4-i686 requires more than 128 Mb RAM for lzma >>>>> compression. >>>>> Unable to read man pages. >>>>> Sad... >>>>> >>>>> >>>>> >>>>> ------------------------------------------------------------------------------ >>>>> This SF.net Dev2Dev email is sponsored by: >>>>> >>>>> Show off your parallel programming skills. >>>>> Enter the Intel(R) Threading Challenge 2010. >>>>> http://p.sf.net/sfu/intel-thread-sfd >>>>> _______________________________________________ >>>>> Devil-linux-discuss mailing list >>>>> Dev...@li... >>>>> https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss >>>>> >>>> >>> >>> ------------------------------------------------------------------------------ >>> This SF.net Dev2Dev email is sponsored by: >>> >>> Show off your parallel programming skills. >>> Enter the Intel(R) Threading Challenge 2010. >>> http://p.sf.net/sfu/intel-thread-sfd >>> _______________________________________________ >>> Devil-linux-discuss mailing list >>> Dev...@li... >>> https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss >>> >> >> > > > ------------------------------------------------------------------------------ > This SF.net Dev2Dev email is sponsored by: > > Show off your parallel programming skills. > Enter the Intel(R) Threading Challenge 2010. > http://p.sf.net/sfu/intel-thread-sfd > _______________________________________________ > 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 message was sent using IMP, the Internet Messaging Program. |
|
From: <kor...@sb...> - 2010-09-03 07:07:55
|
I'm trying with --memory=99%, "but 65 MiB would have been needed" On 09/02/10 19:00, Heiko Zuerker wrote: > Hey, > > edit the file /etc/man.conf > Search for "unlzma" and edit the line so it looks like this: > .lzma /usr/bin/unlzma --memory=max -c -d > > This will fix the issue. I'll add it to CVS. > > Heiko > > Quoting "kor...@sb..." <kor...@sb...>: >> 128Mb box got good-old 1.2.14 release and went to work :) >> Here comes tests with 64mb box: >> #free >> total used free shared buffers cached >> Mem: 54496 52132 2364 0 8600 34716 >> -/+ buffers/cache: 8816 45680 >> Swap: 0 0 0 >> >> #man man >> >> /usr/bin/unlzma: /usr/share/man/man1/man.1.lzma: Memory usage limit reached >> /usr/bin/unlzma: Limit was 21 MiB, but 65 MiB would have been needed >> fgets: No such file or directory >> Error reading man page /usr/share/man/man1/man.1.lzma >> /usr/bin/unlzma: /usr/man/man1/man.1.lzma: Memory usage limit reached >> /usr/bin/unlzma: Limit was 21 MiB, but 65 MiB would have been needed >> fgets: No such file or directory >> Error reading man page /usr/man/man1/man.1.lzma >> No manual entry for man >> >> >> The same result was with 128Mb box, but limit was about 56MiB >> I run no software. Not even sshd! >> >> On 09/02/10 16:29, Heiko Zuerker wrote: >>> Hey, >>> >>> what else do you have running on this box? >>> What's the output of the 'free' command? >>> >>> Heiko >>> >>> Quoting "kor...@sb..." <kor...@sb...>: >>>> Hi! >>>> >>>> Seems like 1.4RC4-i686 requires more than 128 Mb RAM for lzma compression. >>>> Unable to read man pages. >>>> Sad... >>>> >>>> >>>> >>>> ------------------------------------------------------------------------------ >>>> This SF.net Dev2Dev email is sponsored by: >>>> >>>> Show off your parallel programming skills. >>>> Enter the Intel(R) Threading Challenge 2010. >>>> http://p.sf.net/sfu/intel-thread-sfd >>>> _______________________________________________ >>>> Devil-linux-discuss mailing list >>>> Dev...@li... >>>> https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss >>>> >>> >> >> ------------------------------------------------------------------------------ >> This SF.net Dev2Dev email is sponsored by: >> >> Show off your parallel programming skills. >> Enter the Intel(R) Threading Challenge 2010. >> http://p.sf.net/sfu/intel-thread-sfd >> _______________________________________________ >> Devil-linux-discuss mailing list >> Dev...@li... >> https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss >> > > |
|
From: James K. <jke...@gm...> - 2010-09-02 17:57:40
|
Yes I believe I'm not allowing them through. They are all currently tagged as active queue, so I think I know what is happening now. Thanks again for the help. On Thu, Sep 2, 2010 at 1:54 PM, Heiko Zuerker <he...@zu...> wrote: > sending the queued mail is done with: > > sendmail -q > > I really can't help you configure and debug your mail system, please take a > look at the postfix documentation. > > Heiko > > Quoting James Kessler <jke...@gm...>: > > Yes, thank you very much. > > I did run a quick mailq, and it does seem that all messages I've attempted > to send are indeed stuck in the queue. How can I clear them? > > On Thu, Sep 2, 2010 at 1:19 PM, Heiko Zuerker <he...@zu...> wrote: > >> Almost forgot: >> after changing the syslog-ng config file, you'll of course have to >> activate the changes by either running >> /etc/init.d/syslog reload >> or >> /etc/init.d/syslog restart >> >> Heiko >> >> Quoting Heiko Zuerker <he...@zu...>: >> >> > James, >> > >> > per default syslog-ng is active, not syslog. >> > You'll have to edit the file /etc/syslog-ng/syslog-ng.conf and >> > simply uncomment the 2 lines for /var/log/messages. >> > This will log all messages, not just mail. >> > >> > You could also simply check on console 10 for postfix messages ( alt F10 >> ). >> > >> > You can use the mailq command to see if the mail is still hanging in >> > the queue. >> > >> > Heiko >> > >> > Quoting James Kessler <jke...@gm...>: >> > >> >> Hello again, I have just initiated Postfix in Devil Linux. I've >> >> walked through >> >> the configuration files and believe I have set everything up >> >> correctly. When I execute a simple mail command to test it, I am >> >> able to fill out all categories such as subject, the message body >> >> and so on. After I hit ctr+D it seems to send the message without >> >> any errors. However, I am not actually receiving the email. I'm >> >> thinking it's possible I am blocking it within my own firewall, >> >> however I would like to setup my own Postfix Log to see if I am >> >> getting any errors. It is to my understanding that Postfix logs all >> >> failed and >> >> successful deliveries write to a log file. The file, in my case is >> >> in /var/log/mail, and I initiate it in the /etc/syslog.conf file. >> >> However the problem is that after I un-comment the /var/log/mail >> >> line in /etc/syslog.conf the mail log is not being generated after I >> >> attempt to send mail. I have tried a Postfix Reload. Any >> >> thoughts? Thanks again. -- James E. Kessler >> > >> > -- >> > >> > Regards >> > Heiko Zuerker >> > http://www.devil-linux.org >> > >> > ---------------------------------------------------------------- >> > This message was sent using IMP, the Internet Messaging Program. >> > >> > >> >> >> >> -- >> >> Regards >> Heiko Zuerker >> http://www.devil-linux.org >> >> >> ---------------------------------------------------------------- >> This message was sent using IMP, the Internet Messaging Program. >> >> >> >> >> ------------------------------------------------------------------------------ >> This SF.net Dev2Dev email is sponsored by: >> >> Show off your parallel programming skills. >> Enter the Intel(R) Threading Challenge 2010. >> http://p.sf.net/sfu/intel-thread-sfd >> _______________________________________________ >> Devil-linux-discuss mailing list >> Dev...@li... >> https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss >> > > > > -- > James E. Kessler > > -- > > Regards > Heiko Zuerker > http://www.devil-linux.org > > > > ---------------------------------------------------------------- > This message was sent using IMP, the Internet Messaging Program. > > > ------------------------------------------------------------------------------ > This SF.net Dev2Dev email is sponsored by: > > Show off your parallel programming skills. > Enter the Intel(R) Threading Challenge 2010. > http://p.sf.net/sfu/intel-thread-sfd > _______________________________________________ > Devil-linux-discuss mailing list > Dev...@li... > https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss > > -- James E. Kessler |
|
From: Heiko Z. <he...@zu...> - 2010-09-02 17:54:32
|
sending the queued mail is done with: sendmail -q I really can't help you configure and debug your mail system, please take a look at the postfix documentation. Heiko Quoting James Kessler <jke...@gm...>: > Yes, thank you very much. > > > I did run a quick mailq, and it does seem that all messages I've attempted to send are indeed stuck in the queue. How can I clear them? > > > On Thu, Sep 2, 2010 at 1:19 PM, Heiko Zuerker <he...@zu...> wrote: > > > > Almost forgot: > > after changing the syslog-ng config file, you'll of course have to > > activate the changes by either running > > /etc/init.d/syslog reload > > or > > /etc/init.d/syslog restart > > > > Heiko > > > > Quoting Heiko Zuerker <he...@zu...>: > > > > > James, > > > > > > per default syslog-ng is active, not syslog. > > > You'll have to edit the file /etc/syslog-ng/syslog-ng.conf and > > > simply uncomment the 2 lines for /var/log/messages. > > > This will log all messages, not just mail. > > > > > > You could also simply check on console 10 for postfix messages ( alt F10 ). > > > > > > You can use the mailq command to see if the mail is still hanging in > > > the queue. > > > > > > Heiko > > > > > > Quoting James Kessler <jke...@gm...>: > > > > > >> Hello again, I have just initiated Postfix in Devil Linux. I've > > >> walked through > > >> the configuration files and believe I have set everything up > > >> correctly. When I execute a simple mail command to test it, I am > > >> able to fill out all categories such as subject, the message body > > >> and so on. After I hit ctr+D it seems to send the message without > > >> any errors. However, I am not actually receiving the email. I'm > > >> thinking it's possible I am blocking it within my own firewall, > > >> however I would like to setup my own Postfix Log to see if I am > > >> getting any errors. It is to my understanding that Postfix logs all > > >> failed and > > >> successful deliveries write to a log file. The file, in my case is > > >> in /var/log/mail, and I initiate it in the /etc/syslog.conf file. > > >> However the problem is that after I un-comment the /var/log/mail > > >> line in /etc/syslog.conf the mail log is not being generated after I > > >> attempt to send mail. I have tried a Postfix Reload. Any > > >> thoughts? Thanks again. -- James E. Kessler > > > > > > -- > > > > > > Regards > > > Heiko Zuerker > > > http://www.devil-linux.org > > > > > > ---------------------------------------------------------------- > > > This message was sent using IMP, the Internet Messaging Program. > > > > > > > > > > -- > > > > Regards > > Heiko Zuerker > > http://www.devil-linux.org > > > > > > ---------------------------------------------------------------- > > This message was sent using IMP, the Internet Messaging Program. > > > > ------------------------------------------------------------------------------ > > This SF.net Dev2Dev email is sponsored by: > > > > Show off your parallel programming skills. > > Enter the Intel(R) Threading Challenge 2010. > > http://p.sf.net/sfu/intel-thread-sfd > > _______________________________________________ > > Devil-linux-discuss mailing list > > Dev...@li... > > https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss > > -- > James E. Kessler -- Regards Heiko Zuerker http://www.devil-linux.org ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. |
|
From: James K. <jke...@gm...> - 2010-09-02 17:23:08
|
Yes, thank you very much. I did run a quick mailq, and it does seem that all messages I've attempted to send are indeed stuck in the queue. How can I clear them? On Thu, Sep 2, 2010 at 1:19 PM, Heiko Zuerker <he...@zu...> wrote: > Almost forgot: > after changing the syslog-ng config file, you'll of course have to > activate the changes by either running > /etc/init.d/syslog reload > or > /etc/init.d/syslog restart > > Heiko > > Quoting Heiko Zuerker <he...@zu...>: > > > James, > > > > per default syslog-ng is active, not syslog. > > You'll have to edit the file /etc/syslog-ng/syslog-ng.conf and > > simply uncomment the 2 lines for /var/log/messages. > > This will log all messages, not just mail. > > > > You could also simply check on console 10 for postfix messages ( alt F10 > ). > > > > You can use the mailq command to see if the mail is still hanging in > > the queue. > > > > Heiko > > > > Quoting James Kessler <jke...@gm...>: > > > >> Hello again, I have just initiated Postfix in Devil Linux. I've > >> walked through > >> the configuration files and believe I have set everything up > >> correctly. When I execute a simple mail command to test it, I am > >> able to fill out all categories such as subject, the message body > >> and so on. After I hit ctr+D it seems to send the message without > >> any errors. However, I am not actually receiving the email. I'm > >> thinking it's possible I am blocking it within my own firewall, > >> however I would like to setup my own Postfix Log to see if I am > >> getting any errors. It is to my understanding that Postfix logs all > >> failed and > >> successful deliveries write to a log file. The file, in my case is > >> in /var/log/mail, and I initiate it in the /etc/syslog.conf file. > >> However the problem is that after I un-comment the /var/log/mail > >> line in /etc/syslog.conf the mail log is not being generated after I > >> attempt to send mail. I have tried a Postfix Reload. Any > >> thoughts? Thanks again. -- James E. Kessler > > > > -- > > > > Regards > > Heiko Zuerker > > http://www.devil-linux.org > > > > ---------------------------------------------------------------- > > This message was sent using IMP, the Internet Messaging Program. > > > > > > > > -- > > Regards > Heiko Zuerker > http://www.devil-linux.org > > > ---------------------------------------------------------------- > This message was sent using IMP, the Internet Messaging Program. > > > > > ------------------------------------------------------------------------------ > This SF.net Dev2Dev email is sponsored by: > > Show off your parallel programming skills. > Enter the Intel(R) Threading Challenge 2010. > http://p.sf.net/sfu/intel-thread-sfd > _______________________________________________ > Devil-linux-discuss mailing list > Dev...@li... > https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss > -- James E. Kessler |
|
From: Heiko Z. <he...@zu...> - 2010-09-02 17:19:47
|
Almost forgot: after changing the syslog-ng config file, you'll of course have to activate the changes by either running /etc/init.d/syslog reload or /etc/init.d/syslog restart Heiko Quoting Heiko Zuerker <he...@zu...>: > James, > > per default syslog-ng is active, not syslog. > You'll have to edit the file /etc/syslog-ng/syslog-ng.conf and > simply uncomment the 2 lines for /var/log/messages. > This will log all messages, not just mail. > > You could also simply check on console 10 for postfix messages ( alt F10 ). > > You can use the mailq command to see if the mail is still hanging in > the queue. > > Heiko > > Quoting James Kessler <jke...@gm...>: > >> Hello again, I have just initiated Postfix in Devil Linux. I've >> walked through >> the configuration files and believe I have set everything up >> correctly. When I execute a simple mail command to test it, I am >> able to fill out all categories such as subject, the message body >> and so on. After I hit ctr+D it seems to send the message without >> any errors. However, I am not actually receiving the email. I'm >> thinking it's possible I am blocking it within my own firewall, >> however I would like to setup my own Postfix Log to see if I am >> getting any errors. It is to my understanding that Postfix logs all >> failed and >> successful deliveries write to a log file. The file, in my case is >> in /var/log/mail, and I initiate it in the /etc/syslog.conf file. >> However the problem is that after I un-comment the /var/log/mail >> line in /etc/syslog.conf the mail log is not being generated after I >> attempt to send mail. I have tried a Postfix Reload. Any >> thoughts? Thanks again. -- James E. Kessler > > -- > > Regards > Heiko Zuerker > http://www.devil-linux.org > > ---------------------------------------------------------------- > This message was sent using IMP, the Internet Messaging Program. > > -- Regards Heiko Zuerker http://www.devil-linux.org ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. |
|
From: Heiko Z. <he...@zu...> - 2010-09-02 17:18:31
|
James, per default syslog-ng is active, not syslog. You'll have to edit the file /etc/syslog-ng/syslog-ng.conf and simply uncomment the 2 lines for /var/log/messages. This will log all messages, not just mail. You could also simply check on console 10 for postfix messages ( alt F10 ). You can use the mailq command to see if the mail is still hanging in the queue. Heiko Quoting James Kessler <jke...@gm...>: > Hello again, I have just initiated Postfix in Devil Linux. I've > walked through > the configuration files and believe I have set everything up > correctly. When I execute a simple mail command to test it, I am > able to fill out all categories such as subject, the message body > and so on. After I hit ctr+D it seems to send the message without > any errors. However, I am not actually receiving the email. I'm > thinking it's possible I am blocking it within my own firewall, > however I would like to setup my own Postfix Log to see if I am > getting any errors. It is to my understanding that Postfix logs all > failed and > successful deliveries write to a log file. The file, in my case is > in /var/log/mail, and I initiate it in the /etc/syslog.conf file. > However the problem is that after I un-comment the /var/log/mail > line in /etc/syslog.conf the mail log is not being generated after I > attempt to send mail. I have tried a Postfix Reload. Any thoughts? > Thanks again. -- James E. Kessler -- Regards Heiko Zuerker http://www.devil-linux.org ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. |
|
From: James K. <jke...@gm...> - 2010-09-02 17:10:39
|
Hello again, I have just initiated Postfix in Devil Linux. I've walked through the configuration files and believe I have set everything up correctly. When I execute a simple mail command to test it, I am able to fill out all categories such as subject, the message body and so on. After I hit ctr+D it seems to send the message without any errors. However, I am not actually receiving the email. I'm thinking it's possible I am blocking it within my own firewall, however I would like to setup my own Postfix Log to see if I am getting any errors. It is to my understanding that Postfix logs all failed and successful deliveries write to a log file. The file, in my case is in /var/log/mail, and I initiate it in the /etc/syslog.conf file. However the problem is that after I un-comment the /var/log/mail line in /etc/syslog.conf the mail log is not being generated after I attempt to send mail. I have tried a Postfix Reload. Any thoughts? Thanks again. -- James E. Kessler |
|
From: Heiko Z. <he...@zu...> - 2010-09-02 16:01:02
|
Hey, edit the file /etc/man.conf Search for "unlzma" and edit the line so it looks like this: .lzma /usr/bin/unlzma --memory=max -c -d This will fix the issue. I'll add it to CVS. Heiko Quoting "kor...@sb..." <kor...@sb...>: > 128Mb box got good-old 1.2.14 release and went to work :) > Here comes tests with 64mb box: > #free > total used free shared buffers cached > Mem: 54496 52132 2364 0 8600 34716 > -/+ buffers/cache: 8816 45680 > Swap: 0 0 0 > > #man man > > /usr/bin/unlzma: /usr/share/man/man1/man.1.lzma: Memory usage limit reached > /usr/bin/unlzma: Limit was 21 MiB, but 65 MiB would have been needed > fgets: No such file or directory > Error reading man page /usr/share/man/man1/man.1.lzma > /usr/bin/unlzma: /usr/man/man1/man.1.lzma: Memory usage limit reached > /usr/bin/unlzma: Limit was 21 MiB, but 65 MiB would have been needed > fgets: No such file or directory > Error reading man page /usr/man/man1/man.1.lzma > No manual entry for man > > > The same result was with 128Mb box, but limit was about 56MiB > I run no software. Not even sshd! > > On 09/02/10 16:29, Heiko Zuerker wrote: >> Hey, >> >> what else do you have running on this box? >> What's the output of the 'free' command? >> >> Heiko >> >> Quoting "kor...@sb..." <kor...@sb...>: >>> Hi! >>> >>> Seems like 1.4RC4-i686 requires more than 128 Mb RAM for lzma compression. >>> Unable to read man pages. >>> Sad... >>> >>> >>> >>> ------------------------------------------------------------------------------ >>> This SF.net Dev2Dev email is sponsored by: >>> >>> Show off your parallel programming skills. >>> Enter the Intel(R) Threading Challenge 2010. >>> http://p.sf.net/sfu/intel-thread-sfd >>> _______________________________________________ >>> Devil-linux-discuss mailing list >>> Dev...@li... >>> https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss >>> >> >> > > > ------------------------------------------------------------------------------ > This SF.net Dev2Dev email is sponsored by: > > Show off your parallel programming skills. > Enter the Intel(R) Threading Challenge 2010. > http://p.sf.net/sfu/intel-thread-sfd > _______________________________________________ > 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 message was sent using IMP, the Internet Messaging Program. |
|
From: <kor...@sb...> - 2010-09-02 14:39:33
|
128Mb box got good-old 1.2.14 release and went to work :)
Here comes tests with 64mb box:
#free
total used free shared buffers cached
Mem: 54496 52132 2364 0 8600 34716
-/+ buffers/cache: 8816 45680
Swap: 0 0 0
#man man
/usr/bin/unlzma: /usr/share/man/man1/man.1.lzma: Memory usage limit reached
/usr/bin/unlzma: Limit was 21 MiB, but 65 MiB would have been needed
fgets: No such file or directory
Error reading man page /usr/share/man/man1/man.1.lzma
/usr/bin/unlzma: /usr/man/man1/man.1.lzma: Memory usage limit reached
/usr/bin/unlzma: Limit was 21 MiB, but 65 MiB would have been needed
fgets: No such file or directory
Error reading man page /usr/man/man1/man.1.lzma
No manual entry for man
The same result was with 128Mb box, but limit was about 56MiB
I run no software. Not even sshd!
On 09/02/10 16:29, Heiko Zuerker wrote:
> Hey,
>
> what else do you have running on this box?
> What's the output of the 'free' command?
>
> Heiko
>
> Quoting "kor...@sb..." <kor...@sb...>:
>> Hi!
>>
>> Seems like 1.4RC4-i686 requires more than 128 Mb RAM for lzma compression.
>> Unable to read man pages.
>> Sad...
>>
>>
>>
>> ------------------------------------------------------------------------------
>> This SF.net Dev2Dev email is sponsored by:
>>
>> Show off your parallel programming skills.
>> Enter the Intel(R) Threading Challenge 2010.
>> http://p.sf.net/sfu/intel-thread-sfd
>> _______________________________________________
>> Devil-linux-discuss mailing list
>> Dev...@li...
>> https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss
>>
>
>
|
|
From: Heiko Z. <he...@zu...> - 2010-09-02 13:29:39
|
Hey, what else do you have running on this box? What's the output of the 'free' command? Heiko Quoting "kor...@sb..." <kor...@sb...>: > Hi! > > Seems like 1.4RC4-i686 requires more than 128 Mb RAM for lzma compression. > Unable to read man pages. > Sad... > > > > ------------------------------------------------------------------------------ > This SF.net Dev2Dev email is sponsored by: > > Show off your parallel programming skills. > Enter the Intel(R) Threading Challenge 2010. > http://p.sf.net/sfu/intel-thread-sfd > _______________________________________________ > 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 message was sent using IMP, the Internet Messaging Program. |
|
From: <kor...@sb...> - 2010-09-01 06:54:06
|
Hi! Seems like 1.4RC4-i686 requires more than 128 Mb RAM for lzma compression. Unable to read man pages. Sad... |
|
From: Heiko Z. <he...@zu...> - 2010-08-31 15:18:39
|
Not sure, this should work.... Heiko Quoting mailing dl2 <mai...@gm...>: > I use ESX 3.5 and in "VMware Infrastructure Client" I have: > > - Device Type > Datastore ISO file > - Mode (can not be changed) > Emulate IDE > - Virtual Device Node > IDE (0:0) > > Regards. > > 2010/8/31 Heiko Zuerker <he...@zu...>: >> What type interface did you select for the CDROM ? >> IDE works fine in my VMs. >> >> Heiko >> >> Quoting mailing dl2 <mai...@gm...>: >> >>> Hello, >>> >>> I am trying to use dl1.4rc5 on a Esx3.5. >>> >>> I have created a "Ubuntu Linux (32bits)" VM and I have added a cdrom >>> "Datastore ISO file" pointing to the dl1.4rc5 iso file. >>> >>> The VM boot on the CD (iso file) and stops after having found the >>> config on the floppy disk. >>> >>> It says "!!! Devil-Linux CD-ROM not found !!!" >>> >>> Knowing that a lot of you are using ESX, can you tell me your >>> workaround please. >>> >>> Regards. >>> >>> ------------------------------------------------------------------------------ >>> This SF.net Dev2Dev email is sponsored by: >>> >>> Show off your parallel programming skills. >>> Enter the Intel(R) Threading Challenge 2010. >>> http://p.sf.net/sfu/intel-thread-sfd >>> _______________________________________________ >>> 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 message was sent using IMP, the Internet Messaging Program. >> >> >> >> ------------------------------------------------------------------------------ >> This SF.net Dev2Dev email is sponsored by: >> >> Show off your parallel programming skills. >> Enter the Intel(R) Threading Challenge 2010. >> http://p.sf.net/sfu/intel-thread-sfd >> _______________________________________________ >> Devil-linux-discuss mailing list >> Dev...@li... >> https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss >> > > ------------------------------------------------------------------------------ > This SF.net Dev2Dev email is sponsored by: > > Show off your parallel programming skills. > Enter the Intel(R) Threading Challenge 2010. > http://p.sf.net/sfu/intel-thread-sfd > _______________________________________________ > 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 message was sent using IMP, the Internet Messaging Program. |
|
From: mailing d. <mai...@gm...> - 2010-08-31 15:06:18
|
I use ESX 3.5 and in "VMware Infrastructure Client" I have:
- Device Type
Datastore ISO file
- Mode (can not be changed)
Emulate IDE
- Virtual Device Node
IDE (0:0)
Regards.
2010/8/31 Heiko Zuerker <he...@zu...>:
> What type interface did you select for the CDROM ?
> IDE works fine in my VMs.
>
> Heiko
>
> Quoting mailing dl2 <mai...@gm...>:
>
>> Hello,
>>
>> I am trying to use dl1.4rc5 on a Esx3.5.
>>
>> I have created a "Ubuntu Linux (32bits)" VM and I have added a cdrom
>> "Datastore ISO file" pointing to the dl1.4rc5 iso file.
>>
>> The VM boot on the CD (iso file) and stops after having found the
>> config on the floppy disk.
>>
>> It says "!!! Devil-Linux CD-ROM not found !!!"
>>
>> Knowing that a lot of you are using ESX, can you tell me your
>> workaround please.
>>
>> Regards.
>>
>> ------------------------------------------------------------------------------
>> This SF.net Dev2Dev email is sponsored by:
>>
>> Show off your parallel programming skills.
>> Enter the Intel(R) Threading Challenge 2010.
>> http://p.sf.net/sfu/intel-thread-sfd
>> _______________________________________________
>> 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 message was sent using IMP, the Internet Messaging Program.
>
>
>
> ------------------------------------------------------------------------------
> This SF.net Dev2Dev email is sponsored by:
>
> Show off your parallel programming skills.
> Enter the Intel(R) Threading Challenge 2010.
> http://p.sf.net/sfu/intel-thread-sfd
> _______________________________________________
> Devil-linux-discuss mailing list
> Dev...@li...
> https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss
>
|
|
From: Heiko Z. <he...@zu...> - 2010-08-31 14:42:48
|
What type interface did you select for the CDROM ? IDE works fine in my VMs. Heiko Quoting mailing dl2 <mai...@gm...>: > Hello, > > I am trying to use dl1.4rc5 on a Esx3.5. > > I have created a "Ubuntu Linux (32bits)" VM and I have added a cdrom > "Datastore ISO file" pointing to the dl1.4rc5 iso file. > > The VM boot on the CD (iso file) and stops after having found the > config on the floppy disk. > > It says "!!! Devil-Linux CD-ROM not found !!!" > > Knowing that a lot of you are using ESX, can you tell me your > workaround please. > > Regards. > > ------------------------------------------------------------------------------ > This SF.net Dev2Dev email is sponsored by: > > Show off your parallel programming skills. > Enter the Intel(R) Threading Challenge 2010. > http://p.sf.net/sfu/intel-thread-sfd > _______________________________________________ > 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 message was sent using IMP, the Internet Messaging Program. |
|
From: mailing d. <mai...@gm...> - 2010-08-31 08:58:24
|
Hello, I am trying to use dl1.4rc5 on a Esx3.5. I have created a "Ubuntu Linux (32bits)" VM and I have added a cdrom "Datastore ISO file" pointing to the dl1.4rc5 iso file. The VM boot on the CD (iso file) and stops after having found the config on the floppy disk. It says "!!! Devil-Linux CD-ROM not found !!!" Knowing that a lot of you are using ESX, can you tell me your workaround please. Regards. |