Udpcast August 2006

udpcast@udpcast.linux.lu

6 participants
10 discussions

Compiling udpcast on NetBSD 3.0
by elekktretterr＠exemail.com.au 17 Sep '06

17 Sep '06

As udpcast isnt in pkgsrc yet(no idea why, great imaging too), I tried to compile it by hand but I get this error: neptune# make cc -Wall -Wshadow -DBB_FEATURE_UDPCAST_FEC -D_FILE_OFFSET_BITS=64 -DUSE_SYSLOG -DUSE_ASSEMBLER -O6 -DNO_BB -c udp-receiver.c cc -Wall -Wshadow -DBB_FEATURE_UDPCAST_FEC -D_FILE_OFFSET_BITS=64 -DUSE_SYSLOG -DUSE_ASSEMBLER -O6 -DNO_BB -c socklib.c cc -Wall -Wshadow -DBB_FEATURE_UDPCAST_FEC -D_FILE_OFFSET_BITS=64 -DUSE_SYSLOG -DUSE_ASSEMBLER -O6 -DNO_BB -c udpcast.c cc -Wall -Wshadow -DBB_FEATURE_UDPCAST_FEC -D_FILE_OFFSET_BITS=64 -DUSE_SYSLOG -DUSE_ASSEMBLER -O6 -DNO_BB -c receiver-diskio.c cc -Wall -Wshadow -DBB_FEATURE_UDPCAST_FEC -D_FILE_OFFSET_BITS=64 -DUSE_SYSLOG -DUSE_ASSEMBLER -O6 -DNO_BB -c receivedata.c cc -Wall -Wshadow -DBB_FEATURE_UDPCAST_FEC -D_FILE_OFFSET_BITS=64 -DUSE_SYSLOG -DUSE_ASSEMBLER -O6 -DNO_BB -c udpr-negotiate.c cc -Wall -Wshadow -DBB_FEATURE_UDPCAST_FEC -D_FILE_OFFSET_BITS=64 -DUSE_SYSLOG -DUSE_ASSEMBLER -O6 -DNO_BB -c produconsum.c cc -Wall -Wshadow -DBB_FEATURE_UDPCAST_FEC -D_FILE_OFFSET_BITS=64 -DUSE_SYSLOG -DUSE_ASSEMBLER -O6 -DNO_BB -c fifo.c cc -Wall -Wshadow -DBB_FEATURE_UDPCAST_FEC -D_FILE_OFFSET_BITS=64 -DUSE_SYSLOG -DUSE_ASSEMBLER -O6 -DNO_BB -c log.c cc -Wall -Wshadow -DBB_FEATURE_UDPCAST_FEC -D_FILE_OFFSET_BITS=64 -DUSE_SYSLOG -DUSE_ASSEMBLER -O6 -DNO_BB -c statistics.c statistics.c: In function `printFilePosition': statistics.c:40: error: `loff_t' undeclared (first use in this function) statistics.c:40: error: (Each undeclared identifier is reported only once statistics.c:40: error: for each function it appears in.) statistics.c:40: error: parse error before "offset" statistics.c:41: error: `offset' undeclared (first use in this function) *** Error code 1 Stop. make: stopped in /usr/local/src/udpcast-20060619 Thanks to anyone who has a look at this. Cheers. Petr

2 1

Finding the slowpoke machine when ID numbers scroll away
by D G Teed 17 Sep '06

17 Sep '06

We have a bunch of notebooks to image and the guys aren't willing to wait for the occassional messed up notebook to image if it is dragging all of the others down. When one is showing as missing packets continually, they want to disconnect it and carry on with the others. The problem is that with a recent version of udpcast we are noticing that there are many "Press any key to start" messages filling the screen of each client, so we can't see what node number a client is. Is there any way to either: - eliminate the high number of repeated "press any key" appearances on the clients, or - get the node id of the udpcast client from the client console, or associate its udpast node number with an IP. --Donald Teed

3 4

typo in "busyboxUsage" ?
by Tom Carpenter 17 Sep '06

17 Sep '06

The "busyboxUsage" file in "udpcast-20060619.tar.gz" contains the following line: "\t--slice-sice\tinitial slice size\n" \ is "sice" a typo, i.e. should it read "size"? -Tom Carpenter

2 1

Windows Version corrupt on Website?
by Bastian Stock 17 Sep '06

17 Sep '06

Hello there, I hope I get no dubble Post :-) If so "SORRY" (I am new in Using Mailling Lists) today I Downloaded the latest Windows Version of udpcast from the Website. When I start the Programm on a PC with only one Network Interface it works fine (both sender and receiver). But when I start it on the same PC (a VMware) with two Network Interfaces the Programm crashes immediately. I tryed to bind the Interface with: "--interface 192.168.1.2" (Yes the IP is the correct) but this also dosent work. The only Message that appears is: "Udp-sender 2006-06-19" and for the receiver: "Udp-receiver 2006-03-25" If the Windows Error Reporting Service is active it will send a Error Report to MS. I hope this is only a small Error... When it works it is a really cool Programm! ---------------------------------- Greetings from Germany Bastian Stock

