Both SANs and cluster filesystems have multiple machines talking tomultiple shared disks that all of them can see. The difference is thatSANs are designed for a single machine to talk to a given disk at atime, while cluster filesystems allow multiple machines to talk to thedisk at once.

Which raises the big question: why do you need cluster filesystemsat all? Why can't multiple systems share a single disk without doinganything special?

There's two problems with shared disks: caches and coordinatingupdates. These

Since I just went digging for this the other day , here's what I know about what controlswhat Ethernet devices get named on Red Hat Enteprise (and probablyalso on Fedora, but I haven't looked at my Fedora systems in thislevel of detail).

• if kudzu is enabled, it uses /etc/sysconfig/hwconf to nameeverything. If there is no such file or the data in it doesn'tmatch current reality, various bad things happen.

  (You can probably hand-edit

Here's my problem: I have a bunch of identical 1U servers (SunFireX2100 M2s) with four onboard Ethernet ports, driven by two differentchipsets (two nVidia ones, two Broadcom ones). I want to configure ourRHEL installs so that no matter which physical unit I stuff the systemdisks into, the Ethernet ports come up with consistent names that matchthe ports on the back of the server; eth0 should always be the portlabeled 'port 0' and