Linux DRI (and Google Earth)

2010-09-12 Thread Andrea Venturoli

Hello.

What's the status of 3d hardware acceleration in Linux emulation?
I'm running 8.1R/i386 and I was finally able to get DRI working (with 
native software) on my Radeon HD 4200.
So I installe Google Earth, but it's warning that it will use software 
rendering and is, of course, slow.


%pkg_info|grep linux
linux-f10-dri-7.2_1 Mesa libGL runtime libraries and DRI drivers (Linux 
Fedora
linux-f10-expat-2.0.1 Linux/i386 binary port of Expat XML-parsing 
library (Linux
linux-f10-fontconfig-2.6.0 An XML-based font configuration API for X 
Windows (Linux Fe

linux-f10-xorg-libs-7.4_1 Xorg libraries (Linux Fedora 10)
linux_base-f10-10_2 Base set of packages needed in Linux mode for 
i386/amd64 (L


I had linux-dri-7.4_1 installed by default, but tried switching to 
linux-f10-dri-7.2_1; nothing changed.


 bye  Thanks
av.
___
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: Linux DRI (and Google Earth)

2010-09-12 Thread David DEMELIER
2010/9/12 Andrea Venturoli m...@netfence.it:
 Hello.

 What's the status of 3d hardware acceleration in Linux emulation?
 I'm running 8.1R/i386 and I was finally able to get DRI working (with native
 software) on my Radeon HD 4200.
 So I installe Google Earth, but it's warning that it will use software
 rendering and is, of course, slow.

 %pkg_info|grep linux
 linux-f10-dri-7.2_1 Mesa libGL runtime libraries and DRI drivers (Linux
 Fedora
 linux-f10-expat-2.0.1 Linux/i386 binary port of Expat XML-parsing library
 (Linux
 linux-f10-fontconfig-2.6.0 An XML-based font configuration API for X Windows
 (Linux Fe
 linux-f10-xorg-libs-7.4_1 Xorg libraries (Linux Fedora 10)
 linux_base-f10-10_2 Base set of packages needed in Linux mode for i386/amd64
 (L

 I had linux-dri-7.4_1 installed by default, but tried switching to
 linux-f10-dri-7.2_1; nothing changed.

  bye  Thanks
        av.
 ___
 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


The version 7.4 of DRI hasn't the support of hardware acceleration of
radeon hd cards. We need to update the linux mesa port to 7.6 to get
it.

Cheers,

-- 
Demelier David
___
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


AMD SMBus

2010-09-12 Thread Andrea Venturoli

Any chance of enabling this?
(Google was unfriendly :-)

no...@pci0:0:20:0:  class=0x0c0500 card=0x37001565 chip=0x43851002 
rev=0x3c hdr=0x00

vendor = 'ATI Technologies Inc. / Advanced Micro Devices, Inc.'
device = 'ATI SMBus (ATI RD600/RS600)'
class  = serial bus
subclass   = SMBus


 bye  Thanks
av.
___
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: Upgrading packages - portupgrade confusion

2010-09-12 Thread Kaya Saman

[...]

Have you refreshed the ports tree(s) with csup using the same supfile to
ensure the ports trees are up to date ( and therefore identical)? Since you
are using portugrade, as I do, this is what I do to see what needs to be
done:

I cd to /usr/sup which is where I keep my supfiles and the housekeeping.
Then using this command sequence will refresh the ports tree, the ports
index database, and ensure the package database is clean and synced.
Portversion then just tells you with a  symbol any that are old and in
need of an update.

csup -L 2 ports  portsdb -uF  pkgdb -u  portversion

where ports above is my supfile for ports refresh and looks like this:

*default host=cvsup.nl.freebsd.org
*default base=/usr
*default prefix=/usr
*default release=cvs tag=.
*default delete use-rel-suffix compress
ports-all

Then a portupgrade -a as required. If all symbols in the right column are
= everything is up to date and nothing is required. Adjust server location
for mirror near you (or one that works best).

-Mike



___
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
   


Thanks alot Mike for the response!!

I didn't actually refresh the ports tree so I'm gona have to do that.

The thing I don't quite understand though is that if the ports tree gets 
refreshed, do the packages get upgraded or will I need to rebuild them??


I slightly recall the csup commnad, however I've never actually 
performed an inplace upgrade of a package in BSD. Only done this kind of 
thing in Linux - Debian/Ubuntu, CentOS and Solaris - OpenSolaris, 
Belenix where they have package managers.


What's the process for upgrading a package? make reinstall clean??

Many Thanks


Kaya
___
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: Upgrading packages - portupgrade confusion

2010-09-12 Thread Jerry
On Sun, 12 Sep 2010 14:34:52 +0300
Kaya Saman kayasa...@gmail.com articulated:

 [...]
  Have you refreshed the ports tree(s) with csup using the same
  supfile to ensure the ports trees are up to date ( and therefore
  identical)? Since you are using portugrade, as I do, this is what I
  do to see what needs to be done:
 
  I cd to /usr/sup which is where I keep my supfiles and the
  housekeeping. Then using this command sequence will refresh the
  ports tree, the ports index database, and ensure the package
  database is clean and synced. Portversion then just tells you with
  a  symbol any that are old and in need of an update.
 
  csup -L 2 ports  portsdb -uF  pkgdb -u  portversion
 
  where ports above is my supfile for ports refresh and looks like
  this:
 
  *default host=cvsup.nl.freebsd.org
  *default base=/usr
  *default prefix=/usr
  *default release=cvs tag=.
  *default delete use-rel-suffix compress
  ports-all
 
  Then a portupgrade -a as required. If all symbols in the right
  column are = everything is up to date and nothing is required.
  Adjust server location for mirror near you (or one that works best).
 
  -Mike
 
 Thanks alot Mike for the response!!
 
 I didn't actually refresh the ports tree so I'm gona have to do that.
 
 The thing I don't quite understand though is that if the ports tree
 gets refreshed, do the packages get upgraded or will I need to
 rebuild them??

You have to rebuild them.

 I slightly recall the csup commnad, however I've never actually 
 performed an inplace upgrade of a package in BSD. Only done this kind
 of thing in Linux - Debian/Ubuntu, CentOS and Solaris - OpenSolaris, 
 Belenix where they have package managers.
 
 What's the process for upgrading a package? make reinstall clean??

If using a port maintenance application such as portupgrade or
portmanager, you could simply do the following:

portupgrade -a or portmanager -u depending on what application you
are using. Switching between multiple port maintenance applications is
not the worse thing you could do; however, I would not recommend it as
an everyday occurrence.

If doing it manually, you could just do:

make  make deinstall  make reinstall  make distclean

There are other variations of course. I would recommend that you run:
make config in the port's home directory prior to building it for the
first time. there might be some useful features that you want to turn
on or off.

-- 
Jerry ✌
freebsd.u...@seibercom.net

Disclaimer: off-list followups get on-list replies or get ignored.
Please do not ignore the Reply-To header.
__
Minicomputer:
A computer that can be afforded on the budget of a middle-level
manager.
___
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: Upgrading packages - portupgrade confusion

2010-09-12 Thread Michael Powell
Kaya Saman wrote:

 [...]

 csup -L 2 ports  portsdb -uF  pkgdb -u  portversion

To elaborate a little. csup -L 2 ports is what refreshes the ports tree. 
Portupgrade is a third party app you can install to assist in automating the 
updating process. Once you've installed portupgrade there are man pages for 
portsdb, pkgdb, and portversion to see what the switches described above do. 
The commands above are just strung together to prepare a system for 
updating. portupgrade -a is actually what does the actual updating.

There are other tools as well, I'm just not as familiar with them. I think 
the other one is called portmaster. It may even be better, I don't know as I 
tend to stick with what I know as long as it keeps doing the job.  

[snip]
 
 I didn't actually refresh the ports tree so I'm gona have to do that.
 
 The thing I don't quite understand though is that if the ports tree gets
 refreshed, do the packages get upgraded or will I need to rebuild them??

I don't know if I can properly explain well enough, but I'll take a stab at 
it anyways. But I believe the first answer here would be no. Refreshing the 
ports tree does not install or update any installed software. 

I kind of keyed in on your mentioning of portupgrade. Portupgrade is a tool 
for automating the upgrading of installed software. While I believe it, and 
possibly portmaster can operate on pre-built packages I myself stopped using 
packages a long time ago. I compile everything.

A pre-built package is built from the same ports system that you would use 
if you were compiling locally yourself. It's just someone else has done it 
for you. The thing to know is that in either situation, e.g. pre-built 
package or compile it yourself the ports tree is where the versioning and 
dependency tracking happens.

There is more information in the Handbook, and probably presented better 
there than I can. It is spread out in several locations however. It may not 
be immediately apparent when reading the How to install software section 
that you also need to read the other sections further down that explain 
csup, portmaster, etc. The main thing we will keep reiterating though is the 
first step for updating installed apps is always refresh the ports tree 
first.
 
 I slightly recall the csup commnad, however I've never actually
 performed an inplace upgrade of a package in BSD. Only done this kind of
 thing in Linux - Debian/Ubuntu, CentOS and Solaris - OpenSolaris,
 Belenix where they have package managers.
 
 What's the process for upgrading a package? make reinstall clean??
 

Since I don't use packages my vantage point is centered around compiling 
locally myself. However, most of what I describe applies to both situations. 
Typically the first thing to do is update/refresh the ports tree. Should you 
determine something needs to be updated the manual approach would be to 
change to the directory of the app in ports system and do make, followed by 
make deinstall, and then make reinstall. The deinstall/reinstall leaves your 
configurations for installed apps in place.

Portupgrade is a tool that automates this. After refreshing the ports tree 
the portupgrade -a command will pretty much do what was described in the 
previous paragraph automagically. It isn't perfect and sometimes it hiccups. 
I've noticed that doing this more often so that only a few out of date apps 
need upgrading at any one time is smoother. It's when you have a hundred 
things that are really old and out of date because updating has been 
infrequent is when you are most likely to experience trouble.

Hope this helps. I'm not the best at explaining things, but the Handbook is 
a most excellent resource to be studied extensively. It is written much 
better than anything I can manage. And while much of it may seem cryptic at 
first glance, most of what you need to know is in there.

-Mike



___
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: sysinstall vs gmirror

2010-09-12 Thread Matthew Seaman
On 12/09/2010 05:09:04, per...@pluto.rain.com wrote:
 How do I get sysinstall to recognize a gmirror?
 
 I've created the mirror -- which currently has only one provider --
 using Fixit#, followed by
 
 Fixit# ln -s /dist/boot/kernel /boot
 Fixit# gmirror load
 
 after which /dev/mirror/gm0{,a,b} exist.  However, even after
 rescanning the disks, sysinstall doesn't include gm0 in its
 drive list.  I also tried:
 
 Fixit# ( cd /dev  ln -s mirror/* .  ll gm* )
 lrwxr-xr-x  1 root  0  10 Sep  6 10:48 gm0@ - mirror/gm0
 lrwxr-xr-x  1 root  0  10 Sep  6 10:48 gm0a@ - mirror/gm0a
 lrwxr-xr-x  1 root  0  10 Sep  6 10:48 gm0b@ - mirror/gm0b
 
 in case sysinstall looks only in /dev itself and not in any
 subdirectories, and that didn't help.  I even tried:
 
 Fixit# ( cd /dev  ln -s mirror/gm0 ar0 \
 for p in a b d e ; \ 
do ln -s mirror/gm0$p ar0$p ; done  ll ar* )
 lrwxr-xr-x  1 root  0  10 Sep  6 10:48 ar0@ - mirror/gm0
 lrwxr-xr-x  1 root  0  10 Sep  6 10:48 ar0a@ - mirror/gm0a
 lrwxr-xr-x  1 root  0  10 Sep  6 10:48 ar0b@ - mirror/gm0b
 lrwxr-xr-x  1 root  0  10 Sep  6 10:48 ar0d@ - mirror/gm0d
 lrwxr-xr-x  1 root  0  10 Sep  6 10:48 ar0e@ - mirror/gm0e
 
 in case sysinstall looks only for names of known disk drivers,
 and that didn't help either.

I don't think sysinstall will do what you want.

However, what is your ultimate goal?  To install a system with a gmirror
root drive?  You can do that by installing direct to one of your drives
(ie ad0s1* or da0s1*) in the usual way and then converting the system
into a gmirror.  The Onlamp article by Dru Lavigne is the best
referrence here:

http://onlamp.com/pub/a/bsd/2005/11/10/FreeBSD_Basics.html

Or else you can boot into the Fixit system, set up mirroring etc. and
then work through the rest of the installation process by hand.  The
install sets are just split up tarballs and it's pretty easy to extract
a copy of a system from them.

Cheers,

Matthew

-- 
Dr Matthew J Seaman MA, D.Phil.   7 Priory Courtyard
  Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
JID: matt...@infracaninophile.co.uk   Kent, CT11 9PW



signature.asc
Description: OpenPGP digital signature


Re: Upgrading packages - portupgrade confusion

2010-09-12 Thread Kaya Saman

Hi Jerry and Michael,

thanks for all the advise and information!!

I think I was confusing terminologies a little

I was trying to imply that I have been building from ports all this time 
and *not* using pkg_add to obtain pre-built packages. I think mainly 
it's just that I've been using package managers too much with Linux and 
OpenSolaris distros that it got burned into my brain. not to mention 
that yesterday was a 14 hour shift without break which didn't help.


The thing I don't quite understand though is that if the ports tree

 gets refreshed, do the packages get upgraded or will I need to
 rebuild them??


You have to rebuild them.


Does this apply to ports too??


portupgrade -a or portmanager -u depending on what application you
are using. Switching between multiple port maintenance applications is
not the worse thing you could do; however, I would not recommend it as
an everyday occurrence.


Ok so portupgrade -a upgrades all ports according to the manual.


On 09/12/2010 03:52 PM, Michael Powell wrote:

[...]
To elaborate a little. csup -L 2 ports is what refreshes the ports tree.
Portupgrade is a third party app you can install to assist in automating the
updating process. Once you've installed portupgrade there are man pages for
portsdb, pkgdb, and portversion to see what the switches described above do.
The commands above are just strung together to prepare a system for
updating. portupgrade -a is actually what does the actual updating.

There are other tools as well, I'm just not as familiar with them. I think
the other one is called portmaster. It may even be better, I don't know as I
tend to stick with what I know as long as it keeps doing the job.

[
Ok, so if I understand correctly now is that the csup command refreshes 
the ports tree while portupgrade upgrades the actual port itself


eg:

cd /usr/ports/*/nano
make install clean

although not the case but say if this was to build version 1.8 of the 
Nano text editor, running:


csup -L 2
portupgrade nano

would upgrade the installed version to 1.9??

Of course the current version of Nano is totally different I am just 
trying to understand here!!



[...]
I don't know if I can properly explain well enough, but I'll take a stab at
it anyways. But I believe the first answer here would be no. Refreshing the
ports tree does not install or update any installed software.

I kind of keyed in on your mentioning of portupgrade. Portupgrade is a tool
for automating the upgrading of installed software. While I believe it, and
possibly portmaster can operate on pre-built packages I myself stopped using
packages a long time ago. I compile everything.

   
Ok I think this practically explains what I've just been trying to say 
above.


[...]
Hope this helps. I'm not the best at explaining things, but the Handbook is
a most excellent resource to be studied extensively. It is written much
better than anything I can manage. And while much of it may seem cryptic at
first glance, most of what you need to know is in there.

   

Yep I think this helps a lot!!! :-)


-Mike



___
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
   


Many thanks and best regards,


Kaya
___
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: Upgrading packages - portupgrade confusion

2010-09-12 Thread Warren Block

On Sun, 12 Sep 2010, Kaya Saman wrote:

The thing I don't quite understand though is that if the ports tree gets 
refreshed, do the packages get upgraded or will I need to rebuild them??


The ports tree is just build instructions, so updating it doesn't update 
any installed applications.  It does let you use a program to see which 
installed applications need to be updated, like pkg_version or 
portversion.


Here's a document I've been working on lately about upgrading ports. 
I'm not sure it's really there yet, but it covers the basics:

  http://www.wonkity.com/~wblock/docs/html/portupgrade.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: Upgrading packages - portupgrade confusion

2010-09-12 Thread Michael Powell
Kaya Saman wrote:

[snip] 
 
 The thing I don't quite understand though is that if the ports tree
  gets refreshed, do the packages get upgraded or will I need to
  rebuild them??
 
 You have to rebuild them.
 
 Does this apply to ports too??

Yes. A package is just a port that someone has compiled into a pre-built 
binary package for use with pkg_add. These binary packages are placed on ftp 
servers where pkg_add may download from and install. 

A port is just you doing the compiling locally yourself using the ports 
system. The installed result is the same, except for one thing. When a 
package is built some build options may have been selected as defaults while 
others were excluded. When you build the port locally you have complete 
control over all options.
 
 portupgrade -a or portmanager -u depending on what application you
 are using. Switching between multiple port maintenance applications is
 not the worse thing you could do; however, I would not recommend it as
 an everyday occurrence.
 
 
 Ok so portupgrade -a upgrades all ports according to the manual.
 
[snip]

 Ok, so if I understand correctly now is that the csup command refreshes
 the ports tree while portupgrade upgrades the actual port itself

Update the ports tree first! csup -L 2 ports - this file ports is a 
supfile. An example of a supfile was included in a previous mail. More 
detailed info in the Handbook.
 
 eg:
 
 cd /usr/ports/*/nano
 make install clean

cd /usr/ports/editors/nano/
make install clean

This installs nano when it was not installed before.

The manual method to update would be:
(with a freshly updated ports tree)

cd /usr/ports/editors/nano/
make  make deinstall  make reinstall

 
 although not the case but say if this was to build version 1.8 of the
 Nano text editor, running:
 
 portupgrade nano
 
 would upgrade the installed version to 1.9??

Yes - provided you had installed portupgrade and are using an up to date 
ports tree. If your ports tree is as old as the old version of nano then as 
far as FreeBSD is concerned it does not know of any new version. Refreshing 
your ports tree is where that information comes from.

The utility of automation with portupgrade really comes into play when you 
are trying to update more than one port. One port at a time can be done 
manually as in the above example, but that quickly becomes tiresome when 
there are many.

Sometimes a port may provide a shared library which many other ports depend 
upon. Updating that library may cause dependent apps to break. In such a 
situation portupgrade can recurse and rebuild all apps depending on that 
library so they will be linked against the new.

Another tip: Whenever there are situations which can get sticky most of the 
time notes are placed into a file containing instructions on how to deal 
with the problem. Get into the habit of always reading the UPDATING file 
located in /usr/ports so you will know about these *before* updating.
 
[snip]



___
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: Compiling software with different compiler than cc or clang results in unusable output

2010-09-12 Thread Ian Smith
In freebsd-questions Digest, Vol 327, Issue 11, Message: 4
On Sat, 11 Sep 2010 O. Hartmann ohart...@mail.zedat.fu-berlin.de wrote:
  On 09/11/10 11:43, Andrew Brampton wrote:
   On 11 September 2010 10:28, O. Hartmann
   ohart...@mail.zedat.fu-berlin.de  wrote:
  
   you see me a kind of desperate. I wrote my own a small piece of  
   software in
   C, calculating the orbit and position of astronomical objects, astroids, 
   in
   a heliocentric coordinate system from Keplerian orbital elements. So far.

Don't expect too much accuracy from Keplerian orbits anywhere vaguely 
near Jupiter or Saturn - but yes they're a great place to start from.

   The software calculates the set of points of an ellipse based upon
   ephemeridal datas taken from the Minor Planet Cataloge. Again, so far,
   everything all right. The set of points of an orbit is all right and
   correct. But when it comes to positions at a specific time, then I loose
   hair!

The program mentioned below can generate accurate results for as often 
as every few hours; handy at least for comparing your results over time.

   Compiling this piece of software with FreeBSD's gcc (V4.2) and clang 
   (clang
   devel) on my private and lab's FreeBSD boxes (both most recent FreeBSD
   8.1/amd64), this program does well, the calculated orbital positions are
   very close to professional applications or observational checks. But when
   compiling the sources with gcc44 or gcc45 (same source, same CFLAG 
   setting,
   mostly no CFLAGS set), then there is a great discrepancy. Sometimes when
   plotting positions, the results plotted seconds before differs from the 
   most
   recent. The ellipses are allways correct, but the position of a single 
   point
   at a specific time isn't correct.

Know the feeling; it took Kepler 20 years to get ellipses down pat :)

   I use the GNU autotools to build the package.
  
   I suspekt miscompilations in memory alloction or in some time- or
   mathematical functions like sin, cos.
  
   before I digg deeper I'd like to ask the community for some hints how to
   hunt down such a problem.
  
   regards,
   Oliver
  
   Sounds a cool project. I suspect you are miss-using a feature of C or
   are using uninitialised memory, and with gcc44/45's more aggressive
   optimisations it is getting it wrong. I have three suggestions
  
   1) Use valgrind to check if it finds anything wrong when running your
   program. Check both the good and the bad builds.
  
   2) If your program is made up of multiple C files, then try compiling
   all of the C files with gcc42, but just one at a time with gcc44. This
   way will help you track down exactly which C file has the bug.
  
   3) Finally do some printf debugging to find the first line of code
   that is generating the wrong value.
  
   I hope these suggestions help.
   Andrew
  
  Hello Andrew.
  
  Thanks for your comments, they are worth trying out. I will do so ...
  
  item 2) oh, yes, a very good idea ...
  
  item 3) I did already, the whole software is built up by those printf's.
  
  The problem boiled down to be some problem in the UNIX time routines. I 
  use localtime(3), time(3) and a strftime(3) and strptime(3).
  
  I use a 'wikipedia'-algorithm converting the actual time string into an 
  'epoch' used in astronomical calculations. Compiling this routine with 
  gcc42 and clang everything is all right, compiling it with gcc44 or 
  gcc45 it returns 10 times higher values. I use very 'primitive' cutoffs 
  for casting a double value into an int - I need the integrale value, not 
  the remainings after the decimal point. I will check this again and look 
  forward for a cleaner solution. But isn't this a 'bug'?
  
  I'll try the BETA of the new FreeBSD PathScale compiler if I get some.
  
  Well, I'll report ...

