[Bug 239630] New: Documented 256MB not sufficient for install, requires 384MB.
https://bugzilla.novell.com/show_bug.cgi?id=239630 Summary: Documented 256MB not sufficient for install, requires 384MB. Product: openSUSE 10.2 Version: Final Platform: i686 OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Documentation AssignedTo: rwalter@novell.com ReportedBy: webclark@rochester.rr.com QAContact: ke@novell.com Installer needs 384MB (Started with 256, tried 320, 384, 512. 384 and 512 worked). Installation instructions say that you may have trouble with less than 256 and a referred page discusses how to reduce memory requirements. Note that my problem occurred before I got into the details of the install, so the problem I think SHOULD occur on ANY attempt to install with 320MB or less. It was not dependent on any input from me specific to my installation other than language and accepting the license agreements. You CANNOT INSTALL with 256MB! Problem (and solution) was replicated on another machine. Solution is to simply change the install instructions to say that you need XXXMB of memory to install (384? 512?). Never the less, it would be real nice if there were a way to do an install on every machine it can run on, e.g. even 128MB. Specific behavior observed (From suseforums posting by rnsc): First establish that I have good CDs: Downloaded, checked MD5SUMs, burned, cmp xxx.iso /dev/hdd. CDs are good. Began install, got through language etc. to screen asking what kind of install to do. First problem (Minor, got by it): "New Installation" has "Include Add-on Products from Separate Media" grayed out. This was offered in 10.1 (not grayed) and worked fine. Clicking "update" un-grays "Include Add-on...", Then clicking "New Installation" leaves it available. (This is the first sign of flakeyness). Select "New Installation" and "Include Add-On Product from Separate Media" Machine catalogs CD1, then puts up the "Add-On Product Installation" screen. I click "Add" Dialog asking me to select the media type comes up. I click on "CD" and "Next" Dialog asking me to "Insert the Add-On Product CD" comes up. Second problem (Minor, got by it): Pressing the eject button on the drive does not eject the install CD to enable me to put in the Add-On CD. In 10.1, it did. Clicking the provided "Eject" button on the GUI ejects the CD. I put in the "Add-On" CD. Click "Continue" Third (MAJOR) problem:
The above sequence was done multiple times. What happened next varied:
Example #1: "Unable to create catalog from URL 'cd:///', Details: Unknown source type for cd:/// Try again? Example #2: System freezes with mouse arrow roughly in middle of screen. Mouse does not respond. control-alt=F3 takes me to the system log. "Segmentation Fault at SourceManager.ycp: 472"
Followed by many shell-script like errors, segmentation errors, core dumps.
Problem appears to be 100% repeatable in the sense that it never gets beyond this point, although exactly what happens varies. System HAD been running opensuse 10.1 for a few weeks before this. <<< I now know that the machine was running out of RAMDISK, so files created by the install shell scripts were not able to be written. When the information was read from the files, the shell variables were set to NULL, and so everything falls apart. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=239630 rwalter@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rwalter@novell.com AssignedTo|rwalter@novell.com |cihlarov@novell.com ------- Comment #1 from rwalter@novell.com 2007-02-05 00:06 MST ------- We're only dealing with possible documentation issues in this bug. If you want more done with the problems, you need to file separate bugs. Klara, I think this chapter is yours. Can you research the requirements with the appropriate parties and fix as they recommend? -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=239630 cihlarov@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |webclark@rochester.rr.com ------- Comment #2 from cihlarov@novell.com 2007-02-05 01:44 MST ------- Normally 256 MB is sufficient for installation from CD/DVD. Only network installation needs more. Can you provide more information about used HW (motherboards, processors, graph. card)? Do you use graphic card with shared memory? Have you tested your RAM after segfault? -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=239630 webclark@rochester.rr.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |webclark@rochester.rr.com Status|NEEDINFO |NEW Info Provider|webclark@rochester.rr.com | ------- Comment #3 from webclark@rochester.rr.com 2007-02-05 18:37 MST ------- Regarding "We're only dealing with possible documentation issues in this bug. If you want more done with the problems, you need to file separate bugs." I did not discuss any problems in this bug report that were not resolved by installing 512MB of memory. All of the flakey things that I report (and more) only happen when I try to install with 256MB of memory. Looking at the messages coming out of the console, it was clear that shell files were malfunctioning due to not being able to create files, due to the RAM disk being full. Suse 10.2 will not install with 256MB of memory. It installs perfectly with 512MB, on the same hardware (a few times). Based on the "grayed out box" problem (described previously, and again below), I believe it will install with 384MB but have not seen it all the way through. I assume that someone there has successfully installed in 256MB. I don't know how to reconcile this. I gather I am conversing with the documentation team. If SUSE steadfastly believes that it should install in 256MB of memory (Which would be a GOOD thing from my perspective), then perhaps somebody else should be involved too! Regarding your request for more information: I think replication on another PC rules out a memory problem, however the machine has been running memtest86 for several weeks without error. In trying to track down the problem (before I discovered the problem with memory size), I swapped memory modules, tried different memory slots, and tried different processors. Let me give more detail as to what was done, then describe the PC configurations. PC#1 had the problem as described above. Notice the part about "[ ] Include Add-On Products from separate Media" being grayed out. But it can be coerced to be selectable by going to "Update" and back to "New". With 384MB or more this does not happen - the option to include add-on products is always presented. Doesn't this indicate something? If I proceed I have the problems described above. I can give more detail as to my selections. Procedure with PC#1 (PC on which bug report was based) (I will discuss another PC later): (1) I have 4 disks installed, and set up 3 primary and several logical partitions on one pair, all mirrored. The second pair were formatted as a single logical, again mirrored. One logical from the first set and the logical from the second set were put under LVM control as a volume group and a logical volume created. I did go in and out of the menus, LVM, mirroring, etc. several times, mostly because it seemed to forget what I typed! Perhaps this created more data than normal, but notice that the first sign of trouble came with not being able to check the "Include Add-On..." box, long before starting disk partitioning. Once I put in 512MB of memory there were not problems and it went VERY smoothly. (2) I did select quite a bit to install, about 5 GB. Again, trouble came long before selecting all of this. Most of the time problems came during partitioning, before getting to the package selection! PC#2 is a completely separate PC. I have the same situation regarding the "Include Add-On Products from Separate Media" being grayed out, then selecting "Update", then "New" and having it available. This happens with 256MB, not with 384 or more. I checked this before I put in the bug report, but have since installed 10.2 on it (the one I am typing on!) with the same install setup I described above except no mirroring (LVM is being used). I just checked it again tonight, aborting the install after seeing this so I didn't wipe out my system! Note that PC#2 has been running reliably, 24 hours most days being booted perhaps every few weeks since SUSE 8.1 or 8.2, and Windows 98 before that. PC#1 is the same age, but has not been used since new. It has been running memtest86 for several weeks now (I did not put the bug report in promptly). Configuration: PC#1: ASUS P2B-B (Intel 440BX chipset) Intel P3 600E (Coppermine, slot 1) (Also tried 800 and 400) Crucial 256MB ECC (440BX supports ECC) Memory main configuration Crucial 128MB ECC and 64MB ECC used to test memory sizes ATI Radeon (original) video card used at first, but also tried nVidia 5200. Neither card uses shared memory. Both exhibited issues discussed here. Intel Pro-100 Ethernet card SIIG USB-2 PCI card that I have been using since Win98 and through Suse 8.1, 8.2, 9.x in PC#2 Promise Ultra33 IDE controller, again used in PC#2 since Win98 and through Suse 8.1, 8.2, 9.x Creative Labs Soundblaster Live! PC Power & Cooling power supply An old CD-ROM drive (Toshiba or Sony) that I have been using forever in various systems. PC#2: ASUS P3B-F (Intel 440BX chipset) Intel P3 800E (Coppermine, slot 1) Crucial 256MB ECC (440BX supports ECC) Memory main configuration Crucial 128MB ECC and 64MB ECC used to test memory sizes nVidia 5200 Card does not use shared memory. Intel Pro-100 Ethernet card Adaptec USB-2 PCI Card used since 9.x Creative Labs Soundblaster Live! Antec Power Supply NEC ND3540A DVD +/- RW I'll be glad to answer more questions. HAS anyone gone through a 256MB install? If so, what's with the grayed "Include Add-on" box? Thanks. Great product. I tried Kubuntu first (I like the debian package stuff), but Suse 10.2 is at least a year ahead in maturity if they work hard and you stand still. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=239630 cihlarov@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|cihlarov@novell.com |bnc-team-screening@forge.provo.novell.com ------- Comment #4 from cihlarov@novell.com 2007-02-06 02:55 MST ------- This is not a documentation problem. openSUSE 10.2 should be possible to install on system with at least 256 MB RAM (it is only limit on linuxrc, CD/DVD local installation is possible with 200 MB). Please, find a proper owner for the bug. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=239630 chrubis@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team- |yast2-maintainers@suse.de |screening@forge.provo.novell| |.com | -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=239630 jdsn@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dmacvicar@novell.com, ma@novell.com Status|NEW |NEEDINFO Info Provider| |webclark@rochester.rr.com ------- Comment #5 from jdsn@novell.com 2007-02-07 06:15 MST ------- @Ray Clark Could you please provide the log files of a failing installation (with 256MB RAM). For details see: http://en.opensuse.org/Bugs/YaST#Attachments_-_y2logs.2C_hwinfo_etc. @duncan, ma: probably libzypp problem ? -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=239630 jdsn@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|yast2-maintainers@suse.de |dmacvicar@novell.com Status|NEEDINFO |NEW Info Provider|webclark@rochester.rr.com | -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=239630 ------- Comment #6 from webclark@rochester.rr.com 2007-02-07 18:13 MST ------- Created an attachment (id=117984) --> (https://bugzilla.novell.com/attachment.cgi?id=117984&action=view) y2logs taken at key point through ultimately failed install with 256MB, including after yast crashed and as machine flaked out y2logs were captured at key points through install with 256MB. Install failed, several interesting malfunctions. See enclosed readme for step-by-step log of what happened. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=239630 ------- Comment #9 from dmacvicar@novell.com 2007-02-08 09:18 MST ------- ZYPP creates a copy of the repository, to validate its integrty and operates only on the copy. For non remote install we could make the copy have only symlinks to the original files, but then we can't switch CDs. We just need to use less memory, and that comes with 10.3 -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=239630 locilka@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Major |Enhancement Status|NEW |ASSIGNED Component|Documentation |YaST2 Product|openSUSE 10.2 |openSUSE 10.3 Fixed in Milestone|--- |unspecified Version|Final |unspecified ------- Comment #13 from locilka@novell.com 2007-02-15 09:14 MST ------- Defining how much memory is requested for the installation or update is kind of academic debate. It always depends on many factors such as * how many things user change * how many times does he change them * how many packages are selected for the installation * how many add-ons are selected for the installation * ... My testings with optimized logging (almost no logging) said that a computer was able to be installed (using add-ons) with 170-180 MB of memory (of course, without swap). I've tried to use /proc/meminfo to get maximum available memory (waiting for kernel developers for a correct figure). I hope this is the right way how to check whether using a new Add-On product is possible :) -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=239630 ------- Comment #14 from ke@novell.com 2007-02-16 03:04 MST ------- I'd like to propose to add a "Tip" to the docs: "If your machine is low on memory (less than 512 MB) do a minimal installation without add-ons first. After the system installation start YaST again and add additional software." Feel free to add more details or change the wording. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=239630 ------- Comment #19 from webclark@rochester.rr.com 2007-02-21 19:47 MST ------- Warning, this is long. But I think/hope I make some good points. I will try to convey difficulties I see with the current situation and explain how I believe it can be fairly easily addressed. Please forgive me if I come across as being excited... I am! I am anxious for Linux to be usable by "normal" people, and I feel that there is a very thin barrier, the main barrier being an assumption by Linux people that the user knows how Linux works on the inside, and that if they don't, too bad, they better go learn. I believe the concepts you need to convey are are easy and the functionality you need to provide is minimal. What does do a "minimal installation without add-ons first" mean? That I can do anything I want with the base, just don't do any add-ons? Or should I also just accept the default to minimize changes (which generate logs)? Or should I cut down the package list to minimize what is installed? And will this work with 256MB? You specify 512MB, but I feel that 256MB is a magic number because Linux does not run too bad in 256MB for a single user, and I have 6 machines with that constraint. But can I install? People's old windows machines are becoming less and less functional, and they balk at pouring money into a new machine and XP or Vista. They just need reason to hope that it is going to work and not be a hassle. This is a real opportunity for Linux. Having read the "Installation with Little Memory" guidance on the wiki, these are written for someone who is familiar with the Linux and/or Suse boot process. This is probably obvious to the author, but not to your average user. This is good for one set of users who wants to know, but not most who want to get it installed. I am no dummy, and have been using and installing various version of UNIX, SunOS, and Linux for 30 years. I can understand almost anything, but I don't know the implementation details of the linux boot process (although I am learning). And everyone does not WANT to understand, or have time to understand.
But before it is made more usable, there is something more important, whether you do anything about helping people with low memory or not:
[1] Enable the installer to monitor space or detect when it runs out of memory BEFORE it malfunctions. Put up a message and stop, even if very ungracefully. Rule number one is to not continue working in a corrupted state. Currently you get corrupted during package selection and continue, partitioning and continue, etc. Stuff I put in disappears, and I just keep recirculating in the menus hoping it will stick and I can get an install. Sometimes I can! If I get through, what confidence do I have that it worked right? What about if I have enough memory that I have no apparent problems? Can I trust that there are no hidden problems that are going to cause unexplained problems to chase later? Something that fell off of the end of the shell variable assignment on a boundary that happened to not cause a problem? What if it appears to work and I load all my data on but something is not right? I need to have 100% confidence that *IF* I get through the install smoothly, that it worked correctly, as I specified. As for dealing with low memory: [2] You indicate that one can do the add-ons later. I was not sure if there were trade offs between doing it up front vs. later, and I was not aware that selecting it used a substantial amount more memory. A list of 10,000 50 character package names would only take 512K of memory. It is not that simple? I do not have visibility into your implementation details. Inform me of the constraints and provide functionality or information to deal with them. Explain/define up-front on a screen, or in the installation instructions, the behaviors which result in the minimum RAM being used during install. It is only fair to leave out stuff that can be delayed until later with reasonable ease and without consequence. For example, you have a great integration of md and lvm. I expect that if it is possible at all that it would be much more difficult to set up my mirrored partitions and logical volumes later. A question I have after reading all of your comments above is whether minimum memory requirements are achieved with minimum package installation or minimum deviation from the default install! This could be a critical point. It would only take a couple sentences to convey what is needed. Regarding the "reduced memory" advise, does the text mode installer provide the full/same functionality as the graphical? I should not have to take the time to experiment. Please just tell me what the tradeoffs are so I can choose the correct direction without trial and error. This is yes/no and perhaps a short list of generalizations to tell me how it is different. I don't know what a linuxrc parameter is. Can you tell me in a sentence or two what to do rather than refering me to a generalized writeup on a Linux subsystem? "When it says this, type any of the following separated by a space". Addition of this single sentence would have made the wiki "Installation with Little Memory" write up much more useful, useful for anybody! Or better yet, you could add a screen up front with buttons and text boxes to toggle these things for the user. You don't want to have the installation dominated by this memory stuff, but I am sure you could identify 2-3 key options to present or communicate that would get the user 95% of the possible benefit. I am guessing that these are parameters on the boot process... Yet some look like parameters for YAST, and so could be set in the first screen. Perhaps others could do a "reboot" to set them as the user specifies? With regard to the specific linuxrc recommendations, what does adding swap do for me in a practical sense (Yes, I understand the concept AND implementation of paging in extreme detail, but I DON'T understand how this relates to YOUR installation scripts!). Does this completely eliminate memory concerns? End of problem, especially if I can swap on a flash drive (Although older PCs do not have a USB interface). But will this wear out a flash drive in one install? If an installation would result in more than a new hundred write cycles perhaps this would be an appropriate warning. We are not dumb, we just don't want to read the source for the installer to understand how to install! Finally, I understand that the user's behavior affects the memory needed. But you could present a small number of concrete examples at key points in the continuum (NOTE TO an uninvolved reader: The statements below are NOT correct, they are examples of the KIND of statements or options that might be provided!!!!) * Two memory requirements in each of the examples below are given with/without logging enabled. A log enables Suse to debug problems should they occur. If you disable logging and encounter problems, it will be impossible to help you. * If you accept the xyz default and go with a single partition it will install with xxx/yyy MB. You can then add and remove packages later using YAST. * If you pick the "Minimum Package Set" button you will be able to install with the minimum amount of RAM (currently 192/yyyMB). Adding additional packages later using YAST will work identically to the installer and result in an indistinguishable installation". * Performing a complex partitioning scheme requires more memory during installation. For example a system with 4 disks, 8 partitions on each, mirroring and setting up LVM would require an incremental 64/yyyMB over a simple single disk/single partition installation. This means for example that you should expect to be able to do an install with 256/yyyMB of memory if you select the minimal package set yet have a very complex partitioning scheme. * Every menu action results in more memory being needed due to logging. Your mileage will vary as your actions vary. (This gives the user a reference point, and tells him how to minimize requirements.) [ ] Check box to disable all logging to eliminate memory size dependence on navigation and browsing during installation. * "512MB should be sufficient for all installations, although excessive menu navigation during package selection or partitioning could require more memory." I also question if the default should be with logging enabled. Problems are presumably rare, and of those cases it is probably rare to send the logs to someone who can read them. Normally logging is disabled, and people are instructed to enable it in case of problems. In this case, the very act of logging appears to be causing the system to not be functional. This is not good. --- I personally am left with the question as to whether I can trust the result if I put in 384MB and it seems to work, or 256MB and select less packages and it seems to work. And I don't know if I should de-select packages to minimize the number or just run with the default to minimize changes. I wish I could make more concrete suggestions instead of beating around the bush, but I don't know enough. I believe a few key additions to configure the installer and a few simple statements of explanation would go a very long way to enabling users to install Suse with the minimum of memory. If you got this far, thank you for listening, and I hope this helps you to make a better installer. If you can help me understand what to do in the short term, that would be appreciated too. I know you are not tech support, perhaps I can learn by listening to you through this thread. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=239630 ------- Comment #20 from webclark@rochester.rr.com 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.
https://bugzilla.novell.com/show_bug.cgi?id=239630 locilka@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED ------- Comment #21 from locilka@novell.com 2007-03-30 07:16 MST ------- Part of the .changes file: - Reporting Low-Memory issue during installation on machines with less than 384 MB (-5%) of total memory (together with available swap). User is warned not to use Add-Ons in such case (bugzilla #239630). - yast2-add-on-2.15.6 About activating swap: - Linuxrc takes care about it - I've filed an enhancement request to possibly add another workflow step for swap activation in installation/update (when there is not enough memory) About disabling logging: - I don't think it is currently possible to change logging rules once the y2base process is running... -- 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.
participants (1)
-
bugzilla_noreply＠novell.com