Can someone please update the examples in /usr/share/examples/kld?
It's a bit confusing when it doesn't even compile.
Stephen
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Sat, Mar 25, 2000 at 01:40:05PM -0700, Warner Losh wrote:
> In message <[EMAIL PROTECTED]> Jeroen Ruigrok van der Werven
>writes:
> : Block/character device collapsing breaking you up now?
> :
> : /dev/ Should only be character devices now.
>
> I was surprised how many block devices were in
smp-patch-06 is now ready.
http://www.backplane.com/FreeBSD4/
http://www.backplane.com/FreeBSD4/smp-patch-06.diff
Bruce, I'd appreciate a quick review of my solution to the AST issue.
Search for 'syscall_ast_exit' in i386/i386/exception.s after patching.
I moved
Hi,
I installed the package for emacs-20.6 on my machine running
FreeBSD-4.0-RELEASE and it core dumps upon issuing the command 'emacs -nw'.
This package was obtained from:
ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/4.0-RELEASE/packages/All/emacs-20.6.tgz
However, it runs f
Brad Knowles wrote:
> When I try to mount my 3.4-STABLE root filesystem on /old, here's
> what I get:
>
> $ mount /old
> mount: /dev/da0s1a on /old: incorrect super block
'fsck -y /dev/da0s1a'
--
"So, the cows were part of a dream that dream
$B!J=>Mh>R2p@)$G9T$C$F$$$?%5!<%S%9$r;n83E*$KEE;R(BDM$B$G$40FFb$7$F$$$^$9!#(B
$B5$/$@$5$$!K(B
$B$"$J$?$N;XDj$7$?=w@-$KBP$7$F0MMj$rIz$;$?$^$^%"%@%k%H%S%G%*=P1i$r8r>D!&;#1F$7(B
$B$^$9!#(B
$BCOJ}$b2D!#7W#3L>$^$GJd7g;XDj$b$G$-$^$9!#;#1F8e$N%^%9%?!<%F!<%W$O$*0zEO$7$7$^(B
$B$9!#(B
$B!|%S
:
:In message <[EMAIL PROTECTED]> Matthew Dillon writes:
:: It's getting clean enough that you can almost understand the interrupt
:: code :-)
:
:Cool. That's one part of the kernel that I've not quite fully
:understood. I always figured there was something I was missing about
:the cod
:Otherwise right now your guess is as good as mine.
:
:As a side note, it seems silly that we do this:
:
:MPLOCKED incl _cnt+V_SYSCALL
:SYSCALL_LOCK
:call_syscall
:
:I think per-cpu statistics would be an interesting optimization,
:since you're testing all of this, have
At 10:18 AM +1000 2000/3/26, Tony Maher wrote:
> No, sd is deprecated.
> AFAIK its da only in 4.0, and only character devices.
> 3.4 has sd compatability and has block devices.
Hmm. Okay, well I note that what's being used right now is
da1s1a through da1s1h, and I had copied these e
> "Kevin" == Kevin Day <[EMAIL PROTECTED]> writes:
[about clock jiggling]
Kevin> Granted, this is an old 4.0-current machine(from around
Kevin> September), but I've seen heavy NFS server load affect the
Kevin> clocks on all three of my NFS servers. The heavier the load,
Kevin> the faste
>
> I'm wondering if the AMI MegaRAID controller/driver might be the
> reason that I'm getting a large number of clock resets from ntpd.
> About every half hour, ntpd seems to feel the need to reset the clock
> on the server by about 1/3 of a second. The server has a moderate NFS
> load (going
I'm wondering if the AMI MegaRAID controller/driver might be the
reason that I'm getting a large number of clock resets from ntpd.
About every half hour, ntpd seems to feel the need to reset the clock
on the server by about 1/3 of a second. The server has a moderate NFS
load (going out through 1
Warner Losh wrote:
>
> In message <[EMAIL PROTECTED]> Jeroen Ruigrok van der Werven
>writes:
> : Block/character device collapsing breaking you up now?
> :
> : /dev/ Should only be character devices now.
>
> I was surprised how many block devices were in my /dev when I did a ls
> -l /dev | grep
On Sat, 25 Mar 2000, Maxim Kolinko wrote:
>
> how to upgrade 2.2.8-STABLE to 4.0-STABLE ?
>
1) Do a binary upgrade. This will be *by far* the easiest for you
2) Upgrade to 3.2-RELEASE, then upgrade to 4.0-STABLE for the 3->4 upgrade
be sure to follow all the steps listed in /usr/src/UPDATING,
* Matthew Dillon <[EMAIL PROTECTED]> [000324 21:52] wrote:
> I've been doing more SMP cleanup and for the life of me I can't figure
> out why cpl operations are surrounded by its own [S]CPL_LOCK ??
>
> As far as I can tell, the cpl is only accessed/modified:
>
> * by mainline c
In message <[EMAIL PROTECTED]> Jeroen Ruigrok van der Werven
writes:
: Block/character device collapsing breaking you up now?
:
: /dev/ Should only be character devices now.
I was surprised how many block devices were in my /dev when I did a ls
-l /dev | grep ^b.
Maybe we should put something
In message <[EMAIL PROTECTED]> Matthew Dillon writes:
: It's getting clean enough that you can almost understand the interrupt
: code :-)
Cool. That's one part of the kernel that I've not quite fully
understood. I always figured there was something I was missing about
the code and why
On Sat, Mar 25, 2000 at 12:11:50PM -0800, Jordan K. Hubbard wrote:
> > I did and created malloc.conf as documented there. And things were
> > fine after that. Wouldn't it be better if the build process created
> > a default /etc/malloc.conf ?
>
> It's purely an optional file; one doesn't need to
In message <[EMAIL PROTECTED]>, Arun Sharma writes:
>On Sat, Mar 25, 2000 at 09:05:18PM +0100, Poul-Henning Kamp wrote:
>> In message <[EMAIL PROTECTED]>, Arun Sharma writes:
>> >On Sat, Mar 25, 2000 at 08:55:16PM +0100, Poul-Henning Kamp wrote:
>> >>
>> >> Please read the malloc(3) manual page.
On Sat, Mar 25, 2000 at 09:05:18PM +0100, Poul-Henning Kamp wrote:
> In message <[EMAIL PROTECTED]>, Arun Sharma writes:
> >On Sat, Mar 25, 2000 at 08:55:16PM +0100, Poul-Henning Kamp wrote:
> >>
> >> Please read the malloc(3) manual page.
> >>
> >
> >I did and created malloc.conf as documented
> Speaking of which, why is /home/ncvs on beast not pointing to
> the current CVS repository? I got bit by the same error after
> doing (what I thought) was a correct `cvs update' on beast.
Sorry, "my bad"; the alpha releases were falling over on some sort of
NFS bogon (and cvs checkouts using
> I did and created malloc.conf as documented there. And things were
> fine after that. Wouldn't it be better if the build process created
> a default /etc/malloc.conf ?
It's purely an optional file; one doesn't need to be installed by
default in order for things to behave as expected. Consider
In article [EMAIL PROTECTED]> you write:
>cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes
>-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual
>-fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include
>-D_KERNEL -include opt_global.h -elf -mno-fp-regs
In message <[EMAIL PROTECTED]>, Arun Sharma writes:
>On Sat, Mar 25, 2000 at 08:55:16PM +0100, Poul-Henning Kamp wrote:
>>
>> Please read the malloc(3) manual page.
>>
>
>I did and created malloc.conf as documented there. And things were
>fine after that. Wouldn't it be better if the build proce
On Sat, Mar 25, 2000 at 08:55:16PM +0100, Poul-Henning Kamp wrote:
>
> Please read the malloc(3) manual page.
>
I did and created malloc.conf as documented there. And things were
fine after that. Wouldn't it be better if the build process created
a default /etc/malloc.conf ?
-Arun
To
Please read the malloc(3) manual page.
In message <[EMAIL PROTECTED]>, Arun Sharma writes:
>After upgrading to 4.0 from source, I had a simple program which called
>malloc core dump on me. After ktrace'ing it and creating /etc/malloc.conf
>it was happier.
>
>But I can't find malloc.conf anywhere
After upgrading to 4.0 from source, I had a simple program which called
malloc core dump on me. After ktrace'ing it and creating /etc/malloc.conf
it was happier.
But I can't find malloc.conf anywhere in /usr/src. How does it get
created during the build ?
-Arun
To Unsubscribe: send mai
Yes, this was broken for several days. I was just getting ready to fix it when
David O'Brien fixed it (after asking Poul who had made the changes causing
it).
On Sat, 25 Mar 2000, Jordan K. Hubbard wrote:
> cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes
>-Wmissing-prot
cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes
-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi
-nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf
-mno-fp-regs -Wa,-mev56 ../../alpha/alpha/clock.c
../
At:
http://www.backplane.com/FreeBSD4/
I haven't fixed the syscall exit checks yet, but that's next on my
list.
-Matt
Matthew Dillon
<[EMAIL PROTECTED]>
> > > Instead, CMSG* should use _ALIGN() and _ALIGN() should be implemented
> > > somewhere that doesn't add any namespace pollution. We currently
> > > use for things like this, but it is already too
> > > overloaded.
>
> > OK, then how about creating machine/align.h?
>
> That approach in gen
-On [2325 16:35], Alexander Langer ([EMAIL PROTECTED]) wrote:
>Thus spake Maxim Kolinko ([EMAIL PROTECTED]):
>
>> how to upgrade 2.2.8-STABLE to 4.0-STABLE ?
>> cd /usr/src; make aout-to-elf-build
>
>upgrade to RELENG_3 first.
Yeah. I recently did a 3.0 -> 3.4 u
Thus spake Maxim Kolinko ([EMAIL PROTECTED]):
> how to upgrade 2.2.8-STABLE to 4.0-STABLE ?
> cd /usr/src; make aout-to-elf-build
upgrade to RELENG_3 first.
Alex
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
-On [2325 03:05], Brad Knowles ([EMAIL PROTECTED]) wrote:
> I gotta be doing something stupid here. I haven't been able to
>access the existing 3.4-STABLE filesystems on this machine since I
>upgraded it to 4.0-STABLE on a second hard drive, and I likewise
>can
how to upgrade 2.2.8-STABLE to 4.0-STABLE ?
cd /usr/src; make aout-to-elf-build
--
>>> stage 3: cross tools
--
cd /usr/src; MAKEOBJDIRPREFIX=/usr/obj/aout/i386/usr/src/ibm-pc
On Sat, 25 Mar 2000, Yoshinobu Inoue wrote:
> > Instead, CMSG* should use _ALIGN() and _ALIGN() should be implemented
> > somewhere that doesn't add any namespace pollution. We currently
> > use for things like this, but it is already too
> > overloaded.
> OK, then how about creating machine/a
> > So I think machine/param.h should be included from
> > sys/socket.h for more portability.
>
> can't be included in any standard header
> (except in ) because it gives massive, undocumented
> namespace pollution. The macro `MACHINE' is especially likely
> to conflict with an application macr
On Sat, 25 Mar 2000, Yoshinobu Inoue wrote:
> ...
> There seems to be no message from bmah related to this, so I
> now add a follow-up here.
>
> The authors' reply is that,
>
> >The X/Open (as well as POSIX I think) man pages for sendmsg()
> >only list socket.h as an include file.
> >The old BS
Thus spake Brad Knowles ([EMAIL PROTECTED]):
> upgraded it to 4.0-STABLE on a second hard drive, and I likewise
> can't access the 4.0-STABLE filesystems from 3.4-STABLE.
If you don't tell us where it fails (and how), we can't help you.
Alex
To Unsubscribe: send mail to [EMAIL PROTECTED]
wi
> Arrgh. Now it seems I might need to reverse my position. I looked
> through some code fragments in UNIX Network Programming (Volume 1,
> Second Edition, pp. 362-365), and there's some precedent for needing
> with the CMSG*() macros.
>
> On the other hand, RFC 2292 and draft-ietf-ipngwg-rfc22
Ah, excellent summary Bruce! Now I know what to look for and test
re: syscall returns. I'm confident I can at least test for the
cases without needing the MP lock, which is all we really need to be
able to optimize the critical path.
I have also successfully removed all the
Bruce wrote:
> On Fri, 24 Mar 2000, Jim Bloom wrote:
>
> > FreeBSD mailing list wrote:
> > >
> > > This patch does indeed fix the writing of floppies. However, fdformat(1)
> > > still fails as follows:
> >
> > That is very strange. My patch only applies to formatting floppies. It
> > did not
-On [2325 08:00], Andrew Sherrod ([EMAIL PROTECTED]) wrote:
>
>My 3.4 machine at work has periodic problems with the
>fxp. No performance issues (perhaps a little slow, but
>the network is congested enough that this is hard to
>measure). However it does periodically display an
> kdm determines X path as 'test -f $PATH/bin/X', so touching X is enough.
^^^ $PATH/X
-- R. Imura
// my private mail address has changed.
// [EMAIL PROTECTED] > [EMAIL PROTECTED] /(-.-)y-~~
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "uns
> * It's because, there are no /usr/X11R6/bin/X in Asami-san's chroot
> * environment, I bet.
>
> Hmm. So kdm looks at the X symlink to decide whether to build with X
> support or not?
>
> I can add that to my X package, but what exactly do I need? Just the
> symlink (to nowhere), or do I ne
45 matches
Mail list logo
