On Friday, 15 December 2000 at 2:20:40 -0500, Mike Nowlin wrote:
>
>> Does that mean that such BIOS's are proprietary in the sense that they
>> don't recognize the dedicated format?
>
> There are times when the politically-correct of the world use the term
> "proprietary" when they actually mean
> Does that mean that such BIOS's are proprietary in the sense that they
> don't recognize the dedicated format?
There are times when the politically-correct of the world use the term
"proprietary" when they actually mean "dumb" or "really badly
designed". But yes, that's what it means... :)
On Thu, Dec 14, 2000 at 06:13:01PM -0500, Garance A Drosihn wrote:
> At 8:06 AM +0100 12/14/00, Andreas Klemm wrote:
> >On Wed, Dec 13, 2000 at 03:35:51PM +0300, Ilya Martynov wrote:
> > > P.S. I forgot about another problem I meet while setting up
> > > printing. SETUP creates smbclient.conf th
Hi,
Looks like a glitch in stable ? From fresh cvsup, break in builworld :
known-freebsd\" -DIN_GCC -I/usr/obj/usr/src/i386/usr/include -c
/usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/g
cc/convert.c -o convert.o
cc -O -pipe -DFREEBSD_NATIVE -DIN_GCC -DHAVE_CONFIG_H
-DPREFIX=\"/usr/obj/u
In message <[EMAIL PROTECTED]> Glendon Gross
writes:
: Does that mean that such BIOS's are proprietary in the sense that they
: don't recognize the dedicated format?
One could say that, however the fake disk label for dedicated disks is
a problem. The BIOS shouldn't know about partitions, but m
Does that mean that such BIOS's are proprietary in the sense that they
don't recognize the dedicated format?
On Thu, 14 Dec 2000, Warner Losh wrote:
> In message <[EMAIL PROTECTED]> Glendon Gross
>writes:
> : Please correct me if I am wrong, but this discussion seems to revolve
> : around a pr
In message <[EMAIL PROTECTED]> Glendon Gross
writes:
: Please correct me if I am wrong, but this discussion seems to revolve
: around a problem that results from nonstandard BIOS routines.
Not so much non-standard bios routines, but rather from BIOSes that
know too much about what Should Be Th
On 13 Dec, [EMAIL PROTECTED] wrote:
> I have a Micronics 486 VLB motherboard (unknown exact model) that doesn't
> like FreeBSD beyond 3.x. 3.1-RELEASE works fine on this motherboard but
> 4.x versions reboot immediately following the display of the Copyright
> notices and FreeBSD version line.
M
In message <[EMAIL PROTECTED]>,
"Russell D. Murphy Jr." writes:
>
>My machine has locked up solid and rebooted a few times lately; the
>most recent time I managed to get this from the console (copied by
>hand - I believe it's accurate, but no guarantees):
>
.cut
>
>The machine is a Dell wit
Please correct me if I am wrong, but this discussion seems to revolve
around a problem that results from nonstandard BIOS routines.
On Sun, 19 Nov 2000, Warner Losh wrote:
> In message <[EMAIL PROTECTED]> Greg Lehey writes:
> : > No it isn't bogus. You can't boot off a DD disk on some machin
My machine has locked up solid and rebooted a few times lately; the
most recent time I managed to get this from the console (copied by
hand - I believe it's accurate, but no guarantees):
(some information probably scrolled off the scr
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
Dear all,
rpc.lockd in FreeBSD suffers from a pubic server's lazyness --- It says it's
done the job, but never did anything besides talking...
Searching through the lists gives different stories. Some say that NFS locking
isn't really necessary, but what about locking critical situations like
de
13 matches
Mail list logo
