Re: Out of file descriptors ??
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 rc.conf, I opened it up and changed the value. Now I have to extract a line from defaults/rc.conf, put it in rc.conf, and change it -- unless I don't understand the new setup correctly. That makes more work for me, not less. What's the idea here? -- Ben 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
Re: Fixing other people's code (was: world broken in vinum (PATCH))
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 would save people unnecessary > pain. Note, of course, that I have now committed the correct file, > which I had forgotten last night. > > What do you others think? Was the fix that wasn't yours correct? 'Cause I'd rather have code that doesn't compile than code that compiles but is subtly wrong. -- Ben 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
Re: it's time...
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 or they need to configure a kernel. It's certainly chrome, but I'd like it. -- Ben 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
SUPFLAGS in /etc/make.conf
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 update" anyway. Comments? -- Ben 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
Re: SUPFLAGS in /etc/make.conf
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 "unsubscribe freebsd-current" in the body of the message
Re: Your misleading, no, LYING message to me
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. -- 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
Re: multiple cd devices
On Fri, 31 Dec 1999, Wilko Bulte wrote: > As for ample warning: I've seen MAKEDEVs display a list of the devices > they are creating. I think the Tru64 version does this. I myself think this > is a good behaviour (and hope people won't start yelling 'bloat' for once) 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
Re: Please help spread the CVSup mirror load more evenly
On Sat, 22 Jan 2000, Andre Oppermann wrote: > Ah, well, ok. I used it extensively with bind 8.1.2 in an internal > application in a big bank to get approx. load distribution with > Windumb clients (they always take the first record in the list > returned). > > Anyway, if multi CNAME is no good then do: > > cvsup IN A198.104.92.71 ; cvsup1.freebsd.org > cvsup IN A205.149.189.91 ; cvsup2.freebsd.org > ... and so on > > This is legal, is it? Not only is it legal, but I believe BIND will return all the A records 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
Re: Please help spread the CVSup mirror load more evenly
On Fri, 21 Jan 2000, David O'Brien wrote: > Possibly, being ping'able should be be a requirement to being a CVSup > mirror. I don't think it makes sense to try to dictate network policy to people who are doing the FreeBSD Project a favor. Anyway, an application-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
Re: bzip2 in src tree
On Mon, 24 Jan 2000, Brad Knowles wrote: > And the only cost is the slight expansion of the amount of disk > space required to store the source code in /usr/src and the binaries > in /usr/bin [...] And the time and disk space required to make world. No thank you. Remember that 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 in ports? -- 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
Re: Anyone running CompuPic?
On Fri, 10 Sep 1999, Mike Muir wrote: > I get the same problem, after brandelfing to linux and running it, the > splash screen comes up and...disappears with: > > compupic: abnormal termination: (null) > > Brandelf -t FreeBSD segfaults it without even showing the splash 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 Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: more
On Sun, 12 Sep 1999, Chris Costello wrote: > On Sun, Sep 12, 1999, Rodney W. Grimes wrote: > > Not with me, and I am sure Warner and a few other die hard ``more'' users > > are going to be chimming in here as soon as they get to this... > >Down with "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
Re: ccd build failure
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 body of the message
Re: Filtering port 25 (was Re: On hub.freebsd.org refusing to talkto dialups)
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, Inc. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP: sigset_t changes committed
On Wed, 29 Sep 1999, Harold Gutch wrote: > I interpreted the way of currently handling things (build the > kernel first, then the userland) to be a _temporary_ solution, > that Marcel was working on being fixed. If this is not the case, > then I agree with you. If I understand correctly, 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 freebsd-current" in the body of the message
Re: make install trick
On Wed, 6 Oct 1999, Matthew D. Fuller wrote: > Indeed. > Thus: > /dev/da0s1a on / (local, synchronous, writes: sync 32 async 15100) > ^^^ > > Though I'm still waiting for an explanation of WHY exactly I have async > writes on a sync partition. 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 Systems Engineer, Skunk Group StarMedia Network, Inc. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: trek73
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 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
Re: trek73
On Mon, 25 Oct 1999, Jim Bryant wrote: > No matter what Lush Rimbaugh says on the topic, frivilous lawsuits > RARELY win in court. A lawsuit over this would indeed be frivilous. You don't have to win in court, you merely have to exhaust the resources of your opponent. Walnut Creek 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 "unsubscribe freebsd-current" in the body of the message
Re: -stable to -current
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: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ambiguity between -STABLE and -RELEASE
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, Skunk Group StarMedia Network, Inc. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: egcs unstable
On Sat, 13 Nov 1999, Marcel Moolenaar wrote: > BTW: I also don't need inline images, but I find xemacs more appealing > in an X env. Funny ... I only find xemacs useful when *not* using X, because that's where xemacs will do syntax coloring and emacs won't. Followups 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
Re: BIND update
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. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: BIND update
On Wed, 17 Nov 1999, Warner Losh wrote: > In message <[EMAIL PROTECTED]> Forrest Aldrich writes: > : So wouldn't be the impact if a server was compromized in the absence > : of an available fix :) > > A message to the security officer indicated that we don't have 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] with "unsubscribe freebsd-current" in the body of the message
Re: Speaking of moving files (Re: make world broken building fortunes )
On Mon, 13 Dec 1999, Bill Fumerola wrote: > On Mon, 13 Dec 1999, Louis A. Mamakos wrote: > > > So how about /usr/sbin/chown -> /sbin/chown so that MAKEDEV works with > > just the root file system mounted? > > As one who just got his ass bitten by this, I would vote 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
Re: Speaking of moving files (Re: make world broken building fortunes )
On Tue, 14 Dec 1999, Matthew Dillon wrote: > I think at one time or another all of us have missed *something* in > /usr that wasn't in /. For example, disklabel -e doesn't work without > vi -- which is in /usr. Good example of something else that would be great 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
Re: current for production?
On 20 Dec 1999, Fritz Heinrichmeyer wrote: > as there now is almost only talk about sound and ata drivers in this > list, would it be adviseable to use a current-snap on a server machine > (apache,samba,ftp) without need for sound and ata drivers (box with > aic-scsi-only drives)? > > The integrated gcc-2.95.2 is so handy and current does all i want on my > private box anyway. I think you'd have better luck asking people what their experiences with the software have been, rather than asking for a recommendation. No one is likely to want to take the responsibility 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 freebsd-current" in the body of the message
building world on pre-signals-change systems
If I recall correctly, someone posted recently that the time is not far off when one will be able to make world on an older, pre-signals-change system. Is there going to be an announcement when that happens, or has it perhaps happened already? I'm running an Oct 1 -current box, and I 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
sshd library problems
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 library on your system and run this program again.
Then a pointer to a doc (which I read), then it receives signal 11 and
dumps core.
(BTW, "implementation" is misspelled there.)
I have rsaref-2.0 installed from ports, and I have USA_RESIDENT=YES and
RSAREF=YES defined in /etc/make.conf. I've cvsupped from a new vanilla
standard-supfile, using the cvs-crypto collection.
Here are two lines from the output of "truss sshd":
access("/usr/lib/librsaINTL.so",0) = 0 (0x0)
open("/usr/lib/librsaINTL.so",0,027757770600)= 4 (0x4)
Needless to say, I find this slightly confusing. What am I doing wrong?
Thanks in advance.
--
Ben
"I didn't order any WOO-WOO... Maybe a YUBBA... But no WOO-WOO!"
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: sshd library problems
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 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 library on your system and run this program again.
>
> (Aren't those filenames reversed? Just a hunch...)
Hmm. As you can see in my truss output, it's librsaINTL.so that's
getting picked up.
> (ttypb):{54}% ll /usr/lib/librs*
> -r--r--r-- 1 root wheel 6358 Mar 14 04:03 /usr/lib/librsaUSA.a
> lrwxr-xr-x 1 root wheel14 Mar 14 04:03 /usr/lib/librsaUSA.so@ -> librsaUSA.so.1
> -r--r--r-- 1 root wheel 8080 Mar 14 04:03 /usr/lib/librsaUSA.so.1
> -r--r--r-- 1 root wheel 7122 Mar 14 04:03 /usr/lib/librsaUSA_p.a
I moved /usr/lib/librsaINTL* to a backup location, and now the ssh
programs no longer complain or dump core. I apparently shot myself in
the foot by building the world with USA_RESIDENT set to "NO" at some
point.
Thank you, Matthew!
--
Ben
"I didn't order any WOO-WOO... Maybe a YUBBA... But no WOO-WOO!"
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
tcp_wrapper in contrib and ports?
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-current" in the body of the message
Re: bsd.lib.mk "@"'s
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,
> > but will if the following is acceptable.
>
> That won't work on buildworld, where it takes full control of the make
> environment. You'll need to have *something* in the makefiles to allow
> for it.
Anyway, it seems much more drastic to change the user interface to
make(1) than to change a makefile. No?
I don't see what's wrong with the ${SILENT} suggestion.
--
Ben
UNIX Systems Engineer, Skunk Group
StarMedia Network, Inc.
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
Re: sysinstall manpage installation question
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 certainly love to see more documentation on this. > Along those lines, here is a .cfg file I use for a machine that I use > to test SNAPs on. Cool, thanks. -- Ben UNIX Systems Engineer, Skunk Group StarMedia Network, Inc. To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
