Is there a properly intelligent filesystem and driver that can handle a
read-write filesystem across multiple zLinux images?
We're trying to install the set of Tivoli products, using zLinux as the server
for many of the pieces, and the folks doing the install have come to a piece
that says it
On Oct 28, 2005, at 8:08 AM, Nix, Robert P. wrote:
Is there a properly intelligent filesystem and driver that can
handle a read-write filesystem across multiple zLinux images?
We're trying to install the set of Tivoli products, using zLinux as
the server for many of the pieces, and the folks
Nix, Robert P. wrote:
Is there a properly intelligent filesystem and driver that can handle a
read-write filesystem across multiple zLinux images?
There are multiple. Lustre (Cluster Filesystems Inc.) and global filesystem
(RedHat)
can do that. None of them is merged into mainline Linux kernel
OK Thanks everyone.
From the comments, I've learned
There isn't an automagical thingie that I was suppose to know about.
I was aware of the .bashrc, .profile, .profile.local, etc stuff. I
would have thought Oracle would have been aware of it also.
This isn't a zLinux vs Linux thing.
This
Edmund R. MacKenty wrote:
James Melin writes:
Actually, if you have the disk as ext3, you get gazillions of errors when
it is R/O because the system that is mounting the disk R/O tries to use the
journal too but it cant open it R/W.
This is only true if you mounted the device read-write in
Rick Troth wrote:
Ooo ... ouch. The pain of profiling.
And unlike CMS, there is no global address space
where these things can be put.
I STRONGLY recommend that you not set variables in $HOME/.bashrc
for two reasons. First, it is specific to only that one shell.
But secondly, and
