from:"b. f."

László wrote:
Thank you everybody!
Actually I use cvsup, and it is up to date, but now I give a try with portsnap.

It sounds like your index file or your portsdb are older than the rest
of your ports tree.  Try running 'portsdb -Fu'.

b.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: portupgrade

This can happen if the ports tree or index file is outdated.
csup/portsnap, run pkgdb -Fu, and try it again.

I think you meant 'portsdb -Fu'.  The pkgtools often run 'pkgdb -u'
and 'pkgdb -aF' automatically, and a full-blown 'pkgdb -F' or 'pkgdb
-L' usually isn't required unless there is an error, although in most
cases it wouldn't do any harm.

b.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: Should root partition be first partition?

 You can even
leave gaps between partitions if you want, but that is pretty crazy
since it just wastes some of the available space.

There have been quite a lot of recommendations on how to lay out a disk
for best performance, based on the observation that disk access times
vary depending on how far away the data is from the spindle, and the
expected usage patterns for the partition.  Like any such advice, it
has tended to become less valid over time.  Modern disks really don't
have any physical meaning to the Cylinder/Head/Sector style addressing
schemes[*] nowadays -- and you're pretty much bound to be using LBA
style addressing anyhow.  Also, machines nowadays have so much RAM that
(a) swap is hardly ever used and (b) access to popular files is
frequently answered out of VM caches rathe than needing disk IO.


Layout is still important, and leaving some blank space may not be so
crazy.  Here I'm thinking not so much of ordering (although one would
probably be best served by the recommended default ordering), but of
alignment, size, raid/stripe/concat configuration, and file system
block and fragment size selection.  Witness the (as much as tenfold)
performance difference from simple changes, highlighted in the recent
thread entitled 'File system blocks alignment' on freebsd-arch@ during
December 2009 - January 2010, beginning with:

http://lists.freebsd.org/pipermail/freebsd-arch/2009-December/009770.html

If you're laying out a new disk, you may as well take a few minutes
and get the most out of it, even if you're not going to invest in a
lot of new hardware.

b.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: Should root partition be first partition?

On 2/8/10, Jerry McAllister jerr...@msu.edu wrote:
 On Mon, Feb 08, 2010 at 02:37:30PM -0500, b. f. wrote:

  You can even
 leave gaps between partitions if you want, but that is pretty crazy
 since it just wastes some of the available space.
 
 There have been quite a lot of recommendations on how to lay out a disk
 for best performance, based on the observation that disk access times
 vary depending on how far away the data is from the spindle, and the
 expected usage patterns for the partition.  Like any such advice, it
 has tended to become less valid over time.  Modern disks really don't
 have any physical meaning to the Cylinder/Head/Sector style addressing
 schemes[*] nowadays -- and you're pretty much bound to be using LBA
 style addressing anyhow.  Also, machines nowadays have so much RAM that
 (a) swap is hardly ever used and (b) access to popular files is
 frequently answered out of VM caches rathe than needing disk IO.


 Layout is still important, and leaving some blank space may not be so
 crazy.  Here I'm thinking not so much of ordering (although one would
 probably be best served by the recommended default ordering), but of
 alignment, size, raid/stripe/concat configuration, and file system
 block and fragment size selection.  Witness the (as much as tenfold)
 performance difference from simple changes, highlighted in the recent
 thread entitled 'File system blocks alignment' on freebsd-arch@ during
 December 2009 - January 2010, beginning with:

 http://lists.freebsd.org/pipermail/freebsd-arch/2009-December/009770.html

 If you're laying out a new disk, you may as well take a few minutes
 and get the most out of it, even if you're not going to invest in a
 lot of new hardware.

 The system nowdays does all that figuring for you and manages
 boundaries reasonably.

 jerry


That does not seem to be the conclusion of those who contributed to
the thread I cited, although reasonably is open to interpretation.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: display and manipulate math symbols?

2010-02-09 Thread b. f.

 Is there any app or web site where you can select from a bunch
of math symbols and arrange them on-screen?  I'm not talking
about a program to solve; just display.  And i think you can
describe things in english like sqrt(2) in OOo, and have that sq
root sign displayed.  Not that either; rather pre-drawn symbols
that could be moused around,

editors/abiword with deskutils/gucharmap?

graphics/xfig or graphics/gimp with some math symbol images like those
at:   http://us.metamath.org/symbols/symbols.html?

