Re: Bittorrent distribution of cdimages
On Monday 06 October 2003 11:10, Mattias Wadenstein wrote: release time when it would be repointed to another host. How about the hostname debcd-tracker.acc.umu.se? I feel that I need a zone where I can as local admin change the RR quickly and with a low ttl, so I guess the debian.org zone won't be an option. I guess bt-tracker.d.o could always be a CNAME if the project should look official. cheers -- vbi (IANADD, so sorry if I opened my mouth inappropriately) -- The ants in France, stay mainly on the plants. pgp0.pgp Description: signature
Bug in the FAQ
http://www.debian.org/CD/faq/ links to jigdo files of official releases and similar things at http://cdimage.debian.org/jigdo-area/current/jigdo/ This does not exist. http://cdimage.debian.org/debian-cd/jigdo/ is the place where they are and they are distributed to all the http/ftp servers that have adopted the new structure too. /Mattias Wadenstein -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
ia64 testers wanted for sarge cds
Thanks to the help of Richard Hirst who has made the script to make ia64 cds bootable and shown Jeff Bailey how to build debian-installer for ia64, Jeff has built a debian-installer image for ia64 and I have built both netinst and businesscard cds, now we need somebody that can test the cds to see if they boot, the installer is started, and if that works, then you can even do a debian-installer report for ia64 ;-) You can get the images from: http://gluck.debian.org/cdimage/testing/netinst/ia64/ Once we get this tested I'll schedule daily build of ia64 netinst and businesscard cd images and commit the script for debian-cd. Regards... -- Manty/BestiaTester - http://manty.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bittorrent distribution of cdimages
On Sun, 5 Oct 2003, Goswin von Brederlow wrote: Mattias Wadenstein [EMAIL PROTECTED] writes: I suspect I'm not the only one that thinks that this might be a good idea. I'm actually planning on offering this, what I'd like feedback on is how official it should be. mldonkey urls should also be provided. Thats even easier than bittorrent since its just an url containing a checksum. Ok, I've never heard of this so I'll take your word for it. Should I (or whoever is doing them) place the .torrents in the debian-cd directory on cdimage.debian.org so that they are mirrored all over the place and look official or should I place them in some unofficial/test- directory? When it comes to tracker I'm planning on using a dedicated dns name with a short ttl so we can repoint it at need if the machine can't handle it (I should be able to find a fast one though). It would be good if debian had an official tracker (doesn't need to have the image but it would be good). That would be easy, I could run one on cdimage.d.o at all times except release time when it would be repointed to another host. How about the hostname debcd-tracker.acc.umu.se? I feel that I need a zone where I can as local admin change the RR quickly and with a low ttl, so I guess the debian.org zone won't be an option. The debian-installer group is currently struggling to get autobuildable images. I guess it might be good to add the creation of a torrent and donkey file there too so every arch will autobuild those files too. Yeah, that might be nice. There will probably be a need to contribute wrapper scripts for this though so that the generation is less painful. /Mattias Wadenstein
Re: Bittorrent distribution of cdimages
On Mon, 6 Oct 2003, jason andrade wrote:
On Sun, 6 Oct 2002, Goswin von Brederlow wrote:
With bittorrent you have to have a running tracker. You also need
clients connected to the tracker that feed the data. That means each
mirror would have to run a bittorrent client on their local image.
does every mirror run a tracker ? or does each project run a tracker ?
or both ?
There needs only to be one tracker Debian-wide.
e.g do i run a tracker for just debian cd files ? or does someone in the
debian project run a 'debian wide' tracker with pointers to mirrors?
or can i as a mirror run a tracker for all the different files i'd
like to make available, not just within the debian cd archive ?
and can you outline how i run a BT client on local images given that:
o there are multiple releases
o there are multiple architectures within each release
o there are multiple images within each architecture
This is where it gets hard. Because besides running the tracker (which is
only done at a single point (... of failure)) each file needs to be
seeded in BT terminology. That means running the BT client when you
already have the file.
Basically the BT system is a metafile (called torrent) and a tracker. The
torrent is coupled to one file (or a fileset, but I'll assume single file
case here) that when a user first downloads the torrent via http then can
run the BT client on the torrent and have that generate the full file
(iso).
Seeding is done by running the BT client on that torrent when you already
have the full file. Here is the big problem, because the software isn't
quite up to conveniently seeding a large number of files. This is
something that needs to be done, /etc/init.d/bt{seeding,tracker}
{start,stop,reload,restart) with configfiles for what files to seed and
so.
I don't think it would be too hard to get a group to mirror the debian
CD images with bittorrent to their servers and leave the clients
running for the first weak or so till the big rush is over. If Debian
says they will only do jidgo and bittorrent the first week that should
give enough incentive.
We've said this before and it didn't work then. :) For once I'd like to
get the cdimages out in numbers even for those that want to use http
instead of some strange new software.
mirrors are based on the concept of really long lasting presence.. i.e
more than just a week or so. as a mirror i'm happy to contribute to this
new fangled 'bittorrent' system but so far there has been close to zero
documentation or examples i can find that allows me to use it in a 'server'
context as opposed to just a client.
The servers here would be seeds in BT terminology. They have the initial
data and makes sure that new clients can get all the data even if there
are no other users currently in the bittorent cloud of users. So basically
for bittorrent there would be use for a couple of servers/seeds but not in
as great numbers as the ftp/http/rsync mirrors because of the P2P nature
of the clients (they'll download missing pieces from eachother).
/Mattias Wadenstein
Re: Bittorrent distribution of cdimages
On Monday 06 October 2003 11:10, Mattias Wadenstein wrote: release time when it would be repointed to another host. How about the hostname debcd-tracker.acc.umu.se? I feel that I need a zone where I can as local admin change the RR quickly and with a low ttl, so I guess the debian.org zone won't be an option. I guess bt-tracker.d.o could always be a CNAME if the project should look official. cheers -- vbi (IANADD, so sorry if I opened my mouth inappropriately) -- The ants in France, stay mainly on the plants. pgpaS6EGUXj6z.pgp Description: signature
Bug in the FAQ
http://www.debian.org/CD/faq/ links to jigdo files of official releases and similar things at http://cdimage.debian.org/jigdo-area/current/jigdo/ This does not exist. http://cdimage.debian.org/debian-cd/jigdo/ is the place where they are and they are distributed to all the http/ftp servers that have adopted the new structure too. /Mattias Wadenstein
ia64 testers wanted for sarge cds
Thanks to the help of Richard Hirst who has made the script to make ia64 cds bootable and shown Jeff Bailey how to build debian-installer for ia64, Jeff has built a debian-installer image for ia64 and I have built both netinst and businesscard cds, now we need somebody that can test the cds to see if they boot, the installer is started, and if that works, then you can even do a debian-installer report for ia64 ;-) You can get the images from: http://gluck.debian.org/cdimage/testing/netinst/ia64/ Once we get this tested I'll schedule daily build of ia64 netinst and businesscard cd images and commit the script for debian-cd. Regards... -- Manty/BestiaTester - http://manty.net
intel
j ai bien compir
Re: ia64 testers wanted for sarge cds
I tried the netinstall CD image on an HP zx2000 and didn't get very far. Here are the two problems I saw that prevented me from going any further: 1. Selecting Detect a keyboard and select layout causes: An error or warning message was logged while running kbd-chooser SIGSEGV 2. Detect CDROM results in Unable to load module 'ide-probe-mod' for 'Linux IDE probe Driver'. On continue: Unable to load module 'ide-detect' for 'Linux IDE detection Driver' On continue: Unable to load module 'ide-disk' for 'Linux ATA DISK Driver On continue: Perform manual CD configuration? Your installation CD couldn't be mounted. That probably means that the CD is not yet inserted. If that's the case, just insert it and don't perform the manual configuration; the CD mount will be re-tried. If your CD was already in the drive, there was another problem; try the manual CD configuration. At this point I was stuck in a loop trying to mount cdrom. -- Khalid Santiago Garcia Mantinan wrote: Thanks to the help of Richard Hirst who has made the script to make ia64 cds bootable and shown Jeff Bailey how to build debian-installer for ia64, Jeff has built a debian-installer image for ia64 and I have built both netinst and businesscard cds, now we need somebody that can test the cds to see if they boot, the installer is started, and if that works, then you can even do a debian-installer report for ia64 ;-) You can get the images from: http://gluck.debian.org/cdimage/testing/netinst/ia64/ Once we get this tested I'll schedule daily build of ia64 netinst and businesscard cd images and commit the script for debian-cd. Regards... -- Manty/BestiaTester - http://manty.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] Khalid AzizLinux and Open Source Lab (970)898-9214Hewlett-Packard [EMAIL PROTECTED] Fort Collins, CO The Linux kernel is subject to relentless development - Alessandro Rubini
