Re: Openfoam
by David Gaden
Looks like I'm not going to be much help.
>1. The build from source documentation is pretty bad. The "System
>Requirements" need to be broken up between build requirements and
>runtime requirements. I.e, do I need <blah> or <blah>-devel... It has...
I don't know the full list. The distro install instructions list packages required for each supported OS, suggesting someone has the list you need.
>2. The documentation seems to have instructions that are not strictly
>needed for installation, but I could just be confused.
I don't see anything unnecessary in this: http://www.openfoam.org/git.php
>3. Wanting to be compiled in the location it's installed to is bad...
There's still a lot of old-school left in OpenFOAM. Object files go into subdirectories within each library. The #include strategy is particularly stupid - each library requires a directory with shortcuts to all files in its scope. There are scripts that attempt to maintain these, but they don't always work, and the fail mode of name collisions is apparently to destroy both files.
>4. Along those lines, is the entire source tree really needed during use?
The library is broken down into multiple sub-libraries. It shouldn't bee too hard to pull it apart to make large, logically grouped extension packages, like openFOAM-core, openFOAM-chemistry, openFOAM-lagrange, and so on.
>Now more Fedora specific issues:
>
>5. The ThridParty package is completely unacceptable. Anything in
>there that isn't currently already in Fedora will need to be packaged
>first.
Outside my realm of expertise - I don't know much about the third party stuff. Some are pretty standard: openmpi, cmake. But then again, some of them are pretty old too, and I guess we'd have to package these ourselves.
>6. I'm not sure if the built-in wmake tool is acceptable, it seems to
>come from openwatcom.org, it will also need to be packages separately.
I think wmake is native to OpenFOAM - although openwatcom's description of theirs is identical. The wmake source files have OpenFOAM's standard comment headers. If you have to get rid of it, you are right about FreeFoam. Last I heard, the project is still unfinished, but the guys who manage the OpenFOAM-extend fork are borrowing FreeFoam's cmake solution for their Windows port. I understand the Windows port is a huge struggle, and is also unfinished... so I'm not sure how much of the struggle is associated with the cmake aspect.
>7. The 'copy the entire source-tree with the compiled binaries and
>libraries' issue from #3. I'm not sure it will be acceptable.
>
>Now once all those are taken care of, all the 3rd party stuff will
>have to be ripped out during build to make sure it's not used and the
>makefiles patched to use the system libraries where necessary.
>
>All-in-all, a lot of work. Do any of the recent changes solve any of
>these issues?
No.
I didn't realize how much work would be involved. I'd say we give it a little more time to mature. The community is growing, and there's pressure to modernize the project.
Sincerely
-Dave
~~~~
Follow me on Twitter @DavidGaden
12 years, 6 months
Compliment to the devs
by Roelof 'Ben' Kusters
Well done devs!
I have a friend, whose Thai wife has never really used computers. She's
learning it now. He had me dualboot his computer with Windoze and F15;
many people do. We are both used that most people don't give F15 - or
Linux - a moment's thought, as they don't know how to use it. However,
this woman - who knows neither Windoze nor Linux - now prefers to boot
F15. My friend asked her why: "Because it's easier!"
Well done devs; stick it in your cap!
--
Greetz,
Roelof Kusters
aka Ben
The internet isn't a highway, it's a swamp: the more you surf, the more it
draws you in.
Do read my blog! It's more entertaining than my emails:
http://my.opera.com/bentrein
12 years, 6 months
Not a good month for computer pioneers
by Aaron Konstam
In case you missed it, John McCarthy died at 84. I guess you don't have
to lisp to know about him:-)
--
=======================================================================
There's no time like the pleasant.
=======================================================================
Aaron Konstam telephone: (210) 656-0355 e-mail: akonstam(a)sbcglobal.net
12 years, 6 months
UUID for USB devices
by Geoffrey Leach
Under Fedora 14 the following procedure worked for discovering the UUID
for a USB device.
Insert device
Look in /dev/disk/by-label for device
Use file cmd to find device assigned
Look in /dev/disk/by-uuid for the UUID assigned (link to same device)
Alas, that no longer works. Anyone have an up-to-date procedure?
Thanks.
12 years, 6 months
Who to ask about old Red Hat Linux ISOs I've uncovered
by Andre Robatino
The site http://legacy.redhat.com/pub/redhat/linux/ has some old Red Hat Linux
content. Unfortunately, it's very incomplete. I have archives of the install
discs going back at least to RH 7.0. (I started on RH 6.0 so might have
something older around.) I was able to read off all of these, which have the
following md5sums. There are discrepancies between them and the ones listed on
the archive site. For example, for RH 9, the archive site has a signed checksum
file which shows
34048ce4cd069b624f6e021ba63ecde5 shrike-i386-disc1.iso
while my md5sum for RH9_1of3.iso is 400c7fb292c73b793fb722532abd09ad. Googling
for my md5sum indicates that it is correct. So why does the RH9 signed checksum
file (which, although the signature is good, was signed on 2003/09/11, months
after RH9's release) have a different checksum? There are similar discrepancies
for other ISOs.
626b7d18033e320c27c8cd58cc37a288 RH7.0_1of2.iso
c9899d398ca675c1e80a7bdb68d701bf RH7.0_2of2.iso
596b1575773e88e066326f6741312a6f RH7.1_1of2.iso
f27b912299572a542cd663b712444445 RH7.1_2of2.iso
cf7bce0c1cdbfedfae29e60aef202f6f RH7.2_1of2.iso
fd705b3e5d0e37a828db35d21195a9f6 RH7.2_2of2.iso
cb91810ce8173039fed24420407e4c59 RH7.3_1of3.iso
ec1b813d32ffdc8edc2be261735d17de RH7.3_2of3.iso
5dc81ce523cfddf99b4d4d63e91bcaa7 RH7.3_3of3.iso
d7b16b081c20708dc0dd7d41793a4177 RH8.0_1of5.iso
2df17bc02cb1b3316930ed4f7601ad9e RH8.0_2of5.iso
305d6ff5b5850fa316276710a148b0a3 RH8.0_3of5.iso
0a77d7a3bc8c4e87508c46a2670242eb RH8.0_4of5.iso
8dbcf16f0072ee47db49b08921a41ba5 RH8.0_5of5.iso
88b9baba392b02b534a6fa546bcae3de RH8.0_docs.iso
400c7fb292c73b793fb722532abd09ad RH9_1of3.iso
6b8ba42f56b397d536826c78c9679c0a RH9_2of3.iso
af38ac4316ba20df2dec5f990913396d RH9_3of3.iso
12 years, 6 months
OT? want to connect my router to a wireless network
by Dave Stevens
I have a Linksys wrt54G V8 wireless 4-port router. I need to connect
to a wireless access point through this router's radio and then share
the connection to the wired units in my office. It would also be nice
if I could set up the router to be a repeater for the incoming wifi
connection.
F14 in use on the workstation, various others sometimes in use. I know
this is not necessarily the best list but where would be better?
Dave
--
"It is no measure of health to be well adjusted to a profoundly sick society."
Krishnamurti
12 years, 6 months
Persistent WIFI connection
by Weydson Lima
Hey there,
I have a portable 4G device which is my main device to connect to the
Internet. Whenever I return home with my device I have to manually
connect all my Fedora boxes to my 4G device as they are not able to
connect automatically. What's the proper way to set my boxes to
connect automatically when my device is in range? I have already
checked the setting to connect automatically in the
gnome-control-center tool, but it doesn't seem to do anything in my
case.
Edit/Delete Message Reply With Quote Multi-Quote This Message Quick
reply to this message
---
Weydson Lima
weyseal(a)gmail.com
12 years, 6 months
chrome quit, won't restart
by Jackson Byers
$ uname -r
2.6.35.14-97.fc14.i686.PAE
chrome suddenly quit; no response to clicks on icon
trying manually:
$ /opt/google/chrome/google-chrome &
[2] 4311
$ [4311:4311:95679337296:ERROR:process_singleton_linux.cc(250)] Failed
to unlink /home/byers/.config/google-chrome/SingletonLock: Read-only
file system
[4311:4311:95679337571:ERROR:process_singleton_linux.cc(265)] Failed
to create /home/byers/.config/google-chrome/SingletonLock: File exists
[4311:4311:95679337706:ERROR:process_singleton_linux.cc(250)] Failed
to unlink /home/byers/.config/google-chrome/SingletonLock: Read-only
file system
[4311:4311:95679337746:ERROR:browser_main.cc(1650)] Failed to create a
ProcessSingleton for your profile directory. This means that running
multiple instances would start multiple browser processes rather than
opening a new window in the existing process. Aborting now to avoid
profile corruption.
[2]+ Exit 20 /opt/google/chrome/google-chrome
I then rebooted, and chrome came up as usual.
advice?
Jack
12 years, 6 months
