From owner-freebsd-stable Sun Oct 22 01:43:25 1995 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id BAA29250 for stable-outgoing; Sun, 22 Oct 1995 01:43:25 -0700 Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id BAA29195 for ; Sun, 22 Oct 1995 01:42:03 -0700 Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.12/8.6.9) with SMTP id BAA06049; Sun, 22 Oct 1995 01:40:23 -0700 To: davidg@Root.COM cc: Heikki Suonsivu , stable@freebsd.org Subject: Re: 2.1.0-951020-SNAP - 2.1 *Release Candidate* In-reply-to: Your message of "Sat, 21 Oct 1995 23:01:53 PDT." <199510220601.XAA04220@corbin.Root.COM> Date: Sun, 22 Oct 1995 01:40:23 -0700 Message-ID: <6047.814351223@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-stable@freebsd.org Precedence: bulk > I don't know if I consider this a "critical" bug, however, as it might be > difficult to manifest during normal operations. I think that "slirp" must be > doing something strange - like an fchown() on a TTY. I'll have to look into > this in more detail. If "slirp" is manifesting it regularly, then I'd say that qualified for "normal operations", wouldn't it? I do know that the package is very popular, as Heikki mentions. Sort of the poor man's TIA, I think. Jordan From owner-freebsd-stable Sun Oct 22 04:40:47 1995 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id EAA04198 for stable-outgoing; Sun, 22 Oct 1995 04:40:47 -0700 Received: from Root.COM (implode.Root.COM [198.145.90.17]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id EAA04189 for ; Sun, 22 Oct 1995 04:40:38 -0700 Received: from corbin.Root.COM (corbin [198.145.90.50]) by Root.COM (8.6.12/8.6.5) with ESMTP id EAA00221; Sun, 22 Oct 1995 04:40:35 -0700 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.12/8.6.5) with SMTP id EAA04058; Sun, 22 Oct 1995 04:40:08 -0700 Message-Id: <199510221140.EAA04058@corbin.Root.COM> To: Heikki Suonsivu cc: "Jordan K. Hubbard" , stable@freebsd.org Subject: Re: 2.1.0-951020-SNAP - 2.1 *Release Candidate* In-reply-to: Your message of "Sun, 22 Oct 95 08:55:30 +0200." <199510220655.IAA12565@shadows.cs.hut.fi> From: David Greenman Reply-To: davidg@Root.COM Date: Sun, 22 Oct 1995 04:40:03 -0700 Sender: owner-stable@freebsd.org Precedence: bulk >Sorry, I forgot about using sed :-( I recommend removing any device drivers from your kernel that you are not using - the matcd driver, for instance, and many others. I need you to install and test the attached patches. This needs to be done *ASAP* if there will be any hope for these fixes to be in the 2.1 release. Please start testing these as soon as possible and tell me if they 1) fix the problem you are having and 2) don't cause any other problems. I'm especially interested in problems with NFS client operation and any new problems with msdosfs (I already know about it's old bugs :-)). I welcome feedback from other people, too... -DG Index: isofs/cd9660/cd9660_lookup.c =================================================================== RCS file: /home/ncvs/src/sys/isofs/cd9660/cd9660_lookup.c,v retrieving revision 1.7 diff -c -r1.7 cd9660_lookup.c *** 1.7 1995/05/30 08:04:57 --- cd9660_lookup.c 1995/10/22 11:08:09 *************** *** 142,147 **** --- 142,150 ---- return (ENOTDIR); if ((error = VOP_ACCESS(vdp, VEXEC, cred, cnp->cn_proc))) return (error); + if ((flags & ISLASTCN) && (vdp->v_mount->mnt_flag & MNT_RDONLY) && + (cnp->cn_nameiop == DELETE || cnp->cn_nameiop == RENAME)) + return (EROFS); /* * We now have a segment name to search for, and a directory to search. Index: kern/vfs_lookup.c =================================================================== RCS file: /home/ncvs/src/sys/kern/vfs_lookup.c,v retrieving revision 1.7.4.2 diff -c -r1.7.4.2 vfs_lookup.c *** 1.7.4.2 1995/09/12 08:39:06 --- vfs_lookup.c 1995/10/22 11:08:09 *************** *** 422,428 **** * If creating and at end of pathname, then can consider * allowing file to be created. */ ! if (rdonly || (ndp->ni_dvp->v_mount->mnt_flag & MNT_RDONLY)) { error = EROFS; goto bad; } --- 422,428 ---- * If creating and at end of pathname, then can consider * allowing file to be created. */ ! if (rdonly) { error = EROFS; goto bad; } *************** *** 510,528 **** goto dirloop; } /* ! * Check for read-only file systems. */ ! if (cnp->cn_nameiop == DELETE || cnp->cn_nameiop == RENAME) { ! /* ! * Disallow directory write attempts on read-only ! * file systems. ! */ ! if (rdonly || (dp->v_mount->mnt_flag & MNT_RDONLY) || ! (wantparent && ! (ndp->ni_dvp->v_mount->mnt_flag & MNT_RDONLY))) { ! error = EROFS; ! goto bad2; ! } } if (cnp->cn_flags & SAVESTART) { ndp->ni_startdir = ndp->ni_dvp; --- 510,521 ---- goto dirloop; } /* ! * Disallow directory write attempts on read-only file systems. */ ! if (rdonly && ! (cnp->cn_nameiop == DELETE || cnp->cn_nameiop == RENAME)) { ! error = EROFS; ! goto bad2; } if (cnp->cn_flags & SAVESTART) { ndp->ni_startdir = ndp->ni_dvp; *************** *** 638,644 **** * If creating and at end of pathname, then can consider * allowing file to be created. */ ! if (rdonly || (dvp->v_mount->mnt_flag & MNT_RDONLY)) { error = EROFS; goto bad; } --- 631,637 ---- * If creating and at end of pathname, then can consider * allowing file to be created. */ ! if (rdonly) { error = EROFS; goto bad; } *************** *** 663,681 **** #endif /* ! * Check for read-only file systems. */ ! if (cnp->cn_nameiop == DELETE || cnp->cn_nameiop == RENAME) { ! /* ! * Disallow directory write attempts on read-only ! * file systems. ! */ ! if (rdonly || (dp->v_mount->mnt_flag & MNT_RDONLY) || ! (wantparent && ! (dvp->v_mount->mnt_flag & MNT_RDONLY))) { ! error = EROFS; ! goto bad2; ! } } /* ASSERT(dvp == ndp->ni_startdir) */ if (cnp->cn_flags & SAVESTART) --- 656,667 ---- #endif /* ! * Disallow directory write attempts on read-only file systems. */ ! if (rdonly && ! (cnp->cn_nameiop == DELETE || cnp->cn_nameiop == RENAME)) { ! error = EROFS; ! goto bad2; } /* ASSERT(dvp == ndp->ni_startdir) */ if (cnp->cn_flags & SAVESTART) Index: kern/vfs_syscalls.c =================================================================== RCS file: /home/ncvs/src/sys/kern/vfs_syscalls.c,v retrieving revision 1.25.4.2 diff -c -r1.25.4.2 vfs_syscalls.c *** 1.25.4.2 1995/09/18 05:30:19 --- vfs_syscalls.c 1995/10/22 11:08:10 *************** *** 1391,1403 **** vp = nd.ni_vp; LEASE_CHECK(vp, p, p->p_ucred, LEASE_WRITE); VOP_LOCK(vp); ! if (vp->v_mount->mnt_flag & MNT_RDONLY) ! error = EROFS; ! else { ! VATTR_NULL(&vattr); ! vattr.va_flags = uap->flags; ! error = VOP_SETATTR(vp, &vattr, p->p_ucred, p); ! } vput(vp); return (error); } --- 1391,1399 ---- vp = nd.ni_vp; LEASE_CHECK(vp, p, p->p_ucred, LEASE_WRITE); VOP_LOCK(vp); ! VATTR_NULL(&vattr); ! vattr.va_flags = uap->flags; ! error = VOP_SETATTR(vp, &vattr, p->p_ucred, p); vput(vp); return (error); } *************** *** 1427,1439 **** vp = (struct vnode *)fp->f_data; LEASE_CHECK(vp, p, p->p_ucred, LEASE_WRITE); VOP_LOCK(vp); ! if (vp->v_mount->mnt_flag & MNT_RDONLY) ! error = EROFS; ! else { ! VATTR_NULL(&vattr); ! vattr.va_flags = uap->flags; ! error = VOP_SETATTR(vp, &vattr, p->p_ucred, p); ! } VOP_UNLOCK(vp); return (error); } --- 1423,1431 ---- vp = (struct vnode *)fp->f_data; LEASE_CHECK(vp, p, p->p_ucred, LEASE_WRITE); VOP_LOCK(vp); ! VATTR_NULL(&vattr); ! vattr.va_flags = uap->flags; ! error = VOP_SETATTR(vp, &vattr, p->p_ucred, p); VOP_UNLOCK(vp); return (error); } *************** *** 1464,1476 **** vp = nd.ni_vp; LEASE_CHECK(vp, p, p->p_ucred, LEASE_WRITE); VOP_LOCK(vp); ! if (vp->v_mount->mnt_flag & MNT_RDONLY) ! error = EROFS; ! else { ! VATTR_NULL(&vattr); ! vattr.va_mode = uap->mode & ALLPERMS; ! error = VOP_SETATTR(vp, &vattr, p->p_ucred, p); ! } vput(vp); return (error); } --- 1456,1464 ---- vp = nd.ni_vp; LEASE_CHECK(vp, p, p->p_ucred, LEASE_WRITE); VOP_LOCK(vp); ! VATTR_NULL(&vattr); ! vattr.va_mode = uap->mode & ALLPERMS; ! error = VOP_SETATTR(vp, &vattr, p->p_ucred, p); vput(vp); return (error); } *************** *** 1500,1512 **** vp = (struct vnode *)fp->f_data; LEASE_CHECK(vp, p, p->p_ucred, LEASE_WRITE); VOP_LOCK(vp); ! if (vp->v_mount->mnt_flag & MNT_RDONLY) ! error = EROFS; ! else { ! VATTR_NULL(&vattr); ! vattr.va_mode = uap->mode & ALLPERMS; ! error = VOP_SETATTR(vp, &vattr, p->p_ucred, p); ! } VOP_UNLOCK(vp); return (error); } --- 1488,1496 ---- vp = (struct vnode *)fp->f_data; LEASE_CHECK(vp, p, p->p_ucred, LEASE_WRITE); VOP_LOCK(vp); ! VATTR_NULL(&vattr); ! vattr.va_mode = uap->mode & ALLPERMS; ! error = VOP_SETATTR(vp, &vattr, p->p_ucred, p); VOP_UNLOCK(vp); return (error); } *************** *** 1538,1551 **** vp = nd.ni_vp; LEASE_CHECK(vp, p, p->p_ucred, LEASE_WRITE); VOP_LOCK(vp); ! if (vp->v_mount->mnt_flag & MNT_RDONLY) ! error = EROFS; ! else { ! VATTR_NULL(&vattr); ! vattr.va_uid = uap->uid; ! vattr.va_gid = uap->gid; ! error = VOP_SETATTR(vp, &vattr, p->p_ucred, p); ! } vput(vp); return (error); } --- 1522,1531 ---- vp = nd.ni_vp; LEASE_CHECK(vp, p, p->p_ucred, LEASE_WRITE); VOP_LOCK(vp); ! VATTR_NULL(&vattr); ! vattr.va_uid = uap->uid; ! vattr.va_gid = uap->gid; ! error = VOP_SETATTR(vp, &vattr, p->p_ucred, p); vput(vp); return (error); } *************** *** 1576,1589 **** vp = (struct vnode *)fp->f_data; LEASE_CHECK(vp, p, p->p_ucred, LEASE_WRITE); VOP_LOCK(vp); ! if (vp->v_mount->mnt_flag & MNT_RDONLY) ! error = EROFS; ! else { ! VATTR_NULL(&vattr); ! vattr.va_uid = uap->uid; ! vattr.va_gid = uap->gid; ! error = VOP_SETATTR(vp, &vattr, p->p_ucred, p); ! } VOP_UNLOCK(vp); return (error); } --- 1556,1565 ---- vp = (struct vnode *)fp->f_data; LEASE_CHECK(vp, p, p->p_ucred, LEASE_WRITE); VOP_LOCK(vp); ! VATTR_NULL(&vattr); ! vattr.va_uid = uap->uid; ! vattr.va_gid = uap->gid; ! error = VOP_SETATTR(vp, &vattr, p->p_ucred, p); VOP_UNLOCK(vp); return (error); } *************** *** 1625,1639 **** vp = nd.ni_vp; LEASE_CHECK(vp, p, p->p_ucred, LEASE_WRITE); VOP_LOCK(vp); ! if (vp->v_mount->mnt_flag & MNT_RDONLY) ! error = EROFS; ! else { ! vattr.va_atime.ts_sec = tv[0].tv_sec; ! vattr.va_atime.ts_nsec = tv[0].tv_usec * 1000; ! vattr.va_mtime.ts_sec = tv[1].tv_sec; ! vattr.va_mtime.ts_nsec = tv[1].tv_usec * 1000; ! error = VOP_SETATTR(vp, &vattr, p->p_ucred, p); ! } vput(vp); return (error); } --- 1601,1611 ---- vp = nd.ni_vp; LEASE_CHECK(vp, p, p->p_ucred, LEASE_WRITE); VOP_LOCK(vp); ! vattr.va_atime.ts_sec = tv[0].tv_sec; ! vattr.va_atime.ts_nsec = tv[0].tv_usec * 1000; ! vattr.va_mtime.ts_sec = tv[1].tv_sec; ! vattr.va_mtime.ts_nsec = tv[1].tv_usec * 1000; ! error = VOP_SETATTR(vp, &vattr, p->p_ucred, p); vput(vp); return (error); } Index: kern/vfs_vnops.c =================================================================== RCS file: /home/ncvs/src/sys/kern/vfs_vnops.c,v retrieving revision 1.11.4.3 diff -c -r1.11.4.3 vfs_vnops.c *** 1.11.4.3 1995/08/24 05:29:36 --- vfs_vnops.c 1995/10/22 11:08:10 *************** *** 199,217 **** { /* - * Disallow write attempts on read-only file systems; - * unless the file is a socket or a block or character - * device resident on the file system. - */ - if (vp->v_mount->mnt_flag & MNT_RDONLY) { - switch (vp->v_type) { - case VREG: case VDIR: case VLNK: - return (EROFS); - default: - break; - } - } - /* * If there's shared text associated with * the vnode, try to free it up once. If * we fail, we can't allow writing. --- 199,204 ---- Index: msdosfs/msdosfs_vnops.c =================================================================== RCS file: /home/ncvs/src/sys/msdosfs/msdosfs_vnops.c,v retrieving revision 1.17.2.3 diff -c -r1.17.2.3 msdosfs_vnops.c *** 1.17.2.3 1995/10/09 06:13:08 --- msdosfs_vnops.c 1995/10/22 11:08:11 *************** *** 204,227 **** return 0; } ! /* ! * This routine will go into sys/kern/vfs_subr.c one day! ! * ! * Do the usual access checking. ! * file_node, uid and gid are from the vnode in question, ! * while acc_mode and cred are from the VOP_ACCESS parameter list. ! */ ! static int ! vaccess(file_mode, uid, gid, acc_mode, cred) ! mode_t file_mode; ! uid_t uid; ! gid_t gid; ! mode_t acc_mode; ! struct ucred *cred; { ! mode_t mask; ! int i; register gid_t *gp; /* User id 0 always gets access. */ if (cred->cr_uid == 0) --- 204,245 ---- return 0; } ! int ! msdosfs_access(ap) ! struct vop_access_args /* { ! struct vnode *a_vp; ! int a_mode; ! struct ucred *a_cred; ! struct proc *a_p; ! } */ *ap; { ! struct vnode *vp = ap->a_vp; ! struct denode *dep = VTODE(ap->a_vp); ! struct msdosfsmount *pmp = dep->de_pmp; ! struct ucred *cred = ap->a_cred; ! mode_t mask, file_mode, mode = ap->a_mode; register gid_t *gp; + int i; + + file_mode = (S_IXUSR|S_IXGRP|S_IXOTH) | (S_IRUSR|S_IRGRP|S_IROTH) | + ((dep->de_Attributes & ATTR_READONLY) ? 0 : (S_IWUSR|S_IWGRP|S_IWOTH)); + file_mode &= pmp->pm_mask; + + /* + * Disallow write attempts on read-only file systems; + * unless the file is a socket, fifo, or a block or + * character device resident on the file system. + */ + if (mode & VWRITE) { + switch (vp->v_type) { + case VDIR: + case VLNK: + case VREG: + if (vp->v_mount->mnt_flag & MNT_RDONLY) + return (EROFS); + break; + } + } /* User id 0 always gets access. */ if (cred->cr_uid == 0) *************** *** 230,288 **** mask = 0; /* Otherwise, check the owner. */ ! if (cred->cr_uid == uid) { ! if (acc_mode & VEXEC) mask |= S_IXUSR; ! if (acc_mode & VREAD) mask |= S_IRUSR; ! if (acc_mode & VWRITE) mask |= S_IWUSR; return (file_mode & mask) == mask ? 0 : EACCES; } /* Otherwise, check the groups. */ for (i = 0, gp = cred->cr_groups; i < cred->cr_ngroups; i++, gp++) ! if (gid == *gp) { ! if (acc_mode & VEXEC) mask |= S_IXGRP; ! if (acc_mode & VREAD) mask |= S_IRGRP; ! if (acc_mode & VWRITE) mask |= S_IWGRP; return (file_mode & mask) == mask ? 0 : EACCES; } /* Otherwise, check everyone else. */ ! if (acc_mode & VEXEC) mask |= S_IXOTH; ! if (acc_mode & VREAD) mask |= S_IROTH; ! if (acc_mode & VWRITE) mask |= S_IWOTH; return (file_mode & mask) == mask ? 0 : EACCES; } int - msdosfs_access(ap) - struct vop_access_args /* { - struct vnode *a_vp; - int a_mode; - struct ucred *a_cred; - struct proc *a_p; - } */ *ap; - { - mode_t dosmode; - struct denode *dep = VTODE(ap->a_vp); - struct msdosfsmount *pmp = dep->de_pmp; - - dosmode = (S_IXUSR|S_IXGRP|S_IXOTH) | (S_IRUSR|S_IRGRP|S_IROTH) | - ((dep->de_Attributes & ATTR_READONLY) ? 0 : (S_IWUSR|S_IWGRP|S_IWOTH)); - dosmode &= pmp->pm_mask; - - return vaccess(dosmode, pmp->pm_uid, pmp->pm_gid, ap->a_mode, ap->a_cred); - } - - int msdosfs_getattr(ap) struct vop_getattr_args /* { struct vnode *a_vp; --- 248,286 ---- mask = 0; /* Otherwise, check the owner. */ ! if (cred->cr_uid == pmp->pm_uid) { ! if (mode & VEXEC) mask |= S_IXUSR; ! if (mode & VREAD) mask |= S_IRUSR; ! if (mode & VWRITE) mask |= S_IWUSR; return (file_mode & mask) == mask ? 0 : EACCES; } /* Otherwise, check the groups. */ for (i = 0, gp = cred->cr_groups; i < cred->cr_ngroups; i++, gp++) ! if (pmp->pm_gid == *gp) { ! if (mode & VEXEC) mask |= S_IXGRP; ! if (mode & VREAD) mask |= S_IRGRP; ! if (mode & VWRITE) mask |= S_IWGRP; return (file_mode & mask) == mask ? 0 : EACCES; } /* Otherwise, check everyone else. */ ! if (mode & VEXEC) mask |= S_IXOTH; ! if (mode & VREAD) mask |= S_IROTH; ! if (mode & VWRITE) mask |= S_IWOTH; return (file_mode & mask) == mask ? 0 : EACCES; } int msdosfs_getattr(ap) struct vop_getattr_args /* { struct vnode *a_vp; *************** *** 348,381 **** struct proc *a_p; } */ *ap; { ! int error = 0; struct denode *dep = VTODE(ap->a_vp); struct vattr *vap = ap->a_vap; struct ucred *cred = ap->a_cred; ! #ifdef MSDOSFS_DEBUG ! printf("msdosfs_setattr(): vp %08x, vap %08x, cred %08x, p %08x\n", ! ap->a_vp, vap, cred, ap->a_p); ! #endif ! if ((vap->va_type != VNON) || ! (vap->va_nlink != VNOVAL) || ! (vap->va_fsid != VNOVAL) || ! (vap->va_fileid != VNOVAL) || ! (vap->va_blocksize != VNOVAL) || ! (vap->va_rdev != VNOVAL) || ! (vap->va_bytes != VNOVAL) || ! (vap->va_gen != VNOVAL)) { ! #ifdef MSDOSFS_DEBUG ! printf("msdosfs_setattr(): returning EINVAL\n"); ! printf(" va_type %d, va_nlink %x, va_fsid %x, va_fileid %x\n", ! vap->va_type, vap->va_nlink, vap->va_fsid, vap->va_fileid); ! printf(" va_blocksize %x, va_rdev %x, va_bytes %x, va_gen %x\n", ! vap->va_blocksize, vap->va_rdev, vap->va_bytes, vap->va_gen); ! #endif ! return EINVAL; } if (vap->va_uid != (uid_t)VNOVAL || vap->va_gid != (uid_t)VNOVAL) { if ((cred->cr_uid != dep->de_pmp->pm_uid || vap->va_uid != dep->de_pmp->pm_uid || (vap->va_gid != dep->de_pmp->pm_gid && --- 346,400 ---- struct proc *a_p; } */ *ap; { ! struct vnode *vp = ap->a_vp; struct denode *dep = VTODE(ap->a_vp); struct vattr *vap = ap->a_vap; struct ucred *cred = ap->a_cred; + int error = 0; ! /* ! * Check for unsettable attributes. ! */ ! if ((vap->va_type != VNON) || (vap->va_nlink != VNOVAL) || ! (vap->va_fsid != VNOVAL) || (vap->va_fileid != VNOVAL) || ! (vap->va_blocksize != VNOVAL) || (vap->va_rdev != VNOVAL) || ! (vap->va_bytes != VNOVAL) || (vap->va_gen != VNOVAL)) { ! return (EINVAL); ! } ! if (vap->va_flags != VNOVAL) { ! if (vp->v_mount->mnt_flag & MNT_RDONLY) ! return (EROFS); ! if (cred->cr_uid != dep->de_pmp->pm_uid && ! (error = suser(cred, &ap->a_p->p_acflag))) ! return (error); ! /* ! * We are very inconsistent about handling unsupported ! * attributes. We ignored the the access time and the ! * read and execute bits. We were strict for the other ! * attributes. ! * ! * Here we are strict, stricter than ufs in not allowing ! * users to attempt to set SF_SETTABLE bits or anyone to ! * set unsupported bits. However, we ignore attempts to ! * set ATTR_ARCHIVE for directories `cp -pr' from a more ! * sensible file system attempts it a lot. ! */ ! if (cred->cr_uid != 0) { ! if (vap->va_flags & SF_SETTABLE) ! return EPERM; ! } ! if (vap->va_flags & ~SF_ARCHIVED) ! return EINVAL; ! if (vap->va_flags & SF_ARCHIVED) ! dep->de_Attributes &= ~ATTR_ARCHIVE; ! else if (!(dep->de_Attributes & ATTR_DIRECTORY)) ! dep->de_Attributes |= ATTR_ARCHIVE; ! dep->de_flag |= DE_MODIFIED; } if (vap->va_uid != (uid_t)VNOVAL || vap->va_gid != (uid_t)VNOVAL) { + if (vp->v_mount->mnt_flag & MNT_RDONLY) + return (EROFS); if ((cred->cr_uid != dep->de_pmp->pm_uid || vap->va_uid != dep->de_pmp->pm_uid || (vap->va_gid != dep->de_pmp->pm_gid && *************** *** 387,403 **** return EINVAL; } if (vap->va_size != VNOVAL) { ! if (ap->a_vp->v_type == VDIR) ! return EISDIR; error = detrunc(dep, vap->va_size, 0, cred, ap->a_p); if (error) return error; } if (vap->va_mtime.ts_sec != VNOVAL) { if (cred->cr_uid != dep->de_pmp->pm_uid && (error = suser(cred, &ap->a_p->p_acflag)) && ((vap->va_vaflags & VA_UTIMES_NULL) == 0 || ! (error = VOP_ACCESS(ap->a_vp, VWRITE, cred, ap->a_p)))) return error; dep->de_flag |= DE_UPDATE; error = deupdat(dep, &vap->va_mtime, 1); --- 406,436 ---- return EINVAL; } if (vap->va_size != VNOVAL) { ! /* ! * Disallow write attempts on read-only file systems; ! * unless the file is a socket, fifo, or a block or ! * character device resident on the file system. ! */ ! switch (vp->v_type) { ! case VDIR: ! return (EISDIR); ! case VLNK: ! case VREG: ! if (vp->v_mount->mnt_flag & MNT_RDONLY) ! return (EROFS); ! break; ! } error = detrunc(dep, vap->va_size, 0, cred, ap->a_p); if (error) return error; } if (vap->va_mtime.ts_sec != VNOVAL) { + if (vp->v_mount->mnt_flag & MNT_RDONLY) + return (EROFS); if (cred->cr_uid != dep->de_pmp->pm_uid && (error = suser(cred, &ap->a_p->p_acflag)) && ((vap->va_vaflags & VA_UTIMES_NULL) == 0 || ! (error = VOP_ACCESS(vp, VWRITE, cred, ap->a_p)))) return error; dep->de_flag |= DE_UPDATE; error = deupdat(dep, &vap->va_mtime, 1); *************** *** 410,416 **** --- 443,452 ---- * attribute set, so we use the owner write bit to set the readonly * attribute. */ + error = 0; if (vap->va_mode != (u_short) VNOVAL) { + if (vp->v_mount->mnt_flag & MNT_RDONLY) + return (EROFS); if (cred->cr_uid != dep->de_pmp->pm_uid && (error = suser(cred, &ap->a_p->p_acflag))) return error; *************** *** 420,454 **** dep->de_Attributes &= ~ATTR_READONLY; else dep->de_Attributes |= ATTR_READONLY; - dep->de_flag |= DE_MODIFIED; - } - - if (vap->va_flags != VNOVAL) { - if (cred->cr_uid != dep->de_pmp->pm_uid && - (error = suser(cred, &ap->a_p->p_acflag))) - return error; - /* - * We are very inconsistent about handling unsupported - * attributes. We ignored the the access time and the - * read and execute bits. We were strict for the other - * attributes. - * - * Here we are strict, stricter than ufs in not allowing - * users to attempt to set SF_SETTABLE bits or anyone to - * set unsupported bits. However, we ignore attempts to - * set ATTR_ARCHIVE for directories `cp -pr' from a more - * sensible file system attempts it a lot. - */ - if (cred->cr_uid != 0) { - if (vap->va_flags & SF_SETTABLE) - return EPERM; - } - if (vap->va_flags & ~SF_ARCHIVED) - return EINVAL; - if (vap->va_flags & SF_ARCHIVED) - dep->de_Attributes &= ~ATTR_ARCHIVE; - else if (!(dep->de_Attributes & ATTR_DIRECTORY)) - dep->de_Attributes |= ATTR_ARCHIVE; dep->de_flag |= DE_MODIFIED; } return error; --- 456,461 ---- Index: nfs/nfs_vnops.c =================================================================== RCS file: /home/ncvs/src/sys/nfs/nfs_vnops.c,v retrieving revision 1.15.4.1 diff -c -r1.15.4.1 nfs_vnops.c *** 1.15.4.1 1995/07/25 07:47:54 --- nfs_vnops.c 1995/10/22 11:28:13 *************** *** 282,287 **** --- 282,298 ---- struct mbuf *mreq, *mrep, *md, *mb, *mb2; /* + * Disallow write attempts on filesystems mounted read-only; + * unless the file is a socket, fifo, or a block or character + * device resident on the filesystem. + */ + if ((ap->a_mode & VWRITE) && (vp->v_mount->mnt_flag & MNT_RDONLY)) { + switch (vp->v_type) { + case VREG: case VDIR: case VLNK: + return (EROFS); + } + } + /* * For nqnfs, do an access rpc, otherwise you are stuck emulating * ufs_access() locally using the vattr. This may not be correct, * since the server may apply other access criteria such as *************** *** 481,486 **** --- 492,505 ---- register struct vattr *vap = ap->a_vap; u_quad_t frev, tsize = 0; + /* + * Disallow write attempts if the filesystem is mounted read-only. + */ + if ((vap->va_flags != VNOVAL || vap->va_uid != (uid_t)VNOVAL || + vap->va_gid != (gid_t)VNOVAL || vap->va_atime.ts_sec != VNOVAL || + vap->va_mtime.ts_sec != VNOVAL || vap->va_mode != (mode_t)VNOVAL) && + (vp->v_mount->mnt_flag & MNT_RDONLY)) + return (EROFS); if (vap->va_size != VNOVAL) { switch (vp->v_type) { case VDIR: *************** *** 496,501 **** --- 515,526 ---- vap->va_size = VNOVAL; break; default: + /* + * Disallow write attempts if the filesystem is + * mounted read-only. + */ + if (vp->v_mount->mnt_flag & MNT_RDONLY) + return (EROFS); if (np->n_flag & NMODIFIED) { error = nfs_vinvalbuf(vp, vap->va_size ? V_SAVE : 0, *************** *** 592,597 **** --- 617,625 ---- int nqlflag = 0, cachable = 0; u_quad_t frev; + if ((flags & ISLASTCN) && (dvp->v_mount->mnt_flag & MNT_RDONLY) && + (cnp->cn_nameiop == DELETE || cnp->cn_nameiop == RENAME)) + return (EROFS); *vpp = NULL; if (dvp->v_type != VDIR) return (ENOTDIR); *************** *** 2379,2389 **** --- 2407,2429 ---- register struct vattr *vap; register gid_t *gp; register struct ucred *cred = ap->a_cred; + struct vnode *vp = ap->a_vp; mode_t mode = ap->a_mode; struct vattr vattr; register int i; int error; + /* + * Disallow write attempts on filesystems mounted read-only; + * unless the file is a socket, fifo, or a block or character + * device resident on the filesystem. + */ + if ((mode & VWRITE) && (vp->v_mount->mnt_flag & MNT_RDONLY)) { + switch (vp->v_type) { + case VREG: case VDIR: case VLNK: + return (EROFS); + } + } /* * If you're the super-user, * you always get access. Index: ufs/ufs/ufs_lookup.c =================================================================== RCS file: /home/ncvs/src/sys/ufs/ufs/ufs_lookup.c,v retrieving revision 1.3 diff -c -r1.3 ufs_lookup.c *** 1.3 1994/10/08 06:57:26 --- ufs_lookup.c 1995/10/22 11:08:11 *************** *** 145,150 **** --- 145,153 ---- error = VOP_ACCESS(vdp, VEXEC, cred, cnp->cn_proc); if (error) return (error); + if ((flags & ISLASTCN) && (vdp->v_mount->mnt_flag & MNT_RDONLY) && + (cnp->cn_nameiop == DELETE || cnp->cn_nameiop == RENAME)) + return (EROFS); /* * We now have a segment name to search for, and a directory to search. Index: ufs/ufs/ufs_vnops.c =================================================================== RCS file: /home/ncvs/src/sys/ufs/ufs/ufs_vnops.c,v retrieving revision 1.24.4.2 diff -c -r1.24.4.2 ufs_vnops.c *** 1.24.4.2 1995/10/09 07:42:46 --- ufs_vnops.c 1995/10/22 11:08:11 *************** *** 122,130 **** struct vattr *a_vap; } */ *ap; { ! register struct vattr *vap = ap->a_vap; ! register struct vnode **vpp = ap->a_vpp; ! register struct inode *ip; int error; error = ufs_makeinode(MAKEIMODE(vap->va_type, vap->va_mode), --- 122,130 ---- struct vattr *a_vap; } */ *ap; { ! struct vattr *vap = ap->a_vap; ! struct vnode **vpp = ap->a_vpp; ! struct inode *ip; int error; error = ufs_makeinode(MAKEIMODE(vap->va_type, vap->va_mode), *************** *** 209,241 **** struct proc *a_p; } */ *ap; { ! register struct vnode *vp = ap->a_vp; ! register struct inode *ip = VTOI(vp); ! register struct ucred *cred = ap->a_cred; mode_t mask, mode = ap->a_mode; register gid_t *gp; ! int i; ! #ifdef QUOTA ! int error; ! #endif ! #ifdef DIAGNOSTIC ! if (!VOP_ISLOCKED(vp)) { ! vprint("ufs_access: not locked", vp); ! panic("ufs_access: not locked"); ! } ! #endif ! #ifdef QUOTA ! if (mode & VWRITE) switch (vp->v_type) { case VDIR: case VLNK: case VREG: if (error = getinoquota(ip)) return (error); break; } ! #endif /* If immutable bit set, nobody gets to write it. */ if ((mode & VWRITE) && (ip->i_flags & IMMUTABLE)) --- 209,240 ---- struct proc *a_p; } */ *ap; { ! struct vnode *vp = ap->a_vp; ! struct inode *ip = VTOI(vp); ! struct ucred *cred = ap->a_cred; mode_t mask, mode = ap->a_mode; register gid_t *gp; ! int i, error; ! /* ! * Disallow write attempts on read-only file systems; ! * unless the file is a socket, fifo, or a block or ! * character device resident on the file system. ! */ ! if (mode & VWRITE) { switch (vp->v_type) { case VDIR: case VLNK: case VREG: + if (vp->v_mount->mnt_flag & MNT_RDONLY) + return (EROFS); + #ifdef QUOTA if (error = getinoquota(ip)) return (error); + #endif break; } ! } /* If immutable bit set, nobody gets to write it. */ if ((mode & VWRITE) && (ip->i_flags & IMMUTABLE)) *************** *** 336,346 **** struct proc *a_p; } */ *ap; { ! register struct vattr *vap = ap->a_vap; ! register struct vnode *vp = ap->a_vp; ! register struct inode *ip = VTOI(vp); ! register struct ucred *cred = ap->a_cred; ! register struct proc *p = ap->a_p; struct timeval atimeval, mtimeval; int error; --- 335,345 ---- struct proc *a_p; } */ *ap; { ! struct vattr *vap = ap->a_vap; ! struct vnode *vp = ap->a_vp; ! struct inode *ip = VTOI(vp); ! struct ucred *cred = ap->a_cred; ! struct proc *p = ap->a_p; struct timeval atimeval, mtimeval; int error; *************** *** 354,359 **** --- 353,360 ---- return (EINVAL); } if (vap->va_flags != VNOVAL) { + if (vp->v_mount->mnt_flag & MNT_RDONLY) + return (EROFS); if (cred->cr_uid != ip->i_uid && (error = suser(cred, &p->p_acflag))) return (error); *************** *** 378,396 **** * Go through the fields and update iff not VNOVAL. */ if (vap->va_uid != (uid_t)VNOVAL || vap->va_gid != (gid_t)VNOVAL) { error = ufs_chown(vp, vap->va_uid, vap->va_gid, cred, p); if (error) return (error); } if (vap->va_size != VNOVAL) { ! if (vp->v_type == VDIR) return (EISDIR); error = VOP_TRUNCATE(vp, vap->va_size, 0, cred, p); if (error) return (error); } ip = VTOI(vp); if (vap->va_atime.ts_sec != VNOVAL || vap->va_mtime.ts_sec != VNOVAL) { if (cred->cr_uid != ip->i_uid && (error = suser(cred, &p->p_acflag)) && ((vap->va_vaflags & VA_UTIMES_NULL) == 0 || --- 379,413 ---- * Go through the fields and update iff not VNOVAL. */ if (vap->va_uid != (uid_t)VNOVAL || vap->va_gid != (gid_t)VNOVAL) { + if (vp->v_mount->mnt_flag & MNT_RDONLY) + return (EROFS); error = ufs_chown(vp, vap->va_uid, vap->va_gid, cred, p); if (error) return (error); } if (vap->va_size != VNOVAL) { ! /* ! * Disallow write attempts on read-only file systems; ! * unless the file is a socket, fifo, or a block or ! * character device resident on the file system. ! */ ! switch (vp->v_type) { ! case VDIR: return (EISDIR); + case VLNK: + case VREG: + if (vp->v_mount->mnt_flag & MNT_RDONLY) + return (EROFS); + break; + } error = VOP_TRUNCATE(vp, vap->va_size, 0, cred, p); if (error) return (error); } ip = VTOI(vp); if (vap->va_atime.ts_sec != VNOVAL || vap->va_mtime.ts_sec != VNOVAL) { + if (vp->v_mount->mnt_flag & MNT_RDONLY) + return (EROFS); if (cred->cr_uid != ip->i_uid && (error = suser(cred, &p->p_acflag)) && ((vap->va_vaflags & VA_UTIMES_NULL) == 0 || *************** *** 409,416 **** return (error); } error = 0; ! if (vap->va_mode != (mode_t)VNOVAL) error = ufs_chmod(vp, (int)vap->va_mode, cred, p); return (error); } --- 426,436 ---- return (error); } error = 0; ! if (vap->va_mode != (mode_t)VNOVAL) { ! if (vp->v_mount->mnt_flag & MNT_RDONLY) ! return (EROFS); error = ufs_chmod(vp, (int)vap->va_mode, cred, p); + } return (error); } *************** *** 636,644 **** struct componentname *a_cnp; } */ *ap; { ! register struct inode *ip; ! register struct vnode *vp = ap->a_vp; ! register struct vnode *dvp = ap->a_dvp; int error; ip = VTOI(vp); --- 656,664 ---- struct componentname *a_cnp; } */ *ap; { ! struct inode *ip; ! struct vnode *vp = ap->a_vp; ! struct vnode *dvp = ap->a_dvp; int error; ip = VTOI(vp); *************** *** 671,680 **** struct componentname *a_cnp; } */ *ap; { ! register struct vnode *vp = ap->a_vp; ! register struct vnode *tdvp = ap->a_tdvp; ! register struct componentname *cnp = ap->a_cnp; ! register struct inode *ip; struct timeval tv; int error; --- 691,700 ---- struct componentname *a_cnp; } */ *ap; { ! struct vnode *vp = ap->a_vp; ! struct vnode *tdvp = ap->a_tdvp; ! struct componentname *cnp = ap->a_cnp; ! struct inode *ip; struct timeval tv; int error; *************** *** 760,769 **** struct vnode *tvp = ap->a_tvp; register struct vnode *tdvp = ap->a_tdvp; struct vnode *fvp = ap->a_fvp; ! register struct vnode *fdvp = ap->a_fdvp; ! register struct componentname *tcnp = ap->a_tcnp; ! register struct componentname *fcnp = ap->a_fcnp; ! register struct inode *ip, *xp, *dp; struct dirtemplate dirbuf; struct timeval tv; int doingdirectory = 0, oldparent = 0, newparent = 0; --- 780,789 ---- struct vnode *tvp = ap->a_tvp; register struct vnode *tdvp = ap->a_tdvp; struct vnode *fvp = ap->a_fvp; ! struct vnode *fdvp = ap->a_fdvp; ! struct componentname *tcnp = ap->a_tcnp; ! struct componentname *fcnp = ap->a_fcnp; ! struct inode *ip, *xp, *dp; struct dirtemplate dirbuf; struct timeval tv; int doingdirectory = 0, oldparent = 0, newparent = 0; *************** *** 1264,1273 **** struct componentname *a_cnp; } */ *ap; { ! register struct vnode *vp = ap->a_vp; ! register struct vnode *dvp = ap->a_dvp; ! register struct componentname *cnp = ap->a_cnp; ! register struct inode *ip, *dp; int error; ip = VTOI(vp); --- 1284,1293 ---- struct componentname *a_cnp; } */ *ap; { ! struct vnode *vp = ap->a_vp; ! struct vnode *dvp = ap->a_dvp; ! struct componentname *cnp = ap->a_cnp; ! struct inode *ip, *dp; int error; ip = VTOI(vp); From owner-freebsd-stable Sun Oct 22 06:55:28 1995 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id GAA07014 for stable-outgoing; Sun, 22 Oct 1995 06:55:28 -0700 Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id GAA07009 for ; Sun, 22 Oct 1995 06:55:24 -0700 Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.9/8.6.9) id XAA00399; Sun, 22 Oct 1995 23:19:54 +0930 From: Michael Smith Message-Id: <199510221349.XAA00399@genesis.atrad.adelaide.edu.au> Subject: Re: 2.1.0-951020-SNAP - 2.1 *Release Candidate* To: davidg@Root.COM Date: Sun, 22 Oct 1995 23:19:54 +0930 (CST) Cc: hsu@cs.hut.fi, jkh@time.cdrom.com, stable@freebsd.org In-Reply-To: <199510220601.XAA04220@corbin.Root.COM> from "David Greenman" at Oct 21, 95 11:01:53 pm Content-Type: text Content-Length: 925 Sender: owner-stable@freebsd.org Precedence: bulk David Greenman stands accused of saying: > I don't know if I consider this a "critical" bug, however, as it might be > difficult to manifest during normal operations. I think that "slirp" must be > doing something strange - like an fchown() on a TTY. I'll have to look into > this in more detail. Well, put it this waty: People use SLiRP because it's free, and because it works very well. On a small ISP system, say ~200 SLiRP callers a day, you can count on at least one panic/crash/reboot a day. I'd call this pretty serious 8) > -DG -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] My car has "demand start" -Terry Lambert UNIX: live FreeBSD or die! [[ From owner-freebsd-stable Sun Oct 22 07:10:34 1995 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id HAA07776 for stable-outgoing; Sun, 22 Oct 1995 07:10:34 -0700 Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id HAA07759 for ; Sun, 22 Oct 1995 07:10:29 -0700 Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.9/8.6.9) id XAA00470 for stable@freebsd.org; Sun, 22 Oct 1995 23:35:36 +0930 From: Michael Smith Message-Id: <199510221405.XAA00470@genesis.atrad.adelaide.edu.au> Subject: Re: 2.1.0-951020-SNAP - 2.1 *Release Candidate* To: stable@freebsd.org Date: Sun, 22 Oct 1995 23:35:36 +0930 (CST) In-Reply-To: <199510221349.XAA00399@genesis.atrad.adelaide.edu.au> from "Michael Smith" at Oct 22, 95 11:19:54 pm Content-Type: text Content-Length: 684 Sender: owner-stable@freebsd.org Precedence: bulk Michael Smith stands accused of saying: > I'd call this pretty serious 8) > > > -DG And I call David's response pretty snappy! My humble apologies for crossing up there Dave - I've forwarded your patches on to one local who I hope will be able to provide some useful feedback before your deadline. -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] My car has "demand start" -Terry Lambert UNIX: live FreeBSD or die! [[ From owner-freebsd-stable Sun Oct 22 10:10:48 1995 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id KAA28224 for stable-outgoing; Sun, 22 Oct 1995 10:10:48 -0700 Received: from id.slip.bcm.tmc.edu (root@hou07.onramp.net [199.1.137.135]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id KAA28219 for ; Sun, 22 Oct 1995 10:10:44 -0700 Received: (from rich@localhost) by id.slip.bcm.tmc.edu (8.6.12/8.6.9) id MAA00497; Sun, 22 Oct 1995 12:10:28 -0500 Date: Sun, 22 Oct 1995 12:10:28 -0500 From: Rich Murphey Message-Id: <199510221710.MAA00497@id.slip.bcm.tmc.edu> To: nate@rocky.sri.MT.net CC: stable@FreeBSD.org, nate@rocky.sri.MT.net In-reply-to: <199510182217.QAA11314@rocky.sri.MT.net> (message from Nate Williams on Wed, 18 Oct 1995 16:17:58 -0600) Subject: Re: Linux emulator working? Reply-to: rich@lamprey.utmb.edu Sender: owner-stable@FreeBSD.org Precedence: bulk I've run the linux version of doom for X as well as part of the linux version of mathematica on 2.1-STABLE. Here's my notes which are about a month old now. ---------------------------------------------------------------- How to run Linux binaries on FreeBSD 2.1-STABLE: Install a kernel whose configuration file contains: options "COMPAT_LINUX" options SYSVSHM If you do not already have a /lkm/linux_mod.o, build and install the loadable kernel module (LKM) and /usr/bin/linux: cd /usr/src/lkm/linux make all install load the LKM (as root): linux get the linux runtime libraries: mkdir /compat/linux cd /compat/linux ncftp ftp.freebsd.org:pub/FreeBSD/2.0.5-RELEASE/xperimnt/linux-emu/linux-emu.tar.gz tar xzf linux-emu.tar.gz rm -rf usr lkm [you've already installed the lkm and /usr/bin/linux] To test it, install linux doom: ncftp ftp.freebsd.org:pub/FreeBSD/2.0.5-RELEASE/xperimnt/linux-emu/linux-doom-1.8.tar.gz tar xzf linux-doom-1.8.tar.gz cd doom-1.8 ./xdoom See also: man compat_linux ftp.freebsd.org:/home/ftp/pub/FreeBSD/2.0.5-RELEASE/xperimnt/linux-emu/README /usr/src/sys/i386/ibcs2/README.iBCS2 ---------------------------------------------------------------- |2) Install the Linux versions of ld.so, shlibs for normal stuff, and X | libraries from the Slackware 2.3 disk on cdrom.com into | /compat/linux/lib. Yep, and we have copies as well: mkdir /compat/linux cd /compat/linux ncftp ftp.freebsd.org:pub/FreeBSD/2.0.5-RELEASE/xperimnt/linux-emu/linux-emu.tar.gz tar xzf linux-emu.tar.gz rm -rf usr lkm |OK, thinking maybe this program had something weird in it, I downloaded |executor which Bill Pechter already claimed success on, and I get the |exact same error. :( | |What am I doing wrong? What can I do to fix this? I'm going to try to |get Linux-IDL running under FreeBSD to see how the performance compares |to the SPARC version we have. The difference in the libraries and the date of the FreeBSD-stable sources is the only significant differences I can see. So you might try the version of the libraries in the tar file above. PS. My licence for mathematica should have arrived so we should know fairly soon whether the linux port of mathematica will run under freebsd. Rich From owner-freebsd-stable Sun Oct 22 13:25:35 1995 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id NAA06300 for stable-outgoing; Sun, 22 Oct 1995 13:25:35 -0700 Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id NAA06294 for ; Sun, 22 Oct 1995 13:25:30 -0700 Received: (from jkh@localhost) by time.cdrom.com (8.6.12/8.6.9) id NAA09108 for stable@freebsd.org; Sun, 22 Oct 1995 13:25:12 -0700 Date: Sun, 22 Oct 1995 13:25:12 -0700 From: "Jordan K. Hubbard" Message-Id: <199510222025.NAA09108@time.cdrom.com> To: stable@freebsd.org Subject: GATEWAY in 2.1 LINT? Sender: owner-stable@freebsd.org Precedence: bulk Can we remove this? I thought we'd deprecated the option..? Jordan From owner-freebsd-stable Sun Oct 22 15:49:54 1995 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id PAA10558 for stable-outgoing; Sun, 22 Oct 1995 15:49:54 -0700 Received: from Root.COM (implode.Root.COM [198.145.90.17]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id PAA10553 for ; Sun, 22 Oct 1995 15:49:51 -0700 Received: from corbin.Root.COM (corbin [198.145.90.50]) by Root.COM (8.6.12/8.6.5) with ESMTP id PAA01039; Sun, 22 Oct 1995 15:49:49 -0700 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.12/8.6.5) with SMTP id PAA00763; Sun, 22 Oct 1995 15:48:23 -0700 Message-Id: <199510222248.PAA00763@corbin.Root.COM> To: "Jordan K. Hubbard" cc: stable@freebsd.org Subject: Re: GATEWAY in 2.1 LINT? In-reply-to: Your message of "Sun, 22 Oct 95 13:25:12 PDT." <199510222025.NAA09108@time.cdrom.com> From: David Greenman Reply-To: davidg@Root.COM Date: Sun, 22 Oct 1995 15:48:23 -0700 Sender: owner-stable@freebsd.org Precedence: bulk >Can we remove this? I thought we'd deprecated the option..? Sort of...it's still used to set the default state for IP forwarding. -DG From owner-freebsd-stable Mon Oct 23 14:00:17 1995 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id OAA27278 for stable-outgoing; Mon, 23 Oct 1995 14:00:17 -0700 Received: from metal.ops.neosoft.com (root@metal-pluto.ops.NeoSoft.COM [198.65.163.227]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id OAA27271 ; Mon, 23 Oct 1995 14:00:05 -0700 Received: (from smace@localhost) by metal.ops.neosoft.com (8.7.1/8.7.1) id PAA05188; Mon, 23 Oct 1995 15:59:39 -0500 (CDT) From: Scott Mace Message-Id: <199510232059.PAA05188@metal.ops.neosoft.com> Subject: SHOW STOPPER for 2.1 To: hackers@freebsd.org, stable@freebsd.org Date: Mon, 23 Oct 1995 15:59:39 -0500 (CDT) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-stable@freebsd.org Precedence: bulk There's a big problem with the "DES" package on 1020 SNAP the libtelnet.so.2.0 library has dependencies for libdes.so.2.0 and libkrb.so.2.0 (the 2 kerberos IV libraries). Its something weird in the release generation, because I used a libtelnet created from my 2.1-stable source tree and it fixed the problem. Scott From owner-freebsd-stable Mon Oct 23 17:04:30 1995 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id RAA08565 for stable-outgoing; Mon, 23 Oct 1995 17:04:30 -0700 Received: from rocky.sri.MT.net (sri.MT.net [204.94.231.129]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id RAA08560 for ; Mon, 23 Oct 1995 17:04:24 -0700 Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id SAA24180; Mon, 23 Oct 1995 18:06:44 -0600 Date: Mon, 23 Oct 1995 18:06:44 -0600 From: Nate Williams Message-Id: <199510240006.SAA24180@rocky.sri.MT.net> To: stable@FreeBSD.org Subject: pkg_add doesn't work with 951020-SNAP Sender: owner-stable@FreeBSD.org Precedence: bulk I just got through installing the SNAP on our gateway/firewall box (Thanks for the new floppies Jordan!) and I'm attempting to install the 2.1 SUP and TCSH packages. Unfortunately, I get the error: Can't find package `-'. tar: can't open archive ./sup-2.0.tgz : No such file or directory tar: child returned status 3 However, the package looks fine using 'tar ztvf sup-2.0.tgz. Help? Nate From owner-freebsd-stable Mon Oct 23 17:50:54 1995 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id RAA14154 for stable-outgoing; Mon, 23 Oct 1995 17:50:54 -0700 Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id RAA14145 for ; Mon, 23 Oct 1995 17:50:51 -0700 Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.12/8.6.9) with SMTP id RAA09188; Mon, 23 Oct 1995 17:50:34 -0700 To: Nate Williams cc: stable@FreeBSD.org Subject: Re: pkg_add doesn't work with 951020-SNAP In-reply-to: Your message of "Mon, 23 Oct 1995 18:06:44 MDT." <199510240006.SAA24180@rocky.sri.MT.net> Date: Mon, 23 Oct 1995 17:50:33 -0700 Message-ID: <9186.814495833@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-stable@FreeBSD.org Precedence: bulk > I just got through installing the SNAP on our gateway/firewall box > (Thanks for the new floppies Jordan!) and I'm attempting to install the > 2.1 SUP and TCSH packages. Unfortunately, I get the error: > > Can't find package `-'. > tar: can't open archive ./sup-2.0.tgz : No such file or directory > tar: child returned status 3 I must admit that I've been changing the floppies a lot lately.. :-) I fixed package adding this morning, but have been sort of batching a number of fixes together since the one-floppy-set-per-hour routine was getting a little ridiculous! :-) Jordan From owner-freebsd-stable Mon Oct 23 19:32:53 1995 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id TAA23388 for stable-outgoing; Mon, 23 Oct 1995 19:32:53 -0700 Received: from rocky.sri.MT.net (sri.MT.net [204.94.231.129]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id TAA23360 for ; Mon, 23 Oct 1995 19:32:49 -0700 Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id UAA24559; Mon, 23 Oct 1995 20:34:48 -0600 Date: Mon, 23 Oct 1995 20:34:48 -0600 From: Nate Williams Message-Id: <199510240234.UAA24559@rocky.sri.MT.net> To: "Jordan K. Hubbard" Cc: Nate Williams , stable@FreeBSD.org Subject: Re: pkg_add doesn't work with 951020-SNAP In-Reply-To: <9186.814495833@time.cdrom.com> References: <199510240006.SAA24180@rocky.sri.MT.net> <9186.814495833@time.cdrom.com> Sender: owner-stable@FreeBSD.org Precedence: bulk > > I just got through installing the SNAP on our gateway/firewall box > > (Thanks for the new floppies Jordan!) and I'm attempting to install the > > 2.1 SUP and TCSH packages. Unfortunately, I get the error: > > > > Can't find package `-'. > > tar: can't open archive ./sup-2.0.tgz : No such file or directory > > tar: child returned status 3 > > I must admit that I've been changing the floppies a lot lately.. :-) Ummmmm, this isn't a floppy problem, but a problem with the pkg_add routine in /usr/sbin on a fully-installed system. I replaced it with a version from my build and it worked fine. Nate From owner-freebsd-stable Mon Oct 23 19:40:12 1995 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id TAA24149 for stable-outgoing; Mon, 23 Oct 1995 19:40:12 -0700 Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id TAA24125 for ; Mon, 23 Oct 1995 19:40:06 -0700 Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.12/8.6.9) with SMTP id TAA09934; Mon, 23 Oct 1995 19:39:44 -0700 To: Nate Williams cc: stable@FreeBSD.org Subject: Re: pkg_add doesn't work with 951020-SNAP In-reply-to: Your message of "Mon, 23 Oct 1995 20:34:48 MDT." <199510240234.UAA24559@rocky.sri.MT.net> Date: Mon, 23 Oct 1995 19:39:44 -0700 Message-ID: <9932.814502384@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-stable@FreeBSD.org Precedence: bulk > Ummmmm, this isn't a floppy problem, but a problem with the pkg_add > routine in /usr/sbin on a fully-installed system. I replaced it with a > version from my build and it worked fine. Yes, that's true, but I updated that too.. :-) I've fixed so many problems at this point that I'm rolling a new snapshot on westhill now.. :-) Jordan From owner-freebsd-stable Mon Oct 23 19:48:12 1995 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id TAA24967 for stable-outgoing; Mon, 23 Oct 1995 19:48:12 -0700 Received: from rocky.sri.MT.net (sri.MT.net [204.94.231.129]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id TAA24922 for ; Mon, 23 Oct 1995 19:47:50 -0700 Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id UAA24611; Mon, 23 Oct 1995 20:50:02 -0600 Date: Mon, 23 Oct 1995 20:50:02 -0600 From: Nate Williams Message-Id: <199510240250.UAA24611@rocky.sri.MT.net> To: "Jordan K. Hubbard" Cc: Nate Williams , stable@FreeBSD.org Subject: Re: pkg_add doesn't work with 951020-SNAP In-Reply-To: <9932.814502384@time.cdrom.com> References: <199510240234.UAA24559@rocky.sri.MT.net> <9932.814502384@time.cdrom.com> Sender: owner-stable@FreeBSD.org Precedence: bulk > > Ummmmm, this isn't a floppy problem, but a problem with the pkg_add > > routine in /usr/sbin on a fully-installed system. I replaced it with a > > version from my build and it worked fine. > > Yes, that's true, but I updated that too.. :-) Oh, I didn't notice the commit to the package code. > I've fixed so many problems at this point that I'm rolling a new > snapshot on westhill now.. :-) Cool. Nate From owner-freebsd-stable Mon Oct 23 20:59:17 1995 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id UAA01806 for stable-outgoing; Mon, 23 Oct 1995 20:59:17 -0700 Received: from tsbgw.wide.toshiba.co.jp (tsbgw.wide.toshiba.co.jp [202.249.10.123]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id UAA01776 for ; Mon, 23 Oct 1995 20:59:02 -0700 Received: by tsbgw.wide.toshiba.co.jp (8.6.12-KCONV/2.1) with UUCP id MAA09259; Tue, 24 Oct 1995 12:58:32 +0900 Received: by mailhost.isl.rdc.toshiba.co.jp (8.6.12-KCONV/2.1) with ESMTP id MAA27042; Tue, 24 Oct 1995 12:53:40 +0900 Received: from pdcd-mail.pdcd.ilab.toshiba.co.jp by ilab-master.ilab.toshiba.co.jp (8.6.11+2.5Wb2/3.3W9-ilab2.1) with ESMTP id LAA22722; Tue, 24 Oct 1995 11:48:56 +0900 Received: by pdcd-mail.pdcd.ilab.toshiba.co.jp (8.6.11+2.5Wb2+PDCD/3.3W9-pdcd7.1) with ESMTP id LAA17609; Tue, 24 Oct 1995 11:48:55 +0900 Date: Tue, 24 Oct 1995 11:48:55 +0900 From: Masamichi Tateoka Message-Id: <199510240248.LAA17609@pdcd-mail.pdcd.ilab.toshiba.co.jp> To: stable@Freebsd.ORG Cc: tateoka@pdcd.ilab.toshiba.co.jp Subject: I have problem with 2.1.0-951020-SNAP Sender: owner-stable@Freebsd.ORG Precedence: bulk Hi. I'm Masamichi Tateoka, one of FreeBSD FUN. I'm using FreeBSD in my home for UUCP link with my friends. I used 2.0R, and it was very nice for me. And few weeks ago, I installed 2.0.5R in my machine. Then my uucico always sleep in "ttywri" while sending files and never wakeup. So , last night I got ssys.?? in 2.1.0-951020-SNAP and recompiled my kernel. But I got same problem. This problem occur only while using uucico with i-protocol 1024bytes/packet. through TEL line, and I couldn't reappearance other way( cat or dd through line emulator.) So It's impossible to say that whether kernel is bad or not. Now I'm using uucico with i-protocol 512bytes/packet, and I have no problems (maybe). But I think I should inform you. so I wrote this mail. I wish this mail would help you. Yours sincerely. Masamichi Tateoka (tateoka@pdcd.ilab.toshiba.co.jp) (tateoka@yasai.forus.or.jp (HOME) ) P.S. follows are my configurations. ( I'm using /dev/cuaa3 for uucp ) ------ # # GENERIC -- Generic machine with WD/AHx/NCR/BTx family disks # # GENERIC,v 1.45.2.3 1995/06/05 21:50:41 jkh Exp # machine "i386" cpu "I386_CPU" cpu "I486_CPU" cpu "I586_CPU" ident GENERIC maxusers 10 options MATH_EMULATE #Support for x87 emulation options INET #InterNETworking options FFS #Berkeley Fast Filesystem options NFS #Network Filesystem options MSDOSFS #MSDOS Filesystem options "CD9660" #ISO 9660 Filesystem options PROCFS #Process filesystem options "COMPAT_43" #Compatible with BSD 4.3 options "SCSI_DELAY=1" #Be pessimistic about Joe SCSI device options BOUNCE_BUFFERS #include support for DMA bounce buffers options UCONSOLE #Allow users to grab the console config kernel root on wd0 controller isa0 controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr disk fd0 at fdc0 drive 0 controller aha0 at isa? port "IO_AHA0" bio irq ? drq 5 vector ahaintr controller scbus0 device sd0 device st0 device cd0 #Only need one of these, the code dynamically grows # syscons is the default console driver, resembling an SCO console device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr # Enable this and PCVT_FREEBSD for pcvt vt220 compatible console driver #device vt0 at isa? port "IO_KBD" tty irq 1 vector pcrint #options "PCVT_FREEBSD=210" # pcvt running on FreeBSD 2.1 #options XSERVER # include code for XFree86 device npx0 at isa? port "IO_NPX" irq 13 vector npxintr device sio0 at isa? port "IO_COM1" tty irq 4 vector siointr device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr #device sio2 at isa? port "IO_COM3" tty irq 5 vector siointr device sio3 at isa? port "IO_COM4" tty irq 5 vector siointr options COM_MULTIPORT device lpt0 at isa? port? tty irq 7 vector lptintr # Order is important here due to intrusive probes, do *not* alphabetize # this list of network interfaces until the probes have been fixed. # Right now it appears that the ie0 must be probed before ep0. See # revision 1.20 of this file. device ed0 at isa? port 0x300 net irq 9 vector edintr pseudo-device loop pseudo-device ether pseudo-device log pseudo-device sl 1 # ijppp uses tun instead of ppp device pseudo-device ppp 1 pseudo-device tun 1 pseudo-device pty 16 pseudo-device gzip # Exec gzipped a.out's --------- dmesg output. --- FreeBSD 2.1.0-951020-SNAP #0: Mon Oct 23 23:50:49 JST 1995 tateoka@celery:/usr/src/sys.2.1.0-951020-SNAP/compile/YASAI CPU: i486DX (486-class CPU) real memory = 33554432 (32768K bytes) avail memory = 30867456 (30144K bytes) Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> ed0 at 0x300-0x31f irq 9 on isa ed0: address 48:4c:00:00:77:89, type NE2000 (16 bit) sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16450 sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A sio3 at 0x2e8-0x2ef irq 5 on isa sio3: type 16550A lpt0 at 0x3bc-0x3c3 irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: NEC 765 fd0: 1.44MB 3.5in aha0 at 0x330-0x333 irq 11 drq 5 on isa (aha0:0:0): "IBM OEM 0664M1H 7 70" type 0 fixed SCSI 2 sd0(aha0:0:0): Direct-Access 1920MB (3933040 512 byte sectors) (aha0:4:0): "TANDBERG TDC 3600 -06:" type 1 removable SCSI 1 st0(aha0:4:0): Sequential-Access st0: Tandberg tdc3600 is a known rogue density code 0x10, drive empty npx0 on motherboard npx0: INT 16 interface changing root device to sd0a sio3: 13 more silo overflows (total 13) sio3: 3 more silo overflows (total 16) ---- conlcuded. From owner-freebsd-stable Tue Oct 24 01:36:10 1995 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id BAA28104 for stable-outgoing; Tue, 24 Oct 1995 01:36:10 -0700 Received: from btp1da.phy.uni-bayreuth.de (btp1da.phy.uni-bayreuth.de [132.180.20.32]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id BAA28048 ; Tue, 24 Oct 1995 01:35:58 -0700 Received: (from werner@localhost) by btp1da.phy.uni-bayreuth.de (8.6.12/8.6.12) id KAA09099; Tue, 24 Oct 1995 10:35:45 +0100 From: Werner Griessl Message-Id: <199510240935.KAA09099@btp1da.phy.uni-bayreuth.de> Subject: pkg_info fault To: stable@freebsd.org Date: Tue, 24 Oct 1995 10:35:44 +0100 (MET) Cc: questions@freebsd.org X-Mailer: ELM [version 2.4 PL24 ME8a] Content-Type: text Content-Length: 103 Sender: owner-stable@freebsd.org Precedence: bulk "pkg_info -a" in FreeBSD 2.1.0-951020-SNAP (and also STABLE) give me a "Segmentation fault" ! Werner From owner-freebsd-stable Tue Oct 24 10:57:04 1995 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id KAA23718 for stable-outgoing; Tue, 24 Oct 1995 10:57:04 -0700 Received: from sasami.jurai.net (sasami.jurai.net [205.218.122.51]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id KAA23713 for ; Tue, 24 Oct 1995 10:57:02 -0700 Received: (from winter@localhost) by sasami.jurai.net (8.6.11/8.6.9) id MAA23406; Tue, 24 Oct 1995 12:57:00 -0500 Date: Tue, 24 Oct 1995 12:56:59 -0500 (CDT) From: "Matthew N. Dodd" X-Sender: winter@sasami To: stable@freebsd.org Subject: Re: problem with DES and telnet In-Reply-To: <199510212333.SAA04884@crash.ops.neosoft.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-stable@freebsd.org Precedence: bulk On Sat, 21 Oct 1995, Scott Mace wrote: > can't find shared library "libdes.so.2.0" If you select all the "secure dist" stuff you also get some shared library error. This happened in the previous snap (1005). Recompiling telnet and telnetd w/o some define seemed to work. (Sorry I can't be more specific, I don't have the machine right here...) This is easy to duplicate, just install a system with all secure dist options checked... | Matthew N. Dodd | winter@jurai.net | http://www.jurai.net/~winter | | Technical Manager | mdodd@intersurf.net | http://www.intersurf.net | | InterSurf Online | "Welcome to the net Sir, would you like a handbasket?"| From owner-freebsd-stable Tue Oct 24 11:00:15 1995 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id LAA23821 for stable-outgoing; Tue, 24 Oct 1995 11:00:15 -0700 Received: from sasami.jurai.net (root@sasami.jurai.net [205.218.122.51]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id LAA23816 for ; Tue, 24 Oct 1995 11:00:13 -0700 Received: (from winter@localhost) by sasami.jurai.net (8.6.11/8.6.9) id NAA23515; Tue, 24 Oct 1995 13:00:33 -0500 Date: Tue, 24 Oct 1995 13:00:33 -0500 (CDT) From: "Matthew N. Dodd" X-Sender: winter@sasami To: stable@FreeBSD.org Subject: Re: pkg_add doesn't work with 951020-SNAP In-Reply-To: <199510240006.SAA24180@rocky.sri.MT.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-stable@FreeBSD.org Precedence: bulk On Mon, 23 Oct 1995, Nate Williams wrote: > Can't find package `-'. > tar: can't open archive ./sup-2.0.tgz : No such file or directory > tar: child returned status 3 I got this as well (thought it was related to my earlier problem, install couldn't find the INDEX files as my mirror hadn't been run). | Matthew N. Dodd | winter@jurai.net | http://www.jurai.net/~winter | | Technical Manager | mdodd@intersurf.net | http://www.intersurf.net | | InterSurf Online | "Welcome to the net Sir, would you like a handbasket?"| From owner-freebsd-stable Tue Oct 24 14:52:26 1995 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id OAA05590 for stable-outgoing; Tue, 24 Oct 1995 14:52:26 -0700 Received: from id.slip.bcm.tmc.edu (root@hou02.onramp.net [199.1.137.130]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id OAA05580 for ; Tue, 24 Oct 1995 14:52:20 -0700 Received: (from rich@localhost) by id.slip.bcm.tmc.edu (8.6.12/8.6.9) id QAA10322; Tue, 24 Oct 1995 16:52:08 -0500 Date: Tue, 24 Oct 1995 16:52:08 -0500 From: Rich Murphey Message-Id: <199510242152.QAA10322@id.slip.bcm.tmc.edu> To: stable@FreeBSD.org In-reply-to: message from rich on Sun, 22 Oct 95 12:10:27 -0500 Subject: Mathematica 2.2 works under the Linux emulator.. Reply-to: rich@lamprey.utmb.edu Sender: owner-stable@FreeBSD.org Precedence: bulk Just to follow up about the linux emulator.. Mathematica 2.2 for Linux runs just fine. The distribution includes an X client for plotting results but the Linux port does not include the 'mathematica notebook frontend'. I hate working in the notebook anyway so I don't consider it any loss. It complains about some missing ioctls when it checks the licence/password pair, but it works in spite of the messages, so you can safely ignore them. Rich From owner-freebsd-stable Wed Oct 25 00:44:35 1995 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id AAA02602 for stable-outgoing; Wed, 25 Oct 1995 00:44:35 -0700 Received: from Jupiter.SPARCO.Com (cheema@Jupiter.SPARCO.Com [130.18.92.24]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id AAA02597 for ; Wed, 25 Oct 1995 00:44:32 -0700 Received: (from cheema@localhost) by Jupiter.SPARCO.Com (8.6.12/8.6.9) id CAA20421 for stable@freebsd.org; Wed, 25 Oct 1995 02:44:09 -0500 From: Mubashir Cheema Message-Id: <199510250744.CAA20421@Jupiter.SPARCO.Com> Subject: Stange errors To: stable@freebsd.org Date: Wed, 25 Oct 1995 02:44:09 -0500 (CDT) X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1060 Sender: owner-stable@freebsd.org Precedence: bulk I am running FreeBSD 2.1.0-950928-SNAP on Zeos P-90 PCI with a 1.6GB Maxtor IDE Hard Drive and 64MB of memory. I noticed a very strange happening a few minutes ago. My machine rebooted itself automatically while I was in the middle editing a file using vi. /var/log/messages says the following happened at that time : Oct 25 02:02:24 Moon /kernel: wd1a: wdintr: timeout waiting for status reading fsbn 738175 of 738174-738175 (wd1 bn 738175; cn 366 tn 5 sn 4)wd1: status d8 error 0 Can anybody tell me in plain english as to what happened ? Also the messages files is full of these 2 error messages. I am not sure if this is system related or not. Is anybody else seeing them ? Oct 21 05:44:14 Moon named[63]: Lame server on 'barton.net.au' (in 'barton.NET.AU'?): [203.12.80.1].53 'ns.skeeve.net': learnt (A =203.12.80.1,NS=192.189.54.33) Oct 21 05:45:29 Moon named[63]: Lame server on 'webdreams.net.au' (in 'webdreams.NET.AU'?): [203.12.80.1].53 'ns.skeeve.net': learnt (A=203.12.80.1,NS=192.65.182.30) Thanks. Mubashir Cheema From owner-freebsd-stable Wed Oct 25 07:13:20 1995 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id HAA15084 for stable-outgoing; Wed, 25 Oct 1995 07:13:20 -0700 Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id HAA15077 for ; Wed, 25 Oct 1995 07:13:16 -0700 Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.12/8.6.9) with SMTP id HAA27514; Wed, 25 Oct 1995 07:12:47 -0700 To: Mubashir Cheema cc: stable@freebsd.org Subject: Re: Stange errors In-reply-to: Your message of "Wed, 25 Oct 1995 02:44:09 CDT." <199510250744.CAA20421@Jupiter.SPARCO.Com> Date: Wed, 25 Oct 1995 07:12:47 -0700 Message-ID: <27511.814630367@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-stable@freebsd.org Precedence: bulk > Oct 25 02:02:24 Moon /kernel: wd1a: wdintr: timeout waiting for > status reading fsbn 738175 of 738174-738175 (wd1 bn 738175; cn 366 > tn 5 sn 4)wd1: status d8 error 0 > > Can anybody tell me in plain english as to what happened ? I'd say the drive spun down, or failed. One sometimes used to see this with laptops which powered the drive down for power-saving purposes, but I gather this isn't a laptop we're talking about here.. > Oct 21 05:44:14 Moon named[63]: Lame server on 'barton.net.au' > (in 'barton.NET.AU'?): [203.12.80.1].53 'ns.skeeve.net': learnt (A =203.12.80 .1,NS=192.189.54.33) Something unrelated and not to do with your system at all. Jordan From owner-freebsd-stable Wed Oct 25 08:59:17 1995 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id IAA22250 for stable-outgoing; Wed, 25 Oct 1995 08:59:17 -0700 Received: from fieber-john.campusview.indiana.edu (Fieber-John.campusview.indiana.edu [149.159.1.34]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id IAA22238 ; Wed, 25 Oct 1995 08:59:11 -0700 Received: (from jfieber@localhost) by fieber-john.campusview.indiana.edu (8.6.12/8.6.12) id KAA00380; Wed, 25 Oct 1995 10:59:09 -0500 Date: Wed, 25 Oct 1995 10:59:09 -0500 (EST) From: John Fieber To: stable@freebsd.org cc: "Jordan K. Hubbard" Subject: Oct 20 snap install... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-stable@freebsd.org Precedence: bulk I had a slightly more eventful than desired installation of the October 20 snapshot. For a variety of reasons, I needed to expand my dos/windows partion. Previously I had an IDE disk split between dos and FreeBSD, and a SCSI disk for FreeBSD (swap and /usr/local). With the reorganization, I wanted to make the IDE disk all dos and the SCSI disk FreeBSD. Fine, After I figured out that I had to enable the host adapter BIOS on my Adaptec 1542C, booteasy allowed me to select the second disk for booting. However, the kernel was convinced that it was booting from sd1, not sd0 and thus paniced when it tried to mount its root filesystem. I made a new kernel that specified the root device as sd0. It still didn't work. Finally, I looked at the biosboot code to figure out what the command line switches meant and got things working by typing -r at the boot prompt. So: * Can the boot prompt switches be document in a useful place, i.e. at the boot prompt? * Can I set things up so I can boot without typing -r every time? * Why does the kernel think it is booting from sd1 anyway? Other comments: * The "progress bars" in sysinstall often overshoot the right border of their box. * What exactly is the intended action of "Undo all" from the slice and disklabel screens? I got terribly disoriented when selcting that option. If the intent is to undo all actions performed on *that screen*, it should undo them, but remain on that screen. If the intent is to undo *all* slicing and labeling then it should return the user to the main menu. I don't recall exactly where I ended up, but it wasn't anywhere I expected. * The difference between FTP active and FTP passive needs to be documented on the media selection help screen. and gobs of other comments but those can wait for 2.2. -john (And now, with my adaptec bios enabled, my dos network drivers won't load! Grrr...) == jfieber@indiana.edu =========================================== == http://fieber-john.campusview.indiana.edu/~jfieber ============ From owner-freebsd-stable Wed Oct 25 10:16:38 1995 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id KAA28258 for stable-outgoing; Wed, 25 Oct 1995 10:16:38 -0700 Received: from palmer.demon.co.uk (palmer.demon.co.uk [158.152.50.150]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id KAA28247 for ; Wed, 25 Oct 1995 10:16:31 -0700 Received: from localhost (localhost [127.0.0.1]) by palmer.demon.co.uk (8.6.11/8.6.11) with SMTP id MAA07293 ; Wed, 25 Oct 1995 12:19:34 +0100 To: Mubashir Cheema cc: stable@freebsd.org Subject: Re: Stange errors In-reply-to: Your message of "Wed, 25 Oct 1995 02:44:09 CDT." <199510250744.CAA20421@Jupiter.SPARCO.Com> Date: Wed, 25 Oct 1995 12:19:31 +0100 Message-ID: <7291.814619971@palmer.demon.co.uk> From: Gary Palmer Sender: owner-stable@freebsd.org Precedence: bulk Mubashir Cheema stands accused of writing in message ID <199510250744.CAA20421@Jupiter.SPARCO.Com>: >Also the messages files is full of these 2 error messages. I am >not sure if this is system related or not. Is anybody else >seeing them ? >Oct 21 05:44:14 Moon named[63]: Lame server on 'barton.net.au' >(in 'barton.NET.AU'?): [203.12.80.1].53 'ns.skeeve.net': learnt (A =203.12.80. >1,NS=192.189.54.33) >Oct 21 05:45:29 Moon named[63]: Lame server on 'webdreams.net.au' >(in 'webdreams.NET.AU'?): [203.12.80.1].53 'ns.skeeve.net': learnt (A=203.12.8 >0.1,NS=192.65.182.30) Don't worry about these. They just mean that a DNS server claims to be able to give authoratative data for a domain and then gives out unauthoratative data. The server doing the query spits out these lame delegation warnings. If you download bind-4.9.3BETA26.tar.gz from ftp.vix.com, there is a script in there which will allow you to go through your /var/log/messages and send warning messages to the admins of the domains concerned. You ought to see the /var/log/messages on who.cdrom.com (the nameserver that serves all of cdrom.com and also freebsd.org - the lists on freebsd.org hit the DNS hard and often point out DNS bugs, like lame delegations)... the number of lame delegations it finds in a day is astounding. Gary From owner-freebsd-stable Wed Oct 25 13:44:51 1995 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id NAA13241 for stable-outgoing; Wed, 25 Oct 1995 13:44:51 -0700 Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id NAA13231 ; Wed, 25 Oct 1995 13:44:47 -0700 Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.12/8.6.9) with SMTP id NAA29771; Wed, 25 Oct 1995 13:44:09 -0700 To: John Fieber cc: stable@freebsd.org, "Jordan K. Hubbard" Subject: Re: Oct 20 snap install... In-reply-to: Your message of "Wed, 25 Oct 1995 10:59:09 CDT." Date: Wed, 25 Oct 1995 13:44:09 -0700 Message-ID: <29769.814653849@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-stable@freebsd.org Precedence: bulk > Fine, After I figured out that I had to enable the host adapter BIOS on > my Adaptec 1542C, booteasy allowed me to select the second disk for > booting. However, the kernel was convinced that it was booting from sd1, > not sd0 and thus paniced when it tried to mount its root filesystem. Hmmmmm. That's interesting. Did you see both wd0 and sd0 in the disks menu when you were installing it? Just curious, 'cause I've not had the chance to test that particular scenario before. > I made a new kernel that specified the root device as sd0. It still > didn't work. Finally, I looked at the biosboot code to figure out what > the command line switches meant and got things working by typing -r at > the boot prompt. Those those contortions really shouldn't have been necessary. I'm puzzled. > * Can the boot prompt switches be document in a useful place, i.e. at > the boot prompt? Not enough room to document them there.. We're at the wall for bytes as it is.. :-( > * Can I set things up so I can boot without typing -r every time? You could re-write your bootblocks with an implicit assumption of sd1, I guess. Still, I have no idea why this thing thinks it's sd1! That makes simply *no sense* for a drive 0 on your Adaptec! It's not like the IDE drive is supposed to bump the SCSI drive count! :-) > * Why does the kernel think it is booting from sd1 anyway? Good question. > * The "progress bars" in sysinstall often overshoot the right border of > their box. That's actually the cursor, I'm afraid, and everything I've tried to get rid of it simply doesn't work. We get to live with this one. > * What exactly is the intended action of "Undo all" from the > slice and disklabel screens? I got terribly disoriented when > selcting that option. If the intent is to undo all actions > performed on *that screen*, it should undo them, but remain > on that screen. If the intent is to undo *all* slicing and labeling > then it should return the user to the main menu. It undoes everything, I'm afraid. I could make a more intelligent undo, but that's going to have to wait for 2.2.. :-( > * The difference between FTP active and FTP passive needs to be > documented on the media selection help screen. OK. Jordan From owner-freebsd-stable Wed Oct 25 14:41:13 1995 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id OAA19501 for stable-outgoing; Wed, 25 Oct 1995 14:41:13 -0700 Received: from palmer.demon.co.uk (palmer.demon.co.uk [158.152.50.150]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id OAA19441 ; Wed, 25 Oct 1995 14:40:43 -0700 Received: from localhost (localhost [127.0.0.1]) by palmer.demon.co.uk (8.6.11/8.6.11) with SMTP id SAA00471 ; Wed, 25 Oct 1995 18:32:52 +0100 To: John Fieber cc: stable@freebsd.org, "Jordan K. Hubbard" Subject: Re: Oct 20 snap install... In-reply-to: Your message of "Wed, 25 Oct 1995 10:59:09 CDT." Date: Wed, 25 Oct 1995 18:32:50 +0100 Message-ID: <469.814642370@palmer.demon.co.uk> From: Gary Palmer Sender: owner-stable@freebsd.org Precedence: bulk John Fieber stands accused of writing in message ID : >* Can the boot prompt switches be document in a useful place, i.e. at > the boot prompt? Not really - there isn't enough room in the boot blocks to do all the stuff we want as it is, and definately not enough room to put explanations of the various boot flags. This is one reason why a lot of people are shouting for a 3 stage boot process. >* Can I set things up so I can boot without typing -r every time? Yes: recompile the bootblocks with BOOT_HD. This will (AFAIR) make the boot blocks default to using sd0 instead of wd0, and pass the right parameters to the kernel (so I don't think you need the -r flag anymore). This is what I use here to get round the same problem. >* Why does the kernel think it is booting from sd1 anyway? What boot name did you use? If you use ``hd(1,a)/kernel'' you should be OK. Can't remember - it's been so long since I needed to use it :-) >Other comments: >* The "progress bars" in sysinstall often overshoot the right border of > their box. This is a problem with the cursor. It's never turned off, so it looks like the progress bar is actually extending past the end of the box when it's not. I even believe there is a PR for this, but no-one has bothered to go into the guts of libdialog and fix it, esp. since 2.2 will use a completely different technology. (The problem has been known about since early in the 2.0.5 release process, but we didn't have any time to do anything about it then, and we were all shattered afterwards :-) ) >* What exactly is the intended action of "Undo all" from the > slice and disklabel screens? Pass. Never used them / looked at the code. >* The difference between FTP active and FTP passive needs to be > documented on the media selection help screen. I'm not so sure that we need to. If you need to use passive mode FTP (as you are behind a packet filtering router (a.k.a. a firewall)), you know to look for the option and select it. Otherwise you don't really need to touch the setting. Mebbe if you can come up with a short one or two line description then Jordan will put it in. I can't come up with a short desc. of the differences, but then again maybe I'm too close to the problem (and know WAY too many details about the differences :-/ ) Gary From owner-freebsd-stable Wed Oct 25 15:32:54 1995 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id PAA24657 for stable-outgoing; Wed, 25 Oct 1995 15:32:54 -0700 Received: from fieber-john.campusview.indiana.edu (Fieber-John.campusview.indiana.edu [149.159.1.34]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id PAA24652 ; Wed, 25 Oct 1995 15:32:50 -0700 Received: (from jfieber@localhost) by fieber-john.campusview.indiana.edu (8.6.12/8.6.12) id RAA01032; Wed, 25 Oct 1995 17:32:26 -0500 Date: Wed, 25 Oct 1995 17:32:26 -0500 (EST) From: John Fieber To: "Jordan K. Hubbard" cc: stable@freebsd.org, "Jordan K. Hubbard" Subject: Re: Oct 20 snap install... In-Reply-To: <29769.814653849@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-stable@freebsd.org Precedence: bulk On Wed, 25 Oct 1995, Jordan K. Hubbard wrote: > > Fine, After I figured out that I had to enable the host adapter BIOS on > > my Adaptec 1542C, booteasy allowed me to select the second disk for > > booting. However, the kernel was convinced that it was booting from sd1, > > not sd0 and thus paniced when it tried to mount its root filesystem. > > Hmmmmm. That's interesting. Did you see both wd0 and sd0 in the > disks menu when you were installing it? Just curious, 'cause I've not > had the chance to test that particular scenario before. Yes. I only selected sd0 for the install, and I did it "express". > Not enough room to document them there.. We're at the wall for bytes > as it is.. :-( :( I'm not a kernel hacker, but is there any chance some of their functionality could be added/moved to userconfig. If not, possible a little documentation could go there. It would be better than none. > > * Can I set things up so I can boot without typing -r every time? > > You could re-write your bootblocks with an implicit assumption of > sd1, I guess. You mean sd0? Its the kernel is looking for the root on sd1, it *should* look on sd0. > Still, I have no idea why this thing thinks it's sd1! > That makes simply *no sense* for a drive 0 on your Adaptec! It's not > like the IDE drive is supposed to bump the SCSI drive count! :-) It (correctly) comes up as sd0 in the probe. > It undoes everything, I'm afraid. I could make a more intelligent > undo, but that's going to have to wait for 2.2.. :-( Then in the meantime it should bounce the user back to the beginning menu. As I said, I don't recall where I got bounced, but it wasn't somewhere appropriate. -john == jfieber@indiana.edu =========================================== == http://fieber-john.campusview.indiana.edu/~jfieber ============ From owner-freebsd-stable Wed Oct 25 15:48:54 1995 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id PAA26085 for stable-outgoing; Wed, 25 Oct 1995 15:48:54 -0700 Received: from fieber-john.campusview.indiana.edu (Fieber-John.campusview.indiana.edu [149.159.1.34]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id PAA26080 ; Wed, 25 Oct 1995 15:48:50 -0700 Received: (from jfieber@localhost) by fieber-john.campusview.indiana.edu (8.6.12/8.6.12) id RAA00268; Wed, 25 Oct 1995 17:48:41 -0500 Date: Wed, 25 Oct 1995 17:48:41 -0500 (EST) From: John Fieber To: Gary Palmer cc: stable@freebsd.org, "Jordan K. Hubbard" Subject: Re: Oct 20 snap install... In-Reply-To: <469.814642370@palmer.demon.co.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-stable@freebsd.org Precedence: bulk On Wed, 25 Oct 1995, Gary Palmer wrote: > >* Why does the kernel think it is booting from sd1 anyway? > > What boot name did you use? If you use ``hd(1,a)/kernel'' you should > be OK. Can't remember - it's been so long since I needed to use it :-) Hm.... `hd(1,a)/kernel' does work. I was try `sd(0,a)/kernel' which had the very counter-intuitive result of booting from wd0. However, `-r' is a little quicker to type... It looks like its time for me to learn about boot code whether I want to or not! > >* The difference between FTP active and FTP passive needs to be > > documented on the media selection help screen. > > I'm not so sure that we need to. If you need to use passive mode FTP > (as you are behind a packet filtering router (a.k.a. a firewall)), you > know to look for the option and select it. Otherwise you don't really > need to touch the setting. Wrong answer. The people who need passive don't need the documentation. The rest, and that would be the majority, will do like I did and go "Huh? What the hell is the difference between active and passive ftp?" and not know which one to select appropriate. In fact, a better alternative would be to rephrase the options to be less cryptic, e.g.: [ ] FTP (normal) [ ] FTP (through a firewall) -john == jfieber@indiana.edu =========================================== == http://fieber-john.campusview.indiana.edu/~jfieber ============ From owner-freebsd-stable Wed Oct 25 16:06:03 1995 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id QAA27450 for stable-outgoing; Wed, 25 Oct 1995 16:06:03 -0700 Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id QAA27435 ; Wed, 25 Oct 1995 16:05:57 -0700 Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.12/8.6.9) with SMTP id QAA07860; Wed, 25 Oct 1995 16:03:52 -0700 To: John Fieber cc: Gary Palmer , stable@freebsd.org, "Jordan K. Hubbard" Subject: Re: Oct 20 snap install... In-reply-to: Your message of "Wed, 25 Oct 1995 17:48:41 CDT." Date: Wed, 25 Oct 1995 16:03:52 -0700 Message-ID: <7858.814662232@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-stable@freebsd.org Precedence: bulk > It looks like its time for me to learn about boot code whether I want to > or not! You'll enjoy it, trust me! :) > Wrong answer. The people who need passive don't need the documentation. > The rest, and that would be the majority, will do like I did and go "Huh? > What the hell is the difference between active and passive ftp?" and not > know which one to select appropriate. In fact, a better alternative would > be to rephrase the options to be less cryptic, e.g.: OK, here's what the relevant chunk of menus.c looks like now: { "FTP Active", "Install from an FTP server in active mode", DMENU_CALL, mediaSetFTPActive, 0, 0 }, { "FTP Passive", "Install through a firewall in passive FTP mode", DMENU_CALL, mediaSetFTPPassive, 0, 0 }, Will that do? I'll also ammend the media menu, as you suggested. Please also note that documentation enhancement requests that are accompanied by *the actual text* will always get priority treatment from me! :-) Jordan From owner-freebsd-stable Wed Oct 25 16:18:39 1995 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id QAA28407 for stable-outgoing; Wed, 25 Oct 1995 16:18:39 -0700 Received: from fieber-john.campusview.indiana.edu (Fieber-John.campusview.indiana.edu [149.159.1.34]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id QAA28392 ; Wed, 25 Oct 1995 16:18:32 -0700 Received: (from jfieber@localhost) by fieber-john.campusview.indiana.edu (8.6.12/8.6.12) id SAA00329; Wed, 25 Oct 1995 18:18:21 -0500 Date: Wed, 25 Oct 1995 18:18:20 -0500 (EST) From: John Fieber To: "Jordan K. Hubbard" cc: Gary Palmer , stable@freebsd.org, "Jordan K. Hubbard" Subject: Re: Oct 20 snap install... In-Reply-To: <7858.814662232@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-stable@freebsd.org Precedence: bulk On Wed, 25 Oct 1995, Jordan K. Hubbard wrote: > OK, here's what the relevant chunk of menus.c looks like now: > > { "FTP Active", "Install from an FTP server in active mode", > DMENU_CALL, mediaSetFTPActive, 0, 0 }, > { "FTP Passive", "Install through a firewall in passive FTP mode", > DMENU_CALL, mediaSetFTPPassive, 0, 0 }, > > Will that do? I'll also ammend the media menu, as you suggested. I don't like the terminology `Active' because if a user does not know the difference between active and passive, it does not provide any useful hint about which FTP option to use. Saying just `FTP' and `Passive FTP' gives an obvious, and probably correct, choice to users who don't know what `Passive FTP' means. -john == jfieber@indiana.edu =========================================== == http://fieber-john.campusview.indiana.edu/~jfieber ============ From owner-freebsd-stable Wed Oct 25 16:38:37 1995 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id QAA29778 for stable-outgoing; Wed, 25 Oct 1995 16:38:37 -0700 Received: from george.lbl.gov (george.lbl.gov [128.3.196.93]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id QAA29770 for ; Wed, 25 Oct 1995 16:38:32 -0700 Received: (jin@localhost) by george.lbl.gov (8.6.10/8.6.5) id QAA23865; Wed, 25 Oct 1995 16:38:30 -0700 Date: Wed, 25 Oct 1995 16:38:30 -0700 From: "Jin Guojun[ITG]" Message-Id: <199510252338.QAA23865@george.lbl.gov> To: stable@freebsd.org Subject: ep0 broken on 2.1-951020-SNAP Cc: jin@george.lbl.gov Content-Length: 1553 Sender: owner-stable@freebsd.org Precedence: bulk This was send by send-pr. In my experience, I got respond by reporting to bug@freebsd.org, but not respond by reporting to send-pr, so, I am not sure that send-pr works. So, I duplicated message to you. >Synopsis: ep0 cannot be configured and more. >Severity: critical >Priority: high >Category: kern >Release: FreeBSD 2.1-STABLE i386 >Class: sw-bug | change-request >Environment: 3Com Elink-III 3c509 ethernet card tested with many motherboards The all files are dated OCT. 21, and floppy is dated OCT. 23. >Description: The 3c509 ethernet card has been found, but not configured to given host id: # ifconfig -a lp0: flags=8810 mtu 1500 ep0: flags=863 mtu 1500 ether 00:00:24:34:12:d7 lo0: flags=8009 mtu 16384 inet 127.0.0.1 netmask 0xff000000 sl0: flags=c010 mtu 552 tun0: flags=8010 mtu 1500 Also, after manually configuring ep0 correctly, it won't go further than one hop. i.e., if the machine is on 128.3.123 net, then, it won't see 128.3.124 net even though it can see the router and all other hosts on the 128.3.123 net. >How-To-Repeat: See Description >Fix: The installer works fine. I rebuild the kernel, the problem is still in. So, the bug is in some modified code for either the 3Com driver or in the network driver. From owner-freebsd-stable Wed Oct 25 16:45:32 1995 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id QAA00340 for stable-outgoing; Wed, 25 Oct 1995 16:45:32 -0700 Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id QAA00326 ; Wed, 25 Oct 1995 16:45:26 -0700 Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.12/8.6.9) with SMTP id QAA08033; Wed, 25 Oct 1995 16:34:54 -0700 To: John Fieber cc: Gary Palmer , stable@freebsd.org, "Jordan K. Hubbard" Subject: Re: Oct 20 snap install... In-reply-to: Your message of "Wed, 25 Oct 1995 18:18:20 CDT." Date: Wed, 25 Oct 1995 16:34:54 -0700 Message-ID: <8031.814664094@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-stable@freebsd.org Precedence: bulk > I don't like the terminology `Active' because if a user does not know the > difference between active and passive, it does not provide any useful hint > about which FTP option to use. Saying just `FTP' and `Passive FTP' gives > an obvious, and probably correct, choice to users who don't know what > `Passive FTP' means. I'm inclined to agree, actually. It always struck me as awkward the way it was worded before. Changed! Jordan From owner-freebsd-stable Wed Oct 25 19:58:56 1995 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id TAA20319 for stable-outgoing; Wed, 25 Oct 1995 19:58:56 -0700 Received: from fieber-john.campusview.indiana.edu (Fieber-John.campusview.indiana.edu [149.159.1.34]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id TAA20296 ; Wed, 25 Oct 1995 19:58:50 -0700 Received: (from jfieber@localhost) by fieber-john.campusview.indiana.edu (8.6.12/8.6.12) id VAA00847; Wed, 25 Oct 1995 21:58:17 -0500 Date: Wed, 25 Oct 1995 21:58:16 -0500 (EST) From: John Fieber To: Michael Smith cc: gary@palmer.demon.co.uk, stable@freebsd.org, jkh@freebsd.org Subject: Re: Oct 20 snap install... In-Reply-To: <199510260237.MAA09365@genesis.atrad.adelaide.edu.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-stable@freebsd.org Precedence: bulk On Thu, 26 Oct 1995, Michael Smith wrote: > John Fieber stands accused of saying: > > > What boot name did you use? If you use ``hd(1,a)/kernel'' you should > > > be OK. Can't remember - it's been so long since I needed to use it :-) > > > > Hm.... `hd(1,a)/kernel' does work. I was try `sd(0,a)/kernel' which had > > the very counter-intuitive result of booting from wd0. However, `-r' is a > > little quicker to type... > > The comment about hd(1,a) is even in the boot banner. Dunno where else > it could be put 8) On one line of the boot prompt it say hd(1,a), and another line says wd(0,a). There is a potential confliciting message there. Someone who knows that FreeBSD refers to disks as either wd or sd, hd(1,a) could easily be interpreted as meaning you should type sd(1,a) or wd(1,a) to boot from the second disk, be it SCSI or ide. Personally, I've always been puzzled by the first line in the boot prompt. Again, I think it would be really nifty to move some of this boot configuration stuff into userconfig where there is a bit more room to provide a usable interface. > There's a #define for /sys/i386/boot/biosboot/boot.c - BOOT_HD that > builds a bootblock that boots from the _second_ bios disk, but passes > in a minor number of 0 to the kernel. This is what's required to make > the above scenario work. Thanks for the tip. Looks like my course in 80x86 assembly may finally be of some use... -john == jfieber@indiana.edu =========================================== == http://fieber-john.campusview.indiana.edu/~jfieber ============ From owner-freebsd-stable Wed Oct 25 20:05:21 1995 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id UAA21423 for stable-outgoing; Wed, 25 Oct 1995 20:05:21 -0700 Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id UAA21416 ; Wed, 25 Oct 1995 20:05:17 -0700 Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.12/8.6.9) with SMTP id UAA12209; Wed, 25 Oct 1995 20:02:57 -0700 To: John Fieber cc: Michael Smith , gary@palmer.demon.co.uk, stable@freebsd.org, jkh@freebsd.org Subject: Re: Oct 20 snap install... In-reply-to: Your message of "Wed, 25 Oct 1995 21:58:16 CDT." Date: Wed, 25 Oct 1995 20:02:56 -0700 Message-ID: <12207.814676576@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-stable@freebsd.org Precedence: bulk > been puzzled by the first line in the boot prompt. Again, I think it > would be really nifty to move some of this boot configuration stuff into > userconfig where there is a bit more room to provide a usable interface. Diffs? :-) Jordan From owner-freebsd-stable Wed Oct 25 20:06:07 1995 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id UAA21553 for stable-outgoing; Wed, 25 Oct 1995 20:06:07 -0700 Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id UAA21534 ; Wed, 25 Oct 1995 20:06:00 -0700 Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.12/8.6.9) with SMTP id UAA12196; Wed, 25 Oct 1995 20:02:28 -0700 To: Michael Smith cc: jfieber@indiana.edu (John Fieber), gary@palmer.demon.co.uk, stable@freebsd.org, jkh@freebsd.org Subject: Re: Oct 20 snap install... In-reply-to: Your message of "Thu, 26 Oct 1995 12:07:21 +0930." <199510260237.MAA09365@genesis.atrad.adelaide.edu.au> Date: Wed, 25 Oct 1995 20:02:27 -0700 Message-ID: <12194.814676547@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-stable@freebsd.org Precedence: bulk > The passive option is still half useless without socks libraries in the > installer. (In fact, I received _zero_ responses to my question asking > about proxy FTP servers, so I've reluctantly concluded that socks is all > that there is) Weeelllll.. I wouldn't quite say that. Passive FTP truly takes care of a *lot* of firewalled folks, including everybody I know at Cisco (and if they don't represent a good example of a seriously facist network then nobody does!). You can also specify an arbitrary port number with the current install as part of the URL, e.g.: ftp://foo.bar.com:/path And this takes care of a lot of the proxies.. More than that, I dunno.. There are limits to how far I'm willing to bend over backwards to deal with sites who'd really prefer that their users go back to passing information back and forth on paper and get those scary network connectors unplugged from their machines! :-) Jordan From owner-freebsd-stable Wed Oct 25 21:47:00 1995 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id VAA02210 for stable-outgoing; Wed, 25 Oct 1995 21:47:00 -0700 Received: from rocky.sri.MT.net (sri.MT.net [204.94.231.129]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id VAA02204 for ; Wed, 25 Oct 1995 21:46:58 -0700 Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id WAA00923; Wed, 25 Oct 1995 22:49:12 -0600 Date: Wed, 25 Oct 1995 22:49:12 -0600 From: Nate Williams Message-Id: <199510260449.WAA00923@rocky.sri.MT.net> To: stable@FreeBSD.org Subject: More 951020-SNAP problems Sender: owner-stable@FreeBSD.org Precedence: bulk I just noticed that a 'make world' on a system installed with this SNAP had tons of modifications when mtree was run on the system. In particular, none of the /usr/share/man/cat? directories existed until I ran the mtree stuff. I remember this problem happening in 2.0.5 as well, so would it be possible as part of the install process to run mtree on the system just before the person boots off the hard-drive? Nate From owner-freebsd-stable Thu Oct 26 00:28:04 1995 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id AAA17652 for stable-outgoing; Thu, 26 Oct 1995 00:28:04 -0700 Received: from iselgw.ilab.toshiba.co.jp (iselgw.ilab.toshiba.co.jp [202.249.10.129]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id AAA17637 for ; Thu, 26 Oct 1995 00:27:52 -0700 Received: by iselgw.ilab.toshiba.co.jp (8.6.7/MMLAB-1.0) with UUCP id QAA04510; Thu, 26 Oct 1995 16:27:16 +0900 Received: from ilab-master.ilab.toshiba.co.jp by isel3.mmlab.toshiba.co.jp (5.67+1.6W/6.4J.6-mmlab_2.60) id AA28325; Thu, 26 Oct 95 16:26:36 JST Received: from pdcd-mail.pdcd.ilab.toshiba.co.jp by ilab-master.ilab.toshiba.co.jp (8.6.11+2.5Wb2/3.3W9-ilab2.1) with ESMTP id QAA06571; Thu, 26 Oct 1995 16:26:35 +0900 Received: by pdcd-mail.pdcd.ilab.toshiba.co.jp (8.6.11+2.5Wb2+PDCD/3.3W9-pdcd7.1) with ESMTP id QAA15673; Thu, 26 Oct 1995 16:26:35 +0900 Message-Id: <199510260726.QAA15673@pdcd-mail.pdcd.ilab.toshiba.co.jp> To: "Andrew V. Stesin" Cc: stable@freebsd.org, tateoka@pdcd.ilab.toshiba.co.jp Subject: Re: I have problem with 2.1.0-951020-SNAP In-Reply-To: Your message of "Tue, 24 Oct 1995 15:37:28 +0200." <199510241337.PAA25483@office.elvisti.kiev.ua> Date: Thu, 26 Oct 1995 16:26:32 +0900 From: Masamichi Tateoka Sender: owner-stable@freebsd.org Precedence: bulk Hello Andrew. Thank you very much for your reply. My serial card is using STARTECH ST16C550PC. I don't know that whether it has a FIFO bug. Do you know? Last night, I made karnel from 2.0.5R ssys with 2.0R sio.c. and it worked better.(At least, uucico completed the sending.) So, I think There are some problems in the diff of 2.0R sio.c and 2.0.5R's. I'm going to check the diff. ( or changing my chip is better? ) With best regards. Masamichi Tateoka (tateoka@pdcd.ilab.toshiba.co.jp ) (tateoka@yasai.forus.or.jp (HOME) ) From owner-freebsd-stable Thu Oct 26 10:46:31 1995 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id KAA15447 for stable-outgoing; Thu, 26 Oct 1995 10:46:31 -0700 Received: from hawk.gnome.co.uk (gnome.demon.co.uk [158.152.22.16]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id KAA15322 for ; Thu, 26 Oct 1995 10:43:15 -0700 Received: (from jacs@localhost) by hawk.gnome.co.uk (8.6.12/8.6.12) id RAA06092; Thu, 26 Oct 1995 17:37:51 GMT Date: Thu, 26 Oct 1995 17:37:51 GMT Subject: make world fails To: freebsd-stable@freebsd.org From: jacs@gnome.co.uk (Chris Stenton) Message-Id: Sender: owner-stable@freebsd.org Precedence: bulk For some reason the Makefile in FreeBSD-stable/src/sbin/startslip was changed on Oct 23 to SRCS= startslip.c uucplock.c as uucplock.c does not live there make falls over. Chris From owner-freebsd-stable Thu Oct 26 13:14:19 1995 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id NAA21687 for stable-outgoing; Thu, 26 Oct 1995 13:14:19 -0700 Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id NAA21677 for ; Thu, 26 Oct 1995 13:14:14 -0700 Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.12/8.6.9) with SMTP id NAA21681; Thu, 26 Oct 1995 13:11:54 -0700 To: jacs@gnome.co.uk (Chris Stenton) cc: freebsd-stable@freebsd.org Subject: Re: make world fails In-reply-to: Your message of "Thu, 26 Oct 1995 17:37:51 GMT." Date: Thu, 26 Oct 1995 13:11:53 -0700 Message-ID: <21679.814738313@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-stable@freebsd.org Precedence: bulk It's been fixed. You're lagging behind again.. :-) Jordan > > For some reason the Makefile in FreeBSD-stable/src/sbin/startslip > was changed on Oct 23 to > > SRCS= startslip.c uucplock.c > > as uucplock.c does not live there make falls over. > > > > Chris > From owner-freebsd-stable Sat Oct 28 11:03:09 1995 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id LAA02690 for stable-outgoing; Sat, 28 Oct 1995 11:03:09 -0700 Received: from meter.eng.uci.edu (root@meter.eng.uci.edu [128.200.85.3]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id LAA02685 ; Sat, 28 Oct 1995 11:03:06 -0700 Received: from newport.ece.uci.edu by meter.eng.uci.edu (8.7) id LAA07003; Sat, 28 Oct 1995 11:03:03 -0700 (PDT) Received: from localhost by newport.ece.uci.edu (8.7) id LAA12313; Sat, 28 Oct 1995 11:03:02 -0700 (PDT) Message-Id: <199510281803.LAA12313@newport.ece.uci.edu> To: stable@freebsd.org cc: bugs@freebsd.org Subject: probs with latest stable snap Date: Sat, 28 Oct 1995 11:03:01 -0700 From: Steven Wallace Sender: owner-stable@freebsd.org Precedence: bulk I installed the latest snapshot and have some probs: First, when installing, I tried to create two freebsd partitions on the same drive. When it tried to format the partitions, I got "/dev/rsd0s1a: 'a' partition is unavailable" I deleted one partition and was able to continue installing on the other. Another problem I have is running 'xclock'. I get this message: "Warning: Select failed; error code 22", which repeats indefinitely. This is from the xclock distributed on the 2.0.5 cdrom. Also, this morning I woke up to found my computer had rebooted itself and it was in a continuous reboot loop with this panic: (no problems like this in -current) fatal trap 18: integer divide fault while in kernel mode ip = 0x8:0xf019b10b, "pentium_microtime" code segment base 0x0, limit 0xfff type 0x1b, DPL0, press 1, defs 1, gran 1 proc eflags = resume, IOPL = 0 cp = 0 (swapper) i mask = net tty bio Ahh! I have traced it to line 180 of microtime.s: divl %ecx # get value in usec Hmmm, it appears the code checks for pentium_mhz != 0, so it could not be div by 0. However, I looked up div, and it says, "If the dividend is 0 or if the quotient is too large to fit in the result accumulator, a divide error fault (interrupt 0) occurs. So, if the pentium cycle count is > 2^59, then on my 90 MHz pentium (correctly reported), the fault will occur. I do not know what originally caused the first panic, but it appears it put the pentium clock count to a large number. Then it rebooted and gets into a panic div 0 loop. I noticed that after I hit reset, then it booted up just fine (resetting the counter?). I noticed in -current code it has a i586_ctr_bias long long which gets initialized and subtracts the cycle count before the division in microtime.s. I think something like this should be put into -stable to prevent this panic. Steven From owner-freebsd-stable Sat Oct 28 11:41:41 1995 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id LAA07509 for stable-outgoing; Sat, 28 Oct 1995 11:41:41 -0700 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id LAA07488 ; Sat, 28 Oct 1995 11:41:35 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id FAA05152; Sun, 29 Oct 1995 05:39:01 +1100 Date: Sun, 29 Oct 1995 05:39:01 +1100 From: Bruce Evans Message-Id: <199510281839.FAA05152@godzilla.zeta.org.au> To: stable@freebsd.org, swallace@ece.uci.edu Subject: Re: probs with latest stable snap Cc: bugs@freebsd.org Sender: owner-stable@freebsd.org Precedence: bulk >Ahh! I have traced it to line 180 of microtime.s: > divl %ecx # get value in usec >Hmmm, it appears the code checks for pentium_mhz != 0, so it could not >be div by 0. However, I looked up div, and it says, "If the >dividend is 0 or if the quotient is too large to fit in the result accumulator, a divide error fault (interrupt 0) occurs. >So, if the pentium cycle count is > 2^59, then on my 90 MHz pentium >(correctly reported), the fault will occur. I do not know what originally >caused the first panic, but it appears it put the pentium clock count >to a large number. Then it rebooted and gets into a panic div 0 loop. >I noticed that after I hit reset, then it booted up just fine (resetting >the counter?). >I noticed in -current code it has a i586_ctr_bias long long which >gets initialized and subtracts the cycle count before the division >in microtime.s. I think something like this should be put into -stable >to prevent this panic. Normally the counter gets set every clock tick. This reduces the dividend in much the same way as subtracting i586_ctr_bias, so there should be no problem dividing. However, microtime() is apparently sometimes called before the counter has been reset after booting. -current initializes i586_ctr_bias early so there should be no problem. The equivalent in -stable would be resetting the counter early. Bruce From owner-freebsd-stable Sat Oct 28 12:59:39 1995 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id MAA16254 for stable-outgoing; Sat, 28 Oct 1995 12:59:39 -0700 Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id MAA16230 ; Sat, 28 Oct 1995 12:59:32 -0700 Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.12/8.6.9) with SMTP id MAA04838; Sat, 28 Oct 1995 12:59:08 -0700 To: Steven Wallace cc: stable@freebsd.org, bugs@freebsd.org Subject: Re: probs with latest stable snap In-reply-to: Your message of "Sat, 28 Oct 1995 11:03:01 PDT." <199510281803.LAA12313@newport.ece.uci.edu> Date: Sat, 28 Oct 1995 12:59:08 -0700 Message-ID: <4836.814910348@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-stable@freebsd.org Precedence: bulk > First, when installing, I tried to create two freebsd partitions on the > same drive. When it tried to format the partitions, I got > "/dev/rsd0s1a: 'a' partition is unavailable" DO NOT DO THAT. I guess I'll have to make it an error to do so since there are a lot of ways you can hose yourself if you do this (for one thing, it will only boot from the first partition it finds). Jordan From owner-freebsd-stable Sat Oct 28 22:20:36 1995 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id WAA29096 for stable-outgoing; Sat, 28 Oct 1995 22:20:36 -0700 Received: from meter.eng.uci.edu (root@meter.eng.uci.edu [128.200.85.3]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id WAA29091 for ; Sat, 28 Oct 1995 22:20:34 -0700 Received: from newport.ece.uci.edu by meter.eng.uci.edu (8.7) id WAA16175; Sat, 28 Oct 1995 22:20:32 -0700 (PDT) Received: from localhost by newport.ece.uci.edu (8.7) id WAA26107; Sat, 28 Oct 1995 22:11:55 -0700 (PDT) Message-Id: <199510290511.WAA26107@newport.ece.uci.edu> To: stable@freebsd.org Subject: telnet Date: Sat, 28 Oct 1995 22:11:54 -0700 From: Steven Wallace Sender: owner-stable@freebsd.org Precedence: bulk latest snap bin dist + des distrubition. pal-r32-a07b-des >> telnet ld.so: telnet: Can't find shared library "libdes.so.2.0" ldd /usr/bin/telnet /usr/bin/telnet: -ltermcap.2 => /usr/lib/libtermcap.so.2.1 (0x802b000) -ltelnet.2 => /usr/lib/libtelnet.so.2.0 (0x802f000) -ldes.2 => not found (0x0) -lkrb.2 => not found (0x0) -lc.2 => /usr/lib/libc.so.2.2 (0x8039000) -ldes.2 => not found (0x0) -lkrb.2 => not found (0x0) This is WITHOUT kerberos distribution. This telnet should be in krb.* not des.* Actually, I just extracted the telnet from the bin.* distribution and I get: /usr/bin/telnet: -ltermcap.2 => /usr/lib/libtermcap.so.2.1 (0x8029000) -ltelnet.2 => /usr/lib/libtelnet.so.2.0 (0x802d000) -lc.2 => /usr/lib/libc.so.2.2 (0x8037000) -ldes.2 => not found (0x0) -lkrb.2 => not found (0x0) Notice the "des" version has ldes twice while the "normal" version has it once. Subtrat 1 both cases. Hope this helps Steven Steven