/usr/local/etc/rc.d/apache.sh question
Hello,
I have some understanding of how the script works, but I'm not sure what
it's asking for.
[09:37][root@interim:/usr/local/etc/rc.d]# ls
apache.sh*
[09:37][root@interim:/usr/local/etc/rc.d]# ./apache.sh start
./apache.sh: Cannot determine the PREFIX
That's what I get. The following will be the contents of apache.sh:
#!/bin/sh
if ! PREFIX=$(expr $0 : \(/.*\)/etc/rc\.d/$(basename $0)\$); then
echo $0: Cannot determine the PREFIX 2
exit 1
fi
case $1 in
start)
[ -x ${PREFIX}/sbin/apachectl ] ${PREFIX}/sbin/apachectl start
/dev/null echo -n ' apache'
;;
stop)
[ -r /var/run/httpd.pid ] ${PREFIX}/sbin/apachectl stop
/dev/null echo -n ' apache'
;;
*)
echo Usage: `basename $0` {start|stop} 2
;;
esac
exit 0
Can someone please help? If I type apachectl as I usually have done in
Linux, it works, but now this is asking me for something. Can someone
please help?
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-stable in the body of the message
Re: /usr/local/etc/rc.d/apache.sh question
On Thu, Dec 27, 2001 at 09:38:40AM -0800, Peter/Los Angeles, CA wrote: Hello, I have some understanding of how the script works, but I'm not sure what it's asking for. [09:37][root@interim:/usr/local/etc/rc.d]# ls apache.sh* [09:37][root@interim:/usr/local/etc/rc.d]# ./apache.sh start ./apache.sh: Cannot determine the PREFIX Looks like you must use full path for this shell-script. Like this: [09:37][root@interim:/usr/local/etc/rc.d]# /usr/local/etc/rc.d/apache.sh start -- Rgdz,/\ Sergey Osokin aka oZZ, \ / ASCII RIBBON CAMPAIGN [EMAIL PROTECTED]X AGAINST HTML MAIL http://freebsd.org.ru/~osa/ / \ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: /usr/local/etc/rc.d/apache.sh question
Peter/Los Angeles, CA([EMAIL PROTECTED])@2001.12.27 09:38:40 +: Hello, I have some understanding of how the script works, but I'm not sure what it's asking for. [09:37][root@interim:/usr/local/etc/rc.d]# ls apache.sh* [09:37][root@interim:/usr/local/etc/rc.d]# ./apache.sh start ./apache.sh: Cannot determine the PREFIX try /usr/local/etc/rc.d/apache.sh start To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: /usr/local/etc/rc.d/apache.sh question
You guys are great. Thanks a lot. I owe you guys my first born. Peter - Original Message - From: H. Wade Minter [EMAIL PROTECTED] To: Peter/Los Angeles, CA [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Thursday, December 27, 2001 9:43 AM Subject: Re: /usr/local/etc/rc.d/apache.sh question On Thu, 27 Dec 2001, Peter/Los Angeles, CA wrote: I have some understanding of how the script works, but I'm not sure what it's asking for. [09:37][root@interim:/usr/local/etc/rc.d]# ls apache.sh* [09:37][root@interim:/usr/local/etc/rc.d]# ./apache.sh start ./apache.sh: Cannot determine the PREFIX That's what I get. The following will be the contents of apache.sh: It determines the PREFIX by the full path you use to call the script. If you run: /usr/local/etc/rc.d/apache.sh start it will work. --Wade To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
apache question part2
Dear People, Thank you for your help with my initial apache question. I don't know if this is a malfunction or what, although it seems to work. I opened up the router, and directed it to my server at home. It's responding so I know the daemon is working. The number of times that I've used apache, I've never seen this as an initial message. Is it possible that it's just the port that had some corrupted initial message? Anyway, I'll try the other pages in that directory. Take a look at what I'm talking about. http://haloflightleader.net Peter To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Where can I get (download) Free BSD 2.2.7 Release ?
On Thu, Dec 27, 2001 at 09:39:39AM +0500, Igor I. Ushatinsky wrote: Hi, Vladimir! I couldn/t find it at ftp://ftp.freebsd.org You may find 2.1.7.1-RELEASE at ftp://ftp4.ru.freebsd.org/pub/FreeBSD/releases/i386/ I have the CD set for 2.1.7 and 2.2.8. If you can't find it elsewhere, I could probably put them up somewhere accessable. -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: 4.5 PRERELEASE - Call for testing
On Wed, Dec 26, 2001 at 09:30:20PM -0800, Philip J. Koenig wrote: On 26 Dec 2001, at 19:56, William Carrel boldly uttered: Using switch settings to obtain this sort of configuration/protection is at best crude. Try dummynet(4) and/or some QoS capable network hardware. The switches and NICs for many years already should have the inherent ability to run locked at 10Mbps. Indeed they push this as a feature. Why should I go spend outrageous sums on overpriced QoS hardware or install an entirely new box for this purpose when the existing switches and NICs should already do what I need? I too support hierarchical bandwidth topologies. Unless you're banging around medical images or such, 10Mbps to the desktop is plenty. Then connect the switches/hubs together at 100Mbps, and use gigabit between any core routers. That way, no one user can saturate a segment. Happier users, happier me. -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: /usr/local/etc/rc.d/apache.sh question
Thanks.
- Original Message -
From: Josh Tolbert [EMAIL PROTECTED]
To: Peter/Los Angeles, CA [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Thursday, December 27, 2001 10:05 AM
Subject: Re: /usr/local/etc/rc.d/apache.sh question
Peter,
Take a look at what the script is doing. It's checking to see if
execution was started with a full path (/usr/local/etc/rc.d/apache.sh)
instead of a relative path (./apache.sh).
When you run apachectl (startssl, I suspect), apachectl asks for
whatever passphrase you used to encrypt the SSL key.
Good luck,
Josh
On Thu, 27 Dec 2001, Peter/Los Angeles, CA wrote:
Hello,
I have some understanding of how the script works, but I'm not sure what
it's asking for.
[09:37][root@interim:/usr/local/etc/rc.d]# ls
apache.sh*
[09:37][root@interim:/usr/local/etc/rc.d]# ./apache.sh start
./apache.sh: Cannot determine the PREFIX
That's what I get. The following will be the contents of apache.sh:
#!/bin/sh
if ! PREFIX=$(expr $0 : \(/.*\)/etc/rc\.d/$(basename $0)\$); then
echo $0: Cannot determine the PREFIX 2
exit 1
fi
case $1 in
start)
[ -x ${PREFIX}/sbin/apachectl ] ${PREFIX}/sbin/apachectl
start
/dev/null echo -n ' apache'
;;
stop)
[ -r /var/run/httpd.pid ] ${PREFIX}/sbin/apachectl stop
/dev/null echo -n ' apache'
;;
*)
echo Usage: `basename $0` {start|stop} 2
;;
esac
exit 0
Can someone please help? If I type apachectl as I usually have done in
Linux, it works, but now this is asking me for something. Can someone
please help?
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-stable in the body of the message
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-stable in the body of the message
RE: apache question part2
turn off Multiviews in /usr/local/etc/apache/httpd.conf ;-) -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Peter/Los Angeles, CA Sent: December 27, 2001 12:53 To: [EMAIL PROTECTED] Subject: apache question part2 Dear People, Thank you for your help with my initial apache question. I don't know if this is a malfunction or what, although it seems to work. I opened up the router, and directed it to my server at home. It's responding so I know the daemon is working. The number of times that I've used apache, I've never seen this as an initial message. Is it possible that it's just the port that had some corrupted initial message? Anyway, I'll try the other pages in that directory. Take a look at what I'm talking about. http://haloflightleader.net Peter To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
RE: apache question part2
sorry, i should have been more specific... there is at least one line (maybe more) in the apache config file that says... Options ... Multiviews remove the multiviews part, leaving the rest, and run apachectl restart -Original Message- From: Mit Rowe [mailto:[EMAIL PROTECTED]] Sent: December 27, 2001 13:26 To: Peter/Los Angeles, CA; [EMAIL PROTECTED] Subject: RE: apache question part2 turn off Multiviews in /usr/local/etc/apache/httpd.conf ;-) -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Peter/Los Angeles, CA Sent: December 27, 2001 12:53 To: [EMAIL PROTECTED] Subject: apache question part2 Dear People, Thank you for your help with my initial apache question. I don't know if this is a malfunction or what, although it seems to work. I opened up the router, and directed it to my server at home. It's responding so I know the daemon is working. The number of times that I've used apache, I've never seen this as an initial message. Is it possible that it's just the port that had some corrupted initial message? Anyway, I'll try the other pages in that directory. Take a look at what I'm talking about. http://haloflightleader.net Peter To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
tcpd not installed on 4.5-PRERELEASE
Hello, I just cleandir'ed out my whole /usr/obj/src and rebuilt the world (4.5-PRERELEASE), installed it, and figured that tcpd seems to be missing from the install, while tcpdchk and tcpdmatch are installed. What's up here? Did I do something wrong? Is this worth a send-pr? Or is tcpd just not part of the system? -- Matthias Andree They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety. Benjamin Franklin To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Gnome
Probably not the right place to ask, but am trying to start upgrading my ports junque. Gnome bombs out in the controlcenter... I assume there is a sequence to doing the build of gnome, but core and build both bomb out when trying to build controlcenter. Problem appears to be structure related, with a missing member. Can anybody provide any clues? Thanks.. Sam To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: 4.4-STABLE crashes - suspects new ata-driver over wd-drivers
This is great news! I'm crossing my fingers and hoping that Nils can't reproduce the crash any more with Soren's fix. Just to let you all know, Nils has been working his ass off helping me track his crash down. I've been pulling my hair out... I gave him patch after patch to test various conditions panic if the nfs_node's hash list somehow got broken, and for the last week not a single one of those tests detected the problem prior to the panic. The nfs_node's hash list was being corrupted seemingly out of nowhere. The last two days I've had Nils use hardware watchpoints in DDB to try to track down what was modifying the memory location, with no success. The watchpoint was catching the (correct) write to the list head but then failed to catch the corrupted write prior to the system panicing, which is what makes me believe it is some sort of chipset issue. Another thing to note: One of the really weird things about Nils crashes is that the same memory location was getting corrupted every time, five times in a row (which made it possible to use a hardware watch point). The corruption changed somewhat when he added the hardware watch point. Another similar set of crashes in the vm_page_list (that other people report, including a number of machines at Yahoo), have a similar M.O IDE drive, medium/heavy activity, but while corrupted address always winds up in the (static) vm_page array, it always tends to be slightly different. I'm hoping that it winds up being the same or similar issue. I'm not ruling out the possibility that chipsets other then the 686B have problems too. In anycase, Nils description makes a lot of sense. I've asked him to continue testing his system to make sure that this particular crash cannot be reproduced, and I am crossing my fingers. I'm also wondering how applicable this patch might be in regards to forcing a 'safe' mode for other PCI chipsets, to allow us to test it on non-686B machines that have similar problems. -Matt Matthew Dillon [EMAIL PROTECTED] :On Thu, Dec 27, 2001 at 10:45:01AM +0100, Søren Schmidt stood up and spoke: : : OK, here goes the VIA 686b patch, it is hand cut out from the bulk patches : to go into 4.5 so beware :) : :Well, as Matt has said, I reported a crash that he's trying to debug. Since :I have the 686b in my machine, I applied the patch. Ever since then I was :not able to reproduce the crash again, although yesterday it was so easy :that I could do it twice an hour ;-) : :Anyway, you (Soren) said that the right way to fix this is a BIOS update. :Now, could it be that some mainboard manufacturers are incapabel of :handling this? I'm using the latest BIOS for my board, and according to :http://www.chaintech.com.tw/DL/7xMB/7AJA0.HTM, this should already have :been fixed in their BIOS release from 2001-04-23... : :Second interesting thing: I was using a UDMA66 drive on my 686b until a few :weeks ago and never had any problems - the stuff Matt is looking at only :started two appear a short while after I exchanged that drive for a UDMA100 :one. So, it seems as if probably the slower drive didn't produce a high :enough PCI workload for anything to actually happen. : :This fix will probably also have some influence on a few other similar :problems (I read Matt was working on many of them). In the end I hope that :this fix - or a variation thereof - will actually go into 4.5. : :Greetings :Nils : :-- :Nils Holland To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Trying NT Hacks
From: Peter Ong [EMAIL PROTECTED] Sent: Thursday, December 27, 2001 7:02 PM Subject: Re: Trying NT Hacks Really... I just wonder how they figure out the IPs, other than randomly guessing. Someone did mention that, and I guess there really aren't that many IP addresses that a computer could randomly generate in a short amount of time without covering the whole spectrum. They are scanning. Nimda doesn't just guess IP's, it tries every single IP in the entire subnet. That is, if your IP address is 192.168.45.23 and you are inftected, your machine will loop through trying to connect (and infect) every IP address from 192.168.0.1 to 192.168.255.254. This can be quite time-consuming (especially if many of those IP's are not online, or dropping packets aimed at port 80 without sending a RST). But the worm isn't really concerned about the efficiency of the machine it infected, or the bandwidth it's wasting, so it turns out to be quite an effective way to spread. --K To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Trying NT Hacks
One thing that works for me is the portsentry. It's pretty simple, but blocks portscans on a large number of ports, can be configured for tcp or udp., etc.. I have noticed an increase in port 111 and 119 attempts since I started posting here.. mostly random people, and I do frequent lookups. If I start getting lots of trash going to the webserver, I just use the firewall rules and block the whole shebang! Works for me... Sam To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Trying NT Hacks
I put up a brand new server with a brand new IP and the attacks were immediate so, I figured they are just running loose in swarms... At 07:02 PM 12.27.2001 -0800, Peter Ong wrote: Really... I just wonder how they figure out the IPs, other than randomly guessing. Someone did mention that, and I guess there really aren't that many IP addresses that a computer could randomly generate in a short amount of time without covering the whole spectrum. Peter - Original Message - From: Julien B. [EMAIL PROTECTED] To: Peter Ong [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Thursday, December 27, 2001 6:57 PM Subject: Re: Trying NT Hacks On Thu, Dec 27, 2001 at 06:39:58PM -0800, Peter Ong wrote: I don't know what it is with some people. I post my site here today because I was wondering about why the initial page was gibberrish, and then I get crackers. I finally get home, and I'm reviewing my log files, and I'm seeing some folks trying to use IIS/NT exploits on my FreeBSD machine. It's infuriating. My logs are full of these too, and getting bigger and bigger everyday. Most of these attacks comes from some Windows worms. I'm totally amazed through, as i get one such connection every 10 minuts, and my web server is not even public. Regards Julien B To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message Best regards, Jack L. Stone, Server Admin Sage-American http://www.sage-american.com [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Trying NT Hacks
This thread has nothing to do with stable -- take it to chat, or just drop it. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
SMP kernel (still) faulting.
I never saw this message go through to the list, so I'm trying again.
Sorry if this a double...
Looks like I spoke too soon. I checked on the box Sunday afternoon and
saw that it wasn't responding, but was out of town and couldn't do
anything about it. I arrived Wednesday to find the box hung, again,
despite the MAXUSERS=512 option:
#0 dumpsys () at ../../kern/kern_shutdown.c:473
#1 0xc016e410 in boot (howto=260) at ../../kern/kern_shutdown.c:313
#2 0xc016e841 in panic (fmt=0xc026ed64 from debugger)
at ../../kern/kern_shutdown.c:581
#3 0xc01379cd in db_panic (addr=-1071658876, have_addr=0, count=-1,
modif=0xe3267d24 ) at ../../ddb/db_command.c:435
#4 0xc013796b in db_command (last_cmdp=0xc02a3f64,
cmd_table=0xc02a3da4,
aux_cmd_tablep=0xc02c1018) at ../../ddb/db_command.c:333
#5 0xc0137a32 in db_command_loop () at ../../ddb/db_command.c:457
#6 0xc0139be3 in db_trap (type=12, code=0) at ../../ddb/db_trap.c:71
#7 0xc0241e44 in kdb_trap (type=12, code=0, regs=0xe3267e80)
at ../../i386/i386/db_interface.c:158
#8 0xc025629e in trap_fatal (frame=0xe3267e80, eva=269781285)
at ../../i386/i386/trap.c:951
#9 0xc0255f1d in trap_pfault (frame=0xe3267e80, usermode=0,
eva=269781285)
at ../../i386/i386/trap.c:849
#10 0xc0255a63 in trap (frame={tf_fs = 24, tf_es = 16, tf_ds = 16,
tf_edi = -452349504, tf_esi = 0, tf_ebp = -484016404,
tf_isp = -484016468, tf_ebx = 269781252, tf_edx = 1744834624,
tf_ecx = -947204083, tf_eax = 0, tf_trapno = 12, tf_err = 2,
tf_eip = -1071658876, tf_cs = 8, tf_eflags = 66050, tf_esp = -
452349504,
tf_ss = 0}) at ../../i386/i386/trap.c:448
#11 0xc01fc884 in ffs_fsync (ap=0xe3267f18)
at ../../ufs/ffs/ffs_vnops.c:150
#12 0xc01fb3ae in ffs_sync (mp=0xc786cc00, waitfor=3, cred=0xc16ee900,
p=0xdf500780) at vnode_if.h:558
#13 0xc019f315 in sync_fsync (ap=0xe3267f7c)
at ../../kern/vfs_subr.c:2861
#14 0xc019d517 in sched_sync () at vnode_if.h:558
You can take a look at the relevant files at:
ftp://ftp.gactr.uga.edu/pub/outgoing/dillon/smp-fault-512.tar.gz
which, unfortunately, this time is rather large as I did not impose any
memory limitations in that kernel build.
Hope to get this sorted out.
Robin.
The core you gave me had definitely run out of KVM.
I increased the MAXUSERS to 512 as you suggested and the SMP kernel
does seem to be holding now.
--
Robin P. Blanchard
IT Program Specialist
Georgia Center for Continuing Ed.
fon: 706.542.2404 fax: 706.542.6546
email: [EMAIL PROTECTED]
-
This mail sent through IMP: http://horde.org/imp/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-stable in the body of the message
SMP kernel (still) faulting.
Matt --
Looks like I spoke too soon. I checked on the box Sunday afternoon and
saw that it wasn't responding, but was out of town and couldn't do
anything about it. I arrived today to find the box hung, again, despite
the MAXUSERS=512 option:
#0 dumpsys () at ../../kern/kern_shutdown.c:473
#1 0xc016e410 in boot (howto=260) at ../../kern/kern_shutdown.c:313
#2 0xc016e841 in panic (fmt=0xc026ed64 from debugger)
at ../../kern/kern_shutdown.c:581
#3 0xc01379cd in db_panic (addr=-1071658876, have_addr=0, count=-1,
modif=0xe3267d24 ) at ../../ddb/db_command.c:435
#4 0xc013796b in db_command (last_cmdp=0xc02a3f64,
cmd_table=0xc02a3da4,
aux_cmd_tablep=0xc02c1018) at ../../ddb/db_command.c:333
#5 0xc0137a32 in db_command_loop () at ../../ddb/db_command.c:457
#6 0xc0139be3 in db_trap (type=12, code=0) at ../../ddb/db_trap.c:71
#7 0xc0241e44 in kdb_trap (type=12, code=0, regs=0xe3267e80)
at ../../i386/i386/db_interface.c:158
#8 0xc025629e in trap_fatal (frame=0xe3267e80, eva=269781285)
at ../../i386/i386/trap.c:951
#9 0xc0255f1d in trap_pfault (frame=0xe3267e80, usermode=0,
eva=269781285)
at ../../i386/i386/trap.c:849
#10 0xc0255a63 in trap (frame={tf_fs = 24, tf_es = 16, tf_ds = 16,
tf_edi = -452349504, tf_esi = 0, tf_ebp = -484016404,
tf_isp = -484016468, tf_ebx = 269781252, tf_edx = 1744834624,
tf_ecx = -947204083, tf_eax = 0, tf_trapno = 12, tf_err = 2,
tf_eip = -1071658876, tf_cs = 8, tf_eflags = 66050, tf_esp = -
452349504,
tf_ss = 0}) at ../../i386/i386/trap.c:448
#11 0xc01fc884 in ffs_fsync (ap=0xe3267f18)
at ../../ufs/ffs/ffs_vnops.c:150
#12 0xc01fb3ae in ffs_sync (mp=0xc786cc00, waitfor=3, cred=0xc16ee900,
p=0xdf500780) at vnode_if.h:558
#13 0xc019f315 in sync_fsync (ap=0xe3267f7c)
at ../../kern/vfs_subr.c:2861
#14 0xc019d517 in sched_sync () at vnode_if.h:558
You can take a look at the relevant files at:
ftp://ftp.gactr.uga.edu/pub/outgoing/dillon/smp-fault-512.tar.gz
which, unfortunately, this time is rather large as I did not impose any
memory limitations in that kernel build.
Hope to hear from soon.
Robin.
The core you gave me had definitely run out of KVM.
I increased the MAXUSERS to 512 as you suggested and the SMP kernel
does seem to be holding now.
--
Robin P. Blanchard
IT Program Specialist
Georgia Center for Continuing Ed.
fon: 706.542.2404 fax: 706.542.6546
email: [EMAIL PROTECTED]
-
This mail sent through IMP: http://horde.org/imp/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-stable in the body of the message
Re: what a can of worms! (Gnome flames)
Hey, I once tried to do a pure make kde2 from the ports and it took more than a day on a 300 Mhz. Granted it was a 56k modem, but at least 80% of the time was in the compile. I gave up and used the CD's. When you look at the gnome philosophy, which is having a bazillion g-apps written by everyone and their cousin all interlocking in even more bizarre ways (relative to the more central kde, which is baroque enough) -- well hats off to all of you doing the compiles. Perhaps the team should consider a gports of gdeps or something to keep track of it all. (FLAME ON) the biggest linux-ism (I'd say GNU-ism, but I'm not sure GNU would have done it this way) I encounter in day to day life is the lack of rhyme or reason to the packages, which is why you need a redhat or a suse to sort through them. -r To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Problem with /usr/ports/graphics/glide3
27/12/2001 22:48:36, Josh Tolbert [EMAIL PROTECTED] wrote: I have a working X 4.1.0/DRI setup for my voodoo3/3000 at home (documentation of how I managed to get it working is at http://halcyon.scoundrelz.net/~hemi/dri.txt). I found a PC at work and decided I'd try to replicate my X 4.1.0/DRI setup at work. X installed fine from ports and /usr/ports/graphics/glide3 downloaded fine. I applied anholt's patch from ports/31767. On build (make -DWITH_VOODOO3=1 install), I get errors such as the following, with stop errors afterwards: automake: configure.in: required file `./depcomp' not found automake: cvg/glide3/src/makefile.autoconf.am: Assembler source seen but `ASFLAGS' not defined in `configure.in' automake: h3/glide3/src/makefile.autoconf.am: object `cpudtect.lo' created by `cpudtect.c' and `cpudtect.S' automake: h3/glide3/src/makefile.autoconf.am: object `cpudtect.lo' created by `cpudtect.c' and `cpudtect.S' automake: h3/glide3/src/makefile.autoconf.am: object `cpudtect.lo' created by `cpudtect.c' and `cpudtect.S' automake: h3/glide3/src/makefile.autoconf.am: object `cpudtect.lo' created by `cpudtect.c' and `cpudtect.S' automake: h3/glide3/src/makefile.autoconf.am: Assembler source seen but `ASFLAGS' not defined in `configure.in' Could this be related to the issue described in this message from Boxing day? http://docs.freebsd.org/cgi/getmsg.cgi?fetch=634450+0+current/freebsd-ports Matthew To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
