Hi I'm wondering if there is a way to set the machine name
automatically after the broadcast. I heard that the last version of
Ghost do something like that. For the GNU/Linux boxen I can autoset
the hostname from a small script in init.d. I don't know much about
Windows networking. Is the hostname in some file that we can write to
by just mounting the partition? Do we have to mess with the registry?
All the boxes connect to a Samba PDC. Can I copy the machine accounts
and let them share the SID?
--
Yannick Gingras
Hi,
Is it possible that the Reboot system after udpcast? (only available
with full-featured shell) option is not working on the website at the
moment? We built various images lately but none of them reboot after
receiving an image.
Kind regards,
Hofkens Dale
Just noticed that 20060920 was released, so as usual, I compiled it in
my RedHat 9 Linux with gcc (GCC) 3.2.2 20030222 (Red Hat Linux 3.2.2-5).
I can not compile it successfully. However, udpcast-20060619 works.
Here is my procedure to compile version 20060920:
--------
~/tmp/udpcast/udpcast-20060920>./configure
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ANSI C... none needed
checking how to run the C preprocessor... gcc -E
checking for egrep... grep -E
checking whether gcc needs -traditional... no
checking for a BSD-compatible install... /usr/bin/install -c
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking target system type... i686-pc-linux-gnu
checking for an ANSI C-conforming const... yes
checking for inline... inline
checking for pthread_create in -lpthread... yes
checking for ANSI C header files... yes
checking for sys/wait.h that is POSIX.1 compatible... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking fcntl.h usability... yes
checking fcntl.h presence... yes
checking for fcntl.h... yes
checking limits.h usability... yes
checking limits.h presence... yes
checking for limits.h... yes
checking sys/ioctl.h usability... yes
checking sys/ioctl.h presence... yes
checking for sys/ioctl.h... yes
checking sys/time.h usability... yes
checking sys/time.h presence... yes
checking for sys/time.h... yes
checking arpa/inet.h usability... yes
checking arpa/inet.h presence... yes
checking for arpa/inet.h... yes
checking sys/param.h usability... yes
checking sys/param.h presence... yes
checking for sys/param.h... yes
checking for memory.h... (cached) yes
checking malloc.h usability... yes
checking malloc.h presence... yes
checking for malloc.h... yes
checking signal.h usability... yes
checking signal.h presence... yes
checking for signal.h... yes
checking netinet/in.h usability... yes
checking netinet/in.h presence... yes
checking for netinet/in.h... yes
checking winsock2.h usability... no
checking winsock2.h presence... no
checking for winsock2.h... no
checking termios.h usability... yes
checking termios.h presence... yes
checking for termios.h... yes
checking whether llseek declared in unistd.h... no
checking whether lseek64 declared in unistd.h... yes
checking for htons... yes
checking for an ANSI C-conforming const... (cached) yes
checking whether struct tm is in sys/time.h or time.h... time.h
checking return type of signal handlers... void
checking for atexit... yes
checking for on_exit... yes
checking for tcsetattr... yes
checking for lseek64... yes
checking for snprintf... yes
checking for 64-bit off_t... no
checking whether gcc supports loff_t type... yes
checking whether gcc supports offset_t type... no
checking whether gcc supports long long type... yes
configure: creating ./config.status
config.status: creating Makefile
config.status: creating config.h
config.status: config.h is unchanged
~/tmp/udpcast/udpcast-20060920>make
gcc -g -O2 -Wall -Wall -Wshadow -DBB_FEATURE_UDPCAST_FEC
-D_FILE_OFFSET_BITS=64 -DUSE_SYSLOG -DUSE_ASSEMBLER -O6 -DNO_BB -I. -I.
-c -o udp-receiver.o udp-receiver.c
gcc -g -O2 -Wall -Wall -Wshadow -DBB_FEATURE_UDPCAST_FEC
-D_FILE_OFFSET_BITS=64 -DUSE_SYSLOG -DUSE_ASSEMBLER -O6 -DNO_BB -I. -I.
-c -o socklib.o socklib.c
gcc -g -O2 -Wall -Wall -Wshadow -DBB_FEATURE_UDPCAST_FEC
-D_FILE_OFFSET_BITS=64 -DUSE_SYSLOG -DUSE_ASSEMBLER -O6 -DNO_BB -I. -I.
-c -o udpcast.o udpcast.c
gcc -g -O2 -Wall -Wall -Wshadow -DBB_FEATURE_UDPCAST_FEC
-D_FILE_OFFSET_BITS=64 -DUSE_SYSLOG -DUSE_ASSEMBLER -O6 -DNO_BB -I. -I.
-c -o receiver-diskio.o receiver-diskio.c
gcc -g -O2 -Wall -Wall -Wshadow -DBB_FEATURE_UDPCAST_FEC
-D_FILE_OFFSET_BITS=64 -DUSE_SYSLOG -DUSE_ASSEMBLER -O6 -DNO_BB -I. -I.
-c -o receivedata.o receivedata.c
receivedata.c:80: field `data_iov' has incomplete type
receivedata.c:134: confused by earlier errors, bailing out
make: *** [receivedata.o] Error 1
Anyone has same error ?
Thanks in advance.
--
Steven Shiau
Hi,
A suggestion about: http://udpcast.linux.lu/cast-o-matic/
Would it be possible to add javascript buttons to check/uncheck all drivers?
Here is my proposition:
===============================
<script type="text/javascript">
function checkAll(){
champs_input=document.getElementsByTagName('input');
for(i=0;i<champs_input.length;i++){
type=champs_input[i].getAttribute('type');
name=champs_input[i].getAttribute('name');
if(type=="checkbox"){
champs_input[i].checked=true;
}
}
}
function UncheckAll(){
champs_input=document.getElementsByTagName('input');
for(i=0;i<champs_input.length;i++){
type=champs_input[i].getAttribute('type');
name=champs_input[i].getAttribute('name');
if(type=="checkbox"){
champs_input[i].checked=false;
}
}
}
</script>
===============================
An to test:
===============================
<p><a href="javascript: checkAll();">Check All</a> / <a href="javascript:
UncheckAll();">Uncheck All</a></p>
===============================
Thank you very much!
--
Stéphane.
Hi All,
We are using Udpcast for some time now to clone pc's, and it's working
excellently, thanks for all the work that went into this project.
Recently we have changed hardware on our systems we clone, so i went to
the cast-o-matic site and made a new image.
We built a new client image on 20/9/2006 and download the new kernel
(2.6.17.13) to include on our pxe server.
We use LZOP compression, and this is what gives an error.
On the clients we receive the following message LZOP: Applet not found
as an error.
After that the system gives a message it wont reboot and ends.
We dont't have this error with gzip compression, but the image that
resides on our server is LZOP and i read on the udpcast website that
lzop is the preferred compression method. Could it be that we do
something wrong, or is there a bug in the latest udpcast
version/cast-o-matic site.
Thanks for looking into this.
Kind regards,
Hofkens Dale
-----------
Settings used :
pxe image
e100 , ata_piix
dhcp used
port 9000
no udpcast paramaters
compression : lzop
transfer direction : receiver
use ff shell
reboot system
do not blank screen
Hi,
I don't find any parameter to avoid blanking screen when buiding bootcd-image
offline with rpms...
Is it the default way it works?
Thanks!
--
Stéphane.
Hi,
I build udpcd.iso offline using rpm->alien->deb and lzop compression doesn't
seem to work.
(I use 20060917 version)
When I choose lzop, at the moment I press a key to launch opéreation, I get:
lzop: applet not found
And then it seems sot start but it send 0 bit and then print: Transfer
complete
/bin/lzop is present on live system running.
What do you think about it?
Thanks!
--
Stéphane.
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
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
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