2 1

pxe images error
by Sara Nery 14 Sep '06

14 Sep '06

Hi all, I'm testing the pxe images on site to clone images, but it is bringing me this error on the receiver machine: "Warning: unable to open an inital console. Kernel panic - not syncing: No init found. Try passing init=option to kernel. " I'm using the same initrd and linux kernel on site. Sometime ago, I had the same error in a minilinux project I was working on. The problem was that I was using the busybox package instead of busybox-static. The busybox needs the glibc and the busyboox-static does not need. I wonder if this is the same error. Have anybody here passed the same problem?May somebody help me with this issue? Regards, Sara Nery ps - sorry for my poor english -- Sara Nery Silva Analista de Sistemas CEPEDI - Centro de Pesquisa e Desenvolvimento em Informatica e ELetroeletronica de Ilheus http://www.cepedi.org.br CEPEDI Webmail - http://webmail.cepedi.org.br/

2 1

doubt about IGMP robustness
by sooraj＠afilaindia.com 28 Aug '06

28 Aug '06

hi why IGMP Robustness default value is 2. It should not be 1 and it MUST not be zero is there in RFC . Please give explanation for this. Sooraj T

1 0

ATI AT-8024 does not register udpcast multicast group
by Tom Carpenter 28 Aug '06

28 Aug '06

I manage a lab of PCs running Windows XP Pro. All of the PCs are connected to an Allied Telesyn AT-8024 (firmware v3.3.1); IGMP snooping is enabled. To clone the systems in the lab I set up one PC then booted that PC from a floppy with the DOS version of Ghost server; similarly the systems to be cloned are booted from floppies with the Ghost client. (It's more automated than that, but that's the general scheme. FYI the version of Ghost is 7.5). I can see the server and clients join and leave multicast groups when logged into the AT-8024 and issuing the appropriate commands on the switch. If I substitute udpcast for Ghost, the switch never registers that either the server or the clients have joined a multicast group; messages on the udpcast server and clients indicate otherwise. If I then tell the server to send an image to the clients the network is flooded; this doesn't happen when using Ghost. I realize it's time to roll up my sleeves, break out our network monitoring laptop, and get to work...just thought I'd ask if anyone else has run into this or might have some suggestions. Thanks in advance, Tom Carpenter P.S. Don't know if this info is helpful, but when I start up the Ghost server the switch indicates the following: Multicast Group Member Port VLAN Host IP --------------- ----------- ---- ------- 01:00:5e:4d:00:00 21 1 172.30.22.120 When the first Ghost client is started, that information disappears and the following is displayed: Multicast Group Member Port VLAN Host IP --------------- ----------- ---- ------- 01:00:5e:4d:00:00 19 1 172.30.22.119 Left the group 01:00:5e:4d:13:5e 19 1 172.30.22.119 Upon starting the second Ghost client the switch displays the following: Multicast Group Member Port VLAN Host IP --------------- ----------- ---- ------- 01:00:5e:4d:13:5e 19 1 172.30.22.119 20 1 172.30.22.118

1 1

Windows Version corrupt on Website?
by Bastian Stock 13 Aug '06

13 Aug '06

Hello there, today I Downloaded the latest Windows Version of udpcast from the Website. When I start the Programm on a PC with only one Network Interface it works fine (both sender and receiver). But when I start it on the same PC (a VMware) with two Network Interfaces the Programm crashes immediately. I tryed to bind the Interface with: "--interface 192.168.1.2" (Yes the IP is the correct) but this also dosent work. The only Message that appears is: "Udp-sender 2006-06-19" and for the receiver: "Udp-receiver 2006-03-25" If the Windows Error Reporting Service is active it will send a Error Report to MS. I hope this is only a small Error... When it works it is a really cool Programm! ---------------------------------- Greetings from Germany Bastian Stock

1 0

IGMPv2 from command line
by Mike D 09 Aug '06

09 Aug '06

Is there an option from the command line to fall back to IGMPv2. I saw the option in Cast-o-Matic, but can't seem to find the option from the command line tool. Thank you, Mike Drew

2 1

kernal panic - not syncing : attempt to kill init
by Paul Atkins 04 Aug '06

04 Aug '06

Does anyone know a fix to this error when running udpcast on and hp dc7100. the program works perfectly on other hardware platforms we use but returns this error on the dc7100 thanks Paul Atkins IT Systems Developer Northumbria University Newcastle Upon Tyne TEL : 0191 2274659 FAX : 0191 2437630 ==== This e-mail is intended solely for the addressee. It may contain private and confidential information. If you are not the intended addressee, please take no action based on it nor show a copy to anyone. Please reply to this e-mail to highlight the error. You should also be aware that all electronic mail from, to, or within Northumbria University may be the subject of a request under the Freedom of Information Act 2000 and related legislation, and therefore may be required to be disclosed to third parties. This e-mail and attachments have been scanned for viruses prior to leaving Northumbria University. Northumbria University will not be liable for any losses as a result of any viruses being passed on.

1 0

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

Udpcast August 2006