Testing Jigdo Files

Hi all, Just wondering if anyone has any ideas as to when the Jigdo templates etc. for testing will be available for download again? I realise this is probably an old subject, but I've only just joined the list and couldn't find anything on a Google search... Pete -- To UNSUBSCRIBE, email to

Strange Behaviour of Bash in debian/testing: can't type slash

Hi, after an upgrade of my system (debian/testing, previous update at June 2003) I found a strange behaviour in the bash: anytime I type the slash character, I get a beep (more precisely a visual bell), but no '/'. I suppose, this is a problem related to the configuration of the Bash (libreadline

someone has made my init unhappy.

I have started experiencing a rather frustrating problem recently, well within the past month or so anyway. It has taken a more irritating turn in the past few days. I usually logout of my various consoles each evening before leaving the office. I have noticed that recently sometimes one or so o

Re: someone has made my init unhappy.

Hi, On Thu, Jan 08, 2004 at 09:09:02AM -0500, Kirk Reiser wrote: > [...] > INIT: Id "8" respawning too fast: disabled for 5 minutes ID 8 usually mean "the process running with process ID 8 ...". If you get this message again, try to login on any other console (or remotely) to find the process run

Re: someone has made my init unhappy.

I am familiar with what the id means and I'm currently getting that message every five minutes. I am logged in on 9 other consoles and have no idea what I might do to clear the problem on that console. I have tried sending a sighup to init to reload the inittab. I have tried killing off the gett

Re: someone has made my init unhappy.

* Hans-Georg Bork ([EMAIL PROTECTED]) [040108 20:25]: > On Thu, Jan 08, 2004 at 09:09:02AM -0500, Kirk Reiser wrote: > > [...] > > INIT: Id "8" respawning too fast: disabled for 5 minutes > ID 8 usually mean "the process running with process ID 8 ...". Wrong. That mean: The tasked named 8 in /etc

Re: someone has made my init unhappy.

I have the same problem (running unstable): meanwhile tty2 is hanging and logouts from the other tty's are extremely slow (except on tty1)... There is already a bug report: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=224067 Hopefully it will be fixed soon? Rudolf -- Rudolf Lohner --