Re: Errors while making i386 woody CDs.
Hello, Both warnings are related to the same problem ... there are packages without a Section field. You can safely ignore those messages. Thanks. [ Free Software ISOs - ftp://ftp.fsn.hu/pub/CDROM-Images/ ]--- Attila Nagy e-mail: [EMAIL PROTECTED] Free Software Network (FSN.HU)phone @work: +361 210 1415 (194) cell.: +3630 306 6758 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Small report (re: isolinux test image, debian-cd changes available)
Hello, I tested first the 24bf image. I was surprised to see it uses a framebuffer... Now... This can be good, but I don't understand why it is using it - The display is MUCH slower than using the regular interface, and it is still curses-based. What did we gain from framebuffer? The I18N support, I think. You can choose languages with special characters too (UTF8). Second - I am installing it using the Spanish interface. When I get to choose the filesystem type I will be using, the text is almost too wide to be shown on screen... It fits, but it is noticeably too wide, because of the description of the Ext3 line: Wrong list. This report should be sent to the [EMAIL PROTECTED] address. Please forward to them, or file the bug reports against the boot floppies. [ Free Software ISOs - ftp://ftp.fsn.hu/pub/CDROM-Images/ ]--- Attila Nagy e-mail: [EMAIL PROTECTED] Free Software Network (FSN.HU)phone @work: +361 210 1415 (194) cell.: +3630 306 6758 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: 2.2_r6 jigdo files cdimage.d.o
On Sun, Apr 07, 2002 at 01:04:56PM +0200, Mattias Wadenstein wrote: (Yes, jigdo-port is the only one that compiles on AIX for us. C++ isn't exactly portable. :/) Oh - but the file format has changed, and the latest jigdo files are no longer readable by jigdo-port! :-( I *really* want to avoid having to update two different programs whenever I make a change, so I have no plans to fix jigdo-port. [Standard rant: C++ *is* portable, and the standard has been out for 3 years - it's about time everybody caught up with it! Maybe gcc is boot-strappable on AIX... But I realize that would be quite a lot of work just to compile jigdo-file. :-( ] The important part is that the result looks exactly like the one on the master site so I can do an inexpensive rsync to get everything right. Should be possible. However, the template files include an md5sum of the images, which is checked by jigdo; if jigdo says that the file has been regenerated OK, it *is* OK and no extra rsync run is necessary. OTOH, it might make sense to fall back to rsync if not all of the parts in an image could be retrieved. I could add that to the script. Cheers, Richard -- __ _ |_) /| Richard Atterer | \/¯| http://atterer.net ¯ '` ¯ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Downloading sid images using Jigdo
I tried to use jigdo-lite do download sid images, but it can't get some files from http://ftp.fsn.hu/pub/debian-superseded/. Will you please explain me the use of this files, do i need to download newest *.jigdo files to fix this? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Downloading sid images using Jigdo
Hello, I tried to use jigdo-lite do download sid images, but it can't get some files from http://ftp.fsn.hu/pub/debian-superseded/. Will you please explain me the use of this files, do i need to download newest *.jigdo files to fix this? Yes, you have to download the newest *.jigdo files. And yes, this is quite off-topic on this list :) If there are any problems, please write me. [ Free Software ISOs - ftp://ftp.fsn.hu/pub/CDROM-Images/ ]--- Attila Nagy e-mail: [EMAIL PROTECTED] Free Software Network (FSN.HU)phone @work: +361 210 1415 (194) cell.: +3630 306 6758 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: cvs commit to debian-cd/debian by lawrencc
Le Mon, Apr 08, 2002 at 06:40:53PM -0700, Debian Boot CVS Master écrivait: Repository: debian-cd/debian who:lawrencc time: Mon Apr 8 18:40:53 PDT 2002 Log Message: Added syslinux to the dependencies, since it's required for ISOLINUX support to work. You should put it in Recommends since it's i386-only. Otherwise debian-cd won't be installable on non-i386 architectures. Cheers, -- Raphaël Hertzog -+- http://strasbourg.linuxfr.org/~raphael/ Formation Linux et logiciel libre : http://www.logidee.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Optimising Debian-CD
Hi, I've been watching debian-cd running on open struggle with the trivia of generating things like Packages files, and md5sums, and it occurs to me that much of this could do with some work. For example the generation of the md5sum files would be done a lot quicker by a perl script that picks the pre-calculated md5sums out of the ftp archive's md5sum.gz file. If we replaced the whole for loop with a perl script, it would only need to read the md5sums once, could load them into a hash, and simply write them out on the basis of the files found in the CD directory. Before I start this, does anyone have any reasons not to do this? IMO it's actually better to use the master md5sums, because it gives a simple end-to-end sanity check. If the CD building machine had a tendency to corrupt data comming off it's disks (as happened with a previous incarnation of open) or the mirroring run had failed in a subtle way, then a simple loop mount of each image, and running md5sum -c on each, should catch that straight away if the md5sums were not locally recalculated. A slightly more ambitious replacement would be to generate the Packages files by taking the records out of the main archive's Packages files. Another thing that might help, but would need a significant redesign, would be to do all this for all the CD directories from all architectures at the same time (i.e. reorder the loop nesting) so that the perl would only need to look at the md5sums and Packages files once before splurging out the individual CD files. Opinions? In the mean time, I'll knock up an md5sum file generator, and give it a try. Cheers, Phil. -- Say no to software patents! http://petition.eurolinux.org/ |)| Philip Hands [+44 (0)20 8530 9560]http://www.hands.com/ |-| HANDS.COM Ltd.http://www.uk.debian.org/ |(| 10 Onslow Gardens, South Woodford, London E18 1NE ENGLAND signature.asc Description: This is a digitally signed message part
Re: Test of el-torito and isolinux multiboot for CD
On Mon, Apr 08, 2002 at 09:37:07AM +0200, Raphael Hertzog wrote: Filesize: 625606656 bytes Something that's occurred to me before, and is especially relevant for a test image like this: how 'bout a 180M mini cd image? The important parts are booting and getting base installed, and it shouldn't take 600M for that, should it? -- Mike Stone -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: 2.2_r6 jigdo files cdimage.d.o
On Mon, 8 Apr 2002, Richard Atterer wrote: On Sun, Apr 07, 2002 at 01:04:56PM +0200, Mattias Wadenstein wrote: (Yes, jigdo-port is the only one that compiles on AIX for us. C++ isn't exactly portable. :/) Oh - but the file format has changed, and the latest jigdo files are no longer readable by jigdo-port! :-( I *really* want to avoid having to update two different programs whenever I make a change, so I have no plans to fix jigdo-port. [Standard rant: C++ *is* portable, and the standard has been out for 3 years - it's about time everybody caught up with it! Maybe gcc is boot-strappable on AIX... But I realize that would be quite a lot of work just to compile jigdo-file. :-( ] 3 years is a very short time. We have a fairly updated system, but 3 years is well below the time a system might be around without any updates other than security upgrades. The version is: VisualAge C++ Professional / C for AIX Compiler, Version 5 And that is a new compiler, not a very old one. I know of a few sites that run much older ones. Some configure output: checking whether the C++ compiler is recent enough... no * Your compiler failed to recognize some advanced C++ * constructs. This means that it is probably too old. * In case compilation fails, try upgrading to a newer * compiler, e.g. GCC 2.95 or later. It then procedes to fail to find db_create in -ldb[lots of versions] despite that being installed. --without-libdb gives a failure later on at: checking whether dgettext works... no * Make sure gettext is installed, or use * --disable-nls to switch off gettext support. configure: error: dgettext() call could not be linked. Also some interesting features turns up, like: checking size of unsigned long... 0 checking size of unsigned long long... 0 With g++ (and a bunch of hacking), it compiles but fails to link. I haven't had time to take a better look at it yet, or turn the software over to someone else around here. It is still painful, especially compared to jigdo-port which compiled cleanly and without problems. The important part is that the result looks exactly like the one on the master site so I can do an inexpensive rsync to get everything right. Should be possible. However, the template files include an md5sum of the images, which is checked by jigdo; if jigdo says that the file has been regenerated OK, it *is* OK and no extra rsync run is necessary. OTOH, it might make sense to fall back to rsync if not all of the parts in an image could be retrieved. I could add that to the script. It isn't for the images, it is for having all the other files and directories looking exactly like the master site, a true mirror. That is why I want the same directory structure, so that it will find the images with the correct size and not bother with them. If rsync believes it has to sync the images, it will put a great deal of load on both sides, even if the data is still the same. /Mattias Wadenstein -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Woody DVD-Image?
Hello, I am wondering, if anybody has woody DVD-Images. Thanks. Rainer. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Optimising Debian-CD
On Tue, 9 Apr 2002, Wookey wrote: On Tue 09 Apr, Philip Hands wrote: I've been watching debian-cd running on open struggle with the trivia of generating things like Packages files, and md5sums, and it occurs to me that much of this could do with some work. For example the generation of the md5sum files would be done a lot quicker by a perl script that picks the pre-calculated md5sums out of the ftp archive's md5sum.gz file. Before I start this, does anyone have any reasons not to do this? IMO it's actually better to use the master md5sums, because it gives a simple end-to-end sanity check. This seems reasonable, but will it work properly on non-official CDs - or are you only proposing this option for official CDs? ie on non-official Cds some packages are (potentially) replaced by local ones with different MD5sums. I don't think there is a pre-prepared md5sum.gz file to fish these out of (but Icould be wrong - I'm thoroughly out of date on how things have chaned in this area (scanpackages etal) between potato and woody. A slightly more ambitious replacement would be to generate the Packages files by taking the records out of the main archive's Packages files. Same proviso applies. My home made packages have md5sums generated by the standard build scripts. I can see no problems, provided make mirrorcheck is used. Phil. -- Philip Charles; 39a Paterson Street, Abbotsford, Dunedin, New Zealand +64 3 488 2818Fax +64 3 488 2875Mobile 025 267 9420 [EMAIL PROTECTED] - preferred. [EMAIL PROTECTED] I sell GNU/Linux GNU/Hurd CDs. See http://www.copyleft.co.nz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: solution for base-config/cat:: problem
#include hallo.h Adam Di Carlo wrote on Tue Apr 09, 2002 um 08:55:22AM: Chris: Please, use ALL arguments from particular syslinux.cfg files. I was able to reproduce this bug. IMHO caused by missing ram_size specification, so the ramdisk-filesystem gets random IO errors, so the dbootstrap_settings file is not written correctly (contains cat: input/outpur error) and base-config dies while parsing it. I extracted the rootfs from your image, built an own CD with it (rest was from bf2.4 flavor), and it worked fine. That's strange, Raphael had told me before that they used the syslinux.cfg files as is... No idea which file you mean. isolinux.cfg is a syslinux.cfg similar file, adapted by Chris to load different kernels. Compare attached files. Gruss/Regards, Eduard. -- Flüssigseifenbenutzer! Fristeneinhalter! Geschenkpapierbügler! Auslandstanker! DEFAULT /install/linpci APPEND root=/dev/ram ro initrd=idepci.bin flavor=idepci LABEL linux kernel /install/linpci LABEL idepci kernel /install/linpci LABEL compact kernel /install/lincompt append root=/dev/ram ro initrd=compact.bin flavor=compact LABEL vanilla kernel /install/linux append root=/dev/ram ro initrd=root.bin LABEL bf24 kernel /install/lin24 append root=/dev/ram ro initrd=bf24.bin flavor=bf2.4 LABEL rescue kernel /install/linpci append noinitrd LABEL resccomp kernel /install/lincompt append noinitrd LABEL rescvanl kernel /install/linux append noinitrd LABEL rescbf24 kernel /install/lin24 append noinitrd DISPLAY isolinux.txt TIMEOUT 0 PROMPT 1 F1 f1.txt F2 f2.txt F3 f3.txt F4 f4.txt F5 f5.txt F6 f6.txt F7 f7.txt F8 f8.txt F9 f9.txt F0 f10.txt FONT font.psf # see /usr/doc/syslinux/syslinux.doc.gz for file format description DEFAULT linux.bin APPEND vga=normal noinitrd load_ramdisk=1 prompt_ramdisk=1 ramdisk_size=16384 root=/dev/fd0 disksize=1.44 flavor=bf2.4 TIMEOUT 0 DISPLAY debian.txt PROMPT 1 F1 f1.txt F2 f2.txt F3 f3.txt F4 f4.txt F5 f5.txt F6 f6.txt F7 f7.txt F8 f8.txt F9 f9.txt F0 f10.txt LABEL linux KERNEL linux.bin APPEND vga=normal noinitrd load_ramdisk=1 prompt_ramdisk=1 ramdisk_size=16384 root=/dev/fd0 disksize=1.44 flavor=bf2.4 LABEL initrd KERNEL linux.bin APPEND vga=normal noinitrd load_ramdisk=1 prompt_ramdisk=1 ramdisk_size=16384 root=/dev/fd0 disksize=1.44 flavor=bf2.4 LABEL ramdisk KERNEL linux.bin APPEND vga=normal noinitrd load_ramdisk=1 prompt_ramdisk=1 ramdisk_size=16384 root=/dev/fd0 disksize=1.44 flavor=bf2.4 LABEL ramdisk0 KERNEL linux.bin APPEND vga=normal noinitrd load_ramdisk=1 prompt_ramdisk=1 ramdisk_size=16384 root=/dev/fd0 disksize=1.44 flavor=bf2.4 LABEL ramdisk1 KERNEL linux.bin APPEND vga=normal noinitrd load_ramdisk=1 prompt_ramdisk=1 ramdisk_size=16384 root=/dev/fd1 disksize=1.44 flavor=bf2.4 LABEL floppy KERNEL linux.bin APPEND vga=normal noinitrd root=/dev/fd0 disksize=1.44 flavor=bf2.4 LABEL floppy0 KERNEL linux.bin APPEND vga=normal noinitrd root=/dev/fd0 disksize=1.44 flavor=bf2.4 LABEL floppy1 KERNEL linux.bin APPEND vga=normal noinitrd root=/dev/fd1 disksize=1.44 flavor=bf2.4 LABEL rescue KERNEL linux.bin APPEND vga=normal noinitrd msg03299/pgp0.pgp Description: PGP signature
Re: vanilla as default or not
On Tue, 2002-04-09 at 14:02, Adam Di Carlo wrote: Philip Hands [EMAIL PROTECTED] writes: ... Not that it will help most people --- If I'd not been part of this conversation, then I doubt I'd be reading the READMEs to see which my best bet was, I'd just grab the ones in .../current Do you think it would be possible that we could provide CD image labels for vendors, if they wanted to use them, which actually had the names I suggested listed on the CD itself? Hmm, I think most vendors want to put their own labels on them, so that they get to point people to their web site, and so get to sell that customer, and their freinds, more CDs in future. E.g.: Debian 3.0, Intel x86 CD number 2 of 5 SCSI boot CD I agree that users don't usually read and generally just pop in CD#1 and try to boot it. Perhaps we just need a NOTES_FOR_DISTRIBUTORS file somewhere, with hints like this in it. Cheers, Phil. -- Say no to software patents! http://petition.eurolinux.org/ |)| Philip Hands [+44 (0)20 8530 9560]http://www.hands.com/ |-| HANDS.COM Ltd.http://www.uk.debian.org/ |(| 10 Onslow Gardens, South Woodford, London E18 1NE ENGLAND signature.asc Description: This is a digitally signed message part
Re: Test of el-torito and isolinux multiboot for CD
Look at http://cdimage.debian.org/ There are links to 'netinst' iso images, which are more like 35MB in size. -g On Tue, Apr 09, 2002 at 07:05:12AM -0400, Michael Stone wrote: On Mon, Apr 08, 2002 at 09:37:07AM +0200, Raphael Hertzog wrote: Filesize: 625606656 bytes Something that's occurred to me before, and is especially relevant for a test image like this: how 'bout a 180M mini cd image? The important parts are booting and getting base installed, and it shouldn't take 600M for that, should it? -- Mike Stone -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- Glen S Mehn Contract Systems Administrator SquareTrade, Inc [EMAIL PROTECTED]Building Trust in Transactions (sm) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: non-booting sparc, non-making sparc
Hello to all you folks who know more than me. I used today's CVS debian-cd. I am using an ix86 PC. I selected sparc. ARCH=sparc BOOTDIR=/boot The make stops with two errors: cannot find file ar (a binary file that does something for the script but is not here) cannot find cd.b or second.b Then it does not make any images. So I loop mounted a sparc image and gave the cd.b and second.b location to the CONF.sh /bootdir=/dir/for/them and it can not find that dir. cannot find cd.b or second.b So I copied cd.b and second.b into the debian-cd tmp dir and it made images. But it does not boot. So, how does a person make a bootable sparc CD with debian-cd by using an ix86 PC? Cheers, Bill Bennet Where the only monopoly we support has a Boardwalk and a Baltic Avenue. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Optimising Debian-CD
Le Tue, Apr 09, 2002 at 05:39:18PM +0100, Philip Hands écrivait: I'll commit it to CVS once I've managed a successfull build run with it, if that's OK. I'd prefer to see the patch first ... because release is approaching and I'd like to check it before it's commited. Well as I said it happened for 2.2r0 (IIRC) --- I can do without it happening again. Sure. That means that you should launch md5sum -c though. :) Cheers, -- Raphaël Hertzog -+- http://strasbourg.linuxfr.org/~raphael/ Formation Linux et logiciel libre : http://www.logidee.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: pre-release Jigdo files appearing at cdimage.d.o, please test
I tried generating the images with jigdo-lite, but run into problems. jigdo-lite was reporting one missing file (Found 982 of the 983 files required by the template) and was not able to complete the image. This was my first time with jigdo but I suspect the problem was that non-US was updated after you had made the jigdo files. From woody-i386-1.jigdo: % grep non-US woody-i386-1.jigdo sljMO1JHdJDT_gQYa2IPtg=Non-US:dists/woody/non-US/Contents-i386.gz From the actual file system: % jigdo-file md5sum dists/woody/non-US/Contents-i386.gz Iegxgg-6cQCWTLwa4XFOrw dists/woody/non-US/Contents-i386.gz Choosing some other file, such as tools/unz512x3.exe, gives the same checksum that is in the .jigdo file. -- Heikki Vatiainen * [EMAIL PROTECTED] Tampere University of Technology * Tampere, Finland -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: pre-release Jigdo files appearing at cdimage.d.o, please test
On Tue, 2002-04-09 at 21:57, Heikki Vatiainen wrote: I tried generating the images with jigdo-lite, but run into problems. jigdo-lite was reporting one missing file (Found 982 of the 983 files required by the template) and was not able to complete the image. This was my first time with jigdo but I suspect the problem was that non-US was updated after you had made the jigdo files. From woody-i386-1.jigdo: % grep non-US woody-i386-1.jigdo sljMO1JHdJDT_gQYa2IPtg=Non-US:dists/woody/non-US/Contents-i386.gz From the actual file system: % jigdo-file md5sum dists/woody/non-US/Contents-i386.gz Iegxgg-6cQCWTLwa4XFOrw dists/woody/non-US/Contents-i386.gz Choosing some other file, such as tools/unz512x3.exe, gives the same checksum that is in the .jigdo file. That's very odd --- I've downloaded the 1_NONUS image, and it worked fine. Richard, is this evidence that I need to add Contents to the list of files to grep out of jigdo's input list? Does jigdo just assume that if it's given a name, it's a file that matches the one in the archive? If that were the case, how come the Packages files didn't get the same treatment, because they're not excluded either? Also, how could I have just downloaded the image? Cheers, Phil. -- Say no to software patents! http://petition.eurolinux.org/ |)| Philip Hands [+44 (0)20 8530 9560]http://www.hands.com/ |-| HANDS.COM Ltd.http://www.uk.debian.org/ |(| 10 Onslow Gardens, South Woodford, London E18 1NE ENGLAND signature.asc Description: This is a digitally signed message part
cvs commit to debian-cd/debian by lawrencc
Repository: debian-cd/debian who:lawrencc time: Tue Apr 9 15:00:35 PDT 2002 Log Message: Change syslinux to a recommendation, per Raphael. Files: changed:control -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: solution for base-config/cat:: problem
On Apr 09, Eduard Bloch wrote: #include hallo.h Raphael Hertzog wrote on Mon Apr 08, 2002 um 11:31:46PM: The cat:: missing command is an error which someone else already reported to debian-cd when using the bf24 flavor. Chris: Please, use ALL arguments from particular syslinux.cfg files. I was able to reproduce this bug. IMHO caused by missing ram_size specification, so the ramdisk-filesystem gets random IO errors, so the dbootstrap_settings file is not written correctly (contains cat: input/outpur error) and base-config dies while parsing it. I extracted the rootfs from your image, built an own CD with it (rest was from bf2.4 flavor), and it worked fine. I wasn't sure what all the bootargs were for, so I wasn't sure which ones were needed (I didn't want to accidentally end up with a disk prompt or something). I'll fix this in debian-cd cvs and update the ISO image accordingly. The boot.bat command lines will probably have to be fixed too. Chris -- Chris Lawrence [EMAIL PROTECTED] - http://www.lordsutch.com/chris/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
cvs commit to debian-cd/tools/boot/woody by lawrencc
Repository: debian-cd/tools/boot/woody who:lawrencc time: Tue Apr 9 15:38:16 PDT 2002 Log Message: Add ramdisk_size and disksize arguments to loadlin and isolinux command lines. Files: changed:boot-i386 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
cvs commit to debian-cd/tools/boot/woody by lawrencc
Repository: debian-cd/tools/boot/woody who:lawrencc time: Tue Apr 9 15:45:11 PDT 2002 Log Message: Add disksize argument to loadlin command lines. Files: changed:boot-i386 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: solution for base-config/cat:: problem
-BEGIN PGP SIGNED MESSAGE- Hash: MD5 On Tuesday 09 April 2002 20:13, Chris Lawrence wrote: Ok, the master copy of the image is now updated: http://www.phy.olemiss.edu/debian-cd/ The mirrors will probably catch it in the next day or so. Please test so we can shake out the (hopefully zero) remaining bugs! - -- I put your update into my local debian-cd for the bf24 kernel ie: LABEL bf24 kernel /install/lin24 append root=/dev/ram ro initrd=bf24.bin ramdisk_size=16384 disksize=1.44 flavor=bf2.4 and created i386 CD#1, then did a test install with the resulting image.No longer does it report the cat:: problem, and the install went through with no problems. - -- Jim Westveer - I wish there was a button on my monitor for intelligence. There's a button called `brightness', but it doesn't work. - E-Mail: [EMAIL PROTECTED] [EMAIL PROTECTED] work : 425-591-3002 KC7JYJ pgp-key 0x36129171gpg-key 0x9823336C - -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iEYEAREBAAYFAjyzx1UACgkQXpzfopgjM2y8OwCdFlZCXTRTJomSDlUYp3G0PAxq Vx0An2dYWVm2b/bGinJEj7fwY3amXGx1 =LiR+ -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
