Re: Remove Heimdal Kerberos from my FreeBSD
On Saturday 16 July 2005 17:43, Vladimir Terziev wrote: Hi, i've just installed a fresh FreeBSD 5.4 on my PC i saw i have Heimdal Kerberos installed on it. I don't want Heimdal Kerberos on my syetem! Could someone point me to a easy way to remove it and rebuild all software (telnet, ssh, etc) which depends on it? In /etc/make.conf put NO_KERBEROS=yes Then build a new world. That should do the trick. I think freebsd-questions@freebsd.org would have been a more appropriate place to ask this question. Thanks in advance! Vladimir ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED] -- Dominic Marks ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Remove Heimdal Kerberos from my FreeBSD
On Sunday 17 July 2005 02:26, Dominic Marks wrote: In /etc/make.conf put NO_KERBEROS=yes Then build a new world. That should do the trick. This won't remove it, it will just not update it. You would have to delete it by hand. Telnet/ssh/etc don't have to depend on Kerberos and if you use the above option they will be built without Kerb support. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au The nice thing about standards is that there are so many of them to choose from. -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C pgpiQh0hFtWi5.pgp Description: PGP signature
Re: Remove Heimdal Kerberos from my FreeBSD
Yes, i deleted it along with all libs related to it. This caused telnet/ssh/etc to stop working. So i rebuilt the world with NO_KERBEROS=yes and now all is like a charm -- no Heimdal Kerberos and no software depending on it. I think making the Heimdal Kerberos part of the base FreeBSD OS is bad idea, but linking base software (like telnet, ssh), which is part of the base FreeBSD OS, against it, is very very bad idea. Vladimir On Sun, 17 Jul 2005 22:02:04 +0930 Daniel O'Connor [EMAIL PROTECTED] wrote: On Sunday 17 July 2005 02:26, Dominic Marks wrote: In /etc/make.conf put NO_KERBEROS=yes Then build a new world. That should do the trick. This won't remove it, it will just not update it. You would have to delete it by hand. Telnet/ssh/etc don't have to depend on Kerberos and if you use the above option they will be built without Kerb support. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au The nice thing about standards is that there are so many of them to choose from. -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
rfc: wake on lan patches for review
Hello Hackers, I have written a patch for the if_sis driver that enables wake on lan on the NatSemi DP8381[56] network chip. This did not work before because the driver needs to explicitely configure the card to enter wake on lan mode on system shutdown. I also added ioctls to make wake events configurable from userspace, and added an according 'wakeon events' command to ifconfig. The ioctls should be general enough to be used with other chips that require a similar configuration procedure for wake on lan. Before making efforts to get this committed I'd appreciate any comments and suggestions you may have. I'd especially appreciate people trying this at home if they have access to a network card with above mentioned chip. If you have a different card with wake on lan support that did not yet work as expected (i.e. your box does not wake up after shutting it down from FreeBSD), and have a datasheet available you might want to have a look at my code as an example on how to add wake on lan support to your card's driver. In my case, there wasn't much more to it than writing a couple of registers during the driver's shutdown procedure and implementing the new ioctls. You can find the patch at http://stsp.in-berlin.de/wol/ The patch applies cleanly to -current as of July 17th, and will probably apply to RELENG_6 just as well. regards, -- stefan http://stsp.in-berlin.de PGP Key: 0xF59D25F0 ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Remove Heimdal Kerberos from my FreeBSD
On Sunday 17 July 2005 22:16, Vladimir Terziev wrote: Yes, i deleted it along with all libs related to it. This caused telnet/ssh/etc to stop working. So i rebuilt the world with NO_KERBEROS=yes and now all is like a charm -- no Heimdal Kerberos and no software depending on it. I think making the Heimdal Kerberos part of the base FreeBSD OS is bad idea, but linking base software (like telnet, ssh), which is part of the base FreeBSD OS, against it, is very very bad idea. Well you're entitled to your opinion but you might like to back it up with reasons.. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au The nice thing about standards is that there are so many of them to choose from. -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C pgp5xaUfb741i.pgp Description: PGP signature
Re: rc.d ppp dependency
[EMAIL PROTECTED] wrote: Hi when using ppp together with pf there seems to exist a dependency problem. I start ppp and pf with : ppp_enable=YES and pf_enable=YES in rc.conf. At startup when the pf rulefile is loaded, the tun0 (which I use in the pf config) device does not yet exist and therefore the rules can not load. I noticed that in /etc/rc.d/ppp-user, ipfilter is resynced after ppp has started. Shouldn't the same be done for pf? thanks Stefan P.S. a similar problem exists with sshd when a ListenAddress directive is used with an address configured to tun0 Attn: I have been trying to get the same exact problem dealt with for ipnat and renaming interfaces. It appears that under FreeBSD 5-Stable, that although we are welcome to rename a network interface (like fxp0) to whatever we want (say out0), there seems to be a problem with the order in which things happen at boot. RENAMING happens after the ipnat has started, and so I feel that we need to re-sync ipnat after the renaming occurs. Otherwise, ipnat seems to have the old interface names, and ipnat will not work. Notice that in the rcorder of things, we see this (I skipped a bunch for brevity): ipfilter ... ipmon ... ipnat ipfs ... netif (interface renaming occurs; resync of ipfilter) isdnd ppp-user ipfw dhclient nsswitch ip6addrctl atm2 routing ip6fw network_ipv6 mroute6d route6d mrouted routed NETWORKING ... pflog pf pppoed ... localpkg natd What I see is that we need an IF-THEN-ELSE statement in the rcorder system someplace, that can notify pf if ppp is being used, and that will force ipnat to reload, etc. The ppp-user file, as you say, might need to reload pf if necessary. A simple patch could be thought up and attached here, huh? Can you post some of these comments as a bug (PR) to the FreeBSD system? I have one that could probably be fixed if my patch is used. See my related PR at http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/81606 You might refer to PR 81606 as potentially being a similar issue with rcng. These thigns are slowly coming to light. rcng has got a lot of little tweaks it needs, especially if we start to let ports interact with the system rcng files. Billy ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
