logy"). Really sounds like the decision of a legal dept. and
not
a CEO.
Hounding on AMD won't help right now regardless; they're still
finding out what kind of mess they've acquired, making changes to it
is a long way off. :)
--
brandon s. allbery [solaris,freebsd,per
ection, so one of the files being concatenated into cal.vcs is
cal.vcs. (This has always been true for all shells, in my experience.)
--
brandon s. allbery [linux,solaris,freebsd,perl]
[EMAIL PROTECTED]
system administrator [openafs,heimdal,too many hats]
[EMAIL PROTECTED]
elec
ut a manpage; 4.x has had it for a while now.
--
brandon s. allbery[linux,solaris,freebsd,perl] [EMAIL PROTECTED]
system administrator [WAY too many hats][EMAIL PROTECTED]
electrical and computer engineering, carnegie mellon univ. KF8NH
_
intaining. It's not like -x output is all that unusable; it's just not as
"pretty" --- but it also provides more information, which can be useful when
trying to diagnose problems.
By the way, this isn't really a ports issue; -questions is more appropriate.
--
brandon
different between different systypes; even if someone
had developed one, it's just as likely to be for Linux or Solaris as for
*BSD, and as a result wouldn't be particularly useful.
--
brandon s allbery [openafs/solaris/japh/freebsd] [EMAIL PROTECTED]
system administrator [linux/heimdal/
; 5.1? Or is unmounting and simply removing it safe?
Simply unmounting it should be good enough. "camcontrol stop" will
probably do what you want (*after* unmounting it).
--
brandon s allbery [openafs/solaris/japh/freebsd] [EMAIL PROTECTED]
system administrator [linux/heimdal/too many
On Sun, 2002-12-08 at 16:02, Christian Chen wrote:
> So not only do you have to make sure you've added device apm0, you also
> have to delete/comment the "disable" part:
No, you don't:
2@pyanfar:5001 Z$ cat /boot/kernel.conf
di fd1
en apm0