The drag-and-drop requirement is a bit limiting. If OpenOffice doesn't
meet your needs (are you sure the drawing or presentation components
won't work for you?), and you have the time, you might be better off
learning TeX and using something like editors/texmacs or print/lyx15,
which are WYSIWYG, or nearly so.

b.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: openal-soft

2010-02-10 Thread b. f.

I did as  UPDATING says and everything were look okay but when I update (big
update) the system mplayer complain that cannot install openALL because
openal-soft is installed. I went bacjk to the openALL and it is okay but my
question is it is possible to build mplayer with openal support and openal-
soft installed, please?

This is not quite specific enough.  Do you mean, can I use
audio/openal with multimedia/mplayer, and audio/openal-soft with all
of my other openal software?  Or do you mean, can I use
audio/openal-soft with all of my software, including
multimedia/mplayer?

The answer to the first question is yes, but I don't think you will
want to do this.  Because audio/openal conflicts with
audio/openal-soft, you would  have to install audio/openal in a
different PREFIX, and then patch the mplayer port to find and link
with the audio/openal libraries, by changing the openal-related
LIB_DEPENDS in mplayer, and either adding a hard-coded rpath directive
to the mplayer binaries, or using libmap.conf(5) with mplayer
constraints, or building statically-linked mplayer binaries, or always
calling mplayer with directives like LD_LIBRARY_PATH or LD_PRELOAD, or
using custom linker scripts in the place of the openal.so[.?].

It would be easier to just use audio/openal-soft with all of your
software.  This ought to work, because the openal-soft developer
claims that openal-soft is compatible with the older openal:

This library is meant as a compatible update/replacement to the
deprecated OpenAL Sample Implementation (the SI).

http://kcat.strangesoft.net/openal.html

and some other packaging systems have switched  to using it with
mplayer (Debian, for example).  However, I haven't tested this, so you
will have to try it and see if it works.  To do this, remove
audio/openal, install audio/openal-soft, change any WANT_OPENAL
settings to soft, patch mplayer's Makefile.options:

--- Makefile.options.orig   2010-02-10 17:43:54.0 -0500
+++ Makefile.options2010-02-10 17:50:27.0 -0500
@@ -189,7 +189,7 @@
 .endif

 .if defined(WITH_OPENAL)
-LIB_DEPENDS+=  openal.0:${PORTSDIR}/audio/openal
+USE_OPENAL=soft
 .else
 CONFIGURE_ARGS+=   --disable-openal
 .endif

(the whitespace in that patch will probably need to be fixed) and then
rebuild mplayer.  If this works, you should contact the mplayer
maintainer, and ask him to switch the port over to the new USE_OPENAL
framework, and to prefer the newer openal-soft, which is now the
default.


b.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: custom kernel

2010-02-14 Thread b. f.

Derek Funk wrote:
On 2/13/2010 5:31 AM, Erik Norgaard wrote:
 On 13/02/10 04:08, Derek Funk wrote:
 I am trying to find how to install a custom kernel at installation. I
 have found an option in sysinstall to select a kernel. How do I add my
 own to the options so I can select it?

 I think the standard procedure is to install the generic kernel at
 installation then install your custom kernel afterwards. You should
 always keep the generic kernel to fall back on in case of any problems.

 BR, Erik

My kernel is basiclly is the generic kernel just with some added options
and removed devices i don't have. I have built and installed many times
after installation. I play around with this machine a lot and just want
to be able to have my kernel installed at installation.

If it's just one machine, and you are building the custom kernel on
it, why not just use:

make kernel KERNCONF=insert the name of your kernel config file here

as described in /usr/src/UPDATING?  Why use sysinstall at all?

If you are building custom release media, or using a custom network
install, then you can modify sysinstall with scripts, as described in
sysinstall(8), release(7), ch.3 and 5 of

 http://www.freebsd.org/doc/en_US.ISO8859-1/articles/releng/index.html

, the sample install.cfg file, and

http://www.freebsd.org/doc/en_US.ISO8859-1/articles/pxe/article.html

Or you can take an alternative approach that doesn't use sysinstall, as in:

http://www.freebsd.org/doc/en_US.ISO8859-1/articles/fbsd-from-scratch/index.html

or

http://www.freebsd.org/doc/en_US.ISO8859-1/articles/nanobsd/index.html
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: shell script to cap first letter?

2010-03-21 Thread b. f.

i'm wondering if there is a script that i could run my plaintext
files thru that would capitalize thef first letter of each
sentence [[ assuming the character wasn't already a cap!]]

more and more, in recent years, i have posted questions or
written things that have been sloppily or casually hacked
together in all lower case.  this filter would have to determine
what was and was not a sentence.  or a sentence fragment.
[ai]spell can catch i've and suggest I've, etc.

You're asking a lot from a simple filter if you want it to
discriminate between uses of . to terminate a sentence, and other
uses of . that do not require the following word to be capitalized,
such as the use of . in abbreviations -- a lot of fairly
sophisticated spelling and grammar checkers can fail to do this
reliably.  But if you want a naive filter you could use textproc/gsed,
with the /U GNU extension (our BSD sed(1) doesn't understand it),
e.g.:

gsed -e 's|\(\.[.[:space:].]\)\([a-z]\)|\1\U\2|g'

or you could use BSD sed(1), together with a more cumbersome
capitalization script, like the cflword[12345].sed scripts at:

http://sed.sourceforge.net/grabbag/scripts/#txfo

Or you could use Perl.  Or awk(1). Or script a [non-]interactive call
to a more sophisticated spelling or grammar checker. Or roll your own.
 For questions like this, try searching the web first.

b.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: Is CTM still being offered for updating FreeBSD?

2011-02-25 Thread b. f.

So I have a few questions:
1) Is it still being offered and supported as a method of updating
FreeBSD systems?

As of today, yes -- I have recent deltas in my mailbox.  But you could
easily check by subscribing, and looking at:

http://ftp.freebsd.org/pub/FreeBSD/CTM

where the deltas are still being added every few hours.


2) If not can the section in the handbook be removed? I have attached
a patch which removes references to CTM from the handbook. Should it
be applied?

3) Probably the most controversial question - but I'll ask it
nonetheless. If CTM is no longer an option for updating FreeBSD is
there any reason to leave it in base? Is it still being used by a
sufficient number of people to maintain it?

I can't answer for the maintainer, and I don't have usage statistics,
which you could probably obtain from the mailing list and WWW admins.
But the fact that it works, without requiring a lot of resources or
the need for extensive maintenance, and has the benefits that are
clearly described in the Handbook, suggest that you should leave it
alone.  Why is this question even arising? Surely there are other
problems that need to be addressed much more than the ending of a
useful, uncontroversial service by someone who is not familiar with
it?

b.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: GNU make doesn't understand .for? suffix rules obsolete?

2011-03-02 Thread b. f.

 In particular I was surprised
 to find out that GNU make considers
 suffix rules obsolete:
 http://www.gnu.org/software/make/manual/html_node/Suffix-Rules.html#Suffix-Rules

 I didn't think the suffix rules are
 obsolete in BSD make, are they?


No (Although maybe some people will argue that BSD make itself is obsolete...).
But what does it matter -- gnu make still understands them, doesn't it?

 The GNU replacement for suffix rules
 are pattern rules. Now these don't
 seem to be supported by BSD make, are they?


There are some implicit rules, and variable expansions can be used,
but many of the GNU constructs are not supported. See make(1), and:

http://www.freebsd.org/doc/en_US.ISO8859-1/books/pmake/index.html

 Also, since .for .endfor
 construct doesn't seem to be supported
 by GNU make (please confirm or correct if I'm wrong),
 what is an alternative in GNU make?

Patterns and the foreach function:

http://www.gnu.org/software/make/manual/html_node/Foreach-Function.html#Foreach-Function


 My aim, of course, is to have
 a makefile, which would work
 on both GNU and BSD make.
 The project is comparatively simple,
 just a collection of fortran files,
 which need to be compiled and several
 executables need to be linked
 against a number of libraries.

You can limit yourself to constructs common to both makes, but if you
prefer gnu make, then why not just write makefiles accordingly and use
gmake from devel/gmake?

b.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: SIL Fonts

2011-03-03 Thread b. f.

I was unable to find a port with Charis or Doulos typefaces.  Perhaps
someone can tell me that these typefaces are part of some meta-port.  Which?

Hmm. I don't see any port with them, either, although bundling of them
is permitted, under certain circumstances, and I didn't look into the
innards of every font port.  Of course, you could always get them from
SIL and add them manually.  And I imagine that they may be accessible
via third-party texlive packages. Do you need ports for these fonts?

b
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: SIL Fonts

2011-03-03 Thread b. f.

On 3/3/11, Jason C. Wells j...@speakeasy.net wrote:
 On 03/03/11 05:01, b. f. wrote:

 I don't _need_ ports but I do like to use them because they include
 management tools.  thanks for the response.

Right, then, I will add some ports.

b.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: Kernel compiling problems

2011-03-03 Thread b. f.

Heya!

Anybody know what's wrong with this?

## make buildworld buildkernel KERNCONF=NINJA

...

/usr/src/sys/kern/sysv_msg.c:163: error: invalid application of 'sizeof' to
incomplete type 'struct freebsd7_msgctl_args

This error message is suggestive. ;)


options COMPAT_FREEBSD4

options COMPAT_FREEBSD5

options COMPAT_FREEBSD6

Upgrading from 7.x to 8.x, eh?  But I think you forgot to update parts
of your kernel config.  From
src/sys/conf/NOTES:

Note that as a general rule, COMPAT_FREEBSDn depends on
COMPAT_FREEBSDn+1, COMPAT_FREEBSDn+2, etc.

... up until m-1, where m is the FreeBSD version you are building.  So
if you have COMPAT_FREEBSD[456], you need COMPAT_FREEBSD7 as well.
(When running 7.x, you didn't need it, of course.)


b.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: optical driver with ahci bios mode but ata(4) driver

2011-03-05 Thread b. f.

On Mon, Feb 28, 2011 at 8:31 PM, David Demelier
demelier.david at gmail.com wrote:
 Hello,

 My bios can be set to use IDE emulation or ahci mode, I prefere the ahci
 mode because it's a bit faster.

 It's probably stupid to stay with ata(4) driver with the ahci mode, isn't
 it? But with ahci(4) driver you can't burn with burncd(8) and cdrecord just
 fail and break an blank cd for nothing.

 I guess this is the correct behavior when trying to use burncd(8) /
 cdcontrol(1) :

 markand at Melon ~ $ burncd msinfo
 burncd: ioctl(CDIOREADTOCHEADER): Input/output error

 markand at Melon ~ $ cdcontrol info
 cdcontrol: getting toc header: Input/output error
 cdcontrol: Input/output error

 But why the optical drive is only affected? If I use ata(4) driver even with
 ahci mode set in the bios, why the hard drive works pretty well?

You may still be using AHCI, via the ataahci part of ata(4), which is
not as good as the newer driver ahci(4). (Or your BIOS may be lying,
or have some legacy work-around.)

I've had occasional trouble with cdrecord and cd(4), too, and I found
that some of the errors are innocuous, and can be overcome by using
the -immed and -force flags with cdrecord.  There are also some
patches available to improve compatibility between the two, that the
submitter has not had time to commit:

http://lists.freebsd.org/pipermail/freebsd-current/2010-November/020944.html

Those may solve some problems.  Also, there are various settings that
one can tweak.  But we would know more if you provided verbose
listings of the errors that you encounter.  The upstream developer of
cdrtools is occasionally willing to help diagnose some problems, if
you ask politely and give him the necessary information.  You might
try asking him.

b.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: python27 update

2011-03-05 Thread b. f.

...
 I tried to update python26 to python27. I did as I red in /usr/ports/UPDATING:

 portmaster -o lang/python27 lang/python26 and than

  cd /usr/ports/lang/python  make upgrade-site-packages -DUSE_PORTMASTER

 and after one day and a half of pressing yes for deleting old files I got:

Has it been a day and a half already?  ;)  Seriously, though, read the
portmaster manpage and learn how you can take some shortcuts, like
running 'portmaster  -y --clean-distfiles', or using other flags to
lower the amount of interaction required.

 -
 error: Comand cc - shared -pthread -02 -pipe -WI, -rpath
 -/usr/local/lib/gcc45 -fno -strict -aliasing build/temp. freebsd-8.2-RELEASE-
 i386-2.7/build/src.freebsd-8.2-RELEASE-i386-2.7/numpy/core/src/-sortmudele.o -
 Lbuild/temp.freebsd-8.2-RELEASE-i386-2.7-lm -o build/lib-freebsd-8.2-RELEASE-
 i386-2.7/numpy/core/-sortss
 failed with exit status 1
 ***Error code 1


 Stop in /usr/ports/math/py-numpy
 =make failed for math/py-numpy
 = Aborting update
 = Update fpr py26-numpy-1.5.1,1 failled
 Aborting update
 Update for opencv-2.1.0 failed
 aborting update

 Terminated
 ***Error code 143
 Stop in /usr/ports/lang/python


You need to update your ports tree to make sure that you pick up:

http://lists.freebsd.org/pipermail/cvs-ports/2011-March/213081.html

which should fix the above problem.


 Is it possible to save this problem, please? Do I need run again cd
 /usr/ports/lang/python  make upgrade-site-packages -DUSE_PORTMASTER and wait
 one day more or will portmaster continue where it stopped?

Try:

... make upgrade-site-packages -DUSE_PORTMASTER PORTUPGRADE_ARGS=-R

Even if that doesn't work, you won't have to repeat all of your
previous work, because those ports that were successfully updated in
the last run will no longer have files in the old python26 library
directories, and so won't be rebuilt by re-running upgrade
site-packages, unless you were to run portmaster with additional
flags.

b.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: python27 update

2011-03-06 Thread b. f.

I am using portmaster all the time more or less without problems.
I like to switch to portupgrade but I don't know if is good to mix them. I
think I will wait to FreeBSD 9 and than install evrything from scratch.

You would have encountered the problem that you mentioned regardless
of whether you used portupgrade or portmaster, and the results would
have been the same.  It was a flaw in the ports tree itself, not in
the updating tool.

I think that portmaster is probably a better choice for most people,
since it implements most if not all of the features that portupgrade
does, the maintainer is more active, and it doesn't need ruby and bdb
to work, or require extra databases.  Mixing portupgrade and
portmaster shouldn't cause any problems, as long as you take care to
keep your portupgrade port and package databases up-to-date,  but it
probably isn't necessary to use both.

Whatever you decide, I urge you to take a few minutes to read the
manpage of your updating tool.  It can save you a lot of time and
frustration later.  Also, if you want to avoid problems, after major
changes to the ports tree, it is safer to wait for a few days before
updating your own ports.  Usually there are a few problems that are
uncovered and fixed after major changes are made, and it takes a few
days or a week for this to happen.

b.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: python27 update-py-psyco

2011-03-07 Thread b. f.

On 3/7/11, ajtiM lum...@gmail.com wrote:
 On Sunday March 6 2011 12:01:47 b. f. wrote:

 Thank you. I am reading /usr/ports/UPDATING special like now but there are
 problems. And I have a problem again with /usr/ports/devel/py-psyco
 I get:
 c/mergepoints.c:242: error 'JUMP_IF_FALSE' undeclared here
 *** Error code 1



There is not enough context here to learn much, but this is the kind
of error that could occur if this port is built with python 2.7.x.  It
may be that your ports tree is still not up-to-date, because this is
one of the few ports that doesn't work with python 2.7.x [The upstream
maintainer was working on a new version (see the port website), but
hasn't finished it yet], so Martin modified the port:

http://www.FreeBSD.org/cgi/cvsweb.cgi/ports/devel/py-psyco/Makefile.diff?r1=1.17;r2=1.18

Do you have those changes? Is py-psyco using python 2.5.x or 2.6.x
during the build?  If not, update your ports tree (and make sure that
it really _is_ up-to-date, by looking at the file afterward, because
some mirrors have been having problems lately), then (for safety)
rebuild whatever version of python (2.5.x or 2.6.x) you are using with
py-psyco, and then try again. If it still doesn't work, post your full
build log to the freebsd-python mailing list.

b.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: Coldfusion, Postgres and Java under FreeBSD

2011-03-07 Thread b. f.

...
 I'm running Java on FreeBSD right now, but I must say I'd probably
 stick to Linux nowadays if I had any say, at least until there comes a
 day when I'll be able to pkg_add -r openjdk7.
...

Why not now? (Or anytime this past year or more?):

http://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-8.1-release/java/openjdk-7.0.86.tbz
http://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-8.2-release/java/openjdk-7.0.122.tbz
http://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-8-stable/java/openjdk-7.0.122_1.tbz

http://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-8.1-release/java/openjdk-7.0.86.tbz
http://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-8.2-release/java/openjdk-7.0.122.tbz
http://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-8-stable/java/openjdk-7.0.122_1.tbz

etc.

b.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: python27 update-py-psyco

2011-03-08 Thread b. f.

On 3/8/11, ajtiM lum...@gmail.com wrote:
 On Monday March 7 2011 08:37:46 b. f. wrote:
 On 3/7/11, ajtiM lum...@gmail.com wrote:
  On Sunday March 6 2011 12:01:47 b. f. wrote:
 
  Thank you. I am reading /usr/ports/UPDATING special like now but there
  are problems. And I have a problem again with /usr/ports/devel/py-psyco
  I get:
  c/mergepoints.c:242: error 'JUMP_IF_FALSE' undeclared here
  *** Error code 1
...
 Thank you very much for reply but I see that is not possible to build it (I
 red about psyco on mailing list).
 For now everything works but I have more ports to rebuild but psyco is the
 big
 problem.

Well, I'm not sure what list you are referring to here, but you should
still be able to build it, if you set PYTHON_VERSION to python2.5 or
python2.6 in your build environment, on the command-line, or in any
included Makefile (like, for example, /etc/make.conf or
$PORTSDIR/devel/py-psyco/Makefile.local).  Of course, if you are using
psyco with some other software, then you may have to do the same for
that software. You can do that conditionally if you are doing it in
some common Makefile like /etc/make.conf, and still want to use other
software with another version of python. For example:

.if${.CURDIR:M*/ports/devel/py-psyco}
PYTHON_VERSION=python2.6
.endif

b.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: DTrace in RELEASE?

2011-03-15 Thread b. f.

Does anyone know if it's likely DTrace will ever make it into the generic
 RELEASEs?

Maybe, at least in part.  One of the developers has asked that the
hooks needed for dtrace be included by default in upcoming releases:

http://lists.freebsd.org/pipermail/freebsd-arch/2011-March/011157.html

b.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: Booting from firmware RAID

2011-03-16 Thread b. f.

 This is probably more PC-specific than freebsd-specific question. I have
 intel firmware raid. OS needs drivers to work with it. FreeBSD sees it as
 ar0, so it has drivers.
 But I want my OS to be installed on this drive and boot from it. It is not
 good idea, but I really want to do it:)
 Is it possible?

 boot0 and boot1 both work with HDD via BIOS interrupts and CHS, right? So,
 how do they know how to access RAID? They has no drivers.
 Or BIOS supports interrupts to access RAID with out of drivers? If so --
 what for drivers are needed? To access drive via ATA interface?

 Is it possible to boot freebsd from firmware raid?

