On Wed, Nov 29, 2000 at 09:23:40PM -0500, Andrew Gallatin wrote:
>
> Bernd Walter writes:
> > Just to be clear the values given to lca_read_config were:
> > b=0, s=20, f=0, reg=0, width=4
> > That means b in LCA_CFGOFF is false and the second formular will be applied.
> > The first part is 1<
[ -net and -current BCCed for wider coverage, this is probably best
handled on -arch ]
I would like to request reviews of the zero copy sockets and NFS code I've
been posting about for months:
http://people.FreeBSD.org/~ken/zero_copy
There are diffs posted above against -current as of early Nov
On Wed, 29 Nov 2000, Julian Elischer wrote:
> Bruce Evans wrote:
> >
> > On Thu, 23 Nov 2000, Julian Elischer wrote:
> >
> > > locore.s includes:
> > > #define ALLOCPAGES(foo) \
> > > movlR(physfree), %esi ; \
> > > movl$((foo)*PAGE_SIZE), %eax ; \
> > > addl
Bernd Walter writes:
> On Wed, Nov 29, 2000 at 02:47:54PM -0500, Andrew Gallatin wrote:
> >
> > Bernd Walter writes:
> > >
> > > trap entry = 0x2 (memory management fault)
> > > a0 = 0xfbf1e018
> > > a1 = 0x1
> > > a2 = 0x0
> > >
David O'Brien <[EMAIL PROTECTED]> types:
> On Wed, Nov 29, 2000 at 08:06:14AM +0100, News User wrote:
> > I'm building news machines with two partitions for OSen, to allow
> > me to boot into my choice, where my choice has been FreeBSD-STABLE
> > or FreeBSD-CURRENT to see how the two compare, and
On Wed, Nov 29, 2000 at 02:47:54PM -0500, Andrew Gallatin wrote:
>
> Bernd Walter writes:
> >
> > trap entry = 0x2 (memory management fault)
> > a0 = 0xfbf1e018
> > a1 = 0x1
> > a2 = 0x0
> > pc = 0xfc557a10
> > ra
Bruce Evans wrote:
>
> On Thu, 23 Nov 2000, Julian Elischer wrote:
>
> > locore.s includes:
> > #define ALLOCPAGES(foo) \
> > movlR(physfree), %esi ; \
> > movl$((foo)*PAGE_SIZE), %eax ; \
> > addl%esi, %eax ; \
> > movl%eax, R(physfree) ; \
> >
It's a normal part of PHK malloc, the standard FreeBSD malloc. It's for
turning on certain debugging options. PHK used a cute trick with symlinks to
avoid having to actually open a configuration file. See malloc(3).
Jason Young
Access US Chief Network Engineer
> -Original Message-
> Fro
On Sat, 25 Nov 2000, Kris Kennaway wrote:
> On Sat, Nov 25, 2000 at 10:28:53PM +0100, Leif Neland wrote:
> > Could this be the reason why Avp (virusscanner) for FreeBSD 4X just dumps
> > core on Fbsd current?
> > It works on a Fbsd stable.
>
> Could be malloc.conf defaults. i.e. a bug in avp t
> I'd suggest truss/kdump/etc to try and figure out what avp is doing
> differently on -current then -stable.
>
Is anything obvious here? (If not, I won't persue the matter, but ask
Kaspersky nicely if they can make a Fbsd-5 version.
I know current is not for production; this is my testmachine
On Wed, Nov 29, 2000 at 08:06:14AM +0100, News User wrote:
> I'm building news machines with two partitions for OSen, to allow
> me to boot into my choice, where my choice has been FreeBSD-STABLE
> or FreeBSD-CURRENT to see how the two compare, and if there are any
> significant improvements in -C
On Wed, Nov 29, 2000 at 02:11:00PM +0900, Daniel C. Sobral wrote:
> Ugh. Evil stuff. Are environment variables starting with digits allowed
> in sh(1)?
Nope:
$ 3FOO=yes
3FOO=yes: not found
$ export 3FOO=yes
export: 3FOO: bad variable name
To Unsubscribe: send mail to [EMAIL P
On 29-Nov-00 Andrea Campi wrote:
>> Then when it panics write down the values that get printed out. Next,
>> do 'nm /sys/compile/MYKERNEL/kernel.debug | sort' and look for the function
>> whose address matches the c_func address printed out, then send this info
>> back
>> please. :)
>
> This ti
Bernd Walter writes:
>
> trap entry = 0x2 (memory management fault)
> a0 = 0xfbf1e018
> a1 = 0x1
> a2 = 0x0
> pc = 0xfc557a10
> ra = 0xfc55791c
> curproc= 0xfc62f118
> pid = 0
> Then when it panics write down the values that get printed out. Next,
> do 'nm /sys/compile/MYKERNEL/kernel.debug | sort' and look for the function
> whose address matches the c_func address printed out, then send this info back
> please. :)
This time it took me 1 hour to get the panic, compar
On 29-Nov-00 Sascha Luck wrote:
> Hi,
>
> has anyone got the Lucent Orinoco Gold (11MBit/s) PC-Card working
> with the wi driver in -CURRENT?
>
> I know the Silver and Bronze cards work, but I'm thinking of buying
> the Gold for the 128 bit encryption...
>
> Cheers,
>
> Sascha
I'm sending t
On Wed, Nov 29, 2000 at 05:59:03PM +, Sascha Luck wrote:
> has anyone got the Lucent Orinoco Gold (11MBit/s) PC-Card working
> with the wi driver in -CURRENT?
They work fine.
-- Brooks
--
Any statement of the form "X is the one, true Y" is FALSE.
To Unsubscribe: send mail to [EMAIL PROTE
Marc van Kempen wrote:
>
> > The only gain I see, if you can call it a gain, is that you can get
> > non-trivial information out of a shared object from within scripts, but
> > I don't know if this has been the reason. If you don't allow execution
> > of shared objects, you have to use dlopen(3)
Hi,
has anyone got the Lucent Orinoco Gold (11MBit/s) PC-Card working
with the wi driver in -CURRENT?
I know the Silver and Bronze cards work, but I'm thinking of buying
the Gold for the 128 bit encryption...
Cheers,
Sascha
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe fr
On 29-Nov-00 Gray, David W. wrote:
> Hmmm, I'm specifically talking about when you have MAKEOBJDIRPREFIX set to
> something other than /usr/obj - it *almost* works, but /bin/sh uses files
> generated on-the-fly that get put in the wrong places (in the chroot'ed
> hierarchy). (ONLY when buildin
Hmmm, I'm specifically talking about when you have MAKEOBJDIRPREFIX set to
something other than /usr/obj - it *almost* works, but /bin/sh uses files
generated on-the-fly that get put in the wrong places (in the chroot'ed
hierarchy). (ONLY when building the crunches - makeworld
runs fine.) I sup
On 29-Nov-00 Gray, David W. wrote:
> BTW, is it considered a bug or a feature that you MUST use /usr/obj to
> have make release work? I went in circles for quite a while before figuring
> this out (I just didn't have much room in /usr, so was using the make env
> variable to move the obj tree. I
On 29-Nov-00 Andrea Campi wrote:
>>
>> We want mtxd_file and mtxd_line. If you look at the output of the last
>> command, it will probably look something like this:
>
> ../../kern/kern_timeout.c, line 139
Hmm, and the failed assertion was:
panic: mutex Giant owned at ../../kern/kern_intr.c:2
BTW, is it considered a bug or a feature that you MUST use /usr/obj to
have make release work? I went in circles for quite a while before figuring
this out (I just didn't have much room in /usr, so was using the make env
variable to move the obj tree. It failed in various amusing ways whilst
bui
>
> We want mtxd_file and mtxd_line. If you look at the output of the last
> command, it will probably look something like this:
../../kern/kern_timeout.c, line 139
Hope it helps,
Andrea
--
Andrea Campi mailto:[EMAIL PROTECTED]
I.NET S.p.A.
> "Bruce A. Mah" wrote:
> >
> > If memory serves me right, Marcel Moolenaar wrote:
> >
> > > So, from a pure
> > > ELF layout point of view, both shared objects and executables are the
> > > same. But a shared library is not guaranteed to be executable. Allowing
> > > shared objects to be execut
On Tue, Nov 28, 2000 at 02:30:50PM +0100, Dag-Erling Smorgrav wrote:
> Nicolas Souchu <[EMAIL PROTECTED]> writes:
> > What are kernel mutex? A new mechanism for spl replacement? Is it
> > introduced with the new SMP? I found nothing in the mail archives...
>
> You mean you don't read -committers,
27 matches
Mail list logo
