Re: 'make includes' ownership patch
On Sat, May 26, 2001 at 03:06:00PM -0700, Kris Kennaway wrote: > On Sat, May 26, 2001 at 02:59:22PM -0700, Kris Kennaway wrote: > > Shouldn't the includes/Makefile be installing headers using > > INCOWN/INCGRP instead of BINOWN/BINGRP? I ran into this when trying > > to do a 'make includes' as a normal user. > > Oops, hit send too soon; more changes are required of the same form. > Before I go to the trouble of doing those, I might as well get > confirmation whether this is the right thing to do. > This was on my TODO. The only problem with INCOWN/INCGRP not being used here is that they were introduced long after include/Makefile. Cheers, -- Ruslan Ermilov Oracle Developer/DBA, [EMAIL PROTECTED] Sunbay Software AG, [EMAIL PROTECTED] FreeBSD committer, +380.652.512.251Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -current is _definitely_ not stable right now
I forgot something: IdlePTD 4734976 initial pcb at 3b5f80 panicstr: mutex sched lock recursed at /usr/src/sys/kern/kern_synch.c:858 panic messages: --- panic: blockable sleep lock (sx) allproc @ /usr/src/sys/kern/kern_proc.c:146 syncing disks... 90 90 panic: mutex sched lock recursed at /usr/src/sys/kern/kern_synch.c:858 A quick look at that file indicates that rwatson is probably off the hook, since he hadn't touched it. -- I need someone really bad. Are you really bad? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -current is _definitely_ not stable right now
I haven't made any mutex commits -- my commits were credential-related.
At least two bugs have popped up and been resolved since the pcred removal
commits, including:
1) Bug in execve() such that saved uids/gids were not being done in some
situations.
2) Bug in crfree() such that there was a reference leak for uidinfo
structures.
I wouldn't be surprised if a couple more turned up.
Robert N M Watson FreeBSD Core Team, TrustedBSD Project
[EMAIL PROTECTED] NAI Labs, Safeport Network Services
On Sun, 27 May 2001, Doug Barton wrote:
> Gang,
>
> I cvs'ed and built world/kernel shortly after jhb's "all clear" on
> thursday, and things went fairly well. I did the same again after rwatson's
> mutex commits on friday and things have gone downhill from there. Just
> about any heavy system activity locks the system up. That includes things
> like building large ports (for example, avifile), buildworld, and trying to
> actually run aviplay.
>
> On the avi front, typing 'aviplay' with or without an argument is
> guaranteed to instantly wedge the box. I attached a lot of running aviplay
> through truss, but I have no way to know if it stopped at or before the
> offending instruction. As for the general wonkiness of the system, I have
> finally gotten a dump. The backtrace is below, let me know if there is
> anything else I can do to help debug.
>
> Doug
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> (kgdb) where
> #0 dumpsys () at /usr/src/sys/kern/kern_shutdown.c:478
> #1 0xc01cb318 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:321
> #2 0xc01cb745 in panic (fmt=0xc0330ce4 "mutex %s recursed at %s:%d")
> at /usr/src/sys/kern/kern_shutdown.c:600
> #3 0xc01c3c9c in _mtx_assert (m=0xc03f44a0, what=9,
> file=0xc0332360 "/usr/src/sys/kern/kern_synch.c", line=858)
> at /usr/src/sys/kern/kern_mutex.c:571
> #4 0xc01d4b9d in mi_switch () at /usr/src/sys/kern/kern_synch.c:858
> #5 0xc01cb01c in boot (howto=256) at /usr/src/sys/kern/kern_shutdown.c:262
> #6 0xc01cb745 in panic (fmt=0xc0334760 "blockable sleep lock (%s) %s @
> %s:%d")
> at /usr/src/sys/kern/kern_shutdown.c:600
> #7 0xc01e60a0 in witness_lock (lock=0xc03f0f60, flags=0,
> file=0xc0331123 "/usr/src/sys/kern/kern_proc.c", line=146)
> at /usr/src/sys/kern/subr_witness.c:489
> #8 0xc01d2285 in _sx_slock (sx=0xc03f0f60, file=0xc0331123
> "/usr/src/sys/kern/kern_proc.c",
> line=146) at /usr/src/sys/kern/kern_sx.c:114
> #9 0xc01c4e2c in pfind (pid=434) at /usr/src/sys/kern/kern_proc.c:146
> #10 0xc01ea3c6 in selwakeup (sip=0xc0e3d404) at
> /usr/src/sys/kern/sys_generic.c:1175
> #11 0xc01f5c5f in ptcwakeup (tp=0xc0e3d420, flag=1) at
> /usr/src/sys/kern/tty_pty.c:317
> #12 0xc01f5c36 in ptsstart (tp=0xc0e3d420) at
> /usr/src/sys/kern/tty_pty.c:306
> #13 0xc01f3074 in ttstart (tp=0xc0e3d420) at /usr/src/sys/kern/tty.c:1409
> #14 0xc01f4685 in tputchar (c=107, tp=0xc0e3d420) at
> /usr/src/sys/kern/tty.c:2458
> #15 0xc01e20cb in putchar (c=107, arg=0xcd115de8) at
> /usr/src/sys/kern/subr_prf.c:304
> #16 0xc01e234a in kvprintf (fmt=0xc034f881 "ernel trap %d with interrupts
> disabled\n",
> func=0xc01e207c , arg=0xcd115de8, radix=10, ap=0xcd115e00
> "\f")
> at /usr/src/sys/kern/subr_prf.c:487
> #17 0xc01e1ff8 in printf (fmt=0xc034f880 "kernel trap %d with interrupts
> disabled\n")
> at /usr/src/sys/kern/subr_prf.c:260
> #18 0xc02f6955 in trap (frame={tf_fs = -854523880, tf_es = -1071775728,
> tf_ds = -855048176,
> tf_edi = 4, tf_esi = -1058806500, tf_ebp = -854499712, tf_isp =
> -854499744,
> tf_ebx = -855029664, tf_edx = -559038242, tf_ecx = 2, tf_eax =
> -559038244,
> tf_trapno = 12, tf_err = 0, tf_eip = -1071892410, tf_cs = 8,
> tf_eflags = 65670,
> tf_esp = -1052624640, tf_ss = -1058806528}) at
> /usr/src/sys/i386/i386/trap.c:253
> #19 0xc01c3846 in _mtx_lock_sleep (m=0xc0e3e51c, opts=0,
> file=0xc0331500 "/usr/src/sys/kern/kern_resource.c", line=793)
> at /usr/src/sys/kern/kern_mutex.c:380
> #20 0xc01ca0cb in uihold (uip=0xc0e3e500) at
> /usr/src/sys/kern/kern_resource.c:793
> #21 0xc01c86f9 in crdup (cr=0xc1423900) at
> /usr/src/sys/kern/kern_prot.c:1349
> #22 0xc021cf8c in access (p=0xcd094860, uap=0xcd115f80)
> at /usr/src/sys/kern/vfs_syscalls.c:1712
> #23 0xc02f841d in syscall (frame={tf_fs = 47, tf_es = 47, tf_ds = 47,
> tf_edi = 134665044,
> tf_esi = 134676528, tf_ebp = -1077940088, tf_isp = -854499372, tf_ebx
> = 134661184,
> tf_edx = 134665044, tf_ecx = 134661218, tf_eax = 33, tf_trapno = 12,
> tf_err = 2,
> tf_eip = 134555356, tf_cs = 31, tf_eflags = 643, tf_esp =
> -1077940132, tf_ss = 47})
> at /usr/src/sys/i386/i386/trap.c:1172
> #24 0xc02e957d in syscall_with_err_pushed ()
> #25 0x804a131 in ?? ()
> #26 0x804caa1 in ?? ()
> #27 0x804e57c in ?? ()
> #28 0x804dd54 in ?? ()
> #29 0x804e57c in ?? ()
> #30 0x804dd54 in ?? ()
> #31 0x804e57c in ?? ()
> #32 0x804dd54 in ?? ()
> #33 0x804e57c in ??
Supported ATAPI cdr/cdrw drives
As promised I've made up a list of reports I've received so far go to http://freebsd.dk/ and follow the link. I also have a patch for the Yamaha's (yamaha-cdr.p1) which also can be found via the above URL. Let me know if that make things work... -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 'make includes' ownership patch
> On Sat, May 26, 2001 at 03:06:00PM -0700, Kris Kennaway wrote: > > On Sat, May 26, 2001 at 02:59:22PM -0700, Kris Kennaway wrote: > > > Shouldn't the includes/Makefile be installing headers using > > > INCOWN/INCGRP instead of BINOWN/BINGRP? I ran into this when trying > > > to do a 'make includes' as a normal user. > > > > Oops, hit send too soon; more changes are required of the same form. > > Before I go to the trouble of doing those, I might as well get > > confirmation whether this is the right thing to do. > > > This was on my TODO. The only problem with INCOWN/INCGRP not being > used here is that they were introduced long after include/Makefile. And perhaps one should go read the commit message that introduced them... it was an experiment, a sample test designed to only be used in -current /usr/src/lib, that BDE, Sheldon and myself had long followon conversations about, and got dropped into the cracks. The name INC* is not clear as to be correct, per BDE it probably should be HDR* or HDRS* (I specifically avoided that since existing Makefiles used that, not knowing that BDE had seperately been eyeing HDRS* for what I ended up calling INC*.) Since, other commiters have ignored direct, and inderect requests not to propogate this INC* experiment, and it now infects all the way back to at least 3.x* and possibly 4.*, making it near impossible to clean up :-(. So feel free to ignore this email and change src/include/Makefile any way you wish... -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 'make includes' ownership patch
On Mon, May 28, 2001 at 10:22:33AM -0700, Rodney W. Grimes wrote: > > This was on my TODO. The only problem with INCOWN/INCGRP not being > > used here is that they were introduced long after include/Makefile. > > And perhaps one should go read the commit message that introduced them... > it was an experiment, a sample test designed to only be used in -current > /usr/src/lib, that BDE, Sheldon and myself had long followon conversations > about, and got dropped into the cracks. What was the reasoning for a serperate owner specification from BIN*? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 'make includes' ownership patch
On Mon, May 28, 2001 at 10:26:11AM -0700, David O'Brien wrote: > On Mon, May 28, 2001 at 10:22:33AM -0700, Rodney W. Grimes wrote: > > > This was on my TODO. The only problem with INCOWN/INCGRP not being > > > used here is that they were introduced long after include/Makefile. > > > > And perhaps one should go read the commit message that introduced them... > > it was an experiment, a sample test designed to only be used in -current > > /usr/src/lib, that BDE, Sheldon and myself had long followon conversations > > about, and got dropped into the cracks. > > What was the reasoning for a serperate owner specification from BIN*? > Because headers are installed with NOBINMODE, not BINMODE :-) Cheers, -- Ruslan Ermilov Oracle Developer/DBA, [EMAIL PROTECTED] Sunbay Software AG, [EMAIL PROTECTED] FreeBSD committer, +380.652.512.251Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 'make includes' ownership patch
> On Mon, May 28, 2001 at 10:22:33AM -0700, Rodney W. Grimes wrote:
> > > This was on my TODO. The only problem with INCOWN/INCGRP not being
> > > used here is that they were introduced long after include/Makefile.
> >
> > And perhaps one should go read the commit message that introduced them...
> > it was an experiment, a sample test designed to only be used in -current
> > /usr/src/lib, that BDE, Sheldon and myself had long followon conversations
> > about, and got dropped into the cracks.
>
> What was the reasoning for a serperate owner specification from BIN*?
Simple orthagonality. Ie, each bsd.*.mk file typically has a seperate
set of *{DIR/OWN/GRP/MODE} specs. bsd.inc.mk was cloned from another
bsd.*.mk file.
--
Rod Grimes - KD7CAX @ CN85sl - (RWG25) [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
wierdness with mountd
Over the last couple of weeks, I've seen wierd statements coming out of mountd: On startup: May 28 10:16:04 farrago mountd[216]: can't delete exports for / On a mount of /usr/obj: May 28 10:21:43 farrago mountd[217]: can't delete exports for /tmp May 28 10:21:43 farrago mountd[217]: can't delete exports for /usr/obj Here's my exports file: /space/compiles/tstsys farrago Say what? Can anyone say what's ailing mountd here? My systems is a mergemaster'd build/installworld from a couple of days ago. -matt Here's my fstab: /dev/da0a / ufs rw 1 1 /dev/da0b noneswapsw 0 0 /dev/ad0a /altrootufs rw,noauto 0 0 proc/proc procfs rw 0 0 blade:/storage0/home/home nfs rw 0 0 beppo:/usr/ports/usr/ports nfs rw 0 0 beppo:/space/freebsd/FreeBSD-current/sys /tstsysnfs rw 0 0 farrago:/space/compiles/tstsys /tstsys/compile nfs rw,noauto 0 0 beppo:/space/freebsd/ncvs /home/ncvs nfs rw,noauto 0 0 and tmp and /tstsys/compile are devices created/mounted in rc.local: mount /home/ncvs mount /tstsys/compile #mount /tstsys/modules # mdconfig -a -t swap -s 128M -u 10 disklabel -r -w md10 auto newfs -f `sysctl -n hw.pagesize` /dev/md10c #tunefs -n enable /dev/md10c mount /dev/md10c /tmp chmod 1777 /tmp To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Panic during -CURRENT buildworld
This is on a system (my laptop):
FreeBSD localhost 5.0-CURRENT FreeBSD 5.0-CURRENT #13: Sun May 27 23:44:24 PDT 2001
[EMAIL PROTECTED]:/common/C/obj/usr/src/sys/LAPTOP_30W i386 Mon May 28
07:27:59 PDT 2001
Recent CVSup activity:
CVSup begin from cvsup14.freebsd.org at Sat May 26 03:47:01 PDT 2001
CVSup ended from cvsup14.freebsd.org at Sat May 26 03:52:48 PDT 2001
CVSup begin from cvsup14.freebsd.org at Sun May 27 03:47:01 PDT 2001
CVSup ended from cvsup14.freebsd.org at Sun May 27 03:53:36 PDT 2001
CVSup begin from cvsup14.freebsd.org at Mon May 28 03:47:00 PDT 2001
CVSup ended from cvsup14.freebsd.org at Mon May 28 03:53:51 PDT 2001
I had tried the buildworld within X (as had been my normal practice until
the recent difficulties with swap and/or VM), and the system re-booted
itself. Got the well-discussed symptom of an active file system failing
fsck's check of primary vs. first alternate superblock, and after fsck
got finished with the file system, soft updates got turned off, so I turned
soft updates back on again.
Since I was in single-user mode anyhow, I mounted the necessary file
systems, issued a "swapon -a", and proceeded to re-try the "make
buildworld" (& friends) -- from within "script" (again, as I usually do).
Here's a transcript of the first & last parts of the typescript file:
Script started on Mon May 28 01:21:19 2001
# mount && cd /usr/src && uname -a && date && make buildworld && date && make kernel
KERNCONF=LAPTOP_30W && date && make installworld && date && mergemaster && date &&
sync && df -k
/dev/ad0s3a on / (ufs, local, soft-updates)
devfs on /dev (devfs, local)
/dev/ad0s3e on /usr (ufs, local, soft-updates)
/dev/ad0s3g on /var (ufs, local, soft-updates)
procfs on /proc (procfs, local)
/dev/ad0s3h on /common (ufs, local, soft-updates)
FreeBSD 5.0-CURRENT FreeBSD 5.0-CURRENT #13: Sun May 27 23:44:24 PDT 2001
[EMAIL PROTECTED]:/common/C/obj/usr/src/sys/LAPTOP_30W i386
Mon May 28 01:22:06 PDT 2001
--
>>> Rebuilding the temporary build tree
--
rm -rf /usr/obj/usr/src/i386
... [elided -- dhw]
cc -pg -O -pipe -I. -I/usr/src/lib/libncurses -I/usr/src/lib/libncurses/../../c
ontrib/ncurses/ncurses -I/usr/src/lib/libncurses/../../contrib/ncurses/include -
Wall -DFREEBSD_NATIVE -DNDEBUG -DHAVE_CONFIG_H -DTERMIOS -I/usr/obj/usr/src/i386
/usr/include -c /usr/src/lib/libncurses/../../contrib/ncurses/ncurses/tinfo/get
env_num^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
And a hand-transcription of the panic (starting with the last command
shown on the console from the "make buildworld"):
cc -fpic -DPIC -O -pipe -I. -I/usr/src/lib/libncurses
-I/usr/src/lib/libncurses/../../contrib/ncurses/ncurses
-I/usr/src/lib/libncurses/../../contrib/ncurses/include -Wall -DFREEBSD_NATIVE
-DNDEBIG -DHAVE_CONFIG_H -DTERMIOS -i/usr/obj/usr/src/i386/usr/include -c lib_gen.c -o
libgen.So
freeing uidinfo: uid=0, proccnt=33
kernel trap 12 with interrupts disabled
panic: blockable sleep lock (sleep mutex) Giant @/usr/src/sys/vm/vm_fault.c:213
Debugger("panic")
Stopped atDebugger+0x44: pushl %ebx
db> trace
Debugger(c03a499b) at Debugger+0x44
panic(c03a75e0,c03a3820,c03cc4b4,c03c1d9b,d5) at panic+0x70
witness_lock(c047dda0,8,c03c1d9b,d5) at witness_lock+0x1b2
vm_fault(c04692ac,deadc000,1,0,0) at vm_fault+0xb2
trap_pfault(ce7f4e34,0,deadc2af,ce7ffa60,c0e4259c) at trap_pfault+0x5d0
trap(ce7f0018,c01f0010,c01f0010,4,c0e4259c) at trap+0x5d0
calltrap() at calltrap+0x5
--- trap 0xc, eip=0xc01d8cb6, esp=0xce7f4e74, ebp=0xce7f4e80 ---
uihold(c0e42580,c1ca3a68,c03a4235,0,98) at uihold+0x5f
crdup(c0e3d600, ce7ffb7c,ce7ffa60,2,c0445a00) at crdup+0x4c
access(ce7ffa60,ce7f4f80,806b240,806f080,805d1ce) at access+0x18
syscall(2f,2f,2f,805d1ce,806f080) at syscall+0x71d
syscall_with_err_pushed() at syscall_with_err_pushed+0x1b
In addition to the kernel.old (dated a few hours earlier the same day), I
have a saved kernel from 16 May (which is the one from which I had booted
in order to build the one from 23:50 (PDT) on 27 May, so I could try that.
Or I could try some other things, if that might help identify the problem.
I have not (yet) tried any of the posted experimental patches against
anything involving file systems, soft updates, swap, or VM. (I do have
a small patch for keyboard control of the sound "mute" function, as well
as some bits & pieces of some of Doug Ambrisko's sys/dev/an patches.
However, the Cisco/Aironet card wasn't inserted at any point during the
boot that did the panic.)
Help?
Thanks,
david
--
David H. Wolfskill [EMAIL PROTECTED]
As a computing professional, I believe it would be unethical for me to
advise, recommend, or support the use (save possibly for personal
amusement) of any product that is or depends on any Microsoft product.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe
Re: wierdness with mountd
In article <[EMAIL PROTECTED]>, Matthew Jacob <[EMAIL PROTECTED]> wrote: > > Over the last couple of weeks, I've seen wierd statements coming out of > mountd: > > On startup: > > May 28 10:16:04 farrago mountd[216]: can't delete exports for / > > On a mount of /usr/obj: > > May 28 10:21:43 farrago mountd[217]: can't delete exports for /tmp > May 28 10:21:43 farrago mountd[217]: can't delete exports for /usr/obj I've been seeing this too, on a -current system from around May 5. John To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make release failure
If memory serves me right, Dima Dorfman wrote:
> "David O'Brien" <[EMAIL PROTECTED]> writes:
> > On Sun, May 27, 2001 at 11:32:09PM -0700, Bruce A. Mah wrote:
> > > +.if !defined(NORELNOTES)
> >
> > Do we really need Yet Another Knob? Why isn't NODOC suffient?
>
> FWIW, I think we should lose NORELNOTES; as you say, NODOC is
> sufficient.
You both speak the truth. :-)
The following patch fixes the make release breakage and brings the
behavior formerly controlled by NORELNOTES under NODOC. I'm going to
do a little (more) testing today, followed by a commit and some more
testing. Feedback is as usual appreciated...
Thanks for the help all...
Bruce.
Index: Makefile
===
RCS file: /home/ncvs/src/release/Makefile,v
retrieving revision 1.618
diff -u -r1.618 Makefile
--- Makefile2001/05/25 18:01:31 1.618
+++ Makefile2001/05/28 18:38:35
@@ -69,15 +69,11 @@
# CPU cycles (some of the programs are C++, and things like ghostscript
# belong to the required ports nevertheless).
#
-# Setting this also disables doc.2 (RELNOTESng).
+# Setting this also disables building of release note documentation
+# (RELNOTESng).
#NODOC= YES
#NOPORTS= YES
-# RELNOTESng can be disabled by uncommenting the following variable
-# definition. RELNOTESng depends on having ports enabled for this
-# release build.
-#NORELNOTES= YES
-
# Uncomment and modify this definition if you want the release notes
# and other release documentation in a language other than English.
#RELNOTES_LANG=en_US.ISO_8859-1
@@ -109,7 +105,7 @@
# on the boot floppy. WARNING: Breaks on some Athlon (K7) motherboards.
AUTO_KEYBOARD_DETECT?= 0
-.if !defined(NORELNOTES)
+.if !defined(NODOC)
DIST_DOCS_ARCH_INDEP= readme errata
DIST_DOCS_ARCH_DEP=installation relnotes hardware
.endif
@@ -219,9 +215,7 @@
.endif
.if !defined(NODOC)
-DOCREL= doc.1
-.if !defined(NORELNOTES)
-DOCREL+= doc.2
+DOCREL= doc.1 doc.2
.endif
.endif
@@ -240,11 +234,6 @@
@echo "unset NOPORTS, or set at least DOMINIMALDOCPORTS to YES!"
@exit 1
.endif
-.if !defined(NORELNOTES) && defined(NODOC)
- @echo "Docs are required for building the release notes. Either"
- @echo "set NORELNOTES or unset NODOC!"
- @exit 1
-.endif
.if make(release)
.if exists(${CHROOTDIR})
# The first command will fail on a handful of files that have their schg
@@ -357,9 +346,6 @@
.if defined(NOSRC)
echo "export NOSRC=${NOSRC}">> ${CHROOTDIR}/mk
.endif
-.if defined(NORELNOTES)
- echo "export NORELNOTES=${NORELNOTES}" >> ${CHROOTDIR}/mk
-.endif
.if defined(RELNOTES_LANG)
echo "export RELNOTES_LANG=${RELNOTES_LANG}">> ${CHROOTDIR}/mk
.else
@@ -617,7 +603,7 @@
ln ${RD}/mfsfd/stand/etc/services ${RD}/mfsfd/etc/services
ln ${RD}/mfsfd/stand/etc/netconfig ${RD}/mfsfd/etc/netconfig
gzip -9c ${.CURDIR}/../COPYRIGHT > ${RD}/mfsfd/stand/help/COPYRIGHT.hlp.gz
-.if !defined(NORELNOTES)
+.if !defined(NODOC)
@for i in ${DIST_DOCS_ARCH_INDEP}; do \
gzip -9c ${.CURDIR}/doc/${RELNOTES_LANG}/$$i/article.txt >
${RD}/mfsfd/stand/help/`echo $${i} | tr 'a-z' 'A-Z'`.TXT.gz; \
done
@@ -694,8 +680,13 @@
@sh -e ${.CURDIR}/scripts/doFS.sh ${RD}/floppies/fixit.flp ${RD} \
${MNT} ${FIXITSIZE} ${RD}/fixitfd ${FIXITINODE} ${FIXITLABEL}
# Do our last minute floppies directory setup in a convenient place.
- @cp ${.CURDIR}/texts/FLOPPIES.TXT ${RD}/floppies/README.TXT
+.if !defined(NODOC)
+ @cp ${.CURDIR}/doc/${RELNOTES_LANG}/readme/article.txt \
+ ${RD}/floppies/README.TXT
@(cd ${RD}/floppies; md5 README.TXT *.flp > CHECKSUM.MD5)
+.else
+ @(cd ${RD}/floppies; md5 *.flp > CHECKSUM.MD5)
+.endif
touch release.9
#
@@ -707,7 +698,7 @@
-@ln -s . ${FD}/${BUILDNAME}
@cd ${RD} && find floppies -print | cpio -dumpl ${FD}
@cd ${RD}/dists && find . -print | cpio -dumpl ${FD}
-.if !defined(NORELNOTES)
+.if !defined(NODOC)
@for i in ${DIST_DOCS_ARCH_INDEP}; do \
cp ${.CURDIR}/doc/${RELNOTES_LANG}/$$i/article.txt ${FD}/`echo $${i} | tr
'a-z' 'A-Z'`.TXT; \
cp ${.CURDIR}/doc/${RELNOTES_LANG}/$$i/article.html ${FD}/`echo $${i} | tr
'a-z' 'A-Z'`.HTM; \
@@ -746,7 +737,7 @@
@cp ${.CURDIR}/fixit.profile ${CD_DISC2}/.profile
@echo "CD_VERSION = ${BUILDNAME}" > ${CD_DISC1}/cdrom.inf
@echo "CD_VERSION = ${BUILDNAME}" > ${CD_DISC2}/cdrom.inf
-.if !defined(NORELNOTES)
+.if !defined(NODOC)
@for i in ${DIST_DOCS_ARCH_INDEP}; do \
cp ${.CURDIR}/doc/${RELNOTES_LANG}/$$i/article.txt ${CD_DISC1}/`echo $${i} |
tr 'a-z' 'A-Z'`.TXT; \
cp ${.CURDIR}/doc/${RELNOTES_LANG}/$$i/article.html ${CD_DISC1}/`echo $${i}
| tr 'a-z' 'A-Z'`.HTM; \
PGP signature
Re: -current broken ?
Poul-Henning Kamp <[EMAIL PROTECTED]> wrote: > > ===> usr.bin/fetch > /flat/src/usr.bin/fetch/fetch.c: In function `main': > /flat/src/usr.bin/fetch/fetch.c:757: `vtty' undeclared (first use in this function) Noticed this in my `make release' attempt yesterday, too. -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -current broken ?
On Mon, 28 May 2001 21:45:02 +0200, Joerg Wunsch wrote: > > ===> usr.bin/fetch > > > /flat/src/usr.bin/fetch/fetch.c: In function `main': > > /flat/src/usr.bin/fetch/fetch.c:757: `vtty' undeclared (first use in this function) > > Noticed this in my `make release' attempt yesterday, too. Fixed in rev 1.30 of fetch.c. Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 'make includes' ownership patch
On Mon, May 28, 2001 at 10:31:58AM -0700, Rodney W. Grimes wrote:
> > On Mon, May 28, 2001 at 10:22:33AM -0700, Rodney W. Grimes wrote:
> > > > This was on my TODO. The only problem with INCOWN/INCGRP not being
> > > > used here is that they were introduced long after include/Makefile.
> > >
> > > And perhaps one should go read the commit message that introduced them...
> > > it was an experiment, a sample test designed to only be used in -current
> > > /usr/src/lib, that BDE, Sheldon and myself had long followon conversations
> > > about, and got dropped into the cracks.
> >
> > What was the reasoning for a serperate owner specification from BIN*?
>
> Simple orthagonality. Ie, each bsd.*.mk file typically has a seperate
> set of *{DIR/OWN/GRP/MODE} specs. bsd.inc.mk was cloned from another
> bsd.*.mk file.
Well, I don't mind how it gets fixed, but it's very unorthogonal at
the moment having to set two sets of OWN/GRP variables in order to
make includes as non-root.
Someone tell me what they should be using and I'll fix it.
Kris
PGP signature
A diverse Marketplace for a diverse Market
Hi, I am writing to introduce ePushcart.Net Our prices on name brand, guaranteed merchandise consistantly BEAT those on auction sites & at Discount retail stores! Please check us out the next time you shop: http://www.ePushcart.Net Thanks for considering ePushcart.Net- "A Diverse Marketplace for the Diverse market" -ePushcart To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: wierdness with mountd
In message <[EMAIL PROTECTED]>, John Polstra writes: >In article <[EMAIL PROTECTED]>, >Matthew Jacob <[EMAIL PROTECTED]> wrote: >> May 28 10:21:43 farrago mountd[217]: can't delete exports for /tmp >> May 28 10:21:43 farrago mountd[217]: can't delete exports for /usr/obj > >I've been seeing this too, on a -current system from around May 5. This sounds like there are stale entries in /var/db/mountdtab, but I'm not familiour enough with the purpose of mountdtab to know why this is happening. I'll look into this further over the next few days; for now maybe try cleaning out mountdtab manually? Ian To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 'make includes' ownership patch
> On Mon, May 28, 2001 at 10:31:58AM -0700, Rodney W. Grimes wrote:
> > > On Mon, May 28, 2001 at 10:22:33AM -0700, Rodney W. Grimes wrote:
> > > > > This was on my TODO. The only problem with INCOWN/INCGRP not being
> > > > > used here is that they were introduced long after include/Makefile.
> > > >
> > > > And perhaps one should go read the commit message that introduced them...
> > > > it was an experiment, a sample test designed to only be used in -current
> > > > /usr/src/lib, that BDE, Sheldon and myself had long followon conversations
> > > > about, and got dropped into the cracks.
> > >
> > > What was the reasoning for a serperate owner specification from BIN*?
> >
> > Simple orthagonality. Ie, each bsd.*.mk file typically has a seperate
> > set of *{DIR/OWN/GRP/MODE} specs. bsd.inc.mk was cloned from another
> > bsd.*.mk file.
>
> Well, I don't mind how it gets fixed, but it's very unorthogonal at
> the moment having to set two sets of OWN/GRP variables in order to
> make includes as non-root.
>
> Someone tell me what they should be using and I'll fix it.
Change bsd.own.mk to:
INCOWN?=${BINOWN}
INCGRP?=${BINGRP}
INCMODE?= ${NOBINMODE}
as a temporary hack until INC* and bsd.inc.mk is completed/gutted/replaced/
whatever.
--
Rod Grimes - KD7CAX @ CN85sl - (RWG25) [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Panic during -CURRENT buildworld
>Date: Mon, 28 May 2001 10:46:53 -0700 (PDT) >From: David Wolfskill <[EMAIL PROTECTED]> >This is on a system (my laptop): >FreeBSD localhost 5.0-CURRENT FreeBSD 5.0-CURRENT #13: Sun May 27 23:44:24 PDT 2001 > [EMAIL PROTECTED]:/common/C/obj/usr/src/sys/LAPTOP_30W i386 Mon May 28 >07:27:59 PDT 2001 >Recent CVSup activity: >CVSup begin from cvsup14.freebsd.org at Sat May 26 03:47:01 PDT 2001 >CVSup ended from cvsup14.freebsd.org at Sat May 26 03:52:48 PDT 2001 >CVSup begin from cvsup14.freebsd.org at Sun May 27 03:47:01 PDT 2001 >CVSup ended from cvsup14.freebsd.org at Sun May 27 03:53:36 PDT 2001 >CVSup begin from cvsup14.freebsd.org at Mon May 28 03:47:00 PDT 2001 >CVSup ended from cvsup14.freebsd.org at Mon May 28 03:53:51 PDT 2001 >I had tried the buildworld within X (as had been my normal practice until >the recent difficulties with swap and/or VM), and the system re-booted >itself. Got the well-discussed symptom of an active file system failing >fsck's check of primary vs. first alternate superblock, and after fsck >got finished with the file system, soft updates got turned off, so I turned >soft updates back on again. > I was able to do the buildworld (& friends) by booting a saved kernel from 16 May into single-user mode, so I'm now running: FreeBSD dhcp-133.catwhisker.org 5.0-CURRENT FreeBSD 5.0-CURRENT #14: Mon May 28 09:56:14 PDT 2001 root@:/common/C/obj/usr/src/sys/LAPTOP_30W i386 And while running that kernel (no further CVSups; no further source tree mods), I was able to do a "make buildworld" while running X. Seems like an improvement to me, david -- David H. Wolfskill [EMAIL PROTECTED] As a computing professional, I believe it would be unethical for me to advise, recommend, or support the use (save possibly for personal amusement) of any product that is or depends on any Microsoft product. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvs commit: src UPDATING
Warner Losh wrote: > > imp 2001/05/28 21:26:44 PDT > > Modified files: > .UPDATING > Log: > Looks like -current is safe again, and has been since Friday. -current is NOT safe, by any stretch of the imagination. Kris K. and I have both posted numerous messages to -current about the problems we're having let me know if you need copies. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvs commit: src UPDATING
In message <[EMAIL PROTECTED]> Doug Barton writes: : Warner Losh wrote: : > : > imp 2001/05/28 21:26:44 PDT : > : > Modified files: : > .UPDATING : > Log: : > Looks like -current is safe again, and has been since Friday. : : -current is NOT safe, by any stretch of the imagination. Kris K. and I : have both posted numerous messages to -current about the problems we're : having let me know if you need copies. I'm not having problems :-). However, I see that around May 25 or 26 the freelist messages started... Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvs commit: src UPDATING
On Mon, May 28, 2001 at 10:16:46PM -0700, Doug Barton wrote: > > .UPDATING > > Log: > > Looks like -current is safe again, and has been since Friday. Alpha is in evern worse shape than x86. The statement that -current is safe is 110% wrong. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Unrecognised CBCP packet [strange problems with ppp(8)]
Hi, I'm having strange problems with one of local dial-up providers: without any visible reasons from time to time I can't establish PPP connection during 20-30 minutes. Shortly after going into `Network' mode ppp(8) complains about `Unrecognised CBCP packet' and drops down line. Restarting ppp/machine/modem etc. doesn't help and provider's technical people have no idea what could be wrong. Attached please find piece of log, please let me know if any additional information would be necessary. -Maxim Phase: bundle: Authenticate Phase: deflink: his = PAP, mine = none Phase: Pap Output: sobomax1 Ppp ON vega> Phase: Pap Input: SUCCESS () Phase: deflink: lcp -> open Phase: bundle: Network PPp ON vega> Warning: Unrecognised CBCP packet (code 5, length 4) PPp ON vega> Phase: deflink: open -> lcp Phase: bundle: Terminate ppp ON vega> Phase: deflink: Carrier lost Phase: deflink: Disconnected! Phase: deflink: lcp -> logout Phase: deflink: Disconnected! Phase: deflink: logout -> hangup Phase: deflink: Connect time: 32 secs: 248 octets in, 235 octets out To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make release failure
Yes, this patch fix it for me. I had to convert the spaces back to tabs
though. :-)
John
--
John Hay -- [EMAIL PROTECTED]
> If memory serves me right, Dima Dorfman wrote:
> > John Hay <[EMAIL PROTECTED]> writes:
>
> > > > > *** Filesystem is 1440 K, 66 left
> > > > > *** 4000 bytes/inode, 116 left
> > > > > cp: /usr/src/release/texts/FLOPPIES.TXT: No such file or directory
> > > >
> > > > What revision of src/release/Makefile do you have? You want 1.618.
> > >
> > > beast# fgrep '$FreeBSD' /usr/src/release/Makefile
> > > # $FreeBSD: src/release/Makefile,v 1.618 2001/05/25 18:01:31 bmah Exp $
> > > beast# fgrep 'texts/FLOPPIES.TXT' /usr/src/release/Makefile
> > > @cp ${.CURDIR}/texts/FLOPPIES.TXT ${RD}/floppies/README.TXT
>
> Mea culpa. Mea maxima culpa. :-(
>
> > Could you please try the attached, untested patch? I don't know
> > enough about the release build process to know if it should work, but
> > I guess it's worth a shot. Bruce Mah (cc'd) should know whether it's
> > the Right(tm) fix.
>
> Just got back from a road trip...my brain is a little fried now.
>
> dd is going in the right direction, but the Makefile needs to consider
> if NORELNOTES is defined or not. I recommend something like the
> patch appended below...also untested...I'll test this tomorrow
> when I am more awake, and maybe by then I will have figured out why
> this slipped through my testing.
>
> Sorry folks...
>
> Bruce.
>
> Index: Makefile
> ===
> RCS file: /home/ncvs/src/release/Makefile,v
> retrieving revision 1.618
> diff -u -r1.618 Makefile
> --- Makefile2001/05/25 18:01:31 1.618
> +++ Makefile2001/05/28 06:29:31
> @@ -694,8 +694,13 @@
> @sh -e ${.CURDIR}/scripts/doFS.sh ${RD}/floppies/fixit.flp ${RD} \
> ${MNT} ${FIXITSIZE} ${RD}/fixitfd ${FIXITINODE} ${FIXITLABEL}
> # Do our last minute floppies directory setup in a convenient place.
> - @cp ${.CURDIR}/texts/FLOPPIES.TXT ${RD}/floppies/README.TXT
> +.if !defined(NORELNOTES)
> + @cp ${.CURDIR}/doc/${RELNOTES_LANG}/readme/article.txt \
> + ${RD}/floppies/README.TXT
> @(cd ${RD}/floppies; md5 README.TXT *.flp > CHECKSUM.MD5)
> +.else
> + @(cd ${RD}/floppies; md5 *.flp > CHECKSUM.MD5)
> +.endif
> touch release.9
>
> #
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: cvs commit: src UPDATING
On Mon, 28 May 2001, Warner Losh wrote: ... > : -current is NOT safe, by any stretch of the imagination. Kris K. and I > : have both posted numerous messages to -current about the problems we're > : having let me know if you need copies. > > I'm not having problems :-). However, I see that around May 25 or 26 > the freelist messages started... Have you tried to start aviplay ( coming from ports/graphics/avifile ) or using whine? Bye! Michael Reifenberger ^.*Plaut.*$, IT, R/3 Basis, GPS To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Unrecognised CBCP packet [strange problems with ppp(8)]
On Mon, 28 May 2001, Maxim Sobolev wrote: :Hi, : :I'm having strange problems with one of local dial-up providers: without :any visible reasons from time to time I can't establish PPP connection :during 20-30 minutes. Shortly after going into `Network' mode ppp(8) :complains about `Unrecognised CBCP packet' and drops down line. :Restarting ppp/machine/modem etc. doesn't help and provider's technical :people have no idea what could be wrong. Attached please find piece of :log, please let me know if any additional information would be necessary. : I've seen this too. Not very often, not repeatably. I don't think I ever had a problem reconnecting, though. I'm pretty sure I saw this as long ago as 1999, as well. I no longer have a dialup, so I'm kind of fuzzy on details. -- [EMAIL PROTECTED] Bipedalism is only a fad. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
