I read the doc cmd.html, and did some test about --broadcast, IMHO, I
think the following doc in cmd.html should be fixed:
The following networking options should be supplied both on the
sender and the receivers:
This option should only be supplied on the sender.
udp-receiver: unrecognized option `--boradcast'
udp-receiver [--file file] [--pipe pipe] [--portbase portbase]
[--interface net-interface] [--log file] [--ttl time-to-live]
[--mcast-rdv-addr mcast-rdv-address] [--rcvbuf buf] [--nokbd]
[--exit-wait milliseconds] [--nosync] [--license]
--broadcast should only be used in udp-sender, Not with udp-receiver.
Therefore --braodcast should be moved to the session "The following
networking options should be supplied only on the sender:"
Steven Shiau <steven _at_ nchc org tw> <steven _at_ stevenshiau org>
National Center for High-performance Computing, Taiwan.
Public Key Server PGP Key ID: 9762755A
I found the same problem before.
> -----Original Message-----
> From: udpcast-bounces(a)udpcast.linux.lu [mailto:udpcast-
> bounces(a)udpcast.linux.lu] On Behalf Of Steven Shiau
> Sent: Friday, February 16, 2007 1:46 PM
> To: udpcast(a)udpcast.linux.lu
> Subject: [Udpcast] A bug in udpcast doc ?
> I read the doc cmd.html, and did some test about --broadcast, IMHO, I
> think the following doc in cmd.html should be fixed:
> Networking options
> The following networking options should be supplied both on the
> sender and the receivers:
> This option should only be supplied on the sender.
> udp-receiver --boradcast
> udp-receiver: unrecognized option `--boradcast'
> udp-receiver [--file file] [--pipe pipe] [--portbase portbase]
> [--interface net-interface] [--log file] [--ttl time-to-live]
> [--mcast-rdv-addr mcast-rdv-address] [--rcvbuf buf] [--nokbd]
> [--exit-wait milliseconds] [--nosync] [--license]
> --broadcast should only be used in udp-sender, Not with udp-receiver.
> Therefore --braodcast should be moved to the session "The following
> networking options should be supplied only on the sender:"
> Steven Shiau <steven _at_ nchc org tw> <steven _at_ stevenshiau org>
> National Center for High-performance Computing, Taiwan.
> Public Key Server PGP Key ID: 9762755A
> Udpcast mailing list
I used boot cd for updcast.
Yes, the new hdd in exactly the same size and have the same layout becouse i
used dd to get the same partition tables, and after that formated them.
But for now i only want to backup the boot partition, not the entirely hdd.
And i know the problem is on the backup method or file, becouse i have a
ghost image from the partiton and restored it without any problem, and
everything is fine.
If use the file make with udpcast, i get error checking filesystem ( chkdsk
). I'm don't blaming udpcast, becouse i know it's me the one don't know how
to do it.
Maybe the correct question is: is it possible to backup a partition, using
updcast, through a network and strore it on a file server? For your answears
i supose it is posible, wich steps you followed? or which option you use to
backup to a file and restore from a file?
On 2/15/07, Michael D. Setzer II <mikes(a)kuentos.guam.net> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> What exactly did you use to create the image file?
> Does the new hard drive have the same physical layout as the original
> in the way of heads and number of sectors per track?
> Did you do a partition image, or a disk image.
> You might want to look at g4l or g4u for imaging.
> G4L includes ntfsclone coption, which only copies the used data, but it
> require the NTFS partition to already exists.
> It is probable something missing from the MBR record.
> I use the g4l and make disk images of systems with 98, XP, and Linux on
> the 80GB drive, and it restores the images with no problems. NT and XP
> seem to be very picky on the disk layout.
> On 15 Feb 2007 at 17:50, Diego . wrote:
> > Hi,
> > I'm trying to make some kind of imageserver. I backed up my windows 2000
> boot partition to an
> > image file on the server. I restore it, without problems..everything is
> ok. But if i change hdd, o if
> > destroy partition and create a new one ( same size, same place ), i can
> restore the image but
> > windows won't boot. when i check filesystem y get some errors ( of
> course they weren't when i
> > backup the partition ). I even fixboot and mbr with the same result.
> > Anyone can helpme with some tip?
> > Thanks!!
> Michael D. Setzer II - Computer Science Instructor
> Guam Community College Computer Center
> Guam - Where America's Day Begins
> Number of Seti Units Returned: 19,471
> Processing time: 32 years, 290 days, 12 hours, 58 minutes
> (Total Hours: 287,489)
> BOINC TOTAL CREDITS
> Total Credits 2742633.750347
> Total Credits 510505.776350
> Total Credits 8633.726962
> -----BEGIN PGP SIGNATURE-----
> Version: PGP 6.5.8 -- QDPGP 2.61c
> Comment: http://community.wow.net/grt/qdpgp.html
> -----END PGP SIGNATURE-----
I'm trying to make some kind of imageserver. I backed up my windows 2000
boot partition to an image file on the server. I restore it, without
problems..everything is ok. But if i change hdd, o if destroy partition and
create a new one ( same size, same place ), i can restore the image but
windows won't boot. when i check filesystem y get some errors ( of course
they weren't when i backup the partition ). I even fixboot and mbr with the
Anyone can helpme with some tip?
I am testing UDP-sender.exe and UDP-receiver.exe under WinXP with
following commands. But a error (marked by red color) happens after the
server transfers data once. Under linux, I have never met this problem.
I am wonder if there is a bug?
C:\Documents and Settings\hwsun.PSL-AD\Desktop\UDPCast-run>udp-sender -f
t -P 5004 -M 22.214.171.124 --daemon-mode --nokbd --min-receivers 1
Using mcast address 126.96.36.199
UDP sender for test.txt at 10.81.112.185 on Intel(R) PRO/100 VE Network
on - Packet Scheduler Miniport (00-00-e2-5b-c7-66)
Broadcasting control to 188.8.131.52
New connection from 10.81.112.185 (#0) 00000009
Starting transfer: 00000009
bytes= 1 230 re-xmits=0000000 ( 0.0%) slice=0000 1
230 - 0
Disconnecting #0 (10.81.112.185)
bind socket to 10.81.112.185:5005 (Bad file descriptor)
C:\Documents and Settings\hwsun.PSL-AD\Desktop\UDPCast-run>udp-receiver
t.txt -P 5004 -M 184.108.40.206 --nokbd
UDP receiver for mytest.txt at 10.81.112.185 on Intel(R) PRO/100 VE
ection - Packet Scheduler Miniport (00-00-e2-5b-c7-66)
received message, cap=00000009
Connected as #0 to 10.81.112.185
Listening to multicast on 220.127.116.11
bytes= 1 230 ( 0.01 Mbps) 1 230
Mr. Haiwei Sun
Panasonic Singapore Laboratories Pte Ltd
I am curious whether there is an commandline option which could
instruct udp-receiver to exit after a certain amount of time without
any udp-sender activity or generally when the transfer process doesn't
At least I could not find anything in the documents.
We use udpcast together with PXE-boot and sometimes some machines are
simply not responding to the sender (why is yet unclear). After
manually restarting the machines it is usually the case that the
machines to be imaged are responding again and everything is well.
Unfortunately it could be the case that there are machines to be
imaged which are placed in locked rooms and so it is impossible to
restart them manually.
Have Latitude D620s - I can't make UDPcast bootdisks that support the
Broadcom 57xx Gigabit network card and Intel SATA drivers. I can't find
documentation to add these drivers manually. Any ideas?
I'm trying to create an initrd for udpcast with cast-o-matic. In the
first screen, I only chose sky2 gigagabit ethernet driver and the ahci
and piix SATA drivers. These files are actually present in the
generated initrd, but it seems the file /lib/modules/modules.info does
not include any SATA drivers. Could somebody check this please?
I will try,
De: Lluís Gras [mailto:firstname.lastname@example.org]
Enviada em: segunda-feira, 5 de fevereiro de 2007 20:33
Assunto: Re: [Udpcast] I can`t use sata
It seems that modules.info lacks information about kernel/drivers/ata
ns:/home/cosa/INITRD/lib/modules/18.104.22.168udpcast# cat ../modules.info | grep
I'have not tested, but one could try.
mv initrd initrd.gz
gunzip -d initrd.gz
cpio -i < ../initrd
Add information to modules.info from
modinfo -n kernel/drivers/ata/*
modinfo -d kernel/drivers/ata/*
some little script ...
repack initrd with
INITRD$ find . | cpio --quiet --dereference -o -H newc | gzip -9 >
or something similar.
Good Luck, great piece of software i love it ;-)
2007/2/5, Marcelo <marcelo(a)policamp.edu.br <mailto:email@example.com>
Sorry, I dont speak english very well!
I have tried to use modules sata on site, but it doesn`t work. How can I
put the driver into the image?
Udpcast mailing list
... en el país de los ciegos el tuerto es el rey y diciendo esto se arranco
un ojo ...