On Sun, 16 Oct 2011, James Sinnamon <james.sinnamon@gmail.com> wrote:
amonT04). It seems that a 64 bit processor will be needed as a 32 bit processor cannot address more than 4 Gig of memory (see
A 32bit processor can address up to 64G of RAM with PAE. A 32bit process can't address more than 4G of RAM.
1. has sufficient power to run the multi-threaded Java application mentioned above; and
There probably aren't many people here who are going to read a research paper on short notice just to give you hardware advice. I will note however that I was running multi-threaded Java programs on servers 10 years ago when a P3 was a fast CPU and 2G of RAM was a lot. You don't necessarily need a lot of CPU power to do such things. But it really depends on what the application does. Presumably the research paper will have some data on the CPU requirements, why don't you summarise that in your next message to the list?
2. will mostly allow at least one Linux distribution to be installed and quickly without causing me anywhere the number of problems I have faced for at least the last two weeks (see APPENDIX 1).
I think that pretty much every desktop and server system will allow all the major Linux distributions to be installed without much effort.
I would also be interested in what Linux Distribution others would recommend. I have had serious problems with Debian and Saboyan and have found Linux Mint and Ubuntu wanting (see APPENDIX 1). With the latter I two, I simply could not get the Apache server to log its rewriting of URLs with the Rewrite module.
Actually it sounds like you have Drupal problems.
If you aren't able to help with an e-mail before 10.30AM tommorow, could you please consider texting me on 0412 319669 so I can ring you back and get advice from you after I have left home?
There probably aren't many people here who provide that service without a support contract. In the past one of my clients needed some advice and bug fixes in a hurry and offered $100US by Paypal for every issue that was solved. $100US was well accepted for such things. You might consider making a similar offer.
What subsequently bothered me about Debian was that when I told it to re-boot it simply re-booted straight back to Debian! it somehow skipped over both BIOS and the Boot sector boot menu. I could only see BIOS or the boot sector meu if I hit the reset button.
That's a BIOS issue. If the BIOS is configured to just boot without displaying a menu then there's nothing the OS boot loader (in this case GRUB) can do about it.
What had it done to BIOS and the boot sector to make that happen? It seems that Linux Mint also tampers with the boot sector making some earlier Linux installations inaccessible.
It's pretty much a default action to install a boot loader on the primary boot device as part of the OS install. You have to go out of your way to get a different result.
I found that the Linux distributions I used were unable to cope with my having two hard disk drives. They created boot sectors which contradicted each other on both Hard disks. Also, confusingly more than one Linux distribution was written to the same partition. One partition seemed to have the exact same Linux distribution written to it twice.
That sounds like a bug. The expected result is that the primary disk will be used by default and installing on the secondary disk may be an option. You could just unplug the secondary disk for the duration of the install process if you are worried about such things. -- My Main Blog http://etbe.coker.com.au/ My Documents Blog http://doc.coker.com.au/