[EMAIL PROTECTED] (FreeBSD mailing list) writes:
> You know people, it's quite sad that those with knowledge simply
> refuse to answer simple questions without "RTFM" attitudes and
> indirect (and more frequently direct) insults to intelligence and
> sensibilities.
The answer `run mergemaster' w
Oliver Fromme <[EMAIL PROTECTED]> writes:
> Apart from my stupidness of not checking the location of the
> binary first -- what did I do wrong, and what's the recommended
> way of handling this? Am I supposed to rm /usr/bin/ssh each
> time I install a new release or snapshot? I can't believe
>
Jim Bloom <[EMAIL PROTECTED]> writes:
> That small test works fine, but doesn't solve the problem I was having.
Oops. Sorry.
kai
--
~/.signature: No such file or directory
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Jim Bloom <[EMAIL PROTECTED]> writes:
> No. It has the same bug. That method of concatenation only works
> for strings.
Well, I tried it and got the following:
/
| $ cat foo
| #define rule(ADDR,MASK) add pass tcp from ADDR ## : ## MASK to any 25 setup
| rule(192.168.2.5,255.255.254.0)
| $
Jim Bloom <[EMAIL PROTECTED]> writes:
> On the old version of current this expands to
>
> add pass tcp from 192.168.2.5:255.255.254.0 to any 25 setup
>
> but on a new version of current this expands to
>
> add pass tcp from 192.168.2.5 : 255.255.254.0 to any 25 setup
You might wis
Paul Richards <[EMAIL PROTECTED]> writes:
> The daemon approach actually has benfits that I'm keen on that aren't
> related to security. A single point of access to the data means that the
> backend can be changed so that passwords can be in a different file or a
> database, without having to wor
"Jordan K. Hubbard" <[EMAIL PROTECTED]> writes:
> I'm not totally inflexible about making the engineering vs user
> argument either, don't get me wrong, but this one is perilously in the
> middle and bringing something like openssh in as a companion to
> openssl would certainly raise my estimatio
Omachonu Ogali <[EMAIL PROTECTED]> writes:
> ===> lib/libcom_err/doc
> install-info --quiet --defsection="Programming & development tools." --defentry="*
>libcom_err: (com_err).A Common Error Description Library for UNIX."
>com_err.info /usr/share/info/dir
> install-info: unrecognize
"Jordan K. Hubbard" <[EMAIL PROTECTED]> writes:
> I really kinda wish you'd point them to Novice^H^H^H^H^HStandard
> instead since it does more than be a bit more verbose, it also makes
> sure that all the appropriate steps are covered and prevents even
> relatively skilled people from hanging th
Alexander Leidinger <[EMAIL PROTECTED]> writes:
> XF86Setup needs tcl/tk. tcl/tk needs XFree86. If there's no tcl/tk
> XF86Setup isn't compiled. After installing tcl/tk and rebuilding XFree86
> there should be a XF86Setup binary.
May I humbly suggest that this be put somewhere into the
documenta
SSIA, pretty much. I also installed /usr/ports/x11/XFree86-contrib
which doesn't contain that program, either. Did I do something wrong?
I installed a minimal 3.1 from CD (without X11), then made the
-CURRENT world, then installed the above mentioned ports. All of this
a week or so ago; I forg
[EMAIL PROTECTED] (Kai Großjohann) writes:
> * Then I had to compile and install a -CURRENT kernel. For this, I
> needed "cd /usr/src/usr.bin/genassym; make install" and "cd
> /usr/src/usr.sbin/config; make install".
Thanks to Daniel who pointed out that this
"Daniel C. Sobral" <[EMAIL PROTECTED]> writes:
> Kai Großjohann wrote:
> >
> > I now think that I should have made a new kernel, first.
> >
> > Hm. The file /usr/src/UPDATING doesn't say that I should,[...]
>
> UPDATING does say you need
Quite a few steps were necessary to go from 3.1 to -CURRENT which I
think are not explained anywhere. Maybe it would be useful to add
this to /usr/src/UPGRADING?
* First, I ran a `make buildworld'. Nothing special here.
* Then I had to compile and install a -CURRENT kernel. For this, I
need
[EMAIL PROTECTED] (Kai Großjohann) writes:
> I used my running 3.4 stable to run `make buildworld' on the sources
> from 2000-02-04 or so. I ran across the xinstall problem but worked
> around it, then tried `make installworld', which failed and hosed my
> machine. In o
I used my running 3.4 stable to run `make buildworld' on the sources
from 2000-02-04 or so. I ran across the xinstall problem but worked
around it, then tried `make installworld', which failed and hosed my
machine. In order to make sure that the xinstall workaround wasn't
the problem, I installe
16 matches
Mail list logo
