Installation Report: Fresh LaTex-Koma-Script for Debian-Linux

[Stefan Salewski]

Update of Koma-Script package for Debian-TeTex from www.dante.de

The Koma-Script-package of current Debian-Linux has date 31.01.2003.
I asked at [EMAIL PROTECTED] and got an reply by Hilmar Preusse
that there will be no update in next time. He suggested to install a local copy from 
www.dante.de. 

Here is a short installation report. Maybe this is helpful for other people.
I have tried to write down all steps carefully, but there is no warranty from me.
I am not a very experienced Debian- and LaTex-user.

Best regards

Stefan Salewski

Here is my installation report:

--

  cd
  mkdir tmp
  cd tmp

  ftp ftp.dante.de
  cd pub/tex/macros/latex/contrib
  get koma-script.tar.gz
  exit

  tar -xvzf koma-script.tar.gz

In tetex configuration file /etc/texmf/texmf.d/05TeXMF.cnf
there is an entry

  % A place for local additions to a "standard" texmf tree.  For example:
  TEXMFLOCAL = /usr/local/share/texmf

so we can store new koma-script there.

  cd /usr/local/share/
  su
  mkdir texmf # on my system there was no texmf
  exit

  cd 
  cd tmp/koma-script
  less INSTALL(D).TXT

  cp Makefile.unx Makefile

replace in Makefile line 
INSTALLTEXMF=`kpsewhich --expand-var '$$TEXMFLOCAL'`
with 
INSTALLTEXMF=/usr/local/share/texmf

  su
  make
  make install

make install will ask about overwriting files.
This is a bit strange.
Answer two times "y" (yes)
I think this will not really overwrite files, but insert files in
new tree /usr/local/share/texmf.

exit

Test if new koma-script is used, and old one is ignored:

  cd
  mkdir test
  cd test
  
Create testfile named Test.tex which looks like this:

\documentclass{scrartcl}
\begin{document}
dummy
\end{document}

latex Test

less Test.log

You should find a remark that the new package of koma-script is used.

--


-- 
Haeufig gestellte Fragen und Antworten (FAQ): 
http://www.de.debian.org/debian-user-german-FAQ/

Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED]
mit dem Subject "unsubscribe". Probleme? Mail an [EMAIL PROTECTED] (engl)

Zu viele Modprobe-Fehler in /var/log/syslog

[Stefan Salewski]

Hallo,

ich verwende seit einigen Wochen Debian-Testing.
Es funktioniert auch fast alles sehr gut, bloß wird mein Rechner 
mitten im Betrieb immer wieder durch seltsame Modprobe-Aufrufe 
stark ausgebremmst. 
Man muss dann die Arbeit für ca. 20 Sekunden unterbrechen, top 
zeigt, dass Modprobe 97% der cpu-Zeit verbraucht. Nach ca. 20 
Sekunden kann man dann weiterarbeiten.

Ich kann momentan nicht die Ursache finden, mit SuSE8.2 gab es 
dieses Problem nicht. Nachfolgend ein Ausschnitt 
aus /var/log/syslog, ich hoffe mir kann jemand einen Hinweis 
geben, warum Modprobe mitten im Betrieb versucht, für nicht 
existierende Geräte Treiber zu laden.

Mail bitte auch direkt an mich:
[EMAIL PROTECTED]

Gruß

Stefan Salrewski

--

