Hi,
I'm trying to apply the patch 01:40 (fts) on my 4.3 system. But the "chgrp"
doesn't exist on /usr/src/usr.bin... Look:
cd /usr/src/usr.bin/chgrp
# make depend && make all install
The update of "chgrp" fail... Why this occur???
PS: Sorry for my poor english!
Regards!!!
To Unsubscribe: se
On Sun, 29 Jul 2001, Chris BeHanna wrote:
> On Wed, 25 Jul 2001, Gregory Bond wrote:
>
> >
> > >Subject: Re: If you think people use FreeBSD for server, you must've been outta
>school for long long time!
> >
> > All I can say is that it is a pity no-one thought fit to add killfiles to my
> > mai
On Sat, 28 Jul 2001, ian j hart wrote:
> cd /usr/src;make update (CVS) pulls down RELENG_4 not RELENG_4_3.
> There should at least be a warning in UPDATING. Shouldn't
> this be a variable in make.conf?
>
>
> Hmm. The -r would mean BRANCH would have to be a numeric or
> symbolic tag. What if you
> Cheers for any light anyone can shed,
As others have said:
- check login.conf
- force a salt like '$1$$'
also:
check /etc/auth.conf for a "crypt_default" line.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the mess
What's mean "pnpbios: Bad PnP BIOS data checksum" ?
=== dmesg ===
Copyright (c) 1992-2001 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD 4.3-STABLE #13: Fri Jul 27 12:0
> What's mean "pnpbios: Bad PnP BIOS data checksum" ?
It means that your PnP BIOS data has a bad checksum.
We don't trust it in this case. Some vendors don't bother to compute the
checksum for this structure; we are more conservative than Microsoft, and
refuse to use the PnP BIOS in this case
> Yes, it's a hack,
So send in the clone()s.
:>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
Hi,
I have been struggling with a Dell Latitude C800 here. FreeBSD 4.1 and 4.3
was working with no problems, but when I tried to upgrade it to 4-stable,
it did not see the disk anymore. It just gave this message:
#
atapci0: port 0xbfa0-0xbfaf at device 31.1 on pci
0
ata0: at 0x1f0 irq 1
