Re: USB keyboards and extra keys
On Fri, 16 Oct 2009 23:54:40 -0500 Zane C.B. v.ve...@vvelox.net wrote: Any one ever manage to get extra keys to work on a USB keyboard in the RELENG_7 branch? In the past, I have used hotkeys[1] from ports for this. I don't have that keyboard now, so I can't test if it still works. HTH References: 1) http://www.freshports.org/misc/hotkeys/ -- Torfinn ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: ZFS v13 on FreeBSD 7 release/fixit iso's?
On 16 okt 2009, at 20:57, Vincent Hoffman wrote: Michael Proto wrote: On Fri, Oct 16, 2009 at 11:58 AM, Ben Stuyts b...@altesco.nl wrote: I've recently upgraded a few FreeBSD-7-stable servers, and I see ZFS v13 has made it into the tree. From what I can tell, the existing 7.2 release fixit cd's do not support v13 yet. I'd rather not upgrade the pools without a rescue cd available... Are there any 7-stable iso's available which support zfs v13? How about ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/200906/ ? or indeed from http://pub.allbsd.org/FreeBSD-snapshots/ Hey, that's neat, thanks! The second site is a lot more up to date than the former. Ben ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Can close-ing a pipe trigger a SIGPIPE?
Hello! I'm investigating a problem caused by (what seems like a spurious) SIGPIPE. The program creates a child process using pipe, exchanges a few messages with the child (via write and read) and closes the pipe. Some times -- in about 60% of the cases -- this causes a SIGPIPE to be delivered to the parent... Now, it is quite possible for the child to have already exited by the time the parent closes its end of the pipe -- but why should that cause a SIGPIPE, unless the parent tries to write something to the widowed pipe, which it does not? From pipe(2): A pipe that has had an end closed is considered widowed. Writing on such a pipe causes the writing process to receive a SIGPIPE signal. There is no other mention of SIGPIPE in that manual page... I set SIGPIPE on ignore around the pipe-closing as a work-around, but I think, this is a bug... The thing is part of TclX' self-test (test signal-3.0) -- and it was not dying from SIGPIPE before the FreeBSD-7.x, as far as I can remember... It still seems to be fine on Linux... Have there been any changes in this area in FreeBSD? Thanks! -mi ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Can close-ing a pipe trigger a SIGPIPE?
On Sat, Oct 17, 2009 at 12:46:37PM -0400, Mikhail T. wrote: Hello! I'm investigating a problem caused by (what seems like a spurious) SIGPIPE. The program creates a child process using pipe, exchanges a few messages with the child (via write and read) and closes the pipe. Some times -- in about 60% of the cases -- this causes a SIGPIPE to be delivered to the parent... Now, it is quite possible for the child to have already exited by the time the parent closes its end of the pipe -- but why should that cause a SIGPIPE, unless the parent tries to write something to the widowed pipe, which it does not? From pipe(2): A pipe that has had an end closed is considered widowed. Writing on such a pipe causes the writing process to receive a SIGPIPE signal. There is no other mention of SIGPIPE in that manual page... I set SIGPIPE on ignore around the pipe-closing as a work-around, but I think, this is a bug... The thing is part of TclX' self-test (test signal-3.0) -- and it was not dying from SIGPIPE before the FreeBSD-7.x, as far as I can remember... It still seems to be fine on Linux... Have there been any changes in this area in FreeBSD? Thanks! Take ktrace of both parent and child. pgplSQFAnR1s0.pgp Description: PGP signature
Re: Can close-ing a pipe trigger a SIGPIPE?
Kostik Belousov написав(ла): Take ktrace of both parent and child. Great idea! Here is the kdump's listing for both (after ktrace -i): http://aldan.algebra.com/~mi/tmp/tclx-kdump.txt (it is large, so be sure to use a compressing browser). Once loaded, look for substring: Error SIGPIPE signal received while closing file5. The parent process-ID is 92722. The child -- 92723. Thanks! Yours, -mi ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Can close-ing a pipe trigger a SIGPIPE?
Kostik Belousov написав(ла): Take ktrace of both parent and child. I can see the curious piece right here: The child exits: 92723 tclsh8.5 CALL exit(0) The parent masks SIGPIPE (as part of my workaround): 92722 tclsh8.5 CALL sigaction(SIGPIPE,0x7fffa9e0,0) 92722 tclsh8.5 RET sigaction 0 This 0-size write must be part of the pipe-closing -- descriptors 4 and 5 must be the pipe's: 92722 tclsh8.5 CALL write(0x4,0x800e24028,0) 92722 tclsh8.5 RET write -1 errno 32 Broken pipe 92722 tclsh8.5 PSIG SIGPIPE caught handler=0x800f126d0 mask=0x0 code=0x0 92722 tclsh8.5 CALL sigreturn(0x7fffa0c0) 92722 tclsh8.5 RET sigreturn JUSTRETURN 92722 tclsh8.5 CALL close(0x5) 92722 tclsh8.5 RET close 0 92722 tclsh8.5 CALL close(0x4) 92722 tclsh8.5 RET close 0 Why would it write 0 bytes? Is doing so triggering a SIGPIPE now -- but, perhaps, didn't use to? Thanks! -mi ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Can close-ing a pipe trigger a SIGPIPE?
On Sat, Oct 17, 2009 at 01:41:22PM -0400, Mikhail T. wrote: Kostik Belousov wrote: Take ktrace of both parent and child. Great idea! Here is the kdump's listing for both (after ktrace -i): http://aldan.algebra.com/~mi/tmp/tclx-kdump.txt (it is large, so be sure to use a compressing browser). Once loaded, look for substring: Error SIGPIPE signal received while closing file5. The parent process-ID is 92722. The child -- 92723. Thanks! Yours, The interesting part of the ktrace: 92723 tclsh8.5 CALL exit(0) 92722 tclsh8.5 CALL sigaction(SIGPIPE,0x7fffa9e0,0) 92722 tclsh8.5 RET sigaction 0 92722 tclsh8.5 CALL write(0x4,0x800e24028,0) 92722 tclsh8.5 RET write -1 errno 32 Broken pipe 92722 tclsh8.5 PSIG SIGPIPE caught handler=0x800f126d0 mask=0x0 code=0x0 92722 tclsh8.5 CALL sigreturn(0x7fffa0c0) 92722 tclsh8.5 RET sigreturn JUSTRETURN 92722 tclsh8.5 CALL close(0x5) 92722 tclsh8.5 RET close 0 92722 tclsh8.5 CALL close(0x4) 92722 tclsh8.5 RET close 0 It seems unwise to assume that a write(2) of 0 bytes is a noop. Even if it is, doing it is a waste of a system call. -- Jilles Tjoelker ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Can close-ing a pipe trigger a SIGPIPE?
Jilles Tjoelker написав(ла): It seems unwise to assume that a write(2) of 0 bytes is a noop. Even if it is, doing it is a waste of a system call. This is not my code -- it is part of the implementation of Tcl's close command. I'm trying to unravel, where this write coming from, but, meanwhile, it would be useful to find out, if FreeBSD's handling of such writes changed recently, wouldn't it? Because this self-test used to pass cleanly before, so either FreeBSD changed, or the Tcl did (not the TclX extension, which did not change in years). Thanks for your help... -mi ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Can close-ing a pipe trigger a SIGPIPE?
On Sat, Oct 17, 2009 at 01:53:55PM -0400, Mikhail T. wrote: Kostik Belousov написав(ла): Take ktrace of both parent and child. I can see the curious piece right here: The child exits: 92723 tclsh8.5 CALL exit(0) The parent masks SIGPIPE (as part of my workaround): 92722 tclsh8.5 CALL sigaction(SIGPIPE,0x7fffa9e0,0) 92722 tclsh8.5 RET sigaction 0 This 0-size write must be part of the pipe-closing -- descriptors 4 and 5 must be the pipe's: 92722 tclsh8.5 CALL write(0x4,0x800e24028,0) 92722 tclsh8.5 RET write -1 errno 32 Broken pipe 92722 tclsh8.5 PSIG SIGPIPE caught handler=0x800f126d0 mask=0x0 code=0x0 92722 tclsh8.5 CALL sigreturn(0x7fffa0c0) 92722 tclsh8.5 RET sigreturn JUSTRETURN 92722 tclsh8.5 CALL close(0x5) 92722 tclsh8.5 RET close 0 92722 tclsh8.5 CALL close(0x4) 92722 tclsh8.5 RET close 0 Why would it write 0 bytes? Is doing so triggering a SIGPIPE now -- but, perhaps, didn't use to? Obviously, I cannot answer the question. This is something that should be read from source code or asked by authors. pgpgDQxjtN6v2.pgp Description: PGP signature
Re: USB keyboards and extra keys
On Sat, 17 Oct 2009 12:38:10 +0200 Torfinn Ingolfsen torfinn.ingolf...@broadpark.no wrote: On Fri, 16 Oct 2009 23:54:40 -0500 Zane C.B. v.ve...@vvelox.net wrote: Any one ever manage to get extra keys to work on a USB keyboard in the RELENG_7 branch? In the past, I have used hotkeys[1] from ports for this. I don't have that keyboard now, so I can't test if it still works. Unfortunately that does not work. The extra keys on USB keyboards don't result in any thing visible to xev. Also usbhidctl does not show any thing happening on the uhid device that is created by the keyboard. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: bootless!
2009/10/17 Clifford, Ken ken.cliff...@mirror-image.com: Take me off this fucking list!@ From the bottom of the email you just sent: freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org You're welcome. Chris -- A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in a mailing list? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: bootless!
Look at the footers of this email for how to remove yourself. Swearing will not get you any where, and is likely to result in people not helping you. Clifford, Ken wrote: Take me off this fucking list!@ From: owner-freebsd-sta...@freebsd.org [owner-freebsd-sta...@freebsd.org] On Behalf Of Randy Bush [ra...@iij.ad.jp] Sent: Friday, October 16, 2009 9:13 PM To: FreeBSD-STABLE Mailing List Subject: bootless! i386 running 7.2 as of aug 29 twe, gmirrored boot partition, zfs universe cvsupped 24 hours ago new kernel world will not boot. get beastie but stops at first twirly can boot old kernel -s, but not new kernel can not use old kernel with new world, hangs if i try to /etc/rc.d/zfs start am desperate enough that i am flying from dc to seattle see if i can get it revved back to aug 29 with a fixit any clues appreciated. please use From: address, as my normal email is guess where. randy ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: bootless!
is there a recipe for making a 7.2 usb? randy ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: USB keyboards and extra keys
On Sat, 17 Oct 2009 13:02:52 -0500 Zane C.B. v.ve...@vvelox.net wrote: Unfortunately that does not work. The extra keys on USB keyboards don't result in any thing visible to xev. Well, it did on mine. YMMV. Also usbhidctl does not show any thing happening on the uhid device that is created by the keyboard. Perhaps that particular keyboard is broken by design? -- Torfinn ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: bootless!
Randy Bush wrote: is there a recipe for making a 7.2 usb? randy ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org If you mean for converting the ISOs to images you can dd to USB flash drives, http://acm.poly.edu/~spawk/image.sh. I found it somewhere else a long time ago, but it works. Note that you cannot install distributions from it, so you'll have to get those using FTP, another local filesystem, etc. -Boris ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Can close-ing a pipe trigger a SIGPIPE?
Kostik Belousov написав(ла): This 0-size write must be part of the pipe-closing -- descriptors 4 and 5 must be the pipe's: 92722 tclsh8.5 CALL write(0x4,0x800e24028,0) 92722 tclsh8.5 RET write -1 errno 32 Broken pipe 92722 tclsh8.5 PSIG SIGPIPE caught handler=0x800f126d0 mask=0x0 code=0x0 92722 tclsh8.5 CALL sigreturn(0x7fffa0c0) 92722 tclsh8.5 RET sigreturn JUSTRETURN 92722 tclsh8.5 CALL close(0x5) 92722 tclsh8.5 RET close 0 92722 tclsh8.5 CALL close(0x4) 92722 tclsh8.5 RET close 0 Why would it write 0 bytes? Is doing so triggering a SIGPIPE now -- but, perhaps, didn't use to? Obviously, I cannot answer the question. This is something that should be read from source code or asked by authors. You -- or someone else -- could comment like: a) Yeah, the meaning of write-ing 0 bytes changed in version such and such to conform to such and such standard. or b) No, nothing changed in that area of FreeBSD for years -- there must be something in Tcl itself. Yours, -mi ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
