Re: HEADS UP: -CURRENT Feature Slush is OVER
On Sun, 17 Mar 2002, David O'Brien wrote: On Sat, Mar 16, 2002 at 02:08:51PM -0800, Terry Lambert wrote: I hate this whole direction. I think it's an incredibly bad idea that we are not going to be able to reproduce what went onto any given CDROM in ten years. The source will be on the CDROM. Nor is there any major importance to DP1. Are you also upset that you cannot reproduce the July 17th, 1998 -CURRENT snapshot CD from WC? If a tag was laid down can't it be retrieved indefinitely? A non-branching tag? What am I missing? Annelise -- Annelise Anderson Author of: FreeBSD: An Open-Source Operating System for Your PC Available from: BSDmall.com and amazon.com Book Website:http://www.bittreepress.com/FreeBSD/introbook/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: CVSup/buildworld failure
-current with sources as of 1 a.m. PST 1/16/01 built okay for me, and runs fine. Annelise On Tue, 16 Jan 2001, Nate Dannenberg wrote: Tuesday, 16 Jan. 2001, about 7am or so, received the following error message(s) from buildworld, after performing a CVSup sometime during the previous day (mid-day or so), while tracking FreeBSD 5.0-CURRENT (output slightly reformatted to correct lines where just one or two characters wouldn't fit on a previous line): - Text Import Begin - === sys/boot/i386/btx === sys/boot/i386/btx/btx (cd /usr/src/sys/boot/i386/btx/btx; m4 btx.s) | as --defsym BTX_FLAGS=0x0 -o btx.o m4: not found ld -N -e start -Ttext 0x9000 -o btx.out btx.o /usr/obj/usr/src/i386/usr/libexec/elf/ld: warning: cannot find entry symbol start; defaulting to 9000 objcopy -S -O binary btx.out btx === sys/boot/i386/btx/btxldr (cd /usr/src/sys/boot/i386/btx/btxldr; m4 -DLOADER_ADDRESS=0x20 btxldr.s ) | as -o btxldr.o m4: not found ld -N -e start -Ttext 0x20 -o btxldr.out btxldr.o /usr/obj/usr/src/i386/usr/libexec/elf/ld: warning: cannot find entry symbol start; defaulting to 0020 objcopy -S -O binary btxldr.out btxldr === sys/boot/i386/btx/lib as -elf -o btxcsu.o /usr/src/sys/boot/i386/btx/lib/btxcsu.s as -elf -o btxsys.o /usr/src/sys/boot/i386/btx/lib/btxsys.s as -elf -o btxv86.o /usr/src/sys/boot/i386/btx/lib/btxv86.s ld -elf -i -o crt0.o btxcsu.o btxsys.o btxv86.o === sys/boot/i386/boot2 as --defsym FLAGS=0x80 /usr/src/sys/boot/i386/boot2/boot1.s -o boot1.o ld -nostdlib -static -N -e start -Ttext 0x7c00 -o boot1.out boot1.o objcopy -S -O binary boot1.out boot1 dd if=/dev/zero of=boot2.ldr bs=512 count=1 2/dev/null cc -elf -I/usr/src/sys/boot/i386/boot2/../btx/lib -I. -Os -fno-builtin -fforce-addr -fdata-sections -malign-f nctions=0 -malign-jumps=0 -malign-loops=0 -mrtd -mpreferred-stack-boundary=2 -Wall -Waggregate-return -Wbad-f nction-cast -Wcast-align -Wmissing-declarations -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wshado -Wstrict-prototypes -Wwrite-strings -mpreferred-stack-boundary=2 -I/usr/obj/usr/src/i386/usr/include -c /usr src/sys/boot/i386/boot2/boot2.c as --defsym SIOPRT=0x3f8 --defsym SIOFMT=0x3 --defsym SIOSPD=9600 /usr/src/sys/boot/i386/boot2/sio.s -o sioo ld -nostdlib -static -N -Ttext 0x1000 -o boot2.out /usr/obj/usr/src/sys/boot/i386/boot2/../btx/lib/crt0.o boot.o sio.o objcopy -S -O binary boot2.out boot2.bin btxld -v -E 0x1000 -f bin -b /usr/obj/usr/src/sys/boot/i386/boot2/../btx/btx/btx -l boot2.ldr -o boot2.ld -P 1 boot2.bin btxld: /usr/obj/usr/src/sys/boot/i386/boot2/../btx/btx/btx: Not a BTX kernel *** Error code 1 Stop in /usr/src/sys/boot/i386/boot2. *** Error code 1 - Text Import End - Error Codes continued for a few more directory levels before they stopped. I have not been able to buildworld for the last week or so, each time receiving a different kind of error message (and each time after CVSup'ing the latest source). To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: calcru() warnings...
On Wed, 24 Nov 1999, Poul-Henning Kamp wrote: I still hear reports of sporadic calcru() warnings. If any of you see these, could you try to see if they correlate to the uptime of the machine in question ? Since I replaced a September 15 -current with October 14 -current, I get lots of these within 24 or 48 hours of booting. Setting kern.timecounter.method to 1 does stop them. SMP, two PII-400's. Annelise To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
perl error in make world
I'm getting the following error with today's -current sources; this particular system has a rather strange history, so it may not be the sources, but something else. I have tried -DNOCRYPT, which doesn't help. And I've searched the archives without finding anything directly applicable, so suggestions would be appreciated. chmod 755 /usr/obj/usr/src/gnu/usr.bin/perl/perl/lib/auto/DynaLoader/DynaLoader.a cc -nostdinc -O -pipe -I/usr/src/gnu/usr.bin/perl/perl/../../../../contrib/perl5 -I/usr/obj/usr/src/gnu/usr.bin/perl/perl -I/usr/obj/usr/src/tmp/usr/include -o perl perlmain.o lib/auto/DynaLoader/DynaLoader.a -lperl -lm -lcrypt /usr/obj/usr/src/tmp/usr/lib/libcrypt.so: undefined reference to `SHA_Final' /usr/obj/usr/src/tmp/usr/lib/libcrypt.so: undefined reference to `SHA_Init' /usr/obj/usr/src/tmp/usr/lib/libcrypt.so: undefined reference to `SHA_Update' *** Error code 1 Stop in /usr/src/gnu/usr.bin/perl/perl. *** Error code 1 Annelise To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Make release troubles
There are a couple of things you can do if your make release
fails while trying to make the docs.
You could use "on demand" dialing for ppp so that it connects only
when it needs to (and hangs up after some period of inactivity) so
you're not connected for so long. Making these ports is the only
part of a make release that requires fetching files.
You could also have the make release continue more or less where it
left off. You do *not* want to start it over by typing "make release"
in /usr/src/release, as this will delete what's already been done.
But you can chroot to the directory where the release is being built
and run the file "mk" in that directory. This is a shell script
that is created when you run "make release" in /usr/src/release, and
once the chroot directive is reached in the Makefile in /usr/src/release,
only what's in the chroot directory structure is relevant. Running
"mk" from this directory should allow things to continue where they
left off, because this script incorporates the variables you decided
upon when you edited the Makefile in /usr/src/release and runs
the :doRELEASE target in Makefile in $CHROOTDIR/usr/src/release,
which records ("touch release.1", for example) what's been done.
An alternative is to define a target in /usr/src/release/Makefile
called (e.g.) release.0, and have it simply chroot to the directory
where you're building the release and run mk there. You can then
define in mk any target you want to build in the Makefile in
$CHROOTDIR/usr/src/release, and then put this target in the
Makefile. This means you can continue where you left off by
typing "make release.0" in /usr/src/release.
By this time the ports distfiles will already have been copied to
$CHROOTDIR/usr/ports/distfiles, and anything in the /usr/ports/distfiles
directory or wherever you tell it to get the distfiles (/usr/ports/
distfiles.release in your case) will not be found. If you need to
add a distfile, you need to put it in $CHROOTDIR/usr/ports/distfiles.
A possible strategy before beginning the make release is to move the
existing /usr/ports/distfiles to a hold location, do "make install"
in /usr/ports/textproc/docproj, and hope that you in this way get all
the distfiles you need for the release. You might have to deinstall
first so that it does go through the whole build process and gets all
the dependencies. If you do this, you want to make sure your version
of the ports tree in /usr/ports is the same as the version you want
to build in "make release." I personally think these little ports
like tidy are troublesome because the version numbers change so often;
so probably the best approach is to have an open connection during
the build of doc.1 so it can get anything you haven't yet gotten.
Annelise
On Sun, 7 Nov 1999, Marc Schneiders wrote:
I have studied the Makefile.
I have searched the archives of the lists.
I have put the files necessary for the ports build for docproj during
the make in a separate directory (/usr/ports/distfiles.release),
with no extra files there.
I have set this in the Makefile. Nevertheless this is what happened:
touch release.2
Making docs...
=== Extracting for docproj-1.1
[...]
[...]
[...]
=== Registering installation for sgmlformat-1.7
=== Returning to build of docproj-1.1
=== docproj-1.1 depends on executable: sgmlnorm - found
=== docproj-1.1 depends on executable: jade - found
=== docproj-1.1 depends on executable: tidy - not found
===Verifying install for tidy in /usr/ports/www/tidy
=== Extracting for tidy-0.9.99.1
Checksum OK for tidy27sep99.tgz.
Here it just stopped (and had been waiting for 9 hours...). No error
message, nothing. Machine was responding OK. No kernel messages, no
messages. Nothing peculiar in top etc. So I tried something weird (in
my eyes anyway) and kill -HUPped the PID. It continued. Great, well
for a moment.
=== Patching for tidy-0.9.99.1
=== Applying FreeBSD patches for tidy-0.9.99.1
=== Configuring for tidy-0.9.99.1
=== Building for tidy-0.9.99.1
cc -O -pipe -D__USE_MISC -c attrs.c
cc -O -pipe -D__USE_MISC -c istack.c
cc -O -pipe -D__USE_MISC -c parser.c
cc -O -pipe -D__USE_MISC -c tags.c
cc -O -pipe -D__USE_MISC -c entities.c
cc -O -pipe -D__USE_MISC -c lexer.c
cc -O -pipe -D__USE_MISC -c pprint.c
cc -O -pipe -D__USE_MISC -c clean.c
cc -O -pipe -D__USE_MISC -c localize.c
cc -O -pipe -D__USE_MISC -c config.c
cc -O -pipe -D__USE_MISC -c tidy.c
cc -O -pipe -D__USE_MISC -o tidy attrs.o istack.o
parser.otags.o entities.o lexer.o pprint.o
clean.o localize.o config.o tidy.o -lc
=== Installing for tidy-0.9.99.1
install -c -s -o root -g wheel -m 555
/usr/ports/www/tidy/work/tidy27sep99/tidy /usr/local/bin/tidy
=== Installing documentation for tidy-0.9.99.1
=== Generating temporary packing list
=== Registering installation for tidy-0.9.99.1
===
aic driver (thanks!) and cdrom
Thanks very much for this driver, Luoqi. I am using it in a -current built from October 14 sources, with a new kernel of course. The cdrom produces the following, though: Oct 22 14:14:35 two /kernel: Waiting 15 seconds for SCSI devices to settle Oct 22 14:14:35 two /kernel: (probe2:aic0:0:2:2): ccb 0xc0c90c00 - timed out Oct 22 14:14:35 two /kernel: (probe2:aic0:0:2:2): ccb 0xc0c90c00 - timed out Oct 22 14:14:35 two /kernel: (probe2:aic0:0:2:3): ccb 0xc0c90c00 - timed out Oct 22 14:14:35 two /kernel: (probe2:aic0:0:2:3): ccb 0xc0c90c00 - timed out Oct 22 14:14:35 two /kernel: (probe2:aic0:0:2:4): ccb 0xc0c90c00 - timed out Oct 22 14:14:35 two /kernel: (probe2:aic0:0:2:4): ccb 0xc0c90c00 - timed out Oct 22 14:14:35 two /kernel: (probe2:aic0:0:2:5): ccb 0xc0c90c00 - timed out Oct 22 14:14:35 two /kernel: (probe2:aic0:0:2:5): ccb 0xc0c90c00 - timed out Oct 22 14:14:35 two /kernel: Creating DISK da0 Oct 22 14:14:35 two /kernel: Creating DISK da1 Oct 22 14:14:35 two /kernel: Creating DISK cd0 Oct 22 14:14:35 two /kernel: changing root device to da1s2a Oct 22 14:14:35 two /kernel: da0 at aic0 bus 0 target 0 lun 0 Oct 22 14:14:35 two /kernel: da0: QUANTUM VIKING 4.5 NSE 880R Fixed Direct Access SCSI-2 device Oct 22 14:14:35 two /kernel: da0: 5.000MB/s transfers (5.000MHz, offset 8) Oct 22 14:14:35 two /kernel: da0: 4345MB (8899737 512 byte sectors: 64H 32S/T 4345C) Oct 22 14:14:35 two /kernel: da1 at aic0 bus 0 target 1 lun 0 Oct 22 14:14:35 two /kernel: da1: Quantum VP32170 89TC Fixed Direct Access SCSI-2 device Oct 22 14:14:35 two /kernel: da1: 5.000MB/s transfers (5.000MHz, offset 8) Oct 22 14:14:35 two /kernel: da1: 2069MB (4238640 512 byte sectors: 64H 32S/T 2069C) Oct 22 14:14:35 two /kernel: (cd0:aic0:0:2:0): got CAM status 0x20c Oct 22 14:14:35 two /kernel: (cd0:aic0:0:2:0): fatal error, failed to attach to device Oct 22 14:14:35 two /kernel: (cd0:aic0:0:2:0): lost device Oct 22 14:14:35 two /kernel: (cd0:aic0:0:2:0): removing device entry Annelise To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
pccard status?
I installed the April 13 -current snap on my laptop, but I can't build a kernel that will run pccards. pcic fails to allocate an IRQ, and the kernel module pcic won't load. I thought April 13 would avoid the newbus problems, but apparently there were problems back then too. A kernel build with -current sources from March 14 or so works, but has other problems (can't run top, ps, w). I tried using /usr/src/sys/pccard from March 14, but this makes no difference. Is there anything I might try to fix this, other than installing an earlier version? Annelise To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
login
When I log in to my -current machine (April 13 sources) it takes a minute or two after the password is entered before the shell prompt comes up: FreeBSD/i386 (andrsn7.stanford.edu) (ttyp0) login: xanne Password: []--cursor just stays here for a while This is on a LAN; it works fine at the console (and it worked when it was 3.1). I can certainly live with this but it puzzles me. Would anyone know why this might be happening? Annelise To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: login
On Sat, 17 Apr 1999, Soren Schmidt wrote: It seems Annelise Anderson wrote: When I log in to my -current machine (April 13 sources) it takes a minute or two after the password is entered before the shell prompt comes up: FreeBSD/i386 (andrsn7.stanford.edu) (ttyp0) login: xanne Password: []--cursor just stays here for a while This is on a LAN; it works fine at the console (and it worked when it was 3.1). I can certainly live with this but it puzzles me. Would anyone know why this might be happening? Sounds like a DNS timeout or something like that... -Søren I think it was, thanks. I changed the order of the nameservers in resolv.conf and it no longer happens. :) Annelise To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Build Errors in -current
With sources as of about 10 p.m. PST, I got an error in /usr/src/usr.bin/netstat/mbuf.c:71, which was easy to fix. But I still got an error much later with texinfo, so apparently this is only partly fixed. Annelise To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: how to update the system from the master machine
On Mon, 18 Jan 1999, Chan Yiu Wah wrote: Hello, I have two system. One is P233 (master) and the other is a dual P90. How can I update the dual P90 system from the P233 (master) system. Is there anyone can share your experience with me. Thanks. clarence I have used dump and restore to clone a running system, but you want to be careful about what you don't want to be identical on the two systems, or, in my case, the two drives. I use rsync to keep it up to date, so the second disk is a backup for the first. This can be used from one host to another. Again, you might not want everything the same. But rsync is quite fast since it only transfers differences. Annelise To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
