Hi,
am not sure if this is related to my -current kernel or last recent
ssh changes but perhaps you have an idea.
Since yesterday I'm not able, to upload some files using rsync over ssh.
Attached is a short tcpdump.
netstat shows it this way:
input (xl0) output
I have seen this problem with rsync as well. I think I solved it
by downstepping to an older rsync version.
Poul-Henning
In message [EMAIL PROTECTED], Andreas Klemm writes:
--UlVJffcvxoiEqYs2
Content-Type: text/plain; charset=us-ascii
Hi,
am not sure if this is related to my -current
Hi,
Whats the right way od downing or reiniciating gif interface?
"ifconfig gif# down" doesnt seems to work
if its in mans just tell me where to look
Regards,
pal
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
I've got an mfs /tmp too :-]
Hi,
On 0, Ted Sikora [EMAIL PROTECTED] wrote:
After building a new kernel yesterday after a cvsup the following
appeared.
Apr 17 23:07:42 telecast /kernel: WARNING: run /dev/MAKEDEV before
2000-06-01 to get rid of block devices
I did a MAKEDEV all
Yes, that was an oversight on my part. Please let me know if the
fix I committed solves this issue.
Poul-Henning
In message [EMAIL PROTECTED], Brian Somers writes:
I've got an mfs /tmp too :-]
Hi,
On 0, Ted Sikora [EMAIL PROTECTED] wrote:
After building a new kernel yesterday after a
On Sat, 22 Apr 2000, Andreas Klemm wrote:
am not sure if this is related to my -current kernel or last recent
ssh changes but perhaps you have an idea.
No idea on this, but:
BTW, could someone on freefall please update the ports collection.
Nothing works, if I want to build a port with the
Hi,
Whats the right way od downing or reiniciating gif interface?
"ifconfig gif# down" doesnt seems to work
if its in mans just tell me where to look
what do you mean by "reniciating"? if you would like to overwrite
configuration, you just need to "gifconfig gif0 newsrc
On Sat, Apr 22, 2000 at 09:19:50AM +0200, Poul-Henning Kamp wrote:
I have seen this problem with rsync as well. I think I solved it
by downstepping to an older rsync version.
Thanks !
--
Andreas Klemm http://people.FreeBSD.ORG/~andreas
On Sat, Apr 22, 2000 at 02:47:58AM -0700, Kris Kennaway wrote:
If you have a checked out copy of the ports collection in your home
directory you can point to it with the PORTSDIR variable and everything
will work fine. Having said that, an update of the /usr/ports dir would be
good.
Yes
On Sat, 22 Apr 2000 01:45:20 -0400 (EDT), "Brandon D. Valentine"
[EMAIL PROTECTED] said:
to include support for the MCA bus. The vast majority of MCA bus
machines in existence utilize ESDI because they predate the UDMA and
AFAIK, the only MCA disk controller supported does SCSI.
-GAWollman
The warning mentions the date 2000-06-01. What are you planning to
happen on that date? Whatever it is, please make it tolerant. I
don't care whether I can _use_ the old block devices, but I would
like to be able to ls them, dump them, restore them, etc., without
terrible consequences. (I
In message [EMAIL PROTECTED], John Polstra writes:
The warning mentions the date 2000-06-01. What are you planning to
happen on that date? Whatever it is, please make it tolerant.
My intention is to make the system whine even louder starting around
2000-05-01 and then I lean towards a sysctl
Hello to the FreeBSD community,
Would anyone mind telling me what RAID cards are supported and how good SNP is
with FreeBSD. We intend to build machines with up to 8 Intel PIII's and if SNP
cannot work with it, obviously anyone getting such a machine would be a tad
upset.
Thank you kindly for
On Sat, 22 Apr 2000 01:45:20 -0400 (EDT), "Brandon D. Valentine"
[EMAIL PROTECTED] said:
to include support for the MCA bus. The vast majority of MCA bus
machines in existence utilize ESDI because they predate the UDMA and
AFAIK, the only MCA disk controller supported does SCSI.
The
...trying to upgrade from 4.0-CURRENT (last update 21 Jul 99) to
5.0-CURRENT (22 Apr at 0419 UCT) using cvsup over 56K.
I know, I know, I fell behind, but it was doing its thing --ran
for 272 days without even restarting X although the aux generator
fired up during a couple
On Sat, 22 Apr 2000, Brandon D. Valentine wrote:
However, FreeBSD just went ahead with its first release to include
support for the MCA bus. The vast majority of MCA bus machines in
existence utilize ESDI because they predate the UDMA and ATA66
efforts. If we are to support MCA, how can we
I've completed the bmake framework for libgmp 3.0 which is ready to commit
- see http://people.FreeBSD.org/~kris/libgmp.tar.gz
However, I was looking at what in the base system actually uses
libgmp/libmp, and I could only spot four users:
chkey, newkey, keyserv (Secure RPC)
telnet
All of these
On Sat, 22 Apr 2000, Rodney W. Grimes wrote:
AFAIK, the only MCA disk controller supported does SCSI.
The IBM PS/2 family supported them all, ST506, ESDI and SCSI...
I think he is talking about the MCA disk controllers supported by FreeBSD,
which are the Buslogic MCA and the Adaptec MCA.
18 matches
Mail list logo
