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
-1.,-1.0001] 3.157770 at -1.246957268051453610329e+00
> [-2.,-2.0001] 2.987659 at -2.220949465449893090070e+00
>
> Note, 1.01e-17 can be reduced to soemthing like 1.01e-19 or
Extra diffs most welcome!
M
--
Mark R V Murray
signature.asc
Description: Message signed with OpenPGP
> 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
ver/underflow if x is not close to one */
> - if(ix<0x3f77) return (hy<0)? sn*huge*huge:sn*tiny*tiny;
> + if(ix<0x3f76) return (hy<0)? sn*huge*huge:sn*tiny*tiny;
> if(ix>0x3f87) return (hy>0)? sn*huge*huge:sn*tiny*tiny;
> /* now |1-x| is tiny <= 2**-20, suffice to compute
> log(x) by x-x^2/2+x^3/3-x^4/4 */
>
>
> --
> Steve
>
--
Mark R V Murray
signature.asc
Description: Message signed with OpenPGP
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,
>
om_fortuna_seeded=off
> debug.fail_point.random_fortuna_seeded: return(1) -> off
>
> ...
> 9e5eb30f
>
>
> Best,
> Conrad
> ___
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
>
--
Mark R V Murray
signature.asc
Description: Message signed with OpenPGP
> On 13 Sep 2015, at 16:45, Sean Bruno wrote:
> Any chance you can turn TSO off if its on and see what your results are?
Only TSO4 was on. I turned it off; no difference.
M
--
Mark R V Murray
___
freebsd-current@freebsd.org mailing list
> On 8 Sep 2015, at 19:02, Mark R V Murray wrote:
>
>
>> On 8 Sep 2015, at 17:22, Sean Bruno wrote:
>>
>>
>>>>>
>>>>> I’m also seeing breakage with the em0 device; this isn’t a kernel
>>>>> hang, it is a failure
ge
subclass = ATA
atapci0@pci0:2:0:0: class=0x01018f card=0x610111ab chip=0x610111ab rev=0xb1
hdr=0x00
vendor = 'Marvell Technology Group Ltd.'
device = '88SE6101/6102 single-port PATA133 interface'
class = mass storage
subclass = ATA
dc0
> On 8 Sep 2015, at 00:44, Sean Bruno wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
>
>
> On 09/07/15 14:10, Mark R V Murray wrote:
>>
>>> On 5 Sep 2015, at 17:11, Garrett Cooper
>>> wrote:
>>>
>>>
>
device 25.0 on pci0
em0: Using an MSI interrupt
em0: Ethernet address: 00:16:76:d3:e1:5b
em0: netmap queues/slots: TX 1/1024, RX 1/1024
Fixing it is as easy as …
# ifconfig em0 down ; service ipfw restart ; ifconfig em0 up
:-)
I’m running CURRENT, r287538. This last worked of me a month o
> On 22 Aug 2015, at 13:49, Mark R V Murray wrote:
>
>
>> On 22 Aug 2015, at 06:03, Steve Kargl
>> wrote:
>>
>>
>> Please fix.
>
> On its way.
Fixed.
A git commit was in the wrong review (D3197 instead of D3354). This is now
committed
> On 22 Aug 2015, at 06:03, Steve Kargl
> wrote:
>
>
> Please fix.
On its way.
M
--
Mark R V Murray
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any m
and the /dev/da0* devices
> have not been destroyed.
Weirder and weirder :-(.
Something with SX locks? Hmm. I do use those for attach and detach for
RNG sources. Could it be that that stick of yours is somehow getting
involved in the RNG source locks?
M
--
Mark R V Murray
___
dom is probably trying to harvest some entropy.
I’m sorry my commit caused the problem.
I’m also trying to find out why, but I don’t know enough about USB or
mass-storage devices to know why, so this may take me a while. In the
meanwhile, I’ll try to help by pointing out things I do know.
M
--
M
> On 16 Nov 2014, at 18:21, Ian Lepore wrote:
>
> On Sun, 2014-11-16 at 18:17 +, Mark R V Murray wrote:
>>> On 16 Nov 2014, at 17:51, Steve Kargl
>>> wrote:
>>>
>>> Is there a 'random: device_detach():' missing between the 'u
> On 16 Nov 2014, at 17:51, Steve Kargl
> wrote:
>
> Is there a 'random: device_detach():' missing between the 'umass0'
> and 'da0' messages in the last 4 lines.
No. At attach time, the RNG grabs some probe entropy. At detach
Hi Folks,
Please could the wisdom-of-crowds apply its collective attention to this?
Thanks!
M
Begin forwarded message:
> From: Mark R V Murray
> Subject: New /dev/random code for review please.
> Date: 4 May 2014 18:28:43 BST
> To: "sect...@freebsd.org Team"
> Conte
in jails IFF this
didn’t leak out and prevent harvesting in the jail’s host AND this
gave a noticeable simplification of script code.
M
--
Mark R V Murray
signature.asc
Description: Message signed with OpenPGP using GPGMail
On 26 Nov 2013, at 12:10, Anthony Perkins wrote:
> On Mon, Nov 25, 2013 at 09:58:12PM +, Mark Robert Vaughan Murray
> wrote:
>>
>> You may want to extend your idea a bit and do what par (ports/textproc/par)
>> does. This is a paragraph reformatter that takes
ay want to extend your idea a bit and do what par (ports/textproc/par)
does. This is a paragraph reformatter that takes the quoting into account,
replacing it after the paragraph wrapping.
M
--
Mark R V Murray
signature.asc
Description: Message signed with OpenPGP using GPGMail
On 23 Nov 2013, at 10:24, Don Lewis wrote:
> On 23 Nov, Mark Robert Vaughan Murray wrote:
>> Hi *
>>
>> Anyone else seeing panics like this?
>>
>> This is CURRENT, amd64, 2 CPUs, source synced on Thursday 21st Nov evening
>> GMT sometime.
>>
vm_pageout+0x3bc/frame 0xfe003c7ddbb0
+fork_exit() at fork_exit+0x84/frame 0xfe003c7ddbf0
+fork_trampoline() at fork_trampoline+0xe/frame 0xfe003c7ddbf0
+--- trap 0, rip = 0, rsp = 0xfe003c7ddcb0, rbp = 0 ---
+KDB: enter: panic
M
--
Mark R V Murray
signature.asc
Description: Message
default for other arches. Similar for the other
> settings.
That makes sense, thanks!
M
--
Mark R V Murray
signature.asc
Description: Message signed with OpenPGP using GPGMail
e server,
that may not be enough, and we may be scrambling for more.
M
--
Mark R V Murray
signature.asc
Description: Message signed with OpenPGP using GPGMail
the work if there is a somewhat foolproof way of doing so.
M
--
Mark R V Murray
signature.asc
Description: Message signed with OpenPGP using GPGMail
uite a busy harvestq - could you please give me some more details of
what that box is and what it was doing at the time (numbers would be good!)
Thanks!
M
--
Mark R V Murray
signature.asc
Description: Message signed with OpenPGP using GPGMail
On 10 Sep 2013, at 19:13, Harald Schmalzbauer wrote:
> Hello,
>
> some time ago, before random(4) was rewritten for FreeBSD 5 by Mark
> Murray, we had rng, the i815 hardware random number generator.
> At this time, there were rumors about the quality of the randomness.
>
&g
gt; revisions), so at the time I thought head/ was still broken for
> arm and mips architectures.
>
> Sorry for the misunderstanding on my part. delphij corrected me on
> this.
No worries, thanks!
Keep up the good work!
M
--
Mark R V Murray
signature.asc
Description: Message signed with OpenPGP using GPGMail
s as it was. I'll look for a way
to set this bit from the kernel config file.
M
--
Mark R V Murray
signature.asc
Description: Message signed with OpenPGP using GPGMail
On 8 Sep 2013, at 01:36, Glen Barber wrote:
> Either way, I think this commit needs to be reverted until properly
> fixed and tested.
The hyperbole is getting a little thick.
How about
sysctl kern.random.sys.seeded=1
??
M
--
Mark R V Murray
signature.asc
Description: Message
hing you like (hopefully random crud) to the device
and it seeds itself with what it gets. At file close after the write,
it unblocks.
So at the minimum, you can unblock Yarrow by doing
$ echo '' > /dev/random
... as soon as the device is active. There is your knob.
M
--
Mark R
to make it hard to do the wrong thing by accident. It's not
> okay to make it impossible to do that thing on purpose.
Again, true, but please bear in mind that things are suboptimal right now.
M
--
Mark R V Murray
signature.asc
Description: Message signed with OpenPGP using GPGMail
t
> don't have a hardware PRNG to start seeding things with?
This has some merit; but I need to thing about how to do it. Per-architecture
block/no-block defaults are going to get messy unless done properly.
M
--
Mark R V Murray
signature.asc
Description: Message signed with OpenPGP using GPGMail
On 7 Sep 2013, at 20:12, Sean Bruno wrote:
> On Sat, 2013-09-07 at 19:56 +0100, Mark R V Murray wrote:
>>> Ok. Right now, the mips kernel doesn't build unless I have random
>> built
>>> in, we were using it as a module previously.
>>
>>
>&
On 7 Sep 2013, at 19:49, Sean Bruno wrote:
> On Sat, 2013-09-07 at 19:40 +0100, Mark R V Murray wrote:
>>> Looks like it does indeed work if that is set to 1.
>>>
>>> This "DIR-825" config, should be loading random as a module, not
>> built
>
On 7 Sep 2013, at 19:36, Sean Bruno wrote:
> On Sat, 2013-09-07 at 18:39 +0100, Mark R V Murray wrote:
>> On 7 Sep 2013, at 17:43, Sean Bruno wrote:
>>> trying to enable random on my DIR-825 kernconf I get this on boot:
>>>
>>> Configuration file: /
Please make a change to sys/dev/random/randomdev_soft.c;
Around line 82, please change from ".seeded = 0" to ".seeded = 1".
If that works, then your report above with the "Entropy device is blocking."
is trying to read random numbers before /dev/random is secure;
> Using interface wlan0 with hwaddr 00:00:88:88:22:22 and ssid "TESTBRUNO"
> Entropy device is blocking.
Can you please see if you can get the output of "sysctl -a | grep random"
at that point?
M
--
Mark R V Murray
signature.asc
Description: Message signed with OpenPGP using GPGMail
p in /usr/src/lib/libz.
*** Error code 1
Stop in /usr/src.
*** Error code 1
Stop in /usr/src.
*** Error code 1
Stop in /usr/src.
*** Error code 1
Stop in /usr/src.
M
--
Mark R V Murray
Cert APS(Open) Dip Phys(Open) BSc Open(Open) BSc(Hons)(Open)
Pi: 132511160
___
"Bjoern A. Zeeb" writes:
> On Fri, 15 Oct 2010, Mark Murray wrote:
>
> > Alexey Shuvaev writes:
> >>> gifconfig_gif0_ipv6="2001:::::2 2001:::::1
> >>> prefixlen 128"
> >>
h for "Sample IPv6").
Ah!
It didn't occur to me that I might need TWO inet6's! I'll give that a go when
I play with this again tomorrow.
M
--
Mark R V Murray
Cert APS(Open) Dip Phys(Open) BSc Open(Open) BSc(Hons)(Open)
Pi: 132511160
___
setting up IPv6 in CURRENT is a moving
target, and I can't find a working example any more. I've looked in
/etc/defaults/rc.conf, but the gifN examples there are all devoid of any
IPv6 examples.
M
--
Mark R V Murray
Cert APS(Open) Dip Phys(Open) BSc Open(Open) BSc(Hons)(Open)
Pi: 132511160
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
1 - 100 of 794 matches
Mail list logo