Please do.  Well I can't help at all about the compilers, but I suggest 
having a close look over Steve Moshier's 'Numerical Integration of Sun, 
Moon and Planets' at http://www.moshier.net/ssystem.html

I compiled the contents of http://www.moshier.net/de118i-2.zip as-is on 
a FreeBSD 5.5 system four years ago and it just ran, reproducing closely 
my late '90s results from the then DOS version SSYSTEM.EXE; there are 
#defines for using doubles or long doubles, major asteroids on not, even 
including 'your' asteroid's elements, and test results for comparison.

You could check how your different compilers treat those sources?  Apart 
from that it's very readable code and there's just about every maths and 
trig function imaginable, including quadrant-correct arctans and such.  
And also, of course, Julian Ephemeris Date handling routines .. not to 
mention close-to-JPL positions and velocities over many centuries :)

Good luck.  I'm hoping to revive and extend from my '90s Pascal astro 
programs in FPC soon to chew on 100s of years of ssystem ephemerides. 

HTH, Ian___
freebsd-questions@freebsd.org mailing list

Re: Upgrading packages - portupgrade confusion

2010-09-12 Thread Kaya Saman

Thanks Warren and Michael! :-)

On Sun, 12 Sep 2010, Kaya Saman wrote:

The thing I don't quite understand though is that if the ports tree 
gets refreshed, do the packages get upgraded or will I need to rebuild 
them??


