EFY Times, a technology website from India, often provides some interesting Linux and open source news and advice. But sometimes that advice really needs to be taken with a grain of salt. An example, is 10 Basic Linux Commands for Beginners.
Recently I had the experience of encountering antireligious bigotry by a free software advocate. I will not mention the person by name, but I will describe their attitudes and the effects, and by the way of elaboration on why all forms of prejudiced discrimination is not just morally wrong, but damaging to free software as a movement. The experience occurred just prior to Software Freedom Day among the organising committee.
Jeff Carl
Secretariat Advisory Council on Intellectual Property
PO Box 200 Woden ACT 2606
mail.acip@ipaustralia.gov.au
Dear Mr. Carl,
The following is the submission by Linux Users Victoria, Inc., on the Options Paper for the Review of the Innovation Patent System.
Previous posts have described the installation of R, and even installing some of its less than simple packages. But what do you do when a library appears to be installed by one of the normal methods and declares itself as such - until it is actually requested? In other words, a false positive, one of the most frightening creatures known in the world (although fortunately in this case trivial in damage).
Fire Dynamics Simulator (FDS) is a computational fluid dynamics model of fire-driven fluid flow. The software solves numerically a form of the Navier-Stokes equations appropriate for low-speed, thermally-driven flow, with an emphasis on smoke and heat transport from fires. It is also slightly unpleasant to install, but the following notes should make it somewhat easier.
Agile Project Management was born from the experience that highly prescriptive, planned-based approaches to project management simply weren't working in some contexts. In response the Agile Manifesto and Declaration of Interdependence statements were issued which, on the face of it, argue for flexibility in planning, an emphasis on customer-value, teamwork, and a welcoming attitude towards change.
This has been a very good year for Linux Users of Victoria, Inc. By all major metrics, we have improved. Our membership has increased, the attendance at our main meetings and beginners workshops have improved, and we are in a better financial state that we were last year. We held an excellent Software Freedom Day last year with larger attendance and international, and a very successful annual picnic.
In a few weeks, Linux Users of Victoria, Inc., will be holding another Annual General Meeting. But this one is somewhat different to others. At this meeting, the very existence of LUV as an independent organisation may come to an end. A motion is on the agenda that LUV dis-incorporates and merges into Linux Australia, Inc., as a subcommittee of that group. It is an issue which I personally have given some serious thought to over the past several months, and more fleeting consideration over the past few years.
| pgcc | C compiler driver. |
| pgCC | C++ compiler driver. |
| pgf95 pgf77 pgfortran |
Fortran compiler driver. |
| pghpf | High Performance Fortran compiler driver. |
| pgdbg | Debugger. |
| pgcollect pgprof |
Profiler. |
| pgcpuid | Display the CPU type the compiler sees and display the default -tp switch it will use. |
The past several years my desktop machine at work has been running 32-bit Ubuntu (and more recently Xubuntu), even though it had a 64-bit processor. The nature of the work I did meant that this wasn't really an issue at all until recently an application that did require interaction between the desktop client and the HPC cluster dropped support for the 32-bit client. Well, fair enough. But what 64-bit distribution should I install? "Slackware", said the mischevious wonk next to me. Sure. Why not? After all, it was the first Linux distribution, and it has slack in the title - and I do believe in the benefits of the Church of the Sub-Genius. Actually there are two reasons why not, but I thought I'd give a whirl anyway.
Installation was pretty much as documented. You will have to do your own partition management, a typical rule of either partitioning /boot, /home, and a swap partition is pretty sensible. Or you can just put everything under / and work it out later if that way inclined (I was, and I shouldn't have been). When it comes to installing packages, it's worth going for "full", keeping in mind one of the aforementioned "two reasons", although there is a very good argument from older-style Slackware purists that says that you should have full knowledge of your system at all times and shouldn't beholden to pretty stupid niche situations, such as a media player wanting Samba as a dependency.
After that it's a case of getting LILO set up as the boot-loader (I had to run liloconf after the install due to some interesting arguments with an existing GRUB) and the default window manager (my preference is XFCE). Like most things Slackware, options which are expected and normal in most distributions are not necessarily the case with Slackware; in particular it is noted that 64-bit Slackware really means 64-bit. It will not run 32-bit binaries. To enable this there is some fairly straight-foward instructions.
