I'm running 5.1-R, and having forgot to set up UFS2 for my file systems
(doh!) I'm using ACLs the UFS1 way. All is well and good, for the most
part, except that I'm getting a lot of messages like these:
/var/log/messages:Sep 22 20:38:01 kern.crit prophecy kernel:
ufs_extattr_get (/var): inode
in regard to this.
Best regards,
Christopher Nehren
signature.asc
Description: This is a digitally signed message part
On Mon, 2003-08-11 at 04:25, Ian Dowse wrote:
Try the following patch. I can't remember if all the changes in
this are necessary, but I think I found it fixed problems when
interoperating with a Linux-like PLIP implementation.
Unfortunately, it doesn't work -- just prolongs the time it takes
The not implemented error message suggests to me that the VM (in this
case, Win2K) is attempting to perform an operation that the emulation
software (or its underlying operating system -- in this case, Linux
2.4.2 under FreeBSD emulation) doesn't know how to perform. I received a
similar message
I've been having problems recently with strace. Here's example output
(no, nothing is left out):
% strace /bin/ls
And it doesn't print anything. I've tried building it without my CPUTYPE
/etc/make.conf variable (set to athlon-tbird; no other variables are
defined in make.conf except for the
On Fri, 2003-05-30 at 16:10, Dan Nelson wrote:
If you hit ^T, does it print [iowait]? If so, I'm seeing the same
thing :) It's intermittent, though. If I ru ps axl | grep strace, I
get:
Yes, I get the [iowait] message. Also, it runs until completion,
seemingly consistently, if I ^Z it and
On Fri, 2003-05-30 at 17:45, Darryl Okahata wrote:
Perhaps the same problem that affects truss, also affects strace?
(See the recent 5.1 release TODO messages for details.)
Hmm, after reviewing the page, it does seem to be similar, particularly
because strace does use execve(). At least
I've been monitoring the -CURRENT mailing list for about a day or two,
and haven't seen anything that's really broken (except for GCC 3.x,
which I don't use anyway). So, is it safe to upgrade to -CURRENT yet?
TIA for the info,
Chris
To Unsubscribe: send mail to [EMAIL PROTECTED]
with
I've been monitoring the -CURRENT mailing list for about a day or two,
and haven't seen anything that's really broken (except for GCC 3.x,
which I don't use anyway). So, is it safe to upgrade to -CURRENT yet?
TIA for the info,
Chris
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe
--
root@juanillo:/usr/src/sys/i386/compile/JUANILLO $ make
cc -c -x assembler-with-cpp -DLOCORE -O -pipe -Wall -Wredundant-decls
-Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith
-Winline -Wcast-qual -fformat-extensions -ansi -g -nostdinc -I-
10 matches
Mail list logo
