search for: jigdo

I've gone through the trouble (after some 10 rounds I finally have something I'm happy with) and generated jigdo/template files for CentOS 5.0 iso's (CD/DVD i386/x86_64) (and CentOS 4.4 while I was at it: CD/DVD/ServerCD SRPMS/i386/x86_64). (and I started on this before the thread about creating the DVD's from the CD's started ;-) ) They are available at: http://tcs.uj.edu.pl/~buildcentos/cen...

Hi Is there a jigdo image available for CentOS-5.3? Or is there a jigdo project for CentOS? Thanks Marcelo

Hi Ralph I received this e-mail from Fedora Infrastructure list. My problem at that moment was a proper syntax for the jigdo-file command. Using the their script as reference, I made a simpler one to test the command[1]. And it's working: newt (Linux) $pwd; ls -l *.jigdo *.template /users/newt2/mgarcia/iso/dvd -rw-r--r-- 1 mgarcia slocate 214226 May 13 13:44 CentOS-5.3-i386-bin-DVD.jigdo -rw-r--r-- 1 mgarcia sl...

When the update 1 iso's come out could jigdo templates also be released along with the bittorrent files? It would probably save a lot of bandwidth if bittorrent could be resumed on iso's rebuilt via jigdo from vast swathes of the iso's which most of us already have (the 4.0 packages and updates). Cheers, MaZe.

Hi folks, I've just finished rsyncing/downloading/jigdoizing the entire i386/x86_64 CentOS 4.2 distribution. If anyone is interested go to http://mirror.tcs.ii.uj.edu.pl/jigdo/ You'll need to edit the .jigdo file by hand to change the server section [Servers] CentOS42=file:/opt/mirrors/centos/4.2/ to point to a local mirror (file, http or ftp)...

Just tripped over this one today. $ rsync --no-motd rsync://alphageek.dyndns.org/slackware rsync: link_stat "." (in slackware) failed: No such file or directory (2) rsync error: some files could not be transferred (code 23) at main.c(1498) [receiver=3.0.1pre2] $ rsync --no-motd rsync://alphageek.dyndns.org/slackware/slackware-current drwxr-xr-x 4096 2008/03/26 01:30:27

Dear centos community, I was in the process of loading the latest 5.5 release of centos in a VMWARE ESX 4.1 host as my first virtual machine, suddenly while booting I got a panic error with the following on screen. Can someone point me in the right direction. This machine has 24 cores and I allocated 1 for Centos to use with 1024MB of memory. Any clues or workaround to solve this problem? Thank

...ion? What I have is method for recreating bit-for-bit identical image to the original, based on other image(s) containing files which are to be placed on the destination images, plus files unique to the destination image(s) and iso image header (part before first file). The idea is similar to the jigdo utility, but implementation (pure perl + some standard perl modules) different, and much more specialized. So, is that OK to send the scripts to the list for discussion? Best regards, Wojtek

...he Debian CD images that I'm producing. This looks like a good plan for the i386/amd64 images we make, so as to make them bootable from USB by default. However, it's likely to make things slightly more difficult in terms of producing the images themselves: we want to make them available via jigdo as well as via full download of the .iso files directly, so doing post-processing of the images after genisoimage is finished is less than ideal for us. However, as I'm one of the people with commit rights to cdrkit / genisoimage I could probably add support for creating isohybrid-style images...

Debian Squeeze, libvirt 0.8.3, qemu-kvm 0.15.5 After configuring the cd image the bios screen shows: (tested with virsh, virt-install and virt-manager) Starting SeaBIOS (version 0.5.1-20110523_174945-brahms) Booting from CD-Rom 65MB medium found (bzw. whatever size) Boot failed: Could not read from CDROM (code 000c) ... the cd images (debian6-cd1, debian6-netinst, debian6-buisnesscard) have

...then mount -o loop, and put my backups inside that, and then use rsync to sync that offsite. Presumably this will use much less virtual memory. The question is how quickly it would sync the two images. I imagine my problem with hard links will vanish. B. Create a filesystem image as above Use jigdo to keep the images in sync. C. Use md5sum and some home-grown scripts to decide what to transfer. I'm not keen on C. as basically it's implementing what I think rsync should be doing. btw the latest directory contains 1.5 Gbytes of data. The system is still calculating that today's...