The ports tree is just build instructions, so updating it doesn't update
any installed applications.  It does let you use a program to see which
installed applications need to be updated, like pkg_version or
portversion.

Here's a document I've been working on lately about upgrading ports.
I'm not sure it's really there yet, but it covers the basics:

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


Yep I kinda figured that before even posting and also I knew the 
difference between packages built by pkg_add and compiling fresh from 
ports since I've done a few BSD builds now but the really iffy thing was 
a: communication - which let me down not explaining myself properly and 
b: confusion of how to update


On 09/12/2010 05:36 PM, Michael Powell wrote:

[...]
Yes. A package is just a port that someone has compiled into a pre-built
binary package for use with pkg_add. These binary packages are placed on ftp
servers where pkg_add may download from and install.

A port is just you doing the compiling locally yourself using the ports
system. The installed result is the same, except for one thing. When a
package is built some build options may have been selected as defaults while
others were excluded. When you build the port locally you have complete
control over all options.

   


Ditto :-)


portupgrade -a or portmanager -u depending on what application you
are using. Switching between multiple port maintenance applications is
not the worse thing you could do; however, I would not recommend it as
an everyday occurrence.


Ok so portupgrade -a upgrades all ports according to the manual.

 

[snip]

   

Ok, so if I understand correctly now is that the csup command refreshes
the ports tree while portupgrade upgrades the actual port itself
 

