Hi Alain,
I was studying the UDPCast source code for some experimental purposes. I have the following question.
1. The whole data to be transfered into is divided into slices which again contains a series of blocks to transfer. Can we consider the whole data to be transfered as a single slice ( By setting appropriate parameters in code) and what kind of performance issues we can expect if we do a change of this kind at code level.
Thanks in advance,
Sai
---------------------------------
Do you Yahoo!?
Y! Messenger - Communicate in real time. Download now.
The option of ipappend 1 in the default file and retransmission
of HELLOs in udp-sender (--rexmit-hello-interval) has been
valuable to getting udpcast working with the Dell notebooks
we have with Broadcom 5700 series ethernet.
Today, with a slightly newer broadcom chipset appearing in
the most recent shipment, we noticed that udp-receiver was
intermittantly not showing the "hit any button to start transfer"
message. With some trial and error I found that if I
watched the tail of /var/log/message on the receiver (server)
and waited for the messages on TX and RX flow control to
complete before running udp-receiver, it would always initiate
a good connection. If I had started the udp-receiver
prior to the TX/RX flow control appearing in the message log
(in which case there was no "hit any key" message),
I could ^C the receiver, run it again and it would signify
the ready state with 100% success.
In conclusion, we have a workaround of starting udp-receiver
after a few seconds past the client PXE machine booting and
showing the udp-sender status ready (but not yet "hit any key...").
Another solution would be if udp-receiver also supported
--rexmit-hello-interval. It isn't a flaw in the udpcast system
but a kludge for a network device that is proving itself to be
sluggish in initialization in general.
--Donald Teed
I downloaded your CD image and it worked fine until I used it on a pc with a
USB keyboard. These PCs are in the lab I am trying the program on. Do I need
to compile my own image using my own kernal? I am using debian 3.1 and cannot
find the required files as specified by the -k switch.
Please, let me know what I need to do.
Thanks,
AJ
Hello
I use udpcast with several computers. After duplicating one hard disk to the
others, i would like that the computers that received the data reboot
automatically. But i don't know how to do this because udpcast don't allow
us to do that with it's options.
I'm waiting for your advice
Aimé David
_________________________________________________________________
MSN Messenger : personnalisez votre messagerie instantanée !
http://g.msn.fr/FR1001/866
/Hi everybody
I used today the great online tool cast-o-matic to create a custom PXE initrd file.
//I pre-configurated every option to simplify the process of image distribution
(the standard initrd from the latest 2.6 kernel works fine for me).
The custom initrd seems to work (all the menu & options are skipped) but after displaying the usual
two lines :
udp-receiver 2005-02-26
compressed UDP receiver for /dev/hda at 10.10.40.64 on eth0
the next lines (received message, cap=...) never shows up like they did with the standard initrd.
When I check with the console shell I noticed that I can ping the udp-cast server and that the fdisk command
shows my ide disk /dev/hda geometry. So I don't know what I missed in the configuration options (see below).
I did my test on two differents IBM Thinkpad with different networks cards. The only errors I saw in the kernel startup
sequence are related to missing pcmcia cardbus module (there's no option for that in cast-o-matic stage 2). My network
card is on a mini-pci board anyway.
/
/Am I missing something (any tips will be appreciated) ?
Regards.
Bernard
--------------------
cast-o-matic options
--------------------
net modules 3c59x e100 e1000
language/keyboard Français/French
network driver Autodetected
network module parameters checked
use dhcp yes
use a disk module No
Chose disk driver No preconfiguration
Disk module parameters checked
udpcast port 9000
device to be copied /dev/hda
Additional udpcast command-line parameters checked
compression Lzop
transfer direction receiver
/
Jaco Kroon wrote:
> I find that libraries again have deps and have deps, so compiling
> statically might be a better solution. Not sure how much space you
> really save that way but it's deffinately worthwhile if it's only one
> executable.
>
> Then again, space is only really a problem when using floppy images.
Yeah I'm doing pxe-boot via gbit, so space is no issue. I statically
compiled setterm to a 523 k binary (!) :) and threw it on there, and
then did a setterm -b 0 in udpreceiver.pre
But no luck, it doesn't work. Is it a "weird" sort of terminal that
syslinux uses?
Lasse
Hi
The setup I'm udpcasting to is a lot of boxes with no keyboard attached.
So when udpcast blanks the console after a while I have no way of
following what's going on on a particular node. Of course I can always
check the sender, but I'd like to have a view of all the nodes aswell.
Usually I use "setterm -b 0" to achieve this. But the setterm command
doesn't seem to be included in busybox. Can I add the regular command if
I check it's lib-dependencies with ldd?
Or do any of you know of another way to achieve this. I thought about
disabling APM in the kernel maybe, that might do the trick. However I'm
not sure how I compile a new kernel for UDPcast
Lasse Riis
