make -j2 was failing because it started a make each for udp-receiver.1 and
make DESTDIR=/tmp install was failing because the DESTDIR glue wasn't
included. This is a standard part of autoconf and really helps when staging
Finally updated the gentoo packages associated with udpcast.
Keep up the great work,
Daniel Black <dragonheart(a)gentoo.org>
I use the udpcast to send packages to many clients (udp-receiver).
So my udp-receiver command line is:
#udp-receiver --interface tap0 --nokbd --file U2.wmv
Sender line is:
#udp-sender --nopointopoint --interface tap0 --log logudp --nokbd
--autostart 5 --file U2.wmv --full-duplex
My udp-receiver has two kinds of connection: satellite
links(low-latency) and local links (high-latency).
So Could I use the option --fullduplex on udp-sender line?
Thanks for any help,
Bruno Sampayo <bruno(a)samurai.com.br>
Tel.: +55(011) 50973005
Samurai Projetos Especiais
I am using two UDPCast cds (one sender, one receiver) to boot two Intel MacBooks in an attempt to clone one to the other.
Ok, it didn't exactly work out 100%
Turns out when I boot my custom UDPCast cds, the SATA Disk Driver and the Marvell Yukon Network chipset in the MacBook fight with each other for IRQ assignment, and UDPCast finally just turns one IRQ off. IRQ 10.
Meanwhile, I attached an external Microsoft USB 105-Key Keyboard to a MacBook to see if UDPCast would work with it and it did. But the "repeated ghost keystrokes" are still happening that plague the internal MacBook keyboard. So it seems that UDPCast is not playing well with the USB Controller in the MacBooks. It's not the keyboard. It's the controller. If I can identify the USB controller manufacturer, I might be able to insert the proper USB kernel module at boottime and finally be able to type into UDPCast after it boots. That would make it easier to guide through the menu-driven system that UDPCast uses in default-mode. It would also let me read the system boot log with the limited shell that I call up.
So as for my experiment, both MacBooks boot up into a state that is ready-to-go, but they can't see each other on the network. This is most likely due to the IRQ conflict I'm getting from the SATA drive vs. the Network chipset.
Network ports do light up on the switch I'm using, but the two computers won't see each other.
I've even tried two different switches in case one had some kind of internal circuit that blocked Multicast Packet Storms or something...
Has anyone tried UDPCast cloning of Intel-based MacBooks?
I am trying to clone a powerconnect 1435 using udpcast, but can't get it to
recognize my LSI Logic scsi disks with the cast-o-matic image.
I tried to create an initrd from the Fedora I have installed on one of the
nodes. The problem is then that not all modules are loaded at boot and, once
I load then by hand and see the scsi disk on /proc, I have no idea of how to
attach it at /dev
Shouldn't this be automatic? Or should I mknod the device?
I know this is not too specific to udpcast, but I've been out of the linux
world for sometime and am a bit lost here. Google wasn't very helpful
Thanks in advance for any suggestion/help/hint/pointer.
Hello. Thanks for developing udpcast. It almost compiles on my
mac. But I have to make a few small changes.
1.) the linker doesn't support the -Wl,-warn-common option
2.) what is malloc.h? It isn't needed.
3.) struct ifreq is variable size, so we must use _SIZEOF_ADDR_IFREQ
(), not pointer arithemetic
4.) some endian issues
Am Montag, 26. März 2007 17:55 schrieben Sie:
> Wolfgang Schmid wrote:
> > I've gopt the following problem:
> > I use cast-o-matic and do all the settings, choosing also the
> > ahci-sata-module, resp. (knoppix 5.2 lsmod tells me to take it). It even
> > says that it'll include this driver in the bootable cdrom-image:
> > "You have chosen the following disk modules: ahci"
> > So I download image and burn it.
> > But it doesn't work -
> > the cd boots correctly but the module isn't
> > used automatically and it also can't be found in the list the menue
> > offers :-(
> I have a suspicion that your device is not actually ahci, but a
> different SATA chipset. Could you try downloading the full udpcd.iso
> (which includes _all_ drivers...) and check whether it proposes a
> different SATA module?
> The menu system usually works as follows: it checks the installed
> hardware, and if this hardware is compatible with modules on the CD,
> only these are listed, (but you can get the full list by clicking on
> Others). If none match, the full list is diplayed immediately. But so
> far the "full" list had an issue in that not all directories were
> scanned for modules. However, that is is now fixed in today's version
> (20070326), now the full list is really full.
yea, that was what i meant
maybe its running now...
I'll try tomorrow (i've no access to the machines now)
> > I also to check all but none of the modules is included (other
> > preconfiguring issues work e.g. network module)
> > Best regards, Wolfgang
> > (Thanks for the quick reply)
Mag. Wolfgang Schmid
8732 Seckau 1
Tel.: 03514 5234 201
Fax: 03514 5234 205