Query

[SYS ADMIN_7]

Hi Experts

Small silly query.

1) Why /stand if HFS file system only , not vfx??
2)Whether NFS is UDP or TCP based??

Hope there will be plenty of anwers a usual

Rgds
Suraj

[Simon Hargrave]

1) /stand is HFS as this is a requirement for HPUX to boot. Presumably the IPL is coded to read HFS filesystems, which reads the kernel from /stand. If /stand were to be able to understand VxFS /stand too, then it would be much larger. I guess there's been no real reason to update this.

2) NFS (from version 3 I think) can be either UDP or TCP. NFS prior to this version was all UDP. The TCP implementation was created to support higher-latency networks (non LAN, eg Internet).

[Pete Randall]

1) /stand is HFS so that the boot loader can find it's way - the loader has no concept of vxfs file systems

2) UDP


Pete

[SYS ADMIN_7]

Hi All

Any more view on this..

Rgds
Suraj

[Muthukumar_5 · Accepted solution]

/stand directory contains all booting files and system informations are available there.
Functionality is needed which differed on inodes / buffer caches and access level are there.

A good supportive discussion is here as,
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=21461

White paper hfs for the support /stand as,
http://www.uwsg.iu.edu/usail/peripherals/disks/adding/HPfs.html

2. NFS are using UDP to get unreliable and effective with faster data communication.
They are giving good progress on testings.
http://playground.sun.com/pub/nfsv4/save/1093.html

Regards
Muthu

[Patrick Wallek]

Simon and Pete have already given you the answers, but:

1) /stand is HFS because the boot process does not know how to deal with vxfs filesystem. It has been this way for YEARS. I **THINK** I had heard that this requirement may go away in an upcoming release, but I am not sure.

2) NFS version 2 was/is UDP only. NFS Version 3 can be TCP or UDP. This is controlled from /etc/rc.config.d/nfsconf.