Hi everyone,
I have recently received several pieces of spam mail, apparently sent via
this mailing list. These pieces of mail are the usual spam formula; Your
phone has a virus, Ads, Fake blackmail, so on and so forth.
Has anyone else noticed these spam emails, or is it just me?
Thanks,
Jake
> What about adding a new flag to enable strtoul behavior?
I have had a look at the available flag options for a potential strtoul
flag, and a flag that makes sense to me is [-s] / [--strtoul]. [-s] is not
currently being used in i2c, if we wanted to use it.
On Fri, May 14, 2021 at 5:13 AM Rodney
On Tue, Sep 04, 2018 at 09:49:32PM +0530, Rajesh Kumar wrote:
> Hi Jake,
>
> Please try setting hw.pci.mcfg=0 from the boot loader and see if it helps.
>
> On Tue, Sep 4, 2018 at 2:34 AM Jake Champlin wrote:
>
> > Testing out various BSD's with a Huawei Matebo
Testing out various BSD's with a Huawei Matebook D, and FreeBSD -CURRENT is
failing to boot from an installer image. No serial console, so unable to
grab full boot output, any other info or boot flags that would help would
be awesome.
https://i.imgur.com/WAqwbza.jpg, shows where boot process hangs,
sd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to
"freebsd-current-unsubscr...@freebsd.org"
I hope this is some kind of sick joke... I can't imagine anything
worse.
Jake.
__
On Thursday 02 October 2003 14:54, Chris Jackman wrote:
> Sun E250, running world/kernel from September 18th.
> While running a make buildworld, I get :
>
> panic: pmap_remove_all: illegal for unmanaged/fake page 0x9d2000
Update and build a new kernel. This has been
les.
> An alternative is to type-pun via a union, which is also a bit ugly,
> but explicitly allowed by C99. Patch attached (but only superficially
> tested).
>
> - Thomas
>
...
Using a union sounds fine to me.
Jake
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
gt; boot.flp floppy image (the sparc64/mkisoimages.sh script
> doesn't need it).
boot.flp is actually useful on sparc64 because you can dd it to a disk
from solaris and then boot off it to install. I'm happy with having
the option of not building it if it saves time but please make it
on't scale past 4G. We need people with varying memory
configurations to try it to know what else needs to be tuned.
I'm not sure I can trump Peter, but in any case I've put up the dmesg from
my test machine: http://people.freebsd.org/~jake/tip.pae. The hardware
and probably lots of drivers
depend on this already. It might be better to just remove all bzero-ing
of the softc.
Jake
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
s to me that the only way the function can return -1 is if the
> > list is empty.
>
> And this is consistant with what the code was doing before. This change
> is not a functional change, it's just a necessary update due to API
> changes.
I think he's referring to missing braces around the if which was changed
from 1 statement to 2.
Jake
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
ly since the original
interrupt occured in usermode.
The only locking that's required that I can see is that PS_PROFIL not be
set when the profiling buffer is invalid. But all that will happen is that
attempts to update the profiling buffer will be ignored. Technically the
process should get a
ider this a bug and have removed it in your version).
I see no reason not to just use the pc in the trapframe passed to ast,
even in the case of signals they won't be posted until after addupc_task
is called.
Jake
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
e to p_ucred, so you can access it without
needing any locks. Its potentially updated on each kernel entry.
Jake
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
the
pid as the lock cookie, so it can't distinguish 2 threads from the same
process acquiring a lock.
I noticed that netbsd has fixed this for lwps.
Jake
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Apparently, On Sun, Jan 12, 2003 at 05:09:37AM -0800,
Terry Lambert said words to the effect of;
> Jake Burkholder wrote:
> > > Isn't that really a lame excuse? Shouldn't
> > >
> > > #ifdef __FreeBSD__
> > >
> > > be enough
Apparently, On Sun, Jan 12, 2003 at 12:25:20AM -0800,
Terry Lambert said words to the effect of;
> Jake Burkholder wrote:
> > > Is this an omission, or are the ports wrong?
> >
> > FWIW, the alpha headers are basically identical to the sparc64 ones.
> > Ther
nction `fpsetmask'
> xmrm-2.0_2.log:morphvec.cc:439: `fpsetmask' undeclared (first use this function)
>
> Is this an omission, or are the ports wrong?
FWIW, the alpha headers are basically identical to the sparc64 ones.
There may be missing ifdefs in the ports or the makefiles.
Jake
the size of
the superblock and/or offsets of important fields don't change. This
would give 64 bit people a heads up before they try to boot a broken
kernel, and would make compiling a kernel on one of the reference boxes
more useful for people who don't have a 64 bit machine for runtime
*** Error code 1
FWIW, I can't reproduce this locally, it must be a problem with the
tinderbox. I haven't seen Mike around lately, hopefully he can see
what's going on soon.
Sorry for the spam.
Jake
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
the
>previous definition
> /tinderbox/sparc64/src/sys/boot/sparc64/loader/main.c:110: `zipfs_fsops' undeclared
>here (not in a function)
> /tinderbox/sparc64/src/sys/boot/sparc64/loader/main.c:110: initializer element is
>not constant
> /tinderbox/sparc64/src/sys/boot/sparc64/l
d, since it was
decremented in exit1. The refcnt is incremented before p_flag is tested
for P_WEXIT, the swapout is skipped because its found to be set, and then
vmspace_free is called which decrements the refcnt to 0 and prematurely
frees the vmspace. Decrementing the refcnt in exit1 breaks the normal
refernce count semantics because the vmspace is not being freed then.
Jake
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
olicy
> here.
Agree, I don't see any use in supporting upgrades without going through
4.x-STABLE first.
Jake
>
> Ruslan Ermilov wrote:
> >
> > [
> > current@ Cc:'ed because it'll be useful to a number of upgraders.
> > dougb@ Cc:'ed to be aware
t; what is there in SPARC that should be used instead..?
mp_ncpus is defined in sys/smp.h which is not included kern_thread.c
I don't see why this builds on any platform.
Jake
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
> cat test.c
int
main(void)
{
printf("hello world\n");
}
> cc -static -Wl,-r -o test test.c
> touch hack.c
> cc -shared -o hack.So hack.c
> ld -o test1 test /home/jake/hack.So
> ./test1
hello world
>
Conceivably this would allow dlopen to work on the main progr
Apparently, On Tue, Nov 05, 2002 at 01:21:42PM +0600,
Max Khon said words to the effect of;
> hi, there!
>
> On Tue, Nov 05, 2002 at 02:18:23AM -0500, Jake Burkholder wrote:
>
> > > > Before someone says you can dlopen() from static binaries in order to
&g
place to post the patch and test program
> demonstrating dlopen for statically linked programs?
Put it up somehere on the web or email it to the list. I'd
be interested in looking at it.
Jake
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Apparently, On Tue, Oct 29, 2002 at 08:55:03AM -0500,
Andrew Gallatin said words to the effect of;
>
> David O'Brien writes:
> > On Thu, Oct 24, 2002 at 06:39:15PM -0400, Jake Burkholder wrote:
> > > You can also get various new machines on sun.com for aroun
t mine from paladintech. Ultra 10s
are cheaper but more PC class, my 300mhz does a full buildworld in about
5 hours last time I timed it. Ultra 2 is probably the best value, but
we don't support the builtin scsi controller yet.
You can also get various new machines on sun.com for around $
gt;
semop() leaks memory. An important free() was removed by alfred in
rev 1.55. Try this.
Jake
Index: sysv_sem.c
===
RCS file: /home/ncvs/src/sys/kern/sysv_sem.c,v
retrieving revision 1.55
diff -u -r1.55 sysv_sem.c
--- sysv_sem.
ithout having the trampoline in libc.
> I thought the point of having the trampoline in libc would prevent
> having to create new syscalls...
The point is that the signal trampoline automatically uses the new or
old system calls because its linked with libc. Otherwise you need
a different signal trampoline in the kernel for each version of sigreturn,
and some way to determine the right one. The 0x01ds16 hack only works
for so long.
Jake
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
ach taken. :-) You might have been talking to
Not yet :) Its in my perforce tree still; still some issues to resolve.
I remember Bosko mentioning this though (kse loaning).
Jake
> Bosko (possibly at USENIX ATC), as he was maintaining an i386 lightweight
> interrupt thread implementation (alth
parc64 machine I
> > have access to.
>
> This has got to be a local problem, perhaps where src/contrib/sparc/sparc.c
> is out of sync on the builder machine. This builds fine on
> panther.freebsd.org.
Yeah, I just finished a native world here and have cross built several
sinc
Apparently, On Mon, Sep 02, 2002 at 02:24:08PM +1000,
Bruce Evans said words to the effect of;
> aout support is still required for a few things (mainly for compiling
> some boot blocks), but is broken in gcc3 for at least compile-time
Which boot blocks?
> assignments to long longs and
h certain apps.
I haven't noticed much out of the ordinary, but I don't use the programs
you mention. I would suspect this is a 64bit and/or endian-ness problem
somewhere; someone mentioned a while ago that ncftp doesn't work on
alpha either.
Jake
>
> Par expample ntpd from
ls are probably the common case. But I'd suggest just put
it after the trap code at the end of the file and leave the jump. Its
super aligned so there would probably be a bunch of nops to plow through
anyway.
Jake
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Apparently, On Fri, May 31, 2002 at 05:49:59PM -0700,
Julian Elischer said words to the effect of;
> interesting but not exactly brief.. :-)
>
>
> On Fri, 31 May 2002, Jake Burkholder wrote:
>
> >
> > The system call stubs in libc are leaf functions
Apparently, On Fri, May 31, 2002 at 01:45:50PM -0700,
Julian Elischer said words to the effect of;
>
>
> On Fri, 31 May 2002, Jake Burkholder wrote:
>
> [aweful stuff]
> (always did dislike sparc)
Whatever. It's the most fun architecture I've found to pro
n from the system call on sparc64, due
> > to the way that register stack works. The current test program
> > will not work at all, because setjmp, longjmp cannot be used to
> > switch the stack in the same way.
>
> The library will not be using setjmp and longjmp in this way but
> instead the setcontext() call that dan wrote for the current thread
> library. If that works it should be enough.
> (I'd like to investigate your comments though... can you explain
> more about why it's a problem? It sure simplifies things on most
> architectures I've done this on..
[see above]
It works for simple, stack based architectures. It does not work as
well for anything more complicated. Its best for the upcalls to
need as little state as possible.
Jake
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
sys/kern/subr_trap.c 2002/05/29 07:21:58
> +
> + /*
> + * There is no more work to do and we are going to ride
> + * this thead/KSE up to userland. Make sure the user's
> + * pointer to the t
bug in our pipe ('|', not 'gcc -pipe')
> > implimentation.
>
> I have seen signs of a generic pipe bug in vi: vi's i/o buffer for
> pipes is sometimes invalid (kern/sys_pipe.c:pipe_build_write_buffer()
> gets an error faulting it in). This doesn'
Apparently, On Wed, Apr 03, 2002 at 10:01:36PM +0200,
Poul-Henning Kamp said words to the effect of;
> In message <[EMAIL PROTECTED]>, Ju
> lian Elischer writes:
> >
> >
> >On Wed, 3 Apr 2002, Poul-Henning Kamp wrote:
> >
> >>
> >> >How can I find out which binaries have changed?
> >> >t
> It would be nice... :)
You can do this like at the bottom of syscall and trap, with witness_list().
It'll even print out what the other locks are and where they were acquired.
But yeah, if you're going to access pageable memory in kernel mode you pretty
much have to have no other locks held.
Good work on pipe locking btw.
Jake
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Apparently, On Fri, Mar 08, 2002 at 04:12:47PM -0800,
Terry Lambert said words to the effect of;
> Jake Burkholder wrote:
> > > Will this release include some kind of bootable-install support
> > > for any new hardware platforms, such as sparc64? (this snapshot
to subscribe
to the freebsd-sparc mailing list and be testers for the first semi-official
fresbsd/sparc64 release. .
Jake
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
and has never been stable so an incremental patch
> is not really that necessary for continuity.
>
> :> Insofar as diffs go, I'm afraid even the most conservative changes
> :> to the assembly to support interrupt deferral would make for a pretty
> :> bi
st makes unnecessary diffs. The PUSH_DUMMY
> :macro must push a reasonable eip value, in addition to the code segment,
> :so that profiling and stack traces work right. If you have not already,
> :please make sure that a trace from inside an interrupt handler that was
> :unpended lo
.
> > : 2/ people assumed the patch had gone away.
> >
> > Ummm, There are reviews in the archives that object to the API as it
> > relates to optimization and those objections haven't been sanely
> > answered with anything more constructive than "BS".
&g
because they don't touch memory until the trapframe
> :is written out, so I don't see much point in changing this do the masking
> :in software and avoid the soft interrupt.
>
> I have no idea what you are talking about Jake. Could you supply
> some context?
Sorry
and that it increases latency for the fast
part of the interrupt handler, but they are not able to run in critical
sections anyway due to the software masking.
Jake
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
t out that in all cases that you mention, the original
structure before the "giant pushdown" is being restored. A lot of structural
rewriting occured in those commits. It was not done separately. I don't
recall if the patches were posted for review, I certainly never saw them.
T
quire
giant. I've reviewed what he's got so far and it looks pretty damn good
to me, I'll see about getting him to post it. He's working on adding the
per-cpu queues now.
Jake
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
introduced the leaks
in the first place.
Other than that I don't see anything wrong with this. Commit it.
Jake
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
leep and never be woken up. It
might be better to use type vnode with file or swap based backing
store. sparc64 machines tend to have more ram than older pcs that
this might also be used on :)
my $0.02.
Jake
>
> echo "+++ populate /var using /etc/mtree/BSD.var.dist"
> /
this more and would like you to wait until
> :John has a chance to look at it as well.
> :
> :Jake
>
> Sure thing.
Thanks.
> Ah, critnest... you are right. I should be checking for
> critnest > 1.
I think you should just leave it alone, don't check critnest
ink about this more and would like you to wait until
John has a chance to look at it as well.
Jake
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
'd like to get adiff in relatively soon.
This seems to work fine on sparc64.
Jake
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
in
> machdep.c, shoving it into a global and using that global in locore.s
> The resulting kernel booted.
>
> What's the "right" way to do this?
I think you want lda, its used to load an address constant in support.s:
lda t0, fusufault /* trap fault
'd like to get adiff in relatively soon.
This seems to work fine on sparc64.
Jake
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
in
> machdep.c, shoving it into a global and using that global in locore.s
> The resulting kernel booted.
>
> What's the "right" way to do this?
I think you want lda, its used to load an address constant in support.s:
lda t0, fusufault /* trap fault
bugs. In the NEW_SCHED case,
> the relative weights for each priority are determined by the niceweights[]
> table. kg->kg_estcpu is limited only by INT_MAX and priorities are
> assigned according to relative values of kg->kg_estcpu (code for this is
> not shown). The NEW_SCHED cas
> Why does the mutex not link blocked processes though the
> sleep queue linked list entry? Why does it use the run queue entry?
Because in some cases its necessary for a process to acquire
mutexes while its on the sleep queue. If they used the same
linkage the queues would get corrupted.
> In
I have compiled and installed Xfree86-4.1.0_4 from ports several times with
RELEASE, STABLE and CURRENT. I am using 4.1.0 with Slackware Linux with a
ATI Radeon card on the same machine.It works fine. As I mentioned also there
are some others with this setup who are having the same problems. When
people with this hardware having the same
problem.Is there a fix?.
Thanks
Jake
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
> Hi,
>
> -current from yesterday:
> ---snip---
> (45) root@ttyp0 # idprio 31 /bin/sleep 10
> idprio: idprio: Invalid argument
>
> (46) root@ttyp0 # rtprio 31 /bin/sleep 10
> rtprio: rtprio: Invalid argument
> ---snip---
>
> isdnd is also affected (if you use its rtprio keyword in isdnd.rc).
> On 19 Mar 2001, Dag-Erling Smorgrav wrote:
>
> > Bruce Evans <[EMAIL PROTECTED]> writes:
> > > K6-2's aren't really i586's and i586_bzero should never be used for
> > > them (generic bzero is faster),
> >
> > Wrong. I fixed machdep.c to compute and print the bandwidth correctly:
>
> Wrong you
>
> I built a kernel without the random device and tried to use the
> module. I loaded it from the bootloader and the machine panic'ed on boot:
>
> Mounting root from ufs:/dev/da0a
> da0 at sym0 bus 0 target 0 lun 0
> da0: Fixed Direct Access SCSI-2 device
> da0: 40.000MB/s transfers (20.000
replying to myself again
>
> This is the best workaround I can think of:
>
> Index: kern/kern_intr.c
> ===
> RCS file: /home/ncvs/src/sys/kern/kern_intr.c,v
> retrieving revision 1.47
> diff -u -r1.47 kern_intr.c
> --- kern/ker
== SRUN) {
CTR1(KTR_INTR, __func__ ": setrunqueue %d", p->p_pid);
p->p_stat = SRUN;
setrunqueue(p);
Jake
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
> On Tue, 27 Feb 2001, Jake Burkholder wrote:
>
> > > a distributed.net client (ports/misc/dnetc) being run on -current with
> > > today's kernel just hangs my box. the system _dramatically_ slows
> > > down and stops to respond on any external events (ke
> Hello,
>
> a distributed.net client (ports/misc/dnetc) being run on -current with
> today's kernel just hangs my box. the system _dramatically_ slows
> down and stops to respond on any external events (keyboard, network,
> etc).
>
> d.net client is a daemon, that uses cpu idle (and only idle)
> jake2001/02/26 15:27:35 PST
>
> Modified files:
> sys/kern init_main.c kern_fork.c kern_mutex.c
> Log:
> Initialize native priority to PRI_MAX. It was usually 0 which made a
> process's priority go through the roof when it releas
> On Sun, Feb 25, 2001 at 10:29:42PM -0800, Kris Kennaway wrote:
> > This is on a UP system.
>
> Had another one of these, under the same conditions. Both times I was
> running more(1) on a stdin stream which was generated by a "find |
> grep | more" operation, and I suspended the process with ^
> Julian Elischer wrote:
> >
> > Pete Carah wrote:
> > >
> > > I got a panic today on a fresh kernel...
> > >
> > > Compiled with netgraph but non of the netgraph modules.
> > >
> > > Immediately after the memory probe, a message about sequencers 0-15,
> > > then:
> > > Panic: spinlock ng_worklis
> On Sun, Jan 28, 2001 at 01:27:04AM -0800, Julian Elischer wrote:
> > > This is the single most flagrant lack of cooperation I have experienced
> > > while working with the FreeBSD Project. I'm truly dumbfounded.
> >
> > It's not a lack of co-operation.. it's a lack of communication. I didn't
>
> jake2001/02/11 16:20:08 PST
>
> Modified files:
> sys/alpha/alpha trap.c
> sys/dev/acpica/Osd OsdSchedule.c
> sys/i386/i386genassym.c swtch.s trap.c
> sys/ia64/ia64trap.c
> sys/kern init_main.c ke
> jake2001/02/10 12:33:35 PST
>
> Modified files:
> sys/alpha/alpha trap.c
> sys/i386/i386trap.c
> Log:
> Clear the reschedule flag after finding it set in userret(). This
> used to be in cpu_switch(), but I don't see any di
> jake2001/02/10 11:07:32 PST
>
> Modified files:
> sys/kern kern_synch.c
> Log:
> Acquire sched_lock around need_resched() in roundrobin() to satisfy
> assertions that it is held. Since roundrobin() is a timeout there's
> no
>
> Should it become:
>
> #ifdef SMP
> mtx_lock_spin(&sched_lock);
> need_resched();
> forward_roundrobin();
> mtx_unlock_spin(&sched_lock);
> #else
>
> ?
>
> I cannot test it yet, need to reanimate my testbox first.
You need to handle the UP case as well :) Also, I
calls kthread_exit() which calls exit1()
> which happily MALLOC's with M_WAITOK...
> Something is messed up, indeed, but it seems to be a case of WISIWYG instead
> of what I mean... ;-)
>
>
> Also, I think this issue has been there longer but it might have been masked
>
> Running a kernel I got with this:
>
> >
> > cvs co -D"2001-01-30" src/sys
> >
>
> /ithread.c/1.10/Mon Dec 4 21:15:14 2000//D2001.01.29.23.00.00
>
> I get:
>
> panic: malloc(M_WAITOK) in interrupt context
> Debugger("panic")
> Stopped at Debugger+0x45: pushl %ebx
> db> trace
> Debu
> Update to my previous mail:
>
> trying a PRE_SMPNG kernel doesn't change anything, it still displays
> nothing. I've also updated my /boot/loader and bootblocks.
>
> Still no idea?
Are you running a stripped down kernel? or generic?
There's a problem with kernels that are too large not boot
> Bruce Evans wrote:
> >
> > The new gensetdefs gives unbootable kernels on i386's. They hang before
> > printing anything.
>
> I verified that the output of gensetdefs.pl is identical to that of
> gensetdefs(1). Does the kernel boot if gensetdefs(1) is used?
>
Its not identical here, gensetd
> jake2001/01/11 06:46:26 PST
>
> Modified files:
> sys/alpha/includeglobals.h
> sys/conf files.i386
> sys/i386/i386locore.s
> sys/i386/include asnames.h globals.h
> sys/ia64/include globals.h
> Re
> On Fri, Dec 08, 2000 at 03:37:46AM -0800, Jake Burkholder wrote:
> > >
> > > I cvsuped src , built world and tried to compile a new kernel.
> > > Presently compilation fails with error in ASM line 601 in ../../sys/mutex.h.
> > >
> > > Any ide
>
> I cvsuped src , built world and tried to compile a new kernel.
> Presently compilation fails with error in ASM line 601 in ../../sys/mutex.h.
>
> Any ideas?
>
> (that code seems to be used by i4b sppp routines)
This should be fixed, or at least worked around for a while.
Re-cvsup and try
As usual, you'll have to recompile all libkvm using programs.
Jake
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
> Hi all,
>
> I got following kernel build error.
> When I run 'make includes', the error has gone away.
>
> Why does kernel build process depend on installed system files,
> such as /usr/include?
It shouldn't.
This seems to be primarily aic7xxx, although judging from the output
of 'find /usr/
> In message <[EMAIL PROTECTED]>, Mike Smith writes:
> >> >I objected to a recent commit hiding the fact that this is
> >> >"(elm)->field.sle_next". Anyway, curelm must be a pointer to a struct.
> >> >Not just any struct; the struct must contain a "field" declared using
> >> >SLIST_ENTRY().
> >>
> > > I still think (and am going on record) that this is a REALLY, REALLY
> > > BAD idea.
> >
> > So.. what's the decision? Is this going to be backed out or not?
> > I'd like to know before doing the next update & make world..
>
> We'
>
> Is anyone else having trouble compiling the libpam things, because of
> this? I couldn't compile a kernel because of the the assembler changes,
> so I went to do a buildworld, and now I can't get thru a buildworld. I
> tried the suggestion above (do a make includes) but that didn't seem to
> jake2000/05/23 13:41:02 PDT
> Log:
> Change the way that the queue(3) structures are declared; don't assume that
> the type argument to *_HEAD and *_ENTRY is a struct.
>
> Suggested by: phk
> Reviewed by:phk
> Approved by
oris's suggestion of providing
functions with empty bodies. I worry about optimizing for the static UP
kernel because of introducing more SMP and KLD_MODULE ifdefs, possibly 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 comme
ght method. Eventually this could be a runtime abstraction,
with both up and smp classes compiled into the kernel, and objects initialized
with the right method table at boot time.
I have diffs in the works if anyone is interested.
Jake.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
> ThanksI used that "i" option and it worked...well, almost. I have the files
> I need in /etc/ssh but when I start sshd I get this now.
>
> error: Could not load host key: /etc/ssh/ssh_host_key: No such file or
> directory
If you want to track current you must use mergemaster.
This is
> On Mon, Feb 14, 2000 at 02:39:09PM -0700, Doug Russell wrote:
>
> > Does anyone have a Panasonic 526/563 CD-ROM drive working under 4.0-C? I
> > have not had one working for may weeks, however, I wasn't sure if it was a
> > hardware problem here, or something. 3.4 still finds them, so I beleiv
> I found out what was causing "Can't get device list: Cannot allocate
> memory".. libdevstat mismatch.
>
> Now I'm getting a panic, but hopefully I'll have a decent backtrace
> out of it soon.
I ran into to that too and thought I was screwed, but vinum read worked.
I built the new kernel
rebui
> pcm0: at port 0x220-0x22f irq 5 drq 1 flags 0x15 on
> isa0
>
> If dmesg from sb0 would help I could get it.. Anything else I could help
> with in making "device pcm0" work without params? or is that pnp only?
Yes, that is for pnp-only.
--
we are but packets in the internet of life
To Un
Can we have an entry for mii.ko in /boot/defaults/loader.conf?
##
### Networking drivers #
##
mii_load="NO"
ax_load="NO"# ASIX
Regarding all the trouble people have been having getting their
cards detected with newpcm, I had to make a change to my kernel
config for it to find my soundblaster 16, non-pnp.
this does not detect my card:
device pcm0 at isa? port ? irq 5 drq 1 flags 0x15
this does:
device pcm0 at i
1 - 100 of 119 matches
Mail list logo
