debian-cd CVS back online
Hello everyone, the debian-cd CVS repository is back online (after a check of its integrity). Please commit any change that you postponed until now. Cheers, -- Raphaël Hertzog -+- http://www.ouaza.com Formation Linux et logiciel libre : http://www.logidee.com Earn money with free software: http://www.geniustrader.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: debian-cd CVS back online - new jigdo fallback generation feature
On Thu, Dec 18, 2003 at 10:45:15AM +0100, Raphael Hertzog wrote: > the debian-cd CVS repository is back online (after a check of its > integrity). Thanks, Raphaël! I've just committed some code which makes the generation of fallback mirrors much easier. Furthermore, it produces relative template URLs in jigdo files by default. However, Phil, this /might/ break your publish_cds script - it is intended to replace publish_cds. With this feature, you can make debian-cd generate a directory with fallback links not after, but *during* template generation. This is done with jigdo-file's --match-exec switch, which executes a user-defined command whenever a file is found in the image. Advantages over publish_cds: Better integrated into debian-cd, less of a hack. ;) The following things in the default CONF.sh have changed: # HTTP/FTP URL for directory where you intend to make the templates # available. You should not need to change this; the default value "" # means "template in same dir as the .jigdo file", which is usually # correct. If it is non-empty, it needs a trailing slash. "%ARCH%" # will be substituted by the current architecture. #export JIGDOTEMPLATEURL="" # # Name of a directory on disc to create data for a fallback server in. # Should later be made available by you at the URL given in # JIGDOFALLBACKURLS. In the directory, two subdirs named "Debian" and # "Non-US" will be created, and filled with hard links to the actual # files in your FTP archive. Because of the hard links, the dir must # be on the same partition as the FTP archive! If unset, no fallback # data is created, which may cause problems - see README. #export JIGDOFALLBACKPATH="$(OUT)/snapshot/" # # Space-separated list of label->URL mappings for "jigdo fallback # server(s)" to add to .jigdo file. If unset, no fallback URL is # added, which may cause problems - see README. #export JIGDOFALLBACKURLS="Debian=http://myserver/snapshot/Debian/ Non-US=http://myserver/snapshot/Non-US/"; # # Space-separated list of "include URLs" to add to the .jigdo file. # The included files are used to provide an up-to-date list of Debian # mirrors to the jigdo _GUI_application_ (_jigdo-lite_ doesn't support # "[Include ...]"). export JIGDOINCLUDEURLS="http://cdimage.debian.org/debian-cd/debian-servers.jigdo"; # # $JIGDOTEMPLATEURL and $JIGDOINCLUDEURLS are passed to # "tools/jigdo_header", which is used by default to generate the # [Image] and [Servers] sections of the .jigdo file. You can provide # your own script if you need the .jigdo file to contain different # data. #export JIGDOSCRIPT="myscript" Additional info in the README: About jigdo "fallback servers": jigdo works by downloading individual packages and other files from a normal Debian mirror, and using them to regenerate a CD/DVD image. However, the content of Debian mirrors changes over time, files are added and removed. But jigdo must have access to all files needed for the image it has to regenerate, even those that have been removed from the normal Debian mirrors. A fallback server contains a backup of the Debian FTP space for the moment the .jigdo files were generated. This backup is made available under a certain URL which is written to the .jigdo files. jigdo will *only* revert to the fallback server after an unsuccessful attempt to retrieve a file from the normal user-selected Debian mirror, so the bandwidth requirements are modest. A fallback is even necessary for .jigdo files of the stable release, because some files (typically documentation or boot floppies) can change at any time. debian-cd allows you to automatically create a directory on disc which is suitable for use as a fallback mirror. It is populated with hard links to the archive contents. In CONF.sh, simply supply as JIGDOFALLBACKPATH the name of the directory, and as JIGDOFALLBACKURLS the URLs under which it will be made available (two separate URLs are necessary, one for "Debian" and one for "Non-US"). Hopefully I haven't broken debian-cd by committing this, but it seems to work fine judging from my tests on farbror. Cheers, Richard -- __ _ |_) /| Richard Atterer | GnuPG key: | \/¯| http://atterer.net | 0x888354F7 ¯ '` ¯ pgp0.pgp Description: PGP signature
testing netinst
Hi When can I download the testing netinst again? Your servers has been down for quite a long time now. I’ve tried searching some other places but with no luck, I’ve even tried with my friends but they haven’t kept the files. Hope you can solve this for me since I would love to try Debian during the Christmas holiday. Jonas Dahlborg [EMAIL PROTECTED]
Howto burn CDrom from ISO Files for UltraSparcIIi
Is there some one knowing haow to burn cdroms from the iso files for an UltraSparcIIi, please Thank you = J2EE Architect Robert Ghaloustians Mobile : (33) 0681458749 Phone : (33) 0143285923 http://www.rvcmla.org __ Do you Yahoo!? New Yahoo! Photos - easier uploading and sharing. http://photos.yahoo.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: debian-cd CVS back online - new jigdo fallback generation feature
At Thu, 18 Dec 2003 11:37:33 +0100, Richard Atterer <[EMAIL PROTECTED]> wrote: > > [1 ] > On Thu, Dec 18, 2003 at 10:45:15AM +0100, Raphael Hertzog wrote: > > the debian-cd CVS repository is back online (after a check of its > > integrity). > > Thanks, Raphaïl! > > I've just committed some code which makes the generation of fallback > mirrors much easier. Furthermore, it produces relative template URLs in > jigdo files by default. > > However, Phil, this /might/ break your publish_cds script - it is intended > to replace publish_cds. > > With this feature, you can make debian-cd generate a directory with > fallback links not after, but *during* template generation. This is done > with jigdo-file's --match-exec switch, which executes a user-defined > command whenever a file is found in the image. Fine, publish_cds only replaces what's in there already, so I can either remove that code, or make it so that the replacement is also relative. I still need publish CDs to move the images from the staging area to the published area, and generate the MD5SUMS files, but it would become pretty trivial if it didn't have to do the snapshot. > Advantages over publish_cds: Better integrated into debian-cd, less of a > hack. ;) The nice thing about setting it at publish time is that you can run publish_cds with a version number of "pre-release-test" say, and if it works, re-run it with "3.X_rY" on the same images, with no oportunity to screw up. ;-) Not that I do that sort of test, now that publish_cds works. Oh the other thing that you may not have noticed is that I have a hacked up version of publish_cds, called build_snapshot, that I run on raff to build the matching snapshot for us.cdimage.d.o. Since the bulk of fallback requests go to raff, I don't see the nasty hack going away too soon I'm afraid :-/ I should tidy build_snapshot up, take the funcionality out of publish_cds, and put build_snapshot into CVS really, so others can build snapshots (although I'm not sure how useful that is, given that there are only two places that the jigdos point at) Cheers, Phil. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: debian-cd CVS back online - new jigdo fallback generation feature
At Thu, 18 Dec 2003 11:37:33 +0100, Richard Atterer <[EMAIL PROTECTED]> wrote: > > [1 ] > On Thu, Dec 18, 2003 at 10:45:15AM +0100, Raphael Hertzog wrote: > > the debian-cd CVS repository is back online (after a check of its > > integrity). > > Thanks, Raphaïl! > > I've just committed some code which makes the generation of fallback > mirrors much easier. Furthermore, it produces relative template URLs in > jigdo files by default. > > However, Phil, this /might/ break your publish_cds script - it is intended > to replace publish_cds. > > With this feature, you can make debian-cd generate a directory with > fallback links not after, but *during* template generation. This is done > with jigdo-file's --match-exec switch, which executes a user-defined > command whenever a file is found in the image. Fine, publish_cds only replaces what's in there already, so I can either remove that code, or make it so that the replacement is also relative. I still need publish CDs to move the images from the staging area to the published area, and generate the MD5SUMS files, but it would become pretty trivial if it didn't have to do the snapshot. > Advantages over publish_cds: Better integrated into debian-cd, less of a > hack. ;) The nice thing about setting it at publish time is that you can run publish_cds with a version number of "pre-release-test" say, and if it works, re-run it with "3.X_rY" on the same images, with no oportunity to screw up. ;-) Not that I do that sort of test, now that publish_cds works. Oh the other thing that you may not have noticed is that I have a hacked up version of publish_cds, called build_snapshot, that I run on raff to build the matching snapshot for us.cdimage.d.o. Since the bulk of fallback requests go to raff, I don't see the nasty hack going away too soon I'm afraid :-/ I should tidy build_snapshot up, take the funcionality out of publish_cds, and put build_snapshot into CVS really, so others can build snapshots (although I'm not sure how useful that is, given that there are only two places that the jigdos point at) Cheers, Phil. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Status of the images for CDs and DVDs
Santiago Garcia Mantinan wrote: > I'd like to comment on the bug we had with the debian-installer beta-1 cds, > which weren't bootable on some machines, for what I saw, this was not > isolinux fault, the businesscard cds were carrying the same isolinux and had > been made using the very same isolinux options and were not failing, farther > more, the netinst images made prior or after the beta-1 seem to work again. > I'd like to get this tested by some other people than me, by downloading the > daily netinst images we are producing now and testing them in one of the > machines that didn't want to boot out of the beta-1 cds. Maybe we could send out a mail to everyone who filed an install report of failure, and see if they can reproduce the failure, and also make sure they didn't produce a CD with a .iso file on it or similar mistake. -- see shy jo signature.asc Description: Digital signature
Devenir un site mirroir Debian au Senegal
Je compte mettre en place un site mirroir debian au Sénégal dans le cadre de la promotion des logiciels libres au Sénégal. Pour rallier le maximum de personnes dans ce projet, il m'a semblé nécessaire de spécialiser la distribution linux car le Sénégal est un tout petit pays dans ce monde du libre et nous ne pouvons pas nous disperser dans ce domaine. Bien entendu, tout le monde, au Sénégal, installe Redhat parce que c'est une distribution qui permet très rapidement de se bomber le torse en clamant tout haut qu'on sait installer "linux" mais je reste persuadé que Debian nous permet d'élever le niveau au Sénégal et plus particulièrement dans les centres éducatifs pour que demain des sénégalais apportent leurs contributions dans ce monde du libre. Dans ce cadre, il me semble nécessaire d'installer un site mirroir Debian au Sénégal pour assurer le "monopole" de Debian. Ainsi, je cherche un support pour la mise en place de ce site mirroir : les caractéristiques de la(les) machine(s) (je fournis) le débit minimal conseillé de la liaison Internet (je fournis également) et le support à la config (je suis un niewbie d'un mois). Merci d'avance ! _ MSN Messenger : discutez en direct avec vos amis ! http://www.msn.fr/msger/default.asp -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: New version
On Wed, 17 Dec 2003, Jayendran JR wrote: > Hello, > > I noticed that the current ISOs for Debian are nearly a year old > (Dec 2002) though there are patches available. Could you please > clarify if any new version is about to be released so that I can > download the newer ISOs instead of downloading the older ones > and applying patches. Do download Debian Woody 3.0 r2 images. It is the second revision to Woody 3.0 and was released just a few weeks ago. Regards, -- Honza Houstek -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Help me
On Tue, 16 Dec 2003, Bruno Augusto wrote: > I have the image of debian in my computer. It has a iso extension and I > do no how can I procede to do a particion in my computer and extract > this file, and so run the linux. If it has .iso extention, it's probably a CD image. If it's a debian install CD image, you should burn it. After that you can install Debian from the CD (or CDs). -- Honza Houstek -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
unneccessary files on sarge netinst cds and other problems
I hope to get the netinst CDs to a size that can be used with d-i on a 128 MB USB memory stick again. It's currently too big now. There's a lot of cruft on there -- - The following packages are present on the netinst CD, but are not installed as part of the base system, and so are not really needed on it. Most notable is all the MTAs; exim4 is the default MTA and only it is needed. Simularly, we only need one awk, not three, only one inetd, not two, only one init system, not two. exim libldap2 libdb4.1 (perl uses 4.0 which is also present) gawk original-awk masqmail courier-base courier-authdaemon courier-mta exim4-daemon-heavy inetutils-inetd debconf-english file-rc esmtp nullmailer postfix sendmail ssmtp m4 - Many many udebs are present on the netinst CD, but will not be used by d-i, or are part of the d-i initrd, and so only take up space on the CD. I have attached two commented lists of these udebs. - The highly confusing diagrams in README.{txt,html} about setting up apt are all unnecessary; the installer sets up apt for the user. - The README.mirrors.{txt,html} is not particularly useful, since the debian installer will walk the user through setting up apt to use a mirror. - The README.non-US, becauses being very outdated (says we cannot export ssh for example), is useless as this CD contains no non-US items, and I doubt any for sarge will, as non-us is essentially now for oprhaned software and a very few packages with patent problems. - The doc/install directory is pretty much useless, since it documents the boot floppys and not d-i. d-i has not finished its documentation, but I suppose you could replace all this stuff with our INSTALLATION-HOWTO document for now. - Much of the other stuff in the doc/ directory is only of use to developers and sociologist (constitution.txt), is better documented on the web (bug-*, mailing-lists.txt), does not apply to this release of debian (dedication-2.2*), does not apply to this CD (source-unpack.txt; no source here), would better be shipped as a debian package (debian-keyring.tar.gz). - With isolinux, the /install/cdrom.gz is used, which means that /install/cdrom-image.img is useless, and it wastes 2.9 mb. - /install/floppy-initrd.gz is 100% useless - /tools/README.tools documents directories that do not exist. The /tools/REAMDE seems sufficient without README.tools. - /tools/src seems useless, why include source on a minimal netinst CD? - Contents-i386.gz is huge, and confusingly documents files that are in packages not on the CD. I say remove it. - The dists/sarge/contrib directory exists, but has only empty Packages files etc in it. The installer does not use or enable contrib, this should be removed from the netinst cds, which should never need to have non-free or contrib packages on thhem. - dists/sarge/main/source exists, but is empty. If there is not source on a CD, the directory should not be present. - I don't get the point of having both Packages and Packages.gz on the same CD. We somehow save space by including a duplicate compressed copy? All tools should be able to deal with uncompressed Packages files, or, better, compressed ones. Other problems: - The d-i syslinux help screens are not used. You'll find these inside our cdrom-image.img file as distributed by the d-i project. The current help screens do not properly document debian-installer's command line parameters, copyright, etc, etc. - The boot.bat passes obsolete parameters, like init=/linuxrc, which will not work with d-i anymore. - There might be a reason for including cd_drivers-image.img, so floppy images can be made and used to boot a system that cannot boot CD, but then it should also include the scsi_drivers floppy image for similar reasons, and does not. - dists/{frozen,stable,unstable} all incorrectly point to sarge; we currently have ugly hacks in d-i to avoid this confusing d-i, and would like to remove them, and these extra symlinks, please. - On i386, pcmcia-kernel-modules-{all kernels on CD}.deb should be included. Otherwise users will not be able to use pcmcia. -- see shy jo signature.asc Description: Digital signature
missing attachments
The attachments I forgot in my last mail. -- see shy jo # These udebs build the d-i cdrom initrd. As such, there is no reason # to keep another copy of them on the CD in udeb form. # # This duplicates data found in the files build/kernel file, in d-i cvs kernel-image-${kernel:Version} # build/common in d-i cvs rootskel main-menu cdebconf-udeb udpkg anna di-utils-shell di-utils-reboot # build/cdrom/common, in d-i cvs busybox-cvs-udeb rootskel-locale languagechooser discover-data-udeb discover-udeb hw-detect cdrom-detect cdrom-retriever load-installer cdrom-checker bogl-bterm-udeb di-utils-terminfo cdebconf-priority cdebconf-newt-udeb usb-discover nano-udeb floppy-retriever # Already on the initrd, thanks to library reduction. libdebconfclient0-udeb # A reduced version is on the initrd. Nothing currently needs the full # version. slang1a-utf8-udeb # These udebs are only useful in building the boot floppy image. busybox-cvs-floppy-udeb di-utils-bootfloppy rootskel-bootfloppy # Until someone gets the gtk cdebconf frontend going, all this is not worth # including. cdebconf-gtk-udeb fontconfig-udeb libatk1.0-udeb libdirectfb-0.9-19-udeb libexpat1-udeb libfreetype6-udeb libglib2.0-udeb libgtk+2.0-directfb0-udeb libpango1.0-udeb libpng12-0-udeb ttf-freefont-udeb zlib1g-udeb # This udeb is not in good shape and is largely supersceded by # cdebconf-newt-udeb cdebconf-slang-udeb # We're currently using busybox's own shell, and do not need this one. dash-udeb # These dhcp clients are not the currently preferred one. dhcp3-client-udeb pump-udeb # This package is only useful in the d-i-demo. di-utils-exit-installer # These loader udebs are not currently used on this CDs. That may change, # but for now load-installer is used. download-installer load-cdrom load-floppy # Only useful in the hd-media initrd. iso-scan load-iso # We're using busybox's modutils these days. modutils-basic modutils-full # Nothing currently depends on this, and it seems not useful on its own. raidtools2 reiserfsprogs-udeb # These udebs build the d-i cdrom initrd. As such, there is no reason # to keep another copy of them on the CD in udeb form. # # This duplicates data found in the file build/cdrom/i386, in d-i cvs. isa-pnp-modules-${kernel:Version} socket-modules-${kernel:Version} console-keymaps-at console-keymaps-usb floppy-modules-${kernel:Version} fat-modules-${kernel:Version} cdrom-core-modules-${kernel:Version} cdrom-modules-${kernel:Version} ide-modules-${kernel:Version} ide-core-modules-${kernel:Version} input-modules-${kernel:Version} fb-modules-${kernel:Version} kbd-chooser usb-modules-${kernel:Version} firewire-core-modules-${kernel:Version} usb-storage-modules-${kernel:Version} scsi-core-modules-${kernel:Version} # Not needed with the 2.4 kernel on i386. userdevfs # The speakup kernel modules are not useful unless the access images are # provided. *-speakup-di signature.asc Description: Digital signature
Re: unneccessary files on sarge netinst cds and other problems
I wrote: > - There might be a reason for including cd_drivers-image.img, >so floppy images can be made and used to boot a system that cannot >boot CD, but then it should also include the scsi_drivers floppy >image for similar reasons, and does not. I forgot to mention that since the CD does not include the boot-floppy-image.img, it will not be possible to boot d-i from the floppy images on it anyway. -- see shy jo signature.asc Description: Digital signature
debian-cd CVS back online
Hello everyone, the debian-cd CVS repository is back online (after a check of its integrity). Please commit any change that you postponed until now. Cheers, -- Raphaël Hertzog -+- http://www.ouaza.com Formation Linux et logiciel libre : http://www.logidee.com Earn money with free software: http://www.geniustrader.org
Re: debian-cd CVS back online - new jigdo fallback generation feature
On Thu, Dec 18, 2003 at 10:45:15AM +0100, Raphael Hertzog wrote: > the debian-cd CVS repository is back online (after a check of its > integrity). Thanks, Raphaël! I've just committed some code which makes the generation of fallback mirrors much easier. Furthermore, it produces relative template URLs in jigdo files by default. However, Phil, this /might/ break your publish_cds script - it is intended to replace publish_cds. With this feature, you can make debian-cd generate a directory with fallback links not after, but *during* template generation. This is done with jigdo-file's --match-exec switch, which executes a user-defined command whenever a file is found in the image. Advantages over publish_cds: Better integrated into debian-cd, less of a hack. ;) The following things in the default CONF.sh have changed: # HTTP/FTP URL for directory where you intend to make the templates # available. You should not need to change this; the default value "" # means "template in same dir as the .jigdo file", which is usually # correct. If it is non-empty, it needs a trailing slash. "%ARCH%" # will be substituted by the current architecture. #export JIGDOTEMPLATEURL="" # # Name of a directory on disc to create data for a fallback server in. # Should later be made available by you at the URL given in # JIGDOFALLBACKURLS. In the directory, two subdirs named "Debian" and # "Non-US" will be created, and filled with hard links to the actual # files in your FTP archive. Because of the hard links, the dir must # be on the same partition as the FTP archive! If unset, no fallback # data is created, which may cause problems - see README. #export JIGDOFALLBACKPATH="$(OUT)/snapshot/" # # Space-separated list of label->URL mappings for "jigdo fallback # server(s)" to add to .jigdo file. If unset, no fallback URL is # added, which may cause problems - see README. #export JIGDOFALLBACKURLS="Debian=http://myserver/snapshot/Debian/ Non-US=http://myserver/snapshot/Non-US/"; # # Space-separated list of "include URLs" to add to the .jigdo file. # The included files are used to provide an up-to-date list of Debian # mirrors to the jigdo _GUI_application_ (_jigdo-lite_ doesn't support # "[Include ...]"). export JIGDOINCLUDEURLS="http://cdimage.debian.org/debian-cd/debian-servers.jigdo"; # # $JIGDOTEMPLATEURL and $JIGDOINCLUDEURLS are passed to # "tools/jigdo_header", which is used by default to generate the # [Image] and [Servers] sections of the .jigdo file. You can provide # your own script if you need the .jigdo file to contain different # data. #export JIGDOSCRIPT="myscript" Additional info in the README: About jigdo "fallback servers": jigdo works by downloading individual packages and other files from a normal Debian mirror, and using them to regenerate a CD/DVD image. However, the content of Debian mirrors changes over time, files are added and removed. But jigdo must have access to all files needed for the image it has to regenerate, even those that have been removed from the normal Debian mirrors. A fallback server contains a backup of the Debian FTP space for the moment the .jigdo files were generated. This backup is made available under a certain URL which is written to the .jigdo files. jigdo will *only* revert to the fallback server after an unsuccessful attempt to retrieve a file from the normal user-selected Debian mirror, so the bandwidth requirements are modest. A fallback is even necessary for .jigdo files of the stable release, because some files (typically documentation or boot floppies) can change at any time. debian-cd allows you to automatically create a directory on disc which is suitable for use as a fallback mirror. It is populated with hard links to the archive contents. In CONF.sh, simply supply as JIGDOFALLBACKPATH the name of the directory, and as JIGDOFALLBACKURLS the URLs under which it will be made available (two separate URLs are necessary, one for "Debian" and one for "Non-US"). Hopefully I haven't broken debian-cd by committing this, but it seems to work fine judging from my tests on farbror. Cheers, Richard -- __ _ |_) /| Richard Atterer | GnuPG key: | \/¯| http://atterer.net | 0x888354F7 ¯ '` ¯ pgpqA2nyKliSX.pgp Description: PGP signature
testing netinst
Hi When can I download the testing netinst again? Your servers has been down for quite a long time now. I’ve tried searching some other places but with no luck, I’ve even tried with my friends but they haven’t kept the files. Hope you can solve this for me since I would love to try Debian during the Christmas holiday. Jonas Dahlborg [EMAIL PROTECTED]
Howto burn CDrom from ISO Files for UltraSparcIIi
Is there some one knowing haow to burn cdroms from the iso files for an UltraSparcIIi, please Thank you = J2EE Architect Robert Ghaloustians Mobile : (33) 0681458749 Phone : (33) 0143285923 http://www.rvcmla.org __ Do you Yahoo!? New Yahoo! Photos - easier uploading and sharing. http://photos.yahoo.com/
Re: debian-cd CVS back online - new jigdo fallback generation feature
At Thu, 18 Dec 2003 11:37:33 +0100, Richard Atterer <[EMAIL PROTECTED]> wrote: > > [1 ] > On Thu, Dec 18, 2003 at 10:45:15AM +0100, Raphael Hertzog wrote: > > the debian-cd CVS repository is back online (after a check of its > > integrity). > > Thanks, Raphaïl! > > I've just committed some code which makes the generation of fallback > mirrors much easier. Furthermore, it produces relative template URLs in > jigdo files by default. > > However, Phil, this /might/ break your publish_cds script - it is intended > to replace publish_cds. > > With this feature, you can make debian-cd generate a directory with > fallback links not after, but *during* template generation. This is done > with jigdo-file's --match-exec switch, which executes a user-defined > command whenever a file is found in the image. Fine, publish_cds only replaces what's in there already, so I can either remove that code, or make it so that the replacement is also relative. I still need publish CDs to move the images from the staging area to the published area, and generate the MD5SUMS files, but it would become pretty trivial if it didn't have to do the snapshot. > Advantages over publish_cds: Better integrated into debian-cd, less of a > hack. ;) The nice thing about setting it at publish time is that you can run publish_cds with a version number of "pre-release-test" say, and if it works, re-run it with "3.X_rY" on the same images, with no oportunity to screw up. ;-) Not that I do that sort of test, now that publish_cds works. Oh the other thing that you may not have noticed is that I have a hacked up version of publish_cds, called build_snapshot, that I run on raff to build the matching snapshot for us.cdimage.d.o. Since the bulk of fallback requests go to raff, I don't see the nasty hack going away too soon I'm afraid :-/ I should tidy build_snapshot up, take the funcionality out of publish_cds, and put build_snapshot into CVS really, so others can build snapshots (although I'm not sure how useful that is, given that there are only two places that the jigdos point at) Cheers, Phil.
Re: debian-cd CVS back online - new jigdo fallback generation feature
At Thu, 18 Dec 2003 11:37:33 +0100, Richard Atterer <[EMAIL PROTECTED]> wrote: > > [1 ] > On Thu, Dec 18, 2003 at 10:45:15AM +0100, Raphael Hertzog wrote: > > the debian-cd CVS repository is back online (after a check of its > > integrity). > > Thanks, Raphaïl! > > I've just committed some code which makes the generation of fallback > mirrors much easier. Furthermore, it produces relative template URLs in > jigdo files by default. > > However, Phil, this /might/ break your publish_cds script - it is intended > to replace publish_cds. > > With this feature, you can make debian-cd generate a directory with > fallback links not after, but *during* template generation. This is done > with jigdo-file's --match-exec switch, which executes a user-defined > command whenever a file is found in the image. Fine, publish_cds only replaces what's in there already, so I can either remove that code, or make it so that the replacement is also relative. I still need publish CDs to move the images from the staging area to the published area, and generate the MD5SUMS files, but it would become pretty trivial if it didn't have to do the snapshot. > Advantages over publish_cds: Better integrated into debian-cd, less of a > hack. ;) The nice thing about setting it at publish time is that you can run publish_cds with a version number of "pre-release-test" say, and if it works, re-run it with "3.X_rY" on the same images, with no oportunity to screw up. ;-) Not that I do that sort of test, now that publish_cds works. Oh the other thing that you may not have noticed is that I have a hacked up version of publish_cds, called build_snapshot, that I run on raff to build the matching snapshot for us.cdimage.d.o. Since the bulk of fallback requests go to raff, I don't see the nasty hack going away too soon I'm afraid :-/ I should tidy build_snapshot up, take the funcionality out of publish_cds, and put build_snapshot into CVS really, so others can build snapshots (although I'm not sure how useful that is, given that there are only two places that the jigdos point at) Cheers, Phil.
Re: Status of the images for CDs and DVDs
Santiago Garcia Mantinan wrote: > I'd like to comment on the bug we had with the debian-installer beta-1 cds, > which weren't bootable on some machines, for what I saw, this was not > isolinux fault, the businesscard cds were carrying the same isolinux and had > been made using the very same isolinux options and were not failing, farther > more, the netinst images made prior or after the beta-1 seem to work again. > I'd like to get this tested by some other people than me, by downloading the > daily netinst images we are producing now and testing them in one of the > machines that didn't want to boot out of the beta-1 cds. Maybe we could send out a mail to everyone who filed an install report of failure, and see if they can reproduce the failure, and also make sure they didn't produce a CD with a .iso file on it or similar mistake. -- see shy jo signature.asc Description: Digital signature
Devenir un site mirroir Debian au Senegal
Je compte mettre en place un site mirroir debian au Sénégal dans le cadre de la promotion des logiciels libres au Sénégal. Pour rallier le maximum de personnes dans ce projet, il m'a semblé nécessaire de spécialiser la distribution linux car le Sénégal est un tout petit pays dans ce monde du libre et nous ne pouvons pas nous disperser dans ce domaine. Bien entendu, tout le monde, au Sénégal, installe Redhat parce que c'est une distribution qui permet très rapidement de se bomber le torse en clamant tout haut qu'on sait installer "linux" mais je reste persuadé que Debian nous permet d'élever le niveau au Sénégal et plus particulièrement dans les centres éducatifs pour que demain des sénégalais apportent leurs contributions dans ce monde du libre. Dans ce cadre, il me semble nécessaire d'installer un site mirroir Debian au Sénégal pour assurer le "monopole" de Debian. Ainsi, je cherche un support pour la mise en place de ce site mirroir : les caractéristiques de la(les) machine(s) (je fournis) le débit minimal conseillé de la liaison Internet (je fournis également) et le support à la config (je suis un niewbie d'un mois). Merci d'avance ! _ MSN Messenger : discutez en direct avec vos amis ! http://www.msn.fr/msger/default.asp
Re: Help me
On Tue, 16 Dec 2003, Bruno Augusto wrote: > I have the image of debian in my computer. It has a iso extension and I > do no how can I procede to do a particion in my computer and extract > this file, and so run the linux. If it has .iso extention, it's probably a CD image. If it's a debian install CD image, you should burn it. After that you can install Debian from the CD (or CDs). -- Honza Houstek
Re: New version
On Wed, 17 Dec 2003, Jayendran JR wrote: > Hello, > > I noticed that the current ISOs for Debian are nearly a year old > (Dec 2002) though there are patches available. Could you please > clarify if any new version is about to be released so that I can > download the newer ISOs instead of downloading the older ones > and applying patches. Do download Debian Woody 3.0 r2 images. It is the second revision to Woody 3.0 and was released just a few weeks ago. Regards, -- Honza Houstek
unneccessary files on sarge netinst cds and other problems
I hope to get the netinst CDs to a size that can be used with d-i on a 128 MB USB memory stick again. It's currently too big now. There's a lot of cruft on there -- - The following packages are present on the netinst CD, but are not installed as part of the base system, and so are not really needed on it. Most notable is all the MTAs; exim4 is the default MTA and only it is needed. Simularly, we only need one awk, not three, only one inetd, not two, only one init system, not two. exim libldap2 libdb4.1 (perl uses 4.0 which is also present) gawk original-awk masqmail courier-base courier-authdaemon courier-mta exim4-daemon-heavy inetutils-inetd debconf-english file-rc esmtp nullmailer postfix sendmail ssmtp m4 - Many many udebs are present on the netinst CD, but will not be used by d-i, or are part of the d-i initrd, and so only take up space on the CD. I have attached two commented lists of these udebs. - The highly confusing diagrams in README.{txt,html} about setting up apt are all unnecessary; the installer sets up apt for the user. - The README.mirrors.{txt,html} is not particularly useful, since the debian installer will walk the user through setting up apt to use a mirror. - The README.non-US, becauses being very outdated (says we cannot export ssh for example), is useless as this CD contains no non-US items, and I doubt any for sarge will, as non-us is essentially now for oprhaned software and a very few packages with patent problems. - The doc/install directory is pretty much useless, since it documents the boot floppys and not d-i. d-i has not finished its documentation, but I suppose you could replace all this stuff with our INSTALLATION-HOWTO document for now. - Much of the other stuff in the doc/ directory is only of use to developers and sociologist (constitution.txt), is better documented on the web (bug-*, mailing-lists.txt), does not apply to this release of debian (dedication-2.2*), does not apply to this CD (source-unpack.txt; no source here), would better be shipped as a debian package (debian-keyring.tar.gz). - With isolinux, the /install/cdrom.gz is used, which means that /install/cdrom-image.img is useless, and it wastes 2.9 mb. - /install/floppy-initrd.gz is 100% useless - /tools/README.tools documents directories that do not exist. The /tools/REAMDE seems sufficient without README.tools. - /tools/src seems useless, why include source on a minimal netinst CD? - Contents-i386.gz is huge, and confusingly documents files that are in packages not on the CD. I say remove it. - The dists/sarge/contrib directory exists, but has only empty Packages files etc in it. The installer does not use or enable contrib, this should be removed from the netinst cds, which should never need to have non-free or contrib packages on thhem. - dists/sarge/main/source exists, but is empty. If there is not source on a CD, the directory should not be present. - I don't get the point of having both Packages and Packages.gz on the same CD. We somehow save space by including a duplicate compressed copy? All tools should be able to deal with uncompressed Packages files, or, better, compressed ones. Other problems: - The d-i syslinux help screens are not used. You'll find these inside our cdrom-image.img file as distributed by the d-i project. The current help screens do not properly document debian-installer's command line parameters, copyright, etc, etc. - The boot.bat passes obsolete parameters, like init=/linuxrc, which will not work with d-i anymore. - There might be a reason for including cd_drivers-image.img, so floppy images can be made and used to boot a system that cannot boot CD, but then it should also include the scsi_drivers floppy image for similar reasons, and does not. - dists/{frozen,stable,unstable} all incorrectly point to sarge; we currently have ugly hacks in d-i to avoid this confusing d-i, and would like to remove them, and these extra symlinks, please. - On i386, pcmcia-kernel-modules-{all kernels on CD}.deb should be included. Otherwise users will not be able to use pcmcia. -- see shy jo signature.asc Description: Digital signature
missing attachments
The attachments I forgot in my last mail. -- see shy jo # These udebs build the d-i cdrom initrd. As such, there is no reason # to keep another copy of them on the CD in udeb form. # # This duplicates data found in the files build/kernel file, in d-i cvs kernel-image-${kernel:Version} # build/common in d-i cvs rootskel main-menu cdebconf-udeb udpkg anna di-utils-shell di-utils-reboot # build/cdrom/common, in d-i cvs busybox-cvs-udeb rootskel-locale languagechooser discover-data-udeb discover-udeb hw-detect cdrom-detect cdrom-retriever load-installer cdrom-checker bogl-bterm-udeb di-utils-terminfo cdebconf-priority cdebconf-newt-udeb usb-discover nano-udeb floppy-retriever # Already on the initrd, thanks to library reduction. libdebconfclient0-udeb # A reduced version is on the initrd. Nothing currently needs the full # version. slang1a-utf8-udeb # These udebs are only useful in building the boot floppy image. busybox-cvs-floppy-udeb di-utils-bootfloppy rootskel-bootfloppy # Until someone gets the gtk cdebconf frontend going, all this is not worth # including. cdebconf-gtk-udeb fontconfig-udeb libatk1.0-udeb libdirectfb-0.9-19-udeb libexpat1-udeb libfreetype6-udeb libglib2.0-udeb libgtk+2.0-directfb0-udeb libpango1.0-udeb libpng12-0-udeb ttf-freefont-udeb zlib1g-udeb # This udeb is not in good shape and is largely supersceded by # cdebconf-newt-udeb cdebconf-slang-udeb # We're currently using busybox's own shell, and do not need this one. dash-udeb # These dhcp clients are not the currently preferred one. dhcp3-client-udeb pump-udeb # This package is only useful in the d-i-demo. di-utils-exit-installer # These loader udebs are not currently used on this CDs. That may change, # but for now load-installer is used. download-installer load-cdrom load-floppy # Only useful in the hd-media initrd. iso-scan load-iso # We're using busybox's modutils these days. modutils-basic modutils-full # Nothing currently depends on this, and it seems not useful on its own. raidtools2 reiserfsprogs-udeb # These udebs build the d-i cdrom initrd. As such, there is no reason # to keep another copy of them on the CD in udeb form. # # This duplicates data found in the file build/cdrom/i386, in d-i cvs. isa-pnp-modules-${kernel:Version} socket-modules-${kernel:Version} console-keymaps-at console-keymaps-usb floppy-modules-${kernel:Version} fat-modules-${kernel:Version} cdrom-core-modules-${kernel:Version} cdrom-modules-${kernel:Version} ide-modules-${kernel:Version} ide-core-modules-${kernel:Version} input-modules-${kernel:Version} fb-modules-${kernel:Version} kbd-chooser usb-modules-${kernel:Version} firewire-core-modules-${kernel:Version} usb-storage-modules-${kernel:Version} scsi-core-modules-${kernel:Version} # Not needed with the 2.4 kernel on i386. userdevfs # The speakup kernel modules are not useful unless the access images are # provided. *-speakup-di signature.asc Description: Digital signature
Re: unneccessary files on sarge netinst cds and other problems
I wrote: > - There might be a reason for including cd_drivers-image.img, >so floppy images can be made and used to boot a system that cannot >boot CD, but then it should also include the scsi_drivers floppy >image for similar reasons, and does not. I forgot to mention that since the CD does not include the boot-floppy-image.img, it will not be possible to boot d-i from the floppy images on it anyway. -- see shy jo signature.asc Description: Digital signature