From dragonheart at gentoo.org  Sat Apr  7 00:51:33 2007
From: dragonheart at gentoo.org (Daniel Black)
Date: Sat, 7 Apr 2007 08:51:33 +1000
Subject: [Udpcast] [PATCH] fixes parallel make & make DESTDIR=/tmp/xxx
	install
Message-ID: <200704070852.07758.dragonheart@gentoo.org>

make -j2 was failing because it started a make each for udp-receiver.1 and 
udp-sender.1.

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 
an install.

Finally updated the gentoo packages associated with udpcast.
http://packages.gentoo.org/packages/?category=net-misc;name=udpcast

Keep up the great work,

Cheers,
-- 
Daniel Black <dragonheart at gentoo.org>
Gentoo Foundation
-------------- next part --------------
A non-text attachment was scrubbed...
Name: udpcast-20070323-makefix.patch
Type: text/x-diff
Size: 1228 bytes
Desc: not available
URL: <http://www.udpcast.linux.lu/pipermail/udpcast/attachments/20070407/5c165412/attachment.patch>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://www.udpcast.linux.lu/pipermail/udpcast/attachments/20070407/5c165412/attachment.sig>

From ewschmid at web.de  Wed Apr 11 20:12:47 2007
From: ewschmid at web.de (Wolfgang & Elke Schmid)
Date: Wed, 11 Apr 2007 20:12:47 +0200
Subject: [Udpcast] Sata-modules
In-Reply-To: <200703271842.25332.ewschmid@web.de>
References: <200703231526.04101.dewschmid@web.de>
	<200703262015.59421.dewschmid@web.de>
	<200703271842.25332.ewschmid@web.de>
Message-ID: <200704112012.47235.ewschmid@web.de>

