On Apr 7, 2009, at 6:58 PM, Mark Post wrote:
I just fired up a SLES10 SP2 install and checked. In SLES 10, it
wasn't a choice either. Not sure how you managed to do it unless
you were using AutoYaST. Still, it's supposed to be there now, so
it needs to get fixed.
I didn't install SP2 tabula
>>> On 4/7/2009 at 5:28 PM, "Stricklin, Raymond J"
wrote:
> I haven't seen any documentation which states (or even suggests) that
> XFS is deprecated in SLES11, but it is apparently no longer a choice in
> YAST2 during installation.
I just fired up a SLES10 SP2 install and checked. In SLES 10,
>>> On 4/7/2009 at 6:57 PM, "Stricklin, Raymond J"
wrote:
-snip-
> Is there any way to work around it from the installation image, and get
> an XFS filesystem to install onto? If not I guess I could prep the disk
> on a running SLES10 system. Being able to do it from the installation
> image w
Thorsten...
Also... How would these things be defined in the IOCSD.
I have them currently defined as follows...
CNTLUNIT CUNUMBR=FC10,PATH=(FC),UNITADD=((10,001)),UNIT=CTC
CNTLUNIT CUNUMBR=FC11,PATH=(FC),UNITADD=((11,001)),UNIT=CTC
IODEVICE ADDRESS=160,CUNUMBR=FC10,UNIT=CTC,UNITADD=10
IODEVICE ADD
> >>> On 4/7/2009 at 5:28 PM, "Stricklin, Raymond J" wrote:
> > I haven't seen any documentation which states (or even suggests)
that
> > XFS is deprecated in SLES11, but it is apparently no longer a choice
> > in YAST2 during installation.
>
> That would be a bug.
That's reassuring, thanks
>>> On 4/7/2009 at 5:28 PM, "Stricklin, Raymond J"
wrote:
> I haven't seen any documentation which states (or even suggests) that
> XFS is deprecated in SLES11, but it is apparently no longer a choice in
> YAST2 during installation.
That would be a bug.
Mark Post
I haven't seen any documentation which states (or even suggests) that
XFS is deprecated in SLES11, but it is apparently no longer a choice in
YAST2 during installation.
I decided to switch to XFS several years ago after many headaches with
ext3's... shall we say, less enterprise-friendly "features
>>> On 4/7/2009 at 2:41 PM, Saul Thersites wrote:
> Thanks Steffen,
> I'm now in single user mode.
>
> I need to change:
>
> qeth-bus-ccw-0.0.0900 no interface found
>
> What specifically do I need to change here? All that has been done is a CSS
> move from 1 to 2. How can I "can activate th
>>> On 4/7/2009 at 3:51 PM, Daniel Vila wrote:
> Yes , I,m using the Kernel provided in the SLES11 DVD distro , about the
> memory suggestion , I tried with different virtual memory sizes (512, 768
> & 1024)
> and the error continue being the same .
Just because I've seen odd things happen befo
>>> On 4/7/2009 at 3:08 PM, Mark Pace wrote:
> Well I don't know what I missed doing the LVM manually.
Do a "find /etc -type f -mtime -1" to see what files have been changed in the
last 24 hours, and compare the list of those files, and their contents to what
you did manually.
Mark Post
--
On Apr 7, 2009, at 12:51 PM, Daniel Vila wrote:
Hi everyone, I'm trying to start the SLES11 instalation under 5.3
ZVM but load process is interrupted after a
panic kernel message (SLES10 worked without problems using the same
ZVM)
Any ideas to find a fix?
Your initramfs is corrupt.
Re-downl
Yes , I,m using the Kernel provided in the SLES11 DVD distro , about the
memory suggestion , I tried with different virtual memory sizes (512, 768
& 1024)
and the error continue being the same .
390 hardware is a 2064 machine with a Zvm 5.3 running healthy copies of
SLES10 SP1
MD5 checksum number
Did you use the INITRD and KERNEL from SLES11 distro?
I know the SLES10 version do not work from personal experience.
Bruce
- "Daniel Vila" wrote:
> Hi everyone, I'm trying to start the SLES11 instalation under 5.3 ZVM
> but load process is interrupted after a
> panic kernel message (SLES1
Well I don't know what I missed doing the LVM manually. But I removed the
LVM dasd from fstab so that I could boot cleanly.
Then using yast I recreated the LVM vg & lv. Reboot and it all works fine.
On Tue, Apr 7, 2009 at 1:43 PM, Mark Pace wrote:
> Weirdness.
> When I IPL and the LVM fails to
Thanks Steffen,
I'm now in single user mode.
I need to change:
qeth-bus-ccw-0.0.0900 no interface found
What specifically do I need to change here? All that has been done is a CSS
move from 1 to 2. How can I "can activate the interface manually"?
On Tue, Apr 7, 2009 at 11:16 AM, Steffen Maier
>>> On 4/7/2009 at 1:51 PM, Daniel Vila wrote:
> Hi everyone, I'm trying to start the SLES11 instalation under 5.3 ZVM but
> load process is interrupted after a
> panic kernel message (SLES10 worked without problems using the same ZVM)
>
> Any ideas to find a fix?
>
> Virtual memory defined:
I'm pretty certain that the manual suggest 768MB minimum for an
installation. I typically use 1GB for installation.
On Tue, Apr 7, 2009 at 1:51 PM, Daniel Vila wrote:
>
> Hi everyone, I'm trying to start the SLES11 instalation under 5.3 ZVM but
> load process is interrupted after a
> panic kern
Hi everyone, I'm trying to start the SLES11 instalation under 5.3 ZVM but
load process is interrupted after a
panic kernel message (SLES10 worked without problems using the same ZVM)
Any ideas to find a fix?
Virtual memory defined: 512k & 1024k
sles11 start process log:
LOADING SLES11
Weirdness.
When I IPL and the LVM fails to mount -
If I chccwdev --offline 0.0.0203
then
chccwdev --online 0.0.0203
the logical volume appears.
No idea why it does not work during IPL.
On Tue, Apr 7, 2009 at 1:34 PM, Mark Pace wrote:
> That's what I was thought about LVM also. The device is com
That's what I was thought about LVM also. The device is coming online now
(repair filesystem) #
lsdasd
lsdasd
Bus-ID Status Name Device Type BlkSz Size
Blocks
==
0.0.0202 active dasda 94:0E
I thought that they would be mounted in the order that you ran
dasd_configure. That's how SLES 10 worked, so I presumed that SLES 11
works this way, but some testing shows that it doesn't. On my system,
the root volume is always dasda, then it seems to mount them in the
order the files appear in
Actually the swap devices were also defined in fstab as "by-path", so they
worked okay.
But the the LVM device is set as /dev/vg1/lv1 which is not being
created, I assume because of the changed device order.
On Tue, Apr 7, 2009 at 12:57 PM, Mark Pace wrote:
> Well that fixed the problem of t
Well that fixed the problem of the device not coming online at IPL. But now
all the dasd labels have been changed.
0200 was dasda now dasdc
0201 was dasdb now dasdd
0202 was dasdc now dasda
0203 was dasdd now dasdb
root dasd mounts fine because it is mounted "by-path", but the swap disk
were by /
I'm not sure which variations of zipl menu parameters you tried and I
haven't confirmed my suggestion, but did you use one of the following?:
0 s
or
1 s
I.e. appending Linux kernel parameters to the zipl menu item number on
the hardware messages console.
You may find more details in the Device
> Very Interesting !! Really takes me back ( an 1130 at school).
> (Slide 37 seems to have the date wrong ...)
Kim:
So was mine! Fun little machine
Argh, fixed.
Jim
--
For LINUX-390 subscribe / signoff / archive access instruct
On Tue, Apr 7, 2009 at 5:11 PM, Dave Jones wrote:
> Yup, I think this calls for a day off, don't you?
Sure, and a wrist watch with the date in it !
And not just for Jim, should we not all have a day off? I think for
many of us this counts as a religion related holiday.
Rob
Dave Jones wrote:
Yup, I think this calls for a day off, don't you?
Hmm, following this group could easily give one the impression
that the management trend in mainframing is definitely towards
giving mainframers days off ... :)
--
Jack J. Woehr# I run for public office from time
what would be problem if sourcevipa removed ??
--
Email Disclaimer
This E-mail contains confidential information belonging to the sender,
which may be legally privileged information. This information is intended
only for
thanks Alan---will try it--let ya know
--
Email Disclaimer
This E-mail contains confidential information belonging to the sender,
which may be legally privileged information. This information is intended
only for the us
> BTW, Jim's History of the Mainframe can be found on his web
> page under the "Events Events including user groups"
> headingnot the most obvious place to go look:-)
Dave: My note did say to look on the Events page, but I have
updated the web page now with directions.
Jim
--
Very Interesting !! Really takes me back (My first computer system was
an 1130 at school).
(Slide 37 seems to have the date wrong ...)
Jim Elliott wrote:
Today, April 7th is the 45 anniversary of the announcement of
System 360. In celebration, I have updated my History of the
Mainframe presen
I think, in SLES 11, you either must use Yast to add disks, or to use
the scripts supplied by Novell that Yast calls. The script to add
dasd is dasd_configure, and if you run it without any arguments, it
shows this help:
Usage: /sbin/dasd_configure
For your use, you'd enter: dasd_configure 0.
This is running native. No z/VM and my boot screen does not have
Note: VM users please use '#cp vi vmsg '
On Tue, Apr 7, 2009 at 9:50 AM, Mike Friesenegger
wrote:
> I see the following message when I IPL my SLES10SP2:
>
> ipl 150
> 00: zIPL v1.6.3 interactive boot menu
> 00:
> 00: 0. defaul
On Tuesday, 04/07/2009 at 11:02 EDT, Ron Wells
wrote:
> ◄
> tcp 0 0 192.168.253.217:2049 10.239.53.126:1043 ESTABLISHED -
> tcp 0 0 192.168.253.217:2049 10.239.53.126:1042 ESTABLISHED -
> 9:05:02 AM
> Not understanding why it uses 10.239.53 path
> below is mount from z/os
>
> MOUNT FILESYSTEM('1
Yup, I think this calls for a day off, don't you?
BTW, Jim's History of the Mainframe can be found on his web page under
the "Events Events including user groups" headingnot the most
obvious place to go look:-)
Jim Elliott wrote:
Today, April 7th is the 45 anniversary of the announcemen
I see the following message when I IPL my SLES10SP2:
ipl 150
00: zIPL v1.6.3 interactive boot menu
00:
00: 0. default (ipl)
00:
00: 1. ipl
00: 2. Failsafe
00:
00: Note: VM users please use '#cp vi vmsg '
00:
00: Please choose (default will boot in 10 seconds):
I have been typing "#cp
Having an issue--maybe someone can see my error...
trying to mount >> from z/os to VM/Linux image ..
works over OSA but can not seem to get it to work over Hypersocketor
it appears not working ...
Below is what the Linux guy see's ...
>> note>> ping... tracrte works fine <<<
Apr 7 09:03:05
Today, April 7th is the 45 anniversary of the announcement of
System 360. In celebration, I have updated my History of the
Mainframe presentation and posted it on my web site on the
events page.
http://ibm.com/vm/devpages/jelliott
Jim
-
Working on a new SLES11 install.
I added a new disk as an LVM volume. After I had the LV setup and working I
did an
mkinitrd
zipl
When I reboot it does not find the disk and stops.
I can do
chccwdev --online 0.0.0203
mount -a
and the disk comes online and mounts fine. I added dasd=0200-021f
Just tried that as well. Didn't work.
Any time I enter in anything other than 0 or 1 I get:
Please choose:
Error: undefined configuration
On Tue, Apr 7, 2009 at 9:27 AM, Mike Friesenegger
wrote:
> I just tried #cp vi vmsg 1 1 on my sles10 sp2 and it worked.
>
> Mike
>
> >>> On 4/7/2009 at 07:55
H - new stuff in SLES11 -
Found /etc/udev/rules.d
copied 51-dasd-0.0.0202.rules to 51-dasd-0.0.0203.rules and then edited the
file and changed all occurances of 202 to 203, reboot, now difference.
udev is not bringing 203 online at IPL.
On Tue, Apr 7, 2009 at 9:16 AM, Mark Pace wrote:
> Wor
I just tried #cp vi vmsg 1 1 on my sles10 sp2 and it worked.
Mike
>>> On 4/7/2009 at 07:55 AM, in message
<2d2d8f600904070655v45af818fxb640e19bae891...@mail.gmail.com>, Saul Thersites
wrote:
> I just tried to enter single user mode and I can not get pas the boot menu
> options. There are two op
I just tried to enter single user mode and I can not get pas the boot menu
options. There are two options 1. ipl and 2. Failsafe. I have tried two
methods to get to single user mode.
First, I tried #cp vi vmsg 0 1 (even though this is for zVM)
Second, I tried to use s instead of 1 or 2. No luck.
T
The 3215 driver converts a graphical "^c" into a control-C.
I suspect (but have not tested) that the syscons driver does the same.
The 3270 driver might also (but again, have not personally tried it).
So ... first thing to try is: shift-6, then "C", then enter.
-- R; <><
On Mon, Apr 6,
Kirk..
not seeing pa1 setup for ctl+c >> break >> if that is a break seq
anyone use bluezone out here may know what it would e??
--
Email Disclaimer
This E-mail contains confidential information belonging to the sender,
Hi John,
one very common mistake is to enter an incorrect number for the relative
port. - Please read my previous intructions very thoroughly.
Usually the relative port 0 belongs to the TCP/IP enabled adaptor that
is used by OS/2. The next adaptors (as listed in mpts) get the numbers
from 1 incem
46 matches
Mail list logo
