Bug#338371: kernel-package: Kernel-package mess up the /boot/grub/menu.lst

2005-11-09 Thread John Plate
Package: kernel-package Version: 8.135 Severity: normal I installed Debian with netinst normally. (I configured raid-1 and it worked fine - shouldn't have anything with this to do, though). I compiled a new kernel using /boot/config-2.6.8-2-686 as .config for the compilation. I couldn't compile a

Bug#338371: What is wrong?

2005-11-10 Thread John Plate
Otavio Salvador wrote: > I didn't understand what update-grub did wrong. kopt comment express > exactly what it intend to do and looks like it did its job. The problem is that, fx after installation, you have entries that can boot the system. If #kopt is changed and a homecompiled kernel is ins

Bug#338371: What is wrong?

2005-11-10 Thread John Plate
Jason Thomas wrote: > > The problem is that, fx after installation, you have entries that > > can boot the system. > > What, > > So after you install the system it is working fine. After installing the system, it works fine. > > If #kopt is changed and a homecompiled kernel is installed > > (

Bug#338371: What is wrong?

2005-11-10 Thread John Plate
Jason Thomas wrote: > > As said, after installing, raid-1 is installed. For future kernels, > > the raid drive (/dev/md0 in my case) is the one to use. Then the "# > > kopt" is set according to that. > > > > A new kernel (equal to the installed official image) is installed - > > and de-installed

Bug#289724: Enscript needs /etc/papersize

2005-01-10 Thread John Plate
Package: enscript Version: 1.6.4-5 1: Encript does not work if /etc/papersize does not exist. It produces illegal Postscript. 2: If I set DefaultMedia: A4 in /etc/enscript.cfg then enscript will segfault!! (if /etc/papersize does not exist) 3: Should enscript depend on libpaper-utils (w

Bug#369020: Bug IS reproducible

2006-10-20 Thread John Plate
Hi maintainer It is not possible to uninstall imapproxy. [ache] 4 ROOT:~# sh /etc/init.d/imapproxy start Starting IMAP proxy: grep: /proc/6756/cmdline: No such file or directory Failed to start imapproxy. Check logs for details. [ache] 4 ROOT:~# dpkg -r imapproxy (Reading database ... 64543 fil

Bug#468779: installation-reports: Install failed to recognize Intel Nineveh 82566DM adapter network on Econel 100 S2

2008-03-01 Thread John Plate
Package: installation-reports Severity: normal Debian testing (downloaded Feb 28, 2008) failed to recognize the network adapter Intel Nineveh 82566DM on a Fujitsu-Siemens Econel 100 S2 server. The hardware is described in ds_prim-econel-100-s2.pdf. Another network adapter cannot be used in the m

Bug#447056: logcheck-database: Logcheck-database cannot be installed

2007-10-17 Thread John Plate
Package: logcheck-database Version: 1.2.63 Severity: normal When trying to install I get this: ROOT:~# apt-get install logcheck-database Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed logcheck-database 0 upgr

Bug#447057: mon: Modules is now missing

2007-10-17 Thread John Plate
Package: mon Version: 0.99.2-12 Severity: normal An error is sent by mail: Summary output: statfs failed on / (new filesystem type?) at /usr/lib/mon/mon.d/freespace.monitor line 49 Group : harddisks Service : freespace This is a consequence of automatic upd

Bug#468779: installation-reports: Install failed to recognize Intel Nineveh 82566DM adapter network on Econel 100 S2

2008-03-04 Thread John Plate
Frans Pop wrote: > On Sunday 02 March 2008, you wrote: > > Thank you for your response. > > > > As far as the Intel document says, it is not bound to the 2.6 kernel. > > See http://www.intel.com/support/network/sb/cs-009209.htm > > > > We are several people who want a solution for this problem. If

Bug#468779: installation-reports: Install failed to recognize Intel Nineveh 82566DM adapter network on Econel 100 S2

2008-03-06 Thread John Plate
Hi Today I followed the instructions given in my former mail. On a well configured machine it will take 20 minutes (all included) to make the new driver module. It worked for me. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTEC