date:20100131

Mount floppy image

2010-01-31 Thread Leslie Jensen



I'm trying to mount a floppy image following the instructions on:

http://www.bsdguides.org/guides/freebsd/beginners/mdconfig_mount_images



To mount a floppy image, create a virtual device, /dev/md0, for the 
floppy image.


# mdconfig -a -t vnode -f /tmp/boot.flp -u 0



I had to touch /tmp/boot.flp to make it work


Next:


Now mount the virtual device.
#   mount /dev/mnt0 /mnt
_

I believe there's a typo here should be /dev/md0

I get:

mount /dev/md0 /mnt
mount: /dev/md0 : Input/output error

I have no idea what to do now!

Any suggestions?

Thanks

Leslie
___
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: Help! Upgrade from fbsd 5.4 to 8.x

2010-01-31 Thread Roland Smith

On Sat, Jan 30, 2010 at 11:08:05PM -0500, Jeff Mitchell wrote:
 
   ie: This machine has a lot going on .. wiki's (ie: apache et al), 
 mysql databases, mailing lists, and a dozen hand rolled applications. 
 (Hey, someone has to write custom emulators of ancient systems to keep 
 BBSes alive, right?) Naturally, /etc is modified all to hell, and I'm 
 terrified of any automated upgrades for fear random things would just not 
 work later. Especially with the age... Things work great, but I worry 
 about security naturally, and keeping up with patches or installing 
 anything new is a nightmare due to dependancies.

Realize that things like apache, mysql etc. will have changed since the 5.4
days as well. As for the files in /etc and /usr/local/etc, I tend to have a
~/setup/$HOSTNAME directory where I keep configuration files under revision
control. I use some perl scripts so check if e.g. a port or system has caused
any changes in /etc. There is also a script the installs the files in their
proper location and executes post-install commands. I've documented this on a
webpage; http://www.xs4all.nl/~rsmith/unix/configfiles.xhtml

   o Some of the executables on this box are without source but I 
 still need them to run; short of moving them to a VM and doing some 
 voodoo, what are the chances a binary built for fbsd 5.x works fine in 
 8.x? (earlier fbsd's had the break between gcc versions, but I'm rather 

The GENERIC kernel in 8.0 comes with the COMPAT_FREEBSD5 option by default, so
the only thing you need to do is to install the misc/compat5x port.

   3 - yank the drive, slap a giant new fat drive in there, do a full 
 fbsd 8.0 install, and then migration from old drive as needed

Definitely #3.

   Aside -- whats the recommended way to stay on top of upgrades 
 anyway? It used to be a tortuous process back 5 years ago, but hopefully 
 things are much more streamlined now .. nightly 'make upgrade' ftw :)

I tend to keep my main machine on RELEASE-pN, unless there is good reason to
follow STABLE (e.g. hardware support). As for ports, there is the following
weekly ritual;

less /usr/ports/UPDATING
portsnap fetch extract
portmaster -a -B -d

HTH,

Roland
-- 
R.F.Smith   http://www.xs4all.nl/~rsmith/
[plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated]
pgp: 1A2B 477F 9970 BA3C 2914  B7CE 1277 EFB0 C321 A725 (KeyID: C321A725)


pgpFox89y561e.pgp
Description: PGP signature

Re: Mount floppy image

2010-01-31 Thread Leslie Jensen




2010-01-31 09:27, Leslie Jensen skrev:


I'm trying to mount a floppy image following the instructions on:

http://www.bsdguides.org/guides/freebsd/beginners/mdconfig_mount_images



To mount a floppy image, create a virtual device, /dev/md0, for the
floppy image.

# mdconfig -a -t vnode -f /tmp/boot.flp -u 0



I had to touch /tmp/boot.flp to make it work


Next:


Now mount the virtual device.
# mount /dev/mnt0 /mnt
_

I believe there's a typo here should be /dev/md0

I get:

mount /dev/md0 /mnt
mount: /dev/md0 : Input/output error

I have no idea what to do now!

