|
Bugzilla – Full Text Bug Listing |
| Summary: | An error can leave system unusable | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE Linux 10.1 | Reporter: | Vinay Khaitan <vkhaitan> |
| Component: | Installation | Assignee: | Olaf Dabrunz <odabrunz> |
| Status: | RESOLVED INVALID | QA Contact: | Klaus Kämpf <kkaempf> |
| Severity: | Enhancement | ||
| Priority: | P5 - None | CC: | suse-beta |
| Version: | Beta 3 | ||
| Target Milestone: | --- | ||
| Hardware: | i686 | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Vinay Khaitan
2006-02-14 11:46:20 UTC
There is still a possibility to repair an abborted installation which would also repair the bootloader. And if /boot is getting formatted, it is clear that writing the bootloader makes no sense with no content on this partition, would you agree? Let's wait for a comment of the module maintainer. Well, what is the possibility to repair the aborted instllation? I meant to say that /boot should be written right after its formatting. There are two possibilities :- 1. format /boot and write immediately the /boot records . and if that is not possible (because it requires some packages to be installed before) then 2. format /boot and bootloader just before when it writes bootloader and /boot records(I mean grub). Olaf? Please provide a comment. Both can't be done. 1. as you said, we need quite a few things installed (writing the bootloader is done changerooted after installation) We might be able to manage this with grub, as its able to read the filesystem, but this won't work with other bootloaders (eg lilo) 2. can't be done because somewhen during installation, the kernel gets installed, and after this we can't format the partition anymore As it's not required to have such a partition, and with only a '/' partition this entire request is undoable. (The reasons are valid for all SUSE versions) I'll close this invalid |