Update the ports tree first! csup -L 2 ports- this file ports is a
supfile. An example of a supfile was included in a previous mail. More
detailed info in the Handbook.
   


This clarifies, I can't believe what's wrong with me today as I seem to 
not be thinking :-(


I picked this up the first time round on a really good production build 
that I made and now I lost all that knowledge oh well working with 
MS can do that to you I guess??




   
[...]

Another tip: Whenever there are situations which can get sticky most of the
time notes are placed into a file containing instructions on how to deal
with the problem. Get into the habit of always reading the UPDATING file
located in /usr/ports so you will know about these *before* updating.

[snip]

   
This is really great advise as I'm kinda in the process of developing 
documentation myself similar to Warren:


http://wiki.optiplex-networks.com/xwiki/bin/view/FreeBSD/

Luckily I build all my systems in jails so is easily managed and doesn't 
blow up the whole system, however I do share the ports tree throughout 
all jails and the base install meaning that things get simplified 
although it can have its own problems such as version inconsistencies etc...


{{PS. this is also due to the fact that I only one available production 
system and can't afford to get more although soon I hope to one day}}


Thanks so much guys and sorry for being so noobish these last 2 days, 
just sorry you all had to put up with it!! :-)


Anyway best regards to all and hopefully mail along side you guys 
helping out others some sunny day in the future :-D



Kaya
___
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 memstick installation

2010-09-12 Thread Morgan Wesström



2010/8/23 Morgan Wesströmfreebsd-questi...@pp.dyndns.biz:

On 2010-08-23 19:34, Friedemann Becker wrote:

Hello,

I have some questions about an installation on a memorystick.

I have (a few weeks still) a very poor internet connection at home
that's unusable for anything beyond email. I tried some hacking on
musescore (yes I know that it can't work, but that's not my problem
for now). Since I don't want to carry missing ports/packages/other
stuff around on a stick everytime I miss something - which takes one
day each - i would like to have a working system (not installation
image) on usb-stick.
Can i use fdimage with the memorystick installation image on windows,
or any hacked versions of it?
And how do turn this stick in a running system?
Or is there any kind of live-stick-images out there, and if it is, how
to move these on the stick (since windows is missing dd and nero
doesn't like burning sticks :-) )

Thanks in advance



Check my old message on how to do this in FreeBSD 7.2. The same
instructions should work for 8.1 too, just change the version references.
http://lists.freebsd.org/pipermail/freebsd-questions/2009-July/201928.html
/Morgan


On 2010-08-26 13:52, Friedemann Becker wrote:

Thanks a lot,
this seems to work. Is there any chance to get this into the faq or
handbook? It's seems way more usefull to me than a live-CD. Best thing
would be putting it into sysinstall, but maybe this is not reallistic.

Best regards,
Friedemann



For the archives - below I've updated my installation guide to work with 
FreeBSD 8.1-RELEASE, GPT and ZFS if anyone finds it useful.


Make sure your usb memory stick is empty and unpartitioned, then plug it 
in and boot from the FreeBSD DVD.


Select your country and keyboard layout.

Enter the Fixit environment and use the live filesystem on your DVD.

Your usb memory stick will most likely be da0 but you can (and should) 
check it with camcontrol devlist before you continue.


Create a new GPT partitioning scheme:
 # gpart create -s gpt da0

Create a 64KiB partition for the zfs bootcode starting at LBA 1920:
 # gpart add -b 1920 -s 128 -t freebsd-boot da0

Create a zfs partition spanning the remainder of the usb memory stick 
and give it a label we can refer to:

 # gpart add -t freebsd-zfs -l FreeBSDonUSB da0

(The starting LBA for the first partition is there to align the 
partitions to the flash memory's erase block size. This is particularly 
important for the main zfs partition. The main partition above will 
start at exactly 1MiB (LBA 2048) which will align it to any erase block 
size used today. This alignment is also of great importance if you use 
this guide to install FreeBSD to one of the newer harddrives using 4096 
byte sectors.)


Install the protective MBR to LBA 0 and the zfs bootcode to the first 
partition:

 # gpart bootcode -b /dist/boot/pmbr -p /dist/boot/gptzfsboot -i 1 da0

Create /boot/zfs (for zpool.cache) and load the zfs kernel modules:
 # mkdir /boot/zfs
 # kldload /dist/boot/kernel/opensolaris.ko
 # kldload /dist/boot/kernel/zfs.ko

Create a zfs pool and set its bootfs property:
 # zpool create zrootusb /dev/gpt/FreeBSDonUSB
 # zpool set bootfs=zrootusb zrootusb

Switch to fletcher4 checksums and turn off access time modifications:
 # zfs set checksum=fletcher4 zrootusb
 # zfs set atime=off zrootusb

Extract at a minimum, base and the generic kernel:
 # cd /dist/8.1-RELEASE/base
 # DESTDIR=/zrootusb ./install.sh
 # cd ../kernels
 # DESTDIR=/zrootusb ./install.sh generic

Delete the empty, default kernel directory and move the generic kernel 
into its place:

 # rmdir /zrootusb/boot/kernel
 # mv /zrootusb/boot/GENERIC /zrootusb/boot/kernel

Make sure the zfs modules are loaded at boot:
 # echo 'zfs_load=YES'  /zrootusb/boot/loader.conf
 # echo 'vfs.root.mountfrom=zfs:zrootusb'  \
/zrootusb/boot/loader.conf

Create /etc/rc.conf. Adjust and add to your own needs:
 # echo 'ifconfig_DEFAULT=DHCP'  /zrootusb/etc/rc.conf
 # echo 'hostname=freebsd'  /zrootusb/etc/rc.conf
 # echo 'keymap=swedish.iso'  /zrootusb/etc/rc.conf
 # echo 'ntpdate_enable=YES'  /zrootusb/etc/rc.conf
 # echo 'sshd_enable=YES'  /zrootusb/etc/rc.conf
 # echo 'zfs_enable=YES'  /zrootusb/etc/rc.conf

Setup your time zone:
 # cp /zrootusb/usr/share/zoneinfo/Europe/Stockholm \
/zrootusb/etc/localtime

Create an empty fstab to avoid startup warnings:
 # touch /zrootusb/etc/fstab

Set the root password in the new environment:
 # cd
 # chroot /zrootusb /bin/sh
 # passwd root
 # exit

Copy zpool.cache:
 # cp /boot/zfs/zpool.cache /zrootusb/boot/zfs

Unmount the filesystem and set its mountpoint:
 # zfs unmount -a
 # zfs set mountpoint=legacy zrootusb

Exit SYSINSTALL and reboot. You now have a fully functional and bootable 
FreeBSD installation on your usb memory stick.



Regards
Morgan Wesström
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any 

Re: fsck reports errors on clean filesystem (mounted rw)

2010-09-12 Thread Robert Bonomi
 From owner-freebsd-questi...@freebsd.org  Fri Sep 10 17:51:18 2010
 From: cronfy cro...@gmail.com
 Date: Sat, 11 Sep 2010 02:27:46 +0400
 To: freebsd-questions freebsd-questions@freebsd.org
 Subject: fsck reports errors on clean filesystem (mounted rw)

 Hello.

 I ran fsck on my filesystems while system was running (partitons were
 mounted rw with moderate FS usage). fsck reported there were errors
 (INCORRECT BLOCK COUNT and others). I decided to reboot to single mode
 and check all filesystems. But in single mode fsck did not find any
 errors.

  1. Can I be sure my filesystem is consistent?

yes.

  2. If fsck reports nonexistent errors (and probably will try to fix
 them if asked), isn't it even danger to run fsck on running system?

They're not non-existant. and they're _not_ errors.  they are 
*EXPECTED* inconsistancies in the _disk-based_ copies of the file-system
meta-data because the 'current' (memory-resident) data is *not* written
to disk at the instant the meta-data changes.

It is a 'non-issue', because the O/S 'knows what it's doing

There are exactly _four_ possible causes of file-system inconsistencies.
  1) You can have an unexpected loss of power, where the CPU stops working
 before it as time to write the above-mentioned 'memory-resident' data 
 to disk.  There are  sub-classes of tis event, to distinguish between
 A utility company outage, somebody accidentally 'pulling the plug', be
 it litterally, or the power on/off switch, and somebody itting the 
 'reset' button.  They all ave te same effect,  the processor can't
 get te 'current' data in memory out to the disk.
  2) you can hve a catastropic O/S failure -- a system 'crash' -- were the
 O/S has discovered an internal inconsistency. _IT_ doesn't trust its
 own data enough to keep running, and takes 'the lesser of two evils'
 route of *not* writing known to be suspect data over the out-of-date
 data on the disk.
  3) 'bit rot' on the phyiscal media itself.  Where what gets read back is
 *not* what was written there earlier.  Modern disk drives detect this
 inside the controller and use embedded ECC info to give the 'right'
 data back, while alerting that the problem exists.
  4) Hardware failures of any of a variety of sorts -- flakey power supply,
 bad RAM memory, failing controller cipes, etc.


