From gerhard.flepsen at siemens.com Thu Jun 8 17:55:29 2006 From: gerhard.flepsen at siemens.com (Flepsen, Gerhard) Date: Thu, 8 Jun 2006 17:55:29 +0200 Subject: [Udpcast] Need FAT support Message-ID: <03AED5A53FACDE47924D05AE3523551F0B9AD4@ERLM822A.ww001.siemens.net> Hi list, I downloaded a new image of udpcast and had to find out that support for FAT-filesystems seems to have gone away. Is there a way to get it back? Thanks Gerhard -------------- next part -------------- An HTML attachment was scrubbed... URL: From erpaco at ptvtelecom.com Wed Jun 14 10:26:14 2006 From: erpaco at ptvtelecom.com (Paco Cruz) Date: Wed, 14 Jun 2006 10:26:14 +0200 Subject: [Udpcast] Trouble with a 3com-812 router Message-ID: <448FC826.2070700@ptvtelecom.com> Hello all I a have setup udpcast in a classroom at a Secondary School to distribute CDs and whole directorie trees, and it works like a charm, except for a minor nuissance. Everytime I want to use udpcast I have to disconnect from the 3com-812 router that serves as a gateway. When I try to send anything with the gateway connected there is an extremely low transmission with errors el al. As soon as I disconnect the router the throughput goes up to 70-90 Mbps. Does anybody have any hint? Thank you all -- Saludos Paco Cruz --------------------------------------------------------------------- "If you have an apple and I have an apple and we exchange these apples then you and I will still each have *one* apple. But if you have an idea and I have an idea and we exchange these ideas, then each of us will have *two* ideas." George Bernad Shaw --------------------------------------------------------------------- Si tu tienes una manzana y yo tengo una manzana, y las intercambiamos, entonces tu y yo aun tendremos *una* manzana. Pero si tu tienes una idea y yo tengo una idea e intercambiamos esas ideas, entonces cada uno de nosotros tendra *dos* ideas. George Bernard Shaw --------------------------------------------------------------------- From alain at knaff.lu Wed Jun 14 11:49:49 2006 From: alain at knaff.lu (Alain Knaff) Date: Wed, 14 Jun 2006 11:49:49 +0200 Subject: [Udpcast] Trouble with a 3com-812 router In-Reply-To: <448FC826.2070700@ptvtelecom.com> References: <448FC826.2070700@ptvtelecom.com> Message-ID: <448FDBBD.7060607@knaff.lu> Paco Cruz wrote: > Hello all > > I a have setup udpcast in a classroom at a Secondary School to > distribute CDs and whole directorie trees, and it works like a charm, > except for a minor nuissance. > > Everytime I want to use udpcast I have to disconnect from the 3com-812 > router that serves as a gateway. > > When I try to send anything with the gateway connected there is an > extremely low transmission with errors el al. As soon as I disconnect > the router the throughput goes up to 70-90 Mbps. > > Does anybody have any hint? > > Thank you all > Could be that the router is using a link speed of 10 Mbps, or slowing everything down with flow-control packets. Several solutions are possible, depending on the switch: - Try enabling IGMP support if available (so that only those ports interested in the transmission do get the traffic) - Try disabling flow control (some switches support this on a per-port basis... If that is the case, you only need to disable flow control on the port to which that router is connected) Regards, Alain From dteed at artistic.ca Tue Jun 20 13:38:59 2006 From: dteed at artistic.ca (D G Teed) Date: Tue, 20 Jun 2006 08:38:59 -0300 (ADT) Subject: [Udpcast] cap=00000009 message once at beginning of transfer Message-ID: Hi, We have a new notebook to image. I have started testing of the send of the master, and initially the receiver got a message : received message, cap=00000009 then it shows it is connected and the IP and the rest proceeds without a problem. The sender showed: Starting transfer: 00000009 and then the stats on bytes transfered proceed without error. The connection is over a crossover cable - no switch/hub. Is there anything to be concerned with in that cap= message? --Donald Teed From alain at knaff.lu Tue Jun 20 16:55:39 2006 From: alain at knaff.lu (Alain Knaff) Date: Tue, 20 Jun 2006 16:55:39 +0200 Subject: [Udpcast] cap=00000009 message once at beginning of transfer In-Reply-To: References: Message-ID: <44980C6B.1080809@knaff.lu> D G Teed wrote: > Hi, > > We have a new notebook to image. I have started > testing of the send of the master, and initially > the receiver got a message : > received message, cap=00000009 > then it shows it is connected and the IP and > the rest proceeds without a problem. > > The sender showed: Starting transfer: 00000009 > and then the stats on bytes transfered proceed without error. > > The connection is over a crossover cable - no switch/hub. > > Is there anything to be concerned with in that cap= message? > > --Donald Teed > _______________________________________________ > Udpcast mailing list > Udpcast at udpcast.linux.lu > https://lll.lgl.lu/mailman/listinfo/udpcast This message is normal. It shows the "capabilities" of the peers. Capabilities are a bitmap, so 9 means 1+8 = "new generation protocol" + "big endian" (network) byte order, which is the default nowadays. So, nothing to worry about Regards, Alain From kroediet at arcor.de Wed Jun 21 13:09:35 2006 From: kroediet at arcor.de (Dieter Kroemer) Date: Wed, 21 Jun 2006 13:09:35 +0200 (CEST) Subject: [Udpcast] online-Interface e1000 problems Message-ID: <10458579.1150888175854.JavaMail.ngmail@webmail13> Hi, after creater in the online interface an image for the intelpro1000-nic I get after startingthe computer with udpcast following message: /lib/modules/2.6.11.12udpcast/modules.pcimap (No such file or directory) --> after klicking okay: mod probe: could not parse modules.dep. I've got an older udpcast image (from december 20005) for the e1000, there are no problems. (I need a newer image, because the computer have to resart after finishing the cloning.) What can I do? Kind regards Dieter From alain at knaff.lu Wed Jun 21 15:06:26 2006 From: alain at knaff.lu (Alain Knaff) Date: Wed, 21 Jun 2006 15:06:26 +0200 Subject: [Udpcast] online-Interface e1000 problems In-Reply-To: <10458579.1150888175854.JavaMail.ngmail@webmail13> References: <10458579.1150888175854.JavaMail.ngmail@webmail13> Message-ID: <44994452.1040303@knaff.lu> Dieter Kroemer wrote: > Hi, > > after creater in the online interface an image for the intelpro1000-nic I get after startingthe computer with udpcast following message: > > /lib/modules/2.6.11.12udpcast/modules.pcimap (No such file or directory) --> after klicking okay: mod probe: could not parse modules.dep. ^^^^^^^^^ Current udpcast kernel is 2.6.16.18 Are you sure you haven't a mismatched kernel and image here (... which could be an issue if you boot from PXE, as both are separate files in that case...). Regards, Alain From alain at knaff.lu Wed Jun 21 16:11:53 2006 From: alain at knaff.lu (Alain Knaff) Date: Wed, 21 Jun 2006 16:11:53 +0200 Subject: [Udpcast] Need FAT support In-Reply-To: <03AED5A53FACDE47924D05AE3523551F0B9AD4@ERLM822A.ww001.siemens.net> References: <03AED5A53FACDE47924D05AE3523551F0B9AD4@ERLM822A.ww001.siemens.net> Message-ID: <449953A9.5070005@knaff.lu> Flepsen, Gerhard wrote: > Hi list, > > I downloaded a new image of udpcast and had to find out that support for > FAT-filesystems seems to have gone away. > > Is there a way to get it back? > > Thanks > Gerhard Until now, vfat support has been on the floppy images (where it is needed for saving the menu choices), but not on the CD-Rom images (where it is impossible to save anything anyways, as they are read-only). I've now added a check box to cast-o-matic, with which you can chose to also include VFAT support of CD Images (and PXE, and...) Regards, Alain From ygingras at ygingras.net Thu Jun 22 00:45:18 2006 From: ygingras at ygingras.net (Yannick Gingras) Date: Wed, 21 Jun 2006 18:45:18 -0400 Subject: [Udpcast] Ejecting the CD-ROM before broadcast Message-ID: Hi, I'd like to have my udpcast to eject its CD-ROM before a broadcast so I can pick it and boot another box with it. Yeah I could just push the CD-ROM drive button but I'm a lazy bum. cast-o-matic is a great tool so I though I could just upload eject and call it. Ok eject is overkill, I did a smaller eject that I call miniject: #include #include #include #include #include #include #include #include #define DEF_CDROM "/dev/cdrom" int main(int argc, char **argv) { int fd; if (argc > 1) fd = open(argv[1], O_RDONLY|O_NONBLOCK); else fd = open(DEF_CDROM, O_RDONLY|O_NONBLOCK); ioctl(fd, CDROMEJECT); } But unfortunatly I can't find the cdrom device in /dev. Are there any modules that I should add to the image in order to have the cdrom device created in /dev ? -- Yannick Gingras From kroe at rs-schesslitz.de Wed Jun 21 20:59:52 2006 From: kroe at rs-schesslitz.de (Dieter Kroemer) Date: Wed, 21 Jun 2006 20:59:52 +0200 Subject: [Udpcast] online-Interface e1000 problems In-Reply-To: <44994452.1040303@knaff.lu> References: <10458579.1150888175854.JavaMail.ngmail@webmail13> <44994452.1040303@knaff.lu> Message-ID: <44999728.9090303@rs-schesslitz.de> Alain Knaff schrieb: > > > Are you sure you haven't a mismatched kernel and image here (... which > could be an issue if you boot from PXE, as both are separate files in > that case...). Thanks, that was the error - now with the correct kernel it works. Thank you very much :-) Kind regards Dieter From alain at knaff.lu Thu Jun 22 09:41:05 2006 From: alain at knaff.lu (Alain Knaff) Date: Thu, 22 Jun 2006 09:41:05 +0200 Subject: [Udpcast] Ejecting the CD-ROM before broadcast In-Reply-To: References: Message-ID: <449A4991.5050800@knaff.lu> Yannick Gingras wrote: > Hi, I'd like to have my udpcast to eject its CD-ROM before a broadcast > so I can pick it and boot another box with it. Yeah I could just push > the CD-ROM drive button but I'm a lazy bum. cast-o-matic is a great > tool so I though I could just upload eject and call it. Ok eject is > overkill, I did a smaller eject that I call miniject: > > #include > #include > #include > #include > #include > #include > #include > #include > > #define DEF_CDROM "/dev/cdrom" > > int main(int argc, char **argv) > { > int fd; > if (argc > 1) > fd = open(argv[1], O_RDONLY|O_NONBLOCK); > else > fd = open(DEF_CDROM, O_RDONLY|O_NONBLOCK); > ioctl(fd, CDROMEJECT); > } > > But unfortunatly I can't find the cdrom device in /dev. Are there any > modules that I should add to the image in order to have the cdrom > device created in /dev ? > In the current version, by default, CD-Rom drivers are not installed (not needed, because the loading of the OS is performed via the BIOS). So, it's currently not possible to do this miniject Regards, Alain From ygingras at ygingras.net Thu Jun 22 09:54:35 2006 From: ygingras at ygingras.net (Yannick Gingras) Date: Thu, 22 Jun 2006 03:54:35 -0400 Subject: [Udpcast] Ejecting the CD-ROM before broadcast In-Reply-To: <449A4991.5050800@knaff.lu> (Alain Knaff's message of "Thu, 22 Jun 2006 09:41:05 +0200") References: <449A4991.5050800@knaff.lu> Message-ID: Alain Knaff writes: > In the current version, by default, CD-Rom drivers are not installed > (not needed, because the loading of the OS is performed via the BIOS). > So, it's currently not possible to do this miniject I don't know much about customizing embeded OSes but how hard would it be to add the cdrom module to ramdisk ? Do I just need to recompile a kernel with the module builtin ? -- Yannick Gingras From mikes at kuentos.guam.net Thu Jun 22 10:33:25 2006 From: mikes at kuentos.guam.net (Michael D. Setzer II) Date: Thu, 22 Jun 2006 18:33:25 +1000 Subject: [Udpcast] online-Interface e1000 problems In-Reply-To: <44994452.1040303@knaff.lu> References: <10458579.1150888175854.JavaMail.ngmail@webmail13> Message-ID: <449AE275.9946.BF15AF2@mikes.kuentos.guam.net> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 21 Jun 2006 at 15:06, Alain Knaff wrote: Date sent: Wed, 21 Jun 2006 15:06:26 +0200 From: Alain Knaff To: Dieter Kroemer Subject: Re: [Udpcast] online-Interface e1000 problems Copies to: udpcast at udpcast.linux.lu > Dieter Kroemer wrote: > > Hi, > > > > after creater in the online interface an image for the intelpro1000-nic I get after startingthe computer with udpcast following message: > > > > /lib/modules/2.6.11.12udpcast/modules.pcimap (No such file or directory) --> after klicking okay: mod probe: could not parse modules.dep. > ^^^^^^^^^ > Current udpcast kernel is 2.6.16.18 Just as a note: I have found that the 2.6.16.x kernels have some issues with hardware. A few users had hardware that worked with the 2.6.15.6 kernels but not with any of the 2.6.16 kernels. I even had an AMD64 system that would not see the SATA drive. Even rebuild a 2.6.16.20 kernel usig the 2.6.15.6 .config with make oldconfig to make sure it wasn't some change in the config. Currently have the 2.6.15.6 kernel as the default, but the 2.6.16.20 is on the cd as well. Been on a plane with 24 hours of the last two days. > > Are you sure you haven't a mismatched kernel and image here (... which > could be an issue if you boot from PXE, as both are separate files in > that case...). > > Regards, > > Alain > > _______________________________________________ > Udpcast mailing list > Udpcast at udpcast.linux.lu > https://lll.lgl.lu/mailman/listinfo/udpcast > +----------------------------------------------------------+ Michael D. Setzer II - Computer Science Instructor Guam Community College Computer Center mailto:mikes at kuentos.guam.net mailto:msetzerii at gmail.com http://www.guam.net/home/mikes Guam - Where America's Day Begins +----------------------------------------------------------+ http://setiathome.berkeley.edu Number of Seti Units Returned: 19,471 Processing time: 32 years, 290 days, 12 hours, 58 minutes (Total Hours: 287,489) BOINC Seti at Home Total Credits 1288277.115071 -----BEGIN PGP SIGNATURE----- Version: PGP 6.5.8 -- QDPGP 2.61c Comment: http://community.wow.net/grt/qdpgp.html iQA/AwUBRJnJNyzGQcr/2AKZEQKVWgCgrZJdrhFNkdPAj5G17HbuDfvLyA4AoNtn VQREFlmBrcEdiOt0I/xKYW5w =vn1c -----END PGP SIGNATURE----- From mikes at kuentos.guam.net Thu Jun 22 10:21:08 2006 From: mikes at kuentos.guam.net (Michael D. Setzer II) Date: Thu, 22 Jun 2006 18:21:08 +1000 Subject: [Udpcast] online-Interface e1000 problems In-Reply-To: <10458579.1150888175854.JavaMail.ngmail@webmail13> Message-ID: <449ADF94.19705.BE618ED@mikes.kuentos.guam.net> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 21 Jun 2006 at 13:09, Dieter Kroemer wrote: Date sent: Wed, 21 Jun 2006 13:09:35 +0200 (CEST) From: Dieter Kroemer To: udpcast at udpcast.linux.lu Subject: [Udpcast] online-Interface e1000 problems > Hi, > > after creater in the online interface an image for the intelpro1000-nic I get after startingthe computer with udpcast following message: > > /lib/modules/2.6.11.12udpcast/modules.pcimap (No such file or directory) --> after klicking okay: mod probe: could not parse modules.dep. > > > I've got an older udpcast image (from december 20005) for the e1000, there are no problems. > > (I need a newer image, because the computer have to resart after finishing the cloning.) > > What can I do? Not sure if it is related, but I recently had a use of my g4l (ghost for linux) that had a problem with the e1000 card. After some searching, found that the e1000 card has problem with smp systems. Loading the kernel with the nosmp option allowing the card to work. With g4l I build the kernels with the everything build in. It creates images that can work with udpcast, and use udpcast when doing a whole lab. G4L creates images on ftp server in network mode, and can restore them via ftp as well, but the udpcast is much faster when doing mulitple machines. > > Kind regards > Dieter > _______________________________________________ > Udpcast mailing list > Udpcast at udpcast.linux.lu > https://lll.lgl.lu/mailman/listinfo/udpcast > +----------------------------------------------------------+ Michael D. Setzer II - Computer Science Instructor Guam Community College Computer Center mailto:mikes at kuentos.guam.net mailto:msetzerii at gmail.com http://www.guam.net/home/mikes Guam - Where America's Day Begins +----------------------------------------------------------+ http://setiathome.berkeley.edu Number of Seti Units Returned: 19,471 Processing time: 32 years, 290 days, 12 hours, 58 minutes (Total Hours: 287,489) BOINC Seti at Home Total Credits 1288277.115071 -----BEGIN PGP SIGNATURE----- Version: PGP 6.5.8 -- QDPGP 2.61c Comment: http://community.wow.net/grt/qdpgp.html iQA/AwUBRJnGVSzGQcr/2AKZEQJWyACfYEiViuZwqktgJ9axZtY5UaikQuYAn1rd JbGQXZWFx0T8jW+KG80kJU9R =6YFM -----END PGP SIGNATURE----- From thomas.kuehling at mapsolute.com Thu Jun 22 10:29:24 2006 From: thomas.kuehling at mapsolute.com (Thomas Kuehling) Date: Thu, 22 Jun 2006 10:29:24 +0200 Subject: [Udpcast] Ejecting the CD-ROM before broadcast In-Reply-To: References: Message-ID: <1150964965.9491.1.camel@localhost.localdomain> Hi Yannick, i am not really fit in C, but on Linux it's enough to do just an eject without addressing the device. Just type in the bash "eject" and the device will be ejeceted. On Mi, 2006-06-21 at 18:45 -0400, Yannick Gingras wrote: > Hi, I'd like to have my udpcast to eject its CD-ROM before a broadcast > so I can pick it and boot another box with it. Yeah I could just push > the CD-ROM drive button but I'm a lazy bum. cast-o-matic is a great > tool so I though I could just upload eject and call it. Ok eject is > overkill, I did a smaller eject that I call miniject: > > #include > #include > #include > #include > #include > #include > #include > #include > > #define DEF_CDROM "/dev/cdrom" > > int main(int argc, char **argv) > { > int fd; > if (argc > 1) > fd = open(argv[1], O_RDONLY|O_NONBLOCK); > else > fd = open(DEF_CDROM, O_RDONLY|O_NONBLOCK); > ioctl(fd, CDROMEJECT); > } > > But unfortunatly I can't find the cdrom device in /dev. Are there any > modules that I should add to the image in order to have the cdrom > device created in /dev ? > Mit freundlichen Grüßen Thomas Kühling -- Mapsolute Gmbh - Techn. Administration - TK2325-RIPE Düsseldorfer Straße 40a - 65760 Eschborn/Frankfurt a.M. - Germany E-Mail: thomas.kuehling at mapsolute.com - web: http://www.mapsolute.com From mikes at kuentos.guam.net Thu Jun 22 11:03:27 2006 From: mikes at kuentos.guam.net (Michael D. Setzer II) Date: Thu, 22 Jun 2006 19:03:27 +1000 Subject: [Udpcast] Ejecting the CD-ROM before broadcast In-Reply-To: <1150964965.9491.1.camel@localhost.localdomain> References: Message-ID: <449AE97F.5855.C0CD8AB@mikes.kuentos.guam.net> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 22 Jun 2006 at 10:29, Thomas Kuehling wrote: Subject: Re: [Udpcast] Ejecting the CD-ROM before broadcast From: Thomas Kuehling To: Yannick Gingras Organization: Mapsolute GmbH Date sent: Thu, 22 Jun 2006 10:29:24 +0200 Copies to: udpcast at udpcast.linux.lu Send reply to: thomas.kuehling at mapsolute.com > Hi Yannick, > > i am not really fit in C, but on Linux it's enough to do just an eject > without addressing the device. Just type in the bash "eject" and the > device will be ejeceted. > Later versions of the busybox have the eject as an optoin. I added it to the g4l cd, and use it with a frontend script that is downloaded from the ftp server to automate the process, > On Mi, 2006-06-21 at 18:45 -0400, Yannick Gingras wrote: > > Hi, I'd like to have my udpcast to eject its CD-ROM before a broadcast > > so I can pick it and boot another box with it. Yeah I could just push > > the CD-ROM drive button but I'm a lazy bum. cast-o-matic is a great > > tool so I though I could just upload eject and call it. Ok eject is > > overkill, I did a smaller eject that I call miniject: > > > > #include > > #include > > #include > > #include > > #include > > #include > > #include > > #include > > > > #define DEF_CDROM "/dev/cdrom" > > > > int main(int argc, char **argv) > > { > > int fd; > > if (argc > 1) > > fd = open(argv[1], O_RDONLY|O_NONBLOCK); > > else > > fd = open(DEF_CDROM, O_RDONLY|O_NONBLOCK); > > ioctl(fd, CDROMEJECT); > > } > > > > But unfortunatly I can't find the cdrom device in /dev. Are there any > > modules that I should add to the image in order to have the cdrom > > device created in /dev ? > > > > Mit freundlichen Grüßen > Thomas Kühling > > -- > Mapsolute Gmbh - Techn. Administration - TK2325-RIPE > Düsseldorfer Straße 40a - 65760 Eschborn/Frankfurt a.M. - Germany > E-Mail: thomas.kuehling at mapsolute.com - web: http://www.mapsolute.com > > _______________________________________________ > Udpcast mailing list > Udpcast at udpcast.linux.lu > https://lll.lgl.lu/mailman/listinfo/udpcast > +----------------------------------------------------------+ Michael D. Setzer II - Computer Science Instructor Guam Community College Computer Center mailto:mikes at kuentos.guam.net mailto:msetzerii at gmail.com http://www.guam.net/home/mikes Guam - Where America's Day Begins +----------------------------------------------------------+ http://setiathome.berkeley.edu Number of Seti Units Returned: 19,471 Processing time: 32 years, 290 days, 12 hours, 58 minutes (Total Hours: 287,489) BOINC Seti at Home Total Credits 1288277.115071 -----BEGIN PGP SIGNATURE----- Version: PGP 6.5.8 -- QDPGP 2.61c Comment: http://community.wow.net/grt/qdpgp.html iQA/AwUBRJnQQCzGQcr/2AKZEQLXCwCgjcBVbcngO823D9QpdY7ExtDxxygAoNSC IrlSYVQFVrEnbrDoleeuCCFV =o4sU -----END PGP SIGNATURE----- From ygingras at ygingras.net Thu Jun 22 14:53:45 2006 From: ygingras at ygingras.net (Yannick Gingras) Date: Thu, 22 Jun 2006 08:53:45 -0400 Subject: [Udpcast] Ejecting the CD-ROM before broadcast In-Reply-To: <1150964965.9491.1.camel@localhost.localdomain> (Thomas Kuehling's message of "Thu, 22 Jun 2006 10:29:24 +0200") References: <1150964965.9491.1.camel@localhost.localdomain> Message-ID: Thomas Kuehling writes: > i am not really fit in C, but on Linux it's enough to do just an eject > without addressing the device. Just type in the bash "eject" and the > device will be ejeceted. miniject is actually a striped down version of eject. eject has many options to unmount and to eject stuff like floppies and tapes. When you remove all of it, you get miniject. -- Yannick Gingras From alain at knaff.lu Mon Jun 26 16:17:09 2006 From: alain at knaff.lu (Alain Knaff) Date: Mon, 26 Jun 2006 16:17:09 +0200 Subject: [Udpcast] Ejecting the CD-ROM before broadcast In-Reply-To: References: <449A4991.5050800@knaff.lu> Message-ID: <449FEC65.4040602@knaff.lu> Yannick Gingras wrote: > Alain Knaff writes: > >> In the current version, by default, CD-Rom drivers are not installed >> (not needed, because the loading of the OS is performed via the BIOS). >> So, it's currently not possible to do this miniject > > I don't know much about customizing embeded OSes but how hard would it > be to add the cdrom module to ramdisk ? > > Do I just need to recompile a kernel with the module builtin ? > The udpcast kernel already has the ide-cd module, it's just not included on the image. In order to include it, add --modules ide-cd to the makeImage command line. I've now added a checkbox to cast-o-matic to add the feature Regards, Alain From ygingras at ygingras.net Mon Jun 26 22:23:02 2006 From: ygingras at ygingras.net (Yannick Gingras) Date: Mon, 26 Jun 2006 16:23:02 -0400 Subject: [Udpcast] Ejecting the CD-ROM before broadcast In-Reply-To: <449FEC65.4040602@knaff.lu> (Alain Knaff's message of "Mon, 26 Jun 2006 16:17:09 +0200") References: <449A4991.5050800@knaff.lu> <449FEC65.4040602@knaff.lu> Message-ID: Alain Knaff writes: > The udpcast kernel already has the ide-cd module, it's just not > included on the image. > > In order to include it, add --modules ide-cd to the makeImage command line. > > I've now added a checkbox to cast-o-matic to add the feature This is perfect! Thanks! : D -- Yannick Gingras From dbri.tcc at gmail.com Tue Jun 27 00:03:01 2006 From: dbri.tcc at gmail.com (Don Bright) Date: Mon, 26 Jun 2006 17:03:01 -0500 Subject: [Udpcast] Feature Requests: named sessions and no timeout messages Message-ID: Dear UDP Casters, First let me say thank you for making this program. It has enabled me to completely get rid of Symantec Ghost and it's damnable boot floppies, as well as extremely hard to understand licensing arrangement (I was never sure if I had a legal copy or not, someone else at the workplace just gave me a copy of it, and I couldnt get any information on the license for it) I have two feature requests. The first is to have an option, something like --name, which would provide a 'name' for each 'session', so that if two people are using udpcast on the same network, they wont conflict with each other. I know they could just use different ports, but names seem easier than ports (and certain ports might be blocked or conflict with other programs) The second, is to have a command line option to stop the 'timeout' messages on the sender. I'm sending 7 GB of data and getting 1% timeout (maybe because im sending to some old machines) so you can imagine the massive amounts of messages written to the console. I'd like an option like --quiet or --hide-timeouts to stop this stuff. I might make a patch later on, but I thought I'd through this out there in ccase someone has already done it or its being planned. Thank you. From dteed at artistic.ca Tue Jun 27 01:17:39 2006 From: dteed at artistic.ca (D G Teed) Date: Mon, 26 Jun 2006 20:17:39 -0300 (ADT) Subject: [Udpcast] Feature Requests: named sessions and no timeout messages In-Reply-To: References: Message-ID: Actually the timeout messages are useful. If you are imaging a bunch of machines at once, and one has a flaky ethernet device which is slowing down the process, the timeout provides info on which one is behind and might better be yanked from the process to allow the others to complete. But as an option, it could be useful to some people. --Donald Teed On Mon, 26 Jun 2006, Don Bright wrote: > Dear UDP Casters, > > First let me say thank you for making this program. It has enabled me > to completely get rid of Symantec Ghost and it's damnable boot > floppies, as well as extremely hard to understand licensing > arrangement (I was never sure if I had a legal copy or not, someone > else at the workplace just gave me a copy of it, and I couldnt get any > information on the license for it) > > I have two feature requests. > > The first is to have an option, something like --name, which would > provide a 'name' for each 'session', so that if two people are using > udpcast on the same network, they wont conflict with each other. I > know they could just use different ports, but names seem easier than > ports (and certain ports might be blocked or conflict with other > programs) > > The second, is to have a command line option to stop the 'timeout' > messages on the sender. I'm sending 7 GB of data and getting 1% > timeout (maybe because im sending to some old machines) so you can > imagine the massive amounts of messages written to the console. I'd > like an option like --quiet or --hide-timeouts to stop this stuff. > > I might make a patch later on, but I thought I'd through this out > there in ccase someone has already done it or its being planned. Thank > you. > _______________________________________________ > Udpcast mailing list > Udpcast at udpcast.linux.lu > https://lll.lgl.lu/mailman/listinfo/udpcast > From Wladyslaw.Bodzek at cs.put.poznan.pl Tue Jun 27 02:13:34 2006 From: Wladyslaw.Bodzek at cs.put.poznan.pl (=?ISO-8859-2?Q?W=B3adys=B3aw_Bodzek?=) Date: Tue, 27 Jun 2006 02:13:34 +0200 Subject: [Udpcast] Feature Requests: named sessions and no timeout messages In-Reply-To: References: Message-ID: <44A0782E.8080500@cs.put.poznan.pl> >> I have two feature requests. >> >> The first is to have an option, something like --name, which would >> provide a 'name' for each 'session', so that if two people are using >> udpcast on the same network, they wont conflict with each other. I >> know they could just use different ports, but names seem easier than >> ports (and certain ports might be blocked or conflict with other >> programs) You can specify another port base for this kind of situations... (argument: --portbase ; search in man page for more info) Wladek From mikes at kuentos.guam.net Tue Jun 27 09:33:40 2006 From: mikes at kuentos.guam.net (Michael D. Setzer II) Date: Tue, 27 Jun 2006 17:33:40 +1000 Subject: [Udpcast] Feature Requests: named sessions and no timeout messages In-Reply-To: References: Message-ID: <44A16BF4.3152.3E540C4@mikes.kuentos.guam.net> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 In my case, I have found using the --max-bitrate=xxM as a way of greatly reducing this. I have one system in a lab that has a harddrive that doesn't keep up with the others (all same drives). Test on drive show no problems, but moving it from one system to another causes the error to move, so it is the drive. Happens when it is moving the large empty parts of the drive, where it has been cleared out. In this case the network is transferring more data than this drive can write. It will sometimes fall about 1GB behind the others. (1GB of Ram in systems). Using the max-bitrate reduces or eliminates the timeout messages, but does make the process take longer, since it limits the transmission when it could be writing faster. On 26 Jun 2006 at 20:17, D G Teed wrote: Date sent: Mon, 26 Jun 2006 20:17:39 -0300 (ADT) From: D G Teed Subject: Re: [Udpcast] Feature Requests: named sessions and no timeout messages To: Don Bright Copies to: udpcast at udpcast.linux.lu > > Actually the timeout messages are useful. If you are > imaging a bunch of machines at once, and one has > a flaky ethernet device which is slowing down the > process, the timeout provides info on which one is behind > and might better be yanked from the process to allow the > others to complete. > > But as an option, it could be useful to some people. > > --Donald Teed > > > On Mon, 26 Jun 2006, Don Bright wrote: > > > Dear UDP Casters, > > > > First let me say thank you for making this program. It has enabled me > > to completely get rid of Symantec Ghost and it's damnable boot > > floppies, as well as extremely hard to understand licensing > > arrangement (I was never sure if I had a legal copy or not, someone > > else at the workplace just gave me a copy of it, and I couldnt get any > > information on the license for it) > > > > I have two feature requests. > > > > The first is to have an option, something like --name, which would > > provide a 'name' for each 'session', so that if two people are using > > udpcast on the same network, they wont conflict with each other. I > > know they could just use different ports, but names seem easier than > > ports (and certain ports might be blocked or conflict with other > > programs) > > > > The second, is to have a command line option to stop the 'timeout' > > messages on the sender. I'm sending 7 GB of data and getting 1% > > timeout (maybe because im sending to some old machines) so you can > > imagine the massive amounts of messages written to the console. I'd > > like an option like --quiet or --hide-timeouts to stop this stuff. > > > > I might make a patch later on, but I thought I'd through this out > > there in ccase someone has already done it or its being planned. Thank > > you. > > _______________________________________________ > > Udpcast mailing list > > Udpcast at udpcast.linux.lu > > https://lll.lgl.lu/mailman/listinfo/udpcast > > > _______________________________________________ > Udpcast mailing list > Udpcast at udpcast.linux.lu > https://lll.lgl.lu/mailman/listinfo/udpcast > +----------------------------------------------------------+ Michael D. Setzer II - Computer Science Instructor Guam Community College Computer Center mailto:mikes at kuentos.guam.net mailto:msetzerii at gmail.com http://www.guam.net/home/mikes Guam - Where America's Day Begins +----------------------------------------------------------+ http://setiathome.berkeley.edu Number of Seti Units Returned: 19,471 Processing time: 32 years, 290 days, 12 hours, 58 minutes (Total Hours: 287,489) BOINC Seti at Home Total Credits 1378923.633697 -----BEGIN PGP SIGNATURE----- Version: PGP 6.5.8 -- QDPGP 2.61c Comment: http://community.wow.net/grt/qdpgp.html iQA/AwUBRKBStSzGQcr/2AKZEQJTNQCdEUPg1RlICYz7GTs56IOqw9FUeIgAoJge +LOUZXK5UFL7pdM045zUg2r0 =3/Zd -----END PGP SIGNATURE-----