We have dhcp server in our net, which configures windows clients. Maybe
dhcp requests somehow involved in my panics?
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Yep.
-eric
Forrest Aldrich wrote:
> Interesting point... these ARE new drives that were put in today.
>
> I presume you mean to use the BIOS scsi utility?
>
> _F
>
> At 06:16 PM 3/22/00 -0800, Eric Sabban wrote:
> >Try low-levelling the drives. The behavior sounds similar to what I had a
> >lon
I have a prehistoric version of sysinstall on my otherwise up to date
5.0-Current, and when I used it my system rebooted, so I thought I'd
recompile. Unfortunately 'cd /usr/src/release/sysinstall ; make clean ;
make all' bombed out in kget. More details available on request, but I
thought
According to Daniel C. Sobral:
> Or just pressing space when the countdown message first appears...
No time for that.
--
Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- [EMAIL PROTECTED]
FreeBSD keltia.freenix.fr 4.0-CURRENT #78: Sun Feb 27 15:32:39 CET 2000
To Unsubscribe: send mail to
According to Mike Smith:
> Can you be more specific here - does it reboot _immediately_ after
> printing that message, or after the timeout finishes?
Immediately after printing the message. No timeout whatsoever.
> Try putting just "set autoboot_delay=0" in /boot/loader.rc and see if
> that g
This is one of the things that made us do so badly
in the benchmarks against NT/Linux last year.
OBVIOUSLY one should be able to re-read this infoirmation
without affecting a pending write.
Mike Smith wrote:
>
> > effects of the I/O being in-progress. If a user program doesn't access
> >
On Tue, 21 Mar 2000, Warner Losh wrote:
> : But why there is such a sudden change? Everything worked just fine a week
> : before 5-current.
> No it didn't. I've been seeing panics like this for about two weeks,
Ok, it worked for me.
> but it hadn't been a priority until this week for me. And I
As it just happened to me (*again*), I thought I'd complain
to the powers-that-be.
I'm upgrading my laptop to current. (And on a different subject
"cd /usr/src/release;make release" doesn't build because of
some ports problems...but no big deal.)
I mount the cd (or nfs or whatever), cd to the
In message <[EMAIL PROTECTED]> Doug Barton writes:
: But win95 didn't really fix it, it just covered it up. Filenames in
: Win9x are still 8.3, but the "OS" provides a translation layer that maps
: those 8.3 filenames to long ones. Also, are we sure that fdimage,
: running under DOS can hand
Warner Losh wrote:
>
> In message <[EMAIL PROTECTED]> jack
>writes:
> : Today Warner Losh wrote:
> :
> : > boot.flp288
> :
> : The M$ weenies would probably choke on that since they do
> : filenames other than 8.3 with smoke and mirrors.
>
> 8.3 is so archaic these days we shouldn't be bothered
Kris Kennaway wrote:
>
> On Thu, 23 Mar 2000, Paul Richards wrote:
>
> > > Because the dlopen() of librsaintl.so fails.
> >
> > Ok, I give up :-) Why would that happen then ?
>
> I don't know :-)
>
> > I'm not the only person seeing this, it's been reported on the ports
> > list by someone els
On Thu, 23 Mar 2000, Paul Richards wrote:
> > Because the dlopen() of librsaintl.so fails.
>
> Ok, I give up :-) Why would that happen then ?
I don't know :-)
> I'm not the only person seeing this, it's been reported on the ports
> list by someone else as well.
Hmm, I think I missed this mail
Kris Kennaway wrote:
>
> On Thu, 23 Mar 2000, Paul Richards wrote:
>
> > I'm picking up my secure code from internat so why is modssl trying to
> > use rsaref rather than the international rsa?
>
> Because the dlopen() of librsaintl.so fails.
Ok, I give up :-) Why would that happen then ?
I c
Interesting point... these ARE new drives that were put in today.
I presume you mean to use the BIOS scsi utility?
_F
At 06:16 PM 3/22/00 -0800, Eric Sabban wrote:
>Try low-levelling the drives. The behavior sounds similar to what I had a
>long time ago, low level formatting them fixed the pr
cvsup again. You want to get version 1.134 of sys/vm/swap_pager.c. The fix for
your problem was committed 4.5 hours later.
Good luck trying to compile the kernel. I had hangs while linking the kernel as
well as while trying to install a fixed one. Make sure you have a good backup
of the kerne
On Thu, 23 Mar 2000, Paul Richards wrote:
> I'm picking up my secure code from internat so why is modssl trying to
> use rsaref rather than the international rsa?
Because the dlopen() of librsaintl.so fails.
> Is there a document that explains how all this is supposed to work, I've
> lost track
Try low-levelling the drives. The behavior sounds similar to what I had a long time
ago, low level formatting them fixed the problem.
-eric
Forrest Aldrich wrote:
> Since this is a fairly current issue, I'm posting this appropriately.
>
> I have a DELL server that has hooked up to it a PowerVa
I've posted this to current because it seems to be related to the
OpenSSL code.
Apache-modssl throws out the error below when you try to access a SSL
port. The only place I can find this message is in the
openssl/rsaref/rsaref_stubs.c where it tries to open librsaref.so
I'm picking up my secure
Hi,
> : This is driver for ed(ne2000) cards. I have realtek(rl driver). I took a
> : look at his source and didn't find such strings. There is comment there
> : about cutting off mbuf header before passing it to ether_input - what's
> : this?
>
> I applied a similar patch to the end of the rl pa
On Wed, 22 Mar 2000, Jordan K. Hubbard wrote:
> Winner! Much better than my personal favorite of bigbooty.flp. :-)
Bigboote.
--
| Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD |
| [EMAIL PROTECTED] | 2 x '84 Volvo 245DL| ix86,sparc,pmax |
| http://www.jur
Doug Barton wrote:
>
> What kind of overhead does it add? The warning messages in LINT
> look rather dire to me, but I'm interested in knowing the facts..
If you run current, by all means, use INVARIANTS. You'll find a few
selected persons, some even otherwise respectable, that will tell
"Jordan K. Hubbard" wrote:
>
> Good idea, terrible name. Can't you guys some up with something better? :)
AFAIK, the idea is having the name keeping people away from that file.
--
Daniel C. Sobral(8-DCS)
[EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]
One
:> out.
:>
:> What the write-behind code tries to do is to prevent the buffer cache
:> from being saturated with dirty buffers and to smooth out disk write
:> I/O. It makes the assumption that write-behind data is not typically
:> accessed by the program immediately after b
:Content-Type: text/plain; charset=us-ascii
:
:Matthew Dillon ([EMAIL PROTECTED]) wrote:
:> swap-SPL:
:>
:> Required splvm()'s had to be added to two places in the swap subsystem
:> (but I don't think the lack of these spl's is the cause of the
:> recently reported crashes, th
Hi,
cvsup at Wed Mar 22 04:03:28 GMT 2000, this built without problems with -j8
on my SMP box, but on a uniprocessor (-j4, eveything else the same)
something appears to have deadlocked. The machine is generally OK but the
build has hung and there are 57 cron processes hanging around (ps ax
follow
:On Wed, 22 Mar 2000, Poul-Henning Kamp wrote:
:
:> But it might actually make a lot of sense to make INVARIANTS the
:> default this early in the -CURRENT cycle, protests ?
:
: What kind of overhead does it add? The warning messages in LINT
:look rather dire to me, but I'm interested in kno
On Wed, 2395 Sep 1993, Matthew Dillon wrote:
> It is perfectly ok for dirty blocks to remain in the buffer cache. In
> fact, it's *optimal* to leave them in the buffer cache as long as the
> buffer cache does not get saturated with them. The buffer cache is
> perfectly capable o
:
:> effects of the I/O being in-progress. If a user program doesn't access
:> any of the information it recently wrote the whole mechanism winds up
:> operating asynchronously in the background. If a user program does,
:> then the write behind mechanism breaks down and you get
At 2:50 PM -0500 2000/3/22, Forrest Aldrich wrote:
> da4 at ahc0 bus 0 target 1 lun 0
> da4: Fixed Direct Access SCSI-3 device
> da4: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged
>Queueing Enabled
> da4: 34732MB (71132998 512 byte sectors: 255H 63S/T 4427C)
This just
On Wed, Mar 22, 2000 at 02:08:42PM -0800, Mike Smith wrote:
>
> > Yes, I did, to get into the debugger. Now I wonder, if there is
> > some other bug that I need to chase around, how should I proceed?
>
> You can try looking at the stack further above the atkbd interrupt,
> since that's where it w
Today Warner Losh wrote:
> boot.flp288
The M$ weenies would probably choke on that since they do
filenames other than 8.3 with smoke and mirrors.
--
Jack O'NeillSystems Administrator / Systems Analyst
[E
In message <[EMAIL PROTECTED]> jack
writes:
: Today Warner Losh wrote:
:
: > boot.flp288
:
: The M$ weenies would probably choke on that since they do
: filenames other than 8.3 with smoke and mirrors.
8.3 is so archaic these days we shouldn't be bothered with them. It
hasn't been a real rest
On Wed, Mar 22, 2000 at 05:13:25PM +0100, Martin Cracauer wrote:
> Can you point me to the newest set of ObjC patches for gdb, please?
>
> I don't think they will it into the base system, mainly because it
> takes off files from the vendor branch. But we also have a gdb in
> ports, where patches
On Wed, 22 Mar 2000, Jordan K. Hubbard wrote:
> > kern-144.flp
> > root-144.flp
> > boot-288.flp
>
> Winner! Much better than my personal favorite of bigbooty.flp. :-)
>
> - Jordan
>
Then that would make the CD LordWarfen.iso?
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "uns
Matthew Dillon ([EMAIL PROTECTED]) wrote:
> swap-SPL:
>
> Required splvm()'s had to be added to two places in the swap subsystem
> (but I don't think the lack of these spl's is the cause of the
> recently reported crashes, though it is possible).
There are a few more that I
> Yes, I did, to get into the debugger. Now I wonder, if there is some
> other bug that I need to chase around, how should I proceed?
You can try looking at the stack further above the atkbd interrupt, since
that's where it was running when it took the interrupt. If there's
nothing there, the
boot.flp288
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
In message <[EMAIL PROTECTED]> "Ilmar S.
Habibulin" writes:
: This is driver for ed(ne2000) cards. I have realtek(rl driver). I took a
: look at his source and didn't find such strings. There is comment there
: about cutting off mbuf header before passing it to ether_input - what's
: this?
I app
On Wed, Mar 22, 2000 at 01:52:46PM -0800, Mike Smith wrote:
> >
> > The kernel apparently stopped in atkbd_isa_intr().
>
> No, that's where it went when you hit alt-ctrl-esc.
Yes, I did, to get into the debugger. Now I wonder, if there is some
other bug that I need to chase around, how should
Mike Smith wrote:
>
> > > if you can get a prompt, please.
> >
> > No prompt. It reboots just after displaying the 'Hit [Enter] blah' line.
>
> Can you be more specific here - does it reboot _immediately_ after
> printing that message, or after the timeout finishes?
>
> Try putting just "set au
> kern-144.flp
> root-144.flp
> boot-288.flp
Winner! Much better than my personal favorite of bigbooty.flp. :-)
- Jordan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
> I CVSup'ed 5.0 sources yesterday, and built my kernel this afternoon.
> The kernel built find, and I booted with the new kernel. The uname
> output is:
>
> FreeBSD hades.hell.gr 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Wed Mar 22
> 17:04:49 EET 2000 [EMAIL PROTECTED]:/usr/src/sys/compile/HA
Is someone planning on fixing this?
../../i386/isa/pcvt/pcvt_hdr.h:943: warning: `struct isa_device' declared inside
parameter list
../../i386/isa/pcvt/pcvt_hdr.h:943: warning: its scope is only this definition or
declaration, which is probably not what you want.
../../i386/isa/pcvt/pcvt_hdr.
I CVSup'ed 5.0 sources yesterday, and built my kernel this afternoon.
The kernel built find, and I booted with the new kernel. The uname
output is:
FreeBSD hades.hell.gr 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Wed Mar 22
17:04:49 EET 2000 [EMAIL PROTECTED]:/usr/src/sys/compile/HADES i386
Wh
> > if you can get a prompt, please.
>
> No prompt. It reboots just after displaying the 'Hit [Enter] blah' line.
Can you be more specific here - does it reboot _immediately_ after
printing that message, or after the timeout finishes?
Try putting just "set autoboot_delay=0" in /boot/loader.rc
< said:
> However, I can think of two situations under which it might have to
> be a system call:
I'm fairly certain I found a circumstance which required that it be
available to a system call, but I can't remember quite what it was.
(It was some other system call which could accept a ucontext_t
On Wed, Mar 22, 2000 at 02:48:24PM -0500, Daniel Eischen wrote:
> On Wed, 22 Mar 2000, Arun Sharma wrote:
>
> > On Wed, Mar 22, 2000 at 08:04:37AM -0500, Daniel Eischen wrote:
> > >
> > > I had them implemented and working for i386, and even had a hacked up
> > > libc_r that used them instead of
On Wed, 22 Mar 2000, Poul-Henning Kamp wrote:
> But it might actually make a lot of sense to make INVARIANTS the
> default this early in the -CURRENT cycle, protests ?
What kind of overhead does it add? The warning messages in LINT
look rather dire to me, but I'm interested in knowing th
> effects of the I/O being in-progress. If a user program doesn't access
> any of the information it recently wrote the whole mechanism winds up
> operating asynchronously in the background. If a user program does,
> then the write behind mechanism breaks down and you get a stal
I'm having some troubles with the dc driver and the 21143's. I have
12 ports in a machine (3x 4 port cards). Before I had more than 8 of
them connected, I never had any problems. Now... I find that if I
unplug a cable and then reconnect it, that the driver will not
properly recognise the traffi
Sorry:
da4 at ahc0 bus 0 target 1 lun 0
da4: Fixed Direct Access SCSI-3 device
da4: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled
da4: 34732MB (71132998 512 byte sectors: 255H 63S/T 4427C)
_F
At 02:47 PM 3/22/00 -0500, Bill Fumerola wrote:
>On Wed, Mar 22, 2000
On Wed, 22 Mar 2000, Arun Sharma wrote:
> On Wed, Mar 22, 2000 at 08:04:37AM -0500, Daniel Eischen wrote:
> >
> > I had them implemented and working for i386, and even had a hacked up
> > libc_r that used them instead of setjmp/longjmp. This was a few months
> > ago under 4.0-current. At the t
On Wed, Mar 22, 2000 at 02:42:44PM -0500, Forrest Aldrich wrote:
> Since this is a fairly current issue, I'm posting this appropriately.
>
> I have a DELL server that has hooked up to it a PowerVault, with 8 36gb
> 10krpm LVD drives. The system has recognized these previously and dmesg
> sho
Since this is a fairly current issue, I'm posting this appropriately.
I have a DELL server that has hooked up to it a PowerVault, with 8 36gb 10krpm LVD
drives. The system has recognized these previously and dmesg shows them present;
however, /stand/sysinstall says that I don't have ANY disks
On Wed, 22 Mar 2000, Rasmus Skaarup wrote:
>
> Jordan K. Hubbard said:
> > Good idea, terrible name. Can't you guys some up with something better? :)
>
> kern.flp-> start.flp
> mfsroot.flp -> install.flp
>
> boot.flp-> bigstart.flp
>bigdisk.flp ?
Or Maybe:
kern.144
You could do that, rather easily.
In message <[EMAIL PROTECTED]>, "Mr. K." writes
:
>what would be even cooler is if we could jail() a user natively at
>login. I bet this patch could be easily modified to use jail() instead of
>chroot().
>
>On Wed, 22 Mar 2000, Poul-Henning Kamp wrote:
>
>> In
what would be even cooler is if we could jail() a user natively at
login. I bet this patch could be easily modified to use jail() instead of
chroot().
On Wed, 22 Mar 2000, Poul-Henning Kamp wrote:
> In message <051001bf942c$87e3fa40$[EMAIL PROTECTED]>, "Alejandro Ramirez"
> writes:
> >Hi,
> >
Thanks a lot for clarifying my mind,
I will take a look at this.
Greetings...
Ales
- Original Message -
From: Poul-Henning Kamp <[EMAIL PROTECTED]>
To: Alejandro Ramirez <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Wednesday, March 22, 2000 12:40 PM
Subject: Re: Chrooted telnet
In message <051001bf942c$87e3fa40$[EMAIL PROTECTED]>, "Alejandro Ramirez"
writes:
>Hi,
>
>Will FreeBSD 4.x will be able to chroot telnet sessions natively???, or are
>there any plans to integrate this patches to the base system:
Investigate the jail(8) facility in 4.x, it is *far* stronger than
Hi,
Will FreeBSD 4.x will be able to chroot telnet sessions natively???, or are
there any plans to integrate this patches to the base system:
http://www.o-o.org/~licia/projects/login/
Thanks
Ales
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body o
On Wed, Mar 22, 2000 at 08:04:37AM -0500, Daniel Eischen wrote:
>
> I had them implemented and working for i386, and even had a hacked up
> libc_r that used them instead of setjmp/longjmp. This was a few months
> ago under 4.0-current. At the time, I thought they'd be better off
> implemented a
Grigory Kljuchnikov stated:
> Thank you, Erik!
>
> I find rpc.lockd and start it manually. My test with NFS locking works right.
> But it don't start on boot by default if I enable NFS server in
> /stand/sysinstall and there is the comment in /etc/default/rc.conf
> for rpc_lockd_enable:
>
> rpc_
On Wed, Mar 22, 2000 at 05:51:18PM +0100, Erik Trulsson wrote:
> Somebody who knows what is up with rpc.lockd is welcome to comment.
AFAIK the lockd code just says "Sure - have a lock" to any request.
I think David Cross and some other people have a half working
lockd now, they were looking for
Well, actually these have been partially reviewed over the last few
months, but I'd like to commit them now so I need a final review on
these babies.
The three patches are available at:
http://www.backplane.com/FreeBSD4/
buffer cache cleanup:
This is probabl
On Wed, Mar 22, 2000 at 00:35:19 -0700, Warner Losh wrote:
> In message <[EMAIL PROTECTED]> Soren Schmidt writes:
> : > TEMPC=`camcontrol cmd -v -n da -u 0 -c "4D 0 76 0 0 0 0 0 20 0" -i 32 "s9 i1"`
>
> : Hmm, wonder if one can get that info from their ATA disks as well...
>
> Don't know. Y
I believe the lockd daemon is used in environments where applications at
the client end will not work unless they can make a lock call and get a
positive result.. so in environments where you feel its fairly safe to
fake a lock to a client app, in order to get the app working at all, that
you wou
On Wed, Mar 22, 2000 at 03:46:12PM +0300, Grigory Kljuchnikov wrote:
> Thank you, Erik!
>
> I find rpc.lockd and start it manually. My test with NFS locking works right.
> But it don't start on boot by default if I enable NFS server in
> /stand/sysinstall and there is the comment in /etc/default/
Hai,
In <[EMAIL PROTECTED]>, Mirko Viviani wrote:
> Ciao.
>
> Is it possible to apply the gnu/17433 patch before the 4.0-STABLE ?
>
> Related to this I'm excepting some strange behaviour with prgs linked with libc_r
> under 3.4 and I would like to know if they are also in 4.0.
[please break l
> > With sync it's ~20,000 operations matching the total of reads &
> > writes. This demonstrates another aspect of the bug, sync behaviour
> > should cause 10,000 operations; the reads aren't being cached.
>
> This isn't quite true. It's 20,000 *write* operations. I put this down
> to the mtime
On Wed, 22 Mar 2000, Anne Marcel Roorda was heard blurting out:
> Hi,
>
> It would probably help if you remove the '#' from the card
> definition :)
>
> - marcel
That was a cut and paste error from VIM ;-)
--
---
Ron Rosson
On Tue, 21 Mar 2000, Alex Zepeda was heard blurting out:
> On Tue, 21 Mar 2000, Jordan K. Hubbard wrote:
>
> > Good idea, terrible name. Can't you guys some up with something better? :)
>
> reallybigbootthing.flp?
>
How about:
isoboot.flp
Since it's use is for making bootab
On Tue, Mar 21, 2000 at 10:54:32PM -0800, Arun Sharma wrote:
> > > Before getting too far here, can we consider some other
> > > standard interfaces?
> > > #include
> > > int getcontext(ucontext_t *ucp);
> > > int setcontext(const ucontext_t *ucp);
> > > void makecontex
On Tue, 21 Mar 2000, Arun Sharma wrote:
> On Tue, Sep 07, 1999 at 01:21:59PM +0200, Marcel Moolenaar wrote:
> > Peter Wemm wrote:
> > >
> > > Before getting too far here, can we consider some other standard interfaces?
> > >
> > > #include
> > >
> > > int getcontext(ucontext_t *ucp);
Thank you, Erik!
I find rpc.lockd and start it manually. My test with NFS locking works right.
But it don't start on boot by default if I enable NFS server in
/stand/sysinstall and there is the comment in /etc/default/rc.conf
for rpc_lockd_enable:
rpc_lockd_enable="NO" # Run NFS rpc.loc
According to John Baldwin:
> fixes. Can you see how far into the loader it is getting? Also, what
> is in your /boot/loader.rc. Try booting with an empty loader.rc and see
> if you can get a prompt, please.
Reverting to the version in RELENG_4_0_0_RELEASE fixes the problem.
--
Ollivier ROBERT
Hi,
5-current with last commit to sys/ at 2000/03/20 23:12:17 PST (date
taken from CVSROOT/commitlogs/sys), world and kernel are in sync:
(2) root@ttyp2# gdb -k /sys/compile/WORK/kernel.debug /var/crash/vmcore.1
[...]
IdlePTD 3747840
initial pcb at 2fcae0
panicstr: vm_object_terminate: freeing b
According to John Baldwin:
> fixes. Can you see how far into the loader it is getting? Also, what
> is in your /boot/loader.rc. Try booting with an empty loader.rc and see
loader.rc
-=-=-
\ Loader.rc
\
\ Includes additional commands
include /boot/loader.4th
\ Reads and processes loader.rc
sta
cvsup to 6 hours ago.
Fatal trap 12: page fault while in kernel mode
mp_lock = 0102; cpuid = 1; lapic.id = 0100
fault virtual address = 0x0
fault code = supervisor read, page not present
instruction pointer = 0x8:0xc021ad98
stack pointer = 0x10:0xc87d0d88
fr
On Wed, Mar 22, 2000 at 12:04:55PM +0300, Grigory Kljuchnikov wrote:
> Thierry, thank you for the information,
> but it's very bad that there isn't NFS locking in FreeBSD.
> I'm afraid I need to move my FreeBSD NFS server to Solaris
> for x86.
>
> I don't understand why NFS locking isn't in Fre
On Wed, Mar 22, 2000 at 10:00:27AM +0100, Poul-Henning Kamp wrote:
> A traceback would have been nice.
Sorry, compiled kernel without it.
> I just committed a fix for one such bug, please try with that in place.
Yes, this fixed my problem.
Thanks
To Unsubscribe: send mail to [EMAIL PROTECTE
Thierry, thank you for the information,
but it's very bad that there isn't NFS locking in FreeBSD.
I'm afraid I need to move my FreeBSD NFS server to Solaris
for x86.
I don't understand why NFS locking isn't in FreeBSD.
Is it difficult in the implementation or are there another
global problem
> >Jordan K. Hubbard said:
> >> Good idea, terrible name. Can't you guys some up with something better?
> >kern.flp-> start.flp>>> boot.flp
> >mfsroot.flp -> install.flp >>> initsys.flp
> >
> >boot.flp-> bigstart.flp >>> bootinit.flp
> > bigdisk.flp
A traceback would have been nice.
I just committed a fix for one such bug, please try with that in place.
Poul-Henning
--
Poul-Henning Kamp FreeBSD coreteam member
[EMAIL PROTECTED] "Real hackers run -current on their laptop."
FreeBSD -- It will take a long time befor
Fixed. The swap_pager "knew" that B_WRITE was zero. Not nice.
In message <[EMAIL PROTECTED]>, Peter Wemm writes
:
>Stephen Hocking-Senior Programmer PGS SPS Perth wrote:
>
>This one you need to tell phk about: this is one of his sanity checks
>that trapped and found an insane value. (and then
I am the only one who see this? Brand new kernel
cvsuped few minutes ago. It barfs even on plain
compile. Verbose dmesg output below
Copyright (c) 1992-2000 The FreeBSD Project.
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California. All rights reserved.
Fr
Ciao.
Is it possible to apply the gnu/17433 patch before the 4.0-STABLE ?
Related to this I'm excepting some strange behaviour with prgs linked with libc_r
under 3.4 and I would like to know if they are also in 4.0.
1. In a prg linked with libc I can use a local buffer up to 65 MB, but if the s
-Original Message-
From: Rasmus Skaarup <[EMAIL PROTECTED]>
To: Jordan K. Hubbard <[EMAIL PROTECTED]>
Cc: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Wednesday, March 22, 2000 8:19 AM
Subject: Re: 4.0-RELEASE boot.flp fails to boot on K6/2
>
>Jordan K. Hubbard said:
>> Good idea, terrib
Andrey Sverdlichenko wrote:
>
> > > | One is on the way...
> > >
> > > Cam's boredom out-weighed my initiative. 8)
> > >
> > > http://www.freebsd.org/~cg/current.diff.gz contains a partial emu10k1
> > > driver (minus recording) which is need of debugging. Give it a try!
>
> I applied it to 4.0-
> Once again I'm trying to port Arcnet driver from NetBSD/amiga to
> FreeBSD/i386 (like I did more than a year ago for 3.x). The problem is in
Wow! I might be able to make the Arcnet board in my Tandy 6000 XENIX
machine actually talk to someone someday!?!?!?!? COOL! :)
(Actually, that machin
It seems Warner Losh wrote:
> In message <[EMAIL PROTECTED]> Soren Schmidt writes:
> : > TEMPC=`camcontrol cmd -v -n da -u 0 -c "4D 0 76 0 0 0 0 0 20 0" -i 32 "s9 i1"`
>
> : Hmm, wonder if one can get that info from their ATA disks as well...
>
> Don't know. You'd have to ask IBM. All the
> Date: Tue, 21 Mar 2000 18:00:46 -0500 (EST)
> From: Bill Pechter <[EMAIL PROTECTED]>
> Subject: pstat -s error message
>
> I've done two make worlds and can't seem to get rid of the following
> error... I had it on my home system, but didn't log what I did to
> correct it...
>
> I just upgrade
Jordan K. Hubbard said:
> Good idea, terrible name. Can't you guys some up with something better? :)
kern.flp-> start.flp
mfsroot.flp -> install.flp
boot.flp-> bigstart.flp
bigdisk.flp ?
I thought we could rename kern.flp and mfsroot.flp aswell, since they
their name
> > | One is on the way...
> >
> > Cam's boredom out-weighed my initiative. 8)
> >
> > http://www.freebsd.org/~cg/current.diff.gz contains a partial emu10k1
> > driver (minus recording) which is need of debugging. Give it a try!
I applied it to 4.0-CURRENT, but it works in mixer only mode.
Looks
93 matches
Mail list logo
