Re: Running an Old Kernel

2010-06-25 Thread b. f.
On 6/25/10, b. f. bf1...@googlemail.com wrote:
 On 6/25/10, b. f. bf1...@googlemail.com wrote:
 Martin McCormick wrote:
 I have been attempting to shut off that last login message
 that occurs on some FreeBSD systems every time one runs a sudo
 command. I decided to bring back the last kernel which was the
 ...
 Why on earth are you tinkering with your kernels in order to change
 sudo output?  You should instead be editing configuration files
 associated with sudo and related base system utilities, or patching
 sudo.

 I should be more specific: I think you should be able to disable the
 message by commenting out the lines that refer to pam_lastlog.so in
 /etc/pam.d/system, /etc/pam.d/xdm, and /etc/pam.d/telnetd.  But in
 doing so, you will lose some of the security and accounting benefits
 of last(1) and friends.  Is it really worth it, just to silence some
 console messages? In any event, don't tinker with your kernel because
 of this.  It won't help, and it may break your system.

Looking at Matthew Seaman's earlier response, I find that his
suggestion to make  changes to ${PREFIX}/etc/pam.d/sudo is more
appropriate than my guess above.  But you probably need to look into
the details, because judging from the comments in the
${PREFIX}/etc/pam.d/sudo.default file, there seems to be some
subtleties involving sudo and pam_lastlog.  Look at the pertinent
manpages, the sudo docs, and:

http://www.freebsd.org/doc/en/articles/pam/index.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: Bourne .sh ?

2010-07-01 Thread b. f.
I have a file containing this

drwxrwxr-x  14 89987  546  512 Jun  6  2009 7.2-RELEASE
drwxrwxr-x  14 89987  546  512 Mar 23 04:59 7.3-RELEASE
drwxrwxr-x  13 89987  546  512 Nov 23  2009 8.0-RELEASE
drwxrwxr-x  13 89987  546  512 Jul  1 04:56 8.1-RC2

I want to strip off everything to the left of the release
version so I end up with this.

7.2-RELEASE
7.3-RELEASE
8.0-RELEASE
8.1-RC2

How would I code to do this?

By using something like:

awk '{print $9}' nameofmyfile

(Or whatever column it is, if not the ninth.)  Or you can use sed(1).
Or cut(1).  Or colrm(1)...

I'd recommend first reading some of the base system manpages, and
tutorials on basic text processing tools and shell programming than
can be found in many places on the web, before addressing a lot of
questions like this to a FreeBSD-specific list.

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: how to setenv using Bourne .sh

2010-07-10 Thread b. f.
Polytropon wrote:
On Sat, 10 Jul 2010 10:53:17 +0800, Aiza aiza21 at comclark.com wrote:
 Trying the set the pkg_add environment variable PKGDIR using this


 setenv PKGDIR=/usr/packages  and get this error message
 setenv: Syntax Error.

Of course. The sh shell doesn't have setenv.

It looks like he is actually using csh, because in the Bourne shell
issuing that command usually yields setenv: not found.  His problem
is that, unlike export,  setenv doesn't take an = between the
variable and the value to be assigned to it.  See csh(1).

 man setenv is useless.

The manual entry of setenv can be found in man csh. :-)

When you are directed to builtin(1), it usually means that you should
refer to the manpage(s) of the shell that you are using for the
information that you need.

 The question is how do I set a environment variable using the default
 freebsd shell?

You mean: FreeBSD's default scripting shell. :-)

He could mean the default interactive shell, which could be something
other than sh(1), despite the title of his message.  As an alternative
to export or setenv, he could instead use env(1) in some
instances.

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: Headphone output doesn't work with NVidia MCP78 High Definition Audio Controller

2010-07-11 Thread b. f.
I use a laptop with PC-BSD and couldn't get output over the headphone.
The built-in speakers of the laptop work fine and keep working even
when a headphone is plugged in (whereas on Windows they get muted). I
tried every slider and switch in KMix, but nothing enables sound over
the headphone.

You need to look at the sound-related dmesg output from a verbose
boot, or a boot with hw.snd.verbose=4.  Then you can look at some of
the suggestions in snd_hda(4): you may be able to get the headphones
to work by adding the appropriate device.hints(5) as described in
snd_hda(4) manpage.

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: Har

2010-07-11 Thread b. f.
My hdd is using UDMA33 under PC-BSD (which uses a FreeBSD kernel). The
Nvidia SATA chipset seems to be detected, but isn't used! I hope this
is easily solvable because my laptop becomes really slow when the hdd
is used now.

It seems to be using UDMA133, which isn't all _that_ slow.  :)  But of
course SATA would be better, especially if your chipset supports
features like NCQ.  In order to use SATA:

(a) hardware and your BIOS have to support AHCI (because the FreeBSD
developers haven't taken the time to support most SATA hardware that
uses proprietary non-AHCI interfaces);
(b) your kernel has to contain the ahci(4) driver (or the older ata(4)
drivers that have been built with the ATA_CAM kernel option); and
(c) your hardware has to be recognized by these drivers.

You can look at your BIOS setup to try to see if AHCI is enabled, or
talk to the manufacturer.  You can check the output of kldstat -v or
talk to the PC-BSD support team to see if you have the proper drivers.
 And you can look at the output of pciconf -lv to check information
about your hardware, and look at the subclass field, or compare the
chip numbers to the list of supported hardware in the source code of
the drivers, like:

/usr/src/sys/dev/ahci/ahci.c
/usr/src/sys/dev/ata/chipsets/ata-nvidia.c

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: os that rather uses the gpu?

2010-07-13 Thread b. f.
 On Tue, 13 Jul 2010 22:46:15 +0200
 Jozsi Avadkan jozsi.avadkan at gmail.com wrote:

  Does someone know a distribution/operating system, that rather uses
  the GPU for working, not the CPU? [by default]