Any suggestions?

Thanks



Of course the imagefile had to be in /tmp/
and it had to be mount_msdosfs /dev/mnt0 /mnt

Sorry for the noise

Leslie
___
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: Mount floppy image

2010-01-31 Thread Roland Smith

On Sun, Jan 31, 2010 at 09:27:48AM +0100, Leslie Jensen wrote:
 
 I'm trying to mount a floppy image following the instructions on:
 
 http://www.bsdguides.org/guides/freebsd/beginners/mdconfig_mount_images
 
 
 
 To mount a floppy image, create a virtual device, /dev/md0, for the 
 floppy image.
 
 # mdconfig -a -t vnode -f /tmp/boot.flp -u 0
 
 
 
 I had to touch /tmp/boot.flp to make it work

That is strange. Is  /tmp/boot.flp an existing image? If so, what size is it?

Note that is you use touch on a non-existing file, it will create a file 0
bytes long! If you try to mount that, you'll get an error, because there is no
data to be read.

 Now mount the virtual device.
 # mount /dev/mnt0 /mnt
 
 I believe there's a typo here should be /dev/md0

Yes.
 
 I get:
 
 mount /dev/md0 /mnt
 mount: /dev/md0 : Input/output error
 
 I have no idea what to do now!

If you want to _create_ a floppy image, you can use:

dd if=/dev/zero bs=1k count=1440 of=boot.flp

Then use mdconfig to make an md device out of it. Of course you'll have to
create an msdos filesystem on it;

newfs_msdos /dev/md0

After that you can mount it and fill it with whatever you like.

-- 
R.F.Smith   http://www.xs4all.nl/~rsmith/
[plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated]
pgp: 1A2B 477F 9970 BA3C 2914  B7CE 1277 EFB0 C321 A725 (KeyID: C321A725)


pgp1eGhk47ozj.pgp
Description: PGP signature

Re: Pain finding packages

2010-01-31 Thread Mike Clarke

On Saturday 30 January 2010, Kurt Buff wrote:

 For make, do the following, after csup (or an alternative):

      cd /usr/ports
      make search name=samba | less
 or
      cd /usr/ports
      make search key=samba | less

 Then browse that list to see what most particularly applies to your
 needs.

Or, for more compact output, try this script:

#!/bin/sh
cd /usr/ports
make search name=$1 | egrep ^(Port|Path|Info|Moved) | less

-- 
Mike Clarke
___
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: Pain finding packages

2010-01-31 Thread krad

On 30 January 2010 23:42, Kurt Buff kurt.b...@gmail.com wrote:

 On Sat, Jan 30, 2010 at 10:48, Joe Springer joe...@yahoo.com wrote:
  Hi.
 
  I am very new to FreeBSD with several years of Linux experience. After
 installed FreeSDB for the first time, I wanted to install some packages. For
 example, samba.
 
  I found that
 
pkg_add -r samba
 
  fails. I need to know specifically the samba version to install it.
 
  To install, I needed do this:
pkg_add -r samba3
 
  This is difficult. Do I need to look up every package in advance on your
 website to understand what version I need to install?
 
  Isn't there a way to specify Install the latest version of some package
 that is appropriate to the version of my installed FreeBSD?
 
  Thanks,
  Joe

 Not really.

 However, you should have installed a copy of the ports tree during the
 creation of your machine.

 Here are your tools: csup (or portsnap, either of which will keep your
 ports tree current), portupgrade (or portmaster or one of a couple of
 others, to upgrade your current ports) and make. csup is native, and
 portupgrade seems to be more commonly used than the others of its
 kind.

 For make, do the following, after csup (or an alternative):

 cd /usr/ports
 make search name=samba | less
 or
 cd /usr/ports
 make search key=samba | less

 Then browse that list to see what most particularly applies to your needs.


 HTH,

 Kurt
 ___
 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



he is a one liner to update your ports tree

csup -h cvsup.uk.FreeBSD.org  /usr/share/examples/cvsup/ports-supfile