Sometimes: it depends on the firmware, and your bios.  I had a add-in
PCIe SATA RAID controller based on a Marvell SE9128 chipset, and using
a Marvell firmware.  The bios and the FreeBSD 9-CURRENT bootloader
were able to boot from a JBOD drive attached to the controller, up
until the point where the ahci driver tried to take control of the
drive.  Then the Marvell firmware presented a fictitious configuration
to the ahci driver and returned invalid device signatures, so the boot
process failed.  On the same machine, however, I was able to boot
without problems from a JBOD drive attached to a PCI-X SATA RAID
controller based on the Silicon Image SiI3124 chipset, using a Silicon
Image firmware.

b.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: Port dependencies

2011-04-02 Thread b. f.

Chris Telting wrote:
 See above.  What I want to see is minimal installs with all features
 being usable once you install the optional components.  And run time
 detection for programs shouldn't be all that difficult or computation
 intensive.  The program would just consult pkg_info or another similar
 but faster database (and maybe somewhat platform independent) of what's
 installed on the system.

It's not a minimal install if binaries are bloated with extra code
to selectively enable _all_ functionality depending upon run-time
configuration options and dependency detection, rather than just the
functionality that is going to be used.  And build times would be
longer, usually much longer, because all functionality in the software
and all possible dependencies would have be built. And of course a lot
of software would have to be rewritten.  And I think that the added
overhead would not always be negligible. So while your idea has
certain advantages, it also has disadvantages.  It does not seem
practical to implement it, even if it were desirable to do so, for
most software at the present time.

b.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: Piping find into tar...

 I've been playing with the find command lately. Is there a way I can pipe the
 putput list of files from find, into the tar command to create an archive 
 which
 contains the files which find lists? I tried the following, but it didn't work
 (obviously).

 find -E . '.*\.txt$' -print | tar -cjf result.tgz

You could use something like:

find -X . -name '*.txt' | xargs tar -cjf result.tgz

or

find . -name '*.txt' -print0 | xargs -0 tar -cjf result.tgz

b.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: Piping find into tar...

On 5/4/11, Chris Rees utis...@gmail.com wrote:
 On 4 May 2011 08:44, b. f. bf1...@googlemail.com wrote:
 I've been playing with the find command lately. Is there a way I can pipe
 the
 putput list of files from find, into the tar command to create an archive
 which
 contains the files which find lists? I tried the following, but it didn't
 work
 (obviously).

 find -E . '.*\.txt$' -print | tar -cjf result.tgz

 You could use something like:

 find -X . -name '*.txt' | xargs tar -cjf result.tgz

 or

 find . -name '*.txt' -print0 | xargs -0 tar -cjf result.tgz

 b.

 How about using pax?

 find . -depth -print | pax -wd | gzip  archive.tgz

 or

 find . -depth -print | pax -wd | bzip2  archive.tbz


 By the way, in reference to the commands above the -j option is for
 bzip2, so the extension should be .tbz o_O

True.  I just reproduced what the OP had.  The archive will still use
bzip2 compression, and bsdtar won't have a problem handling it, but
the name will be misleading.

As you wrote, pax(1) is an option, as are cpio(1) and many others...
You should be able to use -z with pax to avoid the extra pipe and
explicit invocation of gzip in the first case.

b.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: Piping find into tar...

On 5/4/11, Modulok modu...@gmail.com wrote:


 As for pax, I thought tar could create pax archives too, via the --format
 pax
 option?

Yes, although I haven't tested it thoroughly.  pax(1) should also be
able to create a number of different archive formats via the -x flag.
I prefer tar(1) (bsdtar/libarchive), because it has more features.

b.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: Piping find into tar...

 Dne 4.5.2011 11:42, Modulok napsal(a):
  By the way, in reference to the commands above the -j option is for
  bzip2, so the extension should be .tbz o_O
 
  Thanks everyone! I went with the following, because it works regardless of
  space characters in filenames. (Thanks for the correction on the extenion. 
  It
  should indeed be 'tbz' when using the 'j' flag.)
 
  find -E . -regex '.*\.txt$' -print0 | xargs -0 tar -cjf result.tbz

 When the amount of files is huge then tar will be invoked twice
 or more. Thus result.tbz will contain just files from the last invocation.

 I consider cpio a better option here.

The use of simple patterns permitted by tar(1) or cpio(1) may be a
good choice in some cases, but we were responding to the OP's wish to
use find(1), which is a bit more flexible.  If there were a large
number of files, one could still use find and tar in many cases by
appending to the archive rather than (re)creating it with each tar
invocation, e.g.:

 find . -type f -name '*.txt' -print0 | xargs -0 tar -rvf archive.tar
; bzip2 archive.tar

b.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: Comparing two lists [SOLVED (at least it looks like that)]

2011-05-06 Thread b. f.

 2011-05-07 02:09, Rolf Nielsen skrev:
  Hello all,
 
  I have two text files, quite extensive ones. They have some lines in
  common and some lines are unique to one of the files. The lines that do
  exist in both files are not necessarily in the same location. Now I need
  to compare the files and output a list of lines that exist in both
  files. Is there a simple way to do this? diff? awk? sed? cmp? Or a
  combination of two or more of them?
...
 sort file1 file2 | uniq -d

If the lines aren't repeated in only one file...

For future reference, comm(1) exists to handle problems like this,
although (of course) TIMTOWTDI.

b.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: UDF and DVD's

2011-05-19 Thread b. f.

grarpamp wrote:
...
 I'm guessing the current state within FreeBSD means that I can
 neither read, nor create, or write, readable (compatible) images
 at this, or any given, UDF level?
...

 Is this a blocker for FreeBSD?

 For me, at least, minimally, that seems to be the case... as I now
 have no way to rip, mount and add the files to this DVD that I would
 like to add. Except to use Windows, which I consider to be unreliable
 at best.

Obviously, the base system UDF support is minimal and needs some work.
 But you may find that ports like sysutils/cdrtools[-devel] or
sysutils/udfclient will allow you to do much of what you want to do.

b.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: I486_CPU or I586_CPU in kernel config

2011-05-31 Thread b. f.

Warren Block wrote:
 On Mon, 30 May 2011, Adam Vande More wrote:

  Perhaps this is the one you meant?
 
  http://lists.freebsd.org/pipermail/freebsd-questions/2009-January/190568.html

 That's the one!  Thanks!

  Actually the two threads touch on the same subject, and it seems
  removal of those options is still desirable on newer CPU's.

 sys/i386/i386/support.s is mentioned, but doesn't seem to have anything
 explicitly specific for 586.  There are some i686 entries.

 A test for cpu_class==CPUCLASS_586 in /sys/i386/isa/npx.c is mentioned
 in the thread, but that check isn't in the current code.

Removed:

http://svnweb.FreeBSD.org/base?view=revisionrevision=209460

There was a discussion about the implications for performance,
although I don't remember when it took place, and whether it was on
the mailing lists or in a PR audit trail.  If you're interested you
can track down the details.

b.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: What is xz ?

2011-07-02 Thread b. f.

  From owner-freebsd-questions at freebsd.org  Sat Jul  2 06:45:00 2011
  Date: Sat, 2 Jul 2011 13:43:55 +0200
  From: Polytropon freebsd at edvax.de
  To: Chris Whitehouse cwhiteh at onetel.com
  Cc: freebsd-questions at freebsd.org
  Subject: Re: What is xz ?

  On Sat, 02 Jul 2011 12:26:14 +0100, Chris Whitehouse wrote:
   On 02/07/2011 07:38, Polytropon wrote:

  Correct. I'm currently on 7-STABLE where it's not yet part of
  the base system, but my new 8.2-STABLE also has it in /usr/bin.
  I believe it has been introduced with version 8...

 It is part of  '7.2-RELEASE',   Dunno about 7.1

Hmm.  Are you sure?  If this is true, the archivers/xz port needs to
be patched to IGNORE those branches of 7 that have xz.  But I don't
see any mention of it at:

http://www.freebsd.org/cgi/cvsweb.cgi/src/contrib/xz/ChangeLog

or

http://svnweb.FreeBSD.org/base/stable/7/contrib/

b.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: What is xz ?

2011-07-02 Thread b. f.

On 7/2/11, Robert Huff roberth...@rcn.com wrote:

 b. f. writes:

   It is part of  '7.2-RELEASE',   Dunno about 7.1

  Hmm.  Are you sure?  If this is true, the archivers/xz port needs
  to be patched to IGNORE those branches of 7 that have xz.

   Is that necessarily true?
   For comparison: the default system compiler is gcc-4.2.1 (I
 believe).  There are several higher numbered versions in ports.


You mean, if xz is actually in FreeBSD 7, which doesn't seem to be the
case, is it absolutely necessary to disable builds of archivers/xz on
7?  Or, for that matter, on 8 and 9? -- well, no, it isn't strictly
necessary, but what's the point of not disabling the port when the
same version of xz is in both the base system and the port, and rtld's
default search pattern will favor the former over the latter?  With
the different versions of gcc, you are at least getting some
functional differences.  If naddy updates the port to 5.1.1 or 5.0.3,
the case might be different.

b.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: Portupgrade Package Question

2011-07-09 Thread b. f.

Thomas D. Dean wrote:
...
 For the most recent try, I have

 ...
 #   OS_PATCHLEVEL:-p8
 #   OS_PLATFORM:i386  amd64
 #   OS_PKGBRANCH:   7-current 6.1-release
 OS_RELEASE=8-STABLE
 OS_BRANCH=STABLE
 OS_PKGBRANCH=8-stable

The comments above were not intended as an invitation to try to define
these constants here, but merely describe typical values that the
constants may have.  The constants are computed from parsing your
'uname -rm' output in $LOCALBASE/$RUBY_SITELIBDIR/pkgtools.rb (usually
/usr/local/lib/ruby/site_ruby/1.8/pkgtools.rb), so you cannot set them
in pkgtools.conf.  They were only mentioned so that users would know
that they were available for defining other procedures and variables
(for an example, see below).


 # Useful predefined functions:
 #
 #  localbase()
 #Returns LOCALBASE.
 ...

 But, portupgrade still tries to fetch from 8.2-release.

If you are running 8.2-RELEASE, and yet wish to obtain 8-stable
packages (which are actually built on recent versions of 8.1-STABLE,
with recent versions of the ports tree), then set PKG_SITES
appropriately in pkgtools.conf.  In this case, I think (untested) that
you could substitute

sprintf('%s/pub/FreeBSD/ports/%s/packages-%s-stable/',
ENV['PACKAGEROOT'] || 'ftp://ftp.FreeBSD.org', OS_PLATFORM, OS_MAJOR)

for the default

pkg_site_mirror(root)

in PKG_SITES.  (It might be better to upgrade your base system to
8-STABLE, in which case the defaults will be correct without any need
for these changes, and other problems will also be fixed).


 If I want to use binary ports it looks like I need to zap the ports tree
 and recreate it with portsnap.

This should not be necessary.  You should be able to use any method to
update the tree (anonymous cvs, csup/cvsup, portsnap, http/ftp, rsync,
ctm, etc.).  Of course, if your tree and index file do not correspond
to the version of the binary packages that you want to use, you will
occasionally trip over problems that will require intervention.  (Note
that in the section of the csup file that you reproduced in an earlier
message, 'release-cvs' should be 'release=cvs'.)

PKG_SITES will only be used by the ports-mgmt/portupgrade scripts; if
you want to use pkg_add(1) manually, and obtain the 8-stable packages,
then you should define PACKAGESITE in your environment, or provide a
full URL.  The ports-mgmt/portupgrade scripts also respect
PACKAGESITE, which will override PACKAGEROOT and PKG_SITES in those
scripts.

b.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: Portupgrade Package Question

2011-07-09 Thread b. f.

On 7/9/11, Thomas D. Dean tomd...@speakeasy.org wrote:
 On Sat, 2011-07-09 at 19:54 -0400, b. f. wrote:

 occasionally trip over problems that will require intervention.  (Note
 that in the section of the csup file that you reproduced in an earlier
 message, 'release-cvs' should be 'release=cvs'.)

 The '-' was a typo on my part.  The machine I used for email is not the
 machine I am updating.

 I am updating that machine, now.  The supfile contains
 *default release=cvs tag=RELENG_8

 This should track 8-stable.  Correct?

This is the tag that you would use on src collections to update your
base system sources (usually in /usr/src) to 8-STABLE.  You would use
RELENG_8_2 for the 8.2-STABLE security branch, RELENG_8_2_RELEASE for
8.2-RELEASE, and so on.

But src tags are not the same as ports tags.  That is why they have
separate example supfiles for the base system sources, and for ports.
And that is also why they have the prominent warning in the base
system example supfiles:

###
#
# DANGER!  WARNING!  LOOK OUT!  VORSICHT!
#
# If you add any of the ports or doc collections to this file, be sure to
# specify them with a tag value set to ., like this:
#
#   ports-all tag=.
#   doc-all tag=.
#
# If you leave out the tag=. portion, CVSup will delete all of
# the files in your ports or doc tree.  That is because the ports and doc
# collections do not use the same tags as the main part of the FreeBSD
# source tree.
#
###



As far as I know, the ports collection has no tags for any stable
branches, only tags made at the time of releases.  So for ports, if
you are running 8.2-RELEASE, you have three choices: (1) use
RELEASE_8_2_0 if you want to stick with a snapshot of the ports tree
taken at the time of the release, or (2) use . if you want
up-to-date ports, or (3) choose a specific snapshot of ports via date=
instead of tag= (for details, see, for example, the csup(1) manpage.)



 After the build finishes, portupgrade should fetch from 8-stable.

I'm not sure what you mean here.  As I wrote before, you need to make
some additional changes to ensure that portupgrade uses 8-stable
packages if you have an 8.2-RELEASE base system.  Just having a
up-to-date ports tree and index isn't sufficient.  However, if you
replace your 8.2-RELEASE base system with a newer 8.2-STABLE or
8-STABLE base system, then portupgrade should fetch the 8-stable
packages by default, without any additional changes.

You could cheat, and neither upgrade your base system nor make the
changes I mentioned in my last message, but instead fool portupgrade
into thinking that you have a newer base system, by setting UNAME_R to
something like 8.2-STABLE in your environment when you call
portupgrade, but you are bound to run into problems eventually by
lying in that way.

b.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: Portupgrade Package Question

2011-07-09 Thread b. f.

On 7/10/11, b. f. bf1...@googlemail.com wrote:
 On 7/9/11, Thomas D. Dean tomd...@speakeasy.org wrote:
 On Sat, 2011-07-09 at 19:54 -0400, b. f. wrote:

 You could cheat, and neither upgrade your base system nor make the
 changes I mentioned in my last message, but instead fool portupgrade
 into thinking that you have a newer base system, by setting UNAME_R to

Sorry, that should be UNAME_r, with a lower-case r, above.  But,
as I wrote, using that workaround is probably not a good idea.

 something like 8.2-STABLE in your environment when you call
 portupgrade, but you are bound to run into problems eventually by
 lying in that way.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: options used to compile packages

2011-07-16 Thread b. f.

 I want to compile packages from the ports collections with exactly the
 same options that have been used to compile the official packages from
 the official freebsd package collection. Is the var/db/ports directory
 used to compile the official freebsd package collection available
 somewhere ? If not, it would be very good to make it available as ports
 default options seem to be different from options used to compile
 official packages.

As far as I know, the default options are used to compile the standard
packages.  Where did you think that there were differences?  The
official builds use a vanilla ports tree, and the scripts at
http://svnweb.FreeBSD.org/base/projects/portbuild/ .

b.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: gcc 4.4.7

2011-07-16 Thread b. f.

 I decided to switch from portmaster to portupgrade and pkddb -F show many
 stale dependencies on gcc-4.4.5.20110503 (lang/gcc44).

 Do I need to put new dependencies to gcc-4.5.4.20110630 or something else,
 please?
 For portmaster I put IGNOREMI+ line and it works but I don't know how to do
 with portupgrade.

I am not sure what you mean by using +IGNOREME here.  Unless you have
a good reason to use lang/gcc44, you should replace lang/gcc44 with
lang/gcc45, and rebuild or otherwise obtain newer versions of the
packages that formerly used lang/gcc44 at runtime, so that the newer
packages use the libraries from lang/gcc45 at runtime.  The
bookkeeping in the portupgrade database and in /var/db/pkg, and the
updating tool(s) that you choose to use, are relatively minor details.
 If you choose to use portupgrade to do this, you should probably do
