Re: updating with cvsup, buildworld, etc.
On Mon, 28 May 2001, Matt Bedynek wrote: > I run 8 freebsd boxes and I'm thinking of syncing the src's on one > and mount via NFS to share that to the others. I would like to hear > what others here have done to simlify a task such as this. Actually, if you were planning on using NFS for such a task, you could have the NFS server build the world and then have all of the NFS clients simply install it. That would be even more efficient than having the different boxes build their worlds individually. The above assuming that the boxes share a compatible architecture, of course. -- Roderick 'GoG' van Domburg - ICQ UIN 7798700 GamePoint - The Dutch On-Line Gaming Company To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
compile error
I just cvsup'ed the lastest sources for stable and get the following tring to make buildworld. r/include -c /usr/src/usr.sbin/config/mkheaders.c cc -O -pipe -I. -I/usr/src/usr.sbin/config -Wall -Wunused -Wmissing-prototypes -Wredundant-decls -I/usr/obj/usr/src/i386/usr/include -c /usr/src/usr.sbin/config/mkoptions.c cc -O -pipe -I. -I/usr/src/usr.sbin/config -Wall -Wunused -Wmissing-prototypes -Wredundant-decls -I/usr/obj/usr/src/i386/usr/include -static -o config config.o main.o lang.o mkioconf.o mkmakefile.o mkheaders.o mkoptions.o -ll sh /usr/src/tools/install.sh -c -s -o root -g wheel -m 555 config /usr/obj/usr/src/i386/usr/sbin cd /usr/src/gnu/usr.bin/gperf; make obj; make depend; make all; make install /usr/obj/usr/src/i386/usr/src/gnu/usr.bin/gperf created for /usr/src/gnu/usr.bin/gperf ===> doc /usr/obj/usr/src/i386/usr/src/gnu/usr.bin/gperf/doc created for /usr/src/gnu/usr.bin/gperf/doc make: don't know how to make bool-array.cc. Stop *** Error code 2 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. -- Matt Bedynek [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: 3ware & mysql, again
Mike Smith writes: > > > > I recall something about this on another FreeBSD list a week or so ago. > > Supposedly there is a firmware update available that fixes this problem. > > It's not clear whether Raymond is talking about the same symptoms or not > (as he doesn't clarify this). It's not certain that 3ware have actually > fixed the problem yet; last I heard they were still working on it. Hum. Ok. The actual error messages (from dmesg and /var/log/messages) were of the form "twe0: command failed - device failure". At this point it was impossible to do *anything* to the filesystem(s) on the disks connected to the 3ware controller. (I have seen something similar a good few years back, with a particular Seagate SCSI disk model. Not that this is relevant, though.) I've looked at 3Ware's web site, and they claim that the new firmware (version 6.6) fixes certain problems with RAID 5 configurations. My configuration is RAID 0, so it is entirely possible that the new firmware will have no effect for me. Version 6.6 supposedly requires an updated driver - is the driver in -stable so updated? If so, I'll go ahead and backup my data and upgrade the firmware. //Raymond. -- Raymond Wiker [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Packages link on releng4.freebsd.org and stable.freebsd.org
Hi! I'm trying to install FreeBSD 4.3-20010527-STABLE, but it looks like the package-link points to: packages -> ../../../packages-4-release which doesn't exist :( I've searched around the ftp-site, and wondered if packages should point to: ../../../ports/i386/packages-4.3-release instead? The point is I can't seem to install FreeBSD. Any ideas anyone? -- Phuc To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: 3ware & mysql, again
> Mike Smith writes: > > > > > > I recall something about this on another FreeBSD list a week or so ago. > > > Supposedly there is a firmware update available that fixes this problem. > > > > It's not clear whether Raymond is talking about the same symptoms or not > > (as he doesn't clarify this). It's not certain that 3ware have actually > > fixed the problem yet; last I heard they were still working on it. > > Hum. Ok. The actual error messages (from dmesg and > /var/log/messages) were of the form > "twe0: command failed - device failure". At this point it was > impossible to do *anything* to the filesystem(s) on the disks > connected to the 3ware controller. This is a totally different and unrelated failure. It's not clear what is going wrong here though; I'll have to ask 3ware what this suggests. > I've looked at 3Ware's web site, and they claim that the new > firmware (version 6.6) fixes certain problems with RAID 5 > configurations. My configuration is RAID 0, so it is entirely possible > that the new firmware will have no effect for me. The RAID 5 issue is not related to this (and does not affect FreeBSD). > Version 6.6 supposedly requires an updated driver - is the > driver in -stable so updated? If so, I'll go ahead and backup my data > and upgrade the firmware. No driver changes are required. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: 3ware & mysql, again
Mike Smith writes: > >Hum. Ok. The actual error messages (from dmesg and > > /var/log/messages) were of the form "twe0: command failed - > > device failure". At this point it was impossible to do *anything* > > to the filesystem(s) on the disks connected to the 3ware > > controller. > > This is a totally different and unrelated failure. It's not clear > what is going wrong here though; I'll have to ask 3ware what this > suggests. OK. As I said in my first message, I was running -stable as of Feb. 26th. The March thread on -stable indicated that there were recent fixes for race conditions; I'm going to just watch this machine for a while to see if it works better. Thanks for your help. //Raymond. -- Raymond Wiker [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
help
help To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: 3ware & mysql, again
Does the raid management daemon show anything odd about the raid0 stripe prior to it locking up ? ---Mike At 12:36 PM 5/28/2001 +0200, Raymond Wiker wrote: >Mike Smith writes: > > >Hum. Ok. The actual error messages (from dmesg and > > > /var/log/messages) were of the form "twe0: command failed - > > > device failure". At this point it was impossible to do *anything* > > > to the filesystem(s) on the disks connected to the 3ware > > > controller. > > > > This is a totally different and unrelated failure. It's not clear > > what is going wrong here though; I'll have to ask 3ware what this > > suggests. > > OK. As I said in my first message, I was running -stable as of >Feb. 26th. The March thread on -stable indicated that there were >recent fixes for race conditions; I'm going to just watch this machine >for a while to see if it works better. Mike Tancsa, tel +1 519 651 3400 Network Administration, [EMAIL PROTECTED] Sentex Communications www.sentex.net Cambridge, Ontario Canada www.sentex.net/mike To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: 3ware & mysql, again
Mike Tancsa writes: > > Does the raid management daemon show anything odd about the raid0 stripe > prior to it locking up ? I didn't check this - sorry. I'll make sure that 3dmd is running the next time this happens... //Raymond. -- Raymond Wiker [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
hangs with sysctl -a
Has anybody tried 'sysctl -a ' on a recent -STABLE? My i386 machine hangs reproducibly. Built sometime after src/sys/kern/subr_disk.c rev 1.20.2.2, which could possibly be the culprit. OK, I haven't provided sufficient information nor have I attempted to narrow down the problem, but could anybody just let me know if it works on your machine or not? It's easy to test, ..well if you don't mind hanging it. Thanks. -- Shuhei To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
re: hangs with sysctl -a
I'm seeing this too. CVSUP from kernel yesterday May 27, 2001. -Hoang Shuhei writes: Has anybody tried 'sysctl -a ' on a recent -STABLE? My i386 machine hangs reproducibly. Built sometime after src/sys/kern/subr_disk.c rev 1.20.2.2, which could possibly be the culprit. OK, I haven't provided sufficient information nor have I attempted to narrow down the problem, but could anybody just let me know if it works on your machine or not? It's easy to test, ..well if you don't mind hanging it. Thanks. -- Shuhei To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: hangs with sysctl -a
On Mon, 28 May 2001, AMAKAWA Shuhei wrote: >Has anybody tried 'sysctl -a ' on a recent -STABLE? >My i386 machine hangs reproducibly. >Built sometime after src/sys/kern/subr_disk.c rev 1.20.2.2, >which could possibly be the culprit. Reproduced it here also, it hung right after displaying kern.devstat.version: 4 I couldn't telnet into the box to restart it, I had to hit the reset switch. cvsupped and sources up to date as of: FreeBSD 4.3-STABLE #0: Sun May 27 14:23:06 EDT 2001 == = Bryan D. Liesner LeezSoft Communications, Inc. = = A subsidiary of LeezSoft Inc. = = [EMAIL PROTECTED] Home of the Gipper= == To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: hangs with sysctl -a
>Date: Mon, 28 May 2001 13:52:11 +0100 >From: AMAKAWA Shuhei <[EMAIL PROTECTED]> >Has anybody tried 'sysctl -a ' on a recent -STABLE? I hadn't until your report >My i386 machine hangs reproducibly. >Built sometime after src/sys/kern/subr_disk.c rev 1.20.2.2, >which could possibly be the culprit. >OK, I haven't provided sufficient information nor have I attempted >to narrow down the problem, but could anybody just let me know if it >works on your machine or not? >It's easy to test, ..well if you don't mind hanging it. >Thanks. OK; I tested it, and got the reported hang. I then re-booted & tried again -- this time, outside of the X environment. Big difference I noticed was that the command (the second time around) did output a lot of variables & values; here are the last several reported: kerm.fscale: 2048 kern.devstat.numdevs: 4 kern.devstat.generation: 4 kern.devstat.version: 4 ...and that's where it hung. This is on a -STABLE as of this morning: FreeBSD dhcp-133.catwhisker.org 4.3-STABLE FreeBSD 4.3-STABLE #30: Mon May 28 06:33:53 PDT 2001 [EMAIL PROTECTED]:/common/S2/obj/usr/src/sys/LAPTOP_30W i386 built from sources updated from a local CVS repository that was updated: 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 The machine is my laptop, where I've been tracking -STABLE daily since early March. There's some information about it at http://www.catwhisker.rog/~david/FreeBSd/laptop.html. I have not tried booting in single-user mode to try it yet; I'm willing, if there's reason to believe it might make a difference. I should be able to perform reasonable experiments upon request. Cheers, 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-stable" in the body of the message
RE: stable errors
:: May 28 20:47:48 c353425-a /kernel: psmintr: out of sync :: (0040 != ). :: May 28 20:47:48 c353425-a /kernel: psmintr: out of sync :: (0080 != ). :: :: Did a new kernel after a cvsup today on stable. Oddly enough, I saw this mentioned on /. last month. Hang on... here it is: http://www.slashdot.org/bsd/01/04/22/0056207.shtml -- Juha To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: stable errors
>Date: Tue, 29 May 2001 00:40:21 -0400 >From: Ted Sikora <[EMAIL PROTECTED]> >May 28 20:47:48 c353425-a /kernel: psmintr: out of sync (0040 != ). >May 28 20:47:48 c353425-a /kernel: psmintr: out of sync (0080 != ). >Did a new kernel after a cvsup today on stable. I'm not seeing the symptom. This on a laptop with a touchpad (similar to the Dell Inspiron 5000e): FreeBSD dhcp-133.catwhisker.org 4.3-STABLE FreeBSD 4.3-STABLE #30: Mon May 28 06:33:53 PDT 2001 [EMAIL PROTECTED]:/common/S2/obj/usr/src/sys/LAPTOP_30W i386 Recent CVSup history: 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 In case it's significant, I'm running moused: dhcp-133[3] ps -axwwl|grep moused 0 272 1 0 2 0 892 520 select Ss??0:00.16 moused -3 -p /dev/psm0 -t auto Cheers, 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-stable" in the body of the message
Re: Port update (jakarta-tomcat) problem
> > > See the work around in http://www.freebsd.org/cgi/query-pr.cgi?pr=27495 > > > > I run a local mirror of FreeBSD CVS Repository. > > Now when a client uses my mirror, it obtains > > > > Server warning: Cannot open > > "/usr/local/etc/cvsup/prefixes/FreeBSD.cvs/ports/www/jakarta-tomcat/files,v": > > No such file or directory > > > > How can I resolve this? > > I don't understand why you'd get this on a mirror. Nobody else has > reported it on mirrors of the repository. I recommend that you apply > the work-around described in the PR on your mirror site, and make sure > you run a cvsup update _without_ the "-s" option afterwards. Thanks, that worked. Eugene Grosbein To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
