Sorry. Off topic but need help.

[Bob Martin]

While trying to upgrade a 3.3-Stable box to 4.2-Release, we crashed
during the upgrade. After restoring the system from tape, password no
longer work.

We've tried killing all files except master.passwd and regenerating with
pwd_mkdb, but that didn't work.

Any help would be greatly appreciated.

Bob Martin
-- 
As far as the laws of mathematics refer to reality, they are not
certain, and as far as they are certain, they do not refer to reality.
-- Albert Einstein

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

rpc.statd hangs on boot.

[Bob Martin]

Using current cvsup'd the morning of 8/29, I discovered that rpc.statd
doesn't fork on boot up. I don't know if it's in the rpc.statd code, or
in the new version of rc.network I installed with mergemaster. 

I've worked around this by adding an ampersand to the boot command in
rc.network. 

Is this just something with my system? A new make world with the same
sources didn't solve the problem.

Bob Martin
-- 
As far as the laws of mathematics refer to reality, they are not
certain, and as far as they are certain, they do not refer to reality.
-- Albert Einstein


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Internal compiler error: program ld got fatal signal 10

[Bob Martin]

Steve Kargl wrote:
 
 First, the error message:
 
 cc -fpic -DPIC -I/usr/src/lib/libmd -DSHA1_ASM -DELF -DRMD160_ASM -DELF 
-I/usr/obj/usr/src/i386/usr/include  -c /usr/src/lib/libmd/i386/rmd160.S -o rmd160.So
 building shared library libmd.so.2
 cc: Internal compiler error: program ld got fatal signal 10
 *** Error code 1
 
 Stop in /usr/src/lib/libmd.
 *** Error code 1
 
 Now, the details.  I started on Monday trying to update
 a 15 March 00 -current to current -current.  I get the
 above error message with a source tree after
 
 *default date=2000.05.23.00.00.00
 
 as specified in my cvsup supfile.  The system builds fine
 for all earlier dates that I've tried.  I have used the
 following three CFLAGS as set in /etc/make.conf
 
 CFLAGS=
 CFLAGS=-O -pipe
 CFLAGS=-O2 -pipe
 
 and the above error occurs.
 
 Any and all suggestions are welcomed, but it appears to be
 a problem with the new binutils.
 
 --
 Steve
 
 To Unsubscribe: send mail to [EMAIL PROTECTED]
 with "unsubscribe freebsd-current" in the body of the message
If you are using an older K6 with more than 32mb of ram, this will
happen from time to time of it's own accord. I have never taken the time
to find out why, but if you search the archives, you will find that it
happens quite a bit.

Bob
-- 
"I know not with what weapons World War III will be fought,
but World War IV will be fought with sticks and stones."
-- Albert Einstein


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

PCM and Midi.

[Bob Martin]

Does anyone know when PCM will support midi?

Thanks!
Bob
-- 
"I know not with what weapons World War III will be fought,
but World War IV will be fought with sticks and stones."
-- Albert Einstein


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: current errors

[Bob Martin]

Garrett Wollman wrote:
 
 On Tue, 18 Apr 2000 13:37:21 -0400, Ted Sikora [EMAIL PROTECTED] said:
 
  Any ideas as to the cause of the following errors in current.
 
 Harmless.

Not totally harmless. PNPBIOS is causing a conflict, which is causing a
kernel panic on my system. Since I haven't had a chance to track it
down, I can't be more specific. 

More over, I don't think that device PCM should automaticly enable
PNPBIOS.

Bob Martin


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: current errors

[Bob Martin]

Warner Losh wrote:
 
 In message [EMAIL PROTECTED] Bob Martin writes:
 : Not totally harmless. PNPBIOS is causing a conflict, which is causing a
 : kernel panic on my system. Since I haven't had a chance to track it
 : down, I can't be more specific.
 
 PNPBIOS isn't causing the conflict.  It is merely allowing us to
 detect the conflict.  PNPBIOS just reads a table from the BIOS of
 devices that are hard wired.
 
Confict or not, my system boots and runs flawlessly without PNPBIOS. It
kernel panics with it. (At the moment, it looks like PNPBIOS and SIO are
both claiming the same modem...) 

Bob Martin
-- 
"I know not with what weapons World War III will be fought,
but World War IV will be fought with sticks and stones."
-- Albert Einstein


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message