something like:

portupgrade -o lang/gcc45 lang/gcc44
portupgrade -rfx lang/gcc45 lang/gcc45

(although it has been a while since I used portupgrade). You may want
to first try the steps with an added -n.

b.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: options used to compile packages

2011-07-16 Thread b. f.

 well I don't actually now which package it was, but I compiled gdm (so
 it should be one of it's dependencies). A compilation resulted in a non
 working gdm (something with pam support not found on execution). Upon
 installing gdm and is dependencies from packages, everything worked
 correctly. Therefore I thought there might be other default options. I
 am sorry that I cannot be more precise, but I tried it 2 months ago, so
 I do not remember exactly. I think I will try it again from scratch with
 latest ports tree and give you more precise information.

In addition to the obvious possibilities that your test was faulty, or
that you somehow polluted your build environment, It is also possible
that:

-at least one of your ports was a different version than used in the
default packages, and had a bug;

-there was a transient build error;

or

-you were using a different version of FreeBSD than that used to build
the default packages that you used, and there is a problem with one of
the ports on that version of FreeBSD.

b.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: options used to compile packages

2011-07-17 Thread b. f.

On 7/17/11, David Arendt ad...@prnet.org wrote:
When I did the test, I used FreeBSD 8.2 amd64 using the ports collection
delivered with this distribution.

I see. Since that time, there have been very few changes to the
version of the base system used to build the packages for 8, but more
to some of the ports that you mentioned, so probably the difference
that you observed is due to the latter, if it isn't caused by some
local change on your own system.

Yesterday I did a checkout of the latest ports tree. I compiled bash,
xorg, xfce and gdm using the default options. When trying to login using
gdm, it still complains about a missing keyring pam module. When I
disable keyring support in gdm, gdm runs flawlessly. Therefore I thought
that options used to compile the offical packages might be different. If
default options are used to compile them, it should be a some other
problem. To ensure that my build environment is not polluted, I did this
test on a fresh installation. But anyway it doesn't matter as I have a
workaround.

If you believe that the error arises from a problem other than your
particular configuration of gdm and its dependencies, or at least is
likely to affect others, then it would be helpful if you submitted a
problem report:

http://www.freebsd.org/send-pr.html

after having first looked to see if a similar problem has already been
reported, via:

http://www.FreeBSD.org/cgi/query-pr-summary.cgi?category=severity=priority=class=state=sort=nonetext=responsible=multitext=pamoriginator=release=

or other searches of your own.

b.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: Using csup and -i switch

2011-07-19 Thread b. f.

 Hello,

 I updated all my ports recently but I have submitted a PR for
 audio/musicpd for a simple patch. I would like to update only my
 audio/musicpd on all my machines so I tried the following:

 markand at Groseille ~ $ sudo csup -i audio/musicpd /etc/ports-supfile
 Connected to 193.51.24.2
 Updating collection ports-all/cvs
 Finished successfully

 According to man csup(1) -i should update only files or directory
 matching the pattern but as you can see here nothing is updated ..


According to csup(1), the patterns used with -i are interpreted
relative to the collection's prefix directory.  Probably, then, you
need to use ports/audio/musicpd as your pattern.

b.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: pkg_delete yields 'no such package'

2011-07-24 Thread b. f.

 Matthew Seaman wrote:
 On 24/07/2011 08:48, Toan H. Le wrote:
  Either I use 'pkg_delete xorg-docs' or 'pkg_delete xorg-docs-1.4.1',
  pkg_delete yields the error of 'no such package'. Checking via 'pkg_info'
  and 'pkg_version' confirms the packages xorg-docs-1.4.1 installed. I think I
  did not use the wrong command.

 Hmmm...  That's a typo.  The package name is:

 lucid-nonsense:...ports/x11/xorg-docs:% make -V PKGNAME
 xorg-docs-1.4,1

 Note the comma -- that's part of the version number, and needs to be
 copied down verbatim for pkg_delete(1)

It is often convenient to use the -x or -X switches with these
utilities, or to use a glob, so that you only have to type part of the
full PKGNAME, e.g.:

pkg_delete xorg-docs\*
pkg_delete -x xorg-docs

Just make sure that the glob or regex that you use only applies to the
packages that you want the utilities to act upon, e.g.:

pkg_info -I xorg-docs\*
pkg_info -Ix xorg-docs

See the manpages of the utilities for details.

b.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: how do i find a file in all directories 7 to 9 days old?

2011-07-28 Thread b. f.

  how can i use find or whatever to find a file, say 6 levels deep
  that is = 9 days old?   i'm looking fo something i had to jt down
  [[ASCII]].  can't remembr te file name, nor when i was when i had
  the idea flash into my mind

Try something like:

find / -type f -mtime -10d -mindepth 5 -maxdepth 7

See find(1) for variations.

b.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: how do i find a file in all directories 7 to 9 days old?

2011-07-28 Thread b. f.

On 7/28/11, b. f. bf1...@googlemail.com wrote:
  how can i use find or whatever to find a file, say 6 levels deep
  that is = 9 days old?   i'm looking fo something i had to jt down
  [[ASCII]].  can't remembr te file name, nor when i was when i had
  the idea flash into my mind

 Try something like:

 find / -type f -mtime -10d -mindepth 5 -maxdepth 7

 See find(1) for variations.

Hmm. I'm not sure owing to the difference between the body and the
subject of the message, what criteria are really wanted, but for the
criteria in the subject you might use something like:

find / -type f -mtime -10d -mtime +6d


b.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: High interrupt rate

2011-08-07 Thread b. f.


 I know 75% idle is not bad but this machine, when not under load on a saturday
 night like today, used to be at around 98% idle 99% of the time. Now its is at
 72% idle 99.9% of the time. It has been like this all day.

 The only things with a high interrupt rate are

 cpu0: timer 46922025   2000
 cpu1: timer 46918117   1999

 What could be causing this?

I don't know that 2 timer interrupts per-cpu, per kern.hz, is
altogether unexpected for some configurations, under some conditions.
What happens if you boot with kern.hz=100 in /boot/loader.conf, or
set via the loader command line?  What happens if you remove the
DEVICE_POLLING option from your kernel (and _not_ just disable polling
per-device)?  What is the output from sysctl kern.timecounter
kern.eventtimer?

b.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: High interrupt rate

2011-08-08 Thread b. f.

On 8/7/11, Mario Lobo l...@bsd.com.br wrote:
 On Sunday 07 August 2011 18:34:27 b. f. wrote:
  I know 75% idle is not bad but this machine, when not under load on a
  saturday night like today, used to be at around 98% idle 99% of the
  time. Now its is at 72% idle 99.9% of the time. It has been like this
  all day.
 
  The only things with a high interrupt rate are
 
  cpu0: timer 46922025   2000
  cpu1: timer 46918117   1999
 
  What could be causing this?

 I don't know that 2 timer interrupts per-cpu, per kern.hz, is
 altogether unexpected for some configurations, under some conditions.
 What happens if you boot with kern.hz=100 in /boot/loader.conf, or
 set via the loader command line?  What happens if you remove the
 DEVICE_POLLING option from your kernel (and _not_ just disable polling
 per-device)?  What is the output from sysctl kern.timecounter
 kern.eventtimer?

 b.

 Thanks b. !

 [~]sysctl kern.timecounter
 kern.timecounter.tick: 1
 kern.timecounter.choice: TSC(-100) ACPI-safe(850) i8254(0) dummy(-100)
 kern.timecounter.hardware: ACPI-safe
 kern.timecounter.stepwarnings: 0
 kern.timecounter.tc.i8254.mask: 65535
 kern.timecounter.tc.i8254.counter: 39201
 kern.timecounter.tc.i8254.frequency: 1193182
 kern.timecounter.tc.i8254.quality: 0
 kern.timecounter.tc.ACPI-safe.mask: 16777215


 kern.timecounter.tc.ACPI-safe.counter: 1055460


 kern.timecounter.tc.ACPI-safe.frequency: 3579545


 kern.timecounter.tc.ACPI-safe.quality: 850


 kern.timecounter.tc.TSC.mask: 4294967295


 kern.timecounter.tc.TSC.counter: 1200011080


 kern.timecounter.tc.TSC.frequency: 1995401152


 kern.timecounter.tc.TSC.quality: -100


 kern.timecounter.smp_tsc: 0


 kern.timecounter.invariant_tsc: 1

 [~]sysctl kern.hz
 kern.hz: 1000

 [~]sysctl kern.eventtimer
 sysctl: unknown oid 'kern.eventtimer'

 I'll wait for your views on those before disabling polling on the kernel and
 hz=100.

It looks like your interrupt rate, while probably higher than needed,
is not unexpectedly high for your configuration.  But you can lower it
if you want to do so.

You are using a system before the introduction of the new eventtimer
code.  If you use 9.x, that has the new code and some other
timer-related improvements, and you are not performing polling, then
you can achieve a large reduction in the number of timer interrupts
when the system isn't busy. You can still achieve a reduction on 8.x,
but the reduction usually won't be as large as on 9.x under similar
conditions.

To reduce timer interrupts on an idle system running 8.x or 9.x, if
you do not need to poll (most systems do not), remove  DEVICE_POLLING
from your kernel, and lower kern.hz to a suitable value -- 100 or 250,
for example. For many workloads, a lower value is not only adequate,
but may also be better in some ways.

Also, you may want to consider using your TSC as the system
timecounter, because it is usually more efficient to do so.  This may
not work for SMP, because if there are multiple TSCs on your system,
they may not be synchronized.  In 9.x, there is a test for
synchronization, and the TSCs are preferred to the ACPI-safe timer if
they satisfy this test and meet some other requirements.  In 8.x, the
user has to tell the system that it is safe to use the TSCs by adding:

kern.timecounter.smp_tsc=1

to /boot/loader.conf.  If you are not putting your cores into the C3
state, then you could try setting this via the loader command line,
booting, and then seeing if the kern.timecounter.tc.TSC.quality is
positive, kern.timecounter.hardware is TSC, and everything is working
as expected.  If the results are satisfactory, then you could add the
above entry to /boot/loader.conf.  But it would be better to do this
on 9.x, where there are some added safeguards.