Not exclusively, no.  But there are developments, still mostly in the
research stage, for software allowing heterogeneous computing
platforms of CPUs and GPUs to offload more work onto the GPUs; and
there are some experimental architectures, like Intel Larrabee, that
are CPU/GPU hybrids.

See, for example:

http://en.wikipedia.org/wiki/GPGPU
http://en.wikipedia.org/wiki/Larrabee_(microarchitecture)


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: login.conf: passwordtime not enforced?

2010-07-13 Thread b. f.
after reading some docs about hardening freebsd installations, I
 decided to enforce password expiration after 90days. I've added the
 corresponding line to /etc/login.conf and ... after quite some time
 (way more than 3 months already!) nothing happens ...

If you want help, you'll have to be more specific.  Exactly what
changes did you make to login.conf, in what sections?  Did you run
'cap_mkdb /etc/login.conf' afterwards?  Did you then reset your
account passwords and check the sixth colon-delimited field in
/etc/master.passwd with 'date -r' for each account changed, to see if
the appropriate expiration date was registered?  Next time you make a
change like this, test it with a short expiration time (a minute or
two, say) on a non-critical account to see if works instead of waiting
three months to discover that it does not.

 Any ideas on how to enforce this? Do I have to manually use pw(1) every 90 
 days?

No, you shouldn't have to if you use the feature properly.  You'll be
prompted immediately after login for a new password if your old one
has expired.


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: login.conf: passwordtime not enforced?

2010-07-14 Thread b. f.
On 7/14/10, Fernan Aguero fernan.agu...@gmail.com wrote:
 On Tue, Jul 13, 2010 at 10:19 PM, b. f. bf1...@googlemail.com wrote:

 I'm sorry about that. My apologies. I just assumed that you assumed
 that I was doing the right thing(TM). :)

That would be a very bad assumption to make, when attempting to track
down a problem.

...

 and check the sixth colon-delimited field in /etc/master.passwd with 'date
 -r' for each account changed, to see if
 the appropriate expiration date was registered?

 I don't quite get what 'date -r' does here ... but yes I've checked
 the 6th field in /etc/master.passwd, all accounts (regular users and
 system accounts) have a '0' in that field.

It transforms the password expiration time to a more convenient
format, for those of us who aren't counting machines.  A 0 in the
sixth field indicates that there is no expiration time, and something
is wrong.

 Next time you make a change like this, test it with a short expiration
 time (a minute or
 two, say) on a non-critical account to see if works instead of waiting
 three months to discover that it does not.

 I usually assume that the docs are correct, and don't go about
 checking and re-checking that everything works as expected ... unless
 not for these trivial config tweaks. Of course I've checked that the
 newly created passwords (now using blf instead of md5) worked, but I
 just assumed that the rest of the config settings for this login class
 didn't require further checking ... if the blf change worked, why not
 the rest?

 Do you suggest that I should now go and check if the
 'mixpasswordcase', 'minpasswordlen', 'idletime' or the 'umask'
 settings are honored? I just hope I don't need to ... :)

The docs can be outdated, incomplete, or misinterpreted.  Or your
system could be misconfigured or broken.  How much time and energy you
put into your testing is up to you.  If you're serious about security,
you'll check your changes.  Some of the above-mentioned are fairly
easy to check.

 I just added a new class in login.conf:

 test:\
 :tc=default:\
 ::passwordtime=2m:

 And then added a new user 'testaccount', using adduser(1). I've
 verified that its login class was OK in /etc/master.passwd (BTW again
 the 6th field is '0'). And I never got any message about the password
 being expired, after several succesful login attempts that, obvioulsy,
 spanned more than 2 minutes.


Bravo. The above is more of the kind of thing that needs to be done
when trying to diagnose a problem.  But I think you want:
 test:\
:passwordtime=2m:\
 :tc=default:

See the default login.conf and getcap(3).


 Who is responsible for filling in the password expiration time/date in
 master.passwd, according to the login class config? passwd(1)?
 adduser(1)? Myself, manually?