Cause 1) can be virtually eliminated by 'good practices', and the use of a UPS
with controlled automatic shutdown
Cause 3) you can 'stay hread of' by monitoring system logs for 'corrected'
errors on magnetic media.
Causes 2) and 4) you can't do much about.

With the exception of cause 3) -everything- leads to sysem crash which
results in the 'preserved' data being inconsistent.  The 'good news' is
that you *know* it happened, and can run the fixit software (fsck) before
letting users back on.


___
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: fsck reports errors on clean filesystem (mounted rw)

2010-09-12 Thread Bruce Cran
On Sun, 12 Sep 2010 16:16:53 -0500 (CDT)
Robert Bonomi bon...@mail.r-bonomi.com wrote:

 There are exactly _four_ possible causes of file-system
 inconsistencies. 1) You can have an unexpected loss of power, where
 the CPU stops working before it as time to write the above-mentioned
 'memory-resident' data to disk.  There are  sub-classes of tis event,
 to distinguish between A utility company outage, somebody
 accidentally 'pulling the plug', be it litterally, or the power
 on/off switch, and somebody itting the 'reset' button.  They all ave
 te same effect,  the processor can't get te 'current' data in memory
 out to the disk. 2) you can hve a catastropic O/S failure -- a system
 'crash' -- were the O/S has discovered an internal inconsistency.
 _IT_ doesn't trust its own data enough to keep running, and takes
 'the lesser of two evils' route of *not* writing known to be
 suspect data over the out-of-date data on the disk.
   3) 'bit rot' on the phyiscal media itself.  Where what gets read
 back is *not* what was written there earlier.  Modern disk drives
 detect this inside the controller and use embedded ECC info to give
 the 'right' data back, while alerting that the problem exists.
   4) Hardware failures of any of a variety of sorts -- flakey power
 supply, bad RAM memory, failing controller cipes, etc.

