In message p05200f51ba651eaf1dd8@[128.113.24.47], Garance A Drosihn writes:
So, I'm trying something on -current.
I boot up, log into root. I have two hard disks on the system. All
of my mounted partitions are on ad0, except for one partition on ad2.
I 'umount' that partition. I run the
On 31-Jan-2003 David Rhodus wrote:
| Using the default ftpd that comes with FreeBSD, in the mkdir command,
| why doesn't it expand '~', the cd and rmdir commands seem to. Passing
| over the code it just calls the c function with should expand it.
No, the system calls don't expand a tilde. The
At 7:50 PM -0500 1/29/03, Garance A Drosihn wrote:
At 9:49 PM -0500 1/28/03, Garance A Drosihn wrote:
Hmm, well, I finally got my first actual system panic which wasn't
obviously caused by my own screwing around. On the console I have:
free inode /usr/cvs/net/64 had 0 blocks
panic:
On Mon, 3 Feb 2003, Robert Watson wrote:
The strategy for selecting a credential to check against is generally to
use td_ucred, and to hold no locks. You'll see that suser() does this,
for example. Under some circumstances: specifically, credential updates,
you need to hold the process
Hello,
The sense of the -P option was changed, and it makes it so you have to
do extra work to get the console driver to do the right thing from
inside FreeBSD proper, on a machine that could have its keyboard removed
(or not). It's because the -h is implied, and it's a toggle.
Oh, I see
On Mon, Feb 03, 2003 at 21:40:20 -0800, David Schultz wrote:
followed by a 5 or 6. There is a similar pattern for 'e a 7'. I
think this pretty much demonstrates that the algorithm isn't good
enough to generate high-quality randomness with respect to
different seed values. I'm not
On Tue, Feb 04, 2003 at 12:46:59 +0300, Andrey A. Chernov wrote:
Returning to current algorithm, I am interested in good NSHUFF value in
the range 100-2000. Do you have any findings there?
Apparently 100 is not enough too, I see repeated pattern in your
program. I'll try other values...
--
On Tue, Feb 04, 2003 at 12:46:59 +0300, Andrey A. Chernov wrote:
So, if you define USE_WEAK_SEEDING and re-compile rand.c, you'll get even
worse results from your test. It means current variant is better then
previous. If you know even better algorithm wich pass restrictions above,
just tell
On Tue, Feb 04, 2003 at 12:58:40 +0300, Andrey A. Chernov wrote:
On Tue, Feb 04, 2003 at 12:46:59 +0300, Andrey A. Chernov wrote:
Returning to current algorithm, I am interested in good NSHUFF value in
the range 100-2000. Do you have any findings there?
Apparently 100 is not enough
Thus spake Andrey A. Chernov [EMAIL PROTECTED]:
On Mon, Feb 03, 2003 at 21:40:20 -0800, David Schultz wrote:
I don't try to make rand() good for high-quality pseudo-randomness,
because it can be done by price of speed and, more important, big state
size. Due to rand_r() restriction state size
On Tue, Feb 04, 2003 at 03:52:37 -0800, David Schultz wrote:
You can do better than the present generator with 32 bits of state.
See the following page by Neal Wagner (not to be confused with David Wagner):
http://www.cs.utsa.edu/~wagner/laws/rng.html
The section on LCGs suggests that
--
Rebuilding the temporary build tree
--
stage 1: bootstrap tools
--
stage 2: cleaning up the object tree
On Mon, 3 Feb 2003 18:59:46 +0100
Alexander Leidinger [EMAIL PROTECTED] wrote:
I tried a buildworld yesterday and today, and I got:
---snip---
gcc -I/big/usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/config -DHAVE_C
ONFIG_H -DTARGET_NAME=\i386-undermydesk-freebsd\ -DIN_GCC -c
On Tue, Feb 04, 2003 at 15:07:30 +0300, Andrey A. Chernov wrote:
On Tue, Feb 04, 2003 at 03:52:37 -0800, David Schultz wrote:
You can do better than the present generator with 32 bits of state.
See the following page by Neal Wagner (not to be confused with David Wagner):
On Tue, 4 Feb 2003, Ilmar S. Habibulin wrote:
On Mon, 3 Feb 2003, Robert Watson wrote:
The strategy for selecting a credential to check against is generally to
use td_ucred, and to hold no locks. You'll see that suser() does this,
for example. Under some circumstances: specifically,
David Schultz [EMAIL PROTECTED] writes:
You can do better than the present generator with 32 bits of state.
See the following page by Neal Wagner (not to be confused with David Wagner):
http://www.cs.utsa.edu/~wagner/laws/rng.html
The attached patch, based on one of the m/k pairs
On Tue, Feb 04, 2003 at 14:00:27 +0100, Dag-Erling Smorgrav wrote:
David Schultz [EMAIL PROTECTED] writes:
You can do better than the present generator with 32 bits of state.
See the following page by Neal Wagner (not to be confused with David Wagner):
On Tue, Feb 04, 2003 at 16:10:06 +0300, Andrey A. Chernov wrote:
On Tue, Feb 04, 2003 at 14:00:27 +0100, Dag-Erling Smorgrav wrote:
David Schultz [EMAIL PROTECTED] writes:
You can do better than the present generator with 32 bits of state.
See the following page by Neal Wagner (not to be
On Tue, Feb 04, 2003 at 16:17:48 +0300, Andrey A. Chernov wrote:
On Tue, Feb 04, 2003 at 16:10:06 +0300, Andrey A. Chernov wrote:
On Tue, Feb 04, 2003 at 14:00:27 +0100, Dag-Erling Smorgrav wrote:
David Schultz [EMAIL PROTECTED] writes:
You can do better than the present generator with
Andrey A. Chernov [EMAIL PROTECTED] writes:
There is one bug in your patch: 0 is still illegal, so my fix required.
I believe that's a feature. All linear congruence generator have a
fixed point. 0 is a far better fixed point than any other because it
is more obviously unsuited (for some
On Tue, Feb 04, 2003 at 16:28:45 +0300, Andrey A. Chernov wrote:
I'll produce working variant based on your patch...
When all done correctly, there is repeated pattern still, so some NSHUFF
drop required too:
1 7 e 4 a 0 7 d 3 a 0 6
See attached patch based on -current sources.
--
Andrey
Andrey A. Chernov [EMAIL PROTECTED] writes:
And the next bug is 32bit overflow there:
tmp = *ctx * 62089911;
Ack, I thought the type promotion was automatic. Updated patch is
attached.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
Index: lib/libc/stdlib/rand.c
On Tue, Feb 04, 2003 at 14:43:57 +0100, Dag-Erling Smorgrav wrote:
I believe that's a feature. All linear congruence generator have a
fixed point. 0 is a far better fixed point than any other because it
is more obviously unsuited (for some values of obviously) as a
seed value. (but see
On Tue, Feb 04, 2003 at 16:47:14 +0300, Andrey A. Chernov wrote:
On Tue, Feb 04, 2003 at 16:28:45 +0300, Andrey A. Chernov wrote:
I'll produce working variant based on your patch...
When all done correctly, there is repeated pattern still, so some NSHUFF
drop required too:
1 7 e 4 a
Andrey A. Chernov [EMAIL PROTECTED] writes:
With NSHUFF 100 situation not changed much, so I beleive that stated
problem is common for this type PRNGs, so we gains nothing changing
formulae to Knuth-recommended values.
Yes we do. We get a better sequence for any given seed, i.e. we get
less
Andrey A. Chernov [EMAIL PROTECTED] writes:
On Tue, Feb 04, 2003 at 14:43:57 +0100, Dag-Erling Smorgrav wrote:
All that being said, adding 1 to *ctx before returning it (see patch)
adresses both of your objections: a seed of 0 will not cause the LCG
to get stuck, and the result of rand()
On Tue, Feb 04, 2003 at 15:23:28 +0100, Dag-Erling Smorgrav wrote:
Andrey A. Chernov [EMAIL PROTECTED] writes:
On Tue, Feb 04, 2003 at 14:43:57 +0100, Dag-Erling Smorgrav wrote:
All that being said, adding 1 to *ctx before returning it (see patch)
adresses both of your objections: a seed
Hi,
I am a software developer who has benefitted greatly from using FreeBSD the past few
years as well as other software like KDE. I have been doing what I can here and there
to make sure big projects like KDE will build and run on FreeBSD as well as other
operating systems.
I came to the
[Please wrap lines at 72 characters or less.]
David Leimbach [EMAIL PROTECTED] writes:
Hi,
I am a software developer who has benefitted greatly from using FreeBSD the past few
years as well as other software like KDE. I have been doing what I can here and
there to make sure big projects
See http://www.freebsd.org/projects/c99/
Wes Peters has been assigned this task for a while. Perhaps you could
co-ordinate with him.
Yes and no offense to him... I am sure he is busy. Its not done yet :)
I will contact him and see if I can lend a hand in any way.
Thanks for the
On Fri, 31 Jan 2003, Pascal Giannakakis wrote:
today i updated sources with CVS, compiled world and kernel, then
rebooted. During boot it hangs at the boot message (the place where in
FreeBSD 4.7 a lot of boot info would appear, like ata, cpu, usb0 blah blah).
- The keyboard num-lock does
The first (confirmed to work) cross-release!
Finally, I've been able to build an i386 snapshot on Alpha,
and make sure it works!
This is the uname -a output from the Alpha box which was
used to build the snapshot, root access kindly provided by
Wilko Bulte:
: FreeBSD ds10.wbnet 5.0-CURRENT
There's still one issue to be resolved for i386 on alpha
cross-releases: btxld(8) produces a binary image different
from when it's run natively
This might be related to the failure I've seen trying to cross-compile
i386 world on sparc64. btxldr dies with 'short read' error there.
Alexander,
On Tue, Feb 04, 2003 at 11:46:06AM -0500, Alexander Kabaev wrote:
There's still one issue to be resolved for i386 on alpha
cross-releases: btxld(8) produces a binary image different
from when it's run natively
This might be related to the failure I've seen trying to cross-compile
i386
On Tue, Feb 04, 2003 at 15:22:03 +0100, Dag-Erling Smorgrav wrote:
Yes we do. We get a better sequence for any given seed, i.e. we get
less correlation between n and x(n) for any given x(0). I don't think
it changes much for long sequences, but we get a better distribution
for short
On Tue, Feb 04, 2003 at 17:36:04 +0300, Andrey A. Chernov wrote:
with a != 0 values are monotonically increased, I try with
a == 123459876
With your a == 62089911 (i.e. +1) the same:
0: 62089911
1: 124179822
2: 186269733
3: 248359644
4: 310449555
5: 372539466
6: 434629377
7: 496719288
8:
On Tue, Feb 04, 2003 at 03:05:31AM -0500, Mike Heffner wrote:
On 31-Jan-2003 David Rhodus wrote:
| Using the default ftpd that comes with FreeBSD, in the mkdir command,
| why doesn't it expand '~', the cd and rmdir commands seem to. Passing
| over the code it just calls the c function with
On 04-Feb-2003 Yar Tikhiy wrote:
| On Tue, Feb 04, 2003 at 03:05:31AM -0500, Mike Heffner wrote:
|
| On 31-Jan-2003 David Rhodus wrote:
| | Using the default ftpd that comes with FreeBSD, in the mkdir command,
| | why doesn't it expand '~', the cd and rmdir commands seem to. Passing
| | over the
I'm trying to create a raid set but after hitting the end of
initializing a raid5
stripe the following is displayed on the console:
raid0: node (Rod) returned fail, rolling backward
raid0: IO Error. Marking /dev/da2s1e as failed.
raid0: node (Rod) returned fail, rolling backward
raid0: IO
I have just scratch installed 5.0 from CD. (By scratch install
I mean I told it to delete and recreate all partitions except
/users, so none of my old OS configurations should have been
preseved.)
When I installed 5.0 X11 worked. After turning off ACPI the built-in
trackpoint mouse started
On Tue, Feb 04, 2003 at 06:35:40PM +0200, Ruslan Ermilov wrote:
The first (confirmed to work) cross-release!
Finally, I've been able to build an i386 snapshot on Alpha,
and make sure it works!
[...]
There's still one issue to be resolved for i386 on alpha
cross-releases: btxld(8) produces
Andre Guibert de Bruet schrieb:
On Fri, 31 Jan 2003, Pascal Giannakakis wrote:
today i updated sources with CVS, compiled world and kernel, then
rebooted. During boot it hangs at the boot message (the place where in
FreeBSD 4.7 a lot of boot info would appear, like ata, cpu, usb0 blah blah).
On Tue, Feb 04, 2003 at 10:58:04AM -0800, Lee Damon wrote:
(II) ATI: Candidate Device section Card0.
(--) Chipset ATI Radeon Mobility LW (AGP) found
There are known problems with the ATI Radeon Mobility
driver. I had to compile X11 from the cvs repository
at www.xfree86.org to get my labtop
I've stumbled across a Satellite 1605CDS that I'm trying to beat into shape.
ACPI fails as follows:
acpi0: PTLTDRSDT on motherboard
ACPI-0483: *** Error: GPE0 block (GPE 0 to 15) overlaps the GPE1 block
(GPE 0 to 15)
acpi0: could not enable ACPI: AE_BAD_VALUE
device_probe_and_attach:
On Tue, Feb 04, 2003 at 11:38:09AM -0800, Steve Kargl wrote:
On Tue, Feb 04, 2003 at 10:58:04AM -0800, Lee Damon wrote:
(II) ATI: Candidate Device section Card0.
(--) Chipset ATI Radeon Mobility LW (AGP) found
There are known problems with the ATI Radeon Mobility
driver. I had to
On Tue, Feb 04, 2003 at 10:40:09PM +0100, Flag_reda wrote:
On Tue, Feb 04, 2003 at 11:38:09AM -0800, Steve Kargl wrote:
On Tue, Feb 04, 2003 at 10:58:04AM -0800, Lee Damon wrote:
(II) ATI: Candidate Device section Card0.
(--) Chipset ATI Radeon Mobility LW (AGP) found
There are
On Tue, Feb 04, 2003 at 10:40:09PM +0100, Flag_reda wrote:
On Tue, Feb 04, 2003 at 11:38:09AM -0800, Steve Kargl wrote:
On Tue, Feb 04, 2003 at 10:58:04AM -0800, Lee Damon wrote:
(II) ATI: Candidate Device section Card0.
(--) Chipset ATI Radeon Mobility LW (AGP) found
There are
I have created a patch which contains a preview of the statistics
code I intend to add to GEOM, and would invite people to play with
it and give me some feedback:
http://phk.freebsd.dk/patch/geom_iostat.patch
Here is a small shell-script to watch the output with:
On Wed, Feb 05, 2003 at 12:41:46AM +0300, Sergey A. Osokin wrote:
Tell more about your Radeon, because I use -CURRENT with APM
(not ACPI - it crash my note at boottime),
ATI Radeon LY Mobility 6 (AGP), XFree86-4.2.1 (from ports)
without of any problems.
it's not the radeon, it's the agp
Cliff L. Biffle [EMAIL PROTECTED] wrote:
I sort of expected ACPI to fail after watching everyone else, but the killer
here is that APM doesn't seem to work either once ACPI is disabled. Its
error messages are less interesting. When compiled into the kernel, there
are no error messages,
I noticed a growing queue of undelivered messages today and after some digging
I found out that maildrop, which I use as a local delivery agent for sendmail
in order to deliver to Maildirs, would fail on some messages bigger than its
message-buffer with Unable to create temporary file..
I
On Tuesday 04 February 2003 23:34, David Wolfskill wrote:
I haven't seen that particular issue, but there was a time in -CURRENT
when my make -j8 buildworld runs were failing: I was using an md
device for /tmp, and it was running out of inodes.
I had not thought of that, but /tmp is just a
At 9:04 AM +0100 2/4/03, [EMAIL PROTECTED] wrote:
Garance A Drosihn writes:
I drop out of sysinstall, do some things with that partition, and
then decide to redo the above sequence. Everything has been working
fine, but I'm just testing some things and I end up in a position
where it's
At 10:44 PM +0100 2003/02/04, Poul-Henning Kamp wrote:
In difference from the devstat framework which measures how big a
percentage of the time a drive has one or more outstanding requests,
I think that measuring the responstime is a much more useful metric.
(comments, input, references
At 4:58 PM -0600 2003/02/04, Dan Nelson wrote:
I pressume we also want to collect number of bytes transferred, and
I will add that in the next iteration.
Definitely. What I'd like is enough statistics to be able to duplicate
Solaris' iostat -x output:
You know, that is *precisely* what
In message a05200f08ba65f714a4e9@[146.106.12.76], Brad Knowles writes:
At 10:44 PM +0100 2003/02/04, Poul-Henning Kamp wrote:
In difference from the devstat framework which measures how big a
percentage of the time a drive has one or more outstanding requests,
I think that measuring the
--
Rebuilding the temporary build tree
--
stage 1: bootstrap tools
--
stage 2: cleaning up the object tree
At 1:07 AM +0100 2003/02/05, [EMAIL PROTECTED] wrote:
I don't have a queue-depth as such, but I have number of transactions
in transit. Will a snapshot of that at the time of the read do
what you want ? I am too sleepy to know if that will allow you to
calculate the average number of
In the last episode (Feb 04), Poul-Henning Kamp said:
Collecting number of operations and number of errors is a nobrainer.
The timestamps cost something to make, and my plan was to only
collect them while a monitoring program is running. (Is this a good
idea ?)
In difference from the
On Tue, 4 Feb 2003, Poul-Henning Kamp wrote:
Now, discussion time:
The timestamps cost something to make, and my plan was to only collect
them while a monitoring program is running. (Is this a good idea ?)
probably it is a good idea though it does lead to the possibility of a
On Wednesday, 5 February 2003 at 1:07:47 +0100, Poul-Henning Kamp wrote:
In message a05200f08ba65f714a4e9@[146.106.12.76], Brad Knowles writes:
At 10:44 PM +0100 2003/02/04, Poul-Henning Kamp wrote:
In difference from the devstat framework which measures how big a
percentage of the time a
[redirected to -current]
On Tuesday, 4 February 2003 at 17:55:42 -0800, [EMAIL PROTECTED] wrote:
with last hour, cvsup current, rebuild everything,... immediately
after kernel mount msg for /
kernel cranks out msg
Be nice to each other, mmmkay?
system otherwise fine. Is this a known
On Tuesday, February 4, 2003, at 09:01 PM, Greg 'groggy' Lehey wrote:
with last hour, cvsup current, rebuild everything,... immediately
after kernel mount msg for /
kernel cranks out msg
Be nice to each other, mmmkay?
system otherwise fine. Is this a known prank?
It is now. It's in
I have improved recovery code after timeout in -current.
Could you try that?
/\ Hidetoshi Shimokawa
\/ [EMAIL PROTECTED]
PGP public key: http://www.sat.t.u-tokyo.ac.jp/~simokawa/pgp.html
At Sun, 2 Feb 2003 13:28:33 +0200,
mike wrote:
[1 text/plain; iso-8859-1 (7bit)]
On Thu, 30 Jan 2003
On 4 Feb, Muhannad Asfour wrote:
Hello. I've recently faced a rather odd issue that I've never seen
before. I bought a new server (specs below), and I loaded it up with
FreeBSD 5.0-RELEASE (I know, I know, not for a production environment,
but this is a personal server). Now, whenever I
Hello. I've recently faced a rather odd issue that I've never seen
before. I bought a new server (specs below), and I loaded it up with
FreeBSD 5.0-RELEASE (I know, I know, not for a production environment,
but this is a personal server). Now, whenever I get about 30
simultaneous connections,
On Tue, 2003-02-04 at 22:32, [EMAIL PROTECTED] wrote:
On 4 Feb, Muhannad Asfour wrote:
Hello. I've recently faced a rather odd issue that I've never seen
before. I bought a new server (specs below), and I loaded it up with
FreeBSD 5.0-RELEASE (I know, I know, not for a production
On Tue, 2003-02-04 at 22:49, Laszlo Vagner wrote:
Muhannad Asfour wrote:
Hello. I've recently faced a rather odd issue that I've never seen
before. I bought a new server (specs below), and I loaded it up with
FreeBSD 5.0-RELEASE (I know, I know, not for a production environment,
but this
I have a Toshiba Satellite 1805-S207 laptop. When I boot the generic 5.0-R
kernel from a fresh install (fresh as in initial reboot), it will show the
device lines for agp0 then hang indefinitely, requiring that I turn off the
machine via the power button. This is a repeating event, and occurs
I just booted a kernel with SCHED_ULE. It looks like there's a pretty
serious bug:
PID USERNAME PRI NICE SIZERES STATETIME WCPUCPU COMMAND
573 dnetc139 20 1000K 804K RUN 1:29 85.94% 85.94% dnetc
661 kris 960 2252K 1496K RUN 0:00 6.25% 6.25%
On Tue, Feb 04, 2003 at 09:38:18PM -0800, Kris Kennaway wrote:
I just booted a kernel with SCHED_ULE. It looks like there's a pretty
serious bug:
PID USERNAME PRI NICE SIZERES STATETIME WCPUCPU COMMAND
573 dnetc139 20 1000K 804K RUN 1:29 85.94% 85.94% dnetc
On Tue, Feb 04, 2003 at 09:38:18PM -0800, Kris Kennaway wrote:
I just booted a kernel with SCHED_ULE. It looks like there's a pretty
serious bug:
PID USERNAME PRI NICE SIZERES STATETIME WCPUCPU COMMAND
573 dnetc139 20 1000K 804K RUN 1:29 85.94% 85.94% dnetc
On Tue, Feb 04, 2003 at 09:54:23PM -0800, Steve Kargl wrote:
On Tue, Feb 04, 2003 at 09:38:18PM -0800, Kris Kennaway wrote:
I just booted a kernel with SCHED_ULE. It looks like there's a pretty
serious bug:
PID USERNAME PRI NICE SIZERES STATETIME WCPUCPU COMMAND
On Tue, 4 Feb 2003, Kris Kennaway wrote:
On Tue, Feb 04, 2003 at 09:54:23PM -0800, Steve Kargl wrote:
On Tue, Feb 04, 2003 at 09:38:18PM -0800, Kris Kennaway wrote:
I just booted a kernel with SCHED_ULE. It looks like there's a pretty
serious bug:
PID USERNAME PRI NICE SIZE
In message [EMAIL PROTECTED], Greg 'groggy' Lehey
writes:
2. %busy. I personally think this is the most important one, but as
you say, there's no reason not to do the others as well.
The problem with this one is that we can't measure it in a way which
tells us the truth, and we may not
On Wed, 2003-02-05 at 00:39, Matt Rudderham wrote:
Hi,
You're DMESG is only showing those disks as running at UDMA33, Verify
your cabling and go for some high quality 80Pin cables, this should make
a big difference, I find FreeBSD sometimes has a few quirks in this
area, but nothing concrete
76 matches
Mail list logo
