Menu
▾
▴
devil-linux-develop — developer discussions
You can subscribe to this list here.
| 2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(55) |
Oct
(44) |
Nov
(156) |
Dec
(123) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2002 |
Jan
(130) |
Feb
(156) |
Mar
(162) |
Apr
(171) |
May
(97) |
Jun
(127) |
Jul
(58) |
Aug
(81) |
Sep
(86) |
Oct
(45) |
Nov
(41) |
Dec
(84) |
| 2003 |
Jan
(71) |
Feb
(87) |
Mar
(133) |
Apr
(152) |
May
(151) |
Jun
(232) |
Jul
(320) |
Aug
(237) |
Sep
(271) |
Oct
(536) |
Nov
(301) |
Dec
(393) |
| 2004 |
Jan
(393) |
Feb
(184) |
Mar
(314) |
Apr
(225) |
May
(139) |
Jun
(77) |
Jul
(87) |
Aug
(75) |
Sep
(139) |
Oct
(50) |
Nov
(8) |
Dec
(28) |
| 2005 |
Jan
(66) |
Feb
(63) |
Mar
(14) |
Apr
(14) |
May
(8) |
Jun
(23) |
Jul
(21) |
Aug
(6) |
Sep
(29) |
Oct
(55) |
Nov
(38) |
Dec
(8) |
| 2006 |
Jan
(5) |
Feb
(10) |
Mar
(1) |
Apr
(15) |
May
(32) |
Jun
(44) |
Jul
(11) |
Aug
(8) |
Sep
(9) |
Oct
(14) |
Nov
(4) |
Dec
(3) |
| 2007 |
Jan
(3) |
Feb
(3) |
Mar
(2) |
Apr
|
May
|
Jun
|
Jul
(35) |
Aug
(49) |
Sep
(8) |
Oct
(42) |
Nov
(44) |
Dec
(7) |
| 2008 |
Jan
(2) |
Feb
(7) |
Mar
(8) |
Apr
(80) |
May
(74) |
Jun
(29) |
Jul
(5) |
Aug
(7) |
Sep
(6) |
Oct
(1) |
Nov
|
Dec
|
| 2009 |
Jan
(8) |
Feb
(19) |
Mar
(3) |
Apr
(24) |
May
(22) |
Jun
(23) |
Jul
(8) |
Aug
(23) |
Sep
(8) |
Oct
(27) |
Nov
(52) |
Dec
(27) |
| 2010 |
Jan
(36) |
Feb
(29) |
Mar
(17) |
Apr
(28) |
May
(21) |
Jun
(4) |
Jul
|
Aug
(28) |
Sep
(18) |
Oct
(6) |
Nov
(34) |
Dec
(16) |
| 2011 |
Jan
(18) |
Feb
(12) |
Mar
|
Apr
|
May
(9) |
Jun
(1) |
Jul
(5) |
Aug
(5) |
Sep
(7) |
Oct
(16) |
Nov
(26) |
Dec
(17) |
| 2012 |
Jan
(6) |
Feb
(34) |
Mar
(52) |
Apr
(10) |
May
(3) |
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
(4) |
Nov
(1) |
Dec
(4) |
| 2013 |
Jan
(5) |
Feb
|
Mar
|
Apr
(5) |
May
(4) |
Jun
|
Jul
|
Aug
(14) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2014 |
Jan
|
Feb
(2) |
Mar
(5) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(3) |
Dec
(11) |
| 2015 |
Jan
(5) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
(1) |
Oct
(1) |
Nov
|
Dec
|
| 2016 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(2) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2017 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2018 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: SourceForge.net <no...@so...> - 2003-07-08 17:27:44
|
Bugs item #767922, was opened at 2003-07-08 12:27 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=410643&aid=767922&group_id=34096 Category: Configuration / Scripts Group: None Status: Open Resolution: None Priority: 5 Submitted By: Heiko Zuerker (smiley73) Assigned to: Nobody/Anonymous (nobody) Summary: jail scripts and libraries on CD media Initial Comment: the jail script will get problems when we have needed libs on the CD media. the script needs to figure out when it has to copy the files from CD, instead of just copying the symlink. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=410643&aid=767922&group_id=34096 |
|
From: Heiko Z. <hz...@pr...> - 2003-07-08 17:20:57
|
Howdy ! I'm just setting up a DL box and thought let's test the setup program. The only thing I found so far is this: - modules e100 and e1000 missing in network card module list OK and the software and config part needs more "help text". Otherwise: COOL ! cya Heko = |
|
From: Bruce S. <bw...@ar...> - 2003-07-08 14:59:23
|
> >> From now on everything which is in the directories: > >> $CDDIR/bin > >> $CDDIR/lib > >> $CDDIR/sbin > >> $CDDIR/usr/bin > >> $CDDIR/usr/lib > >> $CDDIR/usr/sbin > >> > >> will be linked into the appropriate folder. > > > >So this could make a lot of optional packages no longer optional? > > > >Instead of making them optional, just put them on the CD and be done > >with them? > > Hmmm, what do others think about this? When move to USB storage or flash > disks, this makes sense. I think it makes sense for _some_ packages now. Especially the interactive (not frequently used) packages. (lynx, wget, diff, ...) I'd much rather have them on CD so they are available when/if I need them, instead of loading them & having them take up memory ALL the time. > >I'm thinking of the H.323 gatekeeper I'm currently working on. > >The first thing it requires is "pwlib". I can just put the libraries > >in $CDDIR/lib (or $CDDIR/usr/lib), and I'm done. No need to make this > >package optional? > > > >It also needs OpenH323 lib. Same question. > > > >And finally the gatekeeper itself. Just put in $CDDIR[/usr]/[s]bin ??? > >No need to make optional? Even for compiling? > > You could do this, but I'm not sure if you want it. > Don't forgett that the CD has to start spinning everytime the binary or the > libs are accessed. It _might_ make sense for some daemons. If a simple binary/daemon is run during boot, it shouldn't have to go back to CD once it's running. I'm not sure about this gatekeeper, since it uses so many libs. - BS |
|
From: Heiko Z. <hz...@pr...> - 2003-07-08 14:43:19
|
On 07/08/2003 10:03:35 AM Bruce Smith wrote: >> From now on everything which is in the directories: >> $CDDIR/bin >> $CDDIR/lib >> $CDDIR/sbin >> $CDDIR/usr/bin >> $CDDIR/usr/lib >> $CDDIR/usr/sbin >> >> will be linked into the appropriate folder. > >So this could make a lot of optional packages no longer optional? > >Instead of making them optional, just put them on the CD and be done >with them? Hmmm, what do others think about this? When move to USB storage or flas= h disks, this makes sense. >I'm thinking of the H.323 gatekeeper I'm currently working on. >The first thing it requires is "pwlib". I can just put the libraries >in $CDDIR/lib (or $CDDIR/usr/lib), and I'm done. No need to make this= >package optional? > >It also needs OpenH323 lib. Same question. > >And finally the gatekeeper itself. Just put in $CDDIR[/usr]/[s]bin ??= ? >No need to make optional? Even for compiling? You could do this, but I'm not sure if you want it. Don't forgett that the CD has to start spinning everytime the binary or= the libs are accessed. Heiko = |
|
From: SourceForge.net <no...@so...> - 2003-07-08 14:41:04
|
Bugs item #767797, was opened at 2003-07-08 09:41 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=410643&aid=767797&group_id=34096 Category: Build System Group: None Status: Open Resolution: None Priority: 5 Submitted By: Heiko Zuerker (smiley73) Assigned to: Nobody/Anonymous (nobody) Summary: copy_lib needs to check new cddirs Initial Comment: script needs to check $CDDIR/lib and $CDDIR/usr/lib since libs can be there too ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=410643&aid=767797&group_id=34096 |
|
From: Bruce S. <bw...@ar...> - 2003-07-08 14:03:47
|
> From now on everything which is in the directories: > $CDDIR/bin > $CDDIR/lib > $CDDIR/sbin > $CDDIR/usr/bin > $CDDIR/usr/lib > $CDDIR/usr/sbin > > will be linked into the appropriate folder. So this could make a lot of optional packages no longer optional? Instead of making them optional, just put them on the CD and be done with them? I'm thinking of the H.323 gatekeeper I'm currently working on. The first thing it requires is "pwlib". I can just put the libraries in $CDDIR/lib (or $CDDIR/usr/lib), and I'm done. No need to make this package optional? It also needs OpenH323 lib. Same question. And finally the gatekeeper itself. Just put in $CDDIR[/usr]/[s]bin ??? No need to make optional? Even for compiling? - BS |
|
From: SourceForge.net <no...@so...> - 2003-07-08 13:59:38
|
Feature Requests item #767776, was opened at 2003-07-08 08:59 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=410646&aid=767776&group_id=34096 Category: Packages Group: None Status: Open Priority: 5 Submitted By: Heiko Zuerker (smiley73) Assigned to: Nobody/Anonymous (nobody) Summary: add expat and xml:parser perl module Initial Comment: - Expat library - Perl module XML::Parser ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=410646&aid=767776&group_id=34096 |
|
From: Bruce S. <bw...@ar...> - 2003-07-08 13:38:23
|
> I just checked in a few changes. > From now on everything which is in the directories: > $CDDIR/bin > $CDDIR/lib > $CDDIR/sbin > $CDDIR/usr/bin > $CDDIR/usr/lib > $CDDIR/usr/sbin > will be linked into the appropriate folder. Cool! > I already moved "vim" there, more will follow. Oh no, not VIM!!! Anything but VIM!!! I want my VIM to be FAST! (just kidding ;) I committed my changes to add bison (w/patch). So your next build should install bison in your local LFS and use it for compiling. - BS |
|
From: Heiko Z. <he...@zu...> - 2003-07-08 02:30:19
|
Hey guys, I just checked in a few changes. From now on everything which is in the directories: $CDDIR/bin $CDDIR/lib $CDDIR/sbin $CDDIR/usr/bin $CDDIR/usr/lib $CDDIR/usr/sbin will be linked into the appropriate folder. I already moved "vim" there, more will follow. cya Heiko |
|
From: <no...@fr...> - 2003-07-07 22:11:39
|
This email is to inform you about the release of version '1.1.42' of 'Distributed Checksum Clearinghouse' through freshmeat.net. All URLs and other useful information can be found at http://freshmeat.net/projects/dcc-source/ The changes in this release are as follows: Client handling of dead servers has been improved. Application layer keep-alives have been added to flooding. Project description: Distributed Checksum Clearinghouse (DCC) is a system of clients and servers that collect and count checksums related to mail messages. The counts can be used by SMTP servers and mail user agents to detect and reject bulk mail. DCC servers can exchange common checksums. The checksums include values that are "fuzzy", or constant across common variations in bulk messages. If you would like to cancel subscription to releases of this project, login to freshmeat.net and choose 'home' from the personal menubar at the top of the page. You'll be presented with a list of projects you're subscribed to in the right column, which you may cancel by highlighting the project in question and clicking the 'delete' button. Sincerely, freshmeat.net |
|
From: Bruce S. <bw...@ar...> - 2003-07-07 20:08:00
|
> >> There's not really a official Roadmap, however: > >> We have a "Feature Request" and a "Bug Tracking" list on > >sourceforge.net. > > > >Are the lists items still to do, or a complete list since 0.5? > >(some already appear to be done) > > I thought I only printed the open items. Just go to our sourceforge.net > project site, there you can see it under "Tracker'. I changed CIPE to "closed" (as you saw from the sourceforge email) since I added it awhile ago, and have been using it on my firewall ever since. :-) - BS |
|
From: SourceForge.net <no...@so...> - 2003-07-07 20:02:23
|
Feature Requests item #723169, was opened at 2003-04-17 11:14 Message generated for change (Settings changed) made by blubdog You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=410646&aid=723169&group_id=34096 Category: Packages Group: None >Status: Closed Priority: 5 Submitted By: Heiko Zuerker (smiley73) Assigned to: Nobody/Anonymous (nobody) Summary: add CIPE Initial Comment: http://sites.inka.de/sites/bigred/devel/cipe.html ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=410646&aid=723169&group_id=34096 |
|
From: Heiko Z. <hz...@pr...> - 2003-07-07 19:12:52
|
On 07/07/2003 02:55:27 PM Bruce Smith wrote: >> >> How about creating a package for the stable bison, extracting the= >> >patch >> >> from pwlib and letting the bison build script do the patching. >> > >> >OK, I'm looking into recompiling bison on the DL system. >> > >> >Using gcc as an example, I guess I should make & "make install" bis= on >> >during the build phase, right after gcc is compiled? (003bison)? > >I'll assume I'm correct there. > >> >During the install phase, should I make it an optional package to >> >install, like gcc? Or just skip it ... >> >> I don't think we need bison on the DL ISO, so I vote for skipping it= . > >Yeah! That makes it much easier! :-) > >I need to apply a patch to bison. >Which directory should I upload the patch file to? > >I thought I could find it, but I'm having trouble locating an example.= I can't look it up right now, but try a " grep -i patch build/scripts/*= ". You place the patch as a bz2 in build/src cya Heiko = |
|
From: Bruce S. <bw...@ar...> - 2003-07-07 19:06:00
|
> Which directory should I upload the patch file to? Never mind ... I see they are in the src directory. - BS |
|
From: Bruce S. <bw...@ar...> - 2003-07-07 18:55:39
|
> >> How about creating a package for the stable bison, extracting the > >patch > >> from pwlib and letting the bison build script do the patching. > > > >OK, I'm looking into recompiling bison on the DL system. > > > >Using gcc as an example, I guess I should make & "make install" bison > >during the build phase, right after gcc is compiled? (003bison)? I'll assume I'm correct there. > >During the install phase, should I make it an optional package to > >install, like gcc? Or just skip it ... > > I don't think we need bison on the DL ISO, so I vote for skipping it. Yeah! That makes it much easier! :-) I need to apply a patch to bison. Which directory should I upload the patch file to? I thought I could find it, but I'm having trouble locating an example. - BS |
|
From: <no...@fr...> - 2003-07-07 18:54:26
|
This email is to inform you about the release of version '2.14' of 'binutils' through freshmeat.net. All URLs and other useful information can be found at http://freshmeat.net/projects/binutils/ The changes in this release are as follows: Project description: GNU binutils work mostly behind the scenes of Linux development, largely because GNU make and the GCC frontend does so many things automatically. Utilities include: ld as nm objdump objcopy nm ar ranlib strip c filt size addr2line and dlltool. If you would like to cancel subscription to releases of this project, login to freshmeat.net and choose 'home' from the personal menubar at the top of the page. You'll be presented with a list of projects you're subscribed to in the right column, which you may cancel by highlighting the project in question and clicking the 'delete' button. Sincerely, freshmeat.net |
|
From: Heiko Z. <hz...@pr...> - 2003-07-07 18:49:44
|
On 07/07/2003 02:39:36 PM Bruce Smith wrote: >> How about creating a package for the stable bison, extracting the >patch >> from pwlib and letting the bison build script do the patching. > >OK, I'm looking into recompiling bison on the DL system. > >Using gcc as an example, I guess I should make & "make install" bison >during the build phase, right after gcc is compiled? (003bison)? > >During the install phase, should I make it an optional package to >install, like gcc? Or just skip it ... I don't think we need bison on the DL ISO, so I vote for skipping it. Heiko = |
|
From: Bruce S. <bw...@ar...> - 2003-07-07 18:39:51
|
> How about creating a package for the stable bison, extracting the patch > from pwlib and letting the bison build script do the patching. OK, I'm looking into recompiling bison on the DL system. Using gcc as an example, I guess I should make & "make install" bison during the build phase, right after gcc is compiled? (003bison)? During the install phase, should I make it an optional package to install, like gcc? Or just skip it ... - BS |
|
From: Friedrich L. <fl...@fl...> - 2003-07-07 17:48:53
|
francois dumont wrote: > Hi ! > > In devil 0.5, there used to be a /etc/init.d/routes; which was used if > $START_ROUTES was set to yes. > > In devil 0.6, routes has disappeared, mking more room for the ROUTING feature. > I can't get what uses it. Where is it launched from?? PLEASE DO NOT post normal usage questions on the developer mailinglist. Thanks. -- MfG / Regards Friedrich Lobenstock ____________________________________________________________________ Friedrich Lobenstock Linux Services Lobenstock URL: http://www.lsl.at/ Email: fl...@fl... ____________________________________________________________________ |
|
From: Friedrich L. <fl...@fl...> - 2003-07-07 17:47:35
|
francois dumont wrote: > Hi ! > > In devil 0.5, there used to be a /etc/init.d/routes; which was used if > $START_ROUTES was set to yes. > > In devil 0.6, routes has disappeared, mking more room for the ROUTING feature. > I can't get what uses it. Where is it launched from?? Please see /etc/sysconfig/nic/ifcfg-eth0.sample -- MfG / Regards Friedrich Lobenstock ____________________________________________________________________ Friedrich Lobenstock Linux Services Lobenstock URL: http://www.lsl.at/ Email: fl...@fl... ____________________________________________________________________ |
|
From: Heiko Z. <hz...@pr...> - 2003-07-07 17:32:53
|
On 07/07/2003 01:23:01 PM francois dumont wrote: >In devil 0.5, there used to be a /etc/init.d/routes; which was used if= >$START_ROUTES was set to yes. > >In devil 0.6, routes has disappeared, mking more room for the ROUTING >feature. >I can't get what uses it. Where is it launched from?? There was never a /etc/init.d/routes and no variable START_ROUTES ! You (or somebody else) must have added it to your 0.5 installation manually. In 0.6 you specify the route in the interface config file (ifcfg-*) and= it's started through the /etc/init.d/network script. Heiko = |
|
From: francois d. <Fra...@ir...> - 2003-07-07 17:26:08
|
Hi ! In devil 0.5, there used to be a /etc/init.d/routes; which was used if=20 $START_ROUTES was set to yes. In devil 0.6, routes has disappeared, mking more room for the ROUTING fea= ture.=20 I can't get what uses it. Where is it launched from??=20 ------------------- Fran=E7ois Dumont Stagiaire IRCAM |
|
From: <no...@fr...> - 2003-07-07 09:47:11
|
This email is to inform you about the release of version '1.1.7' of 'Linux Virtual Server' through freshmeat.net. All URLs and other useful information can be found at http://freshmeat.net/projects/linuxvirtualserver/ The changes in this release are as follows: Additional hash functions were included for IPVS connection entries to prevent hash attacks. The maximum value of the connection threshold was changed from 65535 to INT_MAX (2147483647), the default syncid was changed from 255 to 0, and ip_vs_sync.c was updated for Linux kernel 2.5.74. Some code was also tidied up. Project description: The Linux Virtual Server Project is an Open Source project to cluster many real servers together into a highly available, high-performance virtual server. The LVS handles connections from clients and passes them on the the real servers (so-called Layer 4 switching) and can virtualize almost any TCP or UDP service, like HTTP, HTTPS, NNTP, FTP, DNS, ssh, POP3, IMAP4, SMTP, etc. It is fully transparent to the client accessing the virtual service. If you would like to cancel subscription to releases of this project, login to freshmeat.net and choose 'home' from the personal menubar at the top of the page. You'll be presented with a list of projects you're subscribed to in the right column, which you may cancel by highlighting the project in question and clicking the 'delete' button. Sincerely, freshmeat.net |
|
From: <no...@fr...> - 2003-07-07 09:21:48
|
This email is to inform you about the release of version '2.0.13-20030706' of 'Postfix' through freshmeat.net. All URLs and other useful information can be found at http://freshmeat.net/projects/postfix/ The changes in this release are as follows: The server can now be configured to send all mail with a proxy server. This release added a new CIDR-based lookup table, support for !/pattern/ (negative matches) in PCRE lookup tables, a new receive_override_options parameter that eliminates the need for different cleanup service instances before and after an external content filter, and finer control over how long the SMTP daemon waits for completion of address verification probes. The LDAP client is now more robust. Project description: Postfix is an attempt to provide an alternative to the widely-used Sendmail program. Postfix attempts to be fast, easy to administer, and hopefully secure, while at the same time being sendmail compatible enough to not upset your users. If you would like to cancel subscription to releases of this project, login to freshmeat.net and choose 'home' from the personal menubar at the top of the page. You'll be presented with a list of projects you're subscribed to in the right column, which you may cancel by highlighting the project in question and clicking the 'delete' button. Sincerely, freshmeat.net |
|
From: Bruce S. <bw...@ar...> - 2003-07-07 01:14:42
|
> > Feel free to give it more than 2 minutes and let me know ... > > Not right now, No problem. Whenever. > it's time for bed because it's already close to 3 am here. Yikes! > > I'd really like a better way to probe for network cards. > > Maybe after 1.0 is released, I'll dig into some code to see how > > other distributions do it... > > Hey take it this way before you came there was not even the setup > script. The current script is a huge improvent anyways. I guess a lot > of beginners will thank you for this. So IMO the better network card > probing definitely can wait for 1.0. I suspect it can get very involved, and a good thing to put off. Speaking of network stuff, I plan on creating a 3-NIC firewall script (add DMZ rules to the 2-NIC script). Put me on the list for that. - BS |
35 messages has been excluded from this view by a project administrator.
