alpha tinderbox failure

-- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree

i386 tinderbox failure

-- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree

alpha tinderbox failure

-- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree

alpha tinderbox failure

-- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree

alpha tinderbox failure

-- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree

alpha tinderbox failure

-- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree

i386 tinderbox failure

-- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree

sparc64 tinderbox failure

-- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree

alpha tinderbox failure

-- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree

sparc64 tinderbox failure

-- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree

sparc64 tinderbox failure

-- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree

alpha tinderbox failure

-- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree

sparc64 tinderbox failure

-- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree

i386 tinderbox failure

-- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree

i386 tinderbox failure

-- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree

i386 tinderbox failure

-- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree

i386 tinderbox failure

-- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree

i386 tinderbox failure

-- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree

i386 tinderbox failure

-- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree

sparc64 tinderbox failure

-- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree

i386 tinderbox failure

-- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree

sparc64 tinderbox failure

-- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree

i386 tinderbox failure

-- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree

sparc64 tinderbox failure

-- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree

sparc64 tinderbox failure

-- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree

sparc64 tinderbox failure

-- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree

sparc64 tinderbox failure

-- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree

sparc64 tinderbox failure

-- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree

sparc64 tinderbox failure

-- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree

sparc64 tinderbox failure

-- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree

sparc64 tinderbox failure

-- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree

i386 tinderbox failure

-- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree

i386 tinderbox failure

-- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree

i386 tinderbox failure

-- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree

i386 tinderbox failure

-- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree

i386 tinderbox failure

-- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree

i386 tinderbox failure

-- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree

i386 tinderbox failure

-- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree

i386 tinderbox failure

-- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree

i386 tinderbox failure

-- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree

i386 tinderbox failure

-- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree

i386 tinderbox failure

-- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree

i386 tinderbox failure

-- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree

i386 tinderbox failure

-- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree

i386 tinderbox failure

-- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree

sparc64 tinderbox failure

-- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree

Re: sshd doesn't log hostname into utmp correctly

you please submit it to [EMAIL PROTECTED]? DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message

sparc64 tinderbox failure

-- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree

Re: sshd doesn't log hostname into utmp correctly

Hajimu UMEMOTO [EMAIL PROTECTED] writes: des Could you please submit it to [EMAIL PROTECTED]? Yes, I'll sent it. Can I commit it to FreeBSD repo.? No, please wait and see what the OpenSSH developers say. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL

sparc64 tinderbox failure

-- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree

i386 tinderbox failure

-- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree

sparc64 tinderbox failure

-- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree

Re: minor OPIE + telnet nit

David O'Brien [EMAIL PROTECTED] writes: What I type for the password is not echoed. Yeah, thanks. I'll fix it ASAP. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message

Re: minor OPIE + telnet nit

Dag-Erling Smorgrav [EMAIL PROTECTED] writes: David O'Brien [EMAIL PROTECTED] writes: What I type for the password is not echoed. Yeah, thanks. I'll fix it ASAP. See revision 1.23 of src/lib/libpam/modules/pam_opie/pam_opie.c. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe

i386 tinderbox failure

-- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree

i386 tinderbox failure

-- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree

Re: Be careful mounting -stable partitions on -current

