Re: /dev/null problems
This is fixed already. Read commit mail if you run current. Poul-Henning In message [EMAIL PROTECTED], Gordon Tetl ow writes: I was trying to build a package the other day, but I was having problems with /dev/null. My world is from Nov 4th. drifter# ls -l /dev/null crw-rw-rw- 1 root wheel2, 2 Nov 11 16:56 /dev/null drifter# echo /dev/null drifter# su - gordont %echo /dev/null /dev/null: Operation not permitted. %ls -l /dev/null crw-rw-rw- 1 root wheel2, 2 Nov 11 16:57 /dev/null Anyone else seeing this problem? -gordon To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: /dev/null problems
So in theory this is fixed, but I actually bumped into an unexpected EPERM again from a linux emulated program yesterday (acroread4) which popped up an error message about /dev/null. I haven't tried to reproduce as yet, since I'm currently rebuilding KDE; /dev/null works properly for me on the FreeBSD ABI again, so maybe it's just a bug in acroread4. Robert N M Watson FreeBSD Core Team, TrustedBSD Project [EMAIL PROTECTED] NAI Labs, Safeport Network Services On Sun, 11 Nov 2001, Gordon Tetlow wrote: I was trying to build a package the other day, but I was having problems with /dev/null. My world is from Nov 4th. drifter# ls -l /dev/null crw-rw-rw- 1 root wheel2, 2 Nov 11 16:56 /dev/null drifter# echo /dev/null drifter# su - gordont %echo /dev/null /dev/null: Operation not permitted. %ls -l /dev/null crw-rw-rw- 1 root wheel2, 2 Nov 11 16:57 /dev/null Anyone else seeing this problem? -gordon To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: /dev/null problems
Robert Watson wrote: So in theory this is fixed, but I actually bumped into an unexpected EPERM again from a linux emulated program yesterday (acroread4) which popped up an error message about /dev/null. I haven't tried to reproduce as yet, since I'm currently rebuilding KDE; /dev/null works properly for me on the FreeBSD ABI again, so maybe it's just a bug in acroread4. Also, I've seen netscape etc do this too when it thinks it is executing acroread4, but instead is doing an exec(/dev/null. ... ). On Sun, 11 Nov 2001, Gordon Tetlow wrote: I was trying to build a package the other day, but I was having problems with /dev/null. My world is from Nov 4th. drifter# ls -l /dev/null crw-rw-rw- 1 root wheel2, 2 Nov 11 16:56 /dev/null drifter# echo /dev/null drifter# su - gordont %echo /dev/null /dev/null: Operation not permitted. %ls -l /dev/null crw-rw-rw- 1 root wheel2, 2 Nov 11 16:57 /dev/null Anyone else seeing this problem? -gordon To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] All of this is for nothing if we don't go to the stars - JMS/B5 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
kqueue(2) doesn't deliver EV_EOF on pipes [patch]
Hi,
I've noticed that kqueue(2) doesn't notify reader about EV_EOF
condition on pipe. Attached simple test program highlights
the problem (confirmed both on 5-CURRENT and 4-STABLE). Also
attached is the simple fix.
-Maxim
Index: sys/kern/sys_pipe.c
===
RCS file: /home/ncvs/src/sys/kern/sys_pipe.c,v
retrieving revision 1.86
diff -d -u -r1.86 sys_pipe.c
--- sys/kern/sys_pipe.c 2001/09/21 22:46:53 1.86
+++ sys/kern/sys_pipe.c 2001/11/12 13:28:05
@@ -1221,6 +1221,7 @@
ppipe-pipe_state |= PIPE_EOF;
wakeup(ppipe);
+ KNOTE(ppipe-pipe_sel.si_note, 0);
ppipe-pipe_peer = NULL;
}
/*
#include sys/types.h
#include sys/event.h
#include sys/time.h
#include err.h
#include signal.h
#include stdio.h
#include unistd.h
void
testpassed(int sig)
{
printf(Test passed\n);
exit(0);
}
int
main(int argc, char **argv)
{
int kq, pid, ppid, nevents;
struct kevent changelist[1];
struct kevent eventlist[1];
int pp[2];
pipe(pp);
ppid = getpid();
pid = fork();
switch (pid) {
case -1:
/* Error */
err(1, can't fork());
/* NOTREACHED */
case 0:
/* Child */
close(pp[1]);
kq = kqueue();
EV_SET(changelist, pp[0], EVFILT_READ, EV_ADD | EV_ENABLE | EV_EOF, \
0, 0, NULL);
kevent(kq, changelist, 1, NULL, 0, NULL);
for (;;) {
nevents = kevent(kq, NULL, 0, eventlist, 1, NULL);
if (nevents 0 || (eventlist[0].flags EV_EOF) != 0) {
kill(ppid, SIGTERM);
exit(0);
}
}
break;
default:
/* Sever */
close(pp[0]);
break;
}
signal(SIGTERM, testpassed);
/* Give child some time to initialise kqueue(2) */
sleep(1);
close(pp[1]);
/* Give child some time to receive EV_EOF and kill us */
sleep(1);
kill(pid, SIGTERM);
printf(Test failed\n);
exit(1);
}
Re: kqueue(2) doesn't deliver EV_EOF on pipes [patch]
if (nevents 0 || (eventlist[0].flags EV_EOF) != 0) {
^^
OOPS, last minute bug. Should be `' instead, but it doesn't affect
outcome of the test.
-Maxim
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: daily run output passwd diff
On 11-Nov-01 Crist J. Clark wrote: On Fri, Nov 09, 2001 at 02:55:55PM +0100, Alexander Leidinger wrote: Hi, I think the CVS tag shouldn't be interpreted as an entry which contains a password. ---snip--- Backup passwd and group files: 1c1 # $FreeBSD:(password):09:07 peter Exp $ --- # $FreeBSD:(password):27:16 ache Exp $ 16a17 www:(password):80:80::0:0:World Wide Web Owner:/nonexistent:/sbin/nologin Magelan.Leidinger.net group diffs: 1c1 # $FreeBSD: src/etc/group,v 1.21 2001/10/18 16:53:20 sheldonh Exp $ --- # $FreeBSD: src/etc/group,v 1.22 2001/10/25 03:27:16 ache Exp $ 20a21 www:*:80: ---snip--- Makes sense. No need to hide the revision number. Committed to -CURRENT. MFC 1 week. Index: 200.backup-passwd === RCS file: /home/ncvs/src/etc/periodic/daily/200.backup-passwd,v retrieving revision 1.8 diff -u -r1.8 200.backup-passwd --- 200.backup-passwd 2000/09/14 17:19:10 1.8 +++ 200.backup-passwd 2001/11/11 07:09:49 @@ -42,7 +42,7 @@ [ $rc -lt 1 ] rc=1 echo $host passwd diffs: diff $bak/master.passwd.bak /etc/master.passwd |\ - sed 's/^\([] [^:]*\):[^:]*:/\1:(password):/' + sed 's/^\([] [^#][^:]*\):[^:]*:/\1:(password):/' mv $bak/master.passwd.bak $bak/master.passwd.bak2 cp -p /etc/master.passwd $bak/master.passwd.bak || rc=3 fi What if someone comments out a line in the password file of a user? Then this won't hide that password. When this originally went in, it took a long while to get a sed line people were happy with. Replacing the version number is a minor thing, but getting it to work perfectly may be a bit difficult. If you do this, I'd rather you make sed handle the $FreeBSD$ case as a completely separate case, so something like: sed -e '/\$FreeBSD\$/; //s/blah blah/blah/' or some such (I forget how sed does multiple expressions). -- John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc Power Users Use the Power to Serve! - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
RE: USB and SMP
Definitely the drivers. UHCI is a pile of that stuff that smells. Nick -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Daniel O'Connor Sent: 11 November 2001 03:21 To: Jim Bryant Cc: [EMAIL PROTECTED]; Michael Class Subject: Re: USB and SMP On 10-Nov-2001 Jim Bryant wrote: I have a [secondary] USB Keyboard with a mouse port on it's side installed, as well as a cameramate CompactFlash reader hooked up. Both work. What chipset though? The OHCI stuff seems less reliable than UHCI. Not sure if its the hardware, the driver or some combination :) --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au The nice thing about standards is that there are so many of them to choose from. -- Andrew Tanenbaum To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
namespace pollution with struct thread?
Recent versions of WINE have defined a struct thread in wine/server/thread.h. Unfortunately, wine/server/context_i386.c sucks in sys/user.h, which brings in sys/proc.h. Of course, sys/proc.h contains the post-KSE integrated struct thread. I've managed to build WINE by temporarily placing a #ifdef _KERNEL ... #endif in sys/proc.h. I WINE developer has suggested that this is namespace pollution on the part of FreeBSD, but he hasn't given any details to support what he means. So, should parts of sys/proc.h be protected by _KERNEL. -- Steve To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: kernel won't build - atomic.c/atomic.h errors...
Sorry for mot responding sooner. On Wed, Oct 31, 2001 at 09:27:58PM -0600, Jim Bryant wrote: cc -c -g -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../../.. -I../../../dev -I../../../contrib/dev/acpica -I../../../contrib/ipfilter -I../../../../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 -fomit-frame-pointer ../../../i386/i386/atomic.c In file included from ../../../i386/i386/atomic.c:48: machine/atomic.h: In function `atomic_set_char': machine/atomic.h:214: inconsistent operand constraints in an `asm' On Fri, Nov 02, 2001 at 03:38:56PM -0600, Jim Bryant wrote: Is anyone else seeing this problem? There is a problem with the way gcc handles asm constraints. The quick solution is to compile with `-O'. For a more detailed analysis and my then suggested solution, refer to the thread kernel compile failure without -O option in -current from Jul 2000 (I can't quote the exact message ID of my response because our firewall helpfully rewrites it). Since those patches were written, the code has been cleaned up to remove support for older variants of gcc, but the constraint changes for gcc = 2.8 should still be valid. Peter, VK2PJ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
namespace pollution with struct thread?
On Mon, 12 Nov 2001 14:01:35 -0800, Steve Kargl [EMAIL PROTECTED] said: I WINE developer has suggested that this is namespace pollution on the part of FreeBSD, but he hasn't given any details to support what he means. Applications which include sys/user.h, or any other non-standard header file, should expect that any conceivable symbol might be used therein. FreeBSD makes no guarantees as to the namespace used by non-standard interfaces. (We don't want to be like certain other environments where every symbol that might conceivably be accessible to an application is obfuscated with multiple underscores.) -GAWollman To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: namespace pollution with struct thread?
On the other hand we might conceivably be able to stop the export from the kernel of this struct type. On Mon, 12 Nov 2001, Garrett Wollman wrote: On Mon, 12 Nov 2001 14:01:35 -0800, Steve Kargl [EMAIL PROTECTED] said: I WINE developer has suggested that this is namespace pollution on the part of FreeBSD, but he hasn't given any details to support what he means. Applications which include sys/user.h, or any other non-standard header file, should expect that any conceivable symbol might be used therein. FreeBSD makes no guarantees as to the namespace used by non-standard interfaces. (We don't want to be like certain other environments where every symbol that might conceivably be accessible to an application is obfuscated with multiple underscores.) -GAWollman To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: namespace pollution with struct thread?
On 12-Nov-01 Julian Elischer wrote: On the other hand we might conceivably be able to stop the export from the kernel of this struct type. Not unless we stop exporting struct proc since each proc has an embedded thread. On Mon, 12 Nov 2001, Garrett Wollman wrote: On Mon, 12 Nov 2001 14:01:35 -0800, Steve Kargl [EMAIL PROTECTED] said: I WINE developer has suggested that this is namespace pollution on the part of FreeBSD, but he hasn't given any details to support what he means. Applications which include sys/user.h, or any other non-standard header file, should expect that any conceivable symbol might be used therein. FreeBSD makes no guarantees as to the namespace used by non-standard interfaces. (We don't want to be like certain other environments where every symbol that might conceivably be accessible to an application is obfuscated with multiple underscores.) -GAWollman -- John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc Power Users Use the Power to Serve! - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: namespace pollution with struct thread?
I can confirm that I can build wine and run it if I put #ifdef _KERNEL ... #endif in sys/proc.h. I was uncertain about whether sys/user.h was a non-standard header file. I will probably relay Garrett's point to the wine developers at some point. steve On Mon, Nov 12, 2001 at 03:50:16PM -0800, Julian Elischer wrote: On the other hand we might conceivably be able to stop the export from the kernel of this struct type. On Mon, 12 Nov 2001, Garrett Wollman wrote: On Mon, 12 Nov 2001 14:01:35 -0800, Steve Kargl [EMAIL PROTECTED] said: I WINE developer has suggested that this is namespace pollution on the part of FreeBSD, but he hasn't given any details to support what he means. Applications which include sys/user.h, or any other non-standard header file, should expect that any conceivable symbol might be used therein. FreeBSD makes no guarantees as to the namespace used by non-standard interfaces. (We don't want to be like certain other environments where every symbol that might conceivably be accessible to an application is obfuscated with multiple underscores.) -GAWollman -- Steve To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: daily run output passwd diff
On Mon, Nov 12, 2001 at 08:08:37AM -0800, John Baldwin wrote:
On 11-Nov-01 Crist J. Clark wrote:
On Fri, Nov 09, 2001 at 02:55:55PM +0100, Alexander Leidinger wrote:
Hi,
I think the CVS tag shouldn't be interpreted as an entry which contains
a password.
---snip---
Backup passwd and group files:
1c1
# $FreeBSD:(password):09:07 peter Exp $
---
# $FreeBSD:(password):27:16 ache Exp $
16a17
www:(password):80:80::0:0:World Wide Web Owner:/nonexistent:/sbin/nologin
Magelan.Leidinger.net group diffs:
1c1
# $FreeBSD: src/etc/group,v 1.21 2001/10/18 16:53:20 sheldonh Exp $
---
# $FreeBSD: src/etc/group,v 1.22 2001/10/25 03:27:16 ache Exp $
20a21
www:*:80:
---snip---
Makes sense. No need to hide the revision number.
Committed to -CURRENT. MFC 1 week.
Index: 200.backup-passwd
===
RCS file: /home/ncvs/src/etc/periodic/daily/200.backup-passwd,v
retrieving revision 1.8
diff -u -r1.8 200.backup-passwd
--- 200.backup-passwd 2000/09/14 17:19:10 1.8
+++ 200.backup-passwd 2001/11/11 07:09:49
@@ -42,7 +42,7 @@
[ $rc -lt 1 ] rc=1
echo $host passwd diffs:
diff $bak/master.passwd.bak /etc/master.passwd |\
- sed 's/^\([] [^:]*\):[^:]*:/\1:(password):/'
+ sed 's/^\([] [^#][^:]*\):[^:]*:/\1:(password):/'
mv $bak/master.passwd.bak $bak/master.passwd.bak2
cp -p /etc/master.passwd $bak/master.passwd.bak || rc=3
fi
What if someone comments out a line in the password file of a user? Then this
won't hide that password. When this originally went in, it took a long while
to get a sed line people were happy with. Replacing the version number is a
minor thing, but getting it to work perfectly may be a bit difficult. If you
do this, I'd rather you make sed handle the $FreeBSD$ case as a completely
separate case, so something like:
sed -e '/\$FreeBSD\$/; //s/blah blah/blah/' or some such (I forget how sed does
multiple expressions).
I thought about this, but then thought, Who ever just comments out
password entries without clearing the password too? I guess the
answer is, some people do.
How about,
sed -E 's/^([]
[^:]*):[^:]*:(([0-9]+:){2}[^:]*(:[0-9]+){2}(:[^:]*){3}$)/\1:(password)\2/'
Which only touches entries that match the password format exactly, but
includes commented out ones?
--
Crist J. Clark | [EMAIL PROTECTED]
| [EMAIL PROTECTED]
http://people.freebsd.org/~cjc/| [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: daily run output passwd diff
On 13-Nov-01 Crist J. Clark wrote:
What if someone comments out a line in the password file of a user? Then
this
won't hide that password. When this originally went in, it took a long
while
to get a sed line people were happy with. Replacing the version number is a
minor thing, but getting it to work perfectly may be a bit difficult. If
you
do this, I'd rather you make sed handle the $FreeBSD$ case as a completely
separate case, so something like:
sed -e '/\$FreeBSD\$/; //s/blah blah/blah/' or some such (I forget how sed
does
multiple expressions).
I thought about this, but then thought, Who ever just comments out
password entries without clearing the password too? I guess the
answer is, some people do.
How about,
sed -E 's/^([]
[^:]*):[^:]*:(([0-9]+:){2}[^:]*(:[0-9]+){2}(:[^:]*){3}$)/\1:(password)\2/'
Which only touches entries that match the password format exactly, but
includes commented out ones?
That's fine I suppose. I would rather err on the side of caution and just
exclude the $FreeBSD$ line and perform the change on all other lines by
default. You never know what weird contortion of a password file someone
might be using.
--
John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/
PGP Key: http://www.baldwin.cx/~john/pgpkey.asc
Power Users Use the Power to Serve! - http://www.FreeBSD.org/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: wake up on lan driver support
On Sun, Nov 11, 2001 at 04:38:50PM -0800, matt wrote: any clue to find the tech doc regarding the format of the packet. I'd code such thing. It's a very good feature for FreeBSD. ports/net/wakeonlan I'd really like to see some driver support for WOL for support of dynamic power control on clusters. Suspend/Resume is going to be faster then a boot cycle unless someone ports the loader to the LinuxBIOS framework. -- Brooks -- Any statement of the form X is the one, true Y is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 msg32042/pgp0.pgp Description: PGP signature