On Tuesday 27 March 2007 18:42:25 Wolfgang & Elke Schmid wrote:
> Am Montag, 26. März 2007 20:15 schrieb Wolfgang Schmid:
> > 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)
> > Regards
> >
> > > > 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)
> > >
> > > Regards,
> > >
> > > Alain
>
> Heureka!
> Now it works:
> 1.: the module (ahci) is within the menue-list
> 2.: the partition table is read correctly
> 3.: cloning is still to be tested (tomorrow)!
> Today i tried other machines with little success - it stopped and
> disconnected after a few MBs - many re-xmits! - probably big cable trouble
> :-(
Everthing worked out fine!
I had to clone 3 different kind of PCs and it worked supurbly!

One important thing to mention: 
Avoid connections to other machines (esp. servers) that don't have to be 
cloned - 
they can terribly slow down the cloning process (in my case ut was about the 
factor 15!!!). When I happend to remove the cable it really worked great!!!
Best regards and many thanks
Wolfgang Schmid



From Humberto.Varela at utsa.edu  Fri Apr 13 02:56:41 2007
From: Humberto.Varela at utsa.edu (Humberto J. Varela)
Date: Thu, 12 Apr 2007 19:56:41 -0500
Subject: [Udpcast] Intel Macbook
Message-ID: <CE6DCEEFD3F91D45B795D3D34F2C0F2507C902@OBSIDIAN1604.UTSARR.NET>

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?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.udpcast.linux.lu/pipermail/udpcast/attachments/20070412/cf07254a/attachment.html>

From stefan.jaeckel at wiwi.uni-halle.de  Wed Apr 18 14:31:19 2007
From: stefan.jaeckel at wiwi.uni-halle.de (Stefan Jaeckel)
Date: Wed, 18 Apr 2007 14:31:19 +0200
Subject: [Udpcast] switch_issue_using_udpcast
In-Reply-To: <0F90F42B-B9A7-4E1E-B30A-7DF03A359AF5@freeshell.org>
References: <0F90F42B-B9A7-4E1E-B30A-7DF03A359AF5@freeshell.org>
Message-ID: <200704181431.20650.stefan.jaeckel@wiwi.uni-halle.de>

Hello everybody,

udpcast works very fine on all of my switches, without one. udpcast worked 
also always very fine on that "special" switch (cisco 3560), but only on the 
last time it works not. That means: some time earlier, it worked on that 
switch without any problems , but only on last time it works not. i am only  
a "switchuser", that means that i am not be able to administrate the 
switches. the administrator of the switches said, that all switches have got 
the same configuration.

let me illustrate the network: all workgroup-switches (cisco 2950, 3560 - 
which being used with udpcast) are connected (cascaded) to a cisco 6509 
switching-factory with fibre-channel cables. all these components constitute 
a layer 2 network (ethernet). behind the cisco 6509 stands a cisco router 
(the next layer 3 instance, also connected with fibre channel, i don't know 
the type of this router), which manages the network- routing-protocolls, that 
means it should be also interesting for udpcast mc-routing. 

udpcast does not work on the one cisco 3560. if i use 2 nodes (1 sender , 1 
receiver -- unicast) on that switch it works very well, but with more than 2 
reciever-nodes (multicast) it doesn't work.  every modern cisco switch has 
got a so called "Multicast Forwarding Table" which binds all multicast ports 
(all systems from the "udp-receiver/sender-Multicastgroup" ) via 
igmp-snooping (some thing that can be done from the switch from layer 3) on 
one "Multicast-Mac-Address". this Multicast-Mac-Address would be anounced 
through the cisco switching-factory 6509 until the next cisco-router (layer 3 
instance) is reached. now the udp-sender establishes a connection to this 
MC-group (mac-adresses, binded ports on the switch) and begins to send the 
multcast-data. now the clients do not answer -- i think: maybe, it is a 
broadcast issue on that switch (vlan -- configuration), the udp-sender needs 
a message that a mc-packet is arrived correctly to the receiver (broadcast 
control sender<-->receiver from the program itself can't work correctly). the 
udp-reciever stalles and the sender prints all the timouts from the 
receivers) -- could this be the issue here? Or the routing itself on the next 
layer 3 instance -- i mean, that the layer 3 could not route the mc-pakets to 
the given mc-adress? or the "Multicast Forwarding Table" can only register 1 
port (receiver) for multicasting?

Here is the output from the sender:

(two receivers, it works not):

Udp-sender 2003-08-31
Using mcast address 237.48.205.71
UDP sender for (stdin) at 141.48.205.71 on eth0
Broadcasting control to 141.48.205.255
New connection from 141.48.205.132  (#0) 00000019
Ready. Press any key to start sending data.
New connection from 141.48.205.131  (#1) 00000019
Ready. Press any key to start sending data.
Starting transfer: 00000019
bytes=        570 752 re-xmits=000000 (  0.0%) slice=0056  73 709 551 615 -   
1
Timeout notAnswered=[0,1] notReady=[0,1] nrAns=0 nrRead=0 nrPart=2 avg=7815
Timeout notAnswered=[0,1] notReady=[0,1] nrAns=0 nrRead=0 nrPart=2 avg=7815
Timeout notAnswered=[0,1] notReady=[0,1] nrAns=0 nrRead=0 nrPart=2 avg=7815
Timeout notAnswered=[0,1] notReady=[0,1] nrAns=0 nrRead=0 nrPart=2 avg=7815
Timeout notAnswered=[0,1] notReady=[0,1] nrAns=0 nrRead=0 nrPart=2 avg=7815
Timeout notAnswered=[0,1] notReady=[0,1] nrAns=0 nrRead=0 nrPart=2 avg=7815
Timeout notAnswered=[0,1] notReady=[0,1] nrAns=0 nrRead=0 nrPart=2 avg=7815
Timeout notAnswered=[0,1] notReady=[0,1] nrAns=0 nrRead=0 nrPart=2 avg=7815
Timeout notAnswered=[0,1] notReady=[0,1] nrAns=0 nrRead=0 nrPart=2 avg=7815
Timeout notAnswered=[0,1] notReady=[0,1] nrAns=0 nrRead=0 nrPart=2 avg=7815
Timeout notAnswered=[0,1] notReady=[0,1] nrAns=0 nrRead=0 nrPart=2 avg=7815
Timeout notAnswered=[0,1] notReady=[0,1] nrAns=0 nrRead=0 nrPart=2 avg=7815
Timeout notAnswered=[0,1] notReady=[0,1] nrAns=0 nrRead=0 nrPart=2 avg=7815
Timeout notAnswered=[0,1] notReady=[0,1] nrAns=0 nrRead=0 nrPart=2 avg=7815
Timeout notAnswered=[0,1] notReady=[0,1] nrAns=0 nrRead=0 nrPart=2 avg=7815
Timeout notAnswered=[0,1] notReady=[0,1] nrAns=0 nrRead=0 nrPart=2 avg=7815
Timeout notAnswered=[0,1] notReady=[0,1] nrAns=0 nrRead=0 nrPart=2 avg=7815
Timeout notAnswered=[0,1] notReady=[0,1] nrAns=0 nrRead=0 nrPart=2 avg=7815
Timeout notAnswered=[0,1] notReady=[0,1] nrAns=0 nrRead=0 nrPart=2 avg=7815
Timeout notAnswered=[0,1] notReady=[0,1] nrAns=0 nrRead=0 nrPart=2 avg=7815
Timeout notAnswered=[0,1] notReady=[0,1] nrAns=0 nrRead=0 nrPart=2 avg=7815
Timeout notAnswered=[0,1] notReady=[0,1] nrAns=0 nrRead=0 nrPart=2 avg=7815
Timeout notAnswered=[0,1] notReady=[0,1] nrAns=0 nrRead=0 nrPart=2 avg=7815
Timeout notAnswered=[0,1] notReady=[0,1] nrAns=0 nrRead=0 nrPart=2 avg=7815
Timeout notAnswered=[0,1] notReady=[0,1] nrAns=0 nrRead=0 nrPart=2 avg=7815
Timeout notAnswered=[0,1] notReady=[0,1] nrAns=0 nrRead=0 nrPart=2 avg=7815
Timeout notAnswered=[0,1] notReady=[0,1] nrAns=0 nrRead=0 nrPart=2 avg=7815
Timeout notAnswered=[0,1] notReady=[0,1] nrAns=0 nrRead=0 nrPart=2 avg=7815
Timeout notAnswered=[0,1] notReady=[0,1] nrAns=0 nrRead=0 nrPart=2 avg=7815
Timeout notAnswered=[0,1] notReady=[0,1] nrAns=0 nrRead=0 nrPart=2 avg=7815
Timeout notAnswered=[0,1] notReady=[0,1] nrAns=0 nrRead=0 nrPart=2 avg=7815
Timeout notAnswered=[0,1] notReady=[0,1] nrAns=0 nrRead=0 nrPart=2 avg=7815
Timeout notAnswered=[0,1] notReady=[0,1] nrAns=0 nrRead=0 nrPart=2 avg=7815
Timeout notAnswered=[0,1] notReady=[0,1] nrAns=0 nrRead=0 nrPart=2 avg=7815
Timeout notAnswered=[0,1] notReady=[0,1] nrAns=0 nrRead=0 nrPart=2 avg=7815
Timeout notAnswered=[0,1] notReady=[0,1] nrAns=0 nrRead=0 nrPart=2 avg=7815
Timeout notAnswered=[0,1] notReady=[0,1] nrAns=0 nrRead=0 nrPart=2 avg=7815
Timeout notAnswered=[0,1] notReady=[0,1] nrAns=0 nrRead=0 nrPart=2 avg=7815
Timeout notAnswered=[0,1] notReady=[0,1] nrAns=0 nrRead=0 nrPart=2 avg=7815
Timeout notAnswered=[0,1] notReady=[0,1] nrAns=0 nrRead=0 nrPart=2 avg=7815
Timeout notAnswered=[0,1] notReady=[0,1] nrAns=0 nrRead=0 nrPart=2 avg=7815
Timeout notAnswered=[0,1] notReady=[0,1] nrAns=0 nrRead=0 nrPart=2 avg=7815
Timeout notAnswered=[0,1] notReady=[0,1] nrAns=0 nrRead=0 nrPart=2 avg=7815
Timeout notAnswered=[0,1] notReady=[0,1] nrAns=0 nrRead=0 nrPart=2 avg=7815
Timeout notAnswered=[0,1] notReady=[0,1] nrAns=0 nrRead=0 nrPart=2 avg=7815
Timeout notAnswered=[0,1] notReady=[0,1] nrAns=0 nrRead=0 nrPart=2 avg=7815
Timeout notAnswered=[0,1] notReady=[0,1] nrAns=0 nrRead=0 nrPart=2 avg=7815
Timeout notAnswered=[0,1] notReady=[0,1] nrAns=0 nrRead=0 nrPart=2 avg=7815
Timeout notAnswered=[0,1] notReady=[0,1] nrAns=0 nrRead=0 nrPart=2 avg=7815

---------------------------------------------------------------------------

(one receiver, it works):

Udp-sender 2003-08-31
Using mcast address 237.48.205.71
UDP sender for (stdin) at 141.48.205.71 on eth0
Broadcasting control to 141.48.205.255
New connection from 141.48.205.131  (#0) 00000019
Ready. Press any key to start sending data.
Starting transfer: 00000019
bytes=     88 042 864 re-xmits=000000 (  0.0%) slice=0056  73 709 551 615 -   
0
------------------------------------------------------------------------------------

I hope someone can help me out or give me a hint -- and sorry for my bad 
english!

Best Greatings

Stefan Jäckel




From lasaro at gmail.com  Tue Apr 24 09:57:18 2007
From: lasaro at gmail.com (Lasaro Camargos)
Date: Tue, 24 Apr 2007 09:57:18 +0200
Subject: [Udpcast] Problem with SAS disk
Message-ID: <c16fb9f10704240057g79e4b25dra221caf7477e8e0c@mail.gmail.com>

Hi all.

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
either.

Thanks in advance for any suggestion/help/hint/pointer.

lasaro
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.udpcast.linux.lu/pipermail/udpcast/attachments/20070424/94a90259/attachment.html>

From dteed at artistic.ca  Tue Apr 24 15:31:51 2007
From: dteed at artistic.ca (D G Teed)
Date: Tue, 24 Apr 2007 10:31:51 -0300 (ADT)
Subject: [Udpcast] Problem with SAS disk
In-Reply-To: <c16fb9f10704240057g79e4b25dra221caf7477e8e0c@mail.gmail.com>
References: <c16fb9f10704240057g79e4b25dra221caf7477e8e0c@mail.gmail.com>
Message-ID: <Pine.LNX.4.64.0704241022400.31709@artistic.localdomain.domain>


You mention Fedora initrd.   I would stick with vanilla
kernel materials to work with this.  Alain provides
tools to generate kernel images and initrd files
besides cast-o-matic.  Have you looked at that?  There
is no need to mknod device files these days since
udev and 2.6 kernels dynamically generate /dev contents
as required by drivers.

Perhaps the challenge is, how do you get the LSI logic card
working with something other than Fedora?  Did the hardware
vendor only supply a binary module or do you see it supported
in the latest vanilla Linux kernels?

--Donald Teed


On Tue, 24 Apr 2007, Lasaro Camargos wrote:

> Hi all.
>
> 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
> either.
>
> Thanks in advance for any suggestion/help/hint/pointer.
>
> lasaro
>


From bruno at samurai.com.br  Mon Apr 30 17:01:09 2007
From: bruno at samurai.com.br (Bruno Sampayo)
Date: Mon, 30 Apr 2007 12:01:09 -0300
Subject: [Udpcast] Option --full-duplex
Message-ID: <463604B5.4070308@samurai.com.br>

Hi,
    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 Sampayo <bruno at samurai.com.br>
Tel.: +55(011) 50973005
Engenharia
Samurai Projetos Especiais



From joelbryan.juliano at gmail.com  Mon Apr 30 23:47:08 2007
From: joelbryan.juliano at gmail.com (Joel Bryan Juliano)
Date: Tue, 1 May 2007 05:47:08 +0800
Subject: [Udpcast] Option --full-duplex
In-Reply-To: <463604B5.4070308@samurai.com.br>
References: <463604B5.4070308@samurai.com.br>
Message-ID: <b9fadc470704301447u7f72f61fx66358b2daa1bd934@mail.gmail.com>

I've been experimenting too on full-duplex mode in around 30 computers
in our university, and what I have noticed that if any of those PC's
doesn't support full-duplex, it really degrades the performance of
file-transfer for other networks.

On 4/30/07, Bruno Sampayo <bruno at samurai.com.br> wrote:
> Hi,
>     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 Sampayo <bruno at samurai.com.br>
> Tel.: +55(011) 50973005
> Engenharia
> Samurai Projetos Especiais
>
> _______________________________________________
> Udpcast mailing list
> Udpcast at udpcast.linux.lu
> https://lll.lgl.lu/mailman/listinfo/udpcast
>


-- 
MAILING-LIST SEND: boom!! I'm immortalize!