I've cvsuped the 5.2-RELEASE.
make buildworld was success.
- Original Message -
From: Mike Silbersack [EMAIL PROTECTED]
To: CHOI Junho [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Monday, January 19, 2004 7:12 AM
Subject: Re: FreeBSD - Windows HTTP TCP performance
On Thu, 15 Jan
I've cvsuped up to 5.2-RELEASE.
make buildworld was success.
Thanks.
- Original Message -
From: Ruslan Ermilov [EMAIL PROTECTED]
To: Dmitry A. Bondareff [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Thursday, January 15, 2004 5:53 PM
Subject: Re: Upgrade from 4.9 to 5.1
Hi,
I'm one of the users in need of a clean update path. I will dedicate a system
for update and geom_vinum tests.
Peter
On Tuesday 20 January 2004 21:25, Lukas Ertl wrote:
On Tue, 20 Jan 2004, Kevin Wooten wrote:
My 2 cents is to start building the house from the ground with the geom
On 01/21/04 09:26:58 +0100 Peter Blok wrote:
I'm one of the users in need of a clean update path. I will dedicate a system
for update and geom_vinum tests.
I step in. I complained bitterly about the rip-it-off-plans.
I'm currently not able to help out coding, but I would gladly
supply remote
On Wed, 21 Jan 2004, Andreas Braukmann wrote:
On 01/21/04 09:26:58 +0100 Peter Blok wrote:
I'm one of the users in need of a clean update path. I will dedicate a system
for update and geom_vinum tests.
I step in. I complained bitterly about the rip-it-off-plans.
I'm currently not able to
On Tue, Jan 20, 2004 at 07:47:02PM +0100, Lukas Ertl wrote:
+ I think we should really get together on a separate mailing list - is it
+ time for freebsd-geom@ yet?
My proposal is [EMAIL PROTECTED]
--
Pawel Jakub Dawidek [EMAIL PROTECTED]
UNIX Systems
Greg 'groggy' Lehey [EMAIL PROTECTED] wrote:
And to answer another message: yes, Vinum on FreeBSD *must*
be adapted to GEOM. There's no other solution.
shouldn't we add this as a task item to the releng schedule?
-josef
--
Josef El-Rayes (__)
Email:[EMAIL PROTECTED]
In article [EMAIL PROTECTED] you write:
It seems Kevin Serwick wrote:
Hi all,
I added some files to a multisession CD-R with the
burncd command. It appeared to work fine, but when I
read the disk, the new files didn't show up. So I did
the burncd fixate command - bad idea! Now nothing
The /dev/crypto testing program in FreeBSD, like in NetBSD, was
derived from a test program which I never published with a free
license. It has now been deleted from the NetBSD tree as well.
Please delete it from the FreeBSD tree as well.
Because apparently Sam is too busy to keep your tree
On Wed, 21 Jan 2004, Lukas Ertl wrote:
I step in. I complained bitterly about the rip-it-off-plans.
s/plans/proposal/
I'm currently not able to help out coding, but I would gladly
supply remote console access to a box suitable for vinum testing.
(Including access to a local
Theo,
On Tue, 20 Jan 2004, Theo de Raadt wrote:
The /dev/crypto testing program in FreeBSD, like in NetBSD, was
derived from a test program which I never published with a free
license. It has now been deleted from the NetBSD tree as well.
I'm just curious but when looking at the source I
On Sun, Jan 18, 2004 at 10:19:31AM -0500, Allan Fields wrote:
On Sun, Jan 18, 2004 at 02:43:42PM +0100, Simon L. Nielsen wrote:
On 2004.01.17 14:53:58 -0500, Allan Fields wrote:
Hi,
I'm interested to know what may be in the pipeline as far as GBDE
boot time attach/automation
On Wed, Jan 21, 2004 at 03:20:40PM +, Olafur Osvaldsson wrote:
I'm just curious but when looking at the source I see the following
in the crypto.c file:
* The author of this code is Angelos D. Keromytis ([EMAIL PROTECTED])
I'm not sure that is the file to which he is referring. I don't
On Wed, Jan 21, 2004 at 04:26:09PM +0100, Poul-Henning Kamp wrote:
Hi Allan,
Can you please redo the diff -with '-u' ?
Sure, attached.
Poul-Henning
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD
As readers of the cvs commit logs know, Theo has identified the file
in question, and I've removed it from the repo until such time as its
legal status is resolved. If there are futher issues, please feel
free to mail the specific files to core@ and any proof of ownership
(if it wasn't obvious
Hey guys,
shutdown -p now is dependant upon hardware, and am 100% sure my hardware
supports this; yet it still does not work. Must I have anything added to
my kernel configuration or anything?
Regards,
Liam Foy
___
[EMAIL PROTECTED] mailing list
On Wed, 21 Jan 2004, Liam Foy wrote:
shutdown -p now is dependant upon hardware, and am 100% sure my hardware
supports this; yet it still does not work. Must I have anything added to
my kernel configuration or anything?
What version of FreeBSD are you using? Do you have ACPI enabled, if on
For debugging purposes would like to propose the following patch. The
only thing besides from not knowing anything about other architectures
than i386, is that I don't know exactly what happens when compiling with
-fomit-frame-pointer
Could someone tell me ?
Marc
---
Robert Watson wrote:
On Wed, 21 Jan 2004, Liam Foy wrote:
shutdown -p now is dependant upon hardware, and am 100% sure my hardware
supports this; yet it still does not work. Must I have anything added to
my kernel configuration or anything?
What version of FreeBSD are you using? Do you
On Wed, Jan 21, 2004 at 10:13:44PM +0100, Marc Olzheim wrote:
Could someone tell me ?
Erhm... For some clue what this is about:
http://www.mail-archive.com/[EMAIL PROTECTED]/msg44893.html
Marc
___
[EMAIL PROTECTED] mailing list
On Wednesday, 21 January 2004 at 12:35:52 +0100, Josef El-Rayes wrote:
Greg 'groggy' Lehey [EMAIL PROTECTED] wrote:
And to answer another message: yes, Vinum on FreeBSD *must*
be adapted to GEOM. There's no other solution.
shouldn't we add this as a task item to the releng schedule?
That
On Thursday 22 January 2004 08:17, Liam Foy wrote:
I am current running:
FreeBSD liamfoy.ath.cx 4.9-STABLE FreeBSD 4.9-STABLE #5: Sat Dec 13
15:24:43 GMT 2003 [EMAIL PROTECTED]:/usr/src/sys/compile/Ecthelion
i386
Hope this helps...
Try turning APM on (eg apm -e 1) and then shutting
I'm replying to my own message for the sake of list archives.
I just tried the new dhclient (3.0p12), and dynamic DNS works just fine.
Looks like this was a bug that was fixed. The man page has also been
updated and it now works just as documented in the man page.
--
Leo Bicknell -
Hi,
I'm still having trouble limiting bandwidth for emule ports using dummynet
features.
I'm using FreeBSD 5.2-current machine for firewall. It has 2 Intel pro 100
cards and it is configured as a bridge.
I'm doing bandwidth limiting in the following way:
# eMule
${fwcmd} pipe 59 config bw
On Thursday 22 January 2004 14:49, Ganbold wrote:
Am I doing right? For what NIC should I implement filtering, outside or
inside interface?
When I see MRTG graphs for ipfw it still shows bandwidth more than it
supposed to:(
A few points..
- The nic is not really relevant except as a way of
All,
This is a friendly reminder that submissions for the Bi-Monthly status
reports are due on January 24. For those that missed the first
announcement:
It's time for bi-monthly status reports. This one is a little late due
to the excitement of releasing 5.2, so please submit reports for
:Hi,
:
:I'm still having trouble limiting bandwidth for emule ports using dummynet
:features.
:I'm using FreeBSD 5.2-current machine for firewall. It has 2 Intel pro 100
:cards and it is configured as a bridge.
:
:I'm doing bandwidth limiting in the following way:
:
:# eMule
:${fwcmd} pipe 59
Oops... sorry, I gave bad advise. I'm looking at the code. It recognizes
'K' or 'k' so your specification was right. It's the 'b' verses 'B' that
it's sensitive to, so if you say: kbytes/sec it will think it's kbits/sec,
and if you say kBits/sec it will think it's kBytes/sec.
On Thursday 22 January 2004 16:16, Matthew Dillon wrote:
Oops... sorry, I gave bad advise. I'm looking at the code. It
recognizes 'K' or 'k' so your specification was right. It's the 'b' verses
'B' that it's sensitive to, so if you say: kbytes/sec it will think it's
kbits/sec, and if
:
:
:Oops... sorry, I gave bad advise. I'm looking at the code. It recognizes
:'K' or 'k' so your specification was right. It's the 'b' verses 'B' that
:it's sensitive to, so if you say: kbytes/sec it will think it's kbits/sec,
:and if you say kBits/sec it will think it's
30 matches
Mail list logo
