Re: DSA 438 - bad server time, bad kernel version or information delayed?
On Wed, Feb 18, 2004 at 04:44:15PM -0500, Michael Stone wrote: > On Wed, Feb 18, 2004 at 09:17:13PM +0100, Florian Weimer wrote: > >Yes, this is the norm. Debian hides security bugs from its users for > >extended periods of time. > > begone, troll Casting a spell on him won't work either :-), he'll raise his head again next time this issue comes up. Obviously he isn't capable of accepting defeat. . Siggy
Re: DSA 438 - bad server time, bad kernel version or information delayed?
On Wed, Feb 18, 2004 at 04:44:15PM -0500, Michael Stone wrote: > On Wed, Feb 18, 2004 at 09:17:13PM +0100, Florian Weimer wrote: > >Yes, this is the norm. Debian hides security bugs from its users for > >extended periods of time. > > begone, troll Casting a spell on him won't work either :-), he'll raise his head again next time this issue comes up. Obviously he isn't capable of accepting defeat. . Siggy -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: get error: /bin/sh: line1: myfilter: command in boot messages...
On Wed, Jan 21, 2004 at 02:11:39PM -0500, Walter Tautz wrote: > specically I have a /bin/sh script in /etc/network/if-pre-up.d/myfilter: > > #! /bin/sh [...] > which DOES work. I wonder why it's complaining about the line #! /bin/sh > during the boot messages. Note no such output is in dmesg. The shebang bites again :) Here's some reading on it: http://www.in-ulm.de/~mascheck/various/shebang/ Thanks . Siggy
Re: get error: /bin/sh: line1: myfilter: command in boot messages...
On Wed, Jan 21, 2004 at 02:11:39PM -0500, Walter Tautz wrote: > specically I have a /bin/sh script in /etc/network/if-pre-up.d/myfilter: > > #! /bin/sh [...] > which DOES work. I wonder why it's complaining about the line #! /bin/sh > during the boot messages. Note no such output is in dmesg. The shebang bites again :) Here's some reading on it: http://www.in-ulm.de/~mascheck/various/shebang/ Thanks . Siggy -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