b.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: port build breaks at xmlto

2011-08-12 Thread b. f.

On Fri, Aug 12, 2011 at 01:18:07PM +1000, Daryl Sayers wrote:


 FreeBSD 7.4
 I am having trouble building the xmlto port on FreeBSD 7.4. I am getting an
 error:

 ===  Building for xmlto-0.0.24
 make  all-am
 for xml in xmlif.xml xmlto.xml; do  FORMAT_DIR=./format  /usr/local/bin/bash 
 ./xmlto -o man/man1 man ./doc/$xml ;  done || ( RC=$?; exit $RC )
 xmlto: /usr/ports/textproc/xmlto/work/xmlto-0.0.24/./doc/xmlif.xml does not 
 validate (status 3)
 xmlto: Fix document syntax or use --skip-validation option
 I/O error : Attempt to load network entity 
 http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd
 /usr/ports/textproc/xmlto/work/xmlto-0.0.24/./doc/xmlif.xml:4: warning: 
 failed to load external entity 
 http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd;
http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd;
 

xmlto should be using /usr/local/share/xml/docbook/4.2/docbookx.dtd,
which should be installed by the build dependency
textproc/docbook-xml, but instead is trying to fetch this file from a
remote location, and failing.  Check to see if this file is present,
and intact.  If it isn't, then reinstall textproc/docbook-xml. You
could look at the file (and compare it to the reference file from the
remote location), and the output of pkg_info -ag, to see if anything
is corrupted.



 After alot of frustration I decided to throw everything away and start again:

 # pkg_delete -a

Okay, you've instructed the system to delete the registered files and
directories in the step above -- but is any garbage left in /usr/local
afterward?  After the above step, you should check to see that
/usr/local only contains files that you have placed there, and that
won't interfere with new port installations.


 # cd /usr/ports; rm -fr *
 # csup -h cvsup.au.FreeBSD.org /usr/share/examples/cvsup/ports-supfile
 # cd /usr/ports/textproc/xmlto
 # make

Usually, it's a good idea to perform make deinstall-all clean all
(in that order), although in this case it should not have made a
difference for the first build, if you had succeeded in cleaning
/usr/local and /usr/ports.


 Using the defaults when the config screens appear. As there are now no 
 packages
 installed and the ports tree is brand new there should be no problems but in
 the end it still fails with the same message. My /etc/make.conf is empty also.

 Why cant I build this package.

This port was built on July 17 on the build cluster with 7.3-RELEASE-p4:

http://pointyhat.freebsd.org/errorlogs/amd64-7-latest-logs/xmlto-0.0.24.log

so while there may be a bug in the port, or in one of its
dependencies, it is more probable that your build is polluted.  If you
don't want to use a binary package downloaded from the server, then
you'll have to be patient, and break down the build until you find the
precise location where it is failing, even though that is a nuisance.
A complete build transcript and config.log would help.

b.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: PDF inventory software

2009-06-10 Thread b. f.

Hmm.. The command

find *.pdf -exec pdftotext {} \;

works in directories in which no PDF file returns the Document has
not the mandatory ending %EOF error.  When a directory contains one
of these files, none of the files get converted.  Is there some way to
ignore or skip over this %EOF problem and continue operating on the
remaining PDFs?

Use something like:

find -X DIR -name '*.[pP][dD][fF]' | xargs -I % pdftotext %

where DIR is the root of the filesystem directory hierarchy to be searched.
Be careful of how many arguments you feed to pdftotext: it can overwrite
files.  You may need to handle some files with encryption, etc. differently.

b.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: OpenSSL Base vs. OpenSSL Port?

I had been running 6.2 with openssl base for quite a while. Then I
attempted to implement the dkim-filter port which required using openssl
to generate keys.  That's when I noticed that openssl is broken on my
machine.  See this example:

# openssl genrsa -out rsa.private 1024
Error configuring OpenSSL
28086:error:260AB089:engine routines:ENGINE_ctrl_cmd_string:invalid cmd
name:/usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/engine/eng_ctrl.c:318:
28086:error:0E07406D:configuration file
routines:CONF_modules_load:module initialization
error:/usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto
/conf/conf_mod.c:234:module=engines,
value=openssl_engines, retcode=-1

So I thought rebuilding world might fix it and while I was at it, I
upgraded to 6.4 but still have the same problem.

I'm not familiar with this problem.  If you have the a supported version of 6.X
installed, and you've read the documentation, and are convinced that the error
is due to some problem with the openssl in base, then you should submit a PR:

http://www.freebsd.org/support/bugreports.html


Next I tried installing openssl from ports.  This openssl seems to work:

# /usr/local/bin/openssl genrsa -out rsa.private 1024
Generating RSA private key, 1024 bit long modulus
..++
..++
e is 65537 (0x10001)

But now I am unclear as to what state my system is in.  What is the
preferred method for using openssl from ports vs. using openssl base.  I
don't really care which I use but want to avoid trouble with multiple
versions of openssl and/or ports compiled against the wrong version.
I've been Googling all day but can not find a clear guide.

No need to waste time googling -- just go straight to the code, the
port makefiles
on your system that actually _do_ the work -- in this case
/usr/ports/Mk/bsd.openssl.mk
(or substitute the value of PORTSDIR for /usr/ports if you've got your
Ports tree in some
nondefault location). There you will see some comments and the actual code
governing the use of the variables.

Specifically, what should I have in my /etc/make.conf and what
portupgrade command should I use to ensure things are build against the
correct openssl?  I've seen things like OPENSSL_OVERWRITE_BASE=yes,
NO_OPENSSL=yes, WITH_OPENSSL_PORT=yes, WITH_OPENSSL_BETA=yes, and
portupgrade -rf openssl but remain confused.

Put WITH_OPENSSL_PORT=yes in your build environment -- /etc/make.conf is a good
way -- and then rebuild all ports that depend on openssl.  There are
many different
ways to do this -- you could use:

pkgdb -L  portupgrade -fur openssl-*

(The first command may not be necessary, but I find that the
dependencies of some
ports on openssl are sometimes missing from the pkgdb, and need to be added.)

or

portmaster -t -r openssl-*

for example.  Note that this will only ensure that ports that correctly use
USE_OPENSSL are linked to the proper version of openssl -- some ports may
not have been constructed properly, and may still end up being linked
to the base
openssl.  You can check if there are any such ports by using ldd(1) or
the sysutils/libchk
port.


b.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: OpenSSL Base vs. OpenSSL Port?

On 6/17/09, b. f. bf1...@googlemail.com wrote:

 Put WITH_OPENSSL_PORT=yes in your build environment -- /etc/make.conf is a
 good
 way -- and then rebuild all ports that depend on openssl.  There are
 many different
 ways to do this -- you could use:

 pkgdb -L  portupgrade -fur openssl-*

 (The first command may not be necessary, but I find that the
 dependencies of some
 ports on openssl are sometimes missing from the pkgdb, and need to be
 added.)

 or

 portmaster -t -r openssl-*


I should mention that if you are switching from using the base openssl to using
the openssl from the port, and you intend to use portupgrade, then you
will definitely
need to to run pkgdb -L  pkgdb -F before running portupgrade,
because otherwise
no ports will be listed as being dependent upon the openssl port.

I'm not sure if portmaster will do this properly, as it uses the
existing /var/db/pkg in
many cases, which will not contain the correct dependency information.
You may need to
get a list of ports that USE_OPENSSL, and then update those ports and
the ports that
depend upon them.  For example, you could first install the openssl
port, and then use:

pkg_info -aoq | xargs -I % make -C /usr/ports/% -V USE_OPENSSL -V
PKGNAME | sed -n '/[yY][eE][sS]/{n;p;}' | xargs portmaster -t -r

or something like that.

b.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: OpenSSL Base vs. OpenSSL Port?

On 6/17/09, b. f. bf1...@googlemail.com wrote:
 On 6/17/09, b. f. bf1...@googlemail.com wrote:

 Put WITH_OPENSSL_PORT=yes in your build environment -- /etc/make.conf is
 a
 good
 way -- and then rebuild all ports that depend on openssl.  There are
 many different
 ways to do this -- you could use:

 pkgdb -L  portupgrade -fur openssl-*

 (The first command may not be necessary, but I find that the
 dependencies of some
 ports on openssl are sometimes missing from the pkgdb, and need to be
 added.)

 or

 portmaster -t -r openssl-*


 I should mention that if you are switching from using the base openssl to
 using
 the openssl from the port, and you intend to use portupgrade, then you
 will definitely
 need to to run pkgdb -L  pkgdb -F before running portupgrade,
 because otherwise
 no ports will be listed as being dependent upon the openssl port.

 I'm not sure if portmaster will do this properly, as it uses the
 existing /var/db/pkg in
 many cases, which will not contain the correct dependency information.
 You may need to
 get a list of ports that USE_OPENSSL, and then update those ports and
 the ports that
 depend upon them.  For example, you could first install the openssl
 port, and then use:

 pkg_info -aoq | xargs -I % make -C /usr/ports/% -V USE_OPENSSL -V
 PKGNAME | sed -n '/[yY][eE][sS]/{n;p;}' | xargs portmaster -t -r

 or something like that.

 b.

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

Re: OpenSSL Base vs. OpenSSL Port?

On 6/17/09, b. f. bf1...@googlemail.com wrote:
 On 6/17/09, b. f. bf1...@googlemail.com wrote:

 Put WITH_OPENSSL_PORT=yes in your build environment -- /etc/make.conf is
 a
 good
 way -- and then rebuild all ports that depend on openssl.  There are
 many different
 ways to do this -- you could use:

 pkgdb -L  portupgrade -fur openssl-*

 (The first command may not be necessary, but I find that the
 dependencies of some
 ports on openssl are sometimes missing from the pkgdb, and need to be
 added.)

 or

 portmaster -t -r openssl-*


 I should mention that if you are switching from using the base openssl to
 using
 the openssl from the port, and you intend to use portupgrade, then you
 will definitely
 need to to run pkgdb -L  pkgdb -F before running portupgrade,
 because otherwise
 no ports will be listed as being dependent upon the openssl port.

 I'm not sure if portmaster will do this properly, as it uses the
 existing /var/db/pkg in
 many cases, which will not contain the correct dependency information.
 You may need to
 get a list of ports that USE_OPENSSL, and then update those ports and
 the ports that
 depend upon them.  For example, you could first install the openssl
 port, and then use:

 pkg_info -aoq | xargs -I % make -C /usr/ports/% -V USE_OPENSSL -V
 PKGNAME | sed -n '/[yY][eE][sS]/{n;p;}' | xargs portmaster -t -r

 or something like that.

 b.


