On Thu, 2002-02-21 17:43:48 +0100, Karsten Merker <karsten@excalibur.cologne.de> wrote in message <[🔎] 20020221174348.A254@excalibur.cologne.de>: > On Thu, Feb 21, 2002 at 03:46:57PM +0100, Jan-Benedict Glaw wrote: > > > Well, I've now compiled my own kernel (linux_2_4) with the toolchain I > > found on oss.sgi.com. It's quite _a lot_ more stable now. Maybe the > > boot-floppy guys would like to use a different kernel for boot-up? > What I find strange nonetheless that you get better working kernels > with the cross-toolchain from oss - I have had serious problems with > kernels compiled by it, while the same kernel source compiled natively > by the default Debian gcc 2.95.4 worked fine. This is the only toolchain I had by my hands. I've taken a fresh cvs co (from my local rsync'ed sources) and it's working quite nice now: 192:~# uptime 18:23:04 up 3:05, 2 users, load average: 0.75, 0.45, 0.19 The machine's installation is not perfect: I'm currently replacing all the simply extracted files/debs by really installing them. Btw., I don't get any questions when I attempt to install packages. I think this is due to the fact that debconf (or apt) wasn't really installed at the first time. How do I choose the configuration frontend once again? Another question: install-info (or Perl?) is still broken. Any hints on debugging this? MfG, JBG -- Jan-Benedict Glaw . jbglaw@lug-owl.de . +49-172-7608481 -- New APT-Proxy written in shell script -- http://lug-owl.de/~jbglaw/software/ap2/
Attachment:
pgpok7cR4bQnz.pgp
Description: PGP signature