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: Bruce S. <bw...@ar...> - 2003-10-15 12:25:46
|
> >> So, I copied loadlin.exe (16c) to my floppy, and ran it from there. > >> Boots fine! :-) > >> > >> BTW, the linux.bat kernel parameters probably need to be updated too, > >> since they don't match the parameters in isolinux.cfg. > >> > >> Is this a bug fix for 1.0, or a new 1.1 feature? ;-> > > > > As it fixes a problem it is definitely a bug fix, I'd say. > > > Agreed. Wow, an actual bug for 1.0 ... :-) > RC2 is already uploaded, so it will go into RC3 then. What's the best way to handle this one? The current source file is: loadlin16.tar.bz2 The author doesn't offer a new tar file, only a new loadlin.exe binary. Shall I replace the loadlin.exe binary and tar up my own package and name it loadlin16c.tar.bz2 ? - BS |
|
From: ferris b. <fer...@ho...> - 2003-10-15 12:24:52
|
Thanks, my problem is resolved. It is now working again with v1.0 (When I it use the right way) >From: Heiko Zuerker <hz@pr...> Re: Build problem 2003-10-14 10:27 I >would suggest that you use the 1.0 version, since the 1.1 build system is >undergoing major changes right now and is right now hard to support/debug >in such an early stage. >Specify "-r rel-1-0-patches" when you do a checkout from the CVS. > >Using 1.1 only makes sense when you do active development. >I'll also document a bug, so I add this to the documentation, > >cya > Heiko _________________________________________________________________ MSN Messenger 6 http://g.msn.fr/FR1001/866 : dialoguez en son et en image avec vos amis. |
|
From: Heiko Z. <he...@zu...> - 2003-10-15 01:45:19
|
Friedrich Lobenstock wrote: > Bruce Smith wrote: > >> So, I copied loadlin.exe (16c) to my floppy, and ran it from there. >> Boots fine! :-) >> >> BTW, the linux.bat kernel parameters probably need to be updated too, >> since they don't match the parameters in isolinux.cfg. >> >> Is this a bug fix for 1.0, or a new 1.1 feature? ;-> > > > As it fixes a problem it is definitely a bug fix, I'd say. > Agreed. RC2 is already uploaded, so it will go into RC3 then. cya Heiko |
|
From: Friedrich L. <fl...@fl...> - 2003-10-14 23:16:48
|
Bruce Smith wrote: > So, I copied loadlin.exe (16c) to my floppy, and ran it from there. > Boots fine! :-) > > BTW, the linux.bat kernel parameters probably need to be updated too, > since they don't match the parameters in isolinux.cfg. > > Is this a bug fix for 1.0, or a new 1.1 feature? ;-> As it fixes a problem it is definitely a bug fix, I'd say. -- MfG / Regards Friedrich Lobenstock ____________________________________________________________________ Friedrich Lobenstock Linux Services Lobenstock URL: http://www.lsl.at/ Email: fl...@fl... ____________________________________________________________________ |
|
From: Bruce S. <bw...@ar...> - 2003-10-14 21:20:35
|
> >When running linux.bat from C: I get: > > > >Uncompressing Linux ... > >Invalid compressed format (err=2) > >Halting system > > I didn't use that function for quite a while, can you try it on a machine > where you know DL is booting? > Just to make sure there are no memory problems or so. No memory problems, I ran memtest86 for 26+ hours before I started. :-) The problem appears to be loadlin needs to be upgraded to version 16c. >From the loadlin-16c readme: LOADLIN-16c =========== Support for loading bzImages bigger than 1MB compressed. Those images may be produced by kernels >= 2.4.5 (setup_header_version >= 0x0202). So, I copied loadlin.exe (16c) to my floppy, and ran it from there. Boots fine! :-) BTW, the linux.bat kernel parameters probably need to be updated too, since they don't match the parameters in isolinux.cfg. Is this a bug fix for 1.0, or a new 1.1 feature? ;-> - BS |
|
From: Heiko Z. <hz...@pr...> - 2003-10-14 21:00:13
|
On 10/14/2003 04:46:41 PM Bruce Smith wrote: >> RTFM ;-) >> >> http://www.devil-linux.org/newdoc/ch01s07.html#d0e864 > > >That would be great, if it worked ... :-( > >When running linux.bat from C: I get: > >Uncompressing Linux ... >Invalid compressed format (err=3D2) >Halting system > >Got another RTFM for me? ;-) I was so sure I got you this time... I didn't use that function for quite a while, can you try it on a machi= ne where you know DL is booting? Just to make sure there are no memory problems or so. cya Heiko = |
|
From: Bruce S. <bw...@ar...> - 2003-10-14 20:46:49
|
> RTFM ;-) > > http://www.devil-linux.org/newdoc/ch01s07.html#d0e864 That would be great, if it worked ... :-( When running linux.bat from C: I get: Uncompressing Linux ... Invalid compressed format (err=2) Halting system Got another RTFM for me? ;-) - BS |
|
From: Heiko Z. <hz...@pr...> - 2003-10-14 19:50:30
|
RTFM ;-) http://www.devil-linux.org/newdoc/ch01s07.html#d0e864 cya Heiko On 10/14/2003 03:30:03 PM Bruce Smith wrote: >I recently had this brilliant idea to install Linux on a couple older >boxes. I have a P5-166 and a P5-100. Both have 80MB of memory, and a= >IDE CD drive. Both PC's boot a Windows-98 CDROM fine. When I boot >either PC from the latest DL CD, it reads the CD briefly, then I get: > >isolinux: Loading spec packet failed, trying to wing it... >isolinux: Failed to access CD-ROM device; boot failed. > >The same DL CD works fine on a newer PC. I tried a new CD drive on th= e >P5-1xx PC's and I get the same error. I checked for a newer BIOS on >both PC's, and they are already running the latest. > >A lot of google'ing leads me to believe this is a common problem with >older BIOS's. The syslinux/isolinux page implies old PC's like this m= ay >work with "memdisk" instead of isolinux, but that requires a floppy >image, which we don't produce and a standard size floppy image would b= e >too large to produce with all the modules we include in the initrd. > >Any suggestions before I try and produce a floppy image (minus the SCS= I >modules), and try and make it boot with memdisk, or standard mkisofs a= nd >a eltorito boot image ??? > >P.S. This is bad if DL won't boot on older PC's ... = |
|
From: Bruce S. <bw...@ar...> - 2003-10-14 19:30:05
|
I recently had this brilliant idea to install Linux on a couple older boxes. I have a P5-166 and a P5-100. Both have 80MB of memory, and a IDE CD drive. Both PC's boot a Windows-98 CDROM fine. When I boot either PC from the latest DL CD, it reads the CD briefly, then I get: isolinux: Loading spec packet failed, trying to wing it... isolinux: Failed to access CD-ROM device; boot failed. The same DL CD works fine on a newer PC. I tried a new CD drive on the P5-1xx PC's and I get the same error. I checked for a newer BIOS on both PC's, and they are already running the latest. A lot of google'ing leads me to believe this is a common problem with older BIOS's. The syslinux/isolinux page implies old PC's like this may work with "memdisk" instead of isolinux, but that requires a floppy image, which we don't produce and a standard size floppy image would be too large to produce with all the modules we include in the initrd. Any suggestions before I try and produce a floppy image (minus the SCSI modules), and try and make it boot with memdisk, or standard mkisofs and a eltorito boot image ??? P.S. This is bad if DL won't boot on older PC's ... - BS |
|
From: Dean N. <di...@ti...> - 2003-10-14 18:24:10
|
Well, from what I could find, does this make any sense to you? linux-2.4.20-modulesoff.patch The only place besides RedHat that I could find it mentioned was on the SentryFirewall site. So it may be a RedHat specific modification. In particular, I couldn't find it mentioned on the Kernel mailing list archives... Dean -----Original Message----- Subject: Re: [Devil-linux-develop] Feature Request: Disabling of Module Loading I really like that idea ! Can you find out which Kernel Patch is providing this feature? Heiko On 10/13/2003 11:08:32 PM "Dean Nedelman" wrote: >I was reading the release notes for Fedora (the latest version of >RedHat's >consumer product - in beta). It had the following comment >(http://fedora.redhat.com/docs/release-notes/): > >------------------ > >The Fedora Core 0.94 kernel now makes it possible to prevent the >loading of >kernel modules. This can be useful for system administrators wanting to >ensure that only a strictly-controlled set of modules are loaded. To >disable >kernel module loading, issue the following command: > >echo off > /proc/modules > >Once this command has been issued, all further attempts to load kernel >modules will fail. > >NOTE: Once kernel module loading has been disabled, a reboot is >required to >re-enable it. > >------------------------ > >And I was thinking - wouldn't this be a useful feature for Devil-Linux? >After all - we are [presumably] running a "static" environment. So >once a >system is booted, wouldn't we WANT to prevent the loading (and/or >changing) >of kernel modules? |
|
From: SourceForge.net <no...@so...> - 2003-10-14 17:28:52
|
Bugs item #823587, was opened at 2003-10-14 12:28 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=823587&group_id=34096 Category: Documentation Group: None Status: Open Resolution: None Priority: 9 Submitted By: Heiko Zuerker (smiley73) Assigned to: Nobody/Anonymous (nobody) Summary: add information about cvs branches Initial Comment: I would suggest that you use the 1.0 version, since the 1.1 build system is undergoing major changes right now and is right now hard to support/debug in such an early stage. Specify "-r rel-1-0-patches" when you do a checkout from the CVS. Using 1.1 only makes sense when you do active development. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=410643&aid=823587&group_id=34096 |
|
From: Heiko Z. <hz...@pr...> - 2003-10-14 17:27:38
|
I would suggest that you use the 1.0 version, since the 1.1 build syste= m is undergoing major changes right now and is right now hard to support/deb= ug in such an early stage. Specify "-r rel-1-0-patches" when you do a checkout from the CVS. Using 1.1 only makes sense when you do active development. I'll also document a bug, so I add this to the documentation, cya Heiko On 10/14/2003 11:24:39 AM "ferris bueller" wrote: >I have a problem building a new customized version. >This morning (I am in Europe), I did download >lfssystem-cvs-20030127-i486-stripped.tar.bz2 >then I ran the 2 cvs command written in the doc (V1 and above) >then I ran >cvs update -d -P< >then I ran >./updatesrc< >then I ran >make menuconfig< and I did customize as usual. >then I ran >make build< and there was the following message: > >****************** >/data/build# make build > >executing prepare with option build >applying patch: /data/build/tmp/kernel-patches/cflags_extra.diff >patching file Makefile >Hunk #1 succeeded at 96 (offset 3 lines). >applying patch: /data/build/tmp/kernel-patches/init-sharing.patch >patching file init/do_mounts.c >patching file init/main.c >Hunk #1 succeeded at 26 with fuzz 2. >Hunk #2 succeeded at 425 (offset -3 lines). >Hunk #4 succeeded at 549 (offset -3 lines). >Hunk #5 succeeded at 565 (offset -1 lines). >applying patch: >/data/build/tmp/kernel-patches/linux-2.4.22-i2c-2.8.0.patch >patching file drivers/acorn/char/i2c.c >patching file drivers/acorn/char/pcf8583.c >patching file drivers/i2c/Config.in >patching file drivers/i2c/Makefile >patching file Documentation/i2c/dev-interface >patching file Documentation/i2c/i2c-pport >patching file Documentation/i2c/i2c-protocol >patching file Documentation/i2c/i2c-velleman >patching file Documentation/i2c/smbus-protocol >patching file Documentation/i2c/summary >patching file Documentation/i2c/writing-clients >patching file drivers/i2c/i2c-adap-ibm_ocp.c >patching file drivers/i2c/i2c-algo-8xx.c >patching file include/linux/i2c-algo-8xx.h >patching file drivers/i2c/i2c-algo-bit.c >patching file include/linux/i2c-algo-bit.h >patching file drivers/i2c/i2c-algo-ibm_ocp.c >patching file include/linux/i2c-algo-ibm_ocp.h >patching file drivers/i2c/i2c-algo-pcf.c >patching file include/linux/i2c-algo-pcf.h >patching file drivers/i2c/i2c-algo-sibyte.c >patching file include/linux/i2c-algo-sibyte.h >patching file drivers/i2c/i2c-core.c >patching file drivers/i2c/i2c-dev.c >patching file include/linux/i2c-dev.h >patching file drivers/i2c/i2c-elektor.c >patching file include/linux/i2c-elektor.h >patching file drivers/i2c/i2c-elv.c >patching file drivers/i2c/i2c-frodo.c >patching file include/linux/i2c-id.h >patching file drivers/i2c/i2c-max1617.c >patching file drivers/i2c/i2c-pcf-epp.c >patching file include/linux/i2c-pcf8584.h >patching file drivers/i2c/i2c-philips-par.c >patching file drivers/i2c/i2c-pport.c >patching file drivers/i2c/i2c-proc.c >patching file include/linux/i2c-proc.h >patching file drivers/i2c/i2c-rpx.c >patching file drivers/i2c/i2c-sibyte.c >patching file drivers/i2c/i2c-velleman.c >patching file include/linux/i2c.h >patching file Documentation/Configure.help >patching file drivers/i2c/i2c-adap-ite.c >patching file drivers/i2c/i2c-algo-ite.c >patching file drivers/i2c/i2c-keywest.c >patching file drivers/i2c/scx200_acb.c >patching file drivers/i2c/scx200_i2c.c >patching file drivers/ieee1394/pcilynx.c >patching file drivers/media/video/Makefile >patching file drivers/media/video/bt832.c >patching file drivers/media/video/bttv-if.c >patching file drivers/media/video/i2c-old.c >patching file drivers/media/video/msp3400.c >patching file drivers/media/video/saa5249.c >patching file drivers/media/video/saa7146.h >patching file drivers/media/video/swarm_saa7114h.c >patching file drivers/media/video/tda7432.c >patching file drivers/media/video/tda9875.c >patching file drivers/media/video/tda9887.c >patching file drivers/media/video/tuner-3036.c >patching file drivers/media/video/tuner.c >patching file drivers/media/video/tvaudio.c >patching file drivers/media/video/tvmixer.c >patching file drivers/pcmcia/sa1100_stork.c >patching file drivers/sound/dmasound/dac3550a.c >patching file drivers/sound/dmasound/tas3001c.c >patching file drivers/video/matrox/i2c-matroxfb.c >patching file drivers/video/matrox/matroxfb_maven.c >applying patch: >/data/build/tmp/kernel-patches/patch-watchdogdriver-pcwd.diff >patching file drivers/char/pcwd.c >make[1]: Entering directory `/data/build/tmp/linux-2.4.22' >Makefile:260: arch/i/Makefile: No such file or directory >make[1]: *** No rule to make target `arch/i/Makefile'. Stop. >make[1]: Leaving directory `/data/build/tmp/linux-2.4.22' >ERROR >/data/build/scripts/prepare build failed >make: *** [build] Error 1 > >****************** > >I also tried the option prepare but I do not see any difference in the= >result (As you can see, I am not sure how to use this option...) > >Did I forgot something, is the problem comming from my side? > >_________________________________________________________________ >Hotmail : un compte GRATUIT qui vous suit partout et tout le temps ! >http://g.msn.fr/FR1000/9493 > > > >------------------------------------------------------- >This SF.net email is sponsored by: SF.net Giveback Program. >SourceForge.net hosts over 70,000 Open Source Projects. >See the people who have HELPED US provide better services: >Click here: http://sourceforge.net/supporters.php >_______________________________________________ >Devil-linux-develop mailing list >Dev...@li... >https://lists.sourceforge.net/lists/listinfo/devil-linux-develop = |
|
From: Bruce S. <bw...@ar...> - 2003-10-14 17:10:28
|
> >>make[1]: Entering directory `/data/build/tmp/linux-2.4.22' > >>Makefile:260: arch/i/Makefile: No such file or directory > >>make[1]: *** No rule to make target `arch/i/Makefile'. Stop. > >>make[1]: Leaving directory `/data/build/tmp/linux-2.4.22' > >In the menuconfig, under Build Configuration, did you select a CPU? > > I did let 486 (by default). Look in your .config file and make sure "CONFIG_CPU" is set. - BS |
|
From: ferris b. <fer...@ho...> - 2003-10-14 16:08:26
|
>From: Bruce Smith <bws@ar...> Re: Build problem 2003-10-14 08:31 >>make[1]: Entering directory `/data/build/tmp/linux-2.4.22' >>Makefile:260: arch/i/Makefile: No such file or directory >>make[1]: *** No rule to make target `arch/i/Makefile'. Stop. >>make[1]: Leaving directory `/data/build/tmp/linux-2.4.22' >In the menuconfig, under Build Configuration, did you select a CPU? >(just a guess from the error message) >- BS I did let 486 (by default). _________________________________________________________________ Découvrez les nouvelles émoticônes animées de http://g.msn.fr/FR1001/866 MSN Messenger nouvelle formule |
|
From: Bruce S. <bw...@ar...> - 2003-10-14 15:31:55
|
> make[1]: Entering directory `/data/build/tmp/linux-2.4.22' > Makefile:260: arch/i/Makefile: No such file or directory > make[1]: *** No rule to make target `arch/i/Makefile'. Stop. > make[1]: Leaving directory `/data/build/tmp/linux-2.4.22' In the menuconfig, under Build Configuration, did you select a CPU? (just a guess from the error message) - BS |
|
From: ferris b. <fer...@ho...> - 2003-10-14 15:25:23
|
I have a problem building a new customized version. This morning (I am in Europe), I did download lfssystem-cvs-20030127-i486-stripped.tar.bz2 then I ran the 2 cvs command written in the doc (V1 and above) then I ran >cvs update -d -P< then I ran >./updatesrc< then I ran >make menuconfig< and I did customize as usual. then I ran >make build< and there was the following message: ****************** /data/build# make build executing prepare with option build applying patch: /data/build/tmp/kernel-patches/cflags_extra.diff patching file Makefile Hunk #1 succeeded at 96 (offset 3 lines). applying patch: /data/build/tmp/kernel-patches/init-sharing.patch patching file init/do_mounts.c patching file init/main.c Hunk #1 succeeded at 26 with fuzz 2. Hunk #2 succeeded at 425 (offset -3 lines). Hunk #4 succeeded at 549 (offset -3 lines). Hunk #5 succeeded at 565 (offset -1 lines). applying patch: /data/build/tmp/kernel-patches/linux-2.4.22-i2c-2.8.0.patch patching file drivers/acorn/char/i2c.c patching file drivers/acorn/char/pcf8583.c patching file drivers/i2c/Config.in patching file drivers/i2c/Makefile patching file Documentation/i2c/dev-interface patching file Documentation/i2c/i2c-pport patching file Documentation/i2c/i2c-protocol patching file Documentation/i2c/i2c-velleman patching file Documentation/i2c/smbus-protocol patching file Documentation/i2c/summary patching file Documentation/i2c/writing-clients patching file drivers/i2c/i2c-adap-ibm_ocp.c patching file drivers/i2c/i2c-algo-8xx.c patching file include/linux/i2c-algo-8xx.h patching file drivers/i2c/i2c-algo-bit.c patching file include/linux/i2c-algo-bit.h patching file drivers/i2c/i2c-algo-ibm_ocp.c patching file include/linux/i2c-algo-ibm_ocp.h patching file drivers/i2c/i2c-algo-pcf.c patching file include/linux/i2c-algo-pcf.h patching file drivers/i2c/i2c-algo-sibyte.c patching file include/linux/i2c-algo-sibyte.h patching file drivers/i2c/i2c-core.c patching file drivers/i2c/i2c-dev.c patching file include/linux/i2c-dev.h patching file drivers/i2c/i2c-elektor.c patching file include/linux/i2c-elektor.h patching file drivers/i2c/i2c-elv.c patching file drivers/i2c/i2c-frodo.c patching file include/linux/i2c-id.h patching file drivers/i2c/i2c-max1617.c patching file drivers/i2c/i2c-pcf-epp.c patching file include/linux/i2c-pcf8584.h patching file drivers/i2c/i2c-philips-par.c patching file drivers/i2c/i2c-pport.c patching file drivers/i2c/i2c-proc.c patching file include/linux/i2c-proc.h patching file drivers/i2c/i2c-rpx.c patching file drivers/i2c/i2c-sibyte.c patching file drivers/i2c/i2c-velleman.c patching file include/linux/i2c.h patching file Documentation/Configure.help patching file drivers/i2c/i2c-adap-ite.c patching file drivers/i2c/i2c-algo-ite.c patching file drivers/i2c/i2c-keywest.c patching file drivers/i2c/scx200_acb.c patching file drivers/i2c/scx200_i2c.c patching file drivers/ieee1394/pcilynx.c patching file drivers/media/video/Makefile patching file drivers/media/video/bt832.c patching file drivers/media/video/bttv-if.c patching file drivers/media/video/i2c-old.c patching file drivers/media/video/msp3400.c patching file drivers/media/video/saa5249.c patching file drivers/media/video/saa7146.h patching file drivers/media/video/swarm_saa7114h.c patching file drivers/media/video/tda7432.c patching file drivers/media/video/tda9875.c patching file drivers/media/video/tda9887.c patching file drivers/media/video/tuner-3036.c patching file drivers/media/video/tuner.c patching file drivers/media/video/tvaudio.c patching file drivers/media/video/tvmixer.c patching file drivers/pcmcia/sa1100_stork.c patching file drivers/sound/dmasound/dac3550a.c patching file drivers/sound/dmasound/tas3001c.c patching file drivers/video/matrox/i2c-matroxfb.c patching file drivers/video/matrox/matroxfb_maven.c applying patch: /data/build/tmp/kernel-patches/patch-watchdogdriver-pcwd.diff patching file drivers/char/pcwd.c make[1]: Entering directory `/data/build/tmp/linux-2.4.22' Makefile:260: arch/i/Makefile: No such file or directory make[1]: *** No rule to make target `arch/i/Makefile'. Stop. make[1]: Leaving directory `/data/build/tmp/linux-2.4.22' ERROR /data/build/scripts/prepare build failed make: *** [build] Error 1 ****************** I also tried the option prepare but I do not see any difference in the result (As you can see, I am not sure how to use this option...) Did I forgot something, is the problem comming from my side? _________________________________________________________________ Hotmail : un compte GRATUIT qui vous suit partout et tout le temps ! http://g.msn.fr/FR1000/9493 |
|
From: Heiko Z. <hz...@pr...> - 2003-10-14 12:56:21
|
I really like that idea ! Can you find out which Kernel Patch is providing this feature? Heiko On 10/13/2003 11:08:32 PM "Dean Nedelman" wrote: >I was reading the release notes for Fedora (the latest version of >RedHat's >consumer product - in beta). It had the following comment >(http://fedora.redhat.com/docs/release-notes/): > >------------------ > >The Fedora Core 0.94 kernel now makes it possible to prevent the >loading of >kernel modules. This can be useful for system administrators wanting t= o >ensure that only a strictly-controlled set of modules are loaded. To >disable >kernel module loading, issue the following command: > >echo off > /proc/modules > >Once this command has been issued, all further attempts to load kernel= >modules will fail. > >NOTE: Once kernel module loading has been disabled, a reboot is >required to >re-enable it. > >------------------------ > >And I was thinking - wouldn't this be a useful feature for Devil-Linux= ? >After all - we are [presumably] running a "static" environment. So >once a >system is booted, wouldn't we WANT to prevent the loading (and/or >changing) >of kernel modules? = |
|
From: <no...@fr...> - 2003-10-14 07:46:16
|
This email is to inform you about the release of version '2.6.8' of 'lftp' through freshmeat.net. All URLs and other useful information can be found at http://freshmeat.net/projects/lftp/ The changes in this release are as follows: This version features better multibyte character support, an experimental FTP protocol command PRET, a new setting ftp:use-pret, an unblock SIGCLD signal when running external programs, and compilation fixes. Project description: lftp is a sophisticated command line based FTP client. It has a multithreaded design allowing you to issue and execute multiple commands simultaneosly or in the background. It also features mirroring capabilities and will reconnect and continue transfers in the event of a disconnection. Also, if you quit the program while transfers are still in progress, it will switch to nohup mode and finish the transfers in the background. HTTP protocol and FTP over HTTP proxy are supported. Version 2.3.0 includes HTTPS and FTP over SSL support. 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 ____________________________| Advertising |____________________________ Got the debugger blues? Try Etnus TotalView, the Best Linux/UNIX debugger on the planet. With superior C++ support, the best thread debugging available, a great GUI, and more useful features than any other debugger, TotalView helps reveal bugs faster than any other debugger. And it provides more insight and analysis about your code and your data. So cure the debugger blues. Get your free 15-day trial at http://www.etnus.com/Download/demo-tv.html ____________________________| Advertising |____________________________ |
|
From: Dean N. <di...@ti...> - 2003-10-14 03:09:19
|
I was reading the release notes for Fedora (the latest version of RedHat's consumer product - in beta). It had the following comment (http://fedora.redhat.com/docs/release-notes/): ------------------ The Fedora Core 0.94 kernel now makes it possible to prevent the loading of kernel modules. This can be useful for system administrators wanting to ensure that only a strictly-controlled set of modules are loaded. To disable kernel module loading, issue the following command: echo off > /proc/modules Once this command has been issued, all further attempts to load kernel modules will fail. NOTE: Once kernel module loading has been disabled, a reboot is required to re-enable it. ------------------------ And I was thinking - wouldn't this be a useful feature for Devil-Linux? After all - we are [presumably] running a "static" environment. So once a system is booted, wouldn't we WANT to prevent the loading (and/or changing) of kernel modules? Just a thought.... Dean Nedelman TimeLord Consulting |
|
From: SourceForge.net <no...@so...> - 2003-10-14 00:01:15
|
Feature Requests item #767776, was opened at 2003-07-08 08:59 Message generated for change (Settings changed) made by smiley73 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=410646&aid=767776&group_id=34096 Category: Packages Group: None >Status: Closed Priority: 5 Submitted By: Heiko Zuerker (smiley73) >Assigned to: Heiko Zuerker (smiley73) 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: Heiko Z. <he...@zu...> - 2003-10-13 22:26:17
|
Heiko Zuerker wrote: >On 10/12/2003 08:03:29 PM Heiko Zuerker wrote: > > >>Heiko Zuerker wrote: >> >> >> >>>Bruce Smith wrote: >>> >>> >>> >>>>>The major change is that you can define dependencies (i.e. which >>>>>libs are required for this package). It uses the insserv utility and >>>>>will be the same as our init system. >>>>> >>>>> >>>>> >>>>Sounds scary. Give me a little notice before you check it in? >>>>(so I can run one last good compile, just in case ... ;-) >>>> >>>> >>>> >>>> >>>The new build system seems to work. I have to do a few more compiles >>>to make sure, but it looks like I can check it in later tonight. >>>So do you "cvs update -d -P" before I check my stuff in. ;-) >>> >>> >>Looks like our build system is a little bit too much for insserv. ;-) >>That means there will be some delays.... >> >> > >I found the problem, it was a small bug in insserv. > >All the changes are checked in! >You need to do a "make mrproper unpack" first, since the new build system >will not recognize the old flags. > >There's a new make command: "make prepare" >This will order the build scripts according to the specified dependencies >and creates all the symlinks. >You need to do a "make prepare" when you added new scripts. >Prepare will also be automatically invoked after a mrproper. > >The faciliities are specified in the file build/scripts/buildorder.conf . > > If you don't start with a fresh LFS system, then it is absolutely important that you delete /sbin/insserv inside the LFS system. cya Heiko |
|
From: SourceForge.net <no...@so...> - 2003-10-13 22:16:42
|
Feature Requests item #693367, was opened at 2003-02-25 21:36 Message generated for change (Settings changed) made by smiley73 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=410646&aid=693367&group_id=34096 Category: Build System Group: None >Status: Closed Priority: 5 Submitted By: Heiko Zuerker (smiley73) >Assigned to: Heiko Zuerker (smiley73) Summary: change build system to do dependencies Initial Comment: do not use build/123script anymore introduce system which uses dependencies and calls the scripts in the right order do it similar to the insserv utility ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=410646&aid=693367&group_id=34096 |
|
From: Bruce S. <bw...@ar...> - 2003-10-13 20:00:43
|
> Just a thought....so don't kill me rightaway ;-) > > What if Devil-Linux, during boot, checks the Version Number in the > config file and if it's to old prompts you to update the config by > running your script? I'll look into that. > Or at least if we had a check for the version in there the user > would at least get prompted (or just a sleep 300 to be safe) that > he's runnning an old config. I made that change a long time ago! :-) It displays a red (or yellow - forget) warning and sleeps for 60 seconds (I think) instead of 300 if the versions differ. - BS |
|
From: Heiko Z. <hz...@pr...> - 2003-10-13 19:54:46
|
On 10/13/2003 03:43:30 PM Bruce Smith wrote: >> >I've found one thing that is a pain, upgrading to a new version CD,= >> >plus also upgrading the configuration. >> ... >> Check if the file date is "Jan 1 1980", then it's an unmodified file= . > >I played it safe and compared each individual file. > >> I would be very happy if you would get an update script working ! > >It seems to working on my system (not uploaded yet). > >Basically it untars the old etc file and the new etc file into differe= nt >subdirectories, compares every file in old to new, gives you a list of= >which file(s) changed and asks which file(s) you'd like to copy to the= >new directory. Then it tars up a new etc config file. > >I really hated the thought of having to answer y/n for potentially >dozens of files to copy over to the new config (like the old kernel >"make config"), so I wrote it using "dialog", like the setup program. > >This lets you scroll back & forth though the list of changed files and= >check which file(s) to copy. Plus if you press the HELP button on a >particular modified file, it does a "ls -l" on both old/new files, the= n >does a "diff -u" on them, and then does a "less" on both files. > >The disadvantage is you need "dialog" installed on your desktop. Do y= ou >have a problem with that? Most distro's come with dialog (at least >Redhat has come with it for quite a few releases), or the user can >always download and install the dialog package ... You can also add it to DL, so we don't have any requirements outside of= our system. Just change the function you have added earlier (blah wrong version bla= h), by the upgrade utility. cya Heiko = |
|
From: Friedrich L. <fl...@fl...> - 2003-10-13 19:51:22
|
Bruce Smith wrote: > > It seems to working on my system (not uploaded yet). > > Basically it untars the old etc file and the new etc file into different > subdirectories, compares every file in old to new, gives you a list of > which file(s) changed and asks which file(s) you'd like to copy to the > new directory. Then it tars up a new etc config file. > > I really hated the thought of having to answer y/n for potentially > dozens of files to copy over to the new config (like the old kernel > "make config"), so I wrote it using "dialog", like the setup program. > > This lets you scroll back & forth though the list of changed files and > check which file(s) to copy. Plus if you press the HELP button on a > particular modified file, it does a "ls -l" on both old/new files, then > does a "diff -u" on them, and then does a "less" on both files. > > The disadvantage is you need "dialog" installed on your desktop. Do you > have a problem with that? Most distro's come with dialog (at least > Redhat has come with it for quite a few releases), or the user can > always download and install the dialog package ... Just a thought....so don't kill me rightaway ;-) What if Devil-Linux, during boot, checks the Version Number in the config file and if it's to old prompts you to update the config by running your script? Or at least if we had a check for the version in there the user would at least get prompted (or just a sleep 300 to be safe) that he's runnning an old config. -- MfG / Regards Friedrich Lobenstock ____________________________________________________________________ Friedrich Lobenstock Linux Services Lobenstock URL: http://www.lsl.at/ Email: fl...@fl... ____________________________________________________________________ |
35 messages has been excluded from this view by a project administrator.
