Re: The World and MIT krb5
On Wed, Dec 03, 2003 at 11:52:27AM -0800, Galen Sampson wrote: Hello all, snip [Note: I'm not sure that this should be in current@ rather than [EMAIL PROTECTED] 1) Are the worlds daemons written to link against kerberos (as apposed to the heimdal replacements replacing their traditional counterparts)? The MIT krb5 port includes it's own daemons. 4) Are people that use the MIT kerberos port replacing their daemons (telnet [d], login, ftp[d]) with the ports versions with good success? Yup. Or they're using the Heimdal daemons in the base system (as described in the handbook chapter on Kerberos 5). I prefer MIT myself, but that's largely because of unrelated benefits that may apply only in my situation. I'd imagine that since the port is installed in /usr/local things might not work so great if /usr/local can't be accessed (because of mount failure, etc.) unless the daemons are statically linked (NO THIS IS NOT A THREAD ABOUT STATIC LINKING, THIS IS AN OBSERVATION ABOUT THIS PORT AND A POSSIBLE ANSWER TO 3). I'm not sure what you're talking about here ... if the deamons are in /usr/local/, and the /usr/local isn't available, static linking isn't going to help :-) I tend to put them in /usr/local/krb5 so that I can control which application I get by default with creative $PATH ordering. -T -- From empirical experience, your Exchange admin needs to put down the crack pipe and open a window to disperse the fumes. - A.S.R. quote (Joe Thompson) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
[Tillman: Upgraded to latest -current today, boot hangs on ata3: resetting devices]
It occurs to me that this is likely related to the new interrupt code. that tends to imply that the fix is wait a few days and re-cvsup, but I thought folks here would be interested in seeing Sparc64 feedback. -T -- [It] contains vegetable stabilizer which sounds ominous. How unstable are vegetables? - A.S.R. quote (Jeff Zahn) ---BeginMessage--- The serial console shows this: atapci0: CMD 646 WDMA2 controller port 0xc00020-0xc0002f,0xc00018-0xc0001b,0xc00010-0xc00017,0xc8-0xcb,0xc0-0xc7 at device 3.0 on pci1 atapci0: [MPSAFE] ata2: at 0xc0 on atapci0 ata2: [MPSAFE] ata3: at 0xc00010 on atapci0 ata3: [MPSAFE] pcib2: APB PCI-PCI bridge at device 1.0 on pci0 pci2: OFW PCI bus on pcib2 pcib3: OFW PCI-PCI bridge at device 3.0 on pci2 pci3: OFW PCI bus on pcib3 pci3: bridge, PCI-unknown at device 0.0 (no driver attached) hme1: Sun HME 10/100 Ethernet mem 0x280-0x2807fff at device 0.1 on pci3 pcib3: slot 0 INTB is routed to irq 25 hme1: Ethernet address: 08:00:20:c6:7f:c7 miibus1: MII bus on hme1 ukphy0: Generic IEEE 802.3u media interface on miibus1 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto pci3: bridge, PCI-unknown at device 1.0 (no driver attached) hme2: Sun HME 10/100 Ethernet mem 0x480-0x4807fff at device 1.1 on pci3 pcib3: slot 1 INTB is routed to irq 26 hme2: Ethernet address: 08:00:20:c6:7f:c7 miibus2: MII bus on hme2 ukphy1: Generic IEEE 802.3u media interface on miibus2 ukphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto pci3: bridge, PCI-unknown at device 2.0 (no driver attached) hme3: Sun HME 10/100 Ethernet mem 0x680-0x6807fff at device 2.1 on pci3 pcib3: slot 2 INTB is routed to irq 27 hme3: Ethernet address: 08:00:20:c6:7f:c7 miibus3: MII bus on hme3 ukphy2: Generic IEEE 802.3u media interface on miibus3 ukphy2: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto pci3: bridge, PCI-unknown at device 3.0 (no driver attached) hme4: Sun HME 10/100 Ethernet mem 0x880-0x8807fff at device 3.1 on pci3 pcib3: slot 3 INTB is routed to irq 24 hme4: Ethernet address: 08:00:20:c6:7f:c7 miibus4: MII bus on hme4 ukphy3: Generic IEEE 802.3u media interface on miibus4 ukphy3: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto Timecounters tick every 0.976 msec IPsec: Initialized Security Association Processing. IP Filter: v3.4.31 initialized. Default = pass all, Logging = enabled ad0: WARNING - SETFEATURES recovered from missing interrupt ad0: WARNING - SETFEATURES recovered from missing interrupt ad0: WARNING - SET_MULTI recovered from missing interrupt ad0: WARNING - SETFEATURES recovered from missing interrupt GEOM: create disk ad0 dp=0xf8001087a6c0 ad0: 8223MB ST38410A [16708/16/63] at ata2-master WDMA2 acd0: WARNING - MODE_SENSE_BIG recovered from missing interrupt ata3: resetting devices .. It's an Ultra 5 with an IDE drive. I was previously running -current from after the 09/23 entry in UPDATING. Entries since then don't show anything particularly relevent. I ran cvsup before beginning the compile about 8:00am CST. Are there any known issues like this? Are there known solutions? Even a wait until foo is committed then re-cvsp would be great to hear ;-) I've tried load /boot/kernel.old/kernel from the boot loader to recover at least a booting system. This worked, though naturally my userland no longer matches my kernel. Should I be able to re-install a new kernel userland from this point safely? -T -- I'm getting a new desk soon! Desk goes up. Desk goes down. Desk goes up. Desk goes down. Desk goes up. Desk goes down. Desk goes up. Desk goes down. Desk goes up. Desk goes down. Desk goes up. Desk goes down. Lunch. Productivity is in the eyes of the beholder. - A.S.R. quote (Lars Balker Rasmussen) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-sparc64 To unsubscribe, send any mail to [EMAIL PROTECTED] ---End Message--- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [Tillman: Upgraded to latest -current today, boot hangs on ata3: resetting devices]
On Tue, Nov 04, 2003 at 02:20:19PM -0500, John Baldwin wrote: On 04-Nov-2003 Tillman Hodgson wrote: It occurs to me that this is likely related to the new interrupt code. that tends to imply that the fix is wait a few days and re-cvsup, but I thought folks here would be interested in seeing Sparc64 feedback. The new interrupt code did not affect sparc64, but only i386. Noted, I'll take this back to [EMAIL PROTECTED] Thanks for the info, -T -- Page 12: Unix is a set of tools for smart people. - Harley Hahn, _The Unix Companion_ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: cvsup sites are all at capacity?
On Tue, Sep 16, 2003 at 05:11:02PM -0500, Dan Nelson wrote:
In the last episode (Sep 16), Andrew Lankford said:
I've tried various cvsup sites (normally cvsup2 or cvsup16 ) and
each site returns this message:
Rejected by server: Access limit exceeded; try again later
I've gotten that before but never with all of the hosts out there.
Is everyone and their brother doing a make world today, are the sites
down for maintenance, or is something sinister going on?
cvsup4, 5, 9, 10, 11, 12, 13, 14, and 16 all work for me.
There's a port ('fastest_cvsup') that might be useful for folks.
-T
--
The envious man thinks that if his neighbor breaks a leg, he will be able
to walk better himself.
- Helmut Schoeck, _Envy: A Theory Of Social Behavior_
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Buildworld fails in 5.1
On Wed, Jul 16, 2003 at 02:24:18PM +, Bosko Milekic wrote: Same here, remove the -j N. Right now there seem to be some dependencies which you fail against with a parallel build. And it works here as well. Building with -j highlights a problem I'm seeing on a sparc64 though ... the stock Ultra 5 hard drive is abysmally slow. Bonnie++ reports: Version 1.93c --Sequential Output-- --Sequential Input- --Random- Concurrency 1 -Per Chr- --Block-- -Rewrite- -Per Chr- --Block-- --Seeks-- MachineSize K/sec %CP K/sec %CP K/sec %CP K/sec %CP K/sec %CP /sec %CP Caliban512M 8 95 1995 10 927 515 94 1893 6 54.9 17 Latency 1878ms 445ms2894ms1074ms 272ms5349ms Version 1.93c --Sequential Create-- Random Create Caliban -Create-- --Read--- -Delete-- -Create-- --Read--- -Delete-- files /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP 16 918 72 3008 82 2649 97 697 55 3112 89 2825 97 Latency 1665ms 51352us2797us1622ms 345ms2241us Compare this to a NFS mount (with options rw, intr, nfsv3, -w=32768, -r=32768) on the same box (an Ultra 5) from my vinum fileserver: Version 1.93c --Sequential Output-- --Sequential Input- --Random- Concurrency 1 -Per Chr- --Block-- -Rewrite- -Per Chr- --Block-- --Seeks-- MachineSize K/sec %CP K/sec %CP K/sec %CP K/sec %CP K/sec %CP /sec %CP Caliban512M4076 18 1764 174102 15 79.5 77 Latency 294ms 184ms 44630us1699ms This made the buildworld time /really/ slow: real1068m1.246s user904m49.768s sys 80m51.158s (buildkernel took about an additional ten hours). I'm hoping that replacing it with a more modern hard-drive should fix this, though I'll be poking through atacontrol and dmesg to see if it's a simple configuration problem. In the meantime it's actually faster for me to build off of an NFS mount. Heh. -T -- Page 461: Tools that are simple enough to use the first day are often a real pain after the first month. - Harley Hahn, _The Unix Companion_ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Buildworld fails in 5.1
On Wed, Jul 16, 2003 at 01:47:38PM -0400, Matt Loschert wrote: My buildworlds have been failing ever since the gcc 3.3 upgrade. I got the message that you got on one of the failures. However, my last three builds have consistently failed at the following point: Mine has as well, though I thought the issue was specific to sparc64 (I'm on an Ultra 5). I cvsup'ed up again this morning and am trying again with -jX. It'll take a while to find out as this box takes a long time to compile recent -CURRENT. I'm currently 5 hours into buildworld and it's on contrib/ncurses. My make.conf is as follows: CFLAGS= -O -pipe NOPROFILE= true COPTFLAGS= -O -pipe COMPAT3X= yes COMPAT4X= yes BOOTWAIT= 0 USA_RESIDENT= YES Same compile options as me, though I don't have COMPAT or BOOTWAIT. My 5.x test machine is an Athlon 750 with 256 MB of RAM, and 1 GB of swap. I am using a clean /usr/obj directory for each build. I am using -j 6 for the buildworld. Maybe that is the problems, I will try taking that out. I'd be interested in seeing if that works for you - it'll be a few hours before my run is finished so you'll know before I will ;-) -T -- Do not consciously seek enlightenment. -Muso Kokushi ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
