On Tue, Apr 04, 2000 at 05:28:52PM -0500, Matthew D. Fuller wrote:
> Hi Ben :)
Hello Matthew, always nice to "see" you.
> On Tue, Apr 04, 2000 at 05:41:05PM -0400, a little birdie told me
> that Ben Rosengart remarked
> > Hello all,
> > I am running a
Hello all,
I am running a 5.0-CURRENT system cvsup'd this afternoon, and sshd is
not working for me. When I try to start it, I get the following:
** RSA_PKCS1: Unable to find an RSA implemenation shared library.
** Install either the USA (librsaINTL.so) or International (librsaUSA.so)
** RSA li
the only win here is if bzip is used in an infrastructural
capacity (e.g. for packages and other install stuff), and it has been
pointed out that the savings on disk space are offset by the additional
memory requirements. If it won't be used for infrastructure, then why
can't it stay
level
round-trip time measurement would probably be more accurate, because
some routers treat ICMP and TCP packets differently.
--
Ben Rosengart
UNIX Systems Engineer, Skunk Group
StarMedia Network, Inc.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
s
to any query, and will rotate them.
--
Ben Rosengart
UNIX Systems Engineer, Skunk Group
StarMedia Network, Inc.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
nce)
I like this idea a *lot*.
--
Ben Rosengart
UNIX Systems Engineer, Skunk Group
StarMedia Network, Inc.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Mon, 3 Jan 2000, Bob Vaughan wrote:
> if there is interest in a week or so, I may dig out the old dirt, and post a
> summary of his antics on operlist a few years back. (but only if there is
> interest.)
I think it would be better for all concerned if we just let this die.
will
eventually want to update it, and I'd like to know when it's safe.
Thanks in advance.
--
Ben Rosengart
UNIX Systems Engineer, Skunk Group
StarMedia Network, Inc.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
onsibility of recommending -current
for a production site, but they'll be happy to share their own
experiences and let you come to your own conclusion.
--
Ben Rosengart
UNIX Systems Engineer, Skunk Group
StarMedia Network, Inc.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe
eat to have in /bin.
*ducking*
--
Ben Rosengart
UNIX Systems Engineer, Skunk Group
StarMedia Network, Inc.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
e yes.
As one who's missed chown at times when only root's mounted, I'm with Bill.
--
Ben Rosengart
UNIX Systems Engineer, Skunk Group
StarMedia Network, Inc.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
the
> root hole in -current or -stable, but are vulnerable to the DoS
> attacks.
I'd be happier if you said the message was *from* the security officer. :-)
--
Ben Rosengart
UNIX Systems Engineer, Skunk Group
StarMedia Network, Inc.
To Unsubscribe: send mail to [EMAIL PROTECTED]
On Mon, 15 Nov 1999, Forrest Aldrich wrote:
> Will we be updating 4.0-current to the latest BIND-8.22-P5?
Or -stable for that matter? I believe these changes are eminently
qualified, being bugfixes.
--
Ben Rosengart
UNIX Systems Engineer, Skunk Group
StarMedia Network, Inc.
s redirected to -chat.
--
Ben Rosengart
UNIX Systems Engineer, Skunk Group
StarMedia Network, Inc.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Mon, 8 Nov 1999, Theo PAGTZIS wrote:
> What are your views?
I think it's fine the way it is. It took me a few minutes to wrap my
mind around the FreeBSD release and patching schemata, but ever since
then, they've treated me pretty well.
--
Ben Rosengart
UNIX Systems Engineer
On Fri, 29 Oct 1999, Doug White wrote:
> I still hate the way the signal change was handled.
How would you have done it differently? As I understand it, the pain
was more or less inevitable.
--
Ben Rosengart
UNIX Systems Engineer, Skunk Group
StarMedia Network, Inc.
To Unsubscribe: s
eek doesn't have a huge amount of resources,
and the amount they're likely to dedicate to defending a case like this
is minimal, I suspect.
Followups to -chat.
--
Ben Rosengart
UNIX Systems Engineer, Skunk Group
StarMedia Network, Inc.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with
You're talking as if litigious corporations follow logic and common
sense. This is more the exception than the rule IMO.
Don't construe this as arguing against the inclusion of trek73 ... I
think you're probably right that the risk is minimal, but for different
reasons.
--
Ben
artition. Nobody yet has said anything but 'that's
> interesting...'. A direction to look would be helpful.
I believe "synchronous" refers only to metadata writes. So it would
follow that the async writes are non-metadata writes.
--
Ben Rosengart
UNIX Syste
orrectly, it only needs to be done once per system, but
it makes no difference whether it happens on a given system now or six
months from now.
--
Ben Rosengart
UNIX Systems Engineer, Skunk Group
StarMedia Network, Inc.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebs
I understand the ISP's POV here, but I have legitimate reasons to telnet
to port 25 on various machines (most of them administered by me), and
I'd never dream of using an ISP that would stop me from doing so.
--
Ben Rosengart
UNIX Systems Engineer, Skunk Group
StarMedia Network,
Mutual respect is the glue that holds FreeBSD together, IMHO. As such,
it should not be discarded lightly.
--
Ben Rosengart
UNIX Systems Engineer, Skunk Group
StarMedia Network, Inc.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the b
"n"! Up with "/"!
No, up with '?'.
--
Ben Rosengart
UNIX Systems Engineer, Skunk Group
StarMedia Network, Inc.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
screen.
>
> Nice helpful error message.. can anyone shed some light on that?
If I were you, I would truss it:
$ truss -o truss.out compupic
and see what it's doing just before it dies.
--
Ben Rosengart
UNIX Systems Engineer, Skunk Group
StarMedia Network, Inc.
To Uns
On Sat, 14 Aug 1999, Sheldon Hearn wrote:
> On Fri, 13 Aug 1999 15:17:47 -0400, Ben Rosengart wrote:
>
> This looks like PR material. :-)
conf/13147
--
Ben
UNIX Systems Engineer, Skunk Group
StarMedia Network, Inc.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsub
I submit that putting "-z" in here is silly, because the sample cvsup
config files turn on compression, and suggest commenting it out if you
have a fast link. It seems counterintuitive that one can comment out
the compression in the standard supfiles and then have it enabled by
default with "make
On Wed, 11 Aug 1999, Brian F. Feldman wrote:
> What in the world would be the point of doing this? What would be so great
> about not seeing the system boot up?
One might want minimal or no boot messages, just to look nice, while
still wanting the dmesg stuff around in case something goes wrong
On Sat, 3 Jul 1999, Greg Lehey wrote:
> I personally think that, in such a case, you'd be justified to commit
> it as a temporary measure. Due to the difference in time zones, this
> has hit people while I've been asleep. That doesn't mean the commit
> would stay, of course, but at least it wou
On Fri, 25 Jun 1999, Scot W. Hetzel wrote:
> What is happening is /etc/defaults/rc.conf pulls in /etc/rc.conf, which then
> pulls in /etc/rc.conf repeat until we run out of file descriptors.
I am not fond of the new defaults/rc.conf system. Used to be when I
wanted to modify something in r
On Mon, 7 Jun 1999, John W. DeBoskey wrote:
> ps: I am a heavy user of the scripted install process. I beleive we
> could help our cause by better documenting how the process works
> and providing some examples.
As someone who is soon going to have to set up scripted installs, I
would cer
On Mon, 7 Jun 1999, Chuck Robey wrote:
> On Tue, 8 Jun 1999, Peter Jeremy wrote:
> >
> > I have an alternative compromise - add an option to make(1) so it
> > will ignore the `@' symbol. The following adds a `-@' option (the
> > option letter could be easily changed). I haven't updated make.1,
Hi,
I am curious as to why tcp_wrappers are present in /usr/src/contrib as
well as in the ports collection. Can someone please enlighten me? TIA.
--
Ben
UNIX Systems Engineer, Skunk Group
StarMedia Network, Inc.
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-c
32 matches
Mail list logo
