Hi folks
Could those folks interested in the math.h library please review
https://reviews.freebsd.org/D44168 ?
It is a fix for 128-bit (IEEE float) tgammal(3), which has been a "stub"
implementation using the 80-bit version to date. The above patch fixes that.
Thanks!
M
--
Mark R V Murray
> On 18 Dec 2021, at 17:51, Steve Kargl
> wrote:
>
> On Sat, Dec 18, 2021 at 10:41:14AM +, Mark Murray wrote:
>>
>> Hmm. I think my understanding of ULP is missing something?
>>
>> I thought that ULP could not be greater than the mantissa size
> On 18 Dec 2021, at 03:52, Steve Kargl
> wrote:
>
> On Tue, Dec 14, 2021 at 10:21:55PM +, Mark Murray wrote:
>> On 14 Dec 2021, at 21:51, Steve Kargl
>> wrote:
>>> Interval max ULP x at Max ULP
>>> [6,1755.1]0.873414 at
On 14 Dec 2021, at 21:51, Steve Kargl wrote:
> Interval max ULP x at Max ULP
> [6,1755.1]0.873414 at 1.480588145237629047468e+03
> [1.0662,6]0.861508 at 1.999467927053585410537e+00
> [1.01e-17,1.0661] 0.938041 at 1.023286481537296307856e+00
> [-1.,-1.0001] 3.1
> On 14 Dec 2021, at 20:41, Steve Kargl
> wrote:
>
> On Tue, Dec 14, 2021 at 06:26:13PM +, Mark Murray wrote:
>>
>> This is now visible for review at
>> https://reviews.freebsd.org/D33444 <https://reviews.freebsd.org/D33444>
>>
>
> Just look
> On 13 Dec 2021, at 02:22, Steve Kargl
> wrote:
>
> On Sat, Dec 04, 2021 at 11:48:13PM +, Mark Murray wrote:
>>
>>
>>> On 4 Dec 2021, at 18:53, Steve Kargl
>>> wrote:
>>>
>>>
>>> So, is anyone interested in se
> On 4 Dec 2021, at 18:53, Steve Kargl
> wrote:
>
>
> So, is anyone interested in seeing a massive patch?
Me, please!
M
--
Mark R V Murray
signature.asc
Description: Message signed with OpenPGP
r the quick response.
>>
>> Of course, a one character diff might be easier to review. :-)
>>
>> --
>> steve
>>
>> On Mon, Sep 06, 2021 at 06:55:07PM +0100, Mark Murray wrote:
>>> Thanks!
>>>
>>> And it's committed!
>&
Thanks!
And it's committed!
M
> On 6 Sep 2021, at 18:53, Steve Kargl
> wrote:
>
> Fine with me. I don't have a phabricator account and
> bugzilla reports seems to get lost in the ether.
>
> --
> steve
>
> On Mon, Sep 06, 2021 at 06:45:11PM +01
Hi
I've opened a Phab ticket for this. I hope that's OK?
https://reviews.freebsd.org/D31865
M
> On 6 Sep 2021, at 16:28, Steve Kargl
> wrote:
>
> Paul Zimmermann has identified a bug in Openlibm's powf(),
> which is identical to FreeBSD's libm. Both derived from
> fdlibm. https://github.com
Hi *
I've been getting these build failures for a while (weeks/months). The machine
is a MacchiatoBin DoubleShot (arm64, Quad core). with SATA disks and zfs
filesystem. If I empty out /usr/obj, then the build works, but takes a few
hours. If I do a no-clean build with /obj/obj populated with he
On 12 Sep 2020, at 12:18, Eric McCorkle wrote:
>
> I recently updated my other laptop, and now I'm getting a problem
> loading zfs.ko at boot, relating to the lockstat_enabled symbol not
> being defined (this happens during kernel boot and prevents mounting
> root, so I can't get an exact trace)
> On 28 Aug 2020, at 17:25, Warner Losh wrote:
>
> Greetings,
Hi
> I'd like to retire the spkr driver. It was a cute hack before sound cards
> were ubiquitous, but it's not been kept up to date, and it's not clear that
> it still works It is still Giant locked, and though it's not a huge
>
Hi
RANDOM_ENABLE_UMA has not been tested in a while and my need to be retired. It
had a pretty significant effect on a time-critical part of the kernel, and
there are much better ways to get entropy.
Thanks,
M
> On 16 Feb 2020, at 12:51, Lev Serebryakov wrote:
>
> Hello freebsd-current,
>
Tim Kientzle writes:
> I have a FreeBSD-CURRENT AMD64 system here that was last updated at =
> r215029.
>
> I'm trying to update it to r219079, but the build fails in lib/libz when =
> it tries to compile gvmat64.S. It looks like the Makefile here has a =
> workaround for clang on AMD64, but it d
"Bjoern A. Zeeb" writes:
> On Fri, 15 Oct 2010, Mark Murray wrote:
>
> > Alexey Shuvaev writes:
> >>> gifconfig_gif0_ipv6="2001:::::2 2001:::::1
> >>> prefixlen 128"
> >>
Alexey Shuvaev writes:
> > gifconfig_gif0_ipv6="2001:::::2 2001:::::1
> > prefixlen 128"
>
> I suppose you should prefix it with "inet6" keyword.
> There are 2 examples in rc.conf (search for "Sample IPv6").
Ah!
It didn't
Hi
IPv6 gurus: what are the CURRENT /etc/rc.conf incantations to do the
following (which works):
$ ifconfig gif0 create
$ ifconfig gif0 tunnel 192.168.0.2 11.22.33.44
$ ifconfig gif0 inet6 2001:::::2 2001:::::1 prefixlen
128
$ route -n add -inet6 default 2001:::33
Hi
You haven't responded to this. I'm very interested in these patches,
please.
M
--- Forwarded Message
Date:Thu, 27 Nov 2003 11:51:19 +
From:Mark Murray <[EMAIL PROTECTED]>
To: Terry Lambert <[EMAIL PROTECTED]>
cc: [EMAIL PROTECTED]
Subject: Re:
not posted in their entirety to the mailing list. In
> actuality, I only ever posted portions of my own patches, since
> they also required compiler and linker changes.
Could you please post your patches in their entirety?
M
--
Mark Murray
iumop ap!sdn w,I idlaH
_
you give a timeframe, a subject
and/or something?
M
--
Mark Murray
iumop ap!sdn w,I idlaH
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
rtising". I think that keeping
DFBSD-Advocacy/Discussion on FreeBSD lists to a pretty low level would
help keep blood pressure down all round (No offense intended, DFBSD is
a worthwhile project, its just that inter-project politics are somewhat
rough, and I'm trying to cool things down!
Hi
The matcd(4) driver needs an active maintainer. Do we have any
volunteers? Without active maintenance/use, the driver will rot,
die and be removed from the tree.
Speak up now!
M
--
Mark Murray
iumop ap!sdn w,I idlaH
___
[EMAIL PROTECTED] mailing
"Scott M. Likens" writes:
> Ah, such a strong comment from such a strong member. I would have thought
> you were to high to stoop that low?
>
> But I guess it's good to be flamed for being honest? is it not?
Please don't encourage flames and flamers by respo
you show
some pretty specific problems in rather fine (and not too long) detail,
you are pretty much on your own. Sorry!
For this, the questions@ and newbies@ lists are better than [EMAIL PROTECTED]
M
--
Mark Murray
iumop ap!sdn w,I idlaH
___
[EMAIL
"Poul-Henning Kamp" writes:
> For stuff like AES we should _really_ have a standalone regression
> test. Anyone out there willing to make one from the official AES
> test-vectors from NIST ?
Yeah. I can do this. Gimme a day or three.
M
--
Mark Murray
ium
to use these would be
in the "make distribute" target that "make release" uses. This way, the
files are already separated out into directory structures, and it may be
easier to build complex pkg-plist's with find(1). ALSO, it may be easier
to make more fine-grained packages
So, reluctantly,
yes, if you can't find a better place to hack a fix.
M
--
Mark Murray
iumop ap!sdn w,I idlaH
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
atus line that
you get in response.
Thanks!
M
--
Mark Murray
iumop ap!sdn w,I idlaH
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
7;m suspecting that a lock is needed.
I'll need to put a serial debugger on to go any further. Does this
work, or will I be wasting effort? (Getting that cable in is going
to be a _pain_).
M
--
Mark Murray
iumop ap!sdn w,I idlaH
___
[EMAIL PROTECTED] m
py to try patches if anyone has ideas.
M
--
Mark Murray
iumop ap!sdn w,I idlaH
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
> machine, and want something better than beeps.
Would it be a useful exercise for the minority(?) of users who use this
driver to either see if it can be effectively newbussed or turned into
a port or both?
I see considerable scope for an infrastructu
off EISA, and I
need to turn it on.
I can connect on a serial console, but ECU assumes a VT220, and
the output is unreadable.
Any suggestions?
M
--
Mark Murray
iumop ap!sdn w,I idlaH
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/
n't link properly much later.
I'd need a complete log to comment further. PLEASE DON'T EMAIL IT!! Please
put it somewhere for me to fetch. Any diffs to release/Makefile and the
exact command line used to kick off the build would be useful too.
Thanks!
M
--
Mark Murray
iumop ap!sdn w
Wilko Bulte writes:
> On Thu, Jul 31, 2003 at 01:40:28PM +0100, Mark Murray wrote:
> > Wilko Bulte writes:
> > > > Sounds like an SRM problem or EISA configuration problem.
> > > > Normaly the bus and then system board should be probed at this point.
> >
'runecu' from the SRM console and it should work.
With the froppy in the drive, I presume? The SRM console is the
">>>" prompt where you type "boot", right?
(Typing from work - will do at home later).
M
--
Mark Murray
iumop ap!sdn w,I idlaH
did not follow in detail to be honest. Check the archives.
Well, that's left me hosed :-(.
I looked through current@ and alpha@ (briefly) and saw nothing
obvious. What should I be looking for?
M
--
Mark Murray
iumop ap!sdn w,I idlaH
___
ernel also has above error.
Remove eisa, and the boot goes straight to panic (no clock).
M
--
Mark Murray
iumop ap!sdn w,I idlaH
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
capabilities: 21
pcib0: <2117x PCI host bus adapter> on cia0
pci0: on pcib0
eisab0: at device 7.0 on pci0
halted CPU 0
halt code = 7
machine check while in PAL mode
PC = 18100
>>>
Any idea what gives?
M
--
Mark Murray
iumop ap!sdn w,I idlaH
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
gt;
> Cheers,
> --=20
> Ruslan ErmilovSysadmin and DBA,
> [EMAIL PROTECTED] Sunbay Software Ltd,
> [EMAIL PROTECTED] FreeBSD committer
>
> --A9z/3b/E4MkkD+7G
> Content-Type: application/pgp-signature
> Content-Disposition: inline
>
{MINUSLPAM}
> -.if !defined(NO_KERBEROS)
> +.if exists(${.CURDIR}/../../kerberos5) && !defined(NO_KERBEROS)
> CFLAGS+=3D -DKRB5 -DFORWARD -Dnet_write=3Dtelnet_net_write
> DPADD+=3D${LIBKRB5} ${LIBASN1} ${LIBCOM_ERR} ${LIBROKEN}
> LDADD+=3D-lkrb5 -lasn1 -lcom_err -lroken
Anti writes:
> buildworld fails at telnet if you build with NOCRYPT and NO_OPENSSL --
> telnet stuff is looking for NO_CRYPTO to disable this, which isn't
> documented anywhere...
Thanks!
This should be fixed now.
M
--
Mark Murray
iumop ap
bit thin. Is there a problem with the
> tinderbox build machine perhaps?
My home box is doing it too. as(1) blowing up "randomly". No usable core
dumps. :-(.
M
--
Mark Murray
iumop ap!sdn w,I idlaH
___
[EMAIL PROTECTED] mailing list
http://l
rent.
I'm seeing this on current. I use bash, and the machine is not
loaded. The heaviest process is spamassassin. There isn't even X running
on the box.
M
--
Mark Murray
iumop ap!sdn w,I idlaH
___
[EMAIL PROTECTED] mailing list
http://lists.free
n detail to [EMAIL PROTECTED] so we can get a more
permanent fix.
M
--
Mark Murray
iumop ap!sdn w,I idlaH
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
I have a broken driver, with a dodgy patch to "fix" it, and you guys are
both saying "not my problem".
I'm quite happy to make it my problem, but I'll need a bit of help,
please. Who is it going to be?
M
--
Mark Murray
iumop ap!sdn w,I idlaH
n the interrupts).
Can you have a look at this please?
The symptoms are an ep0 that works for a few packets and then completely
stops working. It doesn't respond to pings, nothing.
M
--
Mark Murray
iumop ap!sdn w,I idlaH
___
[EMAIL PROTECTED] mailing
it all for
> me. However, it's always possible that yours is a slightly different problem,
> so I'd be interested to hear what you are doing exacly so that I could try
> and repeat it.
Hi.
Reverting pccbb.c to 1.75 fixed this for me.
M
--
Mark Murray
iumop ap!sdn w,I idlaH
What a weekend. Frigging _everything_ was a messup.
"M. Warner Losh" writes:
> In message: <[EMAIL PROTECTED]>
> Mark Murray <[EMAIL PROTECTED]> writes:
> : "M. Warner Losh" writes:
> : > Have you gotten all of the recent changes to cur
"M. Warner Losh" writes:
> In message: <[EMAIL PROTECTED]>
> Mark Murray <[EMAIL PROTECTED]> writes:
> : "M. Warner Losh" writes:
> : > Have you gotten all of the recent changes to current wrt ep0? It was
> : > broken by my ma
ease confirm where the change was to be sure?
M
--
Mark Murray
iumop ap!sdn w,I idlaH
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
if I back out recent diffs to
if_ep.c it doesn't fix anything, so I'm suspecting pccardd code.
Any similar observations?
M
--
Mark Murray
iumop ap!sdn w,I idlaH
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinf
John Baldwin writes:
>
> On 24-Jun-2003 Mark Murray wrote:
> > Hi
> >
> > You (?) gave me these patches at least 6 months ago, and they've
> > been working for my Libretto ever since then. Is it OK if I commit
> > them?
>
> No, not quite yet.
Hi
You (?) gave me these patches at least 6 months ago, and they've
been working for my Libretto ever since then. Is it OK if I commit
them?
M
--
Mark Murray
iumop ap!sdn w,I idlaH
Index: dev/acpica/acpi.c
===
RCS file: /home
he port carries a copy of the repository with it. Anyone may fix this port,
I'm not holding a lock.
M
--
Mark Murray
iumop ap!sdn w,I idlaH
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscri
Kris Kennaway writes:
> > Oops. Fix coming later today.
>
> Any progress on this?
Yes. I'll commit as soon as I upload the dist tarball.
M
--
Mark Murray
iumop ap!sdn w,I idlaH
___
[EMAIL PROTECTED] mailing list
http://lists.fr
hardware you
investigate to perform the task.
While you are asking the questions, _experiment_ with what you have, and
look for real-life holes in your setup. Try to think like the attacker you
are trying to thwart. Attack yourself. Get paranoid.
M
--
Mark Murray
iumop ap!sdn w,I idlaH
It usually
comes to quite a lot more than that, depending on what it is you want
to do _exactly_.
The above will work in certain circumstances, but simple testing will
tell you that. What we can't tell is whether you need a Land Rover or
a Bulldoze
Kris Kennaway writes:
> > I installed freebsd-games, and it has most of the games I remember, but n=
> ot
> > rogue.
>
> Well, hrumph, it's supposed to be in that port. Mark, it looks like
> rogue wasn't added for some reason.
Oops. Fix coming later today.
Hi all
Last time I looked, we had _very_ few CTM users.
Is there any reason that the CTM stuff should not be a port?
M
--
Mark Murray
iumop ap!sdn w,I idlaH
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
Martin Blapp writes:
> maps using ypchpass(1). Again, this only applies to the super-user on
> the NIS master server: none of these special functions can be performed
> over the network.
I am happy!
M
--
Mark Murray
iumop ap!sdn
of the users password.
Does this not create a vulnerability?
Example: Bad Guy sets up a personal workstation with himself as root
and steals an IP address from the machine he just switched off. Now
he can change passwords on the server at will.
M
--
Mark Murray
i
troll go away is to ignore it.
I'm dealing with the problem.
M
--
Mark Murray
iumop ap!sdn w,I idlaH
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
racks? Not everyone running -current is on top of this stuff (for better
> or worse).
No. :-).
If you use CURRENT, stay current. We can't prevent _every_ foot-shoot.
M
--
Mark Murray
iumop ap!sdn w,I idlaH
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
KerbIV remains are markers for stuff that we need to revisit.
> For you, the easiest way to jump is to remove MAKE_KERBEROS4
> from /etc/make.conf.
Yes. You should not be using that; it is well broken now.
M
--
Mark Murray
iumop ap!sdn w,I idlaH
To Unsubscribe: send mail to [EMAIL PROTECTED]
live Kerberos 5 !!
M
--
Mark Murray
iumop ap!sdn w,I idlaH
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
FreeBSD NAT
>
>
> How long can this remain unfixed before the code is diked out,
> and the checksum is recalculated fully, instead?
Terry, you sound rather foolish when you argue like this. This
is semantic tomfoolery and off topic. End of thread.
M
--
Mark Murray
iumop ap!sdn w,I
Terry Lambert writes:
> Mark Murray wrote:
> > Only if it kills this _really_ dumb debate. In time, it will no longer
> > compile, and then the situation will be the same as just punting to the
> > Attic without the "fix".
>
> Only if some idiot breaks
Terry Lambert writes:
> Mark Murray wrote:
> > Will it be runnable (as in tested), rather than a compile-only fix?
>
> Is "tested" a requirement fo code to be committed or to have it
> stay in the tree?
Both.
> Be careful of your answer, unless you are willing to
good state to leave the code in the attic.
Only if it kills this _really_ dumb debate. In time, it will no longer
compile, and then the situation will be the same as just punting to the
Attic without the "fix".
M
--
Mark Murray
iumop ap!sdn w,I idlaH
To Unsubscribe: send mail to [EMAIL P
you guys bitch about it not being fixable.
Will it be runnable (as in tested), rather than a compile-only fix?
M
--
Mark Murray
iumop ap!sdn w,I idlaH
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
ed you could do address arithmetic on a caddr_t. You can't do
> that on a void *, at least not in ANSI C. I think gcc lets you do
> it, but it's an extension.
As I have discovered. I specifically looked for this, and my misreading
of the spec is now clear. :-)
M
--
Mark Murr
fix the errors this
causes. So far, they are all no-brainers; mainly function prototypes
that are inconsistent with their definitions. There are a few places
where caddr_t is assumed to point to char.
M
--
Mark Murray
iumop ap!sdn w,I idlaH
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
a static major number.
>
> Please help remove entries in sys/conf/majors for which there exists
> no software, and convert drivers to use "MAJOR_AUTO" instead of using
> static major numbers.
>
> Thanks in advance!
What is a good driver to crib this from? I'll
opensslconf.h's that are used in the FreeBSD build ...
> let's see if this is intentional or not. [cc'd]
Not intentional. If adding it breaks nothing, go ahead. I have Panic City
right now on my devboxes, so I'm working on fixing that.
M
--
Mark Murray
iumop ap!sdn w,I
"David O'Brien" writes:
> On Sun, Feb 16, 2003 at 07:11:49PM +, Mark Murray wrote:
> > In the case where an application is OPIEised and not PAMised, we
> > need to figure out something; PAMizing such apps is not terribly
> > hard. If any of them are in
ld really be falling
in with that, no?
In the case where an application is OPIEised and not PAMised, we
need to figure out something; PAMizing such apps is not terribly
hard. If any of them are in the base system, then this situation
is a bug in its own right. If they are ports, they need to fall in
ible to move _all_ policy control into PAM, instead of
having it split between OPIE and PAM?
M
--
Mark Murray
iumop ap!sdn w,I idlaH
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
es who ignore that simple fact that "" was localhost alias
> in OPIE for years before any evil PAM appearse. As you see, I am specific.
Does the ""-as-localhost-alias break other PAM modules?
In what way does "localhost" or NULL break OPIE?
M
--
Mark Murray
i
Dag-Erling Smorgrav writes:
> "Andrey A. Chernov" <[EMAIL PROTECTED]> writes:
> > Admins with no /etc/opieaccess AFFECTED!
>
> Admins with no /etc/opieaccess IDIOTS for not running mergemaster!
POLA. We don't want to burn our user/admins.
M
--
Mark Murray
iu
"Andrey A. Chernov" writes:
> On Mon, Feb 03, 2003 at 10:55:42 +, Mark Murray wrote:
> >
> > How do you _know_ that your newly chosen magic number isn't going to cause
> > some kind of recurring (and too-short) sequence of numbers?
>
> I run simple
sequence of numbers?
Will it recur after 5 iterations? 100? 1000? 100?
M
--
Mark Murray
iumop ap!sdn w,I idlaH
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
"Andrey A. Chernov" writes:
> On Sun, Feb 02, 2003 at 22:35:54 +, Mark Murray wrote:
> >
> > I stand (somewhat) corrected. The random() code is _nasty_ complexity-wise.
> > Its not obvious how it works.
> >
> > RC4 is 10-20 lines and clean with n
"Andrey A. Chernov" writes:
> On Sun, Feb 02, 2003 at 22:19:33 +, Mark Murray wrote:
>
> > > 1) Implementing random(3) with RC4 is not needed, its algorithm is
> > > already equal or better.
> >
> > Rubbish. :-) RC4's internal state is 256
"Andrey A. Chernov" writes:
> On Sun, Feb 02, 2003 at 21:23:43 +, Mark Murray wrote:
> >
> > That was random(9). KERNEL random().
>
> KERNEL random() can be easily implemented (better - replaced) with
> arc4random(), there is no objections. But...
>
&g
r behavior
> change should either use a new name or make an upward
> compatible change.
You have said that before, and I understand your words.
I disagree with them.
> Now the question is whether perl uses system provided
> random() or rand() or its own since perl is used extensi
OTECTED]> where he
> says
>
> Good point. We can re-implement random() internally with arc4rand().
Quote it in context, please.
That was random(9). KERNEL random().
However, the argument applies equally well to rand(3) and random(3).
M
--
Mark Murray
iumop ap!sdn w,I i
ical OSes
> do a good job of maintaining compatibility. IRIX certainly
> did a pretty good job of it. FreeBSD also does a pretty good
> job on the whole.
"Reasonable" is an opinion. It is not shared by me. :-)
Irix was well known for its bugs.
M
--
Mark Murray
iumop ap!sdn w,I id
Bakul Shah writes:
> Note that it is rand() that is broken, not random() as can be
> seen by modifying Kris Kennaways' test so I don't see why
> Mark Murray was talking about changing it in the first place.
rand(3) says:
STANDARDS
The rand() and srand() functions conf
compatibility. The point of compatibility is to
> not break interfaces unless there is a significant benefit.
We are not proposing interface breaks.
M
--
Mark Murray
iumop ap!sdn w,I idlaH
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
ber generator uses from the traditional simulation use?
> That way you can change crypto_random to your heart's content
> as the crypto needs change (as they will).
The two are related topics.
Consider the (joking reference to) "elephant-free biology". :-)
M
--
Mark Murray
iumop ap!sdn w,I idlaH
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
David Malone writes:
> On Sun, Feb 02, 2003 at 07:08:47PM +0000, Mark Murray wrote:
> > RC4 is _utterly_ repeatable, given a particular seed/key.
>
> I presume it also produces reasonably uniform output for most
> seeds too.
Yes. Modulo the requirement to "burn" a
t the crypto guys to look out for the simulation guys!
Are you a Verilog guy ar a VRML guy? Something else maybe?
M
--
Mark Murray
iumop ap!sdn w,I idlaH
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
m enough for your purposes,
> go create a new function with a *new* name.
Any supporters of this request?
> [I see from his latest email that PHK remembered the old
> discussion!]
So did I!
M
--
Mark Murray
iumop ap!sdn w,I idlaH
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
[EMAIL PROTECTED] writes:
> In message <[EMAIL PROTECTED]>, Mark Murray
> wr
> ites:
>
> >We have most of this, and RC4 can deliver. RC4's "licence" is
> >fine. Call it "ArCFour" and there is no problem. The code is
> >small, fast a
of random numbers in regression testing.
I guess those arguments are now moot?
> This is still a valid concern, but I don't know how significant a
> concern it is.
"Insignificant", IMO.
M
--
Mark Murray
iumop ap!sdn w,I idlaH
To Unsubscribe: send mail to [EMAIL PROTECTED]
t OS'es, so regression is limited. Also, regression must not
> stop bugs fixing progress in anycase.
Given a particular seed, it is repeatable across anything that can
compile C.
M
--
Mark Murray
iumop ap!sdn w,I idlaH
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
"Andrey A. Chernov" writes:
> On Sun, Feb 02, 2003 at 17:30:48 +, Mark Murray wrote:
> >
> > Why not? Arc4 is a) deterministic and b) good for all bits.
>
> If you mean arc4random() function - not, because it use true randomness,
> if you mean RC4 algo
"Andrey A. Chernov" writes:
> > Objections?
>
> We can't, simple because sequence must be repeated for the same seed
> across the calls.
RC4 is repeatable.
M
--
Mark Murray
iumop ap!sdn w,I idlaH
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscr
and() must be simple and speedy. Now used variant is most
> simpler, others are much more complex.
RC4 is fast. RC4 is simple. Any objections? :-)
M
--
Mark Murray
iumop ap!sdn w,I idlaH
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
1 - 100 of 733 matches
Mail list logo
