Re: Ability to tell the difference between normal and syscall traps

2010-05-14 Thread John Baldwin
Ali Polatel wrote: Kostik Belousov yazmış: On Mon, May 10, 2010 at 07:48:47PM +0300, Ali Polatel wrote: Another question is how hard is it to implement PL_EVENT_EXEC? This could be useful for truss as it updates the execution type of the process after successful execve() calls afaict. Is this

Re: Ability to tell the difference between normal and syscall traps

2010-05-14 Thread Kostik Belousov
On Fri, May 14, 2010 at 06:51:19AM -0400, John Baldwin wrote: > Ali Polatel wrote: > >Kostik Belousov yazm: > >>On Mon, May 10, 2010 at 07:48:47PM +0300, Ali Polatel wrote: > >>>Another question is how hard is it to implement PL_EVENT_EXEC? > >>>This could be useful for truss as it updates the

Re: Custom USB layout & sysinstall (Starting FIXIT)

2010-05-14 Thread none none
- Original Message - From: "Julian H. Stacey" To: rank1see...@gmail.com Cc: freebsd-hackers@freebsd.org, "Ken Smith" Date: Fri, 14 May 2010 00:11:04 +0200 Subject: Re: Custom USB layout & sysinstall (Starting FIXIT) > Hi, > rank1see...@gmail.com wrote: > > > So, I downloaded USB stick .i

Re: /dev/null & zero inside chroot for make release

2010-05-14 Thread Julian H. Stacey
Hi, Garrett Cooper wrote: > On May 13, 2010, at 2:06 PM, Jilles Tjoelker wrote: > > > On Thu, May 13, 2010 at 07:44:58PM +0200, Julian H. Stacey wrote: > >> Problem with /dev/null & /dev/zero inside a chroot: > >> I wanted to build a release from inside a chroot > > > >> What sort of null & zero

Re: Custom USB layout & sysinstall (Starting FIXIT)

2010-05-14 Thread Ken Smith
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 5/14/10 1:16 PM, none none wrote: > I've read it, all. > What he is proposing, is about building our own image flavor. > (make-memstick.sh) > Exactly, that act, is an issue here, as it confuses sysinstall's USB > detection. This part of what you

Re: proposed change to style(9): require yoda style if

2010-05-14 Thread Ryszard W. Czekaj
> The convincing one applies to Java and C++: > if (constant.equals(object)) > instead of > if (object != null && object.equals(constant)) > actually looks easier to read. > > Though you are right about constants being pretty rare. > > > Your .sig is strangely appropriate... > > Not m