You say you want striping, but then you say you only have one volume
defined in the volume group... These two things are mutually exclusive.
The only way to have striping is to have multiple devices. The whole concept
of striping is to put sequential blocks of the logical volume on different
waiting in that case, but it
appears that the SLES9 install is trying to mount the LVM filesystems at
once, since otherwise I would have thought I'd just have a slow
install, not get the file descriptor 3 left open error. Everything
worked fine when I was installing all of root on a single minidisk
Hi Mark;
You suggest FCP for larger disk allocations, and we've looked at that here,
but we've back-burnered it for two reasons.
The first is mirroring. With our mainframe DASD, we get mirroring for free
(meaning that it requires no software or CPU time or additional I/Os within
our Linux
on LVM), I'd have at
least two filesystems overlapping--3 volumes but 5 mountpoints. I don't
have a problem with the I/O requests waiting in that case, but it
appears that the SLES9 install is trying to mount the LVM filesystems at
once, since otherwise I would have thought I'd just have a slow
@VM.MARIST.EDU
Subject: Re: Is it possible to do an initial SLES9 install on a
partially-LVM root?
One disk or twenty, LVM for all or just a few filesystems, it should
still
work. So you still have some problem in your definitions that hasn't
been
revealed here yet.
Since you're running into the problem
On Fri, Mar 14, 2008 at 9:13 AM, in message
[EMAIL PROTECTED], RPN01 [EMAIL PROTECTED] wrote:
-snip-
The only path outside of LVM is /boot, because something has to be outside
LVM to allow the system to boot.
And for those of you that make the mistake of not doing that, the error you get
I was trying to do this with a new guest by putting the following
directories in LVM (group system with one volume-204):
/usr
/var
/opt
/home
The rest of the root filesystem (including /boot) is on a regular
physical volume (200), and the
Did you partition the disks you placed in the LVM? You need to use
/dev/dasdc1 rather than /dev/dasdc, as an example.
We install with everything except the /boot in LVM controlled filesystems,
splitting out /, /var, /tmp, /home, and /opt into their own filesystems.
--
Robert P. Nix Mayo
On Thu, Mar 13, 2008 at 4:55 PM, in message
[EMAIL PROTECTED],
Collinson.Shannon [EMAIL PROTECTED] wrote:
I was trying to do this with a new guest by putting the following
directories in LVM (group system with one volume-204):
/usr
/var
/opt
-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Mark Post
Sent: Thursday, March 13, 2008 6:02 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Is it possible to do an initial SLES9 install on a
partially-LVM root?
On Thu, Mar 13, 2008 at 5:50 PM, in message
[EMAIL PROTECTED
Yup, looked like an S0C1 to me too... It was on a System Z BC, brand
new (just turned on IFL)
But fear not, it wasn't hardware...
On a whim I used real ssh from my Linux FTP server and it worked
fine... But surprisingly it came up in a graphic X window...
I had changed my default Putty
On Wed, Aug 8, 2007 at 3:38 PM, in message [EMAIL PROTECTED],
Lee Stewart [EMAIL PROTECTED] wrote:
-snip-
On a whim I used real ssh from my Linux FTP server and it worked
fine... But surprisingly it came up in a graphic X window...
That happens if X forwarding is turned on. YaST looks to
Hi all... I've done this dozens (hundreds?) of times, and I've never
seen this... Maybe I'm blurry-headed from looking at it too close,
maybe I'm missing something obvious, but...
This is the first Linux at a new site. Brand new VM (w/ a Vswitch)...
Downloading the bootstrap files goes
On Tue, Aug 7, 2007 at 2:30 AM, in message [EMAIL PROTECTED],
Lee Stewart [EMAIL PROTECTED] wrote:
-snip-
However the new ISOs included the updated SP3 CDs (...-CD1a.iso etc.).
And they did kick out a little more info, though not much help... On
the Putty session I now also see:
On Thu, Jun 28, 2007 at 11:32 AM, in message
[EMAIL PROTECTED], CWells Jackson
[EMAIL PROTECTED] wrote:
Hey Mark sorry to bother, I just installed suse 9 base
system and I am at the point of starting yast or yast2
and this is the error message I get while loggedonto
the server through putty
On Thu, Jun 28, 2007 at 3:21 PM, in message
[EMAIL PROTECTED], CWells Jackson
[EMAIL PROTECTED] wrote:
thanks Mark I got impatient now I get the following:
sorry for the bother
SUSE LINUX Enterprise Server 9 installation
program v1.6.36 (c) 1996-2004 SU
SE LINUX AG
hi,
I am currently having problems installing SLES9 on an virtual linux on ZVMV5R10.
I have copied reader files etc and setup the linux install exec, edited
configuration details into parmfile.
I IPL the install I am getting eth0: duplicate address detected! error when
eth0 is being configured.
Gordon Will wrote:
hi,
I am currently having problems installing SLES9 on an virtual linux on ZVMV5R10.
I have copied reader files etc and setup the linux install exec, edited
configuration details into parmfile.
I IPL the install I am getting eth0: duplicate address detected! error when
Before you IPL the deck, try to ping 10.100.80.122 from another system.
If you get a response back, that's the problem.
Gordon Will wrote:
hi,
I am currently having problems installing SLES9 on an virtual linux on ZVMV5R10.
I have copied reader files etc and setup the linux install exec,
have tried this, there is definately no server on my network with that ip
address.
thanks.
gordon.
---
---
This email and any files transmitted with it is confidential and
intended solely
for the
On Wednesday, 02/22/2006 at 03:21 GMT, Gordon Will
[EMAIL PROTECTED] wrote:
have tried this, there is definately no server on my network with that
ip
address.
There are PTFs to correct this problem. Please contact the Support
Center.
Alan Altmark
z/VM Development
IBM Endicott
Hi Folks
I am busy with a SLES9 install but am hitting a problem with
the /var/log/YaST2/y2log ( RAM disk) running out of space.
I am sure this is been caused by the number of disks the install process
is seeing at install time, the disk I am using are spread in the server
frame.
Questions:
-Can
, Gerard G
Sent: Tuesday, December 13, 2005 3:43 PM
To: LINUX-390@VM.MARIST.EDU
Subject: SLES9 install y2log too small
Hi Folks
I am busy with a SLES9 install but am hitting a problem with
the /var/log/YaST2/y2log ( RAM disk) running out of space.
I am sure this is been caused by the number of disks
Bob,
I don't see much running and if I try and start yast
By chance, are you trying to start yast from a 3270 session?
What am I missing?
You probably want to use SSH sessions out of habit after the install. 3270
sessions are still handy for CP commands.
If you have a Windows desktop, most
I had gotten things to work NFS wise, the GUI installer was fine until It
asked for CD2. Well there was no CD 2 in the /data/SLES9/sles9root/sles9/
path, just CD1. That's also where I found the initrd, parmfile etc. So
I dug around some and found /data/SLES9/sles9root/core9/CD1 (CD1, etc etc)
.
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
James Melin
Sent: Tuesday, August 09, 2005 1:17 PM
To: LINUX-390@VM.MARIST.EDU
Subject: [LINUX-390] SLES9 install stuff - more weirdness
I had gotten things to work NFS wise, the GUI installer was
fine until
:
Sent by: Linux on Subject: SLES9 install stuff -
more weirdness
390 Port
Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
Uriel Carrasquilla
Sent: Tuesday, August 09, 2005 1:30 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: [LINUX-390] SLES9 install stuff - more weirdness
There are two type of NFS (don't remember the details). One
of them
To: LINUX-390@VM.MARIST.EDU
Subject: SLES9 install stuff - more weirdness
I had gotten things to work NFS wise, the GUI installer was fine until It
asked for CD2. Well there was no CD 2 in the /data/SLES9/sles9root/sles9/
path, just CD1. That's also where I found the initrd, parmfile etc. So
I dug
The CD contains a document that describes the layout of this path, and
what
additional files you need to link or create to make it all work
correctly.
Or you can use the mksles9root script at
http://mikemacisaac.com/mksles9root
Mike MacIsaac [EMAIL PROTECTED] (845) 433-7061
cc
[EMAIL PROTECTED]
IST.EDU Subject
Re: SLES9 install stuff - more
weirdness
08/09/2005 01:18
PM
Sent: Tuesday, August 09, 2005 1:19 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: SLES9 install stuff - more weirdness
The CD contains a document that describes the layout of this path, and
what
additional files you need to link or create to make it all work
correctly.
Or you can use
@VM.MARIST.EDU
Subject: Re: SLES9 install stuff - more weirdness
I did use the mksles9root script. Which appeared to work. Found SP2,
etc
I have the /data/SLES9 dir which contains the ISO images and the last
updated version to the mksles9root.sh script that you reference in your
link. That ran
cc
[EMAIL PROTECTED]
IST.EDU Subject
Re: SLES9 install stuff - more
weirdness
08/09/2005
To
Sent by: Linux on LINUX-390@VM.MARIST.EDU
390 Port cc
[EMAIL PROTECTED]
IST.EDU Subject
Re: SLES9 install stuff - more
cc
[EMAIL PROTECTED]
IST.EDU Subject
Re: SLES9 install stuff - more
weirdness
08/09/2005 01:50
PM
Please
... when you can more easily loop-mount all the CDs, keeping everything
contained in the fewest number of files.
I ran into the problem of crossing mount points on the NFS-exported file
system. If your NFS connection allows crossing mount points, loopback
mounts are certainly an option.
... you
, August 09, 2005 1:58 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: SLES9 install stuff - more weirdness
I tried that first. It failed. So I went to the strategy that worked on
SLES 8, which was to specify the path including CD1 and it found the
others.
Nix, Robert P
and practice are different.
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Michael MacIsaac
Sent: Tuesday, August 09, 2005 2:15 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: SLES9 install stuff - more weirdness
... when you can more easily loop-mount all
]
IST.EDU Subject
Re: SLES9 Install VIA FTP
07/31/2005 02:58
PM
Please respond to
Linux on 390 Port
[EMAIL PROTECTED
that kind of setup to work.
Mark Post
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Jim Chappell
Sent: Tuesday, July 19, 2005 11:43 AM
To: LINUX-390@VM.MARIST.EDU
Subject: SLES9 Install VIA FTP
Has anyone attempted to install SLES9 via FTP where the FTP
Has anyone attempted to install SLES9 via FTP where the FTP server was a
z/OS platform?
If you have successfully accomplished this I would like to compare notes
about your success and my failure.
Jim Chappell
503-745-7841
503-349-5603(cell)
MS:C3E-IDS
[EMAIL PROTECTED]
-
Hey folks,
I'm new to the Linux world (but not to VM) and trying to install SLES9
un z/VM 5.1. We have a guest defined with a CTC coupled to the TCPIP machine.
During the install process the ctc becomes inoperative when we try to attach to
the FTP server. TCPIP message indicates
I would definitely suggest working with the Virtual Switch. It is much
easier to configure and work with.
Bates, Bob wrote:
Hey folks,
I'm new to the Linux world (but not to VM) and trying to install SLES9
un z/VM 5.1. We have a guest defined with a CTC coupled to the TCPIP machine.
cc
[EMAIL PROTECTED]
IST.EDU Subject
Re: SLES9 install under VM
19.07.2005 20:47
Please respond to
Linux on 390 Port
Folks,
I'm installing SLES9 under z/VM 4.4. When transfering the Installation
System via FTP, I don't get what I would expect or what the SuSE doc
seems to indicate I should get for byte counts.
I ftp from a VM Linux guest to other which has copies the SLES9 ISOs. A
dir of boot/ shows:
dir
If you downloaded these from SuSE, check the MD5SUM values.
Froberg, David C wrote:
Folks,
I'm installing SLES9 under z/VM 4.4. When transfering the Installation
System via FTP, I don't get what I would expect or what the SuSE doc
seems to indicate I should get for byte counts.
I ftp from a
David,
Before you put the kernel and RAMdisk did you do:
ftp bin
ftp site fix 80
Mike MacIsaac [EMAIL PROTECTED] (845) 433-7061
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL
on 390 Port LINUX-390@VM.MARIST.EDU
05/24/2005 09:08 AM
Please respond to
Linux on 390 Port
To
LINUX-390@VM.MARIST.EDU
cc
Subject
Re: SLES9 Install with FTP under VM question
If you downloaded these from SuSE, check the MD5SUM values.
Froberg, David C wrote:
Folks,
I'm installing SLES9
When you transfer the files to VM make sure the files are
being transferred Fixed 80 with the VMRDR and INITRD files in
binary. Chapter 8.3 of the SUSE sles9 manual
Architecture-Specific Information. This manual is on the
sles9 CD1 disk.
Thanks for all your replies so far. I
If you downloaded these from SuSE, check the MD5SUM values.
Thanks. I double-checked the md5sum and it looks fine.
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED]
Did you do Parmfile as bin or ascii?
Froberg, David C [EMAIL PROTECTED]
Sent by: Linux on 390 Port LINUX-390@VM.MARIST.EDU
05/24/2005 09:56 AM
Please respond to Linux on 390 Port
To: LINUX-390@VM.MARIST.EDU
cc:
Subject:Re: [LINUX-390] SLES9 Install
Did you do Parmfile as bin or ascii?
Ascii. The SuSE doc shows doing an asc command just before the get for
parmfile.
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED]
Hello, I'm still having some problems installing sles9 on an LPAR.
1) from HMC loaded SLES 9 successfull.
2) SSH to lpar sucessfull
3) Selected SAMBA as install source.
a) replied with appropriate IP number for my PC and CD as my directory
and the ping was successfull.
4) Then I
Robert,
3) Selected SAMBA as install source.
Does the LPAR have have access to a Linux Intel server (or even Solaris,
AIX, ...)? If so, I describe how to set up a SLES9 install tree served
via NFS in chapter 5 of the redbook z/VM and Linux on zSeries: From LPAR
to Virtual Servers in Two Days
to your small LPAR for testing.
This leaves a bad taste in my mouth too
Date: Mon, 28 Mar 2005 16:51:24 -0500
From: Jeremy Warren [EMAIL PROTECTED]
This is less a question than it is a description of a weird
problem I had during SLES9 install just in case anyone else runs
into it.
We
This is less a question than it is a description of a weird problem I had
during SLES9 install just in case anyone else runs into it.
We have a micro lpar with z/VM 5.1 on it. This LPAR only has 128MB of
memory, 64MB of xstore, one mod9 for swap. It's intended to be a
quarantine area that we
.
Tom Duerbusch
THD Consulting
[EMAIL PROTECTED] 03/28/05 3:51 PM
This is less a question than it is a description of a weird problem I
had
during SLES9 install just in case anyone else runs into it.
We have a micro lpar with z/VM 5.1 on it. This LPAR only has 128MB
of
memory, 64MB of xstore
PROTECTED]
03/28/2005 05:12 PM
To: [EMAIL PROTECTED], LINUX-390@VM.MARIST.EDU
cc:
Subject:Re: Sles9 Install Memory Issue
The problem is one of timing.
During the install, you don't use swap files. An incore RAM disk is
created in which SLES9 is laid down
/removing dynamic dasd to a running
machine fairly heavily before we move this over..
Thanks!
Jeremy
Tom Duerbusch [EMAIL PROTECTED]
03/28/2005 05:12 PM
To: [EMAIL PROTECTED], LINUX-390@VM.MARIST.EDU
cc:
Subject:Re: Sles9 Install Memory Issue
The problem
One other thing about Sles9 for newbies (I still classify my self
there).
Suspect all documentation (i.e. Redbooks and the like) that are not
explicitly for Sles9. There are sufficient changes between releases
that require you to know what is going on, in order for you to use SLES8
documentation
Thanks for all the replies.
Mark Pace wrote:
If you are using putty for your ssh client check the SSH section and be
sure you have SSH protocol 2 selected. I have seen the invalid password
many times when SSH protocol 1 was selected.
Changing the putty SSH protocol to 2 worked. I am now able
I am trying to install SLES9 (free download) - it will be used for a real
evaluation.
I am able to IPL the rdr and all is OK setting up the network (OSA) etc - I
chose FTP and SSH.
However when I attempt to use SSH from my workstation I am prompted for the
root password but am denied access -
PM
To: LINUX-390@VM.MARIST.EDU
Subject: SLES9 - install problem - logging in
I am trying to install SLES9 (free download) - it will be used for a real
evaluation.
I am able to IPL the rdr and all is OK setting up the network (OSA) etc - I
chose FTP and SSH. However when I attempt to use SSH from
cc
[EMAIL PROTECTED]
IST.EDU Subject
Re: SLES9 - install problem
Peter,
The symptoms you describe sound vaguely familiar. Did you perform the
second half of the SLES9 install?
After you IPL from reader/tape, you answer networking questions, bring up
the graphical install and format DASD, partition disks, choose RPMs and
then they are laid down onto DASD
To
Sent by: Linux on LINUX-390@VM.MARIST.EDU
390 Port cc
[EMAIL PROTECTED]
IST.EDU Subject
Re: SLES9 - install
Peter,
You are correct - I have not done the 2nd half.
At the end of the 1st half YAST does not give me any choice
During the intall questions, when you get to the prompt:
Which terminal do want to use?
1) X-Window
2) VNC (VNC-Client or Java enabled Browser)
3) ssh
Do you enter 1
I always use 3, works great.
Michael MacIsaac wrote:
Peter,
You are correct - I have not done the 2nd half.
At the end of the 1st half YAST does not give me any choice
During the intall questions, when you get to the prompt:
Which terminal do want to use?
1) X-Window
2) VNC (VNC-Client
, 2005 12:31 PM
To: LINUX-390@VM.MARIST.EDU
Subject: SLES9 - install problem - logging in
I am trying to install SLES9 (free download) - it will be used for a
real
evaluation.
I am able to IPL the rdr and all is OK setting up the network (OSA) etc
- I
chose FTP and SSH.
However when I attempt to use
If you are using putty for your ssh client check the SSH section and be
sure you have SSH protocol 2 selected. I have seen the invalid password
many times when SSH protocol 1 was selected.
Mark D Pace
Senior Systems Engineer
Mainline Information Systems
1700 Summit Lake Drive
Tallahassee, FL.
We may have a winner!
chroot_local_user=YES
Added that the vsftpd.conf and the install now seems to be working!
Do I believe it? NO!
I'll attempt 2 more installs. If they work, I will take out the
chroot_local_user and try again. (of course, I will save the good Suse
9 install.)
But it does
Tom,
If I enter in /data/sles9root, then I can load the ram disk.
But I wonder if yast can handle the /data/sles9root or if
it is also looking for /sles9root?
The SuSE Architecture Specific Information manual says:
INST_IP_DIR=/s390 Enter a directory on the installation server, which
holds
A couple of things that have been a problem for me.
Be sure that in vsftpd.conf you have setchroot_local_user=YES
Also - check your script you used to create the installroot. Make sure
that the echo commands have the -e switch
echo -e /sles9/CD1 /sles9/CD1\n/core9/CD1 /core9/CD1
linux15:/data/sles9root/yast # cat order
/sles9/CD1 /sles9/CD1
/core9/CD1 /core9/CD1
linux15:/data/sles9root/yast #
I think the files order and instorder are correct.
I don't have chroot_local_user specified, so I assume that the default
is no. I'll update and try it again.
Thanks
Tom Duerbusch
linux15:~ # ls -l /data/sles9root
total 1
drwxr-xr-x5 root root 224 Mar 9 14:41 .
drwxr-xr-x 12 suse9users1376 Mar 9 17:16 ..
lrwxrwxrwx1 root root 14 Mar 9 14:41 boot -
sles9/CD1/boot
lrwxrwxrwx1 root root 17 Mar 9 14:41
On Thursday, 03/10/2005 at 11:15 CST, Tom Duerbusch [EMAIL PROTECTED]
wrote:
But, so far, using a Linux/390 ftp server gave me the same results as
using Samba on my Win/2000 box, except for the much greater performance
the Linux/390 side has due to not having to go out on the wire.
Tom, when
after much trial and error I got the SLES9 install to work from a zvm linux ftp
server. My ../installroot directory resembles your /data/sles9root.
The directory with the install material in my case is
/home/usrdk01/installroot. I authorized with chmod all files in installroot
and its
Hi Alan
Originally, I downloaded the iso images to Win/2000 and burnt the CDs.
The CDs all have, what looks like, a normal directory structure.
This was the same process that I used for Suse 7 and Suse 8 installs.
And it still works with Suse 8 installs as I did a fresh install to
create my Linux
Tom,
I then tried using a mount with loop to mount the iso images. Same
problem with media error.
Did you run md5sum -c against an MD5SUM file? The Novell server has been
known to modify bytes upon download. If not you can cut and paste.
For 31-bit CDs:
# cat MD5SUM.sles9
: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Tom
Duerbusch
Sent: Wednesday, March 09, 2005 5:36 PM
To: LINUX-390@VM.MARIST.EDU
Subject: SLES9 Install problems again
-snip-
Where before, I thought I was having problems with the installation process,
now I think it is something more basic
@VM.MARIST.EDU
Subject: Re: SLES9 Install problems again
That sure didn't show much. I'm using vsftpd.
One thing I have to say, now that I'm using a Linux/390 guest as the ftp
server, vs using Win/2000 over a real network, it is so much faster to get
to the error
[snip]
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Tom
Duerbusch
Sent: Wednesday, March 09, 2005 10:07 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: SLES9 Install problems again
That sure didn't show much. I'm using vsftpd.
One thing I have to say, now
To
[EMAIL PROTECTED] LINUX-390@VM.MARIST.EDU
IST.EDU cc
Subject
01/20/2005 04:15 Re: even more sles9 install
PM
it right.
-Cameron
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
Mark D Pace
Sent: Friday, January 21, 2005 10:09
To: LINUX-390@VM.MARIST.EDU
Subject: Re: even more sles9 install weirdness
I recreated the entire install root and still get the same message
That is defineately a bad ftp path statement. you really need to check
that. when SUSE 9 fails on this type of error you should get a dialog box
that has an option to check details. When you check the details you can
change the ftp path and put in a password and try it again until you get
it
did you do an md5sum on them? yes true you may need to download again.
-Cameron
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
Mark D Pace
Sent: Friday, January 21, 2005 12:19
To: LINUX-390@VM.MARIST.EDU
Subject: Re: even more sles9 install weirdness
more sles9 install weirdness
That is defineately a bad ftp path statement. you really need to check
that. when SUSE 9 fails on this type of error you should get a dialog box
that has an option to check details. When you check the details you can
change the ftp path and put in a password and try
sles9 install weirdness
-snip-
Does anyone know the correct checksums for the SuSE 32bit ISOs?
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390
Here are the MD5SUMS for SuSE SLES 9 31 bit ISOs
Ah Ha! I have a bad ISO, but it's CD6. Not sure what that has to do
with the error messages I am getting on the ftp attempt of CD1.
Oh well. Going on vacation. I'll mess with it when I get back.
Thanks to all that helped.
Mark D Pace
Thanks to all that have blazed the trail of sles9 before me.
I have followed this thread pretty close and have used the installroot
procedure to create an installroot for my CDs. I can start the install,
get into yast, setup the DASD, and then I change my software to Minimal
install. But when
even more sles9 install weirdness
01/20/2005 02:46
PM
Please respond to
Linux on 390 Port
[EMAIL PROTECTED]
IST.EDU
Thanks to all that have blazed the trail of sles9 before me.
I
:46 PM
To: LINUX-390@VM.MARIST.EDU
Subject: even more sles9 install weirdness
Thanks to all that have blazed the trail of sles9 before me.
I have followed this thread pretty close and have used the installroot
procedure to create an installroot for my CDs. I can start the install, get
into yast
On Wed, 5 Jan 2005 21:26:44 -0500, David Kreuter
[EMAIL PROTECTED] wrote:
Tried at 768M. At least it was faster. Checked the SUSE manual, from an
SSH session it says to use:
/usr/lib/YaST2/bin/YaST2.sshinstall
Guess what - it's not there! I worked my way down from /
Patience my friend ;-)
Hmm. Anyone seen this? I get linux to boot out of the rdr, and when I
choose SSH or VNC (done this many times), I can't get any further.
If I SSH into my linux machine, it can't find yast or yast2 !
With the VNC choice the VNC client just dies.
Extract from console log, contains unexpected
yup 512m for the install
Lee Stewart wrote:
Do you have 512M for the install? SLES9 supposedly needs that much and I
got all sorts of strange (and some similar) things trying it in less
memory...
Lee
At 04:10 PM 1/5/2005, you wrote:
Hmm. Anyone seen this? I get linux to boot out of the rdr, and
Tried at 768M. At least it was faster. Checked the SUSE manual, from an
SSH session it says to use:
/usr/lib/YaST2/bin/YaST2.sshinstall
Guess what - it's not there! I worked my way down from /
Jeesh.
David
Lee Stewart wrote:
Do you have 512M for the install? SLES9 supposedly needs that much and
Hi!
On Tuesday 07 December 2004 16:03, Rod Furey wrote:
Tom Duerbusch wrote:
O man...
They left out regina! How can I operate without Rexx!
Simple - you download the latest Regina release and
compile it.
Or get the SLES9 SDK. (But don't ask me where from, I'm just an
engineer... :)
On Mon, 6 Dec 2004 16:48:35 -0700, Ledbetter, Scott E
[EMAIL PROTECTED] wrote:
Now I'm wondering about my SLES9 images. I downloaded all 6 CDs for both 31
and 64 bit versions from the Novell website to my Win2K PC. Not a single
one matches the MD5 checksum on the Novell Download webpage.
]
Behalf Of Rob
van der Heij
Sent: Tuesday, December 07, 2004 3:27 AM
To: [EMAIL PROTECTED]
Subject: Re: [LINUX-390] SLES9 Install hang
On Mon, 6 Dec 2004 16:48:35 -0700, Ledbetter, Scott E
[EMAIL PROTECTED] wrote:
Now I'm wondering about my SLES9 images. I downloaded all
6 CDs for both
1 - 100 of 132 matches
Mail list logo
