I'm not sure why the decision was made between SuSE 9 and SuSE 10 to stop
partitioning the disks. This seems to be almost a throw-back to SuSE 8,
where you had to pause in the install to log in, format and partition all
your dasd before continuing the installation.
If the LVM option requires that the disks be partitioned, why doesn't it
check for that, and partition them if required? Why make the user do this,
if it's required every time, and you can't get a successful install without
it?
True, you can partition the disks in SuSE 10 from the GUI, but it is VERY
NON-OBVIOUS as to how one would do it. Selecting the disk and clicking on Do
Not Format... How does that relate to partitioning? The whole idea, to me,
would mean that nothing would be done to the disk. Instead, it magically
gets formatted.... It'd be handy if there was just a "Partition Disk" button
or some such, that mere mortals could hope to understand....
I'm not sure that most of these vendors (like Novell and RedHat) understand
that "Here's the workaround..." doesn't bolster a mainframer's confidence in
the product. It should work right, not work after you jump through this list
of additional hoops. And, when caught in this situation, it should get
fixed. Documented work-arounds are NOT FIXES.
--
.~. Robert P. Nix Mayo Foundation
/V\ RO-OE-5-55 200 First Street SW
/( )\ 507-284-0844 Rochester, MN 55905
^^-^^ -----
"In theory, theory and practice are the same, but
in practice, theory and practice are different."
On 10/24/07 1:33 PM, "Paul Noble" <[EMAIL PROTECTED]> wrote:
> Thanks. I'll try that. I only set the virtual memory that high because someone
> here at work, who claims to have worked with SUSE linux, suggested that the
> error code I was getting may have indicated I was out of memory. It was
> originally at 512M.
>
> The results of the cat /proc/partitions was just ONE listing for each volume,
> the "dasda" version, not the "dasda1".
>
> Thanks,
>
>>>> Mark Post <[EMAIL PROTECTED]> 10/24/2007 1:52 PM >>>
>>>> On Wed, Oct 24, 2007 at 1:29 PM, in message
> <[EMAIL PROTECTED]>, Paul Noble
> <[EMAIL PROTECTED]>
> wrote:
> -snip-
>> I don't know if this makes any difference or not. Our SLES10 base system,
>> which I cloned for this application, has no swap space. I have not yet added
>> any to the clone. The vm has 2G of virtual storage and there is essentially
>> nothing running in the system, yet. Do I need to add swap space, first? I
>
> No, that shouldn't make any difference. Although, you should shrink the
> virtual storage down to something reasonable, say 128MB, and also add a VDISK
> for a paging volume.
>
>> didn't when I did this on a SLES 9 system a few months ago. In that case, I
>> created the LVM first and added swap later.
>
> If you do a "cat /proc/partitions" command, and you don't see your volumes
> listed (at least twice), once with "dasda" and again with "dasda1", then you
> haven't put a partition on them. (Substitute the appropriate device name for
> your 6 new DASD volumes.) Go back into yast, create one partition on each of
> them (using the "do not format" check box), and then go into configure LVM
> again.
>
>
> Mark Post
>
> ----------------------------------------------------------------------
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
>
> ----------------------------------------------------------------------
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