you might want to replace uk with your country code though
___
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: Help! Upgrade from fbsd 5.4 to 8.x

2010-01-31 Thread Volodymyr Kostyrko


On 31.01.2010 06:08, Jeff Mitchell wrote:


Strikes me most people will recommend (3) -- nice big new drive, no risk
of destroying a working machine (can always slap old drive back in),
easy migration of service by service, etc and so on. Strikes me as a
PITA, but then again .. the others are probably all PITAs as well given
the age of the box. Something will break, so maybe its best to just
start fresh with a nice new install and go from there.


Get a stick of flash, build system, install it on the flash and boot 
from it. Try to keep all of your old binaries - I personally don't think 
that all what you have installed will work nowadays. Keeping binaries 
gives you a choice to make a 5.4 jail and put there everything you can't 
install from ports.



*ugh* but that'll teach me to stay on top of it more :)

Aside -- whats the recommended way to stay on top of upgrades anyway? It
used to be a tortuous process back 5 years ago, but hopefully things are
much more streamlined now .. nightly 'make upgrade' ftw :)


Personally I have one computer running X_STABLE or switching to 
X_CURRENT before release. When I see that everything on that machine is 
safe and sound I try to update (after RELEASE of course) least crucial 
servers and so on. By the time I move on to mission critical servers I 
have already found all smelly places. When I was moving from 7.2 to 8.0 
it was just:


# cd /usr/src
# idprio 15 make -j8 buildworld buildkernel  make installkernel 
installworld

# cd /usr/ports/misc/compat7x ; make install clean
# shutdown -r now
# cd /usr/src ; yes | make delete-old ; yes | make delete-old-libs
# portupgrade -fr 'date of kernel compile'

This can sound silly to install kernel and world at once but in this 
situation most of my servers are on ZFS, and ZFS won't come up if you 
boot 8.0 kernel over 7.2 userland - you just need to have correct libs 
installed.


--
Sphinx of black quartz judge my vow.

___
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: Help! Upgrade from fbsd 5.4 to 8.x

2010-01-31 Thread Erich Dollansky

Hi,

I did recently an unplaned update of a machine out of the same time.

You will face so many changes that simply setting up the machine newly might be 
less work.

Of course, do a good backup to at least two media and then install the new 
version.

One thing I experienced was a bit strange. 8.0 did not support my old USB 
hardware. I am running now 7.2 on the machine without problems.

Remember, the USD stack was rewritten from scratch.

I rescuded as much as possible from the old hard disk and copied it onto the 
new one, took the sources, compiled them, run mergemaster and it was working 
again with the exception of the group file. Ok, an editor fixed the problem.

As the problem became obvious while rebooting into the new kernel, you whould 
be able to switch back to your old kernel and then move back to 7.

I did not have this option.