The first time you have to change it manually for each account, with
passwd(1); thereafter pam_unix(8) checks for expiration at login time:
if a password has expired, you are prompted to change it, and the new
password will have the appropriate expiration time.  It works for me
locally, with the default security settings; I've never tried it over
a remote connection.  You may have some configuration settings that
are causing problems.  Have you tinkered with /etc/pam.d/* ? What
other configuration changes have you made? After using cap_mkdb, have
/etc/pwd.db and /etc/spwd.db changed?  Do they have the right
timestamps?  Does the password change mechanism work properly if you
are logging in locally, as opposed to remotely via ssh?  Are your
system clocks keeping the right time?

 and entering that value into the 6th field of /etc/master.passwd. But
 then, I'll have to do this regularly using a script, because,

This shouldn't be necessary.  It would be better to try to find out
what is wrong.

 Is it at all possible to enforce password expiration times in FreeBSD?

Yes.  But it will take some patience to track down your problem.

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: FreeBSD vs YouTube

2010-07-14 Thread b. f.
I'm pretty new to this mailing list, and FreeBSD, in the last 2 weeks i was 
trying to use
FreeBSD as alternative to Windows, but i can't make the flash videos work on 
most of the
popular flash video sites. I've tried to pkg_add, compile from source, 
swfdec-plugin,
gnash on FreeBSD 7.3 and 8.1 ... but nothing worked, i can use mplayer to play 
movies
so this shouldn't be a problem, when i use swfdec, there are some unhandled 
event
(usually unhandled event 19) and sometimes can't write to a 
$HOME/.config/filename file,
and with gnash i see an error occurred, please try again later message on the 
site. I've
tried googling but most of the articles i found seemed outdated. So finally i 
came here
with the question: Is it possible to watch youtube on a FreeBSD system ? And 
if it is,
someone would be so kind to guide me to a FAQ / Article / wiki /

The open-source alternatives are improving, but for the moment, you
may have to use

www/linux-f10-flashplugin10

(or an earlier version) for Flash.  That means you'll have to enable
Linux emulation.  See Chapter 10 of the Handbook for details.  Or you
could bypass the Flash requirements of some sites, with one or more
of:

multimedia/cclive
multimedia/clive
multimedia/clive-utils
www/youtube_dl


There is hope for the future:

http://www.youtube.com/html5

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: login.conf: passwordtime not enforced?

2010-07-15 Thread b. f.
On 7/14/10, Fernan Aguero fernan.agu...@gmail.com wrote:
 On Wed, Jul 14, 2010 at 1:25 PM, b. f. bf1...@googlemail.com wrote:
 On 7/14/10, Fernan Aguero fernan.agu...@gmail.com wrote:
...
 The first time you have to change it manually for each account, with
 passwd(1);

 Sorry if I'm getting dense but do you mean 'manually' as in editing
 master.passwd with vipw?
 Or do you really mean 'manually with passwd(1)? My passwd(1) only
 allows me to change the user password and even doing this doesn't
 update the expiration time in master.passwd. Is there a hidden
 functionality in passwd that allows me to set the expiration time for
 the password?

Yes, I meant with passwd(1).  After some preliminaries, passwd(1)
hands the task over to pam(3), in particular pam_sm_chauthtok(3) of
pam_unix(8). This in turn uses the pw_* routines of libutil, contained
in /usr/src/lib/libutil/pw_util.c.  The pw_* use various libc
functions and pwd_mkdb(8). The handling of the reserved capabilities
minpasswordlen,
mixpasswordcase, passwordtime, etc. needs at least to be in pam(3),
for when you are prompted to reset your password, and should probably
be implemented in the other utilities that don't use pam(3), like
chpass(1),  pw(8), and the vipw(8) consistency checks.  It looks like
passwd(1) used to deal with these capabilities directly, but in April
2002 it was gutted and turned into a front-end for pam(3), and some of
the options-handling fell by the wayside.  In Feb. 2010, in response
to

http://www.FreeBSD.org/cgi/query-pr.cgi?pr=bin/93310

des@, who is responsible for pam(3), added passwordtime-handling in:

http://svn.freebsd.org/viewvc/base?view=revisionrevision=203377

At the time, he announced that it would be merged, at least into
8-STABLE (and subsequently into 8.1), in one week.  He never performed
this merge: I assume that he forgot.  So unfortunately it looks as if
you will have to manually set password expiration times.  You could do
this, for example,  with vipw(8); or with pw(8) and either a -p
argument or a password_days entry in pw.conf(5). Or you could add the
patch from the above PR to your system pam_unix(8) sources and rebuild
them, or update to 9-CURRENT (which is what I am using).

I'm guessing that some of the other reserved options are neglected as
well.  You could enforce them manually, or patch pam_unix(8),
chpass(1),  pw(8), and vipw(8).  If you do so, you should submit PRs
with your patches, in the hopes that someone will reintroduce them
into the base-system utilities.  Ironically, the stripped-down
/usr/src/release/picobsd/tinyware/passwd/local_passwd.c still handles
some of them -- you could look at that for ideas.

Incidentally, If I were you, I would update at least to the latest
stable release of FreeBSD, unless you are constrained to use the
earlier releases for some work-related reason.

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: Are kernel stress test results displayed online?

2010-07-21 Thread b. f.
Yuri wrote:
Before one of the releases, I remember, kernel stress tests results were
online.
Now I can't find them.

Are they run? (I guess they must be.)
Particularly would be interesting to see tests for FreeBSD 8.1-RC2,
FreeBSD 8.0-STABLE and FreeBSD-9.0.
Also does stress test only cover kernel or device drivers as well?

I don't know about the tests that are conducted as part of the release
engineering process, but there are links to some tests at:

http://people.freebsd.org/~pho/stress/index.html

I don't know how useful these will be -- as noted on the above page,
the intended audience is kernel developers, many of the tests are
associated with experimental kernel patches, the test results are
rarely exactly reproducible, and the tests only cover certain kernel
subsystems.  The test source code is available, so you could run your
own tests if you wanted.  You could also look at the tests in
/usr/src/tools/regression, or some of the benchmarks and tests in
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: ports INDEX file

2010-07-23 Thread b. f.
Benjamin Lee wrote:
 On 07/22/2010 06:20 PM, Fbsd8 wrote:
 I have a pristine install  of 8.0.
 There is no /usr/ports directory yet.
 I am trying to use the portcheckout port and the porteasy port to
 just populate the ports tree with only the ports I use.

 Problem is in both cases the above ports require an existing INDEX file
 to process and since I have none they don't work.

 How can I just download the ports INDEX file?
 Portsnap is not a solution.

I see in the source of porteasy that its fetching
http://www.freebsd.org/ports/INDEX-8.bz2

How can I verify this?

Usually the index file is placed at $INDEXDIR/$INDEXFILE, as defined
in $PORTSDIR/Mk/bsd.port.mk. In your case, by default, that would be
/usr/ports/INDEX-8.

As Matthew asked, do you really want to do this?  By modern standards,
the space required for the ports tree is modest (~550MB uncompressed),
and you can learn a lot about what's available and how things work by
looking through it.  Plus you save the time required to implement this
partial ports tree approach.  If you really need to save the disk
space, and don't have other special requirements, then considering
using binary packages instead of compiling from source.

If you do have special requirements -- e.g., you need to build ports
with non-default options or special flags, or you don't trust foreign
binary packages (in that case, though, you should probably be prepared
to do a lot of work auditing the source code as well), and you don't
have at least one machine with the required disk space, then maybe
this approach is worthwhile.  However, that seems unlikely.

If you pursue the partial ports tree approach, you don't need to make
or fetch an INDEX(which, although it may be a useful summary, may be
inappropriate for parsing dependencies for ports built with
non-default options), and you don't need to use either of the ports
that you mentioned:  as someone else said, you could just write a
shell script to fetch the necessary infrastructure Makefiles (those in
/usr/ports/Mk and the needed category subdirectories), and the desired
port and it's dependencies, using cvs(1) (but you have to choose a
server that permits anonymous cvs access, and learn cvs), csup(1)
(configured to use a suitable cvsup server using the ports-all
collection and the -i flag, which would permit you to grab only parts
of that collection), or even an http client like fetch(1) (exploiting
the fact that single ports can be downloaded in tarball form from
cvsweb.freebsd.org in links of the form:

http://www.FreeBSD.org/cgi/cvsweb.cgi/ports/$CATEGORY/$PORT/$PORT.tar.gz?tarball=1

and single Makefiles via other links).

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: can i just upgrade the 8.1 kernel ?

2010-07-23 Thread b. f.
FreeBSD mybsd.zsoft.com 8.0-RELEASE-p2 FreeBSD 8.0-RELEASE-p2 #0: Wed Jul 14
15:35:26 CST 2010
root at mybsd.zsoft.com:/media/G/usr/obj/media/G/usr/src/sys/MYKERNEL  i386

Can i just use the following commands to upgrade to 8.1 kernel ? And does
the virtualbox-ose still work under 8.1 ?

Check the mailing lists and PRs to see if anyone has had problems. It
probably works.

# csup -g -L 2 -h cvsup.freebsd.org
/usr/share/examples/cvsup/standard-supfile

I think that this file contains:
*default release=cvs tag=.
which would update /usr/src to 9-CURRENT (-head).  That doesn't sound
like what you want.  Instead, you probably want the stable-supfile in
the same directory instead, which probably has(check this yourself):
*default release=cvs tag=RELENG_8
That would update your sources to the latest 8-STABLE, which is a
little in advance of 8.1.  Or you could change the tag to RELENG_8_1,
to be more conservative.  That would be 8.1+critical updates, if any.

# cd /usr/src
# make buildkernel KERNCONF=MYKERNEL
# make installkernel KERNCONF=MYKERNEL

You probably want to update the rest of the base system as well as the
kernel.  Follow the instructions near the bottom of /usr/src/UPDATING,
something like:

cd /usr/src
make buildworld kernel KERNCONF=MYKERNEL
reboot in single user
fsck -p /
mount -u /
mount -a
adjkerntz -i
mergemaster -p
cd /usr/src
make installworld
make delete-old delete-old-libs
mergemaster -i
reboot

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: ports INDEX file

2010-07-23 Thread b. f.
On 7/23/10, Fbsd8 fb...@a1poweruser.com wrote:
 b. f. wrote:
 Benjamin Lee wrote:
 On 07/22/2010 06:20 PM, Fbsd8 wrote:
...

 Well first thanks for the info you provided though it was all negative.

I think that you were misinterpreting what I wrote if you think that
it was all negative.

 I will explain what my goal is.

 First though, I have verified that the /usr/ports/INDEX-8 file can be
 gotten without the using cvs or cvsup.

 fetch -m http://www.freebsd.org/ports/INDEX-8.bz2; does if fact work
 and the data on the file is as of 3 hours ago. So that indicates its
 being kept current. The -m means that if the date of the remote file is
 NOT newer then the local one, the download is bypassed

Yes, as long as the server supports this, and doesn't unnecessarily
change the mtime of the file.  Minus some variable expansions, this is
basically what the fetchindex target does. If you don't care about
hard-coding version numbers, etc., then you might as well not invoke
make at all, and just do what you're doing, because it's faster.
...
 compile php5 from the port. But to short cut the compile process, I
 pre-install all of php5's dependents as packages. And of course I had to
 figure out who they all were by hand the first time and built a script
 that automates the whole procedure. I use cvsup at NEW RELEASE time to
 populate the empty ports tree with ports-base. Then I use cvsup to
 checkout the php5 make files and them make install and everything
 comes together just fine.

You may be interested in using ports-mgmt/portmaster ( a shell script
with minimal dependencies), which can do something similar to what you
are trying to do with the --index-only, -P/-PP, and --packages-build
flags.

 Now the Freebsd method of the 22,000 individual ports each with 3 to 5
 files is a method which has out lived its usefulness. TAKE NOTE: NO

There is no doubt that the increasing size of the tree, and the fact
that some parts of the build infrastructure don't scale well, have
created some challenges.  But I hardly think that it has outlived its
usefulness.

 FLAME WAR INTENDED. I just think a option should exist for us who don't
 follow the bleeding edge. Sure to some people that big ports tree is no

Well, the bleeding edge versus snapshot issue is a bit different from
the debate about the size and modularity of the ports tree.

 big deal, but I bet they don't do backups. That ports tree directory is
 a large resource hog if you lift the blinders and look at the big picture.

I guess it depends upon the constraints that you are operating under.
But fetching a new index is going to take about as much network
traffic as an update of the ports tree with csup.

 So since I have a method all ready working as I explained above, I am
 collecting information on the elements needed to write a shell script
 port application based on the method already described. Figure I will
 use cvsup to populate the port-base and checkout just the parent port
 make files. Read the INDEX file to automate finding the parent port
 dependents and reading the /var/db/pkg to skip an dependents all ready
 installed and then launch pkg_add to install the dependents and on any
 package failures cycle back and use cvsup to also checkout its make
 files, before issuing the make install on the parent.

Just bear in mind that the default INDEX contains the dependencies for
ports built with default options.  Changing the options may result in
different dependencies.  Consider using portmaster.

 Along this same line of thought,
 Another area I have problems with is why don't the port make system go
 and checkout any dependent ports missing make files instead of halting
 like it does now.

The ports system wasn't designed to meet your objectives.  Delegating
authority to perform bursts of unsupervised network activity at
unpredictable intervals would probably be considered a problem by many
users.  And some tasks require the entirety of the tree to be present.


 When installing a package it will auto install all of it dependents.


There is interest in work with fat packages to do something like you describe:

Complete (a.k.a. Fat) packages

Suggested Summer of Code 2010 project idea

Technical contact: Brooks Davis

When bootstrapping systems it would be useful to be able to create a
single package file that contains one or more packages and all the
required dependent packages. This is conceptually similar to, but
different from PC-BSD's PBI package format. PBI's contain a private
copy of all dependencies, fat packages would contain each individual
package and once installed it would be as though each package was
individually installed in the usual manner.

This project would consist of additions to the pkg_tools to support
creation and installation of a new package file format and to ports to
build these packages.

Requirements:

Strong knowledge of C code.
A basic understanding of the inner workings of the ports tree.



Also, there is some ongoing work

Re: BSD logo

2010-07-24 Thread b. f.
  I have always been thinking of trying FreeBSD but as a Christian I get
  deterred by its un-Christian
  logo.

It's amazing how exercised people get over a topic like this, like in
that old story:

http://www.milk.com/true-stories/unix_for_the_masses.html

I think it's a pretty dumb logo myself, but a group of people that
offer you free software, and even some help using it -- that doesn't
seem benign to you?  Why don't you talk to some of the other
Christians involved in the project, like those that maintain bible
study software in FreeBSD Ports?

...

 The term daemon has ancient
roots in Greek mythology and has nothing to do with more recent Christian
notions of demons.

Well, nothing to do with is overstating the case a bit.  There are
some connections, even beyond the etymological, and not all Greeks
thought alike about them.  But we take your point.

...

I was a member of a military unit known as the Red Devils years ago.  I
did not feel like I was being corrupted by Evil.

Some people would find this a lot more problematic than wearing a
daemon t-shirt.  ;) Out of curiosity, Is that the one that got its ass
kicked at Pearl Harbor and Wake Island, or the one that got its ass
kicked at Arnhem?  Or just a hardcore bunch of Man U. fans?

...

You stick to your holy water, I'll stick to defenestrating virgins,

That seems like a waste of a perfectly good virgin.

sacrificing goats and chanting the Lord's prayer backwards whilst
dancing naked in a pentagram.
I find it's the only way to get FreeBSD to work

I knew I was missing something.

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: popt-1.50 or better??

2010-07-24 Thread b. f.
here are the last few lines of output from configure, ots-0.5.0:

checking for pkg-config... /usr/X11R6/bin/pkg-config
checking for glib-2.0 = 2.0 libxml-2.0 = 2.4.23... yes
checking OTS_CFLAGS... -I/usr/local/include/glib-2.0
-I/usr/local/lib/glib-2.0/include -I/usr/local/include/libxml2
-I/usr/local/include
checking OTS_LIBS... -L/usr/local/lib -lglib-2.0 -lxml2
checking for poptParseArgvString in -lpopt... no
configure: error: popt 1.5 or newer is required to build ots.
You can download the latest version from
ftp://ftp.rpm.org/pub/rpm/dist/rpm-4.1.x/


poptParseArgvString is in the $PREFIX/lib/libpopt.so.0 library from
our devel/popt port. The latest available version of this software is
1.16, in the Red Hat repos.  Look at the configure script to determine
why it can't find the symbol. Maybe you need to reinstall devel/popt,
or patch the configure script.


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: 8.1 is available

2010-07-24 Thread b. f.
On Sat, Jul 24, 2010 at 07:38:51PM +0800, Aiza wrote:

 Since the release team never makes a announcement on this list when a
 new RELEASE is published. I will let you all know that

 RELEASE 8.1 has been published and is available for download.

And if you were wondering why the release iso images were uploaded to
the main project server four days prior to the announcement, the
official reason given was to allow all of the mirrors time to
synchronize with the main server before the announcement, to avoid
lots of inquiries about why the release isn't available.


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: 8.1 is available

2010-07-24 Thread b. f.
On 7/24/10, Fbsd8 fb...@a1poweruser.com wrote:
 b. f. wrote:
 On Sat, Jul 24, 2010 at 07:38:51PM +0800, Aiza wrote:


 What I am wondering is why the release iso have been renamed. The path
 and file name was to long before and now with 8.1 some fool added the
 word Freebsd to it. What on earth for? How many times does the word
 freebsd have to be in the path/name? Wish somebody would supervise the
 worker bees so they don't go changing thing on their own.

That was because a lot of people with a different opinion about this
complained, so that re@ was persuaded to make the change:


Revision 200775 - (view) (annotate) - [select for diffs]
Modified Mon Dec 21 14:42:35 2009 UTC (7 months ago) by kensmith
File length: 45736 byte(s)
Diff to previous 197313

Add FreeBSD- to the beginning of the filenames for the ISO images.
People who collect ISOs from more than just us have been requesting
this for a while.

MFC after:  1 week

It seems reasonable to me, even if it does require a few (possibly
annoying) one-time-only adjustments for some people.


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: searching INDEX in .sh

2010-07-24 Thread b. f.
I'm looking for a snippet of .sh type shell code that searches the
/usr/ports/INDEX-8 file for dependents.

Just a pointer to a script in the ports system that has this would be
helpful

Do you mean that, given port A, you want to find all ports that need
port A in order to be fetched, extracted, patched, built or installed?
 Or do you want to find all ports that are needed to fetch, extract,
patch, build or install port A? If the former, you could look at the
parts of ports/Mk/bsd.port.mk that are used by running `make -C
$PORTSDIR search bdeps=insert PKGNAME of port A here
display=name,path`, and `make -C $PORTSDIR search rdeps=insert
PKGNAME of port A here  display=name,path`.  If the latter, look at
the parts of ports/Mk/bsd.port.mk that are used by running `make -C
insert PKGORIGIN of port A here pretty-print-run-depends
pretty-print-build-depends`.  Also, parts of the ports-mgmt/portmaster
script used with --index-only may have similar functionality.

And do you mean to only use the INDEX?  Or are you able to use parts
of the port tree?  Or the pkg_info utility?

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: searching INDEX in .sh

2010-07-24 Thread b. f.
On 7/25/10, b. f. bf1...@googlemail.com wrote:


 the parts of ports/Mk/bsd.port.mk that are used by running `make -C
 insert PKGORIGIN of port A here pretty-print-run-depends
 pretty-print-build-depends`.

Sorry, it's actually 'pretty-print-build-depends-list' and
'pretty-print-run-depends-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: searching INDEX in .sh

2010-07-25 Thread b. f.
On 7/25/10, Aiza aiz...@comclark.com wrote:
 b. f. wrote:

 I just found /usr/ports/Tools/scripts/postsearch which uses the
 /usr/ports/INDEX-8 file as its source to search. This is a perl script
 but can be used from within in .sh script.

Ah, ok.  I thought you wanted to use the Bourne shell and base system
utilities only.


 Been playing with it and see a big inconsistence in how ports list
 build-deps and run-deps. Some ports list no build-deps just run-deps and
 vise-versa and some have same listed list in both.

 Thinking I will have to take both the build and run deps lists and sort
 them together and drop dups to create a good list of dependents to allow
 for the lax enforcement of standards in the Makefile about how to list
 the ports dependents.

As someone remarked, this is not necessarily inconsistent. The
standards certainly aren't lax, although mistakes are occasionally
made.  And it is slightly complicated by the fact that the listing in
the INDEX is recursive.

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: I donot like using mergemaster ?

2010-07-27 Thread b. f.
On Monday 26 July 2010, zaxis wrote:
 I want to upgrade my freebsd 8.0  to 8.1.  I have read all the steps
 about upgrading freebsd. I feel mergemaster  is difficult to use e.g.
 which parameters should i use ?   (you may wish to use -U or -ai or
 -Fi)

Well, obviously you will get more out of mergemaster if you read the
manpage and take the time to decide which options will work best for
you.  But if you can't be bothered to do that, the suggested usage in
/usr/src/UPDATING works for most people.  Also, there is an
alternative to mergemaster that is supposed to be easier to use in
some ways: John Baldwin's new port, sysutils/etcupdate.  You may want
to take a look at 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: apps update from ports

2010-07-27 Thread b. f.
I was wondering about your update strategy. Do you update your apps as soon
as a new version is available in the ports ? Or do you follow the if it
works, don't touch it strategy ?


There is no one strategy that pleases everyone.  You'll have to
consider the time required  to perform updates (including some time
for configuring and learning how to use the new software, and for
recovering from occasional problems), and weigh that against the
benefits (if any) of having new software.  Some people prefer to use
the latest software, and others may use a snapshot of the ports tree
that coincides with a stable release, updating only those ports with
known critical security problems in between releases.  Sometimes, you
may wish to make this decision on a port-by-port basis.

I'm guessing portupgrade is your preferred way of doing this hence, do you
also choose -P or -PP ?

If you don't need to build from source, in order to use non-default
options or flags, or get the very latest versions of the port, then
packages are a good choice.  In addition to portupgrade, the
comparatively lightweight ports-mgmt/portmaster port also has this
functionality.

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: popt-1.50 or better??

2010-07-27 Thread b. f.
On Sat, Jul 24, 2010 at 10:53:03PM +, b. f. wrote:
 here are the last few lines of output from configure, ots-0.5.0:
 
 checking for pkg-config... /usr/X11R6/bin/pkg-config
 checking for glib-2.0 = 2.0 libxml-2.0 = 2.4.23... yes
 checking OTS_CFLAGS... -I/usr/local/include/glib-2.0
 -I/usr/local/lib/glib-2.0/include -I/usr/local/include/libxml2
 -I/usr/local/include
 checking OTS_LIBS... -L/usr/local/lib -lglib-2.0 -lxml2
 checking for poptParseArgvString in -lpopt... no
 configure: error: popt 1.5 or newer is required to build ots.
 You can download the latest version from
 ftp://ftp.rpm.org/pub/rpm/dist/rpm-4.1.x/


 poptParseArgvString is in the $PREFIX/lib/libpopt.so.0 library from
 our devel/popt port. The latest available version of this software is
 1.16, in the Red Hat repos.  Look at the configure script to determine
 why it can't find the symbol. Maybe you need to reinstall devel/popt,
 or patch the configure script.



can anybody tell me how to upgrade just this one file:
   devel/popt?  i tried various forms up portupgrade.  zip.

I'm at a loss here.  First of all, you mean upgrade this port,
right?  Because devel/popt is a port, not a file.  If you have an old
version of devel/popt, it would seem that any of the standard updating
tools would work.  If you just want to reinstall it, you could simply:

cd /usr/ports/devel/popt  make deinstall clean install  make clean

Then you could check your libpopt.so.0:

ldconfig -vr | fgrep popt
objdump -T /usr/local/lib/libpopt.so.0 | fgrep poptParseArgvString

Of course, I've assumed that PREFIX=LOCALBASE=/usr/local and
PORTSDIR=/usr/ports.  Make the proper substitutions if they aren't.

I don't see any error logs or an IGNORE for textproc/ots, so I'm
assuming that it builds properly on the package-building cluster.  If
that's the case, then there is something wrong with _your_ build: a
corrupted file, polluted environment, error after autodetection, etc.
But we won't know what is wrong until you show the corresponding part
of the configure script and errors in the config.log.

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: amd64

2010-08-09 Thread b. f.
On 8/9/2010 4:14 PM, Robert Huff wrote:
 Polytropon writes:


   I've installed FreeBSD-amd64. It runs very well. The packages I fetch
 are amd64 too, but what about the ports I compile myself? Are those
 amd64 too?

   Yes, as your compiler infrastructure and target platform
   is amd64, and so is the resulting binary code.


How does it know your are on amd64?  gcc auto detect of CPU?

As the other person wrote, the base system compiler suite and other
base system utilities are configured and compiled to build and use
amd64 binaries by default.  There is only limited support for
cross-building:  on amd64, for example, there are some provisions for
building and using 32-bit, i386 binaries; and the base system
sources have some limited support for cross-building for other
architectures, by setting certain variables in the build environment.
In general, one cannot just build and use any binaries on a given
architecture.

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: AHCI driver

2010-08-10 Thread b. f.
Is it really better to enable AHCI driver?

Almost certainly, yes.  If your BIOS and SATA controller use AHCI, and
are recognized by the ahci(4), mvs(4),  or siis(4) drivers (I think
that these drivers are built as kernel modules by default in the
recent versions of FreeBSD, and don't require the use of a custom
kernel with the non-default ATA_CAM option -- all you have to do is
load them at boot time, either manually or via loader.conf(5)), then
you will be able to use features like NCQ and better power management
with disk drives that support those features.  This can give you
substantial benefits.

If your BIOS and/or SATA controller don't support AHCI, in order to
use cam(4) you must build a custom kernel with the ATA_CAM option.  In
that case you may still see some benefits, but they won't be as
dramatic as in the AHCI case.  If I recall correctly, the only
disadvantage to this option is that it prevents the use of ataraid(4)
-- everything else has a (usually slightly better) counterpart with
the option, and it is only a matter of configuring your system to use
it and learning how to use the new management tools (like
camcontrol(8)), rather than the old tools (like atacontrol(8)).

And yes, if you use the new drivers or the ATA_CAM option, some of
your disks will probably show up as /dev/adaX, rather than the old
/dev/adX. So make sure that you adjust fstab(5) and device.hints(5) as
necessary before rebooting.

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 there a way to rebuild 32-bit libraries under amd64?

2010-08-12 Thread b. f.
I have 8.0-STABLE amd64 machine, and I need to run some 32-bit FreeBSD
process which runs fine on 8.0-STABLE i386.

So I copied all shared libs needed by it from i386 into there respective
locations on amd64, but under lib32/ folder.
 libexecinfo.so.1 = /usr/local/lib32/libexecinfo.so.1 (0x289ca000)
 libffi.so.5 = /usr/local/lib32/libffi.so.5 (0x289d5000)
 libstdc++.so.6 = /usr/local/lib32/libstdc++.so.6 (0x289da000)
 libm.so.5 = /usr/lib32/libm.so.5 (0x28ac4000)
 libgcc_s.so.1 = /usr/local/gcc/4.5.0-32bit/lib/libgcc_s.so.1
(0x28add000)
 libthr.so.3 = /usr/lib32/libthr.so.3 (0x28ae9000)
 libc.so.7 = /usr/lib32/libc.so.7 (0x28afe000)

But the process crashes. After debugging I found that regexec returns
result different from what it returns on i386 with the same input.

So my question is: is there a way to rebuild for example
/usr/lib32/libc.so.7 and /usr/lib32/libthr.so.3 on amd64? Or what may
cause such incompatibility?

Did you install the 32-bit compatibility libraries and utilities on
amd64, by selecting the lib32 option with sysinstall(8), or by running
../lib32/install.sh from the FreeBSD media, or by rebuilding and
reinstalling world without a WITHOUT_LIB32 defined in src.conf(5) or
make.conf(5)?  Then did you make sure that rtld(1) has the proper
hints to find any needed 32-bit libraries that are not in the lib32
part of the base system, by defining the right values for
ldconfig32_paths and/or ldconfig_local32_dirs in rc.conf(5)?

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: ts_to_ct flood on 8.1-STABLE

2010-08-13 Thread b. f.
Since installing 8.1-RC2 and now on up-to-date RELENG_8 I am frequently
getting kern.crit messages like

ts_to_ct(1281661818.743348859) = [2010-08-13 01:10:18]

and have been unable so far to determine their origin or purpose. I saw
no such messages while running 7.x or earlier releases.

This occurs when the rtc is set, via:

atrtc_settime--clock_ts_to_ct

after a verbose boot.  I think that someone changed some of the
timekeeping code to periodically adjust the value of the rtc if ntp is
used to update the system time, machdep.disable_rtc_set=0, and the rtc
driver hasn't been disabled:

http://svnweb.freebsd.org/viewvc/base?view=revisionrevision=208297

This is probably what you are seeing.  It should occur every
machdep.rtc_save_period seconds. It's probably harmless, unless the
adjustments are big or erratic, in which case you may want to check
your rtc's battery, or the results of your ntp usage.

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: Documentation on how to build 32bit applications on amd64?

2010-08-15 Thread b. f.
 On 08/14/2010 04:05, Tijl Coosemans wrote:
  There are patches for CURRENT here:
  http://lists.freebsd.org/pipermail/freebsd-arch/2010-July/010470.html
 

 Thank you Tijl,

 cc-m32-2.diff has some failures:
 --
 |diff --git a/include/Makefile b/include/Makefile
 |index 0ba8b17..e01d0a6 100644
 |--- include/Makefile.orig
 |+++ include/Makefile
 --
 Patching file include/Makefile using Plan A...
 Hunk #1 succeeded at 114.
 Hunk #2 succeeded at 136.
 Hunk #3 succeeded at 147.
 Hunk #4 failed at 186.
 Hunk #5 failed at 263.
 2 out of 5 hunks failed--saving rejects to include/Makefile.rej

 Also file sys/amd64/include/_align.h referred from cc-m32-3.diff is
 missing on my system.
 Maybe your patch isn't up-to-date?

As Tijl mentioned, his patches are for -CURRENT, and you are using
8.0-STABLE, right? STABLE-8, from which 8.0-RELEASE and 8.0-STABLE
were derived, was branched from -CURRENT on 3 Aug. 2009:

http://svn.freebsd.org/viewvc/base?view=revisionrevision=196045

while src/sys/amd64/include/_align.h was added to -CURRENT later, on 8
Sept. 2009:

http://svn.freebsd.org/viewvc/base?view=revisionrevision=196994

You'll need to use -CURRENT, or rework the patches.

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: Xorg Problems

2010-08-19 Thread b. f.
Warren Block wrote:
On Thu, 19 Aug 2010, Ondrej Majerech wrote:
 On 08/19/2010 15:02, Warren Block wrote:

 Don't need it in FreeBSD, either. In fact, using it in FreeBSD often
 causes hesitant input characters that only show up when you move the
 mouse. Or a draggy mouse. Or both.

Finally got motivated to put together a little writeup on this:

http://www.wonkity.com/~wblock/docs/html/aei.html

Isn't your summary (and your last section, despite it being
tongue-in-cheek) misleading, because it says that AllowEmptyInput is
bad, when you actually mean that it is _good_, and that _disabling_ it
in Xorg.conf is bad? Or am I missing something?

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: FreeBSD, GPGPU and OpenCL/CUDA

2010-08-20 Thread b. f.
...

 MPI is typically dependent on the network not OpenMP.  OpenMP 3.0 can
 be made more scalable if there's tasks built-into the kernel that can
 be cleanly exposed to userland.  (Like OpenSolaris + libtask from
 Moinak is a good example)

If you have a specific set of modifications in mind, then you should
bring them up on freebsd-hackers, for example.  There are active users
of OpenMPI around ( e.g.,

http://www.bsdcan.org/2010/schedule/events/169.en.html

, and I'm sure they would be willing to discuss improvements.

 2) HPC ready compiler.. (Sorry guys, but LLVM is just
 not production ready for this task and is missing Fortran)


Not ready now, perhaps -- but development there is fairly rapid, and
the switch to llvm, if there is to be one, is still some time off.
However, later versions of gcc are in ports, there are some
discussions regarding the revival of the icc port, and there is work
underway to allow users to more easily use alternative compilers and
toolchains for the base system as well as for ports:

http://www.freebsd.org/news/status/report-2010-01-2010-03.html#Out-of-Tree-Toolchain


 3) IB network drivers

Don't know the status of Infiniband drivers, are there drivers?

There is a port of of the Open Fabrics Enterprise Distribution underway:

http://svn.freebsd.org/viewvc/base/projects/ofed/

And there is:

http://svn.freebsd.org/viewvc/base/head/sys/contrib/rdma/

 4) Hardware vendor to deliver a complete solution + support
 (iXsystems?)

Well, that's not up to us. All we can do is port more software and
encourage people to use it.  And we includes you.

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: FreeBSD, GPGPU and OpenCL/CUDA

2010-08-20 Thread b. f.
On 8/20/10, Eduardo emor...@xroff.net wrote:
 On Fri, 20 Aug 2010 13:24:16 +
 b. f. bf1...@googlemail.com wrote:

 Reading documentation, thanks b. f. I'm already on freebsd-hackers
 list. Is that the correct list for this topic?

If you have a specific technical question about FreeBSD internals,
then freebsd-hackers is probably a good place to ask.  -hackers is a
low-volume list, and the subscribers will not be happy if there are a
flood of very general inquiries or chat, or if the person who is
asking questions hasn't thought about them beforehand.  -arch is even
more conservative, and solely for questions about the direction of the
base system, especially the kernel.  -ports may also be a good place
to ask about porting software.

 Not only compilers for Fortran or other languages but for new
 architetures, Cluster of SMP CPUs with GPU attached.

Okay.  Maybe we'll see a convergence of the two in the medium/long
term.  Right now, interested parties need to look at the available
hardware, and then talk to the vendors about whether they would be
willing to support a port of their software to FreeBSD, and
_specifically_, what is needed.  For example, we faced a similar
situation with the newer Nvidia GPUs not so long ago.  Some key
developers like John Baldwin got involved, and determined what changes
needed to be made in the FreeBSD base system in order to support the
newer hardware and graphics drivers.  It would have been nice to get
an open-source driver, but since Nvidia wasn't willing to do that,
FreeBSD  chose to meet them half-way.  Probably a similar effort will
be needed for CUDA.  Someone should look at the requirements, and have
a _detailed_, _sustained_ discussion with Nvidia and the FreeBSD
Foundation.  If, for example, KMS is needed, then the Foundation may
be willing to invest in that, because it will probably also be needed
for new graphics drivers and Xorg, anyway.  Robert Noland was working
on it, but he was doing it largely by himself in his spare time, and
then he got a new job and had to slow down considerably, if not stop
altogether.
...

 For now i'm going to port my hpc app to FreeBSD.

Good.  You may want to consider discussing any substantial effort
first on -ports, to avoid duplication of effort, and to see if there
are any better alternatives available.

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 to HTML translations

2010-09-04 Thread b. f.
What PDF to HTML translators, other than pdftohtml, am I likely to be
able to find in ports?  I went looking for pdf2html, expecting to find
that there, but no luck.

Off the top of my head:

OpenOffice
graphics/xpdf (via pdftotext -htmlmeta, simplistic)
graphics/poppler-utils (pdftohtml)

I'm guessing there are others, too.  Or maybe, you could use Adobe's
service.  From:

http://www.adobe.com/products/acrobat/access_onlinetools.html

Adobe PDF Conversion by Email Attachment
If the Adobe PDF file is on local media, such as a hard drive, CD-ROM,
or internal server, it can be submitted as a MIME attachment to an
e-mail message. All converted Adobe PDF documents will be sent back to
the sender as MIME attachments. For plain text, mail the attached PDF
to pdf2...@adobe.com. For HTML, mail the attached PDF to
pdf2h...@adobe.com.

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 to HTML translations

2010-09-04 Thread b. f.
On 9/5/10, b. f. bf1...@googlemail.com wrote:
What PDF to HTML translators, other than pdftohtml, am I likely to be
able to find in ports?  I went looking for pdf2html, expecting to find
that there, but no luck.

 Off the top of my head:

 OpenOffice
 graphics/xpdf (via pdftotext -htmlmeta, simplistic)
 graphics/poppler-utils (pdftohtml)


I guess that you could also use converters/pdf2djvu + djvutoxml from
graphics/djvulibre[-nox11].

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


<    1   2   3