vmunix

[Vogra]

Hi All!
what about the file vmunix? I found file vmunix.prev on directory out of system and I need to delete it, but I don't know if it's can be a problem. Using a find command, I found the result below:
vsurjux1@root:/ #find ./ -name vmunix*
./stand/vmunix
./usr/conf/vmunix.client
./usr/conf/vmunix.fs
./geinc/vmunix.prev
My doubt concern to last file.
thanx in advance

[James R. Ferguson]

Hi:

The file ./geinc/vmunix.prev in /stand can be trashed.

The /stand/vmunix.prev is the *previous* version of the current kernel. You should keep it! In the event that your kernel (file) ever becomes corrupted, you have a viable kernel from which you could boot.

...JRF...

[Patrick Wallek]

It looks as if you have several backup copies of vmunix in other directories. The only vmunix that should be in use is /stand/vmunix. Anything else is probably a copy.

The geinc directory is not a standard HP-UX directory. It was probably created by someone to hold the vmunix.prev because they were running short of space in /stand when they needed to build a new kernel.

Compare /stand/vmunix and /geinc/vmunix.prev and if they are similar you might consider keeping vmunix.prev since it is a backup copy of your kernel. If it is older, do whatever you want. It is always a good idea to keep a copy of vmunix.prev in /stand so that you can boot from it if something happens to your regular kernel.

[Rob Smith]

Hi, that is the one of the previous kernels. I dont't know if I would delete it if there is not a system.prev in /stand. As a matter of fact I would move it back to /stand. This was you will always have a working kernel to boot off of in case anything goes wrong. Hope this helps.

Rob

[eran maor · Accepted solution]

Hi

vmunix.prev is the vmunix that stay in /stand after you are doing changes to the kernel and making a new kernel so you can go back if the resault of the new kernel is not o.k .

you can delete all the vmunix
./usr/conf/vmunix.client
./usr/conf/vmunix.fs

i can see that the vmunix.prev is in a dir
./geinc/vmunix.prev
that is not normal .
i will not tell you to delete it but you can do a new compile of the kernel and recreate the vmunix.prev in the /stand and after that
delete the ./geinc/vmunix.prev

dont delete the ./stand/vmunix !!!

if you have any more que please ask

[Abel Berger]

Hi Claudio, ou deveria dizer e a? mano !

Bem acho que isto vai ajud?-lo :

You can remove vmunix.prev because patch installation proccess loads a new vmunix and put you current vmunix to vmunix.prev.
Look in /stand/build if there is a obsolete test kernel (vmunix.test) you can remove it too.

Take care !

I hope this help

Regards

Abel Berger

[Vogra]

Thanx to All!!
Abel, cara tu ? o primeiro brasileiro que vejo por aqui desde de que entrei. Legal!
Valeuza?o pela ajuda.
Abra?o.

[Vogra]

Ah! The file was identical to current vmunix... was deleted.

[Abel Berger]

Claudio,

Keep in contact !

abel_berger@yahoo.com

[Mr Amir Mujtabain]

Hi,

You can remove vmunix.prev file from any where but do not remove from /stand/vmunix.prev becuase it is useful when your orignal kernel /stand/vmunix will currupt. You can boot from /stand/vmunix.prev anytime.

[Ravi_8]

Hi,
to be on safer side make a copy of /stand/vmunix
(cp -p /stand/vmunix /stand/vmunix.prev) and delete /geinc/vmunix.prev . in case any problem while rebooting you can boot from /stand/vmunix.prev

[Vogra]

Hi Amir & ravi,
I did understand it... and I made a copy.
Thanx.

[CHRIS_ANORUO]

Hi Claudia,

Preserve the vmunix.prev unless you have made a kernel/LVM changes. Also leave the vmunix files in /usr/conf, they are the basic config kernel files that the system has, the files in /usr/conf/master.d do refer to them in updates.