5. An bug in the filesystem code. I've been seeing UFS corruption in
recently -current, as have others, which isn't associated with crashes
or bad media.

-- 
Bruce Cran
___
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


Services do not start at boot

2010-09-12 Thread Arnaud Bergeron
I have a FreeBSD 8.0-RELEASE installation with a UFS root and a ZFS
pool for data and users.

I have a couple of ports installed (netatalk, mediatomb) to share the
content of the ZFS pool along with sharing it over NFS.

After a fresh boot, the NFS shares do not work, mediatomb is not up
and netatalk runs but does not share anything.  There may be other
things not working properly but those are the ones I notice.

If I manually restart mountd, and the two ports using the rc.d scripts
then everything works correctly until the next restart.

I found this message in the archives which is similar to the problem I
have except that I use dhcp:

http://marc.info/?l=freebsd-questionsm=128354380615514w=2

After checking the log I see that indeed my problem is that these
services start before the network is available and they don't cope
well with that.

As a fix, I added dhclient to the REQUIRE: for NETWORKING and a 'sleep
10' after the dhclient command in the dhclient startup script and made
sure that background_dhclient is NO, and it still doesn't work.  I am
at a loss.

Arnaud
___
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: sysinstall vs gmirror

2010-09-12 Thread perryh
Matthew Seaman m.sea...@infracaninophile.co.uk wrote:

 On 12/09/2010 05:09:04, per...@pluto.rain.com wrote:
  How do I get sysinstall to recognize a gmirror?
  ...
 I don't think sysinstall will do what you want.

