I'll second this email...
My computer had been stable all winter (with setiathome runnning full
time) but suddenly come the Australian summer it started freezing.
Not panicing, just totally freezing under load.
I could reproduce it by trying to build the whole of KDE and each time
it was a
Please leave the wd driver for those who cannot use the ATA driver.
At least until the ATA driver gets support for more older disks.
I cant be the only person using an old 80 MB IDE drive as / with
another drive as /usr (a 400 MB SCSI).
I haven't tried for a couple of months but the ATA driver
Are there any particular preparation processes one should go through
when setting up a Mylex DAC960 RAID array ?
(if so give me a pointer to the docs)
Can I just purchase all the hardware, plug in the disks and boot the
FreeBSD-4 install floppies ? (for a system to be booting from the
array
You'll need to make custom install disks with the floating point emulator
in the kernel since you dont have a FPU with that processor.
On Fri, 18 Feb 2000, Kelvin Farmer wrote:
Hi,
I was wondering if its possible to run FreeBSD-4.0 on a 486 SLC2 66mhz.
(win95 runs on this computer ok)
I
On Fri, 7 Apr 2000, Mohit Aron wrote:
Hi,
I'm using FreeBSD-4.0-RELEASE on a Xeon processor. The following
messages have been appearing in my /var/log/messages file apparently upon
an rlogin to the machine:
Apr 7 00:23:16 idli rshd[236]: no modules loaded for `rshd' service
On Sun, 9 Apr 2000, John Polstra wrote:
In article [EMAIL PROTECTED],
Matthew Sean Thyer [EMAIL PROTECTED] wrote:
I stopped the messages by adding the following line below the rshd
line in /etc/pam.conf
rshdauthrequiredpam_permit.so
The way PAM works
On Wed, 19 Apr 2000, Oliver Schonefeld wrote:
i recently updated my -current system from -current as of about mid-march to
lest sundays's -current (jep, from 4.0 to 5.0) due to the work done to the
ida driver.
well, the ida driver seems to work, but the network hast complety stopped
On Tue, 1 Feb 2000, Edwin Culp wrote:
Marc Schneiders wrote:
Some problems have disappeared, some remain, to wit:
/kernel: cmd ntpd pid 86 tried to use non-present sched_get_priority_max
/kernel: cmd ntpd pid 86 tried to use non-present sched_setscheduler
ntpd [86]:
Barry,
I think I know the problem you have.
When "device scbus0" changed to "device scbus" in LINT and I applied
that to my config file I found I could no longer wire down my disks
to scbus0 unless I changed the base SCSI code line back to "device
scbus0".
This is what I have:
device
