Re: Belkin 8-port KVM = keyboard inactive
On Fri, 19 Apr 2002, Brian J. McGovern wrote: *Is the problem in the FreeBSD probe or this particular KVM switch? I don't *recall having this problem with my Belkin Omnicube. Is anybody having *problems with other KVM switches besides the Omniview 8-port? * *Yes, I have several 4 port switches that do the same thing (no keyboard/mouse *on reboot if they're not the active machine). I believe that some of *my Black Box switches also do this, although I can't confirm this at this *time. * * -Brian Strange, I have a 4 port Belkin that works fine, and have just purchased another. Hope it works ;-) -George --- George Yobst, Library Technology Specialist phone: 503.723.4890 Library Information Network of Clackamas County fax: 503.794.8238 16239 SE McLoughlin Blvd, Suite 208 web: http://www.lincc.lib.or.us Oak Grove, OR 97267-4654 email: [EMAIL PROTECTED] ...it is impossible for anyone to begin to learn what he thinks he already knows. - Epictetus To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Add note to UPDATING (was: Re: inetd_enable
k Hi Doug, k your commit to etc/defaults/rc.conf 1.53.2.53 k change the default for inetd and sendmail in Stable. k Both used to be YES and are now NO Actually, I didn't even notice this. I would like to put the sendmail_enable default back to YES in the branch for the sake of POLA. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
strange things with sendmail and quotas on STABLE
Given user Quotas for user test123: /var/mail: blocks in use: 20048, limits (soft = 2, hard = 2) inodes in use: 2, limits (soft = 0, hard = 0) OK, they are over their limit. No problem. What is strange is why does granite# mail -v test123 Subject: Your mailbox is full Hello, you are over the 20MB limit. You must clean out your old mail in order to get new mail EOT test123... Connecting to localhost.sentex.net. via relay... etc... work? This gets delivered, where as in the past it would bounce. Now even stranger, if I try and send a large message thats over a certain size, it will bounce as expected. granite# wc /tmp/r.out 3514650 34236 /tmp/r.out granite# cat /tmp/r.out | mail -s test ignore test123 This message bounces. Apr 19 16:09:46 granite sm-mta[52050]: g3JK9ksf052049: to=[EMAIL PROTECTED], ctladdr=[EMAIL PROTECTED] (1001/1001), delay=00:00:00, xdelay=00:00:00, mailer=local, pri=64850, relay=local, dsn=5.2.2, stat=Service unavailable (/var/mail/test123: Disc quota exceeded) Apr 19 16:09:46 granite sm-mta[52050]: g3JK9ksf052049: g3JK9ksf052050: DSN: Service unavailable (/var/mail/test123: Disc quota exceeded) This did not used to be this way. Any ideas what might have changed this behaviour ? This is a buildworld from Thu Apr 18. ---Mike Mike Tancsa, tel +1 519 651 3400 Sentex Communications,[EMAIL PROTECTED] Providing Internet since 1994www.sentex.net Cambridge, Ontario Canada www.sentex.net/mike To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Inetd not-starting gotcha.
On Fri, 19 Apr 2002, Frank Mayhar wrote: (CC'd to -stable again, so the people in question can see the praise. :-) Mike Hoskins wrote: On Fri, 19 Apr 2002, Frank Mayhar wrote: This change _did_ deserve a heads-up, at least to -stable. Sigh. Wow, commiters are human too? :) _Believe_ me, I'm not slamming Doug. Sueee. :) Y'all are correct, in my ideal world people would have learned about this change because they saw the diff when they ran mergemaster... but that didn't happen for everyone. I was working on an email about this anyway, I'll finish it now. Mea culpa. -- We have known freedom's price. We have shown freedom's power. And in this great conflict, ... we will see freedom's victory. - George W. Bush, President of the United States State of the Union, January 28, 2002 Do YOU Yahoo!? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
*** HEAD'S UP ***
Howdy, Apparently my last message wasn't clear enough, for which I apologize. In addition to the general, non-life-threatening changes to /etc I did recently, a few more fundamental things have changed as well, specifically to /etc/defaults/rc.conf. Rather than focus on the specifics, I'd like to suggest a more general solution. I highly recommend backing up your existing rc.conf[.local], and copying /etc/defaults/rc.conf to /etc/rc.conf. Then, go through the whole file, and explicitly include your choices for anything that you care about, whether they are the defaults or not. In this way, you can be sure that the system will always behave the way you want it to. In addition to this, I generally include the settings that are specific to the individual machine (like hostname, gateway, ifconfig_) in /etc/rc.conf.local. That way it's easier to blat the rc.conf file periodically. I also added an option to mergemaster to compare your rc.conf[.local] stuff to what's in /etc/defaults/rc.conf after you're done updating. To take advantage of that, use 'mergemaster -C', or 'echo COMP_CONFS=yes .mergemasterrc'. What this won't show you is differences to the defaults that you don't have in /etc/rc.conf[.local]. For that, you're expected to pay attention to the diff of /etc/defaults/rc.conf as you install it. :) Any questions, comments, or suggestions... fire away. -- We have known freedom's price. We have shown freedom's power. And in this great conflict, ... we will see freedom's victory. - George W. Bush, President of the United States State of the Union, January 28, 2002 Do YOU Yahoo!? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: *** HEAD'S UP ***
Date: Fri, 19 Apr 2002 15:37:27 -0700 (PDT) From: Doug Barton [EMAIL PROTECTED] Sender: [EMAIL PROTECTED] Howdy, Apparently my last message wasn't clear enough, for which I apologize. In addition to the general, non-life-threatening changes to /etc I did recently, a few more fundamental things have changed as well, specifically to /etc/defaults/rc.conf. Rather than focus on the specifics, I'd like to suggest a more general solution. I highly recommend backing up your existing rc.conf[.local], and copying /etc/defaults/rc.conf to /etc/rc.conf. Then, go through the whole file, and explicitly include your choices for anything that you care about, whether they are the defaults or not. In this way, you can be sure that the system will always behave the way you want it to. In addition to this, I generally include the settings that are specific to the individual machine (like hostname, gateway, ifconfig_) in /etc/rc.conf.local. That way it's easier to blat the rc.conf file periodically. I also added an option to mergemaster to compare your rc.conf[.local] stuff to what's in /etc/defaults/rc.conf after you're done updating. To take advantage of that, use 'mergemaster -C', or 'echo COMP_CONFS=yes .mergemasterrc'. What this won't show you is differences to the defaults that you don't have in /etc/rc.conf[.local]. For that, you're expected to pay attention to the diff of /etc/defaults/rc.conf as you install it. :) Any questions, comments, or suggestions... fire away. OK. You asked for it... I really hate to see the suggestion that people copy files from /etc/defaults to /etc. This really breaks the paradigm of having only changes in defaults in /etc so that defaults can be changed with a normal system update. While the new mergemaster option helps with this, I would really rather not see rc.conf (and other files) become large and not trivial to scan over. A suggestion to scan through /etc/defaults/rc.conf is not unreasonable. Of course, people SHOULD pay attention to whet mergemaster has to say, but even I have messed up when updating an important server and not watching all of the things mergemaster showed in an effort to get the system back on-line quickly. R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: [Freenet6] Does Apache-2 listen for IPv6 on a 6to4 network?
On Fri, Apr 19, 2002 at 06:08:29PM +1000, Robert wrote:
Thanks Edwin...
Well, at least someone can see it :-) It's set to answer only IPv6 enquiries
at the moment.
and does IE understand IPV6? good question ? It's version 6, on W2K - but
that doesn't mean a lot.
Is there a browser that does ?
Mozilla does, so Galeon will do too :-)
But for the rest I have no idea if Netscape Navigator does these
days, or if Opera supports it. After all, it's a chicken and egg
problem :-/
Edwin
--
Edwin Groothuis | Personal website: http://www.MavEtJu.org
[EMAIL PROTECTED]|Interested in MUDs? Visit Fatal Dimensions:
bash$ :(){ :|:};: |http://www.FatalDimensions.org/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-stable in the body of the message
Re: [Freenet6] Does Apache-2 listen for IPv6 on a 6to4 network?
Is there a browser that does ? Mozilla does, so Galeon will do too :-) But for the rest I have no idea if Netscape Navigator does these days, or if Opera supports it. After all, it's a chicken and egg problem :-/ As of last nights Mozilla download, it doesn't on W2K-Advanced Server with SP2, nor does anyting else, because the file wininet.dll is not upgradable on this setup. It's been designed for earlier versions and hasn't caught up yet. Robert To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
checkout-date in kernel name
Hello, I want to have the checkout date in the kernel name, e.g. # uname -sr FreeBSD 4.5-STABLE-20020418 instead of # uname -sr FreeBSD 4.5-STABLE I've done this by patching /sys/conf/newvers.sh. Is there an easier way to do this? Kind regards, Thomas. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Antigen Notification:Antigen found VIRUS= HTML.MimeExploit (CA(Vet)) virus
Antigen for Exchange found Unknown infected with VIRUS= HTML.MimeExploit (CA(Vet)) virus. The file is currently Removed. The message, ¥¸Ëªþ¥úºÐ, was sent from nbm and was discovered in SMTP Messages\Outbound located at University of Missouri/Tigers/TIG-MSXPROTO1. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
/etc/defaults/rc.conf theory
On Fri, 19 Apr 2002, Kevin Oberman wrote: I really hate to see the suggestion that people copy files from /etc/defaults to /etc. This really breaks the paradigm of having only changes in defaults in /etc so that defaults can be changed with a normal system update. But that was never the paradigm. There are a few different ideas about why the defaults file should exist (none of which I'm particularly fond of, btw) but silently changing defaults out from under the users isn't really all that good of an idea, no matter how well intentioned it might be. The one rational reason for having the defaults file is to create a reasonable environment at startup for fresh installs. Given that everything in inetd.conf is commented out, it's reasonable not to start that daemon. The sendmail issue is a little more enigmatic, given that in order for local processes to send outgoing mail it's now necessary to have a sendmail daemon running... it could be argued that changing the defaults in both branches is reasonable at this point. (Technically, there is another good reason for the defaults file, namely that new options should always be defaulted to off when they are introduced. However, that is both abused, and not used consistently, so I'd much rather see /usr/share/examples/rc/*, or something to that effect. But I digress.) While the new mergemaster option helps with this, I would really rather not see rc.conf (and other files) become large and not trivial to scan over. The problem is, if an option exists, it has to be documented somewhere. While fraught with danger, the existing situation isn't HORRIBLE... but it does need help. Of course, people SHOULD pay attention to whet mergemaster has to say, but even I have messed up when updating an important server and not watching all of the things mergemaster showed in an effort to get the system back on-line quickly. I agree that we should provide safety nets whenever possible... that's been one of my main areas of work in the project. But, at some point, it's still on you when you push 'i' for install. This ain't windows. :) -- We have known freedom's price. We have shown freedom's power. And in this great conflict, ... we will see freedom's victory. - George W. Bush, President of the United States State of the Union, January 28, 2002 Do YOU Yahoo!? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Add note to UPDATING (was: Re: inetd_enable
On Fri, 19 Apr 2002, Gregory Neil Shapiro wrote: Actually, I didn't even notice this. I would like to put the sendmail_enable default back to YES in the branch for the sake of POLA. The more I think about this, the more I think it might need to be yes in both places. Is there a way to configure new sendmail to accept outgoing connections without needing daemons running? If so, it might make more sense to have that be the default setup, and leave the _enable off both places. If not, we should probably turn it on both places, with just the outgoing mail stuff set up by default. -- We have known freedom's price. We have shown freedom's power. And in this great conflict, ... we will see freedom's victory. - George W. Bush, President of the United States State of the Union, January 28, 2002 Do YOU Yahoo!? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
user 'smmsp' and NO_SENDMAIL= true
Hello, I've checked out STABLE today. The update (installworld) failed because I don't have a user/group 'smmsp'. As I'm using postfix, I don't need/want this user. In rc.conf I have NO_SENDMAIL= true. What is the way to upgrade? Kind regards, Thomas. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
