In message <[EMAIL PROTECTED]>, John Hay write
s:
>> Try disabling newreno in both ends:
>>
>> sysctl -w net.inet.tcp.newreno=0
>>
>> On my laptop with Wavelan cards this increases TCP throughput by a
>> factor of 5.
>
>Yes, that makes a HUGE difference. I only did it on the current box.
>
In real life, machines don't always get rebooted in a completely
controlled fashion (panic, power failure, etc.). Anything that
makes a reboot longer or less reliable is a definite non-starter.
I can guarantee you, if the current /dev/random code isn't fixed before
it makes STABLE, folks running
On Wed, Oct 25, 2000 at 09:28:31PM -0700, Doug Barton wrote:
>
> How exactly are you rebooting? If you're using the 'reboot' command,
That is my standard rebooting method. ``reboot'' really has to be
tolerated and something useful happen (ie, the next booting up doesn't
hang (or delay for
* From: Marcel Moolenaar <[EMAIL PROTECTED]>
* The following 2 patches solve the problem when building XFree86-3.3.6
* with only the VGA16 and SVGA servers. Building other servers may still
* be broken.
Yikes. The same problem is killing (at least) all the emacsen too.
http://bento.FreeB
Jordan Hubbard wrote:
>
> > Jordan, what do you think about making the keymap selection the first
> > step of the "Standard" installation?
>
> Most people don't need to set it, and the Standard install is all
> about trying to take the "most general" path. If I'm wildly wrong
> about this anywh
On Wed, Oct 25, 2000 at 05:01:44PM -0700, Mark Murray wrote:
> I need logs.
What logs you expect? It is just standard -current rc.* files.
> What is "did not work"?
The same fortune quote again.
> What is "it worked"?
Different fortune quote.
> What was the line you commented out?
His situa
On Wed, Oct 25, 2000 at 10:35:55AM +, Terry Lambert wrote:
> > I see the opposite. I see that without writing to the /dev/random
> > device I get a cons is an object that cares fortune 99+% of the time
> > on my first login. With it, I see more decently random fortunes (but
> > I haven't don
On Wed, Oct 25, 2000 at 02:50:29PM +0400, Andrej Cernov wrote:
> It is because /dev/random totally ignore _time_ and not reseed from it,
> but no other randomness source available at boot time.
We should probably be using the time since boot as ONE thing we seed
with, but it only provides maybe
On Thu, Oct 26, 2000 at 12:48:19PM +0400, áÎÄÒÅÊ þÅÒÎÏ× wrote:
> On Wed, Oct 25, 2000 at 05:01:44PM -0700, Mark Murray wrote:
> > I need logs.
>
> What logs you expect? It is just standard -current rc.* files.
Here they are, in anycase, set -x as you requested (entropy-related lines
only):
+ [
On Thu, Oct 26, 2000 at 02:21:22AM -0700, Kris Kennaway wrote:
> On Wed, Oct 25, 2000 at 02:50:29PM +0400, Andrej Cernov wrote:
>
> > It is because /dev/random totally ignore _time_ and not reseed from it,
> > but no other randomness source available at boot time.
>
> We should probably be usin
Doug Barton wrote:
>
> Wesley Morgan wrote:
> >
> > I'm not knocking anyone or any code, especially considering this IS
> > -current... BUT... I don't need to read the code to know that I am seeing
> > the same fortunes on first login after reboot more often than I can
> > attribute to random cha
On Wed, Oct 25, 2000 at 07:50:28PM -0400, Wesley Morgan wrote:
> Now, the problem I am seeing is that not only do I get the same fortunes
> between reboots, but it is _always_ the same one:
>
> "Be ALERT (the world needs more lerts"
BTW, my always-the-same fortune is different:
"Adore, v.: To v
On 26 Oct 2000, Satoshi - Ports Wraith - Asami wrote:
> * From: Marcel Moolenaar <[EMAIL PROTECTED]>
>
> * The following 2 patches solve the problem when building XFree86-3.3.6
> * with only the VGA16 and SVGA servers. Building other servers may still
> * be broken.
>
> Yikes. The same pro
> The issue is one of seeding the device strongly. If all you care about
> is getting a different fortune when you boot then seeding with
> e.g. the system boot time would be enough, but obviously it doesnt
> make /dev/random cryptographically secure.
I think there's a more general point being ma
Jordan writes a nice piece of mail...
If this was happening in -stable I'd be in total agreement.
However, we're talking -current, and is not -current the
integration area for new technologies, whether they be
rough or round edged?
This reminds me of the old development arguement:
Don't do
> BTW: I believe PPPoE in both Julian and Archie's cases specifically
> uses the netgraph PPP implementation, so it's an "all in the
> kernel" approach; the problem may be your use of user space code
> (i.e. killable code, since you can't kill it in the kernel, only
> unlink or unload it).
Actual
Hi,
I stumbled over an interesting problem: the current kernel's NFS client
code blocks when reading files of size 2828 byte over NFSv3 (see
kern/22309). Today I tracked the problem down. It appears, that an IP
packet cannot be reassembled, when the last fragment of it is from 1 to 7
bytes long.
Poul-Henning Kamp writes:
> In message <[EMAIL PROTECTED]>, John Hay write
> s:
>
> >> Try disabling newreno in both ends:
> >>
> >> sysctl -w net.inet.tcp.newreno=0
> >>
> >> On my laptop with Wavelan cards this increases TCP throughput by a
> >> factor of 5.
> >
> >Yes, that mak
Hello!
fsck tries to run fsck_msdos for MSDOS partition, but there is no
fsck_msdos in -current.
Also fsck(8) says:
SEE ALSO
mount(8), fstab(5), fsck_msdos(8), fsck_ffs(8)
...
> man fsck_msdos
No manual entry for fsck_msdos
>
Dmitry.
To Unsubscribe: send mail to [EMAIL PROTECTED]
[redirected to freebsd-ipfw]
Certainly, there is a bug.
Please test with attached patch.
On Thu, Oct 26, 2000 at 04:01:07PM +0200, Harti Brandt wrote:
>
> Hi,
>
> I stumbled over an interesting problem: the current kernel's NFS client
> code blocks when reading files of size 2828 byte over NFS
At Thu, 26 Oct 2000 19:23:27 +0400, Dmitry Valdov wrote:
> Hello!
>
> fsck tries to run fsck_msdos for MSDOS partition, but there is no
> fsck_msdos in -current.
>
>
> Also fsck(8) says:
> SEE ALSO
> mount(8), fstab(5), fsck_msdos(8), fsck_ffs(8)
>
> ...
> > man fsck_msdos
> No manual
When trying to install ports, very often I find everything freezes just
after fetch completes. If I hit ^C and type "make install" again, the
tarball is there, that's why I say that fetch is already done.
If I hit ^T, I see fetch sitting in sbwait, the time not increasing.
Any idea?
--
You can h
ln -sf /bin/true /sbin/fsck_msdos
Sorry, today I'm quite exausted... ;-)
> -Original Message-
> From: Dmitry Valdov [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, October 26, 2000 5:23 PM
> To: [EMAIL PROTECTED]
> Subject: fsck in -current
>
>
> Hello!
>
> fsck tries to run fsck_msdos
Patrick Hartling <[EMAIL PROTECTED]> wrote:
} John Baldwin <[EMAIL PROTECTED]> wrote:
}
} }
} } On 25-Oct-00 Chuck Robey wrote:
} } > I'm having rather extreme problems with stability on my dual PIII
} } > setup. I know this is to be expected, but it's gotten so extreme on my
} } > system, I c
:In real life, machines don't always get rebooted in a completely
:controlled fashion (panic, power failure, etc.). Anything that
:makes a reboot longer or less reliable is a definite non-starter.
:
:I can guarantee you, if the current /dev/random code isn't fixed before
:it makes STABLE, folks r
Sorry to follow up on myself... I forgot to mention this is -CURRENT,
updated to a couple of days ago...
> -Original Message-
> From: Andrea Campi
> Sent: Thursday, October 26, 2000 6:44 PM
> To: '[EMAIL PROTECTED]'
> Subject: Problem in fetch
>
>
> When trying to install ports, very o
> > What logs you expect? It is just standard -current rc.* files.
>
> Here they are, in anycase, set -x as you requested (entropy-related lines
> only):
>
> + [ -w /dev/random ]
> + [ -f /var/db/entropy -a -r /var/db/entropy -a -s /var/db/entropy ]
> + echo Using /var/db/entropy as an entropy f
> > What logs you expect? It is just standard -current rc.* files.
>
> Here they are, in anycase, set -x as you requested (entropy-related lines
> only):
>
> + [ -w /dev/random ]
> + [ -f /var/db/entropy -a -r /var/db/entropy -a -s /var/db/entropy ]
> + echo Using /var/db/entropy as an entropy f
Satoshi - Ports Wraith - Asami wrote:
>
> * From: Marcel Moolenaar <[EMAIL PROTECTED]>
>
> * The following 2 patches solve the problem when building XFree86-3.3.6
> * with only the VGA16 and SVGA servers. Building other servers may still
> * be broken.
>
> Yikes. The same problem is killin
Please, please commit this.
At Wed, 25 Oct 2000 01:31:57 +0900,
Motomichi Matsuzaki <[EMAIL PROTECTED]> wrote:
> patch for revision 1.20:
>
> --- /etc/pccard_ether Thu Oct 19 16:24:35 2000
> +++ pccard_ether Wed Oct 25 01:27:05 2000
> @@ -46,7 +46,7 @@
>
> interface=$1
> shift
> -start
On 26-Oct-00 Rod Taylor wrote:
> Doug Barton wrote:
>>
>> Wesley Morgan wrote:
>> >
>> > I'm not knocking anyone or any code, especially considering this IS
>> > -current... BUT... I don't need to read the code to know that I am seeing
>> > the same fortunes on first login after reboot more ofte
check outed 1 hour ago.
===> ipfilter
cc -O -pipe -DIPFILTER=1 -DIPFILTER_LKM -DIPFILTER_LOG -D_KERNEL -Wall
-Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes
-Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -DKLD_MODULE -nostdinc
-I- -I. -I@ -I@/../i
On Thu, Oct 26, 2000 at 09:56:00AM -0700, Matt Dillon wrote:
> simple: don't try to save the random seed from the shutdown script. I
> would argue that the very *LAST* thing you want to do when shutting a
> machine down is start writing out files. And, frankly, depending on
I agree
On Tue, Oct 24, 2000 at 02:56:07PM -0700, Jordan Hubbard wrote:
> [redirected to just -current; I'm not sure what this has to do with -net]
>
> > I agree. I've been using them for a while on my dog slow Windows CE
> > machine. There were some minor issues when they were first committed
> > to N
> > BTW: I believe PPPoE in both Julian and Archie's cases specifically
> > uses the netgraph PPP implementation, so it's an "all in the
> > kernel" approach; the problem may be your use of user space code
> > (i.e. killable code, since you can't kill it in the kernel, only
> > unlink or unload it
In message <[EMAIL PROTECTED]> Nik Clayton writes:
: On Tue, Oct 24, 2000 at 02:56:07PM -0700, Jordan Hubbard wrote:
: > [redirected to just -current; I'm not sure what this has to do with -net]
: >
: > > I agree. I've been using them for a while on my dog slow Windows CE
: > > machine. There w
> > It is because /dev/random totally ignore _time_ and not reseed from it,
> > but no other randomness source available at boot time.
>
> We should probably be using the time since boot as ONE thing we seed
> with, but it only provides maybe 3-4 bits of randomness - meaning if
> thats all you s
On Wed, Oct 25, 2000 at 15:17 -0500, Mike Meyer wrote:
> Gerhard Sittig writes:
> > What's new is:
> > - include the general config at the start (and yes, in every
> > single script -- but this should be neglectable in terms of
> > speed penalty and makes them work separately, too -- which is
> The actual time would probably be more useful than the time since
> boot.
Heck - I can use both. Its cheap enough.
> I still have a problem with what I see as a fundamental weakness
> in storing "randomness" across reboots.
Schneier recommends this in his Yarrow paper.
> Logically, given a s
On Thu, 26 Oct 2000, John Baldwin wrote:
> > How about when I hit the reset button? That case SHOULD be taken care
> > of too! Would it not be possible to sample /dev/random to store the
> > entropy every hour or so that the system runs? Atleast that way you
> > would be guarenteed to have som
[Making sure Dag-Erling gets the mail]
-On [20001026 18:45], Andrea Campi ([EMAIL PROTECTED]) wrote:
>When trying to install ports, very often I find everything freezes just
>after fetch completes. If I hit ^C and type "make install" again, the
>tarball is there, that's
$B$O$8$a$^$7$F!#(B$BFMA3$N%a!=%k!"<:NiCW$7$^$9!#(B
$B;d$N%a!<%k%\%C%/%9$K!"#1#0%v7n0LA0$+$i(B$B!V#4#0#0#01_$r?6$j9~$`$H!"<+J,$N8}:B$K!"$*6b$,?6$j9~$^$l$k$h$&$K$J$k!W(B$B$H$$$C$?35N,$N%M%C%H%2!<%`$NM6$$$,FO$/$h$&$K$J$C$FMh$^$7$?!#(B
$B$3$N$h$&$J%a!<%k$K$O6=L#$,L5$+$C$?$N$G!"Ev=i$OL
On Thu, Oct 26, 2000 at 09:25:05AM -0400, John W. De Boskey wrote:
> If this was happening in -stable I'd be in total agreement.
> However, we're talking -current, and is not -current the
> integration area for new technologies, whether they be
> rough or round edged?
Yes, -CURRENT is for new tec
I built a 4.1.1 kernel, and the module was built, but when I load the ipfw
module with
#kldload ipfw
it defaults to a deny_all policy, even though I have default_to_accept in my
kernel configuration.
This makes it difficult to configure remotely without getting locked out of the
system.
Is t
> I stated this same objection until I actually attended Mark's
> presentation at the 'con. The yarrow algorithm uses an encrypted hash for
> the entropy on the way in, and encrypts the output on the way out. This
> would make it extremely difficult to guess the state at reboot, even if we
>
On Thu, Oct 26, 2000 at 01:31:03PM -0700, Glen Gross wrote:
>
> I built a 4.1.1 kernel, and the module was built, but when I load the ipfw
> module with
>
> #kldload ipfw
>
> it defaults to a deny_all policy, even though I have default_to_accept in my
> kernel configuration.
> This makes it d
Thanks, I suppose I should have been able to figure that one out... if I could
log in! I will fix it when I get home. :-)
On Thursday, October 26, 2000 1:32 PM, Bill Fumerola [SMTP:[EMAIL PROTECTED]]
wrote:
> On Thu, Oct 26, 2000 at 01:31:03PM -0700, Glen Gross wrote:
> >
> > I built a 4.1.1
First of all (using -current of 26 October) I was not able to attach pcm to
my Yamaha OPL-SAx soundcard in my Toshiba Tecra8000 when using snd_pcm.ko.
Using a statically compiled driver though I had no trouble whatsoever. The
module was pre-loaded at boot time.
2nd with a working pcm driver I
On Thu, Oct 26, 2000 at 01:36:40PM -0700, Glen Gross wrote:
> Thanks, I suppose I should have been able to figure that one out... if I could
> log in! I will fix it when I get home. :-)
Playing with firewalls without out-of-band (serial console, nocmonkey, etc) is
dangerous.
--
Bill Fumerol
Does this look like english to anyone and is my mailer messed, or is this
gobbledegook to anyone not using Outlook + japanese character set?
DocWilco
At 05:12 27-10-00 +0900, you wrote:
>$B$O$8$a$^$7$F!#(B
>$BFMA3$N%a!=%k!"<:NiCW$7$^$9!#(B
>
>$B;d$N%a!<%k%\%C%/%9$K!"#1#0%v7n0LA0$+$i(B
subscribe
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
>This makes it difficult to configure remotely without getting locked out
>of the
>system.
>Is there a way to cause the ipfw module to default to a different policy upon
>loading?
I'm not sure about influencing modules with options in kernel config, I'll
leave that to the pro's but you could a
Doug Barton wrote:
: Pending Mark's approval, I'd like to suggest we add a cron job to
: dump X k of data from /dev/random to a file (/boot/.periodic_entropy
: maybe?) and use that, AND ${entropy_file:/var/db/entropy} to reseed at
: boot, and only do the "long, annoying" failover process if
:I like that, but I'd like to see more than one file. This avoids the race
:where fsck may blat an incompletely written file after a (in)convenient
:crash.
:
:We are really headed towards saving state in the first swap partition
:(if there is one).
:M
:--
:Mark Murray
:Join the anti-SPAM movement
Doug Barton wrote:
: Pending Mark's approval, I'd like to suggest we add a cron job to
: dump X k of data from /dev/random to a file (/boot/.periodic_entropy
: maybe?) and use that, AND ${entropy_file:/var/db/entropy} to reseed at
: boot, and only do the "long, annoying" failover process if
> This would be trivial, you can use the swap allocation code (example:
> see the VN device, dev/vn/vn.c) to reserve, read, and write the swap.
Thanks! :-)
> However, I don't see much of a point in doing this. Not everyone
> configures swap, so you can't count on it, and a syste
:> This would be trivial, you can use the swap allocation code (example:
:> see the VN device, dev/vn/vn.c) to reserve, read, and write the swap.
:
:Thanks! :-)
:
:> However, I don't see much of a point in doing this. Not everyone
:> configures swap, so you can't count on it, and
in the bus_alloc_resource() man page it states:
dev is the device that requests ownership of the resource. Before
allo-
cation, the device is owned by the parent bus.
should that be:
"Before allocation, the resource is owned by the parent bus." ?
(It doesn't make sense t me as it is
On Thu, 26 Oct 2000, Ed Hall wrote:
> How about skipping the "long, annoying failover process" altogether and
> simply logging to the console that the entropy reseeding process was
> incomplete? Forcing an indeterminate delay to gather entropy is more
> than a little paternalistic.
The
> First of all (using -current of 26 October) I was not able to attach pcm
to
> my Yamaha OPL-SAx soundcard in my Toshiba Tecra8000 when using snd_pcm.ko.
> Using a statically compiled driver though I had no trouble whatsoever. The
> module was pre-loaded at boot time.
snd_pcm is the core module,
In message <[EMAIL PROTECTED]>, Doug
Barton writes:
>On Thu, 26 Oct 2000, Ed Hall wrote:
>
>> How about skipping the "long, annoying failover process" altogether and
>> simply logging to the console that the entropy reseeding process was
>> incomplete? Forcing an indeterminate delay to gather en
On Thu, Oct 26, 2000 at 04:31:57PM -0400, Bill Fumerola wrote:
> #If you want it verbose
> #CFLAGS+= -DIPFIREWALL_VERBOSE
> #CFLAGS+= -DIPFIREWALL_VERBOSE_LIMIT=100
> #
> #If you want it to pass all packets by default
> #CFLAGS+= -DIPFIREWALL_DEFAULT_TO_ACCEPT
So one doesn't have to change the so
On Thu, 26 Oct 2000, Poul-Henning Kamp wrote:
> I don't really care that much how good my random bits are right after
> boot, but I do care about my machine coming up quickly.
I don't know about that, look at your boot logs:
Oct 26 17:32:19 catalyst /boot/kernel/kernel: Copyright (c) 1992-2000
On Thu, Oct 26, 2000 at 02:25:58PM -0700, Matt Dillon wrote:
> /etc/rc already assumes that /var is writable. I recommend that you make
> that assumption by default... have the default entropy file be something
> like "/var/db/entropy_seed" and allow the administrator to override it
>
In message <[EMAIL PROTECTED]
om>, Wesley Morgan writes:
>On Thu, 26 Oct 2000, Poul-Henning Kamp wrote:
>
>> I don't really care that much how good my random bits are right after
>> boot, but I do care about my machine coming up quickly.
>
>I don't know about that, look at your boot logs:
>
>Oct 2
On 26-Oct-00 David O'Brien wrote:
> On Thu, Oct 26, 2000 at 04:31:57PM -0400, Bill Fumerola wrote:
>> #If you want it verbose
>> #CFLAGS+= -DIPFIREWALL_VERBOSE
>> #CFLAGS+= -DIPFIREWALL_VERBOSE_LIMIT=100
>> #
>> #If you want it to pass all packets by default
>> #CFLAGS+= -DIPFIREWALL_DEFAULT_TO_A
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Thu, Oct 26, 2000 at 03:18:55PM -0700, John Baldwin wrote:
> Ugh, no. Peter's forthcoming config(8) changes will allow you to
> specify kernel options to use when building modules (actually, it
> builds modules in the same environment as the kernel) to properly
> handle this. Just be patient
hmmm... I just got a message from chris, he said he will be adding
AES/Rijndael to the kernel ASAP...
According to the Rijndael spec, it seems to also function as an
excellant pseudo-random number generator...
You can find this info at:
http://www.esat.kuleuven.ac.be/~rijmen/rijndael
Section
On 26-Oct-00 David O'Brien wrote:
> On Thu, Oct 26, 2000 at 03:18:55PM -0700, John Baldwin wrote:
>> Ugh, no. Peter's forthcoming config(8) changes will allow you to
>> specify kernel options to use when building modules (actually, it
>> builds modules in the same environment as the kernel) to p
Hi
Very wonderful ideas! It will take me a bit of time to implement this
cleanly as I am not close enough to my Prime Development Platform, but
I will do something as soon as possible. Consider it to be not less
than two weeks, unless someone submits patches first.
:-)
M
> :There is the proble
On Thu, Oct 26, 2000 at 10:43:44PM +0200, Rogier R. Mulhuijzen wrote:
> Oh, just out of curiosity, I build both my kernel and world with
> -mcpu=pentiumpro and -march=pentiumpro. Would there be any reasons not to?
Anything above -O -pipe is not offically supported. While you didn't
give your op
< said:
> Eventually yes, but not this way. According to Bruce sys/types is a
> prerequisite for sys/wait.
This is currently true, but should be fixed this year (probably not
this month -- it depends on how much energy I have).
Draft 4 (draft 5 isn't out yet) of POSIX.1-200x says the following
> I disagree. Vaporware (example Son of Sysinstall) has kept us from
> improving things until the fabled newstuff arrives.
That's actually a bad example since just a brief glance at the cvs
commit logs for sysinstall will show that a number of fingers have
dived into it over the years and "impro
At 26 Oct 2000 20:37:48 GMT,
Rogier R. Mulhuijzen <[EMAIL PROTECTED]> wrote:
> Does this look like english to anyone and is my mailer messed, or is this
> gobbledegook to anyone not using Outlook + japanese character set?
That is spam like a "get money fast!" written in Japanese. That is
not re
David O'Brien wrote:
>
> On Thu, Oct 26, 2000 at 02:25:58PM -0700, Matt Dillon wrote:
> > /etc/rc already assumes that /var is writable. I recommend that you make
> > that assumption by default... have the default entropy file be something
> > like "/var/db/entropy_seed" and allow th
It use to work in early October, but now I get the following using
the stock (/etc/defaults/rc.conf) amd flags:
amd[321]: /host: mount: Operation not supported by device
amd[322]: /net: mount: Operation not supported by device
amd[321]: /host: mount: No such file or directory
amd[322]: /net: moun
On Thu, Oct 26, 2000 at 08:47:35PM -0700, Jordan Hubbard wrote:
>
> G. Hot button. :)
Quite sorry, didn't mean to push any buttons. But once again I just got
hit by having a anchient /stand/sysinstall not be able to find any
devices when I wanted to use it's Fdisk editor. Way back when I w
On Thu, Oct 26, 2000 at 09:04:45PM -0700, Jordan Hubbard wrote:
> It use to work in early October, but now I get the following using
> the stock (/etc/defaults/rc.conf) amd flags:
It works on my Oct 22nd world.
-- David ([EMAIL PROTECTED])
To Unsubscribe: send mail to [EMAIL PROTECTED]
with
On Thu, Oct 26, 2000 at 03:10:35PM -0700, David O'Brien wrote:
> So one doesn't have to change the source, would you be willing to add
> WANT_foo logic so one could just set it in /etc/make.conf? Or add
> ${IPFIREWALL_OPTS} to CFLAGS and then IPFIREWALL_OPTS could be set in
> /etc/make.conf?
Ha
-On [20001026 23:30], Julian Elischer ([EMAIL PROTECTED]) wrote:
>in the bus_alloc_resource() man page it states:
>
>
> dev is the device that requests ownership of the resource. Before
>allo-
> cation, the device is owned by the parent bus.
>
>should that be:
81 matches
Mail list logo