It certainly has been less than totally cooperative so far :(

 However, what is your ultimate goal?
 To install a system with a gmirror root drive?

No, to install a system with each of /, /usr, and /var mirrored and
journalled, with each journal kept in the same (mirrored) partition
as its FS -- diagram below.  IIUC, to put the journal in the same
partition with the FS I have to create the journal while the FS is
empty, hence before installing.  (This is all UFS -- 512MB seems a
bit small for ZFS.)

The plan after partitioning the mirror is to create the journals,
then install onto the journalled FS's, and finally to insert the
second half of the mirror after everything else is up and running.

 ... you can boot into the Fixit system, set up mirroring etc. and
 then work through the rest of the installation process by hand.
 The install sets are just split up tarballs and it's pretty easy
 to extract a copy of a system from them.

The part I don't know how to do is partitioning gm0 by hand.
(I suppose it would require some sort of arcane incantations
involving bsdlabel.)  For all its limitations, sysinstall
seems at least to know how to translate a reasonably human-
readable representation of the desired slice and partition
layout into the necessary fdisk and bsdlabel commands.

Someone suggested using the PC-BSD installer, which knows how
to do stuff like this, but when I asked how to do that from a
memstick (rather than from a CD or DVD) I didn't get an answer.

 ad0s2 FreeBSD ad2s2 FreeBSD
  ad0s2a - gm0 -  ad2s2a
 |   
   +-+
   |
   v
  gm0
   gm0a
gm0a.journal [gjournal label gm0a gm0a]  rootFS
   gm0d
gm0d.journal [gjournal label gm0a gm0a]  /var
   gm0e
gm0e.journal [gjournal label gm0a gm0a]  /usr 

There's more to it than this, but I think I know how to do the rest.
The current sticking point is getting the mirror partitioned.
___
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: ipfw fwd and ipfw allow

2010-09-12 Thread Victor Sudakov
per...@pluto.rain.com wrote:
 
  ... the 'fwd ... keep-state' statement does create a useful
  dynamic rule. It contradicts the ipfw(8) man page but works ...
 
 Hopefully someone who understands all this will submit a patch
 for the man page :)

