Bug#537978: texlive-latex-base: update fails to build font
Package: texlive-latex-base Version: 2005.dfsg.3-1 Severity: grave Justification: renders package unusable I attempted to upgrade tetex-latex, and then after I had problems I looked online and tried livetex-latex, and both failed in the package configuration step with font compilation errors. -- Package-specific info: If you report an error when running one of the TeX-related binaries (latex, pdftex, metafont,...), or if the bug is related to bad or wrong output, please include a MINIMAL example input file that produces the error in your report. Don't forget to also include minimal examples of other files that are needed, e.g. bibtex databases. Often it also helps to include the logfile. Please, never send included pictures! If your example file isn't short or produces more than one page of output (except when multiple pages are needed to show the problem), you can probably minimize it further. Instructions on how to do that can be found at http://www.latex-einfuehrung.de/mini-en.html (english) or http://www.latex-einfuehrung.de/mini.html (german) ## minimal input file ## other files ## List of ls-R files -rw-r--r-- 1 root root 1007 Jul 22 00:43 /var/lib/texmf/ls-R -rw-rw-r-- 1 root staff 79 Jul 22 00:40 /usr/local/share/texmf/ls-R lrwxrwxrwx 1 root root 29 Jul 2 02:30 /usr/share/texmf/ls-R - /var/lib/texmf/ls-R-TEXMFMAIN lrwxrwxrwx 1 root root 27 Jul 22 00:38 /usr/share/texmf-texlive/ls-R - /var/lib/texmf/ls-R-TEXLIVE lrwxrwxrwx 1 root root 27 Jul 22 00:38 /usr/share/texmf-texlive/ls-R - /var/lib/texmf/ls-R-TEXLIVE ## Config files lrwxrwxrwx 1 root root 20 Jul 2 02:30 /usr/share/texmf/web2c/texmf.cnf - /etc/texmf/texmf.cnf -rw-r--r-- 1 root root 5474 Jul 22 00:43 /var/lib/texmf/web2c/fmtutil.cnf -rw-r--r-- 1 root root 5039 Jul 22 00:43 /var/lib/texmf/web2c/updmap.cfg -rw-r--r-- 1 root root 4481 Jul 22 00:43 /var/lib/texmf/tex/generic/config/language.dat -- System Information: Debian Release: 4.0 APT prefers oldstable APT policy: (500, 'oldstable') Architecture: i386 (i586) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.4.20 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages texlive-latex-base depends on: ii texlive-common2005.dfsg.3-1 TeX Live: Base component ii texlive-pdfetex 2005.dfsg.2-12 TeX Live: pdfTeX texlive-latex-base recommends no packages. Versions of packages tex-common depends on: ii debconf [debconf-2.0]1.5.11etch2 Debian configuration management sy ii ucf 2.0020 Update Configuration File: preserv Versions of packages texlive-latex-base is related to: pn tetex-basenone (no description available) pn tetex-bin none (no description available) pn tetex-extra none (no description available) -- debconf information: tex-common/check_texmf_wrong: tex-common/check_texmf_missing: -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#374193: gforge-lists-mailman: use /var/lib/mailman as installation prefix, not /usr/lib/mailman
Roland == Roland Mas [EMAIL PROTECTED] writes: Roland Roland Rob Ristroph), [EMAIL PROTECTED] (Robert G. Ristroph, 2006-07-21 10:27:46 -0500 : Roland == Roland Mas [EMAIL PROTECTED] writes: Roland Roland Rob Ristroph, 2006-06-17 14:54:22 -0500 : Package: gforge-lists-mailman Severity: important Roland Roland I'd need a version number there too. As far as I know, this bug Roland doesn't exist in recent packages of Gforge. Could you confirm that? I don't have a computer on which I can test that, so I can't confirm or deny that the bug has been fixed. Roland Roland Fair enough. Do you remember what version of Gforge had the bug when Roland you encountered it? I am using testing on that machine, and I ran into the problem on 7 June 2006, but that's not necessarily when I did the apt-get install gforge -- it could have been a few weeks prior to that. I can't remember what version it was, but I think it was 4.something and not 3.something. I'm sorry I can't be more specific. I may be installing gforge to a fresh machine in a couple of months; I can re-file the bug then if it still exists. --Rob -- http://rgr.freeshell.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#374193: gforge-lists-mailman: use /var/lib/mailman as installation prefix, not /usr/lib/mailman
Roland == Roland Mas [EMAIL PROTECTED] writes: Roland Roland Rob Ristroph, 2006-06-17 14:54:22 -0500 : Package: gforge-lists-mailman Severity: important Roland Roland I'd need a version number there too. As far as I know, this bug Roland doesn't exist in recent packages of Gforge. Could you confirm that? I don't have a computer on which I can test that, so I can't confirm or deny that the bug has been fixed. --Rob -- http://rgr.freeshell.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#374193: gforge-lists-mailman: use /var/lib/mailman as installation prefix, not /usr/lib/mailman
Package: gforge-lists-mailman Severity: important I had to ln -s /usr/lib/cgi-bin/mailman /usr/lib/mailman/cgi-bin/ before the gforge apache configs would find mailman properly. When I was reporting another bug to mailman guys, they said to report this as a bug to the gforge package. Specifically, from a reply to Bug#371074: That is gforge's bug. Please file a separate bug against gforge-lists-mailman and tell them to use /var/lib/mailman/ as mailman installation prefix, not /usr/lib/mailman/. That's the place where we put all compatibility symlinks so that all things work. Add [EMAIL PROTECTED] to the CC list for that bug; reportbug will give you the opportunity to do that. Thanks, --Rob -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.12-1-386 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#371074: mailman: web interface gives internal server error
Hi, I now have this mailman working, installed from source (2.1.8), not from the debian package. I'm not in a position to be able to replicate this bug anymore, because the server is in use, so you might want to mark this bug accordingly -- I'll answer the questions below about the setup as best I can though. I am really grateful for the responses on this bug report, even if (especially if . . .) it was just a weird configuration on my part. I am used to sending bug reports into a black hole, so it is really nice to have you guys follow up with me on it. Here is an overview of what I did to make it work from source, perhaps something here is helpful: made user/group mailman: groupadd mailman useradd -c GNU Mailman -s /no/shell -d /no/home -s mailman mailman cd /var/lib/mailman chgrp mailman . chmod a_rx,g+ws . ./configure --prefix=/usr/lib/mailman --with-var-prefix=/var/lib/mailman --with-cgi-gid=service --with-username=mailman --with-groupname=mailman --with-mail-gid=Debian-exim make clean make make install check_parms -f At this point I still got the error I mentioned in the first bug report, but I was getting helpful info from the mailman error log, which was a permissions denied message. I removed the suexec, and got a we've hit a bug! message, but nothing in the error log -- I changed the error log to be writeable by everyone, and got a message about the config.pck of one of my pre-existing lists having permission denied. I fixed that, and then had to also do chmod a+rx,g+ws /var/lib/mailman/cgi-bin/* and then it was working. If set up a backup server to this one I might be able to experiment more. However I will probably also set up that web server to run as the normal www-data in order to be simpler. A few more notes below . . . Lionel == Lionel Elie Mamane [EMAIL PROTECTED] writes: Lionel Lionel On Wed, Jun 07, 2006 at 02:39:30AM -0500, Rob Ristroph wrote: I installed mailman with apt-get. Lionel It worked at least well enough to create some lists at some point. Since then the system has been apt-get upgraded several times. Lionel Lionel Did you install 2.1.8 or an older version originally? It was 2.1.8. Now, when I go to any of the mailman links, such as listinfo or the admin page of a list, I get this in my browser: Lionel Internal Server Error Lionel The server encountered an internal error or misconfiguration and was unable to complete your request. Lionel Lionel Isn't your _web server_ CGI configuration fucked up? Do other CGIs Lionel work? Other CGI's worked at that time. This was the only one that didn't. Lionel This looks more like an Apache error message than a Mailman one to Lionel me. Yes, that is possible. In the configuration I am currently using does not use SuExec. It is possible that I was trying to SuExec to a user/group with uid/gid below 100, and that was generating the error. Among other background information you should know: Lionel -- I had to ln -s /usr/lib/cgi-bin/mailman /usr/lib/mailman/cgi-bin/ before the gforge apache configs would find mailman properly Lionel Lionel That is gforge's bug. Please file a separate bug against Lionel gforge-lists-mailman and tell them (add Lionel [EMAIL PROTECTED] to the CC list for that Lionel bug; reportbug will give you the opportunity to do that). OK, I will. -- The output of check_perms: = check_perms -f Lionel /var/lib/mailman/mail bad group (has: root, expected list) (fixing) /var/lib/mailman/cgi-bin bad group (has: root, expected list) (fixing) /var/lib/mailman/logs bad group (has: root, expected list) (fixing) /var/lib/mailman/Mailman bad group (has: root, expected list) (fixing) /var/lib/mailman/bin bad group (has: root, expected list) (fixing) /var/lib/mailman/icons bad group (has: root, expected list) (fixing) /var/lib/mailman/templates bad group (has: root, expected list) (fixing) /var/lib/mailman/locks bad group (has: root, expected list) (fixing) /var/lib/mailman/scripts bad group (has: root, expected list) (fixing) /var/lib/mailman/cron bad group (has: root, expected list) (fixing) Lionel Lionel These are false positives; on a Debian system, those are symlinks, and Lionel check_perms looks at the symlink and not at its target; the targets Lionel have the right group, as far as I can see. I eventually fixed them by hand when I re-installed from source. I don't think those errors were related to the problem. Warning: Private archive directory is other-executable (o+x). This could allow other users on your system to read private archives. Lionel Lionel Yes, but that's the only
Bug#371074: mailman: web interface gives internal server error
Joost == Joost van Baal [EMAIL PROTECTED] writes: Joost Joost On Wed, Jun 07, 2006 at 02:39:30AM -0500, Rob Ristroph wrote: Package: mailman Version: 2.1.8-1 Severity: grave Justification: renders package unusable More information about this error may be available in the server error log. == Joost snip other stuff (but not the server error log) Joost Joost What does the server error log say? Please supply this information to Joost this bugreport. Joost Joost Bye, Joost Joost Joost == Joost snip other stuff (but not the server error log) Joost Joost What does the server error log say? Please supply this information to Joost this bugreport. Joost Joost Bye, Joost Joost Joost It is empty: ls -la /var/log/mailman/ total 84 drwxrwsr-x 2 root list 4096 2006-06-07 07:54 . drwxr-xr-x 18 root root 4096 2006-06-07 07:54 .. -rw-rw-r-- 1 list list0 2006-06-04 07:58 error -rw-rw-r-- 1 list list0 2006-05-28 07:36 error.1 --Rob -- http://rgr.freeshell.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#371074: mailman: web interface gives internal server error
Package: mailman Version: 2.1.8-1 Severity: grave Justification: renders package unusable I installed mailman with apt-get. It installed as a dependancy when I was installing gforge. It worked at least well enough to create some lists at some point. Since then the system has been apt-get upgraded several times. Now, when I go to any of the mailman links, such as listinfo or the admin page of a list, I get this in my browser: Internal Server Error The server encountered an internal error or misconfiguration and was unable to complete your request. Please contact the server administrator, [EMAIL PROTECTED] and inform them of the time the error occurred, and anything you might have done that may have caused the error. More information about this error may be available in the server error log. == Among other background information you should know: -- I had to ln -s /usr/lib/cgi-bin/mailman /usr/lib/mailman/cgi-bin/ before the gforge apache configs would find mailman properly -- The output of check_perms: = check_perms -f /var/lib/mailman/mail bad group (has: root, expected list) (fixing) /var/lib/mailman/cgi-bin bad group (has: root, expected list) (fixing) /var/lib/mailman/logs bad group (has: root, expected list) (fixing) /var/lib/mailman/Mailman bad group (has: root, expected list) (fixing) /var/lib/mailman/bin bad group (has: root, expected list) (fixing) /var/lib/mailman/icons bad group (has: root, expected list) (fixing) /var/lib/mailman/templates bad group (has: root, expected list) (fixing) /var/lib/mailman/locks bad group (has: root, expected list) (fixing) /var/lib/mailman/scripts bad group (has: root, expected list) (fixing) /var/lib/mailman/cron bad group (has: root, expected list) (fixing) Warning: Private archive directory is other-executable (o+x). This could allow other users on your system to read private archives. If you're on a shared multiuser system, you should consult the installation manual on how to fix this. Problems found: 10 Re-run as list (or root) with -f flag = Also, instead of apache running as www-data on this system, it is running as another user; however, it runs mailman as the user it expects via the suexec directive, I have this in the apache conf file: SuexecUserGroup www-data www-data I see no messages in the logs when the error happens, except for this in the gforge apache logs: [Wed Jun 07 02:24:31 2006] [error] [client 70.112.100.20] Premature end of script headers: admin, referer: http://gforge.mydomain.com/mail/admin/index.php?group_id=7 I can't find a core file or anything like that. I should also mention I removed the mailman package at one point and installed the current version of mailman from source, but with the same results (I thought I was installing it wrong at the time). When I installed from source I set the gid and uid to be what the webserver was using and didn't do the suexec thing. --Rob -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.12-1-386 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Versions of packages mailman depends on: ii adduser 3.87 Add and remove users and groups ii apache2-mpm-prefork [httpd] 2.0.55-4 traditional model for Apache2 ii cron 3.0pl1-94 management of regular background p ii debconf [debconf-2.0] 1.4.72 Debian configuration management sy ii exim4 4.60-3 metapackage to ease exim MTA (v4) ii exim4-daemon-heavy [mail-tran 4.60-3 exim MTA (v4) daemon with extended ii libc6 2.3.6-7GNU C Library: Shared libraries ii logrotate 3.7.1-3Log rotation utility ii pwgen 2.05-1 Automatic Password generation ii python2.3.5-5An interactive high-level object-o ii ucf 2.009 Update Configuration File: preserv Versions of packages mailman recommends: ii base-passwd 3.5.11 Debian base system master password -- debconf information: mailman/queue_files_present: * mailman/default_server_language: en mailman/update_passwords: mailman/gate_news: false mailman/update_aliases: * mailman/site_languages: en * mailman/used_languages: en * mailman/create_site_list: -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#349695: clamav-daemon: fails to install with unable to make backup link of `./usr/sbin/clamd'
Package: clamav-daemon Version: 0.87.1-1 Severity: grave Justification: renders package unusable Hi, I attempted to install the newer version of clamav with the command apt-get install clamav on a system that already had clamav on it. The clamav-daemon package had an error, and could not complete installation. Then that failed installation got stuck in my apt-get, so now I can't upgrade or install anything else either. Here is the what happens when I currently run apt-get -f install : www:~# apt-get -f install Reading package lists... Done Building dependency tree... Done Correcting dependencies... Done The following extra packages will be installed: clamav-daemon Suggested packages: daemon The following packages will be upgraded: clamav-daemon 1 upgraded, 0 newly installed, 0 to remove and 294 not upgraded. 6 not fully installed or removed. Need to get 40.2kB of archives. After unpacking 0B of additional disk space will be used. Do you want to continue [Y/n]? Y Get:1 ftp://mirrors.kernel.org testing/main clamav-daemon 0.88-2 [40.2kB] Fetched 40.2kB in 0s (42.0kB/s) (Reading database ... 72063 files and directories currently installed.) Preparing to replace clamav-daemon 0.87.1-1 (using .../clamav-daemon_0.88-2_i386.deb) ... Stopping ClamAV daemon: clamd. Unpacking replacement clamav-daemon ... dpkg: error processing /var/cache/apt/archives/clamav-daemon_0.88-2_i386.deb (--unpack): unable to make backup link of `./usr/sbin/clamd' before installing new version: Operation not permitted Starting ClamAV daemon: clamd. Errors were encountered while processing: /var/cache/apt/archives/clamav-daemon_0.88-2_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) www:~# I'm kind of stuck here -- I don't want to remove clamav and then install it fresh, although I will try that, because then I will end up with no clamav at all if the install of the latest version fails. In general, is there a way to cancel the installation of a partly installed package, so that in the meantime I can install other stuff on the computer ? --Rob -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.12-1-386 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Versions of packages clamav-daemon depends on: pn clamav-base none (no description available) pn clamav-freshclam | clamav-dat none (no description available) ii libc6 2.3.5-8GNU C Library: Shared libraries an pn libclamav1none (no description available) ii lsb-base 3.0-11 Linux Standard Base 3.0 init scrip clamav-daemon recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#309276: Installation of gforge fails to connect to postgres db because it is using IDENT instead of a password
Package: gforge-db-postgresql
Version: 3.1-31
Hi,
I am attempting to install gforge using apt-get. Eventually
after answering a lot of configuration questions I got the
error below. Note that I can access the gforge database by
typing psql -U gforge gforge at the root prompt, and giving
it the password I set for the gforge db user in the
configuration part of the installation.
[EMAIL PROTECTED]:/etc/apache# apt-get install
Reading Package Lists... Done
Building Dependency Tree... Done
0 upgraded, 0 newly installed, 0 to remove and 269 not upgraded.
8 not fully installed or removed.
Need to get 0B of archives.
After unpacking 0B of additional disk space will be used.
Setting up gforge-db-postgresql (3.1-31) ...
Configuring for PostgreSQL 7.3 or later
create OKYou'll see some debugging info during this installation.
Do not worry unless told otherwise.
DBI connect('dbname=gforge;host=127.0.0.1','gforge',...) failed: FATAL: IDENT
authentication failed for user gforge at /usr/lib/gforge/lib/include.pl line
45
Uncaught exception from user code:
Cannot connect to database: at /usr/lib/gforge/lib/include.pl line 47.
main::db_connect called at /usr/lib/gforge/bin/db-upgrade.pl line 36
dpkg: error processing gforge-db-postgresql (--configure):
subprocess post-installation script returned error exit status 255
dpkg: dependency problems prevent configuration of gforge-ldap-openldap:
gforge-ldap-openldap depends on gforge-db-postgresql | gforge-db; however:
Package gforge-db-postgresql is not configured yet.
Package gforge-db is not installed.
Package gforge-db-postgresql which provides gforge-db is not configured yet.
dpkg: error processing gforge-ldap-openldap (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of gforge-cvs:
gforge-cvs depends on gforge-ldap-openldap | gforge-ldap; however:
Package gforge-ldap-openldap is not configured yet.
Package gforge-ldap is not installed.
Package gforge-ldap-openldap which provides gforge-ldap is not configured yet.
dpkg: error processing gforge-cvs (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of gforge-dns-bind9:
gforge-dns-bind9 depends on gforge-db-postgresql | gforge-db; however:
Package gforge-db-postgresql is not configured yet.
Package gforge-db is not installed.
Package gforge-db-postgresql which provides gforge-db is not configured yet.
dpkg: error processing gforge-dns-bind9 (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of gforge-ftp-proftpd:
gforge-ftp-proftpd depends on gforge-ldap-openldap | gforge-ldap; however:
Package gforge-ldap-openldap is not configured yet.
Package gforge-ldap is not installed.
Package gforge-ldap-openldap which provides gforge-ldap is not configured yet.
dpkg: error processing gforge-ftp-proftpd (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of gforge-mta-exim4:
gforge-mta-exim4 depends on gforge-ldap-openldap | gforge-ldap; however:
Package gforge-ldap-openldap is not configured yet.
Package gforge-ldap is not installed.
Package gforge-ldap-openldap which provides gforge-ldap is not configured yet.
dpkg: error processing gforge-mta-exim4 (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of gforge-lists-mailman:
gforge-lists-mailman depends on gforge-db-postgresql | gforge-db; however:
Package gforge-db-postgresql is not configured yet.
Package gforge-db is not installed.
Package gforge-db-postgresql which provides gforge-db is not configured yet.
gforge-lists-mailman depends on gforge-ldap-openldap | gforge-ldap; however:
Package gforge-ldap-openldap is not configured yet.
Package gforge-ldap is not installed.
Package gforge-ldap-openldap which provides gforge-ldap is not configured yet.
gforge-lists-mailman depends on gforge-mta-exim4 | gforge-mta; however:
Package gforge-mta-exim4 is not configured yet.
Package gforge-mta is not installed.
Package gforge-mta-exim4 which provides gforge-mta is not configured yet.
dpkg: error processing gforge-lists-mailman (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of gforge-shell-ldap:
gforge-shell-ldap depends on gforge-ldap-openldap | gforge-ldap; however:
Package gforge-ldap-openldap is not configured yet.
Package gforge-ldap is not installed.
Package gforge-ldap-openldap which provides gforge-ldap is not configured yet.
dpkg: error processing gforge-shell-ldap (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
gforge-db-postgresql
gforge-ldap-openldap
gforge-cvs
gforge-dns-bind9
gforge-ftp-proftpd
gforge-mta-exim4
Bug#301598: bootcd: cd cannot boot -- /sbin/init cannot open dev/console
Bernd == Bernd Schumacher Schumacher writes: Bernd Bernd Hi, Bernd thanks for your bugreport. Bernd Bernd 1. do you use initrd ? Bernd if yes, Bernd 2.1 can you send me a tar of the directory /etc/mkinitrd ? Bernd 2.2 does the CDDEV definition in bootcdwrite.conf start with CDDEV=auto ? Hi, Unfortunately, due to things I can't control, I won't have physical access to the computer I was using to do this for another two weeks. It was a Debian Testing, recently updated; so I believe it was using initrd. I am going to attempt to re-create the problem on a different Debian Testing installation, and I will send further information in a couple of days. --Rob -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#301598: bootcd: cd cannot boot -- /sbin/init cannot open dev/console
Package: bootcd Version: 2.47 Severity: grave Justification: renders package unusable Note that I have previously successfully created working CDs using bootcd on this installation; the following started happening after an apt-get upgrade a couple of weeks ago. When the created ISO is booted, it freezes up, and these are the last messages on the screen: pivot_root: No such file or directory /sbin/init: 426: cannot open dev/console: No such file Kernel panic: Attempted to kill init! I have the kernel and initrd set correctly in bootcdwrite.conf. Let me know if I can help by sending you my bootcdwrite.conf file or the created ISO or parts of it. Thanks in advance for any attention you can give this, and thanks for writing bootcd -- I have found it to be an extremely useful utility. --Rob Ristroph -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.4.27-1-386 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Versions of packages bootcd depends on: ii bootcd-i386 2.47 bootcd extension to create images ii cpio 2.5-1.2GNU cpio -- a program to manage ar ii dosfstools2.10-1 Utilities to create and check MS-D ii fdutils 5.4-20040228-1 Linux floppy utilities ii file 4.12-1 Determines file type using magic ii mkisofs 4:2.01+01a01-2 Creates ISO-9660 CD-ROM filesystem ii realpath 1.9.16 Return the canonicalized absolute -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
