Vos courriers sont indésirables
Je suis une vieille dame veuillez supprimer mon adresse de vos fichiers
You're invited to the first test of the Global Debian bimonthly evening
meetings at BerkeleyTIP-Global. :)
Join in tonight, Monday Jan 11, 5-6P Pacific, 8-9P Eastern, = Tues Jan
12 1A-2A UTC.
http://sites.google.com/site/berkeleytip/schedule
On #berkeleytip on irc.freenode.net,
& on voip - whate
Dear guru's,
I'm getting an OOPS on a recently installed Debian box. Before upgrading to
the latest woody 2.4.18-bf2.4 it would crash hard, killing interrupt
handler. Now, it gets an OOPS but keeps on running. The problem is I
cannot run anything that looks at the process table, or that process
oes, just look at the file created in the directory
you were in while running this command,
it should have a name like XF86Config.new
or something, and find the differences with your config file (especially
in the
"device" section).
gl,
Wim
require it are telnet.monitor and tcp.monitor,
> BTW.
Yup.. the 2 that I'm looking at.. :)
> Alternately, one can probably use netcat to do what tcp_scan does, at
> least for the simple uses mon puts it to. I might find out what the
> those tcp_scan args to and supply nc-based
a package of
SATAN or of just tcp_scan available. I haven't looked into packaging it.
The only monitors which require it are telnet.monitor and tcp.monitor,
BTW.
Alternately, one can probably use netcat to do what tcp_scan does, at
least for the simple uses mon puts it to. I might find out what the
I'm playing with mon as a packaged alternative to nocol, and I have 2
questions:
1) Is df.pm debianized?
2) Is tcp_scan part of a debian package yet?
Both of these are used by mon..
Tim
--
(work) [EMAIL PROTECTED] / (home) [EMAIL PROTECTED] - http://www.buoy.com/~tps
"Why
7 matches
Mail list logo
