>> my vote: A version of the standard keymap with CapsLock and LeftCtl functio
>ns
>> swapped so the control key is under my left finger like God intended!
>
>My vote is both of the above. I've never found a use for CapsLock, but
>LeftCtl is important enough that I wouldn't mind it duplicated.
I wrote:
> Peter Jeremy wrote:
>
> > Mark Blackman wrote:
> > >FWIW, I've done it under 2.2.7 by
> > >
> > >1) installing booteasy on both wd0 *AND* wd2
> > >2) altering the boot.config to
> > > 1:wd(2,a)kernel
> >
> > This works for an a.out 3.0 kernel, but the old bootloader can't handle
>
Matthew Dillon schrieb:
>
> :With NFS v3 there seem still to be some open issues.
> :Im running the latest (4.0)-current with the new vm/NFS changes.
> :While I haven't found any problems with NFSv2 so far, v3 still seems to make
> :trouble.
> :
> :I noticed the error some months ago, while my /us
Hi,
booting into single user mode didn`t remove the splash screen at the
"enter path to shell..." prompt.
FreeBSD 4.0-CURRENT #0: Thu Jan 21
Bye,
Alexander.
--
http://netchild.home.pages.de A.Leidinger @ wurzelausix.cs.uni-sb.de
To Unsubscribe: send mail to majord...@freebsd.org
with "un
Hi,
attached is the source of a test program.
With the CD of my ISDN card it produces:
{0}
(15) netch...@ttyp1 > ./dirtest /cdrom
/cdrom:
.(type: unknown)
.. (type: unknown)
autorun.inf (
On Fri, 22 Jan 1999, Søren Schmidt wrote:
[snip]
> Yep I know, the chipset on the Promise is not initialized to what the
> drives support then, its working in a slow (but always working though)
> mode. I did plan to change this, and even got the docs for the chips
> but it has sunken pretty low o
Previously on Thu, Jan 21, 1999 at 01:53:44PM -0800, Mike Smith wrote:
: > On tuesday I crashed a machine after it ran out of kvm. (dual PII 400 with
: > 768MB RAM) poking about in the code adding:
: >
: > options "VM_KMEM_SIZE=(24*1024*1024)"
: > options "VM_KMEM_SIZE_MAX
On Fri, 22 Jan 1999 12:22:26 +0800, Ying-Chieh Liao wrote:
> you can put this pnp information in /kernel.config
> and, in your /boot/boot.conf, put
>
> load /kernel
> load -t userconfig_script /kernel.config
> boot
Hi chaps,
Try to encourage current users to use /boot/loader.rc instead. We do
> "me too"
>
> -DNOSECURE seems to help but it hasn't completed yet.
>
> julian
me too, but figured the longer strings with the crypt -DNOSECURE makes
must be better :). Anyone know of an easy or possible way to turn a DES crypted
passwd file into the normal libcrypt kind?
---
E-Mail:
having spent almost an hour trying to decode the complexities of the crypt
making process I admit defeat..
can SOMEBODY please fix the build in -current and sent branson
a nice pointy hat..
I think he committed and went on vacation
(I haven't seen any commits that say they fixed this but I'm wait
A new function, kvm_getswapinfo(), has been added to libkvm.
pstat, systat, and top have been updated to use the new function.
-Matt
Matthew Dillon
To Unsubscribe: s
Hi!
Has FreeBSD-3.x a correct implementation of T/TCP?
There is some bug mentioned in Squid FAQ
(http://squid.nlanr.net/Squid/FAQ/FAQ-14.html#ss14.2), about
brokenness of T/TCP in FreeBSD-2.2.2.
Why I'm asking about this, is because I recently read an advice in one
of the FreeBSD mailing lists,
>attached is the source of a test program.
>
>With the CD of my ISDN card it produces:
>
>{0}
>(15) netch...@ttyp1 > ./dirtest /cdrom
>
>/cdrom:
>.(type: unknown)
>.. (type: unknown)
>autorun.inf
On Thu, 21 Jan 1999, David E. Cross wrote:
> I posted this awhile ago to -questions, but never received a reply.
>
> We have a number of FreeBSD NFS servers here. Occasionally we need to
> change the exports list on the servers and send mountd a SIGHUP. This
> leads to a condition that in many
Hi folks,
I have recent sources (cvsup'ed today) and make aout-to-elf broken with:
===> usr.bin/login
cc -pipe -O2 -DCOMPAT_LINUX_THREADS -DVM_STACK -m486 -Wall
-DLOGIN_ACCESS -DLOGALL?? -I/usr/obj/aout/usr/obj/src/tmp/usr/include -c
/usr/obj/src/usr.bin/login/login.c
/usr/obj/src/usr.bin/login/l
On Thu, 21 Jan 1999, Julian Elischer wrote:
>
>
> On Thu, 21 Jan 1999, Richard Seaman, Jr. wrote:
>
> > > And when are COMPAT_LINUX_THREADS and VM_STACK going away?
> >
> > I have no idea. I was hoping that at least COMPAT_LINUX_THREADS
> > would go away before the branch. I don't have commi
I'm having a bit of trouble with 4.0-CURRENT as of last night. After fully
updating my system, on reboot procfs (a KLD module) panics the system as
follows: (more explanation after bt)
#9 0xf01d9c1a in trap (frame={tf_es = 16, tf_ds = 16, tf_edi = -142545460,
tf_esi = -250596864, tf_ebp =
>I've been playing with a Promise FastTrack RAID (IDE) controller with
>3.0-current as of yesterday. Although it is recognised in the PCI bus
>probe as a "Promise Ultra/33" (it has the same vendor/chip ID as the
>non-RAID card), the probes in i386/isa/wd.c fail. I added some debugging
>printfs to
Hello!
My system is too old to have anything other then "Compatable" and
"Bi-directional" modes for the parallel port. Both of this are recognized
as NIBBLE-only by ppc0.
When I try to cp a big file (Wordperfect distribution) onto a Zip
cartridge (with ufs with softupdates) the whole system becom
Attached is a DDB trace that I obtained the next morning after I
posted the original message. FWIW, I've been running without
softupdates now since rebooting after that crash Monday morning,
and everything is running beautifully (albeit a bit more slowly)
:) mounted default.
I hope this can help.
"Kurt D. Zeilenga" wrote:
>"Richard Seaman, Jr." wrote:
>> [lost attribution]
>> > Also, the cc(1) says to use -D_THREADSAFE not -D_THREAD_SAFE.
>> Hmm. Not on my machine. :)
>
>http://www.freebsd.org/cgi/man.cgi?query=cc&apropos=0&sektion=0&manpath=FreeBSD+3.0-current&format=html
This was chan
Sheldon Hearn wrote:
>
> On Fri, 22 Jan 1999 12:22:26 +0800, Ying-Chieh Liao wrote:
>
> > you can put this pnp information in /kernel.config
> > and, in your /boot/boot.conf, put
> >
> > load /kernel
> > load -t userconfig_script /kernel.config
> > boot
>
> Hi chaps,
>
> Try to encourage curren
This may or may not affect you.
Today's installworld broke passwords for me. By that, I mean that login,
xdm, su and friends gave authentication failures on all passwords for
all users that I tried. I suspect this has to do with a hashing
algorithm that isn't backward compatible.
I used Kerberos
On Thu, Jan 21, 1999 at 07:39:28PM -0700, Russell L. Carter wrote:
> d...@tar.com said:
> %libc_r could be modified so that is doesn't replace libc, but rather
> %is an addon, comparable to the kernel threaded libc case. But, it
> %would involve a bit of work.
>
> I thought so at first, but then
Maybe your have switched between hashing modes (DES->MD5 or MD5->DES)?
Because hashing algorithms doesn't changing without a wide notification has
been made. Please check handbook on this subj.
Maxim
Sheldon Hearn wrote:
> This may or may not affect you.
>
> Today's installworld broke passwords
hi, there!
On Fri, 22 Jan 1999, Sheldon Hearn wrote:
> This may or may not affect you.
>
> Today's installworld broke passwords for me. By that, I mean that login,
> xdm, su and friends gave authentication failures on all passwords for
> all users that I tried. I suspect this has to do with a ha
On Thu, Jan 21, 1999 at 12:38:14PM -0600, Richard Seaman, Jr. wrote:
> On Thu, Jan 21, 1999 at 06:12:29PM +0200, Jeremy Lea wrote:
>
> > On Tue, Jan 19, 1999 at 09:11:51AM -0600, Richard Seaman, Jr. wrote:
> > > Actually, the new version, in FreeBSD "ports" form, doesn't require
> > > -DLINUXTHRE
On Fri, 22 Jan 1999 16:51:40 +0200, Maxim Sobolev wrote:
> Maybe your have switched between hashing modes (DES->MD5 or MD5->DES)?
Possibly that's what's happened, but it certainly isn't something I did
deliberately.
> Because hashing algorithms doesn't changing without a wide
> notification ha
> Why I'm asking about this, is because I recently read an advice in one
> of the FreeBSD mailing lists,
> about "Why my dial-up PPP connection from a FreeBSD box is so slow
> comparing with Windows NT
> (about ten times slower)?"
>
> And the advice was (without explanations): "Try to switch off t
On Fri, 22 Jan 1999, Kazutaka YOKOTA wrote:
> Gentlemen, I don't intend to add yet another keymap to
> /usr/share/syscons/keymaps. I am merely trying to define a reasonable
> set of common, consistent key binding for existing keymaps.
>
> National keyboards have different layout of regular keys.
Hi ho !
Someone recommended me a week or so ago, to use the "2 floppy install".
Did so now with a FreeBSD 3.0-SNAP from Jan 21 1999.
No success: my notebook 'sits' beneath me and tells me the following
after inserting the 2nd floppy:
zf_read: fill error
[cpu register contents deleted]
.
On Fri, Jan 22, 1999 at 05:00:52PM +0100, Andreas Klemm wrote:
> Hi ho !
>
> Someone recommended me a week or so ago, to use the "2 floppy install".
> Did so now with a FreeBSD 3.0-SNAP from Jan 21 1999.
> No success: my notebook 'sits' beneath me and tells me the following
> after inserting the 2
On Fri, 22 Jan 1999, Doug Rabson wrote:
> On Thu, 21 Jan 1999, Julian Elischer wrote:
>
> >
> >
> > On Thu, 21 Jan 1999, Richard Seaman, Jr. wrote:
> >
> > > > And when are COMPAT_LINUX_THREADS and VM_STACK going away?
> > >
> > > I have no idea. I was hoping that at least COMPAT_LINUX_THREA
Hi!
I'm experiencing some strange errors with one of our workstations. I
recently moved all of our workstations to 3.0 current as of 1998-12-18.
Does any of this make any sense to anyone:
trumpet:~>rlogin balalaika
netd in free(): warning: junk pointer, too low to make sense.
trumpet:~>telnet bal
On Fri, 22 Jan 1999, Palle Girgensohn wrote:
> Hi!
>
> I'm experiencing some strange errors with one of our workstations. I
> recently moved all of our workstations to 3.0 current as of 1998-12-18.
> Does any of this make any sense to anyone:
>
> trumpet:~>rlogin balalaika
> netd in free(): war
Andreas Klemm wrote:
> On Fri, Jan 22, 1999 at 05:00:52PM +0100, Andreas Klemm wrote:
> > Hi ho !
> >
> > Someone recommended me a week or so ago, to use the "2 floppy install".
> > Did so now with a FreeBSD 3.0-SNAP from Jan 21 1999.
> > No success: my notebook 'sits' beneath me and tells me the
I can no longer bring up my vinum volume with the vinum read
command:
vinum read /dev/wd0s1e /dev/wd2s1f
vinum read /dev/wd0s1e
vinum read /dev/wd2s1f
all come back with
vinum: no drives
I understand that all slices belonging to a volume must
now be passed to read, but that doesn't make any diff
On Thu, Jan 21, 1999 at 02:00:53PM -0800, Kurt D. Zeilenga wrote:
> > For kernel threading you just use libc. Whether or not libc generates
> > thread safe (re-entrant) calls depends on whether its also linked with
> > a library that 1) sets __isthreaded to a non-zero value, 2) has a
> > _spinlo
"Richard Seaman, Jr." wrote:
>
> On Thu, Jan 21, 1999 at 02:00:53PM -0800, Kurt D. Zeilenga wrote:
>
> > > For kernel threading you just use libc. Whether or not libc generates
> > > thread safe (re-entrant) calls depends on whether its also linked with
> > > a library that 1) sets __isthreaded
On Fri, 22 Jan 1999, Mikhail Teterin wrote:
> Hello!
>
> My system is too old to have anything other then "Compatable" and
> "Bi-directional" modes for the parallel port. Both of this are recognized
> as NIBBLE-only by ppc0.
>
> When I try to cp a big file (Wordperfect distribution) onto a Zip
>
-BEGIN PGP SIGNED MESSAGE-
I hope this is the right list...
I'm having some problems building 3.0 stable on a 3.0-19990105-SNAP machine.
I've tried blowing away /usr/src and checking it back out again to no avail.
Buildworld always dies with this error:
install -c -o root -g wheel -m 4
On Thu, 21 Jan 1999, Warner Losh wrote:
> In message
> Andrzej Bialecki writes:
> : I'm more than willing to test it in low memory conditions.. :-) I have
> : that special 386SX/4MB RAM machine in the corner to test things like
> : picobsd memory requirements...
>
> So how well does this work?
On Fri, Jan 22, 1999 at 09:49:23AM -0800, Kurt D. Zeilenga wrote:
> "Richard Seaman, Jr." wrote:
> > _THREAD_SAFE is only used in stdio.h. Looking at what's there, it could
> > be rewritten to eliminate _THREAD_SAFE entirely, at a (very slight)
> > performance penalty. You'd have to check __isthr
In article <199901211425.iaa33...@friley-184-92.res.iastate.edu>,
Patrick Hartling wrote:
> It appears that revision 1.9 of lib/libpam/modules/pam_kerberosIV/klogin.c
> and revision 1.3 of lib/libpam/modules/pam_kerberosIV/pam_kerberosIV.c
> broke ftpd when compiling with MAKE_KERBEROS defined.
"Richard Seaman, Jr." wrote:
>
> On Fri, Jan 22, 1999 at 09:49:23AM -0800, Kurt D. Zeilenga wrote:
> > "Richard Seaman, Jr." wrote:
> > > _THREAD_SAFE is only used in stdio.h. Looking at what's there, it could
> > > be rewritten to eliminate _THREAD_SAFE entirely, at a (very slight)
> > > perform
On Fri, 22 Jan 1999, Palle Girgensohn wrote:
> I'm experiencing some strange errors with one of our workstations. I
> recently moved all of our workstations to 3.0 current as of 1998-12-18.
> Does any of this make any sense to anyone:
>
> trumpet:~>rlogin balalaika
> netd in free(): warning: junk
In article <36a867ed.8adac...@altavista.net>,
Maxim Sobolev wrote:
>
> -o login login.o login_access.o login_fbtab.o -lutil -lcrypt
> login.o: Undefined symbol `_pam_start' referenced from text segment
...
I merged the fix into RELENG_3 this morning. Sorry about that!
John
--
John Polstra
#define quoting(Jordan K. Hubbard)
// All: Sorry the boot.flp has been broken for this long, but I've had
// other distractions lately. I will make it work once more, somehow
// or other, and just keep your eyes on current.freebsd.org over
// the next few days. When it returns to 1.44MB in size a
OK, in retrospect, turning off swapping was a mistake. I should have
thought about this a bit more before blindly accepting the suggestion
from Andrzej. ;) Fixed.
- Jordan
> #define quoting(Jordan K. Hubbard)
> // All: Sorry the boot.flp has been broken for this long, but I've had
> // other di
|Maybe having just one pthread.h that pulls in the required headers
|based on a switch (eg. -DLINUXTHREADS) is the way to go?
Doing this makes linuxthread support more or less "official", I would
think.
I am for it.
Russell
|
|--
|Richard Seamman, Jr. email: d...@tar.com
|5182 N. Map
> -Original Message-
> From: Sheldon Hearn [mailto:a...@iafrica.com]
> Sent: Friday, January 22, 1999 3:17 PM
> To: Maxim Sobolev
> Cc: curr...@freebsd.org
> Subject: Re: WARNING: Today's current breaks passwords
>
>
>
>
> On Fri, 22 Jan 1999 16:51:40 +0200, Maxim Sobolev wrote:
>
> >
In message <36a85ef1.444a...@urc.ac.ru> you write:
>Why I'm asking about this, is because I recently read an advice in one
>of the FreeBSD mailing lists,
>about "Why my dial-up PPP connection from a FreeBSD box is so slow
>comparing with Windows NT
>(about ten times slower)?"
>
>And the advice was
On Fri, 22 Jan 1999, Russell L. Carter wrote:
> |Maybe having just one pthread.h that pulls in the required headers
> |based on a switch (eg. -DLINUXTHREADS) is the way to go?
>
> Doing this makes linuxthread support more or less "official", I would
> think.
>
> I am for it.
*confused look*
s
> -Original Message-
> From: John Fieber [mailto:jfie...@indiana.edu]
> Sent: Friday, January 22, 1999 3:51 PM
> To: Kazutaka YOKOTA
> Cc: curr...@freebsd.org
> Subject: Re: keymaps
>
>
> On Fri, 22 Jan 1999, Kazutaka YOKOTA wrote:
>
> > Gentlemen, I don't intend to add yet another keym
On Fri, Jan 22, 1999 at 02:47:53PM -0500, Alfred Perlstein wrote:
> *confused look*
>
> somehow even though i've been trying to follow this thread i got lost.
>
> questions:
> 1) are 'linuxthreads' enabled by defualt now?
The terminology is a little confusing. There's "linuxthreads" for those
> having spent almost an hour trying to decode the complexities of the crypt
> making process I admit defeat..
> can SOMEBODY please fix the build in -current and sent branson
> a nice pointy hat..
> I think he committed and went on vacation
>
> (I haven't seen any commits that say they fixed this
On Fri, 22 Jan 1999, Richard Seaman, Jr. wrote:
> > *confused look*
> >
> > somehow even though i've been trying to follow this thread i got lost.
> >
> > questions:
> > 1) are 'linuxthreads' enabled by defualt now?
>
> The terminology is a little confusing. There's "linuxthreads" for those
>
Luoqi Chen wrote:
> I spend half night yesterday to sort this mess out. If no one objects,
> I'll commit my fixes. (anyone volunteers to make the hat?)
I know who gets the hat; please cool it on the fixes until the original
committer has finished.
I'm watching this one closely, and I need to trac
In message <1999012216.a2...@terry.dragon2.net>, Ying-Chieh Liao
writes
>On Thu, Jan 21, 1999 at 23:03:45 +, Tim wrote:
>> How do I set up the CSN now as I get CSN 1 disabled and CSN 2 disabled
>> on boot.
>
>you can put this pnp information in /kernel.config
>and, in your /boot/boot.conf,
>On Wed, Jan 20, 1999 at 05:58:01PM +0100, Dag-Erling Smorgrav wrote:
>> Mike Nguyen writes:
>> consolidating all that config information in one place, such as
>> /etc/rc.conf, would be a good thing.
>
>Agreed, it really isn't such a good idea to clutter /etc/ with all
>those single line configura
On Friday, 22 January 1999 at 9:23:48 -0800, Jake wrote:
> I can no longer bring up my vinum volume with the vinum read
> command:
>
> vinum read /dev/wd0s1e /dev/wd2s1f
> vinum read /dev/wd0s1e
> vinum read /dev/wd2s1f
>
> all come back with
> vinum: no drives
Correct. As I explained in detail
As Joao Carlos Mendes Luis wrote...
> #define quoting(Jordan K. Hubbard)
> // All: Sorry the boot.flp has been broken for this long, but I've had
> // other distractions lately. I will make it work once more, somehow
> // or other, and just keep your eyes on current.freebsd.org over
> // the next
Greg Lehey wrote:
> On Friday, 22 January 1999 at 9:23:48 -0800, Jake wrote:
> > I can no longer bring up my vinum volume with the vinum read
> > command:
> >
> > vinum read /dev/wd0s1e /dev/wd2s1f
> > vinum read /dev/wd0s1e
> > vinum read /dev/wd2s1f
> >
> > all come back with
> > vinum: no drive
On Saturday, 23 January 1999 at 6:24:17 +0800, Peter Wemm wrote:
> Greg Lehey wrote:
>> On Friday, 22 January 1999 at 9:23:48 -0800, Jake wrote:
>>> I can no longer bring up my vinum volume with the vinum read
>>> command:
>>>
>>> vinum read /dev/wd0s1e /dev/wd2s1f
>>> vinum read /dev/wd0s1e
>>>
Hey guys!
After all these commits for secure/lib/libcrypt it seems that
make world doesn't work anymore.
===> csu/i386-elf
===> libcom_err
===> libcom_err/doc
===> ../secure/lib/libcrypt
cc -nostdinc -O -pipe -I/usr/src/secure/lib/libcrypt/../../../lib/libmd -Wall
-I/usr/obj/usr/src/tmp/usr/inclu
Greg Lehey wrote:
> On Saturday, 23 January 1999 at 6:24:17 +0800, Peter Wemm wrote:
> > Greg Lehey wrote:
> >> On Friday, 22 January 1999 at 9:23:48 -0800, Jake wrote:
> >>> I can no longer bring up my vinum volume with the vinum read
> >>> command:
> >>>
> >>> vinum read /dev/wd0s1e /dev/wd2s1f
On Saturday, 23 January 1999 at 7:10:08 +0800, Peter Wemm wrote:
> Greg Lehey wrote:
>> On Saturday, 23 January 1999 at 6:24:17 +0800, Peter Wemm wrote:
>>> Greg Lehey wrote:
On Friday, 22 January 1999 at 9:23:48 -0800, Jake wrote:
> I can no longer bring up my vinum volume with the vin
Mark,
can you announce when the fixes are in place?
thanks,
julian
On Fri, 22 Jan 1999, Mark Murray wrote:
> Luoqi Chen wrote:
> > I spend half night yesterday to sort this mess out. If no one objects,
> > I'll commit my fixes. (anyone volunteers to make the hat?)
>
> I know who gets the hat;
> make: don't know how to make crypt-md5.c. Stop
Me three. I was looking forward to testing all the VM improvements,
but have been stuck because of this. I've watched the cvs-all list
and haven't seen a mention of this being fixed.
--
Brian Litzinger
On Fri, Jan 22, 1999 at 02:54:08PM -0800
On Fri, 22 Jan 1999, Matthew Dillon wrote:
> A new function, kvm_getswapinfo(), has been added to libkvm.
>
> pstat, systat, and top have been updated to use the new function.
>
> -Matt
>
> Matthew Dillon
>
> Luoqi Chen wrote:
> > I spend half night yesterday to sort this mess out. If no one objects,
> > I'll commit my fixes. (anyone volunteers to make the hat?)
>
> I know who gets the hat; please cool it on the fixes until the original
> committer has finished.
>
> I'm watching this one closely, an
On Fri, 22 Jan 1999, Jordan K. Hubbard wrote:
> OK, in retrospect, turning off swapping was a mistake. I should have
> thought about this a bit more before blindly accepting the suggestion
> from Andrzej. ;) Fixed.
Oh well.. It made sense for me, I just thought it might help to save some
space.
On Fri, 22 Jan 1999, Matthew Dillon wrote:
> A new function, kvm_getswapinfo(), has been added to libkvm.
>
> pstat, systat, and top have been updated to use the new function.
Have you considered using sysctl(3) for this instead? If yes, could you
explain why the libkvm seemed better to
so what happenned..
he checked in more stuff this morning and DIDN'T fix the build breakage
from yesterday..
doesn't he know about it?
On Fri, 22 Jan 1999, Mark Murray wrote:
> Luoqi Chen wrote:
> > I spend half night yesterday to sort this mess out. If no one objects,
> > I'll commit my fixes.
On Fri, 22 Jan 1999, Brian Feldman wrote:
> On Fri, 22 Jan 1999, Doug Rabson wrote:
>
> > On Thu, 21 Jan 1999, Julian Elischer wrote:
> >
> > >
> > >
> > > On Thu, 21 Jan 1999, Richard Seaman, Jr. wrote:
> > >
> > > > > And when are COMPAT_LINUX_THREADS and VM_STACK going away?
> > > >
> > >
<
said:
> Where's struct kvm_swap and typedef struct kvm_swap *kvm_swap_t supposed to
> now be?
Hopefully the latter isn't anywhere, since style(9) says very
specifically that such typedefs are Not To Be Introduced.
-GAWollman
--
Garrett A. Wollman | O Siem / We are all family / O Siem / We'
On Fri, 22 Jan 1999, Garrett Wollman wrote:
> < said:
>
> > Where's struct kvm_swap and typedef struct kvm_swap *kvm_swap_t supposed to
> > now be?
>
> Hopefully the latter isn't anywhere, since style(9) says very
> specifically that such typedefs are Not To Be Introduced.
This doesn't change
Dual p5-90 w/ 48M ram, doing a major cvs update/merge (which mostly got
lost):
panic: found dirty cache page 0xf046f1c0
mp_lock = 0101; cpuid = 1; lapic.id = 0100
Debugger("panic")
Stopped at Debugger+0x37: movl$0,in_Debugger
db> trace
Debugger(f01f1806) at Debugger+0x37
panic(f
At 10:34 AM 1/23/99 +0800, Peter Wemm wrote:
>Dual p5-90 w/ 48M ram, doing a major cvs update/merge (which mostly got
>lost):
>
>panic: found dirty cache page 0xf046f1c0
>mp_lock = 0101; cpuid = 1; lapic.id = 0100
>Debugger("panic")
>Stopped at Debugger+0x37: movl$0,in_Debugger
>
Tim wrote:
>
> >and, in your /boot/loader.rc, put
> >
> >load /kernel
> >load -t userconfig_script /kernel.config
>
> Thanks for the info but unfortunately this has not worked, maybe this is
> the syntax I have used in the /kernel.config file
>
> pnp 1 enable os irq0 11 port0 0x3e8
>
> used to
Peter Wemm wrote:
> Dual p5-90 w/ 48M ram, doing a major cvs update/merge (which mostly got
> lost):
>
> panic: found dirty cache page 0xf046f1c0
> mp_lock = 0101; cpuid = 1; lapic.id = 0100
> Debugger("panic")
> Stopped at Debugger+0x37: movl$0,in_Debugger
> db> trace
This is
:Peter Wemm wrote:
:> Dual p5-90 w/ 48M ram, doing a major cvs update/merge (which mostly got
:> lost):
:>
:> panic: found dirty cache page 0xf046f1c0
:...
:
:This is possibly a false alarm.. Something wierd was happening. I cleaned
:out the kernel and reconfigured with NFS static (it was being
:On Fri, 22 Jan 1999, Matthew Dillon wrote:
:
:> A new function, kvm_getswapinfo(), has been added to libkvm.
:>
:> pstat, systat, and top have been updated to use the new function.
:
:Have you considered using sysctl(3) for this instead? If yes, could you
:explain why the libkvm seemed b
:At 10:34 AM 1/23/99 +0800, Peter Wemm wrote:
:>Dual p5-90 w/ 48M ram, doing a major cvs update/merge (which mostly got
:>lost):
:>
:>panic: found dirty cache page 0xf046f1c0
:>mp_lock = 0101; cpuid = 1; lapic.id = 0100
:...
:I just got the same thing doing a make -j8 world
:Machine is a
On Fri, 22 Jan 1999, Manfred Antar wrote:
> At 10:34 AM 1/23/99 +0800, Peter Wemm wrote:
> >Dual p5-90 w/ 48M ram, doing a major cvs update/merge (which mostly got
> >lost):
> >
> >panic: found dirty cache page 0xf046f1c0
> >mp_lock = 0101; cpuid = 1; lapic.id = 0100
> >Debugger("panic")
All because of a makefile snaffoo..
luoqi has a patch to fix it, but if anyone knows what
the author was trying to achieve, can they please try fixing it?
julian
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
In article <199901210732.saa09...@lightning.itga.com.au>,
Gregory Bond wrote:
> Now we've gone and got forked, can someone please give us examples of cvsup
> files for those that want to follow 4-current and those that want to follow
> 3-stable.
To track -current, the cvsupfile should contain
Matthew Dillon wrote:
> :Peter Wemm wrote:
> :> Dual p5-90 w/ 48M ram, doing a major cvs update/merge (which mostly got
> :> lost):
> :>
> :> panic: found dirty cache page 0xf046f1c0
> :...
> :
> :This is possibly a false alarm.. Something wierd was happening. I cleaned
> :out the kernel and re
I tried both cam and bio -- no difference. It is not that it's
slow -- I was prepared for that, it is that it totally hangs --
forever.
I narrowed it down to softupdates. If I disable the softupdates on
the cartridge's filesystem copying finishes successfully. Somehow
the `cp' process takes 150% o
Julian Elischer wrote:
> All because of a makefile snaffoo..
> luoqi has a patch to fix it, but if anyone knows what
> the author was trying to achieve, can they please try fixing it?
>
brandon and markm seem to have vanished. Please, commit
luoqi's patch. You have commit privilege.
--
Steve
Is this code included, or must it be patched in?
Is softupdates enabled by default or do I have to use a special
mount flag?
Thanks,
Joe
Joe McGuckin
ViaNet Communications
1235 Pear Ave, Suite 107
Mountain View, CA 90403
Phone: 650-969-2203
Cell: 415-710-4894
Fax: 650-969-2124
To Unsu
On Fri, 22 Jan 1999, Joe McGuckin wrote:
> Is this code included, or must it be patched in?
Because of licensing issues, you have to enable it yourself. See the
instructions in /sys/ufs/ffs/README.softupdates for how to do this.
> Is softupdates enabled by default or do I have to use a special
Steve Kargl wrote:
> Julian Elischer wrote:
> > All because of a makefile snaffoo..
> > luoqi has a patch to fix it, but if anyone knows what
> > the author was trying to achieve, can they please try fixing it?
> >
>
> brandon and markm seem to have vanished. Please, commit
> luoqi's patch. Yo
I ran into an interesting problem in the process of modifying
"netstat" to understand the PF_NETGRAPH protocol family. "netstat"
uses kvm_read(), etc. to read kernel symbols. However, this doesn't
work when the symbols you're looking for are in an KLD module (eg,
ng_socket.ko) -- the symbol will no
94 matches
Mail list logo
