On Fri, 13 Jul 2001, Bruce Burden wrote:
> > Some SCSI drive manufacturers ship their drives
> > with WCE enabled. Other SCSI drive manufacturers, who are more
> > concerned with data integrity as opposed to performance figures, will
> > ship their drives with WCE disabled.
>
Robert <[EMAIL PROTECTED]> writes:
> What is up with "cron" not working?
>
> I cvsup'd last night and its still br0ke.
It works fine unless you don't specify a username in /etc/crontab.
It's a bug that it crashes instead of civilly reporting the error, but
it has never and will never do what y
In message <[EMAIL PROTECTED]>,
[EMAIL PROTECTED]
writes:
>
>
> I apologize if I should already know how to do this, but I haven't
> figured it out and haven't seen anything in the mailing lists
> archives or handbook about it. The closest I've found relates
> just to system source.
>
> I wa
On Friday 13 July 2001 21:26, Juha Saarinen wrote:
> ::camcontrol modepage da0 -m 0x08 -e -P 3
>
> su-2.05# camcontrol modepage da0 -m 0x08 -e -P 3
> camcontrol: cam_lookup_pass: CAMGETPASSTHRU ioctl failed
> cam_lookup_pass: No such file or directory
> cam_lookup_pass: either the pass driver
OK, recompiled the kernel with the 'pass' driver, and did the
camcontrol modepage thing. On this particular system, with two IBM
DDYS-T36950N SCSI-3 drives, WCE is enabled on both.
--
Regards,
Juha
PGP fingerprint:
B7E1 CC52 5FCA 9756 B502 10C8 4CD8 B066 12F3 9544
"My pid is Inigo Montoya. Yo
On Fri, Jul 13, 2001 at 07:48:30PM -0700, Cy Schubert - ITSD Open Systems Group wrote:
::
:: cd /dev && ./MAKEDEV all
::
:: or
::
:: cd /dev && ./MAKEDEV pass4 xpt2
::
:: I'm assuming you have the pass(4) device in your kernel, which is by
:: default in the GENERIC kernel.
Nope, didn't
I apologize if I should already know how to do this, but I haven't
figured it out and haven't seen anything in the mailing lists
archives or handbook about it. The closest I've found relates
just to system source.
I want to install XFree86 4.0.x instead of the current release of
4.1.0. The c
In message <01f101c10c0c$73e1c000$0a01a8c0@den2>, "Juha Saarinen"
writes:
> ::camcontrol modepage da0 -m 0x08 -e -P 3
>
> su-2.05# camcontrol modepage da0 -m 0x08 -e -P 3
> camcontrol: cam_lookup_pass: CAMGETPASSTHRU ioctl failed
> cam_lookup_pass: No such file or directory
> cam_lookup_pass
>
> Some SCSI drive manufacturers ship their drives
> with WCE enabled. Other SCSI drive manufacturers, who are more
> concerned with data integrity as opposed to performance figures, will
> ship their drives with WCE disabled.
>
I have 3 IBM drives, and the /root
:: camcontrol modepage da0 -m 0x08 -e -P 3
su-2.05# camcontrol modepage da0 -m 0x08 -e -P 3
camcontrol: cam_lookup_pass: CAMGETPASSTHRU ioctl failed
cam_lookup_pass: No such file or directory
cam_lookup_pass: either the pass driver isn't in your kernel
cam_lookup_pass: or da0 doesn't exist
Boy, life would be easier if folks would just read the man pages. :-)
-G Do not try to expand shell glob patterns in the pkg-name when
selecting packages to be deleted (by default pkg_delete automati-
cally expands shell glob patterns in the pkg-name).
From: "
On Fri, 13 Jul 2001, Ryan Taylor wrote:
> Would something like this in your /etc/rc.conf do the trick:
>
> natd_flags="-proxy_rule port 8080 server 1.2.3.4:my_divert_port"
>
> This should divert incoming packets on port 8080 to the server 1.2.3.4 on
> port my_divert_port. I use this on a firew
At 9:52 PM -0700 7/12/01, Jordan Hubbard wrote:
>And, as I'm sure others have pointed out by now, it's even easier
>to do this with the -a flag. :)
>
>Of course, since pkg_delete also supports globbing now, one assumes
>'pkg_delete *' from *any* directory would also work.
watch out there. you wo
On Fri, 13 Jul 2001, Steve Price wrote:
> Anyone have any suggestions for what the most probable causes of
> the following panic are?
>
> panic: NMI indicates hardware failure
Typically, it is a memory problem. If you use ECC or parity memory, and
a memory error is detected (and unfixable w
Andrew Boothman wrote:
> Hi all!
>
> I've successfully built and installed a new world (including GENERIC kernel),
> cvsuped a few hours ago.
>
> But I'm having trouble compiling my custom kernel. During a 'make buildkernel
> KERNCONF=SPATULA' I'm getting the following failure :
>
> ===> ipf
Steve Price <[EMAIL PROTECTED]> writes:
> Anyone have any suggestions for what the most probable causes of
> the following panic are?
>
> panic: NMI indicates hardware failure
It's obvious that something is generating an NMI when it shouldn't.
There's a sysctl, machdep.panic_on_nmi, that control
It's nice, but I have had it burn my ports so bad I had to start over.
Gnome seemed to confuse it. I have had this happen twice and will use
portupgrade after I hear people saying nice things about it for a
while.
- Mike H.
Date: Thu, 12 Jul 2001 15:22:05 -0700
From: Kris Kennaway <[EMAI
Anyone have any suggestions for what the most probable causes of
the following panic are?
panic: NMI indicates hardware failure
Thanks.
-steve
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
On Thu, 12 Jul 2001, Mike Hoskins wrote:
> On Thu, 12 Jul 2001, Matt Dillon wrote:
>
> > My new 'firewall' manual page has an ipfw example of a natd setup.
> > It might help. You need a relatively recent -stable to have the
> > man page.
>
> I see the page... Thanks, btw. However,
Brian Somers wrote:
> Hi,
>
> I said your ppp.conf was censored because you didn't attach it - you
> just attached an error message that said it couldn't read it :*P
LOL! ok.. I see. Darn mozilla. :) Ok, here goes a url, that should be fine:
http://anarcat.dyndns.org/ftp/pub/FreeBSD/local_in
* Andrew Boothman <[EMAIL PROTECTED]> [010713 00:09]:
> Replying to my own message, the subject of this message should have course
>
> have been "_ipfilter_ Module Breakage".
>
> > ===> ipfilter
Search the archives of this mailing list, about a month ago.
ipf moved oin the base system and borke
* Paul <[EMAIL PROTECTED]> [010712 23:23]:
> Once upon a time, Matt Dillon <[EMAIL PROTECTED]> scribed:
>
> > In anycase, the results prove our point rather succinctly.
>
> Unfortunately, it proves our point to us daemonites mostly, and is
> probably still lost on the average sysadminmag
Hi,
I said your ppp.conf was censored because you didn't attach it - you
just attached an error message that said it couldn't read it :*P
The right fix is to simply remove these lines.
What do your logs say when you enable LCP logging and the negotiation
fails ?
> Brian Somers wrote:
>
> >
23 matches
Mail list logo