the alternate. I might have rebooted without unmounting the -stable partition. There's nothing wrong with your partition, but there's a bug in your version of fsck. You can fix your partition with 'fsck -b 32 -y', but you really should update your system. DES -- Dag-Erling Smorgrav - [EMAIL

Re: sparc64 tinderbox failure

Mike Barcroft [EMAIL PROTECTED] writes: Thanks. Do you want to increase the tinderbox to run twice a day? Sure, done. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message

sparc64 tinderbox failure

-- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree

Re: sparc64 tinderbox failure

Mike Barcroft [EMAIL PROTECTED] writes: Dag-Erling Smorgrav [EMAIL PROTECTED] writes: Mike Barcroft [EMAIL PROTECTED] writes: DES, there wasn't enough context on this to solve the problem. I don't really see what more you need. What's missing? The first line and cause of the subsequent

Re: sparc64 tinderbox failure

Dag-Erling Smorgrav [EMAIL PROTECTED] writes: Ah, looks like a bug in whereintheworld. It's not supposed to truncate error messages. I've hacked whereintheworld to print everything since the last '===' in case of an error, rather than just the last ten lines. If anyone is interested it's

i386 tinderbox failure

-- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree

sparc64 tinderbox failure

-- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree

i386 tinderbox failure

-- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree

i386 tinderbox failure

-- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree

sparc64 tinderbox failure

-- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree

sparc64 tinderbox failure

-- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree

Re: sparc64 tinderbox failure

buildkernel KERNCONF=${kc} -DNO_WERROR done DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message

sparc64 tinderbox failure

-- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree

i386 tinderbox failure

-- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree

sparc64 tinderbox failure

-- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree

sparc64 tinderbox failure

-- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree

sparc64 tinderbox failure

-- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree

Re: i386 tinderbox failure

Dag-Erling Smorgrav [EMAIL PROTECTED] writes: make: don't know how to make GENERIC. Stop Damn, my bad. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message

sparc64 tinderbox failure

-- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree

Re: VOP_GETATTR panic on Alpha

suggestions before I just turn off DEBUG_VFS_LOCKS? DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message

Re: VOP_GETATTR panic on Alpha

Andrew Kolchoogin [EMAIL PROTECTED] writes: sorry, kernel from today's sources at 17:38 works just fine. Try with DEBUG_VFS_LOCKS. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message

i386 tinderbox failure

-- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree

sparc64 tinderbox failure

-- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree

i386 tinderbox failure

-- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree

sparc64 tinderbox failure

-- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree

Re: Update to the DRM

. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message

sparc64 tinderbox failure

-- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree

Re: Update to the DRM

Eric Anholt [EMAIL PROTECTED] writes: Missed the N on my cvs diff -uN. New patch is uploaded, including not stripping FreeBSD ID tags. http://people.freebsd.org/~anholt/dri/files/currentdrm-20020711.diff Looks good, I'll rebuild reboot in a couple of minutes. DES -- Dag-Erling Smorgrav

sparc64 tinderbox failure

-- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree

Re: What to do with witness verbiage (is this new?)?

Alex Zepeda [EMAIL PROTECTED] writes: After the rude awakening that I was after all running current, I've finally turned on the WITNESS related options for my kernel Congratulations in turning your -CURRENT box into a doorstop! ;) DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED

Re: OPIE auth broken too (was Re: PasswordAuthentication not works in sshd)

Andrey A. Chernov [EMAIL PROTECTED] writes: Why what? Sysadmin allows PasswordAuthentication only. Why? DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message

Re: OPIE auth broken too (was Re: PasswordAuthentication not works in sshd)

Andrey A. Chernov [EMAIL PROTECTED] writes: On Wed, Jul 10, 2002 at 14:17:51 +0200, Dag-Erling Smorgrav wrote: Andrey A. Chernov [EMAIL PROTECTED] writes: Why what? Sysadmin allows PasswordAuthentication only. Why? Because he choose to not trust hosts keys which can be stolen especially

Re: OPIE auth broken too (was Re: PasswordAuthentication not works in sshd)

Andrey A. Chernov [EMAIL PROTECTED] writes: On Wed, Jul 10, 2002 at 15:02:43 +0200, Dag-Erling Smorgrav wrote: But why disable keyboard-interactive authentication? There is nowhere documented that keyboard-interactive auth is required for PasswordAuthentication. It works without it for ages

Re: Patch for review (was Re: OPIE auth broken too (was Re: PasswordAuthentication not works in sshd))

Neither fix is correct. The correct solution is to remove the kludge in auth-passwd.c that tries to use PAM for password authentication. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message

Re: sparc64 tinderbox failure

Giorgos Keramidas [EMAIL PROTECTED] writes: How does this look for fixing this warning? No, gcc should accept a NULL format string for err(3). It looks like __printf0like is broken. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED

Re: sparc64 tinderbox failure

-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message

sparc64 tinderbox failure

-- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree

Re: PasswordAuthentication not works in sshd

Andrey A. Chernov [EMAIL PROTECTED] writes: It not helps. Moreover, I found that I am able to do 'ssh localhost' but unable to do ssh from any other machine, with exact the same password. Try commenting out the pam_opieaccess line in /etc/pam.d/sshd. DES -- Dag-Erling Smorgrav - [EMAIL

Re: PasswordAuthentication not works in sshd

not present there. What if the client is untrusted? Do you find it reasonable to allow users to type their password on an untrusted client? Many of our users use OPIE for precisely this scenario - reading their mail on an untrusted machine in the USENIX terminal room. DES -- Dag-Erling Smorgrav

Re: PasswordAuthentication not works in sshd

no other utility in the base system does. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message

Re: OPIE auth broken too (was Re: PasswordAuthentication not works in sshd)

the hysteria a couple of notches and give me a proper bug report? DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message

sparc64 tinderbox failure

Mon Jul 8 07:00:00 GMT 2002 cvs [update aborted]: /home/ncvs/CVSROOT: Interrupted system call To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message

i386 tinderbox failure

-- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree

Re: sshd is complaining about /var/log/lastlog permission

, but it's harmless. I just haven't had time to sort it out yet. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message

<    1   2   3   4   5   6   7   8   9   10   >