Good that you look to have solved your problem.

If you were only suffering from too little HDD resource, then you can adjust the Boinc limits in your account preferences on your s@h account page.

Happy crunchin',
Martin

My understanding of the /proc directory on *NIX systems is that it's basically an imaginary virtual file system. ... It's there for a reason, and there's a reason why only 'root' can make modifications to it.

Everything on *nix is part of a filesystem and procfs is a view into the running kernel. It can be called a 'virtual' filesystem in that it doesn't really exist. It is just a "viewing portal" that 'looks like' a filesystem so that standard filesystem programs can be used to interrogate and manipulate kernel parameters. In "Windows-speak" you might call it a "live kernel registry".

Lots of system utilities make use of "/proc". There is also "/system"...

No physical disk space is utilised by either of them (apart from perhaps RAM swap space). Trying to get a file size for them is pretty much meaningless.

As far as replacing the main disc with a larger one, it should be really simple.

If your new disc is installed, you can get started right away, otherwise, shut down, put the new disc in, and boot back up.

From here, this is really easy. As root, do

dd if=/dev/hda of=/dev/hdb bs=512

This will do a bit-level copy from your root disc (assuming your root disc is the primary master IDE disc). If unsure of the designation of the hardware, usually a simple command of 'mount' or 'df' will give you the information you need. ...

That's a good 'quick-n-dirty' way of doing it.

Two notes:

On recent systems, all HDDs are seen as /dev/sdX where "X" is a drive letter.

And if you are going to use "dd" then best is to shut down your system and reboot into a LiveCD so that the disk you are copying from is not being used.

Or you could just format the new disk and add a mount point for it to use it as-is, with your system still on the existing disk.

A good way to work so that you can easily upgrade is to have partitions for "/", swap, and "/home". Then you can reinstall a new system into "/" and leave you "/home" user data intact and ready for use with the new system.


Anyone at a local user group should be able to help you out.

Hope that helps,

Good luck,
Martin

My understanding of the /proc directory on *NIX systems is that it's basically an imaginary virtual file system. It occupies a small amount of RAM and that's about it. Mostly it's just a way of organizing the resources for all the running processes. Say for example PID 6342 needs 5 files to be in RAM. There's a PID direcotry in /proc for PID 6342, and the contents of that directory are those 5 files and control information for the process itself.

/proc gets created as one of the very very first steps (I think right after PID 1 (init) gets started, /proc gets created. init is the first process to start, and the last one to shut down. On openSuSE, when shutting down, if I hit escape to get out of the splash screen and see what steps are being taken, just before "halting system", there is "unmounting profs".

My experience is that you can't really do much with /proc, and it doesn't really take up any space either on disk, or RAM, so in a nutshell, just forget about it. It's there for a reason, and there's a reason why only 'root' can make modifications to it.

/proc doesn't contain real files on disk, only information about the system and running processes. It's a meta-filesystem just like /dev/null, /dev/random, etc. Nothing in /proc actually takes up disk space, and you can read more about its purpose and contents at procfs.

/proc/0/cwd returns the current working directory of the process with PID 0, thus if the working directory is root, then /proc/0/cwd is just an alias for /, and you can recursively do this for as many levels as you want.

I still don't get the connect between George and Gracy and Douglas Adams?

To understand my SIG...
You must watch the movie "Star Trek IV: The Voyage Home"... George and Gracy play a major part in the plot of the movie.

Have you considered installing the optimized app on your hosts? You could boost your production by ~50% just by switching apps! And it's free !!!

Does it tien in George and Gracy with Douglas Adams?

This is simple......depending on your budget.....get the best core 2 cpu you can afford......get the best Asus mobo you can afford......RAM does not have to be expensive, get the fastest timings, not the fastest speed.......get the best cpu cooler you can afford.......load up the new Wet Noodle app.......

And OC the bejeesus out of it..........

BTW, the advice still holds even if you do not wish to enter the 'dark world' of OCing.......

Money is no object, what should I get?

Windows enterprise server cost several thousand dollars maybe 10,000 dollars linux is free

I still don't get the connect between George and Gracy and Douglas Adams?

To understand my SIG...
You must watch the movie "Star Trek IV: The Voyage Home"... George and Gracy play a major part in the plot of the movie.

Have you considered installing the optimized app on your hosts? You could boost your production by ~50% just by switching apps! And it's free !!!

This is simple......depending on your budget.....get the best core 2 cpu you can afford......get the best Asus mobo you can afford......RAM does not have to be expensive, get the fastest timings, not the fastest speed.......get the best cpu cooler you can afford.......load up the new Wet Noodle app.......

And OC the bejeesus out of it..........

BTW, the advice still holds even if you do not wish to enter the 'dark world' of OCing.......

Money is no object, what should I get?

Windows enterprise server cost several thousand dollars maybe 10,000 dollars linux is free

Well, I know win2k advanced server supports oodles of cpus......readily available for a couple of hundred bucks......just don't know about a x64 version..........

w2kas supports 8 cores you need the data center or enterprise server I got w2kas for 88 dollars.

Or if you are a 'build it yourselfer'.......
A server based 16 core beast running the fastest Xeons........

That is more my style

What OS would you run the beast on?

Anything I can understand. I am not a MAC person.

To run 16 cores would take a Linux box or a very expensive enterprise windows server or windows data server.

Or if you are a 'build it yourselfer'.......
A server based 16 core beast running the fastest Xeons........

That is more my style

What OS would you run the beast on?

XP x64 of course.

That would be fine...

I believe xp will handle 8 cores tell me if I am wrong.