Erich
On 31 January 2010 pm 12:08:05 Jeff Mitchell wrote:
 
   Hello my friends,
 
   I've just noticed one of my beloved headless shell boxen is 
 FreeBSD 5.4; its a workhorse I've been neglecting far too long and I'd 
 really like to bring it up to 'current' (say fbsd 8.x). For awhile it was 
 held back by very specific applications I had to support, but I'm in the 
 clear now.
 
   Given the age of the installation, I'm wondering what the 
 recommended upgrade path would be.
 
   ie: This machine has a lot going on .. wiki's (ie: apache et al), 
 mysql databases, mailing lists, and a dozen hand rolled applications. 
 (Hey, someone has to write custom emulators of ancient systems to keep 
 BBSes alive, right?) Naturally, /etc is modified all to hell, and I'm 
 terrified of any automated upgrades for fear random things would just not 
 work later. Especially with the age... Things work great, but I worry 
 about security naturally, and keeping up with patches or installing 
 anything new is a nightmare due to dependancies.
 
   o I should be able to identify most important changes and data; 
 /etc, /home, the kernel build path so I've got the old kernel conf files I 
 used for this machine (yay!), /usr/local was used instead of polluting 
 /usr-proper, etc.
 
   o I'd love if I coudl do an upgrade, and things would still work; 
 I mean, from samba configuration etc and so on, eveyrthign is great. I 
 realize this is unlikely though .. upgrading services likely means conf 
 changes all over the random place, etc.
 
   o Some of the executables on this box are without source but I 
 still need them to run; short of moving them to a VM and doing some 
 voodoo, what are the chances a binary built for fbsd 5.x works fine in 
 8.x? (earlier fbsd's had the break between gcc versions, but I'm rather 
 hoping thats not a problem here.)
   gcc (GCC) 3.4.2 [FreeBSD] 20040728
 
   The obvious options are..
 
   1 - upgrade step by step; go from fbsd 5.4 to 6.4 (say) to 7.2 
 (say) to 8.0
 
   2 - one big-ass upgrade from 5.4 to 8 (*fear*)
 
   3 - yank the drive, slap a giant new fat drive in there, do a full 
 fbsd 8.0 install, and then migration from old drive as needed
 
   Strikes me most people will recommend (3) -- nice big new drive, 
 no risk of destroying a working machine (can always slap old drive back 
 in), easy migration of service by service, etc and so on. Strikes me as a 
 PITA, but then again .. the others are probably all PITAs as well given 
 the age of the box. Something will break, so maybe its best to just start 
 fresh with a nice new install and go from there.
 
   *ugh* but that'll teach me to stay on top of it more :)
 
   Aside -- whats the recommended way to stay on top of upgrades 
 anyway? It used to be a tortuous process back 5 years ago, but hopefully 
 things are much more streamlined now .. nightly 'make upgrade' ftw :)
 
   jeff
 
 --
 If everyone would put barbecue sauce on their food, there would be no war.
 ___
 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
 
 


___
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: Help! Upgrade from fbsd 5.4 to 8.x

2010-01-31 Thread Erich Dollansky

Hi,

On 31 January 2010 pm 19:18:35 Volodymyr Kostyrko wrote:
 On 31.01.2010 06:08, Jeff Mitchell wrote:
 
  Strikes me most people will recommend (3) -- nice big new drive, no risk
  of destroying a working machine (can always slap old drive back in),
  easy migration of service by service, etc and so on. Strikes me as a
  PITA, but then again .. the others are probably all PITAs as well given
  the age of the box. Something will break, so maybe its best to just
  start fresh with a nice new install and go from there.
 
 Get a stick of flash, build system, install it on the flash and boot 
 from it. Try to keep all of your old binaries - I personally don't think 

hardware running 5.4 typically will not boot from USB.

Erich
___
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

knutclient-0.9.4 (sysutils/knutclient) - Cannot compile

2010-01-31 Thread Elias Chrysocheris

Hello,

Today I set up my system to monitor my UPS using NUT (sysutils/nut). 
Everything went smoothly. I also noticed that there is a KDE client for NUT, 
named knutclient, and it lies at sysutils/knutclient, so I decided to give it 
a try.

Unfortunately it cannot complete the compilation, due to an error ./configure: 
Can't open ./configure: No such file or directory

The full copy/paste of the process is at 
http://paste.gr/rffb5

Any hints?

Thank you in advance
Elias
___
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: Help! Upgrade from fbsd 5.4 to 8.x

2010-01-31 Thread Robert Huff


Erich Dollansky writes:

  Remember, the USD stack was rewritten from scratch.

It it my understanding that in most cases the new USB stack
should ve compatible with the old USB stack, at least to the extent
that programs that compile and run under $OldUSB should compile
and run under $NewUSB out of the box.


Robert Huff

___
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: Problems with make clean

2010-01-31 Thread Frank Wißmann


Kevin Kinsey schrieb:

Frank Wißmann wrote:

Hi, Beasties!
I just installed the new VirtualBox through ports. It worked fine, but 
now I have trouble cleaning the directory. Neither make clean nor a 
rm -rf work/ do what they are supposed to. Here is the output:


