ton cumpulsorily (and annoyingly).
>
> Why in your opinion is that crazy behavior and what should I do?
Are the startx-launched and kdm-launched X daemons using the same config
file? Check the top of /var/log/Xorg.*.log for sure. If you ran
"X -configure" at some point i
a miniinst.iso
> file?
That's a good question :-) I didn't realize we hadn't made one.
--
Doug White| FreeBSD: The Power to Serve
[EMAIL PROTECTED] | www.FreeBSD.org
___
freebsd-questions@freebsd.org m
P clients will just ignore
your banner since it won't conform to the FTP protocol specification.
If you want it to display when the user logs into your FTP server, put it
in /etc/ftpmotd. If you want your telnet client to see it, put it in
/etc/motd.
--
Doug White| Free
are simply misinterpreting your results here.
File creation tests are usually more for filesystem-specific benchmarking
than for throughput benchmarking. I'd suggest something more like iozone
for throughput testing. If the volumes have nothing on them you care about
then rawio can
27;s been any recent work on
> this.
We're waiting on a driver update that is tied up in legalities at the
moment.
--
Doug White| FreeBSD: The Power to Serve
[EMAIL PROTECTED] | www.FreeBSD.org
___
freebsd-questions@f
h/var.h,v": 1: "head" expected
>
> Then when I run "make buildworld", that fails
What cvsup server are you using? It appears to be corrupted.
--
Doug White| FreeBSD: The Power to Serve
[EMAIL PROTECTED] | www.FreeBSD.org
_
a dual ppro. Its pssible it has some
unsual cdrom setup that freebsd does not support. xompaqs are prone to
somewhat nonstandard setups.
--
Doug White| FreeBSD: The Power to Serve
[EMAIL PROTECTED] | www.FreeBSD.org
___
[E
md64 to x86 after
> already
> booting an OS.
Me either. -current actually supports running i386 binaries in amd64 mode.
Thats one of the processor's features. :-)
You can't run amd64 binaries when booted into an i386 OS, of course.
--
Doug White| F
hu Oct 9 08:49:21 PDT 2003
> --
> On Thu, 9 Oct 2003 wintran at email.cz wrote:
>
> > Hi,
> > does it plan to support PCMCIA card Proxim Orinoco model 8471-WD in
> FreeBSD?
>
> If someone wants to work on it and can get specs, sure.
>
> Doug Whi
owrk device drivers. Search for
"Project Evil" for information. :)
--
Doug White| FreeBSD: The Power to Serve
[EMAIL PROTECTED] | www.FreeBSD.org
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mai
:
>
> neptune:~> ssh [EMAIL PROTECTED]
> key_verify failed for server_host_key
ssh -v might help, but I suspect your host key changed and you've
configured strict checking. Is your client ssh.com or OpenSSH?
>
>
> NOTE: Please CC me, as I am not currently
ulprit hiere is a bad cable or termination. Recheck your
connections and chain layouts.
Adaptec's site has troubleshooting tips for SCSI chain issues.
--
Doug White| FreeBSD: The Power to Serve
[EMAIL PROTECTED] | www.FreeBSD.org
Try taking the SATA controller out of native mode.
--
Doug White| FreeBSD: The Power to Serve
[EMAIL PROTECTED] | www.FreeBSD.org
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-
he
getblk off-by-one bug that Scott fixed the other day. Update your -current
or apply the patch from the lists.
--
Doug White| FreeBSD: The Power to Serve
[EMAIL PROTECTED] | www.FreeBSD.org
___
[EMAIL PROTECTED] mailing list
the F1: FreeBSD message, or after you press a key, or what?
This sounds like a BIOS issue. boot0 uses only BIOS calls to do its work.
Lots of problems like this are also caused by bad drive geometry.
What is the partition layout on the disk(s) in the system? Hardware
description?
--
Doug White
e kernel (if fxr.watson.org is to be
believed). Check standard-supfile, delete your compile directory, and try
updating again.
--
Doug White| FreeBSD: The Power to Serve
[EMAIL PROTECTED] | www.FreeBSD.org
___
[EMAIL P
ver, the usb mouse didn't work. Booting in 4.9 all runs well. In
> 5.2 the usbdev -v hangs about 5 seconds on the first hub. The mouse is
> recognized, but the cursor didn't move. (I've also cvsup to the latest
> sources and build my own kernel).
Not sure here; the USB mouse
cross IDE and SCSI disks in
the same system.
>- Disk configuration:
> - ad0 (s1: FreeBSD-4.0)
> - da0 (s1: FAT32, W98)
> - da1 (s1: FBSD-5.2)
> - da2 (s1: FAT32)
--
Doug White| FreeBSD: The Power to Serve
[EMAIL PROTECTED] | www
Any.pm.
This should be reported to the CGI_Lite authors.
--
Doug White| FreeBSD: The Power to Serve
[EMAIL PROTECTED] | www.FreeBSD.org
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/
geometry is wrong. Try zeroing
> > off the front end of the disk, partitioning it with DOS FDISK, then put
> > FreeBSD on it.
>
> I don't like the sound of that. I'll just stick with STABLE until 5.x is
> really ready.
-STABLE will have the same problem since its i
se boot0 and the BIOS can't figure out how to
reach the partition, generally because the geometry is wrong. Try zeroing
off the front end of the disk, partitioning it with DOS FDISK, then put
FreeBSD on it.
--
Doug White| Fre
; I'm not sure if it's only happening to some installations - but I was
> certainly in the same boat.
>
> I ended up having to re-install Win2k and I used Grub as my new bootloader.
Can't say I'm having any boot0 issues here with -current and win2k pro
sp3. Note window
22 matches
Mail list logo
