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: Heiko Z. <he...@zu...> - 2003-09-09 01:55:32
|
Heiko Zuerker wrote: > Dean Nedelman wrote: > >>> Hey, >>> >>> I just included Clam-AV in DL and now we need Amavis. >>> But there is: >>> Amavis >>> AmavisD >>> Amavis-NG >>> Amavis-New >>> >>> Does anybody have any experience with those? It needs to work together >>> with Postfix (of course) and must be stable/secure. >>> >> >> >> You may want to take a look at Sagator >> (http://analyzer.salstar.sk/sagator/). >> >> It works with Clam-AV, Postfix, and supports chroot! >> > > Sagator looks good but has one major problem: it uses a file config.py > which you have to modify. Due to this we can't use it, since the CD is > read-only. After taking another look at the package, I "fixed" the problem with symlinks. It's now included in DL, but still needs some afterwork and testing. Not to mention all those unzip,unrar,unwhatever tools, which have to be included. cya Heiko |
|
From: SourceForge.net <no...@so...> - 2003-09-09 01:47:49
|
Bugs item #802878, was opened at 2003-09-08 20:47 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=802878&group_id=34096 Category: Base System Group: None Status: Open Resolution: None Priority: 5 Submitted By: Heiko Zuerker (smiley73) Assigned to: Nobody/Anonymous (nobody) Summary: fix sagator init script Initial Comment: already in build/scripts/scripts/sagator , but needs to be changed for the DL environment ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=410643&aid=802878&group_id=34096 |
|
From: SourceForge.net <no...@so...> - 2003-09-09 00:53:35
|
Bugs item #802043, was opened at 2003-09-07 10:35 Message generated for change (Comment added) made by smiley73 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=410643&aid=802043&group_id=34096 Category: Base System Group: None >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Heiko Zuerker (smiley73) >Assigned to: Heiko Zuerker (smiley73) Summary: SCM USBAT-02 patch doesn't work with 2.4.22 Initial Comment: get new one or remove completely ---------------------------------------------------------------------- >Comment By: Heiko Zuerker (smiley73) Date: 2003-09-08 18:53 Message: Logged In: YES user_id=112133 disabled it ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=410643&aid=802043&group_id=34096 |
|
From: Heiko Z. <he...@zu...> - 2003-09-09 00:11:09
|
Dean Nedelman wrote: >>Hey, >> >>I just included Clam-AV in DL and now we need Amavis. >>But there is: >>Amavis >>AmavisD >>Amavis-NG >>Amavis-New >> >>Does anybody have any experience with those? It needs to work together >>with Postfix (of course) and must be stable/secure. >> > > > You may want to take a look at Sagator > (http://analyzer.salstar.sk/sagator/). > > It works with Clam-AV, Postfix, and supports chroot! > Sagator looks good but has one major problem: it uses a file config.py which you have to modify. Due to this we can't use it, since the CD is read-only. cya Heiko |
|
From: SourceForge.net <no...@so...> - 2003-09-08 00:37:55
|
Bugs item #795699, was opened at 2003-08-26 18:58 Message generated for change (Settings changed) made by smiley73 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=410643&aid=795699&group_id=34096 Category: Package Group: None >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Heiko Zuerker (smiley73) >Assigned to: Heiko Zuerker (smiley73) Summary: lspci problems with /usr/share/pci.ids Initial Comment: o lscpi should use /usr/share/pci.ids by default (according to the man page). Therefore, these two commands should be identical (according to the man page): "lscpi" and "lscpi -f /usr/share/pci.ids". However, they are not - the first command fails to use the /usr/share/pci.ids file and translate the numeric information. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=410643&aid=795699&group_id=34096 |
|
From: Heiko Z. <he...@zu...> - 2003-09-07 23:50:30
|
OOOPS I forgott to mention something. ;-) De-Select System/USBAT-2 Support in "make menuconfig". Heiko Bruce Smith wrote: >>make mrproper unpack build install iso >> >>....... > > > Forget the previous abort. I started with a fresh lfssystem and it got > farther, but still aborted: > > make -C usb > make[3]: Entering directory `/data/build/tmp/linux-2.4.22/drivers/usb' > make -C host > make[4]: Entering directory `/data/build/tmp/linux-2.4.22/drivers/usb/host' > make all_targets > make[5]: Entering directory `/data/build/tmp/linux-2.4.22/drivers/usb/host' > make[5]: Nothing to be done for `all_targets'. > make[5]: Leaving directory `/data/build/tmp/linux-2.4.22/drivers/usb/host' > make[4]: Leaving directory `/data/build/tmp/linux-2.4.22/drivers/usb/host' > make -C storage > make[4]: Entering directory `/data/build/tmp/linux-2.4.22/drivers/usb/storage' > make all_targets > make[5]: Entering directory `/data/build/tmp/linux-2.4.22/drivers/usb/storage' > gcc -D__KERNEL__ -I/data/build/tmp/linux-2.4.22/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -fomit-frame-pointer -fno-stack-protector -pipe -mpreferred-stack-boundary=2 -march=i686 -I../../scsi/ -nostdinc -iwithprefix include -DKBUILD_BASENAME=scsiglue -c -o scsiglue.o scsiglue.c > gcc -D__KERNEL__ -I/data/build/tmp/linux-2.4.22/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -fomit-frame-pointer -fno-stack-protector -pipe -mpreferred-stack-boundary=2 -march=i686 -I../../scsi/ -nostdinc -iwithprefix include -DKBUILD_BASENAME=protocol -c -o protocol.o protocol.c > gcc -D__KERNEL__ -I/data/build/tmp/linux-2.4.22/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -fomit-frame-pointer -fno-stack-protector -pipe -mpreferred-stack-boundary=2 -march=i686 -I../../scsi/ -nostdinc -iwithprefix include -DKBUILD_BASENAME=transport -c -o transport.o transport.c > gcc -D__KERNEL__ -I/data/build/tmp/linux-2.4.22/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -fomit-frame-pointer -fno-stack-protector -pipe -mpreferred-stack-boundary=2 -march=i686 -I../../scsi/ -nostdinc -iwithprefix include -DKBUILD_BASENAME=usb -c -o usb.o usb.c > In file included from usb.c:192: > unusual_devs.h:224: `US_FL_START_STOP' undeclared here (not in a function) > unusual_devs.h:224: initializer element is not constant > unusual_devs.h:224: (near initialization for `us_unusual_dev_list[26].flags') > unusual_devs.h:224: initializer element is not constant > unusual_devs.h:224: (near initialization for `us_unusual_dev_list[26]') > unusual_devs.h:232: initializer element is not constant > unusual_devs.h:232: (near initialization for `us_unusual_dev_list[27]') > unusual_devs.h:242: initializer element is not constant > unusual_devs.h:242: (near initialization for `us_unusual_dev_list[28]') > unusual_devs.h:249: initializer element is not constant > unusual_devs.h:249: (near initialization for `us_unusual_dev_list[29]') > unusual_devs.h:256: initializer element is not constant > unusual_devs.h:256: (near initialization for `us_unusual_dev_list[30]') > unusual_devs.h:263: initializer element is not constant > unusual_devs.h:263: (near initialization for `us_unusual_dev_list[31]') > unusual_devs.h:270: initializer element is not constant > unusual_devs.h:270: (near initialization for `us_unusual_dev_list[32]') > unusual_devs.h:277: initializer element is not constant > unusual_devs.h:277: (near initialization for `us_unusual_dev_list[33]') > unusual_devs.h:283: initializer element is not constant > unusual_devs.h:283: (near initialization for `us_unusual_dev_list[34]') > unusual_devs.h:289: initializer element is not constant > unusual_devs.h:289: (near initialization for `us_unusual_dev_list[35]') > unusual_devs.h:296: initializer element is not constant > unusual_devs.h:296: (near initialization for `us_unusual_dev_list[36]') > unusual_devs.h:302: initializer element is not constant > unusual_devs.h:302: (near initialization for `us_unusual_dev_list[37]') > unusual_devs.h:308: initializer element is not constant > unusual_devs.h:308: (near initialization for `us_unusual_dev_list[38]') > unusual_devs.h:313: initializer element is not constant > unusual_devs.h:313: (near initialization for `us_unusual_dev_list[39]') > unusual_devs.h:320: initializer element is not constant > unusual_devs.h:320: (near initialization for `us_unusual_dev_list[40]') > unusual_devs.h:326: initializer element is not constant > unusual_devs.h:326: (near initialization for `us_unusual_dev_list[41]') > unusual_devs.h:332: initializer element is not constant > unusual_devs.h:332: (near initialization for `us_unusual_dev_list[42]') > unusual_devs.h:338: initializer element is not constant > unusual_devs.h:338: (near initialization for `us_unusual_dev_list[43]') > unusual_devs.h:346: initializer element is not constant > unusual_devs.h:346: (near initialization for `us_unusual_dev_list[44]') > unusual_devs.h:354: initializer element is not constant > unusual_devs.h:354: (near initialization for `us_unusual_dev_list[45]') > unusual_devs.h:364: initializer element is not constant > unusual_devs.h:364: (near initialization for `us_unusual_dev_list[46]') > unusual_devs.h:377: initializer element is not constant > unusual_devs.h:377: (near initialization for `us_unusual_dev_list[47]') > unusual_devs.h:385: initializer element is not constant > unusual_devs.h:385: (near initialization for `us_unusual_dev_list[48]') > unusual_devs.h:390: initializer element is not constant > unusual_devs.h:390: (near initialization for `us_unusual_dev_list[49]') > unusual_devs.h:397: initializer element is not constant > unusual_devs.h:397: (near initialization for `us_unusual_dev_list[50]') > unusual_devs.h:403: initializer element is not constant > unusual_devs.h:403: (near initialization for `us_unusual_dev_list[51]') > unusual_devs.h:408: initializer element is not constant > unusual_devs.h:408: (near initialization for `us_unusual_dev_list[52]') > unusual_devs.h:414: initializer element is not constant > unusual_devs.h:414: (near initialization for `us_unusual_dev_list[53]') > unusual_devs.h:420: initializer element is not constant > unusual_devs.h:420: (near initialization for `us_unusual_dev_list[54]') > unusual_devs.h:426: initializer element is not constant > unusual_devs.h:426: (near initialization for `us_unusual_dev_list[55]') > unusual_devs.h:433: initializer element is not constant > unusual_devs.h:433: (near initialization for `us_unusual_dev_list[56]') > unusual_devs.h:440: initializer element is not constant > unusual_devs.h:440: (near initialization for `us_unusual_dev_list[57]') > unusual_devs.h:447: initializer element is not constant > unusual_devs.h:447: (near initialization for `us_unusual_dev_list[58]') > unusual_devs.h:453: initializer element is not constant > unusual_devs.h:453: (near initialization for `us_unusual_dev_list[59]') > unusual_devs.h:459: initializer element is not constant > unusual_devs.h:459: (near initialization for `us_unusual_dev_list[60]') > unusual_devs.h:467: initializer element is not constant > unusual_devs.h:467: (near initialization for `us_unusual_dev_list[61]') > unusual_devs.h:484: initializer element is not constant > unusual_devs.h:484: (near initialization for `us_unusual_dev_list[62]') > unusual_devs.h:490: initializer element is not constant > unusual_devs.h:490: (near initialization for `us_unusual_dev_list[63]') > unusual_devs.h:496: initializer element is not constant > unusual_devs.h:496: (near initialization for `us_unusual_dev_list[64]') > unusual_devs.h:502: initializer element is not constant > unusual_devs.h:502: (near initialization for `us_unusual_dev_list[65]') > unusual_devs.h:508: initializer element is not constant > unusual_devs.h:508: (near initialization for `us_unusual_dev_list[66]') > unusual_devs.h:517: initializer element is not constant > unusual_devs.h:517: (near initialization for `us_unusual_dev_list[67]') > unusual_devs.h:526: initializer element is not constant > unusual_devs.h:526: (near initialization for `us_unusual_dev_list[68]') > unusual_devs.h:539: initializer element is not constant > unusual_devs.h:539: (near initialization for `us_unusual_dev_list[69]') > unusual_devs.h:552: initializer element is not constant > unusual_devs.h:552: (near initialization for `us_unusual_dev_list[70]') > unusual_devs.h:559: initializer element is not constant > unusual_devs.h:559: (near initialization for `us_unusual_dev_list[71]') > unusual_devs.h:568: initializer element is not constant > unusual_devs.h:568: (near initialization for `us_unusual_dev_list[72]') > unusual_devs.h:575: initializer element is not constant > unusual_devs.h:575: (near initialization for `us_unusual_dev_list[73]') > unusual_devs.h:581: initializer element is not constant > unusual_devs.h:581: (near initialization for `us_unusual_dev_list[74]') > unusual_devs.h:587: initializer element is not constant > unusual_devs.h:587: (near initialization for `us_unusual_dev_list[75]') > unusual_devs.h:600: initializer element is not constant > unusual_devs.h:600: (near initialization for `us_unusual_dev_list[76]') > unusual_devs.h:607: initializer element is not constant > unusual_devs.h:607: (near initialization for `us_unusual_dev_list[77]') > unusual_devs.h:614: initializer element is not constant > unusual_devs.h:614: (near initialization for `us_unusual_dev_list[78]') > unusual_devs.h:625: initializer element is not constant > unusual_devs.h:625: (near initialization for `us_unusual_dev_list[79]') > unusual_devs.h:636: initializer element is not constant > unusual_devs.h:636: (near initialization for `us_unusual_dev_list[80]') > unusual_devs.h:643: initializer element is not constant > unusual_devs.h:643: (near initialization for `us_unusual_dev_list[81]') > usb.c:196: initializer element is not constant > usb.c:196: (near initialization for `us_unusual_dev_list[82]') > usb.c:198: initializer element is not constant > usb.c:198: (near initialization for `us_unusual_dev_list[83]') > usb.c:200: initializer element is not constant > usb.c:200: (near initialization for `us_unusual_dev_list[84]') > usb.c:202: initializer element is not constant > usb.c:202: (near initialization for `us_unusual_dev_list[85]') > usb.c:204: initializer element is not constant > usb.c:204: (near initialization for `us_unusual_dev_list[86]') > usb.c:206: initializer element is not constant > usb.c:206: (near initialization for `us_unusual_dev_list[87]') > usb.c:210: initializer element is not constant > usb.c:210: (near initialization for `us_unusual_dev_list[88]') > usb.c:212: initializer element is not constant > usb.c:212: (near initialization for `us_unusual_dev_list[89]') > usb.c:214: initializer element is not constant > usb.c:214: (near initialization for `us_unusual_dev_list[90]') > usb.c:216: initializer element is not constant > usb.c:216: (near initialization for `us_unusual_dev_list[91]') > usb.c:218: initializer element is not constant > usb.c:218: (near initialization for `us_unusual_dev_list[92]') > usb.c:220: initializer element is not constant > usb.c:220: (near initialization for `us_unusual_dev_list[93]') > usb.c:224: initializer element is not constant > usb.c:224: (near initialization for `us_unusual_dev_list[94]') > usb.c:226: initializer element is not constant > usb.c:226: (near initialization for `us_unusual_dev_list[95]') > usb.c:228: initializer element is not constant > usb.c:228: (near initialization for `us_unusual_dev_list[96]') > usb.c:230: initializer element is not constant > usb.c:230: (near initialization for `us_unusual_dev_list[97]') > usb.c:232: initializer element is not constant > usb.c:232: (near initialization for `us_unusual_dev_list[98]') > usb.c:234: initializer element is not constant > usb.c:234: (near initialization for `us_unusual_dev_list[99]') > usb.c:237: initializer element is not constant > usb.c:237: (near initialization for `us_unusual_dev_list[100]') > zio_cf.h:34: warning: `drive' defined but not used > make[5]: *** [usb.o] Error 1 > make[5]: Leaving directory > `/data/build/tmp/linux-2.4.22/drivers/usb/storage' > make[4]: *** [first_rule] Error 2 > make[4]: Leaving directory > `/data/build/tmp/linux-2.4.22/drivers/usb/storage' > make[3]: *** [_subdir_storage] Error 2 > make[3]: Leaving directory `/data/build/tmp/linux-2.4.22/drivers/usb' > make[2]: *** [_subdir_usb] Error 2 > make[2]: Leaving directory `/data/build/tmp/linux-2.4.22/drivers' > make[1]: *** [_dir_drivers] Error 2 > make[1]: Leaving directory `/data/build/tmp/linux-2.4.22' > ERROR > /data/build/scripts/linux build failed > make: *** [build] Error 1 |
|
From: Heiko Z. <he...@zu...> - 2003-09-07 23:46:23
|
Bruce Smith wrote: >>I just checked in the changes to get DL working with the new kernel. >>The workaround for iproute/iputils is, that we use the kernel includes >>from 2.4.21 until a patch is available. > > > make mrproper unpack build install iso > > ....... > > ranlib libbackend.a > stage1/xgcc -Bstage1/ -B/usr/i686-pc-linux-gnu/bin/ -DIN_GCC -g -O2 > -W -Wall > -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wtraditional > -pedantic -Wno-long-long -DHAVE_CONFIG_H -o cc1 \ > c-parse.o c-lang.o attribs.o c-errors.o c-lex.o c-pragma.o > c-decl.o c-typeck.o c-convert.o c-aux-info.o c-common.o c-format.o > c-semantics.o c-objc-common.o libcpp.a main.o libbackend.a > ../libiberty/libiberty.a > ../libiberty/libiberty.a(md5.o)(.text+0x123): In function `md5_stream': > ../../gcc-3.2.3/libiberty/md5.c:135: undefined reference to `__guard' > ../libiberty/libiberty.a(md5.o)(.text+0x1fb):../../gcc-3.2.3/libiberty/md5.c:182: undefined reference to `__guard' > ../libiberty/libiberty.a(md5.o)(.text+0x23c):../../gcc-3.2.3/libiberty/md5.c:162: undefined reference to `__stack_smash_handler' > ../libiberty/libiberty.a(md5.o)(.text+0x24d): In function `md5_buffer': > ../../gcc-3.2.3/libiberty/md5.c:193: undefined reference to `__guard' > ../libiberty/libiberty.a(md5.o)(.text+0x28f):../../gcc-3.2.3/libiberty/md5.c:204: undefined reference to `__guard' > ../libiberty/libiberty.a(md5.o)(.text+0x2ae):../../gcc-3.2.3/libiberty/md5.c:204: undefined reference to `__stack_smash_handler' > collect2: ld returned 1 exit status > make[3]: *** [cc1] Error 1 > make[3]: Leaving directory `/data/build/tmp/gcc-build/gcc' > make[2]: *** [stage2_build] Error 2 > make[2]: Leaving directory `/data/build/tmp/gcc-build/gcc' > make[1]: *** [bootstrap] Error 2 > make[1]: Leaving directory `/data/build/tmp/gcc-build' > ERROR > /data/build/scripts/gcc build failed > make: *** [build] Error 1 > Use a clean LFS system. I did it this morning and the compile went through without any problems. cya Heiko |
|
From: Heiko Z. <he...@zu...> - 2003-09-07 23:46:22
|
Bruce Smith wrote: >>I just checked in the changes to get DL working with the new kernel. > > > And I fixed it (again), so you can download all the sources! ;-) > > (before my fix:) > mirror: Access failed: 550 man-1.5m2.tar.bz2: Permission denied > mirror: Access failed: 550 util-linux-2.12.tar.gz: Permission denied > That's not fair! I actually ran a update_src to see if all files are downloaded and it worked ! grrrrr cya Heiko |
|
From: Bruce S. <bw...@ar...> - 2003-09-07 23:34:30
|
> make mrproper unpack build install iso > > ....... Forget the previous abort. I started with a fresh lfssystem and it got farther, but still aborted: make -C usb make[3]: Entering directory `/data/build/tmp/linux-2.4.22/drivers/usb' make -C host make[4]: Entering directory `/data/build/tmp/linux-2.4.22/drivers/usb/host' make all_targets make[5]: Entering directory `/data/build/tmp/linux-2.4.22/drivers/usb/host' make[5]: Nothing to be done for `all_targets'. make[5]: Leaving directory `/data/build/tmp/linux-2.4.22/drivers/usb/host' make[4]: Leaving directory `/data/build/tmp/linux-2.4.22/drivers/usb/host' make -C storage make[4]: Entering directory `/data/build/tmp/linux-2.4.22/drivers/usb/storage' make all_targets make[5]: Entering directory `/data/build/tmp/linux-2.4.22/drivers/usb/storage' gcc -D__KERNEL__ -I/data/build/tmp/linux-2.4.22/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -fomit-frame-pointer -fno-stack-protector -pipe -mpreferred-stack-boundary=2 -march=i686 -I../../scsi/ -nostdinc -iwithprefix include -DKBUILD_BASENAME=scsiglue -c -o scsiglue.o scsiglue.c gcc -D__KERNEL__ -I/data/build/tmp/linux-2.4.22/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -fomit-frame-pointer -fno-stack-protector -pipe -mpreferred-stack-boundary=2 -march=i686 -I../../scsi/ -nostdinc -iwithprefix include -DKBUILD_BASENAME=protocol -c -o protocol.o protocol.c gcc -D__KERNEL__ -I/data/build/tmp/linux-2.4.22/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -fomit-frame-pointer -fno-stack-protector -pipe -mpreferred-stack-boundary=2 -march=i686 -I../../scsi/ -nostdinc -iwithprefix include -DKBUILD_BASENAME=transport -c -o transport.o transport.c gcc -D__KERNEL__ -I/data/build/tmp/linux-2.4.22/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -fomit-frame-pointer -fno-stack-protector -pipe -mpreferred-stack-boundary=2 -march=i686 -I../../scsi/ -nostdinc -iwithprefix include -DKBUILD_BASENAME=usb -c -o usb.o usb.c In file included from usb.c:192: unusual_devs.h:224: `US_FL_START_STOP' undeclared here (not in a function) unusual_devs.h:224: initializer element is not constant unusual_devs.h:224: (near initialization for `us_unusual_dev_list[26].flags') unusual_devs.h:224: initializer element is not constant unusual_devs.h:224: (near initialization for `us_unusual_dev_list[26]') unusual_devs.h:232: initializer element is not constant unusual_devs.h:232: (near initialization for `us_unusual_dev_list[27]') unusual_devs.h:242: initializer element is not constant unusual_devs.h:242: (near initialization for `us_unusual_dev_list[28]') unusual_devs.h:249: initializer element is not constant unusual_devs.h:249: (near initialization for `us_unusual_dev_list[29]') unusual_devs.h:256: initializer element is not constant unusual_devs.h:256: (near initialization for `us_unusual_dev_list[30]') unusual_devs.h:263: initializer element is not constant unusual_devs.h:263: (near initialization for `us_unusual_dev_list[31]') unusual_devs.h:270: initializer element is not constant unusual_devs.h:270: (near initialization for `us_unusual_dev_list[32]') unusual_devs.h:277: initializer element is not constant unusual_devs.h:277: (near initialization for `us_unusual_dev_list[33]') unusual_devs.h:283: initializer element is not constant unusual_devs.h:283: (near initialization for `us_unusual_dev_list[34]') unusual_devs.h:289: initializer element is not constant unusual_devs.h:289: (near initialization for `us_unusual_dev_list[35]') unusual_devs.h:296: initializer element is not constant unusual_devs.h:296: (near initialization for `us_unusual_dev_list[36]') unusual_devs.h:302: initializer element is not constant unusual_devs.h:302: (near initialization for `us_unusual_dev_list[37]') unusual_devs.h:308: initializer element is not constant unusual_devs.h:308: (near initialization for `us_unusual_dev_list[38]') unusual_devs.h:313: initializer element is not constant unusual_devs.h:313: (near initialization for `us_unusual_dev_list[39]') unusual_devs.h:320: initializer element is not constant unusual_devs.h:320: (near initialization for `us_unusual_dev_list[40]') unusual_devs.h:326: initializer element is not constant unusual_devs.h:326: (near initialization for `us_unusual_dev_list[41]') unusual_devs.h:332: initializer element is not constant unusual_devs.h:332: (near initialization for `us_unusual_dev_list[42]') unusual_devs.h:338: initializer element is not constant unusual_devs.h:338: (near initialization for `us_unusual_dev_list[43]') unusual_devs.h:346: initializer element is not constant unusual_devs.h:346: (near initialization for `us_unusual_dev_list[44]') unusual_devs.h:354: initializer element is not constant unusual_devs.h:354: (near initialization for `us_unusual_dev_list[45]') unusual_devs.h:364: initializer element is not constant unusual_devs.h:364: (near initialization for `us_unusual_dev_list[46]') unusual_devs.h:377: initializer element is not constant unusual_devs.h:377: (near initialization for `us_unusual_dev_list[47]') unusual_devs.h:385: initializer element is not constant unusual_devs.h:385: (near initialization for `us_unusual_dev_list[48]') unusual_devs.h:390: initializer element is not constant unusual_devs.h:390: (near initialization for `us_unusual_dev_list[49]') unusual_devs.h:397: initializer element is not constant unusual_devs.h:397: (near initialization for `us_unusual_dev_list[50]') unusual_devs.h:403: initializer element is not constant unusual_devs.h:403: (near initialization for `us_unusual_dev_list[51]') unusual_devs.h:408: initializer element is not constant unusual_devs.h:408: (near initialization for `us_unusual_dev_list[52]') unusual_devs.h:414: initializer element is not constant unusual_devs.h:414: (near initialization for `us_unusual_dev_list[53]') unusual_devs.h:420: initializer element is not constant unusual_devs.h:420: (near initialization for `us_unusual_dev_list[54]') unusual_devs.h:426: initializer element is not constant unusual_devs.h:426: (near initialization for `us_unusual_dev_list[55]') unusual_devs.h:433: initializer element is not constant unusual_devs.h:433: (near initialization for `us_unusual_dev_list[56]') unusual_devs.h:440: initializer element is not constant unusual_devs.h:440: (near initialization for `us_unusual_dev_list[57]') unusual_devs.h:447: initializer element is not constant unusual_devs.h:447: (near initialization for `us_unusual_dev_list[58]') unusual_devs.h:453: initializer element is not constant unusual_devs.h:453: (near initialization for `us_unusual_dev_list[59]') unusual_devs.h:459: initializer element is not constant unusual_devs.h:459: (near initialization for `us_unusual_dev_list[60]') unusual_devs.h:467: initializer element is not constant unusual_devs.h:467: (near initialization for `us_unusual_dev_list[61]') unusual_devs.h:484: initializer element is not constant unusual_devs.h:484: (near initialization for `us_unusual_dev_list[62]') unusual_devs.h:490: initializer element is not constant unusual_devs.h:490: (near initialization for `us_unusual_dev_list[63]') unusual_devs.h:496: initializer element is not constant unusual_devs.h:496: (near initialization for `us_unusual_dev_list[64]') unusual_devs.h:502: initializer element is not constant unusual_devs.h:502: (near initialization for `us_unusual_dev_list[65]') unusual_devs.h:508: initializer element is not constant unusual_devs.h:508: (near initialization for `us_unusual_dev_list[66]') unusual_devs.h:517: initializer element is not constant unusual_devs.h:517: (near initialization for `us_unusual_dev_list[67]') unusual_devs.h:526: initializer element is not constant unusual_devs.h:526: (near initialization for `us_unusual_dev_list[68]') unusual_devs.h:539: initializer element is not constant unusual_devs.h:539: (near initialization for `us_unusual_dev_list[69]') unusual_devs.h:552: initializer element is not constant unusual_devs.h:552: (near initialization for `us_unusual_dev_list[70]') unusual_devs.h:559: initializer element is not constant unusual_devs.h:559: (near initialization for `us_unusual_dev_list[71]') unusual_devs.h:568: initializer element is not constant unusual_devs.h:568: (near initialization for `us_unusual_dev_list[72]') unusual_devs.h:575: initializer element is not constant unusual_devs.h:575: (near initialization for `us_unusual_dev_list[73]') unusual_devs.h:581: initializer element is not constant unusual_devs.h:581: (near initialization for `us_unusual_dev_list[74]') unusual_devs.h:587: initializer element is not constant unusual_devs.h:587: (near initialization for `us_unusual_dev_list[75]') unusual_devs.h:600: initializer element is not constant unusual_devs.h:600: (near initialization for `us_unusual_dev_list[76]') unusual_devs.h:607: initializer element is not constant unusual_devs.h:607: (near initialization for `us_unusual_dev_list[77]') unusual_devs.h:614: initializer element is not constant unusual_devs.h:614: (near initialization for `us_unusual_dev_list[78]') unusual_devs.h:625: initializer element is not constant unusual_devs.h:625: (near initialization for `us_unusual_dev_list[79]') unusual_devs.h:636: initializer element is not constant unusual_devs.h:636: (near initialization for `us_unusual_dev_list[80]') unusual_devs.h:643: initializer element is not constant unusual_devs.h:643: (near initialization for `us_unusual_dev_list[81]') usb.c:196: initializer element is not constant usb.c:196: (near initialization for `us_unusual_dev_list[82]') usb.c:198: initializer element is not constant usb.c:198: (near initialization for `us_unusual_dev_list[83]') usb.c:200: initializer element is not constant usb.c:200: (near initialization for `us_unusual_dev_list[84]') usb.c:202: initializer element is not constant usb.c:202: (near initialization for `us_unusual_dev_list[85]') usb.c:204: initializer element is not constant usb.c:204: (near initialization for `us_unusual_dev_list[86]') usb.c:206: initializer element is not constant usb.c:206: (near initialization for `us_unusual_dev_list[87]') usb.c:210: initializer element is not constant usb.c:210: (near initialization for `us_unusual_dev_list[88]') usb.c:212: initializer element is not constant usb.c:212: (near initialization for `us_unusual_dev_list[89]') usb.c:214: initializer element is not constant usb.c:214: (near initialization for `us_unusual_dev_list[90]') usb.c:216: initializer element is not constant usb.c:216: (near initialization for `us_unusual_dev_list[91]') usb.c:218: initializer element is not constant usb.c:218: (near initialization for `us_unusual_dev_list[92]') usb.c:220: initializer element is not constant usb.c:220: (near initialization for `us_unusual_dev_list[93]') usb.c:224: initializer element is not constant usb.c:224: (near initialization for `us_unusual_dev_list[94]') usb.c:226: initializer element is not constant usb.c:226: (near initialization for `us_unusual_dev_list[95]') usb.c:228: initializer element is not constant usb.c:228: (near initialization for `us_unusual_dev_list[96]') usb.c:230: initializer element is not constant usb.c:230: (near initialization for `us_unusual_dev_list[97]') usb.c:232: initializer element is not constant usb.c:232: (near initialization for `us_unusual_dev_list[98]') usb.c:234: initializer element is not constant usb.c:234: (near initialization for `us_unusual_dev_list[99]') usb.c:237: initializer element is not constant usb.c:237: (near initialization for `us_unusual_dev_list[100]') zio_cf.h:34: warning: `drive' defined but not used make[5]: *** [usb.o] Error 1 make[5]: Leaving directory `/data/build/tmp/linux-2.4.22/drivers/usb/storage' make[4]: *** [first_rule] Error 2 make[4]: Leaving directory `/data/build/tmp/linux-2.4.22/drivers/usb/storage' make[3]: *** [_subdir_storage] Error 2 make[3]: Leaving directory `/data/build/tmp/linux-2.4.22/drivers/usb' make[2]: *** [_subdir_usb] Error 2 make[2]: Leaving directory `/data/build/tmp/linux-2.4.22/drivers' make[1]: *** [_dir_drivers] Error 2 make[1]: Leaving directory `/data/build/tmp/linux-2.4.22' ERROR /data/build/scripts/linux build failed make: *** [build] Error 1 |
|
From: Bruce S. <bw...@ar...> - 2003-09-07 17:54:35
|
> I just checked in the changes to get DL working with the new kernel.
> The workaround for iproute/iputils is, that we use the kernel includes
> from 2.4.21 until a patch is available.
make mrproper unpack build install iso
.......
ranlib libbackend.a
stage1/xgcc -Bstage1/ -B/usr/i686-pc-linux-gnu/bin/ -DIN_GCC -g -O2
-W -Wall
-Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wtraditional
-pedantic -Wno-long-long -DHAVE_CONFIG_H -o cc1 \
c-parse.o c-lang.o attribs.o c-errors.o c-lex.o c-pragma.o
c-decl.o c-typeck.o c-convert.o c-aux-info.o c-common.o c-format.o
c-semantics.o c-objc-common.o libcpp.a main.o libbackend.a
../libiberty/libiberty.a
../libiberty/libiberty.a(md5.o)(.text+0x123): In function `md5_stream':
../../gcc-3.2.3/libiberty/md5.c:135: undefined reference to `__guard'
../libiberty/libiberty.a(md5.o)(.text+0x1fb):../../gcc-3.2.3/libiberty/md5.c:182: undefined reference to `__guard'
../libiberty/libiberty.a(md5.o)(.text+0x23c):../../gcc-3.2.3/libiberty/md5.c:162: undefined reference to `__stack_smash_handler'
../libiberty/libiberty.a(md5.o)(.text+0x24d): In function `md5_buffer':
../../gcc-3.2.3/libiberty/md5.c:193: undefined reference to `__guard'
../libiberty/libiberty.a(md5.o)(.text+0x28f):../../gcc-3.2.3/libiberty/md5.c:204: undefined reference to `__guard'
../libiberty/libiberty.a(md5.o)(.text+0x2ae):../../gcc-3.2.3/libiberty/md5.c:204: undefined reference to `__stack_smash_handler'
collect2: ld returned 1 exit status
make[3]: *** [cc1] Error 1
make[3]: Leaving directory `/data/build/tmp/gcc-build/gcc'
make[2]: *** [stage2_build] Error 2
make[2]: Leaving directory `/data/build/tmp/gcc-build/gcc'
make[1]: *** [bootstrap] Error 2
make[1]: Leaving directory `/data/build/tmp/gcc-build'
ERROR
/data/build/scripts/gcc build failed
make: *** [build] Error 1
|
|
From: Bruce S. <bw...@ar...> - 2003-09-07 17:09:34
|
> I just checked in the changes to get DL working with the new kernel. And I fixed it (again), so you can download all the sources! ;-) (before my fix:) mirror: Access failed: 550 man-1.5m2.tar.bz2: Permission denied mirror: Access failed: 550 util-linux-2.12.tar.gz: Permission denied - B |
|
From: SourceForge.net <no...@so...> - 2003-09-07 15:35:44
|
Bugs item #802043, was opened at 2003-09-07 10:35 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=802043&group_id=34096 Category: Base System Group: None Status: Open Resolution: None Priority: 5 Submitted By: Heiko Zuerker (smiley73) Assigned to: Nobody/Anonymous (nobody) Summary: SCM USBAT-02 patch doesn't work with 2.4.22 Initial Comment: get new one or remove completely ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=410643&aid=802043&group_id=34096 |
|
From: SourceForge.net <no...@so...> - 2003-09-07 15:28:58
|
Bugs item #799388, was opened at 2003-09-02 15:45 Message generated for change (Settings changed) made by smiley73 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=410643&aid=799388&group_id=34096 Category: Base System Group: None >Status: Closed >Resolution: Fixed Priority: 7 Submitted By: Heiko Zuerker (smiley73) >Assigned to: Heiko Zuerker (smiley73) Summary: iputils doesn't compile with 2.4.22 Initial Comment: just doesn't compile... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=410643&aid=799388&group_id=34096 |
|
From: SourceForge.net <no...@so...> - 2003-09-07 15:28:40
|
Bugs item #799387, was opened at 2003-09-02 15:44 Message generated for change (Settings changed) made by smiley73 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=410643&aid=799387&group_id=34096 Category: Base System Group: None >Status: Closed >Resolution: Fixed Priority: 7 Submitted By: Heiko Zuerker (smiley73) >Assigned to: Heiko Zuerker (smiley73) Summary: iproute2 doesn't compile with 2.4.22 Initial Comment: just doesn't compile... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=410643&aid=799387&group_id=34096 |
|
From: Heiko Z. <he...@zu...> - 2003-09-07 15:17:49
|
Hey, I just checked in the changes to get DL working with the new kernel. The workaround for iproute/iputils is, that we use the kernel includes from 2.4.21 until a patch is available. cya Heiko |
|
From: SourceForge.net <no...@so...> - 2003-09-07 13:59:56
|
Bugs item #759801, was opened at 2003-06-24 08:28 Message generated for change (Comment added) made by smiley73 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=410643&aid=759801&group_id=34096 Category: Configuration / Scripts Group: None >Status: Deleted >Resolution: Wont Fix Priority: 5 Submitted By: Heiko Zuerker (smiley73) >Assigned to: Heiko Zuerker (smiley73) Summary: ext2/3 warning in initrd Initial Comment: >o When it went to unpack the floppy, it first checked for ext3, then >ext2, >then it mounted the floppy. Has the rules changed and are we supposed >to >use ext3/ext2 formatted floppies? [I am using FAT formatted floppies.] HIDE this warning. ---------------------------------------------------------------------- >Comment By: Heiko Zuerker (smiley73) Date: 2003-09-07 08:59 Message: Logged In: YES user_id=112133 Those message seem to come out of the Kernel, we can't get rid of them. ---------------------------------------------------------------------- Comment By: Heiko Zuerker (smiley73) Date: 2003-08-26 19:58 Message: Logged In: YES user_id=112133 a utility to detect and use the correct filesystem would solve this problem or a patch which get's rid of that stupid warning message ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=410643&aid=759801&group_id=34096 |
|
From: <no...@fr...> - 2003-09-07 04:54:20
|
This email is to inform you about the release of version '2.12' of 'util-linux' through freshmeat.net. All URLs and other useful information can be found at http://freshmeat.net/projects/util-linux/ The changes in this release are as follows: This version adds a "-p" option for losetup and mount, an SGI layout fix on fdisk, recognition of some PCDOS floppies on mount, and in "umount name", it now first tries to interpret "name" as a mount point. Project description: Util-linux is a suite of essential utilities for any Linux system. Its primary audience is system integrators and DIY Linux hackers. Util-linux is attempting to be portable, but the only platform it has been tested much on is Linux i386. It contains the following programs: agetty arch blockdev cal cfdisk chfn chkdupexe chsh clear col colcrt colrm column ctrlaltdel cytune ddate dmesg elvtune fastboot fasthalt fdformat fdisk fsck.cramfs fsck.minix getopt halt hexdump hwclock initctl ipcrm ipcs isosize kill last line logger login look mcookie mesg mkfs mkfs.bfs mkfs.cramfs mkfs.minix mkswap more mount namei need passwd pg pivot_root ramsize raw rdev readprofile reboot rename renice rescuept reset rev rootflags script setfdprm setsid setterm sfdisk shutdown simpleinit sln swapoff swapon tunelp ul umount vidmode vipw wall whereis write. 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-09-07 04:48:25
|
This email is to inform you about the release of version '1.5m2' of 'man' through freshmeat.net. All URLs and other useful information can be found at http://freshmeat.net/projects/man/ The changes in this release are as follows: In this version, Greek man pages and messages were added. makewhatis was fixed. Project description: The man page suite, including man, apropos, and whatis consists of programs that are used to read most of the documentation available on a Linux system. The whatis and apropos programs can be used to find documentation related to a particular subject. 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: Dean N. <di...@ti...> - 2003-09-07 04:10:56
|
>Hey, > >I just included Clam-AV in DL and now we need Amavis. >But there is: >Amavis >AmavisD >Amavis-NG >Amavis-New > >Does anybody have any experience with those? It needs to work together >with Postfix (of course) and must be stable/secure. > You may want to take a look at Sagator (http://analyzer.salstar.sk/sagator/). It works with Clam-AV, Postfix, and supports chroot! Dean Nedelman TimeLord Consulting |
|
From: Heiko Z. <he...@zu...> - 2003-09-07 02:10:29
|
Hey, I just included Clam-AV in DL and now we need Amavis. But there is: Amavis AmavisD Amavis-NG Amavis-New Does anybody have any experience with those? It needs to work together with Postfix (of course) and must be stable/secure. cya Heiko |
|
From: SourceForge.net <no...@so...> - 2003-09-06 15:02:41
|
Feature Requests item #799178, was opened at 2003-09-02 09:59 Message generated for change (Settings changed) made by smiley73 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=410646&aid=799178&group_id=34096 Category: Packages Group: None >Status: Closed Priority: 5 Submitted By: Heiko Zuerker (smiley73) >Assigned to: Heiko Zuerker (smiley73) Summary: add clamav Initial Comment: http://clamav.elektrapro.com/ What is Clam AntiVirus ? Clam AntiVirus is an anti-virus toolkit for UNIX. The main purpose of this software is the integration with mail servers (attachment scanning). The package provides a flexible and scalable multi-threaded daemon, a command line scanner, and a tool for automatic updating via Internet. The programs are based on a shared library distributed with the Clam AntiVirus package, which you can use with your own software. The virus database is based on the virus database from OpenAntiVirus, but contains additional signatures (including signatures for popular polymorphic viruses, too) and is KEPT UP TO DATE. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=410646&aid=799178&group_id=34096 |
|
From: SourceForge.net <no...@so...> - 2003-09-06 02:00:28
|
Bugs item #795704, was opened at 2003-08-26 19:13 Message generated for change (Settings changed) made by smiley73 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=410643&aid=795704&group_id=34096 Category: Base System Group: None >Status: Deleted Resolution: Rejected Priority: 5 Submitted By: Heiko Zuerker (smiley73) Assigned to: Nobody/Anonymous (nobody) Summary: save-config doesn't work with 16 MB Initial Comment: Bruce Smith wrote: > I had a weird thing this morning while running save-config, where it > aborted in a very strange way (in VMware). To make a long story short, > after a lot of traces, manual "tar" commands, and head beating, I > figured out it was because my VMware was set to 16MB of memory. > > This is a fresh boot with a blank floppy. It seems like there is enough > memory in 16MB to run tar, but when the "j" option kicks in, bzip2 loads > and aborts tar. > > I increased my memory in VMware to 32MB and save-config runs fine there > (except for the "diff" part which I don't care about). > > We might want NOT want to advertise DL will run in 16MB of memory, if > people cannot save their configuration on that size machine. The other > option would be to use some busybox commands in save-config instead of > the standard ones ... (or not :) Damned. Of course that was a function I didn't test. It's worth a try to use just for this function the busybox tar. Can you take care of it? I have too many other things. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=410643&aid=795704&group_id=34096 |
|
From: SourceForge.net <no...@so...> - 2003-09-06 02:00:09
|
Bugs item #795704, was opened at 2003-08-26 19:13 Message generated for change (Settings changed) made by smiley73 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=410643&aid=795704&group_id=34096 Category: Base System Group: None Status: Open >Resolution: Rejected Priority: 5 Submitted By: Heiko Zuerker (smiley73) Assigned to: Nobody/Anonymous (nobody) Summary: save-config doesn't work with 16 MB Initial Comment: Bruce Smith wrote: > I had a weird thing this morning while running save-config, where it > aborted in a very strange way (in VMware). To make a long story short, > after a lot of traces, manual "tar" commands, and head beating, I > figured out it was because my VMware was set to 16MB of memory. > > This is a fresh boot with a blank floppy. It seems like there is enough > memory in 16MB to run tar, but when the "j" option kicks in, bzip2 loads > and aborts tar. > > I increased my memory in VMware to 32MB and save-config runs fine there > (except for the "diff" part which I don't care about). > > We might want NOT want to advertise DL will run in 16MB of memory, if > people cannot save their configuration on that size machine. The other > option would be to use some busybox commands in save-config instead of > the standard ones ... (or not :) Damned. Of course that was a function I didn't test. It's worth a try to use just for this function the busybox tar. Can you take care of it? I have too many other things. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=410643&aid=795704&group_id=34096 |
|
From: SourceForge.net <no...@so...> - 2003-09-06 01:59:43
|
Bugs item #795700, was opened at 2003-08-26 18:59 Message generated for change (Settings changed) made by smiley73 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=410643&aid=795700&group_id=34096 Category: Base System Group: None >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Heiko Zuerker (smiley73) >Assigned to: Heiko Zuerker (smiley73) Summary: poweroff not working Initial Comment: reported by Dean Nedelman o Shutdown is still not powering off the computer. I'll take a look at this later today to see if RedHat has anything special in their shutdown procedures to actually power off the machine. I am pretty sure that this machine used to power off when I used RedHat. ---------------------------------------------------------------------- Comment By: Heiko Zuerker (smiley73) Date: 2003-08-28 15:34 Message: Logged In: YES user_id=112133 Dean Nedelman o A check of the web indicated that I either need the "apm" module to load (and specify modprobe apm power_off=1 or placing apm power_off=1 in /etc/modules - though that doesn't seem to match our configuration), or to specify "apm=on apm=power_off" as part of the boot. (A good web page on that is: http://www.togaware.com/linux/survivor/APM_Power.html ) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=410643&aid=795700&group_id=34096 |
|
From: SourceForge.net <no...@so...> - 2003-09-06 01:16:52
|
Bugs item #796935, was opened at 2003-08-28 15:34 Message generated for change (Settings changed) made by smiley73 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=410643&aid=796935&group_id=34096 Category: Configuration / Scripts Group: None >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Heiko Zuerker (smiley73) >Assigned to: Heiko Zuerker (smiley73) Summary: add -h to halt script Initial Comment: Dean Nedelman o One of the other options to /sbin/halt that we are NOT using and probably should consider is -h. It tells the system to spin down the disks and flush the disk cache. (Remember, we are talking about halt and poweroff here, not reboot). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=410643&aid=796935&group_id=34096 |
35 messages has been excluded from this view by a project administrator.
