Mailinglist Archive: opensuse-bugs (7967 mails)

< Previous Next >
[Bug 239630] Documented 256MB not sufficient for install, requires 384MB.
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Thu, 22 Feb 2007 17:47:57 -0700 (MST)
  • Message-id: <20070223004757.561CEF8F@xxxxxxxxxxxxxxxxxxxxxx>
https://bugzilla.novell.com/show_bug.cgi?id=239630





------- Comment #20 from webclark@xxxxxxxxxxxxxxxx 2007-02-22 17:47 MST -------
I apologize for the "rant" nature of my previous post.
Here is a concrete suggestion:

Initial installation screen:
Either:

Your memory configuration of XXXMB is sufficient for
all but the most complex and involved installations.
[Options to manage Installation Memory Requirements]
or
Your memory configuration of XXXMB may not be sufficient
depending on the details of your installation.
It is recommended that you use the available options
to manage memory usage.
[Options to manage Installation Memory Requirements]

The [Options to Reduce...] button would take you to a screen
presenting information and options. These are dependent on
the FACTS of usage, which I am not clear on so this is only
and example and will need to be adjusted to reflect the true
situation:

The simplest and most effective action you can take
to minimize memory requirements during install is to
accept the offered default install.
(or is it)
The simplest and most effective action you can take
to minimize memory requirements during install is to
not add the "Add-Ons" CD to the installation sources
and to deselect all but the "XXX" package (minimum list).

Additional packages can be installed through YAST
found under "Computer/Administrator Settings" after
booting into your new system with identical results,
and are performed with the same installation interface.

This will enable you to install with XXX-YYYMB
depending on the complexity of your partitioning
scheme. Preparing only the partitions needed for
the basic system (/, /var, /bin, /usr, /sbin, /etc,
including usage of md and lvm for these partitions
if desired) during installation will minimize
partitioning requirements. Other partitions can be
prepared after you boot into your new system.

Other actions to reduce memory requirements:

[ ] Disable all logging during install. Logs for
post-mortum analysis of installation problems
will not be available, but memory usage will
be limited to XXXMB with the minimum install
described above.

[ ] Add swap space. This will eliminate(?) all(?)
memory concerns.
[ ]
Select device/partition from pull-down list.
Partition must be FAT32, Ext, Reiser, nor NTFS
and must have at least 512MB of free space.
A 512MB linux swap file will be created. No
data loss should be expected, but be sure to
back up all data on the physical drive before
proceeding. Note that a typical install will
incur on the order of x000 write cycles, which
represents significant "wear" should you select
a flash device.

(Could you also allow creation of a swap file
on an NFS or SMB share? One side of your
customer base will have another Linux machine,
the other side are apt to have a windows machine)

[Shell] Drop into shell. Will return here on Exit.

Note that unless logging is disabled, every click,
menu change, and action consumes memory.

Next, maintain a "Free memory" monitor in the corner of every
installation screen. This will provide constant feedback to
the customer so that they will learn what hurts. Perhaps
this is not necessary, but it is an idea.

Arrange to abort the installation if you run out of memory.
Ideally this would be air-tight, for example with a shim or
wrapper which checks availability before every operation that
consumes memory, but I understand that this may be difficult
or require a large rewrite that is not practical.
You have a running UNIX system, you could have a task that
wakes up every 1 second to check free space, raising the
alarm when the free memory drops to the size of the maximum
atomic usage. This would simply quit a little bit short of
full. Just some ideas.

All this will give the user a very concrete indication of how
much memory is needed, tools to deal with low memory situation,
and good information to understand whether those tools will
be enough. It will eliminate trial and error. The low memory
detector will protect the user from an undetected bad install.

Thanks again. Hope this is helpful.


--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

< Previous Next >