to that port?
nope -- and I've tried all sorts of ports other than 8000 too:
(I'm assuming you do have a lo0 device with 127.0.0.1)
Have you tried binding it to the address on the interface which
your host will send packets to the remote host over?
--
David Taylor
[EMAIL PROTECTED]
The future just
On Sat, 08 Nov 2003, David Taylor wrote:
Have you tried binding it to the address on the interface which
your host will send packets to the remote host over?
Erm, wait, I don't know what I was thinking there. ssh doesn't let you
specify the local address it binds to. All I can say
protection people from themselves.
--
David Taylor
[EMAIL PROTECTED]
The future just ain't what it used to be
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
, but
I'm sure it was smoother before I switched.
--
David Taylor
[EMAIL PROTECTED]
The future just ain't what it used to be
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL
cvsuped to -CURRENT, and discovered that the
opposite was now more stable (WITH_FREEBSD_AGP/agp_load=YES now causes
my computer to lockup regularly when in X).
I suggest you try the opposite setting and see if that helps. Also keep
WITH_FREEBSD_AGP and agp_load in 'sync'.
--
David Taylor
[EMAIL
If anyone wants any more info from the dump, just ask...
--
David Taylor
[EMAIL PROTECTED]
The future just ain't what it used to be
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail
On Tue, 12 Aug 2003, David Taylor wrote:
I've been getting this occasionally (a few times a day) since I upgraded
to -CURRENT yesterday. I tried installing Bosko's Intel Data Corruption
patch today, to see if that changed anything, but it doesn't appear to
have worked.
[snip]
*sigh*
Now
it would be possible to delete a couple of those leading
spaces on each line?
Although it fits into an 80-column display in vim/cat/whatever, mutt ends
up wrapping it, and making it very ugly, but removing a couple of the
spaces would make it fit fine.
--
David Taylor
[EMAIL PROTECTED]
The future
On Sun, 29 Jun 2003, David Taylor wrote:
I don't suppose it would be possible to delete a couple of those leading
spaces on each line?
Bah, ignore me, after deciding it was mutt's fault for wrapping it when it
shouldn't be, I found the 'wrapmargin' setting in my muttrc file...
Reducing
:25:26 BST 2002
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/GATTACA i386
However, at least that shows it isn't any local setup issue, I guess.
--
David Taylor
[EMAIL PROTECTED]
The future just ain't what it used to be
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current
On Tue, 16 Jul 2002, David Taylor wrote:
Bah, ignore me, it appears you've already admitted your post was rather
less than clear :)
--
David Taylor
[EMAIL PROTECTED]
The future just ain't what it used to be
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current
how the other u*.c files
handle detaching... any hints would be appreciated :)
--
David Taylor
[EMAIL PROTECTED]
The future just ain't what it used to be
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
On Tue, 12 Feb 2002, David Taylor wrote:
I have approximately no experience with FreeBSD device drivers, but I'm
currently attempting to see if I can figure out how the other u*.c files
handle detaching... any hints would be appreciated :)
Well. I managed to create a patch which _works_
means you have used an invalid combination of O_RDONLY, O_WRONLY, and
O_RDWR. But no error is listed in the manpage for an invalid filename,
other than ENAMETOOLONG, which is clearly inappropriate.
Perhaps the correct fix would just be to document the use of EINVAL?
--
David Taylor
[EMAIL PROTECTED
that if they have a USB
mouse, they need do nothing, insetad of think 'Uhh, I don't recognise any of
these, lets try this one' and getting it wrong.
--
David Taylor
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
reported the same panic a while ago. It appears to have been caused by
the last large KSE commit.
--
David Taylor
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
prepared to
crash my system.. (A simple cd /mnt/w2k/; ls; crashes the box. Oddly
enough, it didn't seem to have the same effect in single-user mode, not sure
why...)
--
David Taylor
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body
unlocking.
backtrace:
panic
lockmgr
vop_stdunlock
ntfs_inactive
vput
lstat
Unfortunately, gdb -k kernel.X vmcore.X is still coring on startup, so I
can't get any more info, unless someone has something they want me to do at
the DDB prompt.
--
David Taylor
[EMAIL PROTECTED]
PGP signature
On Thu, 31 May 2001, Bruce Evans wrote:
On Wed, 30 May 2001, David Taylor wrote:
When trying to profile ircd-hybrid-7 on -CURRENT (I tried using a pre-vm
madness version first, then tried a version cvsuped today), I reliably get
lots of:
kernel trap 12 with interrupts disabled
are detecting
the correct geometry, and FreeBSD isn't...
Unfortunately, if your drive doesn't have a jumper like that, I've no idea
what could be wrong...
--
David Taylor
[EMAIL PROTECTED]
PGP signature
regenerated, incorrectly, somewhere?)
--
David Taylor
[EMAIL PROTECTED]
PGP signature
21 matches
Mail list logo