Argh. Sorry about the last (non-)message.  I meant to say:

Or rather, since (portmaster -r only accepts a single port as an
argument -- _sigh_ ) :

pkg_info -aoq | xargs -I % make -C /usr/ports/% -V USE_OPENSSL -V
PKGNAME | sed -n '/[yY][eE][sS]/{n;p;}' | xargs portmaster -f

which is thorough, but overkill. I'd stick with portupgrade or manual
'make deinstall clean install  make clean' for this task.

b.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: right CPUTYPE

2009-06-18 Thread b. f.

On Thu, Jun 18, 2009 at 8:08 PM, Aryeh Friedmanaryeh.friedman at
gmail.com wrote:
 What CPUTYPE should I put in /etc/make.conf for:

 CPU: AMD Phenom(tm) II X4 955 Processor (3210.85-MHz 686-class CPU)

OP is referring to CPUTYPE ( see make.conf(5) ) , not the cpu string
in the kernel configuration file, so HAMMER isn't a valid choice.  It
depends on what compiler
you are using: if you are using the base compiler, which is a patched
version of gcc 4.2,  I think that you want:

CPUTYPE=athlon64

But if you're using gcc = 4.3, with the right toolchain, or llvm, you
may be able to use the newer:

CPUTYPE=amdfam10

to take advantage of your CPU's newer instruction sets. As someone
said, the effect this will have in compiling may be different when you
are using FreeBSD i386 as opposed to FreeBSD amd64.


b.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: The question of moving vi to /bin

2009-06-24 Thread b. f.

 On Tuesday 23 June 2009 15:41:48 Manish Jain wrote:

...

About ed first. I might annoy a few people (which would gladden me in
this particular case), but ed was just one of Ken Thompson's nightmares
which he managed to reproduce in Unix with great precision. By no
stretch of imagination would it qualify as an editor, because an editor
can meaningfully edit only what it can first show. And ed has never had
anything to show. A modern operating system like FreeBSD should really
be kicking ed out of the distribution completely : bad ideas don't have
to be necessarily perpetuated just for the sake of compliance with the
original concept of Unix.

If you want to make a case for replacing ed(1), you're going to have
to come up with some concrete reasons for doing so, not just make a
(long and hyperbolic) statement that you don't like it.

...

That's the whole problem of /rescue/vi. When you suddenly find yourself
in single-user mode, the last thing you want to do is realise that
tweaking is needed for something which should work normally just when
you need it, and quickly too.

Yes.  But there have been some recent changes:

http://svn.freebsd.org/changeset/base/194628

that suggest that this problem is being addressed.

...

But why are we talking about a few hundred
kilos for such a basic utility as vi in times when everyone has hundreds
of GB's on the disk, and the / partition itself is 512 MB by default.
The BSD concept of having vi under /usr originated when resources were
less by a factor of thousands (= (100 MB disks), = (8 MB physical RAM)
and so on). When we are well past those kind of constraints, the concept
needs an rethink.

No, we're not.  A lot of people are still using old hardware, or
embedded hardware, where efficiency in space and computational effort
are still important, and will remain so for a while.  Please don't
encourage bloat.

...

Actually, there is an even more radical update that I would have loved
FreeBSD to have initiated. Instead, the credit has gone to Microsoft.
The simple thing is when a system has multiple gigabytes of RAM, the OS
should be able give an option to the user of completely doing away with
swapping and force all the action in real, physical memory instead.

??? Who is giving them that credit?  This isn't new.  You already have
some control over swapping via several oids:

vm.swap_enabled
vm.disable_swapspace_pageouts
vm.defer_swapspace_pageouts
vm.swap_idle_enabled
vm.swap_idle_threshold1
vm.swap_idle_threshold2
etc.

See, for example, tuning(7).  These have been around for ages (well,
at least since June 1996).  You can also build your kernel with:

options NO_SWAPPING

which takes precedence over these settings.  That option has been
around even longer. Linux has corresponding features, although they
didn't always work well on older kernels.

More recently, kib@ has just committed some changes that allow for
finer control of swapping, and, in the opposite direction, anonymous
memory,  in his overcommit patches:

http://svn.freebsd.org/changeset/base/194766
http://svn.freebsd.org/changeset/base/194767
http://people.freebsd.org/~kib/overcommit/


b.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: Questions on portmaster

2009-07-01 Thread b. f.

Manish Jain wrote:
...Does each child start 'make fetch' in the background ?

make checksum, yes.

Further, how can portmaster be tuned to automatically ignore ports which
are actually marked as IGNORE in the port directory ? This is not
covered in the manpage.

It respects IGNORE (it checks for it in the port Makefile, and also
hands off to bsd.port.mk, which respects it).   If you mean +IGNOREME,
the others have answered your question.

While doing portmaster -a, I have only managed to stop portmaster from
building exactly one port specified with the -x option. Can I get to
stop multiple ports from being built ? Is there regular expression
support for the -x option ?

Not in the sense that you mean, at least that I'm aware of.  This one
of the things that needs improvement.  It is a bit awkward, because it
uses the shell's built-in POSIX getopts to parse options, and then
calls itself recursively.  One way you could fix it would be to apply
a patch like:

--- portmaster.orig 2009-07-01 12:36:14.0 -0400
+++ portmaster  2009-07-01 18:55:59.0 -0400
@@ -9,7 +9,7 @@
 if [ -z $PARENT_PID ]; then
PARENT_PID=$$
: ${TMPDIR:=/tmp}
-   UPGRADE_TOOL=portmaster
+   UPGRADE_TOOL=$0

# /usr/local is needed in the path for make
PATH=/bin:/usr/bin:/sbin:/usr/sbin:/usr/local/bin:/usr/local/sbin
@@ -788,7 +788,11 @@
u)  UNATTENDED=uopt; ARGS=-u $ARGS ;;
v)  PM_VERBOSE=vopt; ARGS=-v $ARGS ;;
w)  SAVE_SHARED=wopt; ARGS=-w $ARGS ;;
-   x)  EXCL=$OPTARG ;;
+   x)  if [ -z ${OPTARG%%-*} ]; then
+   fail 'The -x option requires an argument'
+   else
+   EXCL=-x $OPTARG $EXCL
+   fi ;;
*)  echo '' ; echo === Try ${0##*/} --help; exit 1 ;;
esac
 done
@@ -810,10 +814,7 @@
 [ -n $FETCH_ONLY -a -n $NO_RECURSIVE_CONFIG ] 
fail The -F and -G options are mutually exclusive
 if [ -n $EXCL ]; then
-   case $EXCL in
-   -*) fail 'The -x option requires an argument' ;;
-   *)  ARGS=-x $EXCL $ARGS ;;
-   esac
+   ARGS=$EXCL $ARGS
 fi

 #=== Begin functions for getopts features and main ===
@@ -1461,14 +1462,17 @@
 check_exclude () {
[ -n $EXCL ] || return 0

-   case $1 in
-   *${EXCL}*)
-   if [ -n $PM_VERBOSE ]; then
-   echo === Skipping $1
-   echobecause it matches the pattern: *${EXCL}*
-   fi
-   return 1 ;;
-   esac
+   for pkgglob in `echo $EXCL | sed -e 's#-x##g'`
+   do
+   case $1 in
+   *${pkgglob}*)
+   if [ -n $PM_VERBOSE ]; then
+   echo === Skipping $1
+   echobecause it matches the pattern:
*${pkgglob}*
+   fi
+   return 1 ;;
+   esac ;
+   done
return 0
 }


(Mind the whitespace because of my MUA.)  Then you could just use
repeated -x flags, each with one and only one package glob that you
wanted to exclude.  I changed the definition of UPGRADE_TOOL so that
you could put this script in your path under another name, say
jainpmaster, and then call it independently of the original
portmaster.  As usual, I make no claim that this is the best, only, or
most elegant way to do this.

Regards,
b.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: Questions on portmaster

2009-07-02 Thread b. f.

On 7/2/09, Manish Jain invalid.poin...@gmail.com wrote:
 b. f. wrote:
 Manish Jain wrote:

 Regarding the download speeds I was getting with portmaster fetches (0.7
 kBps to 4.0 kBps), I immediately booted into Windows/Cygwin and did a
 wget from the same site portmaster was using. The speed I got from wget
 was ~ 35 kBps. This happened not just once but multiple times. Each time
 I did this, I had to interrupt portmaster. Finally I managed to get to
 install the wget port on FreeBSD itself. When I ran wget from FreeBSD,
 it reported comparable transfer rates (~ 35 kBps) from the same sites as
 portmaster was using.


This has nothing to do with portmaster.  Remember, portmaster is just
a (sometimes) convenient shell script wrapper for the normal ports
infrastructure.  What you're probably seeing is either the usual
fluctuations in network performance, or the difference between wget
and FreeBSD fetch(1), which by default is used for getting distfiles
and packages.  This is set in bsd.port.mk, and you can override it if
you prefer to use something else.  See the comments concerning
FETCH_BINARY, FETCH_ARGS, FETCH_CMD, FETCH_{BEFORE,AFTER}_ARGS,
FETCH_ENV, and FETCH_REGET at the top of bsd.port.mk, or the relevant
portion of that script.  You can also try tuning your network
settings, which can speed things up significantly in some cases.

 It respects IGNORE (it checks for it in the port Makefile, and also
 hands off to bsd.port.mk, which respects it).

 I got a curl port from portsnap marked IGNORE. portmaster did not ignore
 it anywhere near gracefully enough and finally killed off all child
 processes and itself.