The man page says that the Dynamic rules will be checked at the first
check-state, keep-state or limit occurrence, and the action performed
upon a match will be the same as in the parent rule.

It suggests that if the parent rule is a 'fwd' rule, the corresponding
dynamic rule is also a 'fwd' rule, which would be no use (who needs a
reflexive 'fwd' rule?). However, in reality a parent 'fwd' rule seems
to create an 'allow' dynamic rule, which is useful but confusing.

Where exactly is this place in the ipfw code?

-- 
Victor Sudakov,  VAS4-RIPE, VAS47-RIPN
sip:suda...@sibptus.tomsk.ru
___
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: sysinstall vs gmirror

2010-09-12 Thread Adam Vande More
On Sun, Sep 12, 2010 at 11:14 PM, per...@pluto.rain.com wrote:

 The part I don't know how to do is partitioning gm0 by hand.
 (I suppose it would require some sort of arcane incantations
 involving bsdlabel.)  For all its limitations, sysinstall
 seems at least to know how to translate a reasonably human-
 readable representation of the desired slice and partition
 layout into the necessary fdisk and bsdlabel commands.


I don't know of any exact howto, but the general principles are laid out
here:

http://wiki.freebsd.org/RootOnZFS/GPTZFSBoot/Mirror

It shows how to load geom modules from usb stick, once they are loaded you
can then setup geom,  Next fdisk/gpart accordingly(don't forget to make it
bootable).  If your setup if GPT compatible, I recommend using it.  IMO,
it's significantly more straightforward than the old mbr style.  once you've
got your partitions setup the way you want, create your filesystems and use
the instrustions on the page to extract the distrobution on to them.
Obviously they need to be mounted for this to occur, so adapt the example to
your own use.

Note, I've never tried to boot from a gjournaled geom, but I think it will
work.

-- 
Adam Vande More
___
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