ICAS8:/home/salewski# tail -n 30 /var/log/syslog
Jun 14 13:52:03 localhost kernel: sbpcd-0 [04]:  No drive found.
Jun 14 13:52:03 localhost modprobe: FATAL: Error inserting sbpcd 
(/lib/modules/2.6.6-1-k7/kernel/drivers/cdrom/sbpcd.ko): 
Input/output error
Jun 14 13:52:03 localhost kernel: sbpcd-0 [01]:  sbpcd.c v4.63 
Andrew J. Kroll <[EMAIL PROTECTED]> Wed Jul 26 04:24:10 
EDT 2000
Jun 14 13:52:03 localhost kernel: sbpcd-0 [02]:  Scanning 0x340 
(LaserMate)...
Jun 14 13:52:35 localhost kernel: sbpcd-0 [03]:  Scanning 0x340 
(SoundBlaster)...
Jun 14 13:53:08 localhost kernel: sbpcd-0 [04]:  No drive found.
Jun 14 13:53:08 localhost modprobe: FATAL: Error inserting sbpcd 
(/lib/modules/2.6.6-1-k7/kernel/drivers/cdrom/sbpcd.ko): 
Input/output error
Jun 14 13:53:08 localhost kernel: sbpcd-0 [01]:  sbpcd.c v4.63 
Andrew J. Kroll <[EMAIL PROTECTED]> Wed Jul 26 04:24:10 
EDT 2000
Jun 14 13:53:08 localhost kernel: sbpcd-0 [02]:  Scanning 0x340 
(LaserMate)...
Jun 14 13:53:40 localhost kernel: sbpcd-0 [03]:  Scanning 0x340 
(SoundBlaster)...
Jun 14 13:54:00 localhost kernel: via_audio: ignoring drain 
playback error -11
Jun 14 13:54:13 localhost kernel: sbpcd-0 [04]:  No drive found.
Jun 14 13:54:13 localhost modprobe: FATAL: Error inserting sbpcd 
(/lib/modules/2.6.6-1-k7/kernel/drivers/cdrom/sbpcd.ko): 
Input/output error
Jun 14 13:54:13 localhost modprobe: FATAL: Error inserting cdu31a 
(/lib/modules/2.6.6-1-k7/kernel/drivers/cdrom/cdu31a.ko): 
Input/output error
Jun 14 13:54:13 localhost modprobe: FATAL: Error inserting cdu31a 
(/lib/modules/2.6.6-1-k7/kernel/drivers/cdrom/cdu31a.ko): 
Input/output error
Jun 14 13:54:21 localhost kernel: mcd: initialisation failed - No 
mcd device at 0x300 irq 11
Jun 14 13:54:21 localhost modprobe: FATAL: Error inserting mcd 
(/lib/modules/2.6.6-1-k7/kernel/drivers/cdrom/mcd.ko): 
Input/output error
Jun 14 13:54:21 localhost kernel: mcd: Initialization failed, I/O 
port (300) already in use
Jun 14 13:54:21 localhost modprobe: FATAL: Error inserting mcd 
(/lib/modules/2.6.6-1-k7/kernel/drivers/cdrom/mcd.ko): 
Input/output error
Jun 14 13:54:21 localhost kernel: SJCD: Sanyo CDR-H94A cdrom 
driver version 1.7.
Jun 14 13:54:22 localhost kernel: SJCD: Resetting: .. 
reset failed, no drive found.
Jun 14 13:54:22 localhost modprobe: FATAL: Error inserting sjcd 
(/lib/modules/2.6.6-1-k7/kernel/drivers/cdrom/sjcd.ko): 
Input/output error
Jun 14 13:54:22 localhost kernel: SJCD: Sanyo CDR-H94A cdrom 
driver version 1.7.
Jun 14 13:54:23 localhost kernel: SJCD: Resetting: .. 
reset failed, no drive found.
Jun 14 13:54:23 localhost modprobe: FATAL: Error inserting sjcd 
(/lib/modules/2.6.6-1-k7/kernel/drivers/cdrom/sjcd.ko): 
Input/output error
Jun 14 13:54:43 localhost kernel: optcd: unknown drive detected; 
aborting
Jun 14 13:54:43 localhost modprobe: FATAL: Error inserting optcd 
(/lib/modules/2.6.6-1-k7/kernel/drivers/cdrom/optcd.ko): 
Input/output error
Jun 14 13:55:04 localhost kernel: optcd: unknown drive detected; 
aborting
Jun 14 13:55:04 localhost modprobe: FATAL: Error inserting optcd 
(/lib/modules/2.6.6-1-k7/kernel/drivers/cdrom/optcd.ko): 
Input/output error
Jun 14 13:56:07 localhost kernel: via_audio: ignoring drain 
playback error -11
ICAS8:/home/salewski#