building new kernel

[Jay Cantwell]

I am scheduled to build a new kernel this sunday on my production machine...here is some info then my question:
bdf:
/dev/vg00/lvol1 67733 26258 34701 43% /stand
my vmunix and vmunix.prev are a little over 12MB....do you think there enough space ??

2. my system.d directory appears in the /stand/dlkm directory but not in the /stand directory....is this going to cause a problem (ie. prevent kernal build, corrupt, etc...)

3. what is the system.d directory used for and can I simply MOVE it back to the /stand directory ??

thanks...Jay

[Steven E. Protter · Accepted solution]

1. Yes, not a problem.

2. I have a copy of system.d in the same location. My system also has a copy in /stand I guggest copying it, not movingit

3. Never checked ....

SEP

[John Dvorchak]

Your /stand/vmunix.prev will be replaced with the current vmunix so there will be no real space issue.

On my HPUX 11.00 system the system.d is in /stand/dlkm currently so I don't think you have a problem there either. I am curious why you thought it would reside in /stand instead of /stand/dlkm.

As for it's purpose, I am not sure, but since it is in the dlkm path I would guess that it is a temporary holding spot used while building the kernel's modules. Mine is empty.

[Jay Cantwell]

Good morning John....just making sure..I have another 11.0 system and the system.d directory is in the /stand directory....just making sure that I have all my "aflacs" in a row :):)....thanks..

Jay

[Keith Bevan_1]

d be loathed to move it just in case.Jay,

With your vmunix being a little of 12MB you wont have a problem.

The vmunix.prev will get overwritten anyway as the vmunix is copied to vmunix.prev before rebuilding the kernel, so no new space will be used unless your current or new kernel is significantly larger than the .pre

Point two again I dont see this being an issue, but if you are concerned then you can always use sam to do the legwork and let sam worry about the location of the system.d file. If it doesn't find it where expected it will soon let you know.

Point three I would be loathed to move it just in case. IT is possibly a by product of a previous kmtune/kmupdate.

Keith

[Keith Bevan_1]

Jay,

Please disregard the first line of my previous post, it should have just read :-
_______
Jay,
_______

A cut a paste issue on my Windows i'm afraid.

Keith