rm: 
work/virtualbox-3.0.51r22902/out/freebsd.amd64/debug/obj/VBoxRT/VBox: 
Directory not empty


No explanation, sorry.  Have you tried

$chflags -R nosch work
$rm -rf work

?


Hi, Kevin!
Of course I did it. But the result was the same: no removal possible. 
I'm still confused.

Thanks for your thoughts and have a nice sunday whereever you are!

Greetings Frank

--
GU d- s:+ a+ C+$ UBS$ P L- !E--- W N+@ !o K--? !w--- O !M- !V- PS+ PE 
Y? !PGP- t+ 5 X !R tv- b++ DI !D G e h+ r- y?


When pack meets pack in the jungle
and no one will move from the trail
wait till the leaders have spoken
it may be fair words shall prevail

(Rudyard Kipling)
___
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: Help! Upgrade from fbsd 5.4 to 8.x

2010-01-31 Thread Volodymyr Kostyrko


On 31.01.2010 13:45, Erich Dollansky wrote:

Strikes me most people will recommend (3) -- nice big new drive, no risk
of destroying a working machine (can always slap old drive back in),
easy migration of service by service, etc and so on. Strikes me as a
PITA, but then again .. the others are probably all PITAs as well given
the age of the box. Something will break, so maybe its best to just
start fresh with a nice new install and go from there.


Get a stick of flash, build system, install it on the flash and boot
from it. Try to keep all of your old binaries - I personally don't think


hardware running 5.4 typically will not boot from USB.


Not totally true. 5.4 was released in 2005 whereas newest motherboard 
with which I faced personally problems booting from USB was from 2003. 
And it actually declares that it can boot from USB.


However it's quite possible the hardware would not boot from USB stick. 
This way 8.0 kernel can be compiled with specifically setting that it 
should take root from other fs - USB stick or formatted swap. Swap can 
be too small. USB can be not the choice too - on the mentioned 
motherboard system freezes on boot when any USB drive is present.


--
Sphinx of black quartz judge my vow.

___
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: Generating normally distributed random numbers.

2010-01-31 Thread Jason Lenthe


 I am working on a project where I have the need to generate normally
 distributed random positive integers, preferably unsigned 64 bit (or
 even longer if possible) integers. More specifically, I will need the
 ability to supply the expected value and the standard deviation for the
 desired distribution, so a standard normal distribution will not do.
 
 Is there anyone out there who knows how to accomplish this? I have no
 idea whatsoever, and for all I know there may already be a function that
 does this in the math library. I'm quite accomplished when it comes to
 math, but strangely I've never programmed computers for it.

You won't any functions to do this in the standard C or C++ libraries
(though you can readily build on rand()/rand_r()) Java has
java.util.Random.nextGaussian().  Boost has normal_distribution.hpp.

