Re: Suggestion for change of /usr/src/UPDATING (was: Re: HEADS UP! Always use the 'make buildkernel' target to make yer kernels)
Mark Ovens wrote: > > On Wed, Aug 02, 2000 at 10:49:12AM -0700, John Reynolds~ wrote: > > > > [ On Wednesday, August 2, Warner Losh wrote: ] > > > : I am not in favour of putting *that* in UPDATING. Either suggest an > > > : appropriate entry in /boot/loader.conf: > > > > > > Actually, make installkernel was fixed so that you don't need to do > > > this. > > > > > > > It was? Did I miss a "HEADS UP" somewhere along the line? I knew that this was > > the behavior in -current and it was going to be "MFC"ed ``at some point'' but > > when did it occur? > > > > Seems like this would screw people like me who edited their /boot/loader.conf > > file unless we change it back to look for /kernel. > > > > Thanks for the notice ... I'll make sure to look at stuff and edit > > /boot/loader.conf appropriately before I type "reboot" the next time :) > > > > If you add > > makeoptions KERNEL=kernel #Build kernel "foo" and install "/foo" > > to your kernel config file it will install it as /kernel without this > change; and back up your old one as /kernel.old. I would expect this > line in the config file will be harmless (albeit redundant) when the > change is MFC'd so you won't have to edit /boot/loader.conf. I have to make a point here and that is I like the current arrangement. I would much rather have installkernel make a file called MYKERNEL than have it make all kernel's as "kernel". I think that as we follow Stable or Current, we need to create a GENERIC that goes along with them. When you don't have a clue, boot GENERIC. It may not solve anything but it is a data point. I don't like having all of my kernels called kernel because of this. I would much rather mv RUBY to kernel than mv kernel to kernel.GENERIC or GENERIC and re-installkernel for RUBY. I follow upgrades with my general setup and only at significant places do I create a GENERIC. I have a shell script that moves RUBY, for example, to kernel and I don't touch GENERIC. Kent > > HTH > > > -Jr > > > > -- > > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > > | John Reynolds WCCG, CCE, Higher Levels of Abstraction | > > | Intel Corporation MS: CH6-210 Phone: 480-554-9092 pgr: 602-868-6512 | > > | [EMAIL PROTECTED] http://www-aec.ch.intel.com/~jreynold/ | > > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > > with "unsubscribe freebsd-stable" in the body of the message > > -- > If I buy a copy of WinDelete, and it doesn't delete Windows, > am I entitled to my money back? > > 51.44°N FreeBSD - The Power To Serve http://www.freebsd.org > 2.057°W My Webpage http://ukug.uk.freebsd.org/~mark > mailto:[EMAIL PROTECTED]http://www.radan.com > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ Bomber dropping fire retardant in front of Hanford Wild fire. http://kstewart.urx.com/kstewart/bomber.jpg To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: telnet connection refused from IP outside subnet
> : comment out the PARANOID line in /etc/hosts.allow? > : #ALL : PARANOID : RFC931 20 : deny > Yes. This PARANOID option is really quite silly since RFC 931 is > useless outside of your own administrative domain and off dubious > value inside it. Best to leave it commented out. > Warner The RFC931 part may be silly, but the PARANOID part keeps out any ip address that does not reverse DNS to a name. We find that useful. - Tim To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
4.1-REL bootloader failure
-BEGIN PGP SIGNED MESSAGE- hi there, i recently tried to install an 4.1-REL (2 Floppies) on an dual i386 SCSI HD 1/2 gig RAM over FTP and chose the expert mode or whatever it is called again in the Installation-Menu. However everything went just fine, but after a reboot the bootloader just couldn't find a kernel to boot. I repeated the procedure 2 more times thereafter but the result remained the same, is there something i should know about installing via FTP ? :-)) or perhaps something has changed on the installation disks ? oh fun facts: annoyed by that unexpected denial of service i chose to install OpenBSD instead and , believe it or not, just came to the point to check its dmesg just to realize that it doesnt support SMP yet :(( :)) yours kinda sincerely, Stefan Schmidt - -- Q: What's the difference between Bell Labs and the Boy Scouts of America? A: The Boy Scouts have adult supervision. -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.0 (FreeBSD) Comment: Made with pgp4pine iD8DBQE5iJxVukA5Jvp3yMERARpTAJ4+Rp5zFU03b/jtgywfNFa3RWwOZwCffQ0q SXdhIpAlpvD38ZR+1BCGMzs= =YM1b -END PGP SIGNATURE- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Suggestion for change of /usr/src/UPDATING (was: Re: HEADS UP! Always use the 'make buildkernel' target to make yer kernels)
On Wed, Aug 02, 2000 at 10:49:12AM -0700, John Reynolds~ wrote: > > [ On Wednesday, August 2, Warner Losh wrote: ] > > : I am not in favour of putting *that* in UPDATING. Either suggest an > > : appropriate entry in /boot/loader.conf: > > > > Actually, make installkernel was fixed so that you don't need to do > > this. > > > > It was? Did I miss a "HEADS UP" somewhere along the line? I knew that this was > the behavior in -current and it was going to be "MFC"ed ``at some point'' but > when did it occur? > > Seems like this would screw people like me who edited their /boot/loader.conf > file unless we change it back to look for /kernel. > > Thanks for the notice ... I'll make sure to look at stuff and edit > /boot/loader.conf appropriately before I type "reboot" the next time :) > If you add makeoptions KERNEL=kernel #Build kernel "foo" and install "/foo" to your kernel config file it will install it as /kernel without this change; and back up your old one as /kernel.old. I would expect this line in the config file will be harmless (albeit redundant) when the change is MFC'd so you won't have to edit /boot/loader.conf. HTH > -Jr > > -- > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > | John Reynolds WCCG, CCE, Higher Levels of Abstraction | > | Intel Corporation MS: CH6-210 Phone: 480-554-9092 pgr: 602-868-6512 | > | [EMAIL PROTECTED] http://www-aec.ch.intel.com/~jreynold/ | > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message -- If I buy a copy of WinDelete, and it doesn't delete Windows, am I entitled to my money back? 51.44°N FreeBSD - The Power To Serve http://www.freebsd.org 2.057°W My Webpage http://ukug.uk.freebsd.org/~mark mailto:[EMAIL PROTECTED]http://www.radan.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: telnet connection refused from IP outside subnet
On Wed, 2 Aug 2000, [gill] wrote: > check ps -ax to make sure the daemon is up They are (syslogd and sshd). > run the daemon /usr/local/sbin/sshd -d and watch the debug info > run the client ssh -v for verbose I'll try this and play around a little more tonight. > are you running 4.0-RELEASE, 4.1-RELEASE, or -STABLE? Stable. Oh, and for anyone else who wonders (already received a few helpful emails ;), yes I did HUP the daemons after making configuration changes. Thanks. -mrh To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Suggestion for change of /usr/src/UPDATING (was: Re: HEADS UP! Always use the 'make buildkernel' target to make yer kernels)
> In message <[EMAIL PROTECTED]> Nate Williams writes: > : > : That's wrong. 'shutdown now' takes you to single user mode. 'shutdow > n -r now' > : > : will make it reboot. > : > > : > That's changed since the last time I did shutdown then :-). Of > : > course, that was 5 years ago or so... > : > : It's been that way since 4.3BSD, at least. Not sure which OS you were > : using at the time, since it's been the same since 386BSD days. :) > > SunOS (well, Solbourne's OS/MP), I think. Of course, I might have > always typed -h and just spaced it. SunOS had -h. Shutdown has behaved basically the same since I started working w/ BSD systems in 1983 (BSD 4.2). Mark > > Warner > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message -- Mark Andrews, Nominum Inc. 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Suggestion for change of /usr/src/UPDATING (was: Re: HEADS UP! Always use the 'make buildkernel' target to make yer kernels)
Neil Blakey-Milner wrote: > > Marcel's changes mean that you the tools you use to install the world > are ones that you can run with the old kernel. However, once they're > installed, you may not be able to run the new binaries with the old > kernel. In all, you "should" boot the kernel, and you "might" get away > with not doing it, but "you're on your own" if you mess up. This is correct. The change allows us to have a single 'upgrade' target that builds the world, builds the kernel, installs the kernel, installs the world, perform various other upgrades and finally end with a reboot (not necessarily in this exact order, although ending with a reboot seems kind of mandatory :-) The advantage of the change is also that it allows installworld to be run with -j > 1. We now simply never run what we install and thus avoid race conditions... -- Marcel Moolenaar mail: [EMAIL PROTECTED] / [EMAIL PROTECTED] tel: (408) 447-4222 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: ipv6
On Tue, Aug 01, 2000 at 17:40 -0400, Nader Turki wrote: > > I just installed FreeBSD 4.1-RELEASE. Well, I got this new > thing that's called IPv6 older versions of FreeBSD never asked > me that before. Anyway I said YES and hope that's not gonna > casue me any trouble. 'cause i have no idea what ipv6 is. If you're curious about it try something like "man -k ipv6". If you don't know what _that_ means try "man man". And get used to make use of the locally available info, it will serve you faster than waiting for others to hold your hands. (You should already know about this when using FreeBSD for a longer time. virtually yours 82D1 9B9C 01DC 4FB4 D7B4 61BE 3F49 4F77 72DE DA76 Gerhard Sittig true | mail -s "get gpg key" [EMAIL PROTECTED] -- If you don't understand or are scared by any of the above ask your parents or an adult to help you. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Suggestion for change of /usr/src/UPDATING (was: Re: HEADS UP! Always use the 'make buildkernel' target to make yer kernels)
In message <[EMAIL PROTECTED]> Nate Williams writes: : > : That's wrong. 'shutdown now' takes you to single user mode. 'shutdown -r now' : > : will make it reboot. : > : > That's changed since the last time I did shutdown then :-). Of : > course, that was 5 years ago or so... : : It's been that way since 4.3BSD, at least. Not sure which OS you were : using at the time, since it's been the same since 386BSD days. :) SunOS (well, Solbourne's OS/MP), I think. Of course, I might have always typed -h and just spaced it. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Suggestion for change of /usr/src/UPDATING (was: Re: HEADS UP! Always use the 'make buildkernel' target to make yer kernels)
In message <[EMAIL PROTECTED]> Nate Williams writes: : Warner, I think you are confused. 'shutdown now' takes you to single : user mode. 'halt' will take you to the above prompt. I was confused between shutdown now and shutdown -h now. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Irda support
Hmmm, show this to your linux buddies
http://www.rewls.nu/takeittux.jpg
Jason Kasper <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]
08/02/2000 01:55 PM
Please respond to freebsd-stable
To: [EMAIL PROTECTED]
cc:
Subject:Irda support
I realize this may be slightly off-topic, but for the life of me, I
can't find any reference anywhere
(google/altavista/deja.com/freebsd.org/etc.) that would indicate that
anybody is even looking at irda support for freebsd. Are there any
plans to support irda in the freebsd kernel in the upcoming time-frame?
Far be it from me to encourage holy wars, but it gets tiring hearing the
linux-user crowd chortling over their kernel's ability to do irda when
mine can't.
Thanks in advance
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=
Jason Kasper (vanRijn)
Systems Engineer
bash$ :(){ :|:&};:
VORFA
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
Re: making a RELEASE [should make buildworld made before?]
Makoto MATSUSHITA wrote: > > obrien> However, today's buildworld is more resilent having better > obrien> build-tools, etc.. targets than when release/Makefile was > obrien> first written. Maybe this need could be removed. But this > obrien> hasn't happened yet. > > If I understand the facts of src/release/Makefile correctly, > > - First 'make installworld' under /usr/src is for "creating a chroot > environment for further release engineering." Maybe it can be > supercedesed by copying existing environment or just extracting > 'bin' distribution. But there is no tool for this. Yes, and just doing a make installworld is the easiest way to do this. > - Second 'make buildworld' inside a chroot environment is the actual > build procedure. Obviously, it cannot remove :-) > > - Second 'make installworld' inside a chroot environment is for > "creating an environment for further _actual_ release procedures." > Even though we have much much better procedures for build-tools, > _actual_ release procedures (release.[1-9], doc.?, cdrom.?, and > ftp.? target in src/release/Makefile) does not consider about > that. If these procedures requires newer version of toolchain, it > should be a release-breaker. Well, it is similar to the reason we have build-tools, etc. in the world. We want to make sure that we have tools that match the release Makefile we are using. Also, it is a good test, since we need to make sure that the sources can do an actual installworld before we ship them out to people. :) -- John Baldwin <[EMAIL PROTECTED]> -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Suggestion for change of /usr/src/UPDATING (was: Re: HEADS UP! Always use the 'make buildkernel' target to make yer kernels)
> : That's wrong. 'shutdown now' takes you to single user mode. 'shutdown -r now' > : will make it reboot. > > That's changed since the last time I did shutdown then :-). Of > course, that was 5 years ago or so... It's been that way since 4.3BSD, at least. Not sure which OS you were using at the time, since it's been the same since 386BSD days. :) Nate To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Suggestion for change of /usr/src/UPDATING (was: Re: HEADS UP! Always use the 'make buildkernel' target to make yer kernels)
> : > : [1] > : > : --> reboot <-- > : > : > : [...] > : > : This line should be "shutdown now", isn't it? Any further suggestions to > : > : make life of Warner easier? > : > > : > No. It should be "reboot" since that's the simplest thing. "shutdown > : > now" doesn't cause the machine to reboot, but merely causes the > : > processor to halt. It is the same thing as "halt," unless you have > : > users on the machine, in which case they will get a nice message > : > before the machine dies > : > : Um, not in my experience. Shutdown now shuts you down to single > : user mode without rebooting, it does *not* do a halt. > > No. shutdown now takes you all the way down to "hit any key to > reboot" *AND* you want to reboot. Warner, I think you are confused. 'shutdown now' takes you to single user mode. 'halt' will take you to the above prompt. Nate To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: making a RELEASE
On Wed, Aug 02, 2000 at 11:42:50AM +0100, Dominic Mitchell wrote: > > I cvsup-ed all src collections, including ports and doc (i.e. src-all, > > doc-all and ports-all). ... > > Wich path should I give to CVSROOT dir ? > > You need to download the the cvs collections, not the "checked-out" > collections for make release to work. You could also set CVSROOT to the anoncvs.freebsd.org service. This would be slower, but save you disk space. -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: making a RELEASE [should make buildworld made before?]
Hi, > I cvsup-ed all src collections, including ports and doc (i.e. src-all, doc-all and >ports-all). You should fetch cvs collection. Btw, I missed to find, that "make buildworld" is mandatory before make release (It failed in several places, if I didn't build the world). Therefore, during make release world is recompiled at least two times. Is it a normal operation? With respect, Domas Mituzas dbit.lt, network systems engineer To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: making a RELEASE
On Wed, 2 Aug 2000 [EMAIL PROTECTED] wrote: > Hi, > > I cvsup-ed all src collections, including ports and doc (i.e. src-all, doc-all and >ports-all). > > I went to /usr/src/release and tried to "make release". It asked me to provide >CVSROOT variable. And oops.. I am confused ... :-) > > Wich path should I give to CVSROOT dir ? > > Any documentation regarding "make release" procedure ? > http://www.FreeBSD.org/FAQ/hackers.html#CUSTREL - Chris D. Faulhaber - [EMAIL PROTECTED] - [EMAIL PROTECTED] FreeBSD: The Power To Serve - http://www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: making a RELEASE
On Wed, Aug 02, 2000 at 07:23:13AM -0400, Chris BeHanna wrote: > SLOW DOWN! > > "make release" will make the iso images (right?) no, make release make only ftp,cd-version of install tree, no image > > What he wants, I suspect, is to cd to /usr/src and follow the > instructions in /usr/src/UPDATING. -- Laa To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: making a RELEASE
On Wed, 2 Aug 2000, Dominic Mitchell wrote: > On Wed, Aug 02, 2000 at 01:34:00PM +0100, [EMAIL PROTECTED] wrote: > > Hi, > > > > I cvsup-ed all src collections, including ports and doc (i.e. src-all, > > doc-all and ports-all). > > > > I went to /usr/src/release and tried to "make release". It asked me to > > provide CVSROOT variable. And oops.. I am confused ... :-) > > > > Wich path should I give to CVSROOT dir ? > > You need to download the the cvs collections, not the "checked-out" > collections for make release to work. > > > Any documentation regarding "make release" procedure ? > > % less /usr/src/release/Makefile SLOW DOWN! "make release" will make the iso images (right?) What he wants, I suspect, is to cd to /usr/src and follow the instructions in /usr/src/UPDATING. Regards, Chris BeHanna [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: is fetch broken?
Matt Heckaman <[EMAIL PROTECTED]> writes: > *nods* It still breaks wmstock though, it never sees itself as getting the > complete file and errors out, and keeps on trying making temporary files > that it never knows are correct :) Thank you for the quick diagnoses > though, it's appreciated. Quick fix (I think): Index: http.c === RCS file: /home/ncvs/src/lib/libfetch/http.c,v retrieving revision 1.34 diff -u -r1.34 http.c --- http.c 2000/07/25 11:45:38 1.34 +++ http.c 2000/08/02 11:17:09 @@ -770,8 +770,7 @@ struct url *url, *new; int chunked, need_auth, noredirect, proxy, verbose; int code, fd, i, n; -off_t offset; -size_t clength, length, size; +off_t offset, clength, length, size; time_t mtime; char *p; FILE *f; Now, the question is why gcc didn't warn me about this... DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Suggestion for change of /usr/src/UPDATING (was: Re: HEADS UP! Always use the 'make buildkernel' target to make yer kernels)
Johan Karlsson <[EMAIL PROTECTED]> writes: > This has been taken care of in current but in a slightly different way. > When using the build/installkernel targets the built / installed kernel > is named 'kernel' > Hence, when these changes are MFC:ed this part is not needed at all in > UPDATING. > > I think it is better to MFC than adding this :-) Good news. I would appreciate if that is going to be announced here and not silently done. Roland To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: making a RELEASE
On Wed, Aug 02, 2000 at 01:34:00PM +0100, [EMAIL PROTECTED] wrote: > Hi, > > I cvsup-ed all src collections, including ports and doc (i.e. src-all, > doc-all and ports-all). > > I went to /usr/src/release and tried to "make release". It asked me to > provide CVSROOT variable. And oops.. I am confused ... :-) > > Wich path should I give to CVSROOT dir ? You need to download the the cvs collections, not the "checked-out" collections for make release to work. > Any documentation regarding "make release" procedure ? % less /usr/src/release/Makefile :-) -Dom To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
making a RELEASE
Hi, I cvsup-ed all src collections, including ports and doc (i.e. src-all, doc-all and ports-all). I went to /usr/src/release and tried to "make release". It asked me to provide CVSROOT variable. And oops.. I am confused ... :-) Wich path should I give to CVSROOT dir ? Any documentation regarding "make release" procedure ? 10x. p.s. please CC: [EMAIL PROTECTED] --- Plamen D. Petkov, ICQ# 2214327 [EMAIL PROTECTED] First Bulgarian Internet Store http://www.bgstore.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: cvs commit: ports/www/mozilla Makefile ports/www/mozilla/files md5 ports/www/mozilla/patches patch-ai ports/www/mozilla/pkg PLIST
On Tue, Aug 01, 2000 at 11:47:33PM -0400, Coleman Kane wrote: > Still, this is no excuse for changing the port without asking the > maintainer Obviously, something's amiss. I compiled it yesterday on my 4.1-STABLE at home, and it would fail with some really obscure messages. After a bit of looking around, I realized some files in /usr/X11R6/lib/mozilla or thereabouts where only readable by root - silly that, they seem to be related to the GUI, chmod go+rx fixed it. As it is, the port should only run by root. Not a major problem with the port then. For those of you that built mozilla M16, DO try /usr/ports/www/galeon. HTH, K. Konstantinidis To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: sendmail 8.11.0
On Tue, Aug 01, 2000 at 09:16:46PM -0700, Crist J . Clark wrote: > On Tue, Aug 01, 2000 at 02:03:57PM -0600, Chris Fedde wrote: > > My point is that there is a perfectly good mechinism in existance to allow > > switching between MTA. The rc.conf mechinism works well and is consistant > > for all other components of the system. In this one case we add a layer of > > indirection below rc.conf. > > Why not simply use something like > > > > mta_enable="YES" > > mta=/usr/sbin/sendmail > > or > > mta_ena > > mta=/usr/sbin/qmail > > > > and the appropriate frag in /etc/rc to work with this > > I find the whole mailwrapper thing bizarre in the extreem ;-) > > But that will only affect the MTA listening for relays. It will not > change what executable a program trying to send mail on the local > machine will exec to send mail... Unless now everything that sends > mail has to source rc.conf first. Yuck. Precisely. Like it or not, /usr/sbin/sendmail has become an interface to sending mail and is *not* exclusive to sendmail. -Dom (Paid up member of the Sendmail Must Die club) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Suggestion for change of /usr/src/UPDATING (was: Re: HEADS UP! Always use the 'make buildkernel' target to make yer kernels)
At 02 Aug 2000 09:58:04 +0200, Roland Jesse wrote: > Siegbert Baude <[EMAIL PROTECTED]> writes: > > > ---Begin Suggestion--- > > Not bad, but: > > > # Verify that the new kernel works, it will be installed as > > # /YOUR_KERNEL_HERE > > chflags noschg /kernel > > chflags noschg /YOUR_KERNEL_HERE > > mv /kernel /kernel.old > > mv /YOUR_KERNEL_HERE /kernel > > chflags schg /kernel > > I am not in favour of putting *that* in UPDATING. Either suggest an > appropriate entry in /boot/loader.conf: > > # Make sure that the new kernel gets booted the next time > # you reboot by putting the following line in > # /boot/loader.conf: > kernel="/YOUR_KERNEL_HERE" > > Or (and that's what I like more and do) in the section where one > modifies her kernel config file: > > # Make sure that the kernel gets installed as /kernel and > # therefore gets loaded at boot time. Put a "kernel" entry > # in your kernel config file, like this: > makeoptions KERNEL=kernel This has been taken care of in current but in a slightly different way. When using the build/installkernel targets the built / installed kernel is named 'kernel' Hence, when these changes are MFC:ed this part is not needed at all in UPDATING. I think it is better to MFC than adding this :-) /Johan K To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: telnet connection refused from IP outside subnet
On Tue, 1 Aug 2000 [EMAIL PROTECTED] wrote: > Actualy, I don't have 'login failers'. I just can't > connect! "Connection refused", not login failer! I do not get login > prompt at all! Correct... However, per inetd(8), wrapped services log failed attempts using the auth syslog facility. > 'host' is ok in both directions (host and host gives the > same name/IP). Can I assume resolving is ok ? You did this from your server, not your home system, correct? Just checking, since inetd will obviouslly be using the DNS of your server to see if a given host is allowed. Do you have the same problem if you comment out the PARANOID line in /etc/hosts.allow? #ALL : PARANOID : RFC931 20 : deny What's a traceroute look like from the disallowed connection to the server, and from the server to your disallowed IP? > If i could force things to be logged somehow :-) I can send my > /etc/syslog.conf if it will be of help ? Hmm, I understand your pain... I just attempted to make sshd log failed attempts and... I must be overlooking something really simple, because it's not working. I looked at inetd(8) and sshd(8). I have the following in /etc/ssh/sshd_config by default: SyslogFacility AUTH LogLevel INFO So I created the following in /etc/syslog.conf (Yes, those are tabs): auth.* /var/log/auth.log In sshd_config I even tried bumping LogLevel up to VERBOSE. I touched /var/log/auth.log and it is writeable by syslogd. I then removed an allow rule for one of my boxes, ssh'd in, and got denied without anything being logged to auth.log. Sshd is standalone... So logging behavior relating to inetd shouldn't matter, but I noticed mention of daemon.* being used by inetd so tried logging those too... Still nothing. Hmm. -mrh To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
