I'll say it again more clearly -- all of you whiners just plain suck.
We know you'll never write diffs, and it is up to you to prove us
wrong. If you don't write diffs, we have a difficult time feeling any
loss.
a software community is made of more than developers.
Clearly, you have no
The guy can be some stupid binary software with an if(uid!=root) bail();
People running arbitrary binary software requiring root on their systems
deserve what they get. You can not work around this stupidity by ANY policy.
that is not the case and is, in fact, the entire point of
That was the conversation in detail, nothing altered, nothing left
out, read and draw your own conclusions.
Conclusion: you are not contributing to the problem at all.
Sorry, I'm not angry, I'm focused and productive.
Nope, not productive at all in my opinion. Theo is right on the mark
# demo=
# if [ $demo == -n -o $demo == -e ]; then
echo bar
fi
# demo=-n
# if [ $demo == -n -o $demo == -e ]; then
echo bar
fi
ksh: [: -n: unexpected operator/operand
/home/lukeb
$ demo='-n'
/home/lukeb
$ if [[ $demo == '-n' || $demo == '-e' ]]; then print YUP; fi
YUP
/home/lukeb
$
2) Is there a nice and fast method to check the latest changes with the cvs
command?
cvs has a diff command that is clearly described in the manual page:
http://www.openbsd.org/cgi-bin/man.cgi?query=cvsapropos=0sektion=0manpath=OpenBSD+Currentarch=i386format=html
cmd1 21 $WHERE
This doesn't do what you think it does, which I'm assuming is redirect
stderr and stdout to $WHERE.
Hannah Schroeter wrote:
Hello!
On Sun, Apr 30, 2006 at 05:07:07PM +0200, Federico Giannici wrote:
My CD finally arrived and I immediately installed 3.9 in the first machine.
I immediately found a problem for me: it seems that the GENERIC kernel
no longer support the procfs filesystem.
I see old messages on various obsd related lists about ksh93 having
been at least considered for a package and it not clear if it every
was a package, but at any rate does not appear to be now.
I wondered if there is development on that or maybe unofficial
packages or something.
The reason
find /usr/src -name *.[c|h] -exec grep 'bpf.h' /dev/null {} \;
^(a) ^(b)
(a) I doubt there are any file names ending in a pipe symbol in /usr/src.
man ksh
The point being made is that '*.[ch]' is what you want. | does not
mean or in a character class in
9 matches
Mail list logo