Uh, yeah -- but that's another matter.  It did IGNORE it, but it just
stopped entirely.  This is another one of the things that need
improvement.  portupgrade, by contrast, will keep going, only ignoring
the port in question and any ports that depend upon it, but updating
the rest.  You should be able to patch portmaster to mimic this
behavior.

 Anyway, my system became so unpredictable that I had to reinstall
 FreeBSD. For the moment, I am avoiding portmaster till I can try it out
 on a dummy PC first.


Well, something is awry if your system was damaged that badly, and it
probably wasn't because of portmaster.  In general, few ports ought to
damage the base system.  You're probably better off trying to remove
and then reinstall all of your ports first (the instructions in the
portmaster manpage are good in this regard), before reinstalling
everything.

 BTW, I also tried portmanager and it segfaulted at the stage of
 generating a report.


Oh, well.  Sounds like a job for  rnol...@freebsd.org. But wait --
 who wants to bother him about some tiny piece of port management
software when he is heroically staging a single-handed campaign to
maintain X11 on FreeBSD?

b.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: Urgent help needed : portmaster dies on py-cairo

2009-07-05 Thread b. f.

Manish Jain wrote:

After 3-4 hours, portsnap died on graphics/py-cairo saying :
cannot find python headers

I'm guessing you meant portmaster died here ...

/usr/ports/graphics/py-cairo/work/pycairo-1.8.4/config.log says :
configure:4734: cc -E -I/usr/local/include conftest.c
conftest.c:10:28: error: ac_nonexistent.h: No such file or directory
configure:4741: $? = 1


cd /usr
find . -name 'ac_nonexistent.h'
#no results

As the name suggests, this header doesn't really exist.  It's just a
dummy header used during a test in the configure script to see how the
compiler reacts when a header isn't there, in preparation for testing
for the presence of real headers.  That shouldn't be the problem: are
you sure the configure script really failed at that point?  If so,
something is probably wrong with your compiler or toolchain, and
that's usually bad news. :(

py-cairo-1.8.4 needs python2.6. My system has both python2.5 and
python2.6 installed, with their headers under
/usr/local/include/python2.5 and /usr/local/include/python2.6
respectively.

Why do you have both versions installed?  2.6 is  largely
backwards-compatible with 2.5, so why not just rip out 2.5 and use 2.6
exclusively?  You'll save some trouble and disk space. Make sure your
ports tree is up-to-date, so that PYTHON_DEFAULT_VERSION defaults to
python2.6.  Then deinstall lang/python25 and reinstall lang/python26.
In particular, check to see that /usr/local/bin/python is present is a
link to /usr/local/bin/python2.6.  If it isn't, then something is
wrong -- perhaps you have PYTHON_VERSION or PYTHON_DEFAULT_VERSION
defined to the wrong value, or your ports tree is corrupt.  Then
rebuild all of the ports that depend upon python, and remove any
vestige of the old /usr/local/lib/python2.5 directory tree. If you've
stale ports that are still wired to use python2.5 for no good reason,
you can patch them or their port Makefiles, or put a workaround in
make.conf.

Any help on enabling py-cairo locate the python headers would be
greatly appreciated.

What is the output of:

make -C /usr/ports/graphics/py-cairo -V CONFIGURE_ENV

If PYTHON is in there, properly defined as the path to the python2.6
binary, and the binary actually exists, then the configure script
should succeed. If not, something is wrong.  The configure script
uses:

PYTHON_INCLUDES=`$PYTHON-config --includes 2/dev/null` to find the
proper Python.h.  Is /usr/local/bin/python2.6-config missing or broken
on your system?  What about /usr/local/include/python2.6/Python.h?

b.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: Urgent help needed : portmaster dies on py-cairo

2009-07-06 Thread b. f.

On 7/6/09, manish jain invalid.poin...@gmail.com wrote:
 2009/7/6 b. f. bf1...@googlemail.com


 After running pkgdb -F, I find that there hundreds of ports depending on
 python2.5.

Most of these are probably indirectly dependent, and may not be
seriously affected.  Many, for example, may have been dragged in by
xorg's silly dependency on python via libxcb.

Looks to me it will be easier to backup my dstfiles and reinstall
 the whole system afresh a 3rd time rather than trying to fix the existing
 ports. This time I will install no packages from the installation media, and
 build directly from ports instead. The first 2 ports I will build this time
 will be lang/python26 followed by lang/python.

Sounds good.

 I suppose this should set the
 systemwide default python version to 2.6.

As the others have mentioned, you don't need to do this unless you
wish to use a version of python other than 2.6, which is now the
default.


 1) How do I find or set  PYTHON_DEFAULT_VERSION ?
 2) What workaround would be needed in make.conf to get 2.5-hardwired ports
 to use 2.6 instead ?

1) See above.
2) I didn't mean, as Seaman seemed to think, and you may have, that
you can use ports built against 2.5 with 2.6.  That would only rarely
work, and most likely lead to all sorts of problems. Instead you
should proceed with your plan, and rebuild all dependent ports via:

pkgdb -L
pkgdb -F
portupgrade -fvrx lang/python26 lang/python26
rm -r /usr/local/lib/python2.5

or rebuild just that subset of ports that are most likely to be broken
by the change, via the upgrade-site-packages target in lang/python, as
Seaman suggested.

What I meant by my original comment was, that if you should happen to
want to build a port against 2.6, but find that it is hardwired in the
port Makefile via USE_PYTHON to another version or versions, and you
don't want to go to the trouble of patching the port Makefile, and
then preserving this local modification when you merge in updates to
the port tree, you can add a workaround in /etc/make.conf.  Say, for
example, you see that mail/py-spambayes has:

USE_PYTHON= -2.5

in the port Makefile, and you want to install spambayes, but you don't
want to have to reinstall python 2.5 or an earlier version of python.
If you add:

.if${.CURDIR:M*/mail/py-spambayes*}
PYTHON_VERSION=python2.6
NO_IGNORE=yes
.endif

to /etc/make.conf, you can override the spambayes port Makefile
without patching it.  Now, you are _not_ supposed to do this, and you
will probably have to deal with any consequences of such a local
change on your own.  Many ports have these restrictions for a good
reason, but such an override can be occasionally useful.

b.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: Portupgrade not handling dependencies

For the past 2 weeks though I have to run portupgrade 2-3 times every
time I have more than one update because at least 1 port fails due to a
dependency(which is seemingly upgraded after it tries to upgrade the
other port).  What the heck is going on and how do I fix it?

We obviously can't help you without more information.  What ports are
failing?  What are the dependencies that are out of sequence?  What
OPTIONS are you using with all of these?  Have you overidden anything
via pkgtools.conf?  Is you ports tree up-to-date, and intact?

b.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: Portupgrade not handling dependencies

On 7/8/09, Eric Sheesley eshee...@shadowlair.com wrote:
 Well, it has been happening with just about every port(no specific ones)
 that have a dependency which is also being built.  An example from today:

 ===   Registering installation for libtheora-1.0_1
 ===  Cleaning for libtheora-1.0_1
 ---  Cleaning out obsolete shared libraries
 [Updating the pkgdb format:bdb_btree in /var/db/pkg ... - 456 packages
 found (-0 +1) . done]
 ---  Skipping 'multimedia/ffmpeg' (ffmpeg-2008.07.27_10) because a
 requisite package 'libtheora-1.0' () failed (specify -k to force)
 ** Listing the failed packages (-:ignored / *:skipped / !:failed)
 -  (bsdpan-Acme-Damn-0.04)
 * multimedia/ffmpeg (ffmpeg-2008.07.27_10)
 %portupgrade -a
 ---  Skipping 'bsdpan-Acme-Damn-0.04' because it is held by user
 (specify -f to force)
 ---  Upgrading 'ffmpeg-2008.07.27_10' to 'ffmpeg-2008.07.27_11'
 (multimedia/ffmpeg)
 ---  Building '/usr/ports/multimedia/ffmpeg'


I see.  In the default /usr/local/etc/pkgtools.conf, there is a sample
line (not commented out) that places any port that matches the glob
bsdpan-* in HOLD_PKGS, meaning that portupgrade will refuse to handle
it.  Presumably this is so users can manage their own local tree of
Perl ports that aren't in the regular ports tree.  I don't do this, so
I'm not familiar with how the two interact.  But portupgrade seems to
have done the right thing here: in the snippet you gave us, it ignored
bsdpan-Acme-Damn and proceeded to begin building ffmpeg after updating
libtheora -- the only problem seems to be that in the intermediate
summary it lists ffmpeg, erroneously, as having been skipped -- but
that seems to just be a cosmetic problem, because it then proceeds to
start updating it.  If later on it refuses to update it, then you've
got a problem.  In that case, you should try running

pkgdb -L
pkgdb -F

to make sure that your pkgdb is in good shape, and then try your
updates again.  You might also try instead something like:

portupgrade -ax bsdpan-*

If that doesn't work, then you may either have to rip out your
bsdpan-* ports, or just use a another tool for updating -- portmaster,
for example.  Or you can roll your own.


b.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: Portupgrade not handling dependencies

On 7/8/09, Eric Sheesley eshee...@shadowlair.com wrote:
 Actually, the bsdpan package is not the issue here.  I was aware it
 wouldn't update that(no port for this perl module yet anyway).

 If you notice, it doesn't proceed to install ffmpeg, i force it
 to(highlighted by ):


Yes, I was too hasty.  So this happens with ports other than
libtheora, ports that you have no problem installing manually, with
make deinstall  make clean install  make clean? And there is never
any descriptive message given?  Unknown Build Error or Unknown
Install Error or the like?  If so, you could try forcibly rebuilding
portupgrade and it's dependencies, and see if that fixes the problem.
If it doesn't, and you think that your ports tree and INDEX file are
okay, there may be a problem with your package database -- /var/db/pkg
by default.  In which case you may have to clean everything out and
rebuild, if you can't find the problem.  There have been other
problems reported with portupgrade, but it works fine for me, so I
think the issue is peculiar to your system.

b.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: Portupgrade not handling dependencies