If you're going to do it yourself, usually normal deviates are generated
using the polar method
(http://en.wikipedia.org/wiki/Marsaglia_polar_method).  If you really
want to read up on this topic see Chapter 3 of Knuth's Art of of
Computer Programming.

The polar method is really designed for floating point numbers since you
need log() but you could always round the values to the nearest integer.
   Getting getting normal deviates bigger than 64 bits could be a real
challenge.

A generator for a standard normal distribution is readily adapted to any
normal distribution by multiplying by the standard deviation and adding
the mean.

Sincerely,
Jason

___
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: Nehelem 64 bit, kern conf and /etc/make.conf

2010-01-31 Thread b. f.

I just installed FreeBSD 8.0 (amd64) onto my new Nehalem-based system.

CPU: Intel(R) Xeon(R) CPU L5506 @ 2.13GHz (2128.00-MHz K8-class CPU)
Origin = GenuineIntel Id = 0x106a5 Stepping = 5

Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE

Features2=0x9ce3bdSSE3,DTES64,MON,DS_CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,DCA,SSE4.1,SSE4.2,POPCNT
AMD Features=0x28100800SYSCALL,NX,RDTSCP,LM
AMD Features2=0x1LAHF
TSC: P-state invariant

I am now in the process of configuring the kernel config file.

A few questions;

1. Is the kernel config file I want to modify
/usr/src/sys/amd64/conf/GENERIC ? (Copy that file as /root/PORKY, and
set up a symlink from /usr/src/sys/amd64/conf to /root/PORKY.)

You don't have to do this: you could just use GENERIC. But if you
want to build a custom kernel, and you are not familiar with all of
the kernel options, GENERIC is a good starting point.

2. What should I set this line to:
cpu HAMMER
Right now it's HAMMER, I have no idea what Hammer is. What would be
the best thing to set it to? I want to be as specific as possible for
my CPU type.

Leave this alone. If you change it, you will break your kernel. It's
not meant to be customized: it's just a name that was chosen because
it happened to be AMD's prototype 64-bit CPU at the time the amd64
port was being written.

3. The instructions here:
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-config.html
mention a line like this:
machinei386
(which would probably by amd64 in my case), but the machine line
is missing entirely from GENERIC conf file. Should I add it?

No, leave it alone. The documentation is outdated; this option is now
set in DEFAULTS, which is a small list of very important stuff that
every kernel of a certain architecture must contain in order to
function properly. It is not meant to be customizable.

4. In /etc/make.conf, I'm used to having, for example:
CPUTYPE?=core2
What would be my CPU in this case (Xeon L5506)? I know this line is
not necessary, but I'd like to set it to the most specific kind of CPU
possible for my case to gain any optimizations, so long as it does not
make my system unstable.

This option is only used to set the flags for the C and C++ compilers.
The base system compiler for FreeBSD 7-9 is a patched version of gcc
4.2, and is hooked up to a patched version of binutils 2.15. This
compiler suite and tool-chain are not new enough to take full
advantage of your CPU: the best you can do is set it to auto-detect
your CPU, or hard-code it to the most modern compatible CPU that
existed when the compiler suite and tool-chain were written. However,
some people have started to use newer compilers and tool-chains from
FreeBSD Ports (some ports even require it), and if you do that, you
may need a different value. Probably, your best bet is to use:

CPUTYPE?= native

and to check to make sure that the base system compiler is actually
equating this with 'nocona', and enabling all of your SIMD extensions
that it supports. This won't make a great deal of difference for
kernel performance, but it will affect other base system programs and
ports if you are using CFLAGS with -march or other optimization 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: Generating normally distributed random numbers.

2010-01-31 Thread Rolf Nielsen


On 2010-01-31 15:53, Jason Lenthe wrote:



I am working on a project where I have the need to generate normally
distributed random positive integers, preferably unsigned 64 bit (or
even longer if possible) integers. More specifically, I will need the
ability to supply the expected value and the standard deviation for the
desired distribution, so a standard normal distribution will not do.

Is there anyone out there who knows how to accomplish this? I have no
idea whatsoever, and for all I know there may already be a function that
does this in the math library. I'm quite accomplished when it comes to
math, but strangely I've never programmed computers for it.



Thank you for your suggestions. I haven't yet looked too carefully into 
them, so I haven't decided which approach to use. But your suggestions 
have given me ideas to work on.


Thanks,

Rolf Nielsen
___
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

VirtualBox doesn't start

2010-01-31 Thread Frank Wißmann


Hi, folks!
I want to launch my freshly installed VB with the run-command under 
KDE 3.5.10, but it won't start. All I get is Command can't be executed 
in german. I also tried with full pathname 
/usr/local/lib/virtualbox/VboxBFE, but that doesn't work either.

Where should I look for a solution?

Greetings Frank

--
GU d- s:+ a+ C+$ UBS$ P L- !E--- W N+@ !o K--? !w--- O !M- !V- PS+ PE 
Y? !PGP- t+ 5 X !R tv- b++ DI !D G e h+ r- y?


When pack meets pack in the jungle
and no one will move from the trail
wait till the leaders have spoken
it may be fair words shall prevail

(Rudyard Kipling)
___
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

57 matches

Mail list logo