Hi Jim/Mark,
I have tried the same after chrooting
into /mnt/newroot. Also issued mkinitrd,zipl.
Re-IPled using 1b26, again the same
cpu looping problem re-appears.
How to check if the kernel on the
disk is 64 bit or not ??
Below is the procedure i have followed
:
inst-sys:~ # insmod dasd_mod
Hi All,
Since some months we are running SuSe Linux Guests under z/VM. For the
initial installations I used IBM's redpaper written by Simon Williams
about building SLES8 systems under z/VM. This initial installation was
not very carefull with DASD space, it took about 2 3390-III volumes. So a
You would think that IBM, owning the Tivoli brand, would direct a few dozen
of their programmers to fix the issues that prevent most of us from using
TSM on L/390 if for no other reason than to not lose business to other
backup vendors.
Post, Mark K
[EMAIL PROTECTED]
Srinivas,
It appears you're 64-bit, from this:
(version 2.4.19-3suse-SMP) (s390x)
s390x is the 64-bit implementation, s390 is the 32-bit. The directories
shown look like mine, and I'm running SLES 8 s390x, too.
Regards,
--Jim--
James S. Tison
Senior Software Engineer
TPF Laboratory /
For a rough and ready figure of how big your filesystems
should be, you can go back to your minimal system and
issue a du against them, e.g. du -h /usr which will
at the end of it all give you a Mb size for what the
system thinks is contained in /usr. You can then back
calculate this to whatever
Srinivas,
I'm at a loss. I would say it's time to call in SUSE and IBM to figure out
what's going on. Well, perhaps one more thing. What does the I/O
definition for this LPAR look like? Are there any devices defined that you
don't plan on using? If so, eliminate everything except those
You would think so, wouldn't you? But then that implies that you and I
actually think. Apparently the Tivoli folks still believe the mainframe is
dead, or some equally foolish mindset. Let's see. Most estimates put the
amount of corporate data in the world that resides on mainframes somewhere
Hi Srinivas,
Did you dadsfmt and fdasd the volume? I ask because the first 4 bytes
at should be C9D7D3F1 (or IPL1), the 4 bytes at 001 should be
C9D7D3F2 (or IPL2) and the 4 bytes at 002 should be E5D6D3F1 (or VOL1).
That's if your using CDL format.
I just ran zipl against a
mv /my/dir/dir/files /my/dir/files - provided they are both the target and
destination are in the same file system should do it. All you're really
trying to do is eliminate the superfluous directory level, and this will do
that.
Marcy Cortes
[EMAIL PROTECTED]
On Wed, 2004-05-05 at 12:24, Adam Thornton wrote:
On Wed, 2004-05-05 at 12:00, Marcy Cortes wrote:
I need a mv incantation to move everything up a directory, i.e. change:
/my/dir/dir/files to
/my/dir/files
cd /my/dir/dir
mv * ..
Other people's suggestions are better, as this does not
Adam,
Actually:
cd /my/dir/dir
mv files ..
You're method moves things other that the files subdirectory up one level,
and does not move the private (.*) files. Moving the subdirectory does
move everything include the dot files.
--
John McKown
Senior Systems Programmer
UICI Insurance Center
One way to do it:
/bin/csh (to get into csh)
cd /my/dir/dir/files
foreach i (`ls`)
mv $i ../$i
echo $i
end
-- db
David Boyes
Sine Nomine Associates
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
Marcy Cortes
Sent: Wednesday, May
I used yours because it came in first. I don't think I had any dotfiles
though.
Thanks everyone.
-Original Message-
From: Adam Thornton [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 05, 2004 10:30 AM
To: [EMAIL PROTECTED]
Subject: Re: [LINUX-390] Command to move everything up a
Neale,
We have a local account with such a configuration. Once finding the proper
driver, it was not too hard to get the FICON/FCP CHPID access the SCSI
3590 tape drives.
Jean-Pierre Baril
Specialiste en technologies de l'information/IT Specialist
Novipro Inc / 2055, rue Peel, bureau 701
We have a local account with such a configuration. Once
finding the proper
driver, it was not too hard to get the FICON/FCP CHPID access the SCSI
3590 tape drives.
Jean-Pierre Baril
I think the point is that for every 390 customer that has SCSI-attached
3590 drives, there are at least 2
Hi David,
This was done with SLES 8 under z/VM V4R3. Customer had already embarked
on migrating some Unix Application to Linux on s/390 (meaning 31-bit),
actually an 2086-103/105. So, for them to justify the addition of one TSM
Server (actually the consolidation of 18 Intel TSM Servers spread
Rod wrote:
If you ask 10 people how you should partition things
then you'll get 11 answers. A lot of it depends on
what you want to do.
Certain vendors always reply, It depends, ;-)
=
Jim Sibley
RHCT, Implementor of Linux on zSeries
Computer are useless.They can only give answers. Pablo
[ ... good case for doing TSM on zSeries for specific customer with
SCSI tape already in place ... ]
Most of the
pre-reqs were already there.
This is the key sentence. I agree that it made sense for this customer
-- but they are the exception, not the rule in terms of equipment
present in
Hello (again) from Gregg C Levine
Back in April I attended a seminar given by IBM on the usual subjects.
And one before that in March. During the entire April seminar the
Tivoli rep, didn't want to discuss the importance of VM, and Linux as
a guest, nor the reasoning behind that position, and
Before you attempt to move anything, do:
shopt -s dotglob
from the bash prompt, which will change bash's globbing routine to include
those pesky little dotfiles, too. Of course, this presumes you're using
the
bash shell.
--Jim--
James S. Tison
Senior Software Engineer
TPF Laboratory /
20 matches
Mail list logo
