Re: Ports forbids me to install compat3x-i386

2007-05-06 Thread Theorem


Stevan Tiefert wrote:

I need to install the port misc/compat3x-i386 as a dependency for the
port audio/mbrola. The port misc/compat3x-i386 is marked as IGNORE and
it returns an error after portinstall compat3x-i386:

vagabund# portinstall compat3x-i386
** Port marked as IGNORE: misc/compat3x:
is forbidden: FreeBSD-SA-03:05.xdr, FreeBSD-SA-03:08.realpath
- not fixed / no lib available


How can I install the port compat3x-i386?


'make install' ?

The port you're trying to install ( mbrola ) is binary only and requires 
libraries that are no longer either 1. in the expected locations or 2. replaced 
by something better.   I suspect since the maintainer for compat3x listed as 
[EMAIL PROTECTED] then there's not much you can do other than mail that list.


	If you decide to hack up your own BSD dist, drag in the binary from ports, and 
keep adding libraries to your system.  The errors from the binary should point 
out what's wrong and what to add next.


Not much help, good luck.


Theorem

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


FreeBSD 6.0 fdisk = bad disk geometry ?

2007-05-01 Thread Theorem
I'm having trouble setting up a new RAID5 array.  It's a RocketRAID 1740 with 4x 
500G disks, in RAID5 this gives approx. 1.5T of space.  It looks like it's 
operating properly on /dev/da0 .


Unfortunately, when I go to FDISK this via /usr/sbin/sysinstall I see the same 
error over and over and over trying to set my disk to the right cycls / heads / 
sectors.


here are 2 screenshots of the messages :

http://i7.photobucket.com/albums/y260/theorem21/manual_set_err.jpg
http://i7.photobucket.com/albums/y260/theorem21/repeat_set_err.jpg

Even trying to set the disk manually gives the repeat_set_err.jpg, so I can't 
possibly have a correct disk geometry.


Can anyone help me out ?  Any suggestions are welcome, I don't know if ignoring 
this is the best option.




Thanks,

theorem
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Make is broken! How to fix?

2007-05-01 Thread Theorem



W. D. wrote:

At 21:25 5/1/2007, Garrett Cooper wrote:

W. D. wrote:

At 20:59 5/1/2007, Matt Emmerton wrote:

usw2# cd make++
usw2# ls -lt
total 5
-rw-r--r--  1 root  wheel  1221 May  1 18:35 Makefile
-rw-r--r--  1 root  wheel   190 May  1 18:35 distinfo
-rw-r--r--  1 root  wheel   643 May  1 18:35 pkg-plist
-rw-r--r--  1 root  wheel   602 Oct 17  2004 pkg-descr
usw2# make install
/usr/ports/Mk/bsd.port.mk, line 5460: Malformed conditional
(defined(USE_RCORDER) || defined(USE_RC_SUBR)  ${USE_RC_SUBR:U} != YES)
/usr/ports/Mk/bsd.port.mk, line 5470: Malformed conditional
(defined(USE_RC_SUBR)  ${USE_RC_SUBR:U} != YES)
/usr/ports/Mk/bsd.port.mk, line 5481: if-less endif
/usr/ports/Mk/bsd.port.mk, line 5481: Need an operator
/usr/ports/Mk/bsd.port.mk, line 5958: if-less endif
/usr/ports/Mk/bsd.port.mk, line 5958: Need an operator
make: fatal errors encountered -- cannot continue

FreeBSD 4.4-RELEASE

Just ran cvsup.  Any ideas?
--

The ports collection is only guaranteed to work on the current release of
FreeBSD, which is 6.2.
You're running 4.4-REL, which is fairly old (~5.5 years -- Sep/2001) and you
should consider upgrading.

How do I do that without killing this production server?


--
Matt Emmerton

W.D.,
	You can't unfortunately. The only way to go about this is plan out a 
date when you can take down the server for approximately 1-5 hours 
(comfortably) depending on what you need to compile / install, and the 
speed of the machine.
	Another option (not really encouraged, but available), is to take 
cvsup, sync to the most current 5.5 / 6.2 tree, and compile, then take 
down your machine quickly into single-user mode while installing the new 
kernel / world. The process is in gross detail here: 
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cutting-edge.html.


	Also, did you know that your mail address probably is getting marked as 
spam by the majority of the users on this list running anti-spam software?


Why?  What anti-spam methods are you using?


Mark,
	That's not true. The ports collection is supposed to work for all 
versions of FreeBSD which are supported, which includes 5.x.


-Garrett


	Well, you could also roll back the port for 'make' via cvsup to a point where 
it does compile, but 4.4 is ancient. I think it's time to bite the bullet and 
upgrade.


	I suggest going to at least 4.11 first.  Then *maybe* a jump to 5.x , followed 
by a jump to 6.x.


	If this is production I'd build out a 6.2 version on another machine, throw the 
software from box A onto Box B , then swap them quickly ( maybe just the HDDs 
even!), downtime would be almost nothing and you can run this test to work out 
any kinks along the way.


	If that's not an option with a second machine then a staged upgrade to the 
latest of the major revisions ( 4.4 - 4.11 , 4.11 - 5.5 , 5.5 - 6.2 )  The 
three staged approach should creep in the changes slowly enough so you can 
address problems along the way should there be any issues.  A straight jump from 
4.4 - 6.2 probably won't work due to the major changes along the way (ACLs have 
been introduced, standard locations for various system utils have moved , etc.. 
).  You will probably want a settling period for each of the staged approach, 
say , 3 - 5 days after each one ?


Watch out for ISA cards if you have any, I attempted a jump from 4.11 - 5.1 
with problems :(


Good luck,
Theorem
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: send error with perl and unix domain sockets

2007-05-01 Thread Theorem

Andy Greenwood wrote:

Sent this a while back and never got a response. Any ideas would be
very appreciated!


Because it's too long, I don't know what you're asking and it's also perl/php, 
not FreeBSD.



I'm working on getting a script to work (see below). It is a perl
daemon associated with a bittorent client that I am helping develop.
The daemon uses unix domain sockets to commincate with the php pages.
However, anytime a message is sent via php, the script dies with

send: Cannot determine peer address at
/usr/local/www/root/tf-b4rt/trunk/html/bin/fluxd/fluxd.pl line 1256

I did some research and found a similar problem with OpenBSD's perl
http://www.nntp.perl.org/group/perl.perl5.porters/2007/02/msg121151.html


Yes, but aren't you having a problem with php ?

*SNIP*

 the bug report above
suggests that this was a problem for OpenBSD due to differences in
struct sockaddr_un. Could that be a problem here as well?


try :  EFNet #perlhep   or freenode #perl or #perlhelp  Unfortunately I can't 
find a decent perl mailing list for you.  Also look on line 1256.


But If you're really asking a php question try #php in either location.   Might 
I suggest rewriting it in perl instead ?


*SNIP END*
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]