On Sat, 30 Sept 2023 at 08:47, Mark Millard wrote:
> ram_attach is based on regions_to_avail but that is a problem for
> its later bus_alloc_resource use --and that can lead to:
>
> panic("ram_attach: resource %d failed to attach", rid);
>
> Unfortunately, the known example is use of EDK2 on RPi4
On Fri, 7 Jul 2023 at 13:11, Mina Galić wrote:
> Hi folks,
>
> "recently", we added support for null-mounting single files:
>
>
> https://freshbsd.org/freebsd/src/commit/521fbb722c33663cf00a83bca70ad7cb790687b3
>
> This code restricts the mountable … thing to:
>
> if ((lowerrootvp->v_type
I think your intuition is correct - it never makes sense to unload the
kernel (IMO). I approved the review.
Doug.
On Thu, 9 Nov 2023 at 16:10, Zhenlei Huang wrote:
> Hi,
>
> This is *NOT* joking.
>
> While working on https://reviews.freebsd.org/D42527 I realized the
> module kernel also has us
Did you get any feedback on this? I would like to be able to use hwpmc but
my desktop is a recent skylake and I also get the 'hwpc_core: unknown PMC
architecture: 4' error.
CPU: Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz (4008.14-MHz K8-class CPU)
Origin="GenuineIntel" Id=0x506e3 Family=0x6 Mod
Is plockstat supposed to work on FreeBSD? I'm running FreeBSD-current and
when I try it, I get:
plockstat: failed to compile program: probe description
plockstat65047:::rw-block does not match any probes
Any ideas what to try next?
___
freebsd-current@f
On 28 January 2016 at 15:03, Tomoaki AOKI wrote:
> It's exactly the NO GOOD point. The disk where boot1 is read from
> should be where loader.efi and loader.conf are first read.
>
I just wanted to note that gptzfsboot and zfsboot behaves this way. Boot1
looks for loader in the pool which contain
I think a local socket is probably the best solution long term. Using a
local socket also allows using filesystem permissions to control access
which is required for gssd but not necessarily for nfsuserd.
On 10 December 2015 at 13:37, Rick Macklem wrote:
> Hi,
>
> Mark has reported a problem vi
On Thursday, July 9, 2015, Garrett Wollman
wrote:
> In article
> >,
> oliver.pin...@hardenedbsd.org writes:
>
> >Btw, I have found this is atf's documantation:
> >atf_tc_expect_signal(SIGSEGV, "reaseon"), with this, we could mark the
> >specific test case could "fail" / or expect to coredump.
>
As far as I can tell, POSIX doesn't require either EFAULT or any other
behaviour - the text in http://www.open-std.org/jtc1/sc22/open/n4217.pdf
just says, "No errors are defined". Our man page is wrong and any real
program which relies on gettimeofday not faulting when given bad inputs is
broken.
You could add a single integer-valued vfsopt which holds the high-order
bits of f_flags?
On 7 May 2015 at 02:10, Rick Macklem wrote:
> David Boyd reported a problem to freebsd-current@ w.r.t. the
> MNT_AUTOMOUNTED
> flag getting cleared by mountd.
> http://docs.FreeBSD.org/cgi/mid.cgi?14294772
On 16 February 2013 16:18, Elias Mårtenson wrote:
> On 17 February 2013 00:03, Doug Rabson wrote:
>
>> I don't think much (if anything) has changed with gssd between 9.1 and
>> current. When your gssd hangs, you can try to get a stack trace using gdb's
>>
On 16 February 2013 13:57, Elias Mårtenson wrote:
> On 16 February 2013 18:58, Doug Rabson wrote:
>
>> This may be a stupid question but does the user 'elias' exist in the
>> local password database?
>>
>> If you are using heimdal from the base distributi
This may be a stupid question but does the user 'elias' exist in the local
password database?
If you are using heimdal from the base distribution and you have source,
you should be able to build them with debug information which may help.
When I was writing gssd, I mostly ran it under gdb to debug
If all you are doing is reading, the ZFS on-disk format is well documented
and fairly easy to work with. Take a look at the ZFS bootloader code - that
implements a ZFS reader in not too many lines of code and could easily be
re-purposed for a recovery tool.
On 24 May 2012 09:04, Lev Serebryakov w
On 27 September 2011 13:57, Adrian Chadd wrote:
> On 27 September 2011 20:22, Robert Huff wrote:
> >
> > krad writes:
> >> we can leave that to our grand children to figure out though 8)
> >
> >Wasn't that what people said about two-digit years?
>
> Our children will be dealing with Y20
You could try using the standard header - that has inline
functions which should cover all the SSE instructions.
On 12 June 2011 17:43, Hartmann, O. wrote:
> I use some numerical code utilizing the SIMD units of modern X86
> architectures. Code compiles well using gcc/gcc46,
> but clang does no
On 6 June 2010 21:09, Jos Backus wrote:
> Any chance the kadmin protocol will ever be standardized?
>
>
My understanding is that the MIT kadmin protocol is based GSS-API
authenticated RPC which FreeBSD didn't support until recently. I added
working RPCSEC_GSS to our userland RPC library in 2008 a
On 9 Mar 2010, at 00:10, James R. Van Artsdalen wrote:
> Norikatsu Shigemura wrote:
>> According to http://en.wikipedia.org/wiki/AES-NI , we can get
>> specification document: http://software.intel.com/file/20457 .
>>
>> I saw it, and consider that we can release under BSDL. Because
>
On Fri, 05 Mar 2010 14:27:06 +0300, Alex Keda wrote:
> On 05.03.2010 14:16, Doug Rabson wrote:
>> On Fri, 05 Mar 2010 14:10:43 +0300, Alex Keda
wrote:
>>
>>> On 05.03.2010 13:59, Poul-Henning Kamp wrote:
>>>
>>>> In message<
On Fri, 05 Mar 2010 14:10:43 +0300, Alex Keda wrote:
> On 05.03.2010 13:59, Poul-Henning Kamp wrote:
>> In message<4b90e171.2040...@lissyara.su>, Alex Keda writes:
>>
>>
>>> then can a more correct name of the project or ClosedBSD or
ManagedBSD?
>>> =)
>>> or something abstract?
>>>
>>
On Fri, 05 Mar 2010 13:48:17 +0300, Alex Keda wrote:
> On 05.03.2010 12:59, Doug Rabson wrote:
>> On 5 Mar 2010, at 09:56, Alex Keda wrote:
>>
>>
>>> On 05.03.2010 12:45, Doug Rabson wrote:
>>>
>>>> On 5 Mar 2010, at 09:30, Alex Keda w
On 5 Mar 2010, at 09:56, Alex Keda wrote:
> On 05.03.2010 12:45, Doug Rabson wrote:
>> On 5 Mar 2010, at 09:30, Alex Keda wrote:
>>
>>
>>> On 05.03.2010 12:17, Robert Watson wrote:
>>>
>>>> consumers like Isilon, NetApp, Juniper, an
On 5 Mar 2010, at 09:30, Alex Keda wrote:
> On 05.03.2010 12:17, Robert Watson wrote:
>> consumers like Isilon, NetApp, Juniper, and many others
> thus, it is not 'Free', this managed by 'consumers like Isilon, NetApp,
> Juniper, and many others'?
It might be helpful to think of them as 'custom
On Fri, 2003-11-28 at 07:59, Peter Jeremy wrote:
> On Thu, Nov 27, 2003 at 11:24:23AM -0500, Robert Watson wrote:
> [Darwin pre-binding]
> >presumably applies to other processor architectures. The one thing that
> >turns me off to this scheme is that I'd like it if we could find a way to
> >repres
On Mon, 2003-11-17 at 08:44, Philippe Charnier wrote:
> Salut,
>
> Doug Rabson <[EMAIL PROTECTED]> wrote:
>
> >On Sat, 2003-11-15 at 22:32, Philippe Charnier wrote:
> >> Hello,
> >>
> >> I have a Compaq armada 7800 with a noname pccard
On Sat, 2003-11-15 at 22:32, Philippe Charnier wrote:
> Hello,
>
> I have a Compaq armada 7800 with a noname pccard ethernet adapter
> which used to be detected as:
>
> rl0: port 0x1100-0x11ff mem 0x8800-0x880001ff irq 11
> at device 0.0 on cardbus0
> rl0: Ethernet address: 00:10:60:58:60:b
On Mon, 2003-11-10 at 23:39, Alex Wilkinson wrote:
> On Mon, Nov 10, 2003 at 09:02:03AM +0000, Doug Rabson wrote:
>
> I wasn't involved in converting taskqueue from 4.x-style SWIs to kernel
> threads so I can't be sure but this does look reasonable. I
I wasn't involved in converting taskqueue from 4.x-style SWIs to kernel
threads so I can't be sure but this does look reasonable. I've been
wondering about the 'not exiting' diagnostic from init for a while
myself.
On Mon, 2003-11-10 at 05:10, Alfred Perlstein wrote:
> I noticed that init was comp
On Thu, 2003-10-23 at 22:45, othermark wrote:
> I wrote:
> > I will try seeing how far I can go up the list of snapshots until I
> > encounter the first boot -s panic.
>
> Well I walked up the available snapshots and the first panic occurs with
> the snapshot from the 17th of October. Reviewing t
On Tue, 2003-10-21 at 07:59, Terry Lambert wrote:
> Christian Brueffer wrote:
> > > I don't think so. I tried that on my A7M266D with no effect. I believe
> > > something in recent pmap code doesn't like this mobo, or maybe dual
> > > athlons in general. I can run RELENG_5_1 rock solid, and -cur
On Thu, 2003-10-16 at 14:23, Jun Su wrote:
> Seems Tools\makeobjops.awk needs some update.
Sorry about that - I forgot to commit that bit.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, sen
On Fri, 2003-09-12 at 12:46, Johny Mattsson wrote:
> Hi all,
>
> My main FreeBSD box has an Elite/ECS motherboard with the ITE8705
> Environmental Controller/hardware monitor chip, which I'd love to use so
> that I can monitor the system temperature, voltages, and fan speed.
>
> At present (wel
The code in mga_stage.c is externally maintained. Its probably not a
good idea to edit that one.
On Wed, 2003-07-23 at 19:55, Poul-Henning Kamp wrote:
> The following patch are my suggestion (already sent to maintainers)
> for inlines to remove so we can get under the 2000 limit in GCC on
> i386.
On Wednesday 04 June 2003 1:26 pm, Paul Richards wrote:
> On Wed, Jun 04, 2003 at 12:09:00PM +0100, Doug Rabson wrote:
> > On Mon, 2003-06-02 at 21:04, Paul Richards wrote:
> > > On Tue, 2003-06-03 at 18:19, M. Warner Losh wrote:
> > > > Notice how thread 1's
On Thu, 2003-06-05 at 15:51, Paul Richards wrote:
> On Wed, Jun 04, 2003 at 02:43:20PM +0100, Doug Rabson wrote:
> > On Wed, 2003-06-04 at 14:16, Paul Richards wrote:
> > > On Wed, Jun 04, 2003 at 01:33:46PM +0100, Doug Rabson wrote:
> > >
> > > > Inte
On Wed, 2003-06-04 at 14:16, Paul Richards wrote:
> On Wed, Jun 04, 2003 at 01:33:46PM +0100, Doug Rabson wrote:
>
> > Interfaces actually can be added at runtime. Existing objects (i.e.
> > objects instantiated before the new interface was added) will continue
> > to wo
On Wed, 2003-06-04 at 13:24, Paul Richards wrote:
> On Wed, Jun 04, 2003 at 10:01:07AM +0100, Doug Rabson wrote:
> > On Tuesday 03 June 2003 12:00 am, Paul Richards wrote:
> > > On Tue, 2003-06-03 at 23:09, M. Warner Losh wrote:
> > > >
On Mon, 2003-06-02 at 21:04, Paul Richards wrote:
> On Tue, 2003-06-03 at 18:19, M. Warner Losh wrote:
> >
> > Notice how thread 1's _m gets set based on the results of the kobj
> > lookup, and we have a race, even if thread1 and thread2 took out their
> > driver instance locks.
>
> That means we
hod dispatch in kobj
is very slightly slower than a vtable-style array of function pointers
but the difference is barely measurable. Given the behaviour of modern
caches, it is possible to make nearly as many kobj method calls per
second as normal function calls.
--
Doug Rabson
On Saturday 09 November 2002 4:28 pm, Daniel Eischen wrote:
> On Sat, 9 Nov 2002, Doug Rabson wrote:
> > On Friday 08 November 2002 11:13 pm, Daniel Eischen wrote:
> > > On Fri, 8 Nov 2002, M. Warner Losh wrote:
> > > > This is not a fly in the pointment, but rather a
elease, for
the first time ever, which can't run old binaries. Sorry, that isn't
acceptable. The correct and robust way of doing things is to stop
creating binaries (in both 4.x and 5.x) that reference __sF, then wait
a full release cycle for the change to propagate. We can the
having a strict list of explicit
symbol exports, either in the source code using syntax extensions or with a
file supplied to the linker. I'm not sure whether binutils supports this kind
of thing but it would allow us to cut down the set of symbols export
suite either).
> >
> > I lost a filesystem on my current disk a month ago so make sure you
> > use current on another disk.
>
> I compiled kde3 a week or so ago on my laptop running -current and it is
> now my new desktop, so I think reports of kde being totally hose
if (__isthreaded) \
_pthread_cond_signal(m)
+#define cond_broadcast(m) if (__isthreaded) \
+ _pthread_cond_broadcast(m)
#define cond_wait(c, m)if (__isthreaded) \
_pthread_cond_wait(c, m)
--
Doug Rabson
On Thu, 31 Oct 2002, Daniel Eischen wrote:
> On Thu, 31 Oct 2002, Doug Rabson wrote:
> > On Thu, 31 Oct 2002, Daniel Eischen wrote:
> > > I don't see how that can be. _pthread_mutex_lock() in libc_r calls
> > > init_static_private(), not init_static().
>
On Thu, 31 Oct 2002, Daniel Eischen wrote:
> On Thu, 31 Oct 2002, Doug Rabson wrote:
>
> > On Thu, 31 Oct 2002, Daniel Eischen wrote:
> >
> > > On Thu, 31 Oct 2002, Doug Rabson wrote:
> > > > On Thu, 31 Oct 2002, Daniel Eischen wrote:
> > > > >
On Thu, 31 Oct 2002, Daniel Eischen wrote:
> On Thu, 31 Oct 2002, Doug Rabson wrote:
> > On Thu, 31 Oct 2002, Daniel Eischen wrote:
> > > You can also play the libgcc game inside of libc for those applications
> > > or libraries that are too lazy to do it for thems
its needed, it just uses libc's weak versions. Finally,
'Threadplug.so' is loaded which does use threads. This object is linked
with libpthread.so which is now in the list of libs, crucially *after*
libc.so.
After all this loading and runtime linking, the question is how does
libX11
On Thu, 31 Oct 2002, Daniel Eischen wrote:
> On Thu, 31 Oct 2002, Doug Rabson wrote:
>
> > On Thu, 31 Oct 2002, Alexander Kabaev wrote:
> >
> > > On Wed, 30 Oct 2002 22:25:12 -0500 (EST)
> > > Daniel Eischen <[EMAIL PROTECTED]> wrote:
> > >
&g
s in libpthread.so. Linux
doesn't use libXThrStub.so, presumably because libc.so's pthread_* symbols
are suitable stubs.
--
Doug Rabson Mail: [EMAIL PROTECTED]
Phone: +44 20 8348 6160
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Thu, 31 Oct 2002, Doug Rabson wrote:
> On Thu, 31 Oct 2002, Alexander Kabaev wrote:
>
> > On Wed, 30 Oct 2002 22:25:12 -0500 (EST)
> > Daniel Eischen <[EMAIL PROTECTED]> wrote:
> >
> > > > If last weak will win, the normal case when Xthrstub is loa
,8 @@
#define cond_init(c, a, p) _pthread_cond_init(c, a)
#define cond_signal(m) if (__isthreaded) \
_pthread_cond_signal(m)
+#define cond_broadcast(m) if (__isthreaded) \
+ _pthread_cond_broadcast(m)
#define cond_wait(c, m
and libc_r defines a set of strong _pthread_* symbols and a set of weak
pthread_* aliases for them.
It sounds like libc should define weak _pthread_*, and weak pthread_*
aliases for them. Libc_r should define strong _pthread_* symbols and
libc's aliases will then resolve to them. That ought
#x27;t expect anyone to ever run gnome on Solaris but people certainly run
gnome on FreeBSD.
If you can find some other way that pthread calls can be directed reliably
to libc_r even if some random stub library was loaded first, then fine.
Otherwise, it seems that strong definitions for pthread symbo
tanding things. I single stepped through the call to
pthread_setspecific(), watched the linker lookup the symbol and followed
it through into the wrong place (i.e. the stub instead of the real
implementation).
--
Doug Rabson Mail: [EMAIL PROTECTED]
Phone: +44 20 8348 6160
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Wed, 30 Oct 2002, Terry Lambert wrote:
> Doug Rabson wrote:
> > > I think the only sensible solution to this problem is for libraries which
> > > provide an actual pthreads implementation (rather than a set of stubs) to
> > > define strong symbols. Wierd d
On Wed, 30 Oct 2002, Terry Lambert wrote:
> Doug Rabson wrote:
> > > You need to link the library against libc_r.so instead of libXThrStub.so.
> >
> > Probably not. Doing that breaks the existing 'feature' of being able to
> > use X11 in entirely non-thre
On Wed, 30 Oct 2002, Doug Rabson wrote:
> On Wed, 30 Oct 2002, Terry Lambert wrote:
>
> > Doug Rabson wrote:
> > > On Wed, 30 Oct 2002, Terry Lambert wrote:
> > > > Daniel Eischen wrote:
> > > > > Patch looks correct.
> > > >
> >
* approach would
> solve the "oops!" and other foot shooting problems.
Yes please. Our root filesystem space requirements are too high, IMHO.
--
Doug Rabson Mail: [EMAIL PROTECTED]
Phone: +44 20 8348 6160
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Wed, 30 Oct 2002, Terry Lambert wrote:
> Doug Rabson wrote:
> > On Wed, 30 Oct 2002, Terry Lambert wrote:
> > > Daniel Eischen wrote:
> > > > Patch looks correct.
> > >
> > > Please commit? 8-).
> >
> > Well I made a libc with this p
On Wed, 30 Oct 2002, Daniel Eischen wrote:
> On Wed, 30 Oct 2002, Doug Rabson wrote:
>
> > On Wed, 30 Oct 2002, Terry Lambert wrote:
> >
> > > Daniel Eischen wrote:
> > > > > That's bizarre... it's defined in libc_r, so there's no reason f
curs early in the list. Later on stacks of libraries are
loaded dynamically, some of which depend on libc_r.so. Unfortunately
libc_r.so is far too late in the list to get a lookin and it dies in
exactly the same way as before, for the same reason (calling a
non-function
a
> bit exagerated or perhaps dated.
Hmm. I compiled it a few days ago and it was quite broken. It died in
kdeinit very quickly. I will probably retest after sorting out the X
threading problems as I have a hunch this is related.
--
Doug Rabson Mail: [EMAIL PROTECTED]
Phone: +44 20 8348 6160
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Tue, 29 Oct 2002, Terry Lambert wrote:
> Doug Rabson wrote:
> > The point is that with the current setup of the XFree86-4-libraries port,
> > you don't have any choice, since libX11 links to libXThrStub. This is the
> > key problem, IMHO. I have a machine running RedH
On Tue, 29 Oct 2002, Terry Lambert wrote:
> Doug Rabson wrote:
> > The point is that with the current setup of the XFree86-4-libraries port,
> > you don't have any choice, since libX11 links to libXThrStub. This is the
> > key problem, IMHO. I have a machine running RedH
On Tue, 29 Oct 2002, Terry Lambert wrote:
> Doug Rabson wrote:
> > On investigating one of the crashes more carefully, I discovered that all
> > calls to pthread_*() were being resolved to stubs in libXThrStub.so in
> > spite of the fact that libc_r was also loaded. Thi
On Tue, 29 Oct 2002, John Polstra wrote:
> In article <[EMAIL PROTECTED]>,
> Doug Rabson <[EMAIL PROTECTED]> wrote:
> > On Tue, 29 Oct 2002, John Polstra wrote:
> > > When a symbol is defined in multiple libraries, the first library
> > > wins. That
On Tue, 29 Oct 2002, John Polstra wrote:
> In article <[EMAIL PROTECTED]>,
> Doug Rabson <[EMAIL PROTECTED]> wrote:
> > I just spent a few hours trying to get gnome working on one of my systems,
> > since kde still appears to be completely hosed. Unfortunately, not
definition in the list of libs, which in this case is
libXThrStub :-(
--
Doug Rabson Mail: [EMAIL PROTECTED]
Phone: +44 20 8348 6160
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current"
On Wednesday 22 May 2002 6:49 pm, David O'Brien wrote:
> On Wed, May 22, 2002 at 09:57:24AM +0100, Doug Rabson wrote:
> > GDB 5.2 works pretty well with -current - I've been using it recently. I
> > plan to upgrade GDB in -current to 5.2 soon (as soon as David has enough
ports) work instead?
GDB 5.2 works pretty well with -current - I've been using it recently. I plan
to upgrade GDB in -current to 5.2 soon (as soon as David has enough time to
sort out the CVS magic).
--
Doug Rabson Mail: [EMAIL PROTECTED]
ut this commit fixes things.
It hangs on my ia64 diskless box too.
--
Doug Rabson Mail: [EMAIL PROTECTED]
Phone: +44 20 8348 6160
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
gt; :willing to try building RELENG_4 first?
>
> I have successfully built and installed a -stable world. It took all
> day, but it worked :-) Unfortunately, it did not clear up the problem.
>
> I still get this error however:
You must build kern
On Fri, 8 Mar 2002, Matthew Jacob wrote:
>
> And FWIW, alpha kernels on some Uniprocessor boxes freeze up.
I managed to panic my 4-cpu 4100 yesterday with a 'make -j8 buildworld'
I'm going to look at that today.
--
Doug Rabson Ma
re we don't
> have direct access to the hardware. However, according to the psuedo
> code for rti in the Brown book, munging with the saved PSL in
> trapframe to set the IPL should work. Hmm..
I think we can tweak the saved PSL and it should be able to mask
interrupts in the same wa
uess you ought to
use your own copyright here instead of John Birrell's. Come to think of
it, the same thing could be said of alpha/include/reloc.h. Perhaps this
header could be removed entirely if the contents of i386/include/reloc.h
found a better home.
Other than those minor comments, I
a -I/sys and have
> the same tree that gets stuck under /usr/include).
I quite like the fact that the programming interface is
separated from the driver implementation. There is less chance that the
driver writer will expose irrelavent implementation details in the API,
oided at all costs.
>
> BEWARE: there are some snapshots on current.freebsd.org with this bug. They
> will self destruct after install.
Too late - I'm just rebuilding one of my scratch machines right now :-(
--
Doug Rabson
' of your system disk, or get you a console on
> the WC box.
My 4100 was working after the last set of mcpcia fixes. I haven't updated
it for about a week so it may be broken again I guess.
--
Doug Rabson Mail: [EMAIL PROTECTED]
a_init() - this is the
earliest part of the alpha boot sequence. After alpha_init() returns, we
switch to using proc0's stack for the first time (alpha_init() runs on the
bootstrap stack) and call mi_startup() to get the rest of the kernel
going.
--
Doug Rabson Ma
ce. :P Is your mouse a
> serial mouse? There seem to be some problems with input on the sio
> devices.
This is because the schedsofttty() call is commented out so the high-level
interrupt routine in sio is never entered.
--
Doug Rabson Mail: [EMAIL PROTECTED]
No
nel
> after the commit, or should we site tight for a week while the Alpha bits
> are tweaked into working status?
The code should boot - if not, I will follow up with a few cleanup
commits. The next job for the alpha is to overhaul the interrupt code to
support irq threads.
--
Doug Rabson
rk, which is why I'm using the AGP driver.
No idea about this one.
--
Doug Rabson Mail: [EMAIL PROTECTED]
Nonlinear Systems Ltd. Phone: +44 20 8348 3944
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
e supposed to be able to build without crypto ??
Since the random dev is a cryptographically strong PRNG, I think its
reasonable to depend on the crypto kernel bits.
--
Doug Rabson Mail: [EMAIL PROTECTED]
Nonlinear Systems Ltd. Phone: +44 20 8442 9037
--- Maxim Sobolev <[EMAIL PROTECTED]> wrote: > Hi,
>
> I've just found that somebody ported linux agpgart module (used by
> the GXL) to
> FreeBSD. Could someone take a look at it and tell me whether it have
> a chances
> to be imported into base system or I should create a port of it.
>
> http
for FreeBSD which I was going to give you since you have the right
paperwork for submitting stuff to FSF. With those patches, a simple port
would be easy and might make importing it to -current a bit easier.
--
Doug Rabson Mail: [EMAIL PROTECTED]
Nonlinear Systems Ltd
m the next available number.
>
> Also - Peter said something about the "mem" device needing
> to only contain the /dev/mem and /mem/kmem devices, and
> /dev/(random|urandom|null|zero) needing to move to MI areas. I have done
> this, as KLD's. Who wa
On Wed, 10 May 2000, Simon Shapiro wrote:
>
> On 10-May-00 Doug Rabson wrote:
> > On Tue, 9 May 2000, Mike Smith wrote:
> >
> >> > On Tue, May 09, 2000 at 04:27:10PM -0700, Mike Smith wrote:
> >> > > The only answer I've seen for this one is
re you return success from your shutdown method, you must have
> brought your hardware to a quiescent state, ready for immediate loss of
> power. It must not generate any more interrupts or access any more data
> once you have returned.
>
> You can veto your shutdown (by returning
volatility exclusion.
You can suppress the warning if you cast to uintptr_t first. Pretty ugly
though.
--
Doug Rabson Mail: [EMAIL PROTECTED]
Nonlinear Systems Ltd. Phone: +44 20 8442 9037
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
to /var/db/pkg and type 'pkg_delete kde*' a few times. After a
while they all get deleted.
--
Doug Rabson Mail: [EMAIL PROTECTED]
Nonlinear Systems Ltd. Phone: +44 20 8442 9037
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
missed out rl. Basically the part of the
packet which includes headers needs to have the start of the ip header
aligned to a 4-byte boundary. Since the preceding ethernet header is not
padded to 4 bytes, this often means copying the first part of the packet
to another mbuf.
--
Doug Rabson
it
> should just be a function call in all cases.
>
> http://io.yi.org/lock.diff
>
> I will send-pr it if no one has any comments.
It looks quite reasonable to me.
--
Doug Rabson Mail: [EMAIL PROTECTED]
Nonlinear Systems Ltd. Phone: +44 20 8442 9037
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Wed, 26 Apr 2000, Greg Lehey wrote:
> On Tuesday, 25 April 2000 at 9:39:10 +0100, Doug Rabson wrote:
> > On Tue, 25 Apr 2000, Greg Lehey wrote:
> >
> >> On Sunday, 23 April 2000 at 10:07:38 +0100, Doug Rabson wrote:
> >>> On Sun, 23 Apr 2000, Greg Lehey
ls. Having said that, this isn't that slow - I timed a
method call to a two argument function at ~40ns on a 300MHz PII.
I could improve this for some applications (including this one) by
providing a mechanism for an application to cache the function pointer
returned by the method lookup.
--
On Tue, 25 Apr 2000, Greg Lehey wrote:
> On Sunday, 23 April 2000 at 10:07:38 +0100, Doug Rabson wrote:
> > On Sun, 23 Apr 2000, Greg Lehey wrote:
> >
> >> In the last few days, my remote serial gdb has almost completely
> >> stopped working. Previously I had
ct the kinds of work which can be done on 4.x but
I'm convinced that this will improve both the percieved ("I recompiled my
kernel and now it panics on boot - this sucks") and actual stability of
the system.
--
Doug Rabson Mail: [EMAIL PROTECTED]
Nonlinea
ad modules that
> are out-of-date with the kernel?
This sounds quite reasonable. Perhaps you should commit the linux patch to
-current right now and then merge it on Wednesday. That would give plenty
of time for any teething problems to show up.
--
Doug Rabson
coming from?
I noticed this too but I have no idea why. I also had to move back to
9600.
--
Doug Rabson Mail: [EMAIL PROTECTED]
Nonlinear Systems Ltd. Phone: +44 181 442 9037
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe fr
ume
> in the headers it's a volatile __asm).
>
> We can either use an mb() type of thing, or we can declare the structural
> field volatile, or we can cast the access to be volatile.
It also forces the cpu to drain writes and prevents reads from being
re-ordered before the
1 - 100 of 446 matches